Local Version: 10.0.0
Operating System (OS) and OS version: Windows 11 Home 25H2 (OS build:26200.8246)
There is no logs on my local.
Have you been through our Windows guide yet? It sounds like the device might be blocking Local.
We have a Windows Troubleshooting guide below that goes over some common items worth checking. For example, ensure that Local is running as an administrator, that there are no security blockers, and that Local has access to update the Hosts file.
I’ve done all of that and the problem still exists
Does the device have plenty of disk space @aleksandarcapric?
If it does then you might have to try launching Local via Power Shell and then see if that works or if there is a deeper issue at play. Further instructions can be found here:
There is no Local folder nor Local.exe in Programs folder
If you installed Local choosing, “Anyone who uses this computer (all users)” instead of the default of “Only for me (username)”, Local will instead be at:
C:\Program Files (x86)\Local\Local.exe
But if you didn’t change that default setting, it should be at:
C:\Users\your-username\AppData\Local\Programs\Local\Local.exe
your-username should be replaced with your actual username. Also note that you won’t be able to see the AppData folder in File Explorer by default unless you show hidden files, but that does not matter for the purpose of running the PowerShell command.
If neither of those locations run in PowerShell for you, you can also try navigating to your logs and sharing the local-lightning-verbose.log file with us, which will be at one of these locations depending on how you installed Local (you will need to enable show hidden files in the file explorer to browse to these folders):
If Local was installed for just your user (the default) “all users”:
C:\Users\[your-username]\AppData\Roaming\Local\local-lightning-verbose.log
If Local was installed for “all users”:
C:\Program Files (x86)\Local\local-lightning-verbose.log
Thank you for the screenshot, @aleksandarcapric. It shows Local is crashing before even its logger starts.
You can try reinstalling Local, or reinstalling Local for your user account only, instead of for all user accounts. The installer is available here: https://localwp.com/releases/
I just did that and everything is the same.
Thanks for trying that, @aleksandarcapric. Did you fully remove the Local preferences folder before reinstalling? If preferences are corrupt, that could explain the failed starts you’re seeing. By default the Local installer will not overwrite existing preferences.
It doesn’t work, it’s still the same issue.
I have tried launching it in safe mode and it still didn’t open
Sorry for the continued trouble, @aleksandarcapric.
Is this the first time you’re attempting to run Local, or has it run on your system before?
Did you try reinstalling Local for your user account only?
Do you have any security or antivirus software running?
I run it once and the second time I tried to run it I couldn’t.
Yes I did and nothing has changed.
I have only Windows Security, I’ve tried to disable it and run Local again but it was the same.
Thanks, @aleksandarcapric. If Local launched ok before, you could try:
C:\Users\<your-username>\AppData\Roaming\Local folder inside Roaming to Local-backup.This is designed to give Local a fresh environment to start from in case you have corrupt configs or other files.
It doesn’t work. In Local folder there is only machine-info.json, should it be like that?
In Local folder there is only machine-info.json, should it be like that?
There should be many more files than this, but it’s probably because Local is not starting.
If the machine is managed by a company or other admin, it would be worth checking with them if there are any restrictions in place that would stop apps from launching. They may need to whitelist Local.
If you manage the machine, you could try creating a new Windows admin user account and installing Local there, or running Local from another machine if you have one available.
(Sorry not to offer a better solution. It’s unusual for Local to crash before logging starts. The info from this thread so far doesn’t point to a root cause I can help you to work around, or a bug we can fix.)
It doesn’t work too, I’ve tried running it as an administrator and it didn’t run.
I’ve tired installing a older version and it still won’t launch.
Do you happen to have access to another device you could test on @aleksandarcapric? We’ve checked about everything we can think of to try here but are still unable to replicate the same issue from our end on Windows 11. Without a replicable bug or any further logging, we’re a bit at a loss for what might be preventing this from working normally on your machine. Have you tried downloading and running any other developer applications on this device that work without issue?