How do you resolve Could not load patch: Unarchiver . . . error

[Jens.Peter.Nielsen]

I posted one 4h earlier

How do you resolve Could not load patch: Unarchiver . . . error

It solved a problem for somebody else. I don’t know enough to conclude anything. You could delete everything in documents/rack2 and reinstall rack2.0.3 But if you use ransomware protection, you would still get errors, if you didn’t add the Rack executable to the “allow” list. [image] Not sure the devs can solve all install errors - but it would be nice if a filename was giving on the “unlink” error, to narrow it down.

[PaulPiko]

Ah, great! I should pay more attention

[Jens.Peter.Nielsen]

thanks to Analogic in Discord

Discord - A New Way to Chat with Friends & Communities

[LarsBjerregaard]

Can’t login to that. Was it some interesting text you wanted to share?

[Jens.Peter.Nielsen]

[Squinky]

@LarsBjerregaard

If the ransomware protection thing is turned on, on your compute

I turned it on in my windows. don’t know if it’s a good idea or not, but that’s another question.

From time to time I run an app, and it makes windows pop up the notice that it was blocked. Then if it seems legit (like VCV saving a patch) I allow that app, which is a one time thing.

[rbnicklas]

Lars,

Thanks for asking. It turns out that Jens’ suggestion to remove the read-only file protection on files within the Rack2 folder did resolve the issue (see above), both when trying to open files and creating new ones.

So, thanks to Jen for the clear and thorough help.

In my case, ransomware settings in Windows did not seem to have an effect (and I did explore those settings as Jens had suggested above). I can see how such settings might affect VCV Rack’s ability to write to selected folders.

[LarsBjerregaard]

@rbnicklas

remove the read-only file protection on files within the Rack2 folder

Yes, but if you have the ransomware thing turned on IT will have made the files read-only, it didn’t happen by itself. So the core issue is the ransomware setting.

@rbnicklas

in my case, ransomware settings in Windows did not seem to have an effect

Well, you never answered whether it was turned on or not, and I’ll bet you that if it’s turned on, and you haven’t added Rack to its exclusion-list, it will happen again in the future, because it’ll set the files and directories read-only again. Setting the files read-write yourself is not the right solution methinks, turning off ransomware protection or at least excluding Rack from the list, is. But glad it’s working for you now, for the moment…

[LarsBjerregaard]

Good news, looks like the issue will be fixed in the upcoming release:

https://community.vcvrack.com/t/vcv-rack-2-0-4-pre-release-available/15619?u=larsbjerregaard

• Make Windows installer add Rack to list of CFA allowed apps, allowing Rack to write to “My Documents” folder if Controlled Folder Access is enabled.

[user913]

I solved it by disabling AVAST But i’m with windows 7

[seismologist]

I’m on Win 7 for audio work, too.

Anyway, I can confirm that Avast’s ransomware module was the culprit. No need to disable Avast completely, just the ransomware “feature.” This will fix the unarchiver issue, as well as issues with updating VCV and plugins.