Can't save files - You don't have permission to save in this location
I am a new Musescore user on a Windows 10 machine.
When I try saving my score with Save As, I get an error that says "You don't have permission to save in this location. Contact the adminstrator to obtain permission. Would you like to save in the XXX folder Instead?"
The file will save ok to the desktop but not to the location that is set in preferences or other locations of my choosing.
I've tried running as Adminstrator although the User profile is already set as Administrator. I've also looked at the permissions on the folders using Explorer and they aren't any different than anywhere else.
Love the software but frustrated by this problem.
Thoughts?
Comments
Even the Administrator is not allowd to do everything, esp. not to write into system directories.
Where exactly is it writing to, what is your Preference setting and what other locations do fail?
I believe on the system drive (C:) you're confined to \users\yourusername
In reply to Even the Administrator is not by Jojo-Schmitz
I am trying to write into the default director. It is in \users\myname\documents\musescore\scores.
I have permission based on being able to do operations there from Windows Explorer. Have tried other locations to and have the same problem.
I'm no expert on Windows, but it sounds from your description like maybe the *application* is not installed with the right permissions. That is, you are a user might have permission to write to that folder, but maybe the application is running as another user somehow. Also, be sure you are checking the permissions of the right "version" of your documents folder. Normally there is one that is entirely local but another one that livers within OneDrive, and depending on how you have things configured, it might not always be obvious which one you are actually in at any given point.
In reply to I'm no expert on Windows, but by Marc Sabatella
I had *exactly* this same problem when I first moved from windows 7 to 10. Nothing I tried would fix it. After some months, the problem resolved itself (presumably following an automatic update).