-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prusaslicer wont open 2.3 windows 10 #5812
Comments
Your PrusaSlicer.ini file is corrupted, it is likely caused by the system crash you mentioned. Delete the PrusaSlicer.ini file and restart the PrusaSlicer. |
where can i find that file? |
the path is in the screenshot you posted. |
thanks guys! i did end up loosing some of my settings but its back! =] |
that configuration could be recovered in the case PrusaSlicer.ini is corrupted during saving. The config is first written into a temp file marked with a MD5 checksum. Once the file is saved, it is copied to a backup file first, then moved to PrusaSlicer.ini. When loading PrusaSlicer.ini fails, the backup file will be loaded instead, however only if its MD5 checksum is valid. The following "Fixes" comments are for github triggers. We implemented a workaround, not a fix, we don't actually know how the data corruption happens and why. Most likely the "Move file" Windows API is not atomic and if PrusaSlicer crashes on another thread while moving the file, PrusaSlicer.ini will only be partially saved, with the rest of the file filled with nulls. We did not "fix" the issue, we just hope that our workaround will help in majority of cases. Fixes prusaslicer wont open 2.3 windows 10 #5812 Fixes Won't Open - Windows 10 #4915 Fixes PrusaSlicer Crashes upon opening with "'=' character not found in line error" #2438 Fixes Fails to open on blank slic3r.ini %user%\AppData\Roaming\Slic3rPE
that configuration could be recovered in the case PrusaSlicer.ini is corrupted during saving. The config is first written into a temp file marked with a MD5 checksum. Once the file is saved, it is copied to a backup file first, then moved to PrusaSlicer.ini. When loading PrusaSlicer.ini fails, the backup file will be loaded instead, however only if its MD5 checksum is valid. The following "Fixes" comments are for github triggers. We implemented a workaround, not a fix, we don't actually know how the data corruption happens and why. Most likely the "Move file" Windows API is not atomic and if PrusaSlicer crashes on another thread while moving the file, PrusaSlicer.ini will only be partially saved, with the rest of the file filled with nulls. We did not "fix" the issue, we just hope that our workaround will help in majority of cases. Fixes prusaslicer wont open 2.3 windows 10 #5812 Fixes Won't Open - Windows 10 #4915 Fixes PrusaSlicer Crashes upon opening with "'=' character not found in line error" #2438 Fixes Fails to open on blank slic3r.ini %user%\AppData\Roaming\Slic3rPE
Transactional saving of PrusaSlicer.ini implemented in PrusaSlicer 2.3.2-beta. |
2.3
windows 10 pro build 19041.746
prusa mk2.5s
Behavior
*Describe the problem: when i try to open PS it pops up this error every time. i had a system crash earlier and had to shut the pc down now this pops up
Steps needed to reproduce the problem: attempt to click on "prusa-slicer.exe"
Expected Results: open prusa slicer
Actual Results: PrusaSlicer GUI initialization failed pop up window
The text was updated successfully, but these errors were encountered: