Musescore will only start when run with Admin privileges
I have the latest Windows 10 and Musescore and have used Musescore for many years successfully. Recently it wouldn't start (not even to show the splash screen) unless I ran it "as Administrator". I tried killing the process in task manager, but no difference. I uninstalled, removed all residue files from .../documents/musescore, Program files, App data and all mentions of musescore in the registry. I installed the latest version and it would not start from the last dialogue box of the install script (or subsequently) unless I run "as Administrator". It looks like some sort of permissions problem, but what, where and how to put it right.
Comments
Did you install it as admin? Did you install it "for all users" (should be an option somewhere in the installer I think)?
In reply to Did you install it as admin?… by Marc Sabatella
I installed it as a standard user, but was asked for admin password as part of the install. No option to install for all users.
In reply to I installed it as a standard… by Midi-man
Create another user with admin rights?
In reply to Create another user with… by Shoichi
Or tick the "run as administrator" box in the advanced properties of the shortcut.
In reply to Or tick the "run as… by SteveBlower
Yes - that's what I've done as a workaround. Really wanted to know what Musescore is doing before it shows the splash screen, so I can work out why it's failing to start.
I have just installed the latest Windows update "KB5000808" and afterwards tried running Musescore as a standard user. It worked perfectly. I have no idea whether this solved the problem or not, but unless it recurs, I think this issue should now be closed.
Many thanks to all of you who took the time to read my post and make suggestions.
In reply to I have just installed the… by Midi-man
Thanks for the feedback.
The issue seems not to be connected with the Windows update, but Musescore not being able to access a network printer which was offline. If I waited (about 10 minutes) after starting Musecscore, it suddenly loaded, having I guess timed out the request. Changing the default printer to "print to PDF" seems to have solved it. When I started Musescore as Admin the default printer was "print to PDF", so that explains why that worked.
In reply to The issue seems not to be… by Midi-man
Aha, good catch! We currently check the default printer to try to understand what a reasonable default page size should be for new scores. It's a terrible hack that causes any number of problems, but so far it seems no one can agree on the better way to solve this in a way that works for all operating systems and all locales.