Your side might be good, how’s the server you’re trying to download from doing? This was happening with a few plugins for me, I came back and tried again a few hours later and they went through fine.
just chiming in to say i also have this problem with Nysthi and Valley plugins (Windows 10, Rack 2 Pro)
Same problem with Valley and Ohmer. I’m on Macbook OSX 10.15x
Wow, that’s weird. I came to this forum cause I’m facing the exact same problem right now, looks like I’m not alone with this.
I just did it. Those two had popped up in the library as needing update. Did it and they are fine now.
Rack v2 has a 10 sec max download time when updating plugins, so if a plugin doesn’t finish in that amount of time, the update cancels. This is affecting a lot of the larger plugins. I contacted VCV support about it, and hopefully it gets fixed soon (either with a longer timeout, or by removing the limit altogether)
5 Likes
Ah, interesting–so that’s presumably why it sometimes skips over plugins and requires multiple passes to update?
Yeah, sometimes you get lucky with plugins right at that limit and your internet is a little faster, bringing it under that 10 sec limit
Ah! Yeah, I just watched this happen several times with Substation, NYSTHI, and Valley, all of which I would dearly like to have now in V2 
For anyone wondering if this is happening to them, you’ll see the percentage counting up, then it will either flash up much faster or just reset to the version number, there won’t be a check-mark, and the next plugin (if there is one) will start downloading.
Even after the timeout is redefined to be less hair-trigger (like e.g. 30 seconds since the last packet was received, not 10 seconds to do the whole thing) it would probably be good to color the failed plugins in red with a tooltip, or something. Right now it’s not even clear from the interface that something has gone wrong.
1 Like
For me, are the “ohmerprems” and “valley” module, which does not install, I noticed, unlike the others, when downloading the “* .vcvplugin” is zero bytes when it is created, so no ‘’ installation when restarting the application.
1 Like
Oh, that is super interesting. I’d say “mystery solved”. It is pretty bad to give no error message. Is there at least something in the log when this happens?
I don’t know about no time out… In my experience most front end proxy servers will time out after a minute or two. Don’t know why really, but it seems “normal” to me now… 10 seconds, however, is crazy short.
1 Like
Yup, it’s in the log, but easy to miss
1 Like
I tend to agree, although really until this release it’s not really happened much before, and Andrew is pretty ruthless with not added non-essential features (probably one of the reasons he can so something as amazing as VCV).
I know at work someone would probably make me work for a week on something like that 
1 Like
Agree, and good point. Optimizing the user experience for very atypical events/circumstances is probably not a good use of Andrew’s time.
The 10sec-to-complete rule is trivial to (and much more important to) change.
yep, make it a minute and people would be a lot better off.
1 Like
I tried again now and both downloads were successful!
Had the same problem here, after several attempts, udating - restarting - updating again - restarting and so on, my installation got corrupted apparently, so it never would have fully solved the update process with the obligatory restart. So I decided to uninstall everything. after uninstalling and then re-installing VCV Rack2Free, everything showed up in the module browser without me having to hit update again.
Just for those like me who apparently got stuck in a vicious loop)))
Note that I previously also had the beta installed, which I removed in the process as well.
Looking at the steps towards the solution, I have a feeling the issues were down to people using my beta modules before the library version became available. Rack thought it already had the correct version installed. So yeah, deleting the Valley folder in Rack2/plugins will trigger a reinstall where Rack will then download the library version. Hopefully it should be plain sailing from now on.
1 Like
I have the same problem with some modules, someone suggested on me on FB to install the missing modules manually by downloading them directly from Github and copying then in the plugin folder. It worked for me for NYSTHI, wich is great already ! but not I couldn’t find the rest on GitHub… thanks for explaining this with the 10 sec update limit, it totally make sense. hope there will be a solution for this. but still great that V2 is out and thanks to all the Devs who are doing an amazing job !
my installation for your modules stops for me at 30-50%. ive tried several times, and i dont have any beta modules to confuse the system… if no one knows what is wrong, or how to fix it, i will just be patience and try it again now and then