Could not load patch: Unarchiver could not write file to dir: could not unlink. Help Please

[LarsBjerregaard]

@ScreenSlave

You need to do this every time you open a patch. This is the only fix I have tried that works every time.

The permanent and correct “fix”, on macOS, is: Go to “settings => privacy & security => files & folders”. On the list of apps look for VCV and give it write access to your Documents folder. VCV support says they believe this will be fixed in the next Rack release, so that Rack always will have write access to the Documents folder.

stuck in a loop trying to get it to run on M1 Mac

This is very interesting. I’m not on latest macOS but I should check on my wife’s machine. So, it seems like in newer versions of macOS, Apple has gone down the same route as Windows, to combat ransomware, and has started to prevent “non-authorized” apps from having write-access to the Documents directory and its sub-directories. I wonder what apps are automatically authorized to write to Documents, maybe when they’re from the app store? But at least it seems like VCV Rack is not automatically…

On Windows, you need to go to Settings, then “Ransomware Protection” and “Controlled folder access”, and allow VCV Rack access to the Documents folder. This was actually adressed in the Rack 2.0.4 installer and shouldn’t be an issue anymore.