Hey @vyshnavi, Welcome to the Local Community Forums!
Thanks for trying out Local. It’s hard to say what exactly isn’t working. Can you provide the Local log so that we can see what Local is going through?
If you need help finding that log file, there’s a link above.
Hey @vyshnavi – I’m not seeing anything obviously breaking within the Local log.
Can you describe in a little more detail how Local is being installed as well as the exact version of Windows 10 that is being used?
For example, are you installing Local in a different location than what the default is?
After trying to start Local, if you open up the activity monitor, do you see any Local processes running?
Lastly, do you have any antivirus software installed? It’s possible that the this is preventing Local from running, so you might try temporarily deactivating the antivirus software and see if that allows Local to be installed and started successfully.
Are you able to attach the Local log? Additionally, do you see any Local processes running? What about any antivirus software – if you have something installed, can you try temporarily deactivating it and then installing and starting Local?
Can you describe in a little more detail how Local is being installed as well as the exact version of Windows 10 that is being used?
vyshnavi : Windows 1909
For example, are you installing Local in a different location than what the default is? Vyshnavi: No… Just clicked on Next after the exe is downloaded.
After trying to start Local, if you open up the activity monitor, do you see any Local processes running? Vyshnavi: Yes from task manager
Lastly, do you have any antivirus software installed? It’s possible that the this is preventing Local from running, so you might try temporarily deactivating the antivirus software and see if that allows Local to be installed and started successfully.
Have you tried restarting Windows after the initial install, and before trying to run Local? I’ve seen Local experience problems on Windows after install or update that a restart has cleared up. Perhaps files, processes, ports, etc. may have been locked or held by the OS or other processes.
@burt is right – maybe a restart of Windows will help clear up any lingering processes.
If that doesn’t clear things up, can you show us the actual processes from the task manager?
I would think that if those processes are running, then the Local window would be showing. One other thing to verify – do you have any external monitor attached? Is it possible that the Local window is on a different monitor or in some way hidden from view behind another window?
Same, wanted to try out Local, but no worky. I tried to uninstall, reinstall, restart, run in safe mode, run as admin, install in different location, on different drive, delete the folder in appdata, nothing, just three processes in task manager, nothing in taskbar, nothing on screen. I have Windows 10 Version 20H2. Downloaded and installed local-5.9.7-windows file. I have no antivirus except from windows defender. This guys log file looks same as mine. local-lightning.log (4.3 KB)
The above comment mentions that Acer computers come with a binary ( ePowerEvent.exe) that was preventing the window from opening. Do either of you have something similar running when trying to start Local?
Unfortunately, that’s not going to be it. I don’t have a laptop. I have an intel-based desktop pc. Also, I don’t think there is any software blocking Local from showing, as I ran it in safe mode where only necessary windows programs are running and it didn’t show there either.
That’s definitely odd. Do other electron-based applications work on this computer? Some common ones include VS Code or Slack Desktop.
Do older versions of Local work? For example, if you try manually installing the 5.9.0 version, do you encounter the same issue of Local’s window not opening?
If rolling back to the 5.6.10 version does get Local to load for you, I might merge these two topics so that we can zero in on what specifically broke after 5.6.10.
Just posting to say that I installed Local for the first time today and experienced the same issue with the most recent versions. Rolling back to version 5.6.10 worked for me.
I’m writing to let know that I’m facing the same issue, test all releases from latest (5.9.8) back to 5.6.10, leaving this last the only working on my system.
I may have found the problem, If some one on the Local Development Team can contact me, I can give more detal.
POSSIBLE BUG:
When running Local with versions superior of 5.6.10, on Windows 10 PRO , WMIC Sub process its not found, throwing an error, making the Local Process not to load completely.
