SABnzbd Forums

I can confirm the same issue after upgrading from 1.2.2. to 1.2.3. Deleting the CRYPT32.DLL fixed the issue for me.

I am running Win XP in a VirtualBox that I only use for this purpose (don't judge the old OS please).

Could you also try 2.0.0RC1 for me? (the standalone)
So I know if I fixed it correctly in the building.

safihre wrote:Can you maybe try SABnzbd 2.0.0RC1, just released it today with updated build process to not rely on the platform DLL's.

Yes, I tried both the 32-bit and 64-bit standalones. No errors at launch.

Also as an aside - I installed cryptography from source in a similar VM and didn't have any errors when generating a self-signed certificate (using their tutorial in the docs). I didn't spend a lot of time with it but (initially at least) it doesn't appear to be a problem with the package. It was built against the same version of OpenSSL that was used when building Python.

It turns out you were right. The packaging software just copied all the DLL's that were ever used by modules and we already deleted a few before after building since it should use the system one.
So I just had to add this Crypto.dll one to the list-of-DLL's-not-to-package and all is good

Thanks for giving the pointers!