Local 5.7.4 not starting (Windows 10). Shows three processes in task manager but nothing happens

Hi, Ben. Thanks for the idea. We tried that a while back without any luck although this morning we uninstalled Sophos again but this time attempted to load Local in Safe Mode only. Unfortunately the newer versions are still not loading.

Previously I mentioned 5.6.6 was the last best install but we did not attempt the subsequent versions prior to 5.7.1. Testing each 5.6.X, the final version, 5.6.10, was found to be the last known working version of Local.

Comparing 5.6.6 and 5.6.8 using git tracking, we’ve spotted a corrupt composer file (composer.zip (498.0 KB) (found in Local\resources\extraResources\bin\composer\posix\composer) but it doesn’t seem to be the culprit as the subsequent versions leading up to 5.7.1 load fine.

We have found something has changed in 5.7.1 that is preventing Local from running and we believe it may be to do with the node_modules in the app. For instance, in 5.6.10, the app loads as expected with the following folder contents in the resources folder:

image
image
image (note: one package)

In 5.7.1, the app doesn’t load. The app.asar.unpacked folder is also empty.
image (note: 0 node_modules)

I’m certainly no app developer and I understand the app.asar doesn’t need to be unpacked something does seem strange here. Unpacking the both versions of the app does show a lot more packages were added between these versions, so I am unsure what to expect for the folder structure here.

Is any of this normal behavior for the installations?