"Sometimes" no longer possible to restart MuseScore
Use latest version of Windows 10 and downloaded version 2.2 from MuseScore. Once the program was opened and closed back, it is sometimes no longer possible to restart the program. The program works back, after restarting Windows. To be honest I can miss this way of working like toothache.
Please make sure that when you close your program, the printer tool is removed from the RAM.
Thanks in advance.
| Attachment | Size |
|---|---|
| vlcsnap-00001.png | 401.9 KB |
| vlcsnap-00002.png | 323.46 KB |
Comments
MuseScore has problems staring up if it can't communicate with the default printer (it needs that to determin the correct default paper format)
In reply to MuseScore has problems… by Jojo-Schmitz
Once MuseScore. EXE is started and closed back, the splwow64. exe file remains resident in memory as long as Windows is not restarted. The file splwow64. exe does not allow two instances to be created in memory. As a result, MuseScore is sometimes blocked.
In reply to Once MuseScore. EXE is… by [DELETED] 28863248
I don't see any splwow64.exe on Windows 7 while MuseScore is running nor after, but indeed on Windows 10.
I've never had an issue with restarting MuseScore though, subsequent starts just seem to take the running splwow64.exe.
I don't think MuseScore has any control over this.
Instead of restarting Windows, how about killing that splwow64.exe?
Is https://support.microsoft.com/en-us/help/2856657/splwow64-exe-process-d… related?
In reply to I don't see any splwow64.exe… by Jojo-Schmitz
Indeed, I killed that process. However, it is not a normal behavior. For those who have no understanding of all these tools and do not know what is going on. They must restart Windows. Even though MuseScore will hardly have any control over it, it has nevertheless been good to mention it.
Greetings :)
In reply to Indeed, I killed that… by [DELETED] 28863248
Sure, killing it was ment to be a workaround.
I wonder whether this is only an issue with certain Windows 10 versions, maybe introduced with 1803? I'm still on 1709.
In reply to Sure, killing it was ment to… by Jojo-Schmitz
This is may be the case. Microsoft Windows does have more issue that never get solved, just think of "DPC WATCHDOG VIOLATION " and "BAD POOL HEADER " That results in blue screen and crashes.
:)