Local Community

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

I’ve never used Local before and thought I’d give it a shot but after installing, I run it and nothing happens. There are three Local processes running in task manager but that’s it.

From what I’ve looked up online, I should be getting a window that prompts me to install other dependencies such as Virtualbox. I already had virtualbox installed so I tried uninstalling that and Local then reinstalling Local but I get the same problem.

I’ve tried closing Local in task manager and restarting it (running as admin this time) but still I get the same issue.

Here is my log file:

{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%resourcesPath%%\lightning-services\mailhog-1.0.0+3\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.374Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%resourcesPath%%\lightning-services\mailhog-1.0.0+3\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.376Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%resourcesPath%%\lightning-services\mariadb-10.4.10+4\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.377Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%resourcesPath%%\lightning-services\mariadb-10.4.10+4\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.410Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%resourcesPath%%\lightning-services\mysql-8.0.16+5\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.411Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%resourcesPath%%\lightning-services\mysql-8.0.16+5\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.447Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%resourcesPath%%\lightning-services\nginx-1.16.0+3\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.448Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%resourcesPath%%\lightning-services\nginx-1.16.0+3\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.480Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%resourcesPath%%\lightning-services\php-7.3.5+10\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.481Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%resourcesPath%%\lightning-services\php-7.3.5+10\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.509Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Loading Add-on: %%appPath%%\node_modules\@getflywheel\local-addon-broken-link-checker\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.510Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“level”:“info”,“message”:“Successfully Loaded Add-on: %%appPath%%\node_modules\@getflywheel\local-addon-broken-link-checker\lib\main.js”,“timestamp”:“2020-09-14T09:43:02.511Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\local-browsersync\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.512Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\local-browsersync-client\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.512Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\local-components\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.513Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\localcert\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.513Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\localtunnel\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.513Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “productName” specified in package.json: %%appPath%%\node_modules\@getflywheel\memoize-one-ts\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.514Z”}
{“thread”:“main”,“class”:“AddonLoaderService”,“message”:“Add-on does not have “main” or “renderer” specified in package.json: %%appPath%%\node_modules\@getflywheel\replacestream\package.json”,“level”:“info”,“timestamp”:“2020-09-14T09:43:02.514Z”}
{“thread”:“main”,“reason”:{},“p”:{},“level”:“warn”,“message”:“Unhandled Rejection.”,“timestamp”:“2020-09-14T09:43:02.556Z”}

VirtualBox was a dependency for older (pre 5.x) versions of Local, but newer versions of Local don’t rely on any virtualization and having Virtualbox installed shouldn’t cause any issues with Local running.

From the above error log, I’m not seeing anything obviously causing problems.

You mention seeing three processes – are there any Windows showing in the taskbar? Can you to <ctrl>+tab to see if there are any windows that are being hidden behind something?

It’s definitely not showing on the taskbar or system tray, nor is it showing up with alt+tab, ctrl+tab or windows+tab.

If you kill those processes, restart the computer and try to run Local again, does anything change? Are there additional entries within the Local log after doing those things?

No, same issue unfortunately. It shows up in task manager as 3 processes and nothing happens.

Sorry, I forgot to add the updated log to the last message. This is the whole log after several restarts.

local-lightning.log (68.2 KB)

Whenever I launch Local, I notice the following warning in Event Viewer:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user CASTRIA-PC\Castria SID (S-1-5-21-3950659860-3171604669-3266963451-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

This apparently has something to do with something called PerAppRuntimeBroker.

After doing some diggin, the above Event Viewer entry is apparently a normal process of Windows and not indicative of a problem with a program so is almost certainly not what’s causing Local to not start.

I’ve tried installing Local to a different location on a different drive but still it won’t open.

+1

Hi. We have been experiencing this issue of Local not loading for the past few releases for each of our Windows machines. Each time we update to the new release, we experience these same symptoms Castria has mentioned, i.e. 3 background processes, no window (it’s definitely not hidden off-screen somewhere). During the uninstallation process, it prompts to close Local as if it is open.

No amount of restarting or uninstalling combinations seems to resolve. As suggested by Clay in another thread, to no avail, we also tried deleting the window-state.json in AppData.

As with each such case, we end up rolling back to version 5.6.6 which loads as expected.

Attached is the log in case it’s of any use.

local-lightning.log (934.0 KB)

Cheers,
Jeff

I can confirm after seeing jamergin’s message that I can get Local to run fine by installing 5.6.6. The latest version will not run and I’m still unable to discover anything that is causing that.

Thank you for continuing to look into this!

I haven’t been able to replicate this issue, but when I started googling for the above string, some of the content out there seems to point to a permissions issue with the Windows Registry.

I’ll be honest and say that it’s been a while since I’ve monkeyed around in the Windows Registry, but I could see how something like steps outlined in this post might help:

Do either of you have experience with this sort of troubleshooting? I wouldn’t recommend tinkering with the Registry unless you’re pretty comfortable with taking backups and restoring the system, since it’s easy to mess something up.

If you are up to trying things, I’d be curious to know if the above steps help grant Local access to run on your system.

One other thing, since I’m having issues replicating on my Windows test box, I’d be curious to know if there’s anything special about these Windows machines. For example:

  • Are these work computers from an employer that might have special security settings in place?
  • Are you running Windows Pro or Windows Home edition?

I had found near-identical solutions myself when looking in to this problem. It didn’t fix the issue for me. The errors kept showing up in event viewer and Local kept not opening. The guide you linked had a couple of differences so i went through it just in case but still no luck. Event viewer keeps showing the warning and Local still isn’t opening.

I completely uninstalled Local and restarted my computer and reinstalled but still nothing.

I’m on my own home computer which i also use as my work computer (self-employed) and there’s no special security settings in place. I’m running Windows 10 Home edition.

Thanks, Ben, and sorry for the delay. This is a work PC running Windows 10 Pro and Sophos.

Confirming this is still an ongoing issue with the latest versions and we are only able to get 5.6.6 to work so we are missing out on the new innovations in newer releases.

Upon inspecting Event Viewer, we are also receiving the same warning as castria:

   The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user XXXXXXX-XXXXXXX\XXXXXXXSID (XXXXXXXXXXXXXXXXXXXXXXXX) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

We have followed the steps detailed in the link you provided and ran through the steps again for the other CLSID and APPID for PerAppRuntimeBroker (below) to modify the grant activation.
HKEY_CLASSES_ROOT\CLSID{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
HKEY_CLASSES_ROOT\APPID{15C20B67-12E7-4BB6-92BB-7AFF07997402}

Unfortunately this has not worked and, as castira mentioned, we have found Microsoft has reported it can be safely ignored and appears to be unrelated as detailed here:

event-10016-logged-when-accessing-dcom

In case it is of any use, here are the details for the event where I’ve obfuscated my computer name, user and SID. It shows missing values for parameter 10 and 11.

**-** **System**

|||**-** **Provider**

[ **Name** ] Microsoft-Windows-DistributedCOM

[ **Guid** ] {1B562E86-B7AA-4131-BADC-B6F3A001407E}

[ **EventSourceName** ] DCOM|
| --- | --- |

|||**-** **EventID** 10016

[ **Qualifiers** ] 0|
| --- | --- |

**Version** 0

**Level** 3

**Task** 0

**Opcode** 0

**Keywords** 0x8080000000000000

|||**-** **TimeCreated**

[ **SystemTime** ] 2020-10-16T04:50:14.001477700Z|
| --- | --- |

**EventRecordID** 44427

|||**-** **Correlation**

[ **ActivityID** ] {326609aa-724a-48f0-b932-f82a1f250513}|
| --- | --- |

|||**-** **Execution**

[ **ProcessID** ] 1252

[ **ThreadID** ] 24464|
| --- | --- |

**Channel** System

**Computer** XXXXXXXXXXXX

|||**-** **Security**

[ **UserID** ] XXXXXXXXXXXXXXXXXXXXXXXX
| --- | --- |

**-** **EventData**

**param1** application-specific

**param2** Local

**param3** Activation

**param4** {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

**param5** {15C20B67-12E7-4BB6-92BB-7AFF07997402}

**param6** XXXXXXXXXXXXXXX

**param7** XXXXX

**param8** XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

**param9** LocalHost (Using LRPC)

**param10** Unavailable

**param11** Unavailable

From what I’ve noticed when Local does run, there are 4 background processes. The versions that are not working are only showing 3 background processes. Sometimes when analyzing the wait chain, there is an unfinished process on one of the 3 background processes.

image

Cancelling this process and restarting Local so all 3 processes are ‘running as normal’ still does not load the 4th process.

We will keep looking and report back if we find anything further.

Cheers

I wonder if Sophos is blocking something?

Local is built on Electron which means from an architectural standpoint, there are a few processes that it spawns – the main thread and usually a couple of worker threads.

Is there a way to temporarily stop Sophos to see if that is what is preventing Local from working? If it is, we can start to zero in on the exact thing that Sophos doesn’t like.

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?

In case it helps, it’s the renderer thread that is the missing process which I guess is the window itself.

4 background processes running 5.6.10

3 background processes running 5.9.0

Here is the full version of the command line for the 5.6.10 --type=renderer process is below in 2 parts because I couldn’t fit it all in one screen:


Maybe something helpful in there.