[SOLVED] Unable to locally save new score in MuseScore 4.1.0.
A brand new MuseScore 4.1.0 file fails to be saved locally.
I updated from MuseScore 4.0.2 to MuseScore 4.1.0 then this problem occured. It seems the file fails to create itself. I reinstalled MuseScore and the problem persisted. I am on a 64-bits Windows 10 computer.
Below are screenshots of the error message and the process I took for a file creation.
| Attachment | Size |
|---|---|
| MuseScore41Update.zip | 365.32 KB |
Comments
It's hard to say much from just pictures. Please attach the score you are having trouble with and list precise steps to reproduce the problem. Just type the instructions; much simpler for both you and use than trying to piece the steps together from screenshots.
In reply to It's hard to say much from… by Marc Sabatella
I cannot attach the score as it cannot save itself. The file does not create itself upon saving. To reproduce the problem, try creating a blank new score and save this score. The "File not found" error will then show.
In reply to I canve inot attach the… by markorandjic
That's a very strange folder name. What happens if you try saving somewhere else? Seems likely to be a permissions problem somewhre in that path on your system. Your user name probably shouldn't have all that "DESKTOP" stuff in it.
In reply to That's a very strange folder… by Marc Sabatella
The addition of the "DESKTOP" was automatically added on user creation. The saving process worked perfectly well on MuseScore 4.0.2. As for what happens when I save somewhere else, it successfully saves. I shall tinker more to understand the condition under which this fails. Thanks for your help!
In reply to That's a very strange folder… by Marc Sabatella
I have tried to save under administrative rights, but the error persists. It seems to only happen in the C: drive, where MuseScore is installed.
In reply to That's a very strange folder… by Marc Sabatella
I have solved the problem, Microsoft Defender flagged the file creation as a threat, therefore not creating it. Thanks for your time!
In reply to I have solved the problem,… by markorandjic
How did you tell Microsoft Defender to ignore the threat? A similar thing seems to be happening to me.
In reply to How did you tell Microsoft… by kieferpbernar
Same thing happened to me after upgrading to MuseScore Studio 4.3.1. Turning off Real-time protection didn't work
(Settings--> Privacy & security --> Windows Security --> Real-time protection. Toggles on/off (don't forget to turn it back on,).
In reply to Same thing happened to me,… by Edewarn
I SOLVED IT! TURN OFF CONTROLLED FOLDER ACCESS
Hello all, I started having this problem when I inadvertently enable the controlled folder option in Windows, for the life of me I would never have found out what the problem was without the information in this thread, so thanks a lot.
However, I'm puzzled as to why this problem occurs with Musecore 4 and not, that I have noticed, with any other of the many applications that I use, including Musescore 3, to which I recurred while I could not manage to get MS 4 to save files.
Why is Windows particularly suspicious of Musescore 4? Is this an issue that the Musecore team would be looking at?
In reply to Hello all, I started having… by josemdavid
Seems more likely a bug in Windows - it shouldn't be preventing any application from writing to the normal Document folders. Please be sure to report it to Microsoft.