Error Loading python39.dll

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
gnmusgrave
Newbie
Newbie
Posts: 2
Joined: April 4th, 2021, 8:31 am

Error Loading python39.dll

Post by gnmusgrave »

I just upgraded from V3.2.0 to 3.2.1 on a Win 7 SP1 system.

All previous versions have worked perfectly.

I cannot start the new version. I get the following error:

C:\Program Files (x86)\SABnzbd-3.2.1>SABnzbd-console.exe
Error loading Python DLL 'C:\Program Files (x86)\SABnzbd-3.2.1\python39.dll'.
No error messages generated.
FormatMessageW: The parameter is incorrect.
LoadLibrary: PyInstaller: FormatMessageW failed.

Any suggestions?

Thanks.

User avatar
safihre
Administrator
Administrator
Posts: 4240
Joined: April 30th, 2015, 7:35 am
Location: Switzerland
Contact:

Re: Error Loading python39.dll

Post by safihre »

Yes, Windows 7 is no longer supported by Python 3.9.
You can use the Legacy version of Sabnzbd from the Downloads page. This is also mentioned in the release motes.

I'm surprised you even managed to install it, did you use the installer? It should block you from installing it on Windows 7 system and redirect you to the Downloads page.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate

gnmusgrave
Newbie
Newbie
Posts: 2
Joined: April 4th, 2021, 8:31 am

Re: Error Loading python39.dll

Post by gnmusgrave »

I didn't use the installer. I downloaded the standalone version, but used the 64-bit version rather than the 32-bit and legacy version (didn't read the message carefully enough!). Problem now solved! Thank you!

I guess I'm going to have to bite the bullet and change to Win 10 soon if this sort of thing continues. I applied the free upgrade from Win 7 to Win 10 several years ago, and it was a world of pain for several days. That early version of Win 10 broke many things on my system, and then I had to rebuild a lot of stuff after applying the "seamless" regression back to Win 7 that was provided in the newly upgraded Win 10. Since then I've avoided Win 10 like the plague. However, now it seems I might have no choice. The saving grace might be that Win 10 has been updated many times since then, so maybe it will be a smoother transition now. Sigh....

Post Reply