Installing on Windows 11 throws a security warning:
(I appreciate the shot above is from HELO, it happens in Invoker as well!)
You have to 'Run Anyway' and then 'More Info' and force it past this screen in order for the installation to complete, assuming you have the right user permissions to allow this; otherwise, it will just fail silently.
More worryingly, if you download the installer exe via Chrome, then try to run it from the File Downloads panel, it will actually crash Chrome entirely, as the installer conflicts with the Chrome process when it hangs on the security prompt.
One reboot later, you can open the installer and add a project.
Then you'll get the Error: spawn /usr/local/bin/php ENOENT message because it failed to find PHP installed - and failed to tell you it couldn't find it.
Only by digging around in closed GitHub issues did I figure out how to resolve this part. This really ought to be sign-posted on the warning itself or actually displayed as a set-up step to new users "We couldn't find PHP! Nothing will work without it! Please select it now".
This is kind of crucial, and I'm worried it was overlooked, especially in a paid app. Makes me nervous about what else may go wrong because no one cared to test outside of their Macs 🤨
Installing on Windows 11 throws a security warning:
(I appreciate the shot above is from HELO, it happens in Invoker as well!)
You have to 'Run Anyway' and then 'More Info' and force it past this screen in order for the installation to complete, assuming you have the right user permissions to allow this; otherwise, it will just fail silently.
More worryingly, if you download the installer exe via Chrome, then try to run it from the File Downloads panel, it will actually crash Chrome entirely, as the installer conflicts with the Chrome process when it hangs on the security prompt.
One reboot later, you can open the installer and add a project.
Then you'll get the
Error: spawn /usr/local/bin/php ENOENT
message because it failed to find PHP installed - and failed to tell you it couldn't find it.Only by digging around in closed GitHub issues did I figure out how to resolve this part. This really ought to be sign-posted on the warning itself or actually displayed as a set-up step to new users "We couldn't find PHP! Nothing will work without it! Please select it now".
This is kind of crucial, and I'm worried it was overlooked, especially in a paid app. Makes me nervous about what else may go wrong because no one cared to test outside of their Macs 🤨