@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.
I can Confirm WMIC its the problem. But not because its not finding it, its because on Windows 10 PRO, WMIC process returns something that Local don’t like or better to say can’t be parsed. Making the application to not continue execution.
Hey @hackinc2000 – thanks for digging in and I’m sorry to not reply sooner!
Do you have more info on this, like any screenshots or steps you did to diagnose this? I’d love to have more publicly available steps to help with reproducing this!
Hi @ben.turner Thanks for your reply!!! Yes I have more information. But for security reasons and because of the methods used to diagnose this, I would prefer to send You a Private Message with the information if that its ok with You! I try but Messaging to You its disabled!
Yep! Thanks to @hackinc2000 for pushing this fix forward!
That’s interesting – the nature of the bug was that Windows was responding with data that Local didn’t expect, and Local wasn’t doing a good job of failing gracefully.
It’s possible that in some part of the configuration of your system, the thing that Windows was responding with made sense to Local and you were able to open Local without any issues.