Crash Restore last session - Corrupted MuseScore.ini

• Sep 5, 2021 - 03:31
Reported version
3.6
Type
Graphical (UI)
Frequency
Once
Severity
S1 - Blocker
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project

Hello
When you move the user interface window to an associated monitor, other than the main display, and close Musescore from that screen, then the MuseScore3.ini file is automatically modified, and the new settings saved. prevent MuseScore from reopening.
By taking care to make a backup beforehand of the .ini file, then by replacing the newly modified file with the backup, everything is in order.
If we take a closer look at the structure of the.ini file using a text editor, Notepad for example, we see that two items have been modified after closing the session from the remote screen: Geometries and MainWindow

MuseSore OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34
Windows 21H1 (build 19043.1202)


Comments

Frequency Many Once
Status active needs info

I"m doing this all day, with a Laptop and 3 screens and a desktop with 2 screens attached, never ever any problem with it, unless the secomdary screen is switched off or disconnected on a subsequent session. In wich case switchin on or connecting or reverting MuseScore to factory settings via command line or deleting those lines from the initial file helps

It wasn't long ago that it worked perfectly. I don't know what has changed: Dell driver, windows update? But obviously something has moved.
I tried unsuccessfully the following command to restore factory settings
C: \ Program Files \ MuseScore 3 \ bin \ MuseScore3.exe -F

However, I have found that if I used MuseScore on a secondary display, and brought the window back to the primary (portable) display before closing MuseScore then everything was fine.
I therefore confirm that in my configuration, MuseScore should not be closed when the program is used on a secondary screen, but only when the application is brought back to the main screen.
I found a workaround. I will wait for the next Windows update, my XPS 17 drivers, or the new version of MuseScore. Maybe that will change things.