Unfortunately, changing the read-only protection on the VCV Rack 2 folder did not resolve the issue, for me I notice that the VCV Rack folder (version 1.*) has a similar protection, yet it does not throw an error.
I suspect (and I’m only guessing) that the issue is related to parsing the VCV file on input… I did not encounter the error while using the initial VCV Rack 2 release, but only after upgrading to v 2.02/2.03.
Hopefully, the condition that causes the error will be identified and we’ll read about the solution in this forum.
Interesting Jens. Is this “Ransomware protection” a new feature in Windows, that thinks it’s a good idea to make people’s files read-only? That would be… interesting.
I wonder if Rack is treated as unknown/unfriendly because it doesn’t have a code signing certificate, so can’t write there. That’s just a suspicion, I haven’t tested that myself. If I get a chance I’ll try it with my code signing certificate and see what happens.
I haven’t read the details, I usually just turn it off.
Controlled folder access is supported on the following versions of Windows:
Windows 10, version 1709 and later
Windows 11
Windows Server 2019
Windows Server 2022
Windows system folders are protected by default, along with several other folders:
c:\Users\<username>\Documents
etc.
If “protection” on c:\Users<username>\Documents means “we’ll make your files read-only”, that sounds insane. The definition of documents is literally that the user will be writing files. Oy vey… sometimes Microsoft really looses the plot. Prepare for a deluge of user complaints for all manner of software that won’t work because of this and they have no clue why if it’s engaged by default. Yikes.
Could be, if that “Ransomware protection thing” takes that into account. But still, make people’s document files read-only to protect them against themselves is just untenable. But yeah, if this is the new norm it could force Rack into being more signed, more “approved”, etc… It’s a brave new, awful world.
Only MS verified programs can write to Documents when Ransomware protection is turned on. How you get to be verified is another question… It’s not directly related to code signing, I tried that. But you can explicitly trust a program, and then it can write to Documents (see the image in my previous message). That would be the way to do it if the user wanted to keep Ransomware protection turned on.
Windows security also keeps track of unauthorised attempts to write to Documents, and they’re shown in Protection history. You can allow the program by following the associated link
Yikes! I guess this ransomware protection thing is relatively new, otherwise we would have heard a lot about this before. And yeah, it sounds like Rack Windows users are going to be bitten hard by this, if they don’t know what’s going on. @Vortico definately needs to put this in the installation steps for Windows, until the situation might be sorted. But jeez… most people won’t know this is turned on by default, and will have no clue why their programs stop working.
This could cause issues for any program developer. The Documents folder, and Pictures, Videos, Music and Favourites are the usual place to store data for the user, and it has been the recommended practice for as long as those “special” places have existed. I’ll have to investigate this, hopefully before anything of mine gets blocked…