Version 1.17.03 - Installation was fine. It ran fine. The next day, it hung on startup. You get the splash screen and then nothing. “LIghtburn.exe is not responding,” is the only message.
I’ve opened port 443 to incoming traffic. No change.
I’ve reinstalled Lightburn. No change.
I’ve deactivated it off this machine. No change (can’t even get to reactivation).
I’ve uninstalled, reinstalled, and…no change.
Windows Defender Firewall with Advanced Security - Refresh rules…and THAT seems to work.
Brand new Windows 11 system. 64GB RAM etc etc. ASUS MB, Intel CPU, 4080 GPU.
I’m running a second seat on a laptop next to the laser. No issues. Third seat was briefly installed on a 7 year old Windows 10 laptop that can barely run anymore. No problem.
I’ve got a brand new win11 system that I need to do all the build/client work on, and it’s the only one that won’t run unless I shake security rules well before using. Wacky.
I guess I’ll just keep doing this EVERY morning until there’s a solution. A lil more help would be appreciated. I’ve got time if anyone wants to step by step trouble-shoot.
That is very strange. Is there a way you can tell Windows Defender to exempt LightBurn?
The fact that it hangs is weird. The splash screen means that the app itself is running, so it’s something after that causing the trouble. I know there is one process used in the license startup system that gets the “fingerprint” of the computer using a Windows instrumentation app that sometimes causes issues for schools, so that would be my guess, but it’s only a guess.
Try this: right-click the LightBurn icon on your desktop and choose “Properties”. Click the ‘shortcut’ tab and in the box that says “Target:” add -D to the end of it. The result should look like this:
"C:\Program Files\LightBurn\LightBurn.exe" -d
That will launch LightBurn with debug logging enabled. Run the app, wait for it to hang, shut it down however you need to, and then look in your “Documents” folder for a file called “LightBurnLog.txt”. Attach that file here, and then go back and remove the -D from the shortcut or it’ll keep appending to the log with every run, and it’ll get huge.
Hi…sorry for the delayed reply…I was busy being productive.
Once I deleted the activation and reactivated the machine, everything smoothed out. I’ve got this bookmarked in case it happens again, and i’ll debug and send logs. Cheers.
