@axel12 Removed the fix from 1.2.0 and installed the fixed installer, still works, so looks like that solves the issue for me at least.

4f6d6b2f-d186-452e-869b-be1909ecad56-image.png