When ordinary LightBurn windows share preferences, the last window closed writes those preferences to the shared file. A setting changed in one window can therefore be replaced when another window closes afterward. Save the projects separately, then reduce the session to one window before making intentional preference changes.
LightBurn's guide to multiple instances documents this behavior. Keeping one window open while changing preferences makes it easier to identify which session should save the intended state.
Follow a two-window timeline
Suppose an operator opens job A, then opens job B in a second window. Both ordinary windows use the same preference location. The operator changes a preference in A, closes A, and later closes B. The later save from B can overwrite the preference change made in A.
This is different from two people editing the same project document. Both job files might be saved correctly while the application's preferences return to an unexpected state. Reopening the correct project cannot by itself prove which application preferences survived.
Write down the intended change before closing windows. If a window has unsaved artwork, save that project under its intended name first. Do not sacrifice a project merely to force a particular close order.
Make one controlled preference edit
- Save the work in every open project and identify which files were saved.
- Close the other LightBurn windows so one ordinary instance remains.
- Export the existing preferences through the supported command for the installed version.
- Make the intended change in that remaining instance.
- Close and reopen LightBurn, then read the setting back.
- Retain a clearly labeled export of the verified state when appropriate.
The readback is the evidence that the intended preference persisted. A screenshot taken before closing shows only what one window displayed at that moment.
| X1S Pro workstation item | Save or verify it as |
|---|---|
| Artwork and job arrangement | The appropriate project document |
| Application preference change | A single-instance edit followed by restart readback |
| Recoverable application state | An identified preferences export |
| Material-library dependency | A separate Assign or Link decision |
Avoid making several unrelated setup changes during this exercise. A narrow change is easier to verify and reverse if the workstation does not behave as expected.
Separate three kinds of state
A cloud-synced project overwrite concerns competing document edits. The last-closed-window issue concerns shared local preferences. Assign versus Link in the Material Library concerns whether a layer follows a preset. These can coexist, but solving one does not demonstrate that the other two are controlled.
The TYVOK X1S Pro supports the large-format diode workflow described on its product page, including LightBurn messaging. Verify the actual device profile and software setup with TYVOK. The machine's nominal 800 × 2000 mm format does not create independent application preferences for each open job.
LightBurn documents advanced independent-instance arrangements separately. Treat those as a deliberate workstation configuration project; opening another ordinary window is not proof that it has isolated settings.
Multiple-window questions
Will saving both project files preserve every application preference?
No. Project saves and shared application preferences are different records. Verify the specific preference after restarting the application.
Can I avoid the problem just by remembering which window to close last?
That can be fragile when several windows or operators are involved. For an intentional preference change, save the projects, close the extra windows and make the edit in one remaining instance, then verify persistence.