Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.2.0Beta2 won't run on my Windows 7x64 machine. #1770

Closed
DrakeJones opened this issue Jan 27, 2021 · 14 comments
Closed

3.2.0Beta2 won't run on my Windows 7x64 machine. #1770

DrakeJones opened this issue Jan 27, 2021 · 14 comments

Comments

@DrakeJones
Copy link

3.2.0Beta2 won't run on my Windows 7x64 machine. 3.1.1 is fine.

After install trying to run or start service yields the following error msg.

"The Program can't start because api-ms-win-core-path-|1-1-0.dll is missing form your computer. Try reinstalling the program to fix this problem."

@sanderjo
Copy link
Contributor

Also https://forums.sabnzbd.org/viewtopic.php?f=11&t=25172&p=123463#p123463

Out of curiosity: why do you use Win7, and not Win10?

@DrakeJones
Copy link
Author

DrakeJones commented Jan 27, 2021

For privacy. Windows "as a service" 10 is a data-miner front. It's not really free - your personal data is the currency you lease it with. I really resent MS for that. Windows 10 "Ameliorated" (spyware removed) is available https://ameliorated.info/ but functionality is crippled badly. I also run a Linux box. If you don't plan to support Windows any longer, I'll stick with 3.1.1. SABnzbd is my preferred downloader.

<<Just read your forum post. I'll try that.>>

@Safihre
Copy link
Member

Safihre commented Jan 27, 2021

I build the 32bit version with Python 3.8. Could you see if that works on Windows 7?
https://github.com/sabnzbd/sabnzbd/actions/runs/514800684

If that works, I can keep it that way as the legacy version to support non-64bit and Windows 7 systems.

@DrakeJones
Copy link
Author

The installer is looking for the python39.dll - fails.

@Safihre
Copy link
Member

Safihre commented Jan 27, 2021

No, not the installer. You'll need to use the standalone version Windows Windows standalone binary (32bit and legacy).

@DrakeJones
Copy link
Author

Okay. That works. Thanks.

@1ColdAssHonkey
Copy link

Thank you Safihre for this customized legacy build. I am in the exact boat as DrakeJones is and was having the same issue. The standalone version works great for me too. Just one question, why a 32-bit build? Is it to make it accessible to more legacy systems than a 64-bit? Thank you again for the program!

@Safihre
Copy link
Member

Safihre commented Jan 30, 2021

@1ColdAssHonkey indeed, to make it available for all non-standard systems. There is almost no difference between the 32 and 64bit version of Sabnzbd in terms of performance etc :)

@1ColdAssHonkey
Copy link

1ColdAssHonkey commented Feb 1, 2021 via email

@antdude
Copy link

antdude commented Feb 26, 2021

I'm having the same problem with 64-bit v3.2.0 portable (https://github.com/sabnzbd/sabnzbd/releases/download/3.2.0/SABnzbd-3.2.0-win64-bin.zip) in my over decade old, updated 64-bit W7 HPE SP1 PC. :(

https://github.com/sabnzbd/sabnzbd/releases/download/3.2.0/SABnzbd-3.2.0-win32-bin.zip worked. It would had been nice if both the software (installers if used, but I don't use them) and web site say to use the old 32-bit version for old 64-bit W7 HPE SP1. :/

@Safihre
Copy link
Member

Safihre commented Feb 26, 2021

The installer will show a nice error when you try to run them on these old systems, to use the legacy/32bit version.
The changelog also mentions the dropped support for old Windows systems.

@thezoggy
Copy link
Contributor

Win7 SP1 came out - February 9, 2011; so over 10 years ago!

As you are aware many things work just fine on such outdated os if you are willing to accept the lack of security or stability updates. However, most installers let alone python have dropped support. This is outside sab's control so we have to purposely make a special build using outdated software to sidestep that issue... this is only a short term thing as the need for a 32 bit build is largely unneeded and we are using this as a hacky solution to provide a build using older python/builder to keep legacy os support. This probably will end in the near future as more and more things go against us as more dependencies stop supporting win7 and older (for example win rar/par stop supporting win7 and older).

Honestly you might be best off just controlling the dependencies yourself by running sab from source, that way you dont rely on our installer (and by proxy, what version of python we build off of). But really if that machine is connected to the internet you should upgrade to a newer os for security sake :)

@DrakeJones
Copy link
Author

Thank you very much for the legacy side build (for as long it lasts). Point(s) taken. Funny thing, I live in Italy and it was only about 4 or 5 years ago that the local ATMs were upgraded from XP to Windows 7! At least I have gigbit internet in a 600 year old building. ;-)

@thezoggy
Copy link
Contributor

an "appliance" is a bit different than a general purpose desktop os. but yeah, plenty of <appliances/iot/smart-tv/whatever> out there running old os with old applications :)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants