Yeager
(Peter Vos)
April 6, 2026, 7:16pm
1
After the second time it says it can not extract the package.
Win10.
apophene
(Apophene)
April 7, 2026, 2:29am
2
In the same boat here; Win 11.
I had a dan one that didn’t update along with chrysalis and I updated my vcv rack and now it is just chrysalis that doesn’t load… watching the video’s this thing would do nice arps and be great with python code generators. I am going to be stoked if this one works the way it is supposed to soon..
jedrzejewskimk
(Mateusz "Ghalebor" Jedrzejewski)
April 10, 2026, 6:09am
4
Chrysalis install Loop problem W11
SkwareUawe
(Andrea A.G. Grossi)
April 10, 2026, 9:20am
5
Sorry but I concur here: still in loop on Win10
celeste
(Celeste)
April 13, 2026, 5:05am
7
Hey, It seems that there is an issue with the build for windows (that in VCV is done in a cross compiler for all platforms). Looking into this to provide some fix soon.
4 Likes
Thanks for looking into this.
Yeager
(Peter Vos)
April 27, 2026, 12:21pm
9
Alas, update 2.0.1 did not solve the issue (for me)
Yeager
(Peter Vos)
April 29, 2026, 10:32pm
12
Maybe 2.0.2 will do the trick once it’s released.
opened 02:48AM - 07 Apr 26 UTC
The Chrysalis 2.0.0 plugin downloaded from the VCV library fails to load in VCV … Rack 2.6.6 win-x64 with the following warning:
```
[0.500 warn src/plugin.cpp:237 loadPlugin] Could not load plugin C:/Users/user/AppData/Local/Rack2/plugins-win-64/Chrysalis: Failed to read init() symbol in C:/Users/user/AppData/Local/Rack2/plugins-win-x64/Chrysalis/plugin.dll
```
As a result the plugin is continually listed as updatable in VCV Rack’s Library menu.
The plugin loads successfully on both my mac-arm64 and mac-x64 machines. I haven’t yet booted up my Linux machine to test it, but for now this appears to be a Windows-specific issue.
Because this is a different warning than the one reported in #4, I’ve created a separate issue for it.
Managed to build and install 2.0.2 successfully just now on my win11 laptop
1 Like
kwurqx
(Kwurqx)
April 30, 2026, 2:41pm
14
I reported this issue for both 2.0.0 (some time ago) and 2.0.1 (recently) at the Chrysalis Github project.
EDIT…just noticed a possible solution v2.0.2. I’ll try that later on Win10/x64.
2 Likes