Lightburn hangs on splash screen (V1.7.08)

I’m trying to bring up Lightburn from a desktop short cut and it just hangs. It has been a while since I’ve used it. I’m trying to run it on a Windows 11 OS. The last time I used lightburn it ran on windows 11 no problem.

TIA

Since it’s been a while since you used Lightburn it could be an issue with a windows update where they messed up the C++ files. Try the solution below.

Doesn’t work. any more ideas?

Steve

So, I added a -d to the startup of Lightburn and it created a log file. Here is the contents of that log. The " D: Duplicate entry? This shouldn’t happen" seem to happen forever. I’m guessing that is the issue.

TIA

20:41:13.465 D: “” “Mon Apr 21 2025”
20:41:13.465 D: License system started
20:41:13.465 D: No 2nd instance detected
20:41:13.465 D: Mutex created
20:41:13.671 D: Timer functions linked
20:41:13.687 D: Splash created
20:41:13.702 D: Splash shown
20:41:13.702 D: Events processed
20:41:13.702 D: no old user association found
20:41:13.702 D: no old user association found
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn’, ‘LightBurn.LightBurn.1’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn2’, ‘LightBurn.LightBurn.1’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn\Content Type’, ‘text/plain’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn\PerceivedType’, ‘text’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn2\Content Type’, ‘text/plain’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn2\PerceivedType’, ‘text’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn\OpenWithProgIds\LightBurn.LightBurn.1’, ‘’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes.lbrn2\OpenWithProgIds\LightBurn.LightBurn.1’, ‘’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes\LightBurn.LightBurn.1’, ‘LightBurn’ ): already correct
20:41:13.702 D: RegSet( ‘Software\Classes\LightBurn.LightBurn.1\Shell\Open\Command’, ‘C:\Program Files\LightBurn\LightBurn.exe “%1”’ ): already correct
20:41:13.750 D:
20:41:13.750 D: File associations set
20:41:13.750 D: Using the core prefs dir
20:41:13.908 W: QMetaObject::connectSlotsByName: No matching signal for on_actionSettings_triggered()
20:41:13.914 W: QMetaObject::connectSlotsByName: No matching signal for on_actionEdit_GameControllers_triggered()
20:41:13.924 D: UI initialized
20:41:13.924 D: Language menu initialized
20:41:15.016 D: connected
20:41:15.016 D: Window setup complete
20:41:15.016 D: EV: 1018 took 9 uS
20:41:15.016 D: Cut list initialized
20:41:15.032 D: Recent projects initialized
20:41:15.036 D: Created Tool: Selection
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen
20:41:15.174 D: Duplicate entry? This shouldn’t happen

The log entry you would normally see in that position would be ‘D: Preferences loaded’, it’s absence indicates an issue during the loading of your prefs.ini file.

Last time I saw this error it turned out to be a problem with a corrupt Art Library.

Do you use an Art library?

Make a backup copy of your current Application Settings and Art Libraries : File>Bundles>Export Bundle.

Close LightBurn.

Open Notepad and then open your prefs.ini file (Ctrl+O and paste in %USERPROFILE%\AppData\Local\LightBurn\prefs.ini).

Take note of the location and names of the Art Libraries:

To prevent LightBurn from trying to load the Art Libraries at start up you can either delete just the “ArtLibraries” field as highlighted above and save, or you can find the library file/s that are referenced and move them to a different folder or rename them.

After this, if LightBurn loads successfully… you will know it’s an Art Library issue, and hopefully you will have a backup of the affected .lbart file on your computer.

Best way to backup the Art Libraries are to include them in a Bundles Export.

2 Likes

Ok, this worked!!! I had 5 Art libraries, I eliminated them one by one till I found the offending library.

Thanks
Steve

2 Likes