par2 and unrar binarys not found after update (Windows on ARM)

[DutchG]

Hi,

I've been using your great program for a while now. But almost every time I'm running into problems after updating Sab. It installs but fails to run because of errors that both par2 and unrar binaries are not found which is weird because they are still in their default folders

It has happened on several windows installations. Luckily i'm running most virtual so i can restore a snapshot because so far i have not found a way to fix the problem.

2024-06-08 15:10:06,466::INFO::[notifier:157] Sending notification: Error - par2 binary... NOT found! (type=error, job_cat=None)
2024-06-08 15:10:06,466::ERROR::[SABnzbd:454] par2 binary... NOT found!
2024-06-08 15:10:06,466::INFO::[notifier:157] Sending notification: Error - unrar binary... NOT found! (type=error, job_cat=None)
2024-06-08 15:10:06,466::ERROR::[SABnzbd:469] unrar binary... NOT found!
2024-06-08 15:10:06,466::INFO::[SABnzbd:474] 7za binary... found (C:\Program Files\SABnzbd\win\7zip\7za.exe)

Also is there any way to completely reinstall Sab with all references gone?

[sander]

Virusscanner at work, so not allowing access to the exe of unrar and par2?

[DutchG]

Virusscanner at work, so not allowing access to the exe of unrar and par2?

Just the default Windows Defender is active. No notifications or quarantines.
This also does not explain why it was working fine before the upgrade.

Could the windows smartscreen warning have anything to do with this?

[DutchG]

Before updating it works just fine and the files are still there

2024-06-15 13:40:18,786::INFO::[SABnzbd:450] MultiPar binary... found (C:\Program Files\SABnzbd\win\multipar\par2j64.exe)
2024-06-15 13:40:18,786::INFO::[SABnzbd:453] par2 binary... found (C:\Program Files\SABnzbd\win\par2\x64\par2.exe)
2024-06-15 13:40:18,786::INFO::[SABnzbd:460] UNRAR binary... found (C:\Program Files\SABnzbd\win\unrar\x64\UnRAR.exe)
2024-06-15 13:40:18,786::INFO::[SABnzbd:475] 7za binary... found (C:\Program Files\SABnzbd\win\7zip\7za.exe)

[sander]

If you're sure it's not Windows Defender ... disable Windows Defender and try again.

[DutchG]

If you're sure it's not Windows Defender ... disable Windows Defender and try again.

I've tried and it does not make any difference.

[sander]

So: you disabled the virusscanner, re-run the install, tried again, and still the problem?

If not: do that
If so: there are two possibilities:

1) Keep your system updated, and try again each few weeks, until your virusscanner trusts all files in SABnzbd

2) go into the rabbit hole known as Windows & Virusscanners:
- open PowerShell
- execute like below and check the .exe files are there

Code: Select all

PS C:\> Get-ChildItem "C:\program files\sabnzbd\win\" -Recurse -Filter *.exe


    Directory: C:\program files\sabnzbd\win\7zip


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         6/16/2024  12:27 PM         847360 7za.exe


    Directory: C:\program files\sabnzbd\win\multipar


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         6/16/2024  12:27 PM         418304 par2j64.exe


    Directory: C:\program files\sabnzbd\win\par2\x64


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         6/16/2024  12:27 PM        1462272 par2.exe


    Directory: C:\program files\sabnzbd\win\unrar\x64


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         6/16/2024  12:27 PM         506008 UnRAR.exe


PS C:\>

[nowayz]

I had the same problem. It has to do with the fact that the binaries for unrar, par2, and par2j are in the wrong folders now.
Go to C:\Program Files\SABnzbd\win and move the executables out of the x64 folder and into their root folder. Also rename par2j64.exe to par2j.exe. I figured this out using ProcMon and figured out what path it was trying to load the 'missing' applications from

There's definitely something wrong with this latest release on windows. I am using Surface Pro 11 with ARM CPU though, so I don't want to be too hasty and assume this is happening for everybody.

[sander]

> I am using Surface Pro 11 with ARM CPU though,

Ah, Windows on ARM! There is patched version of SABnzbd for Windows on ARM. Thus solved in next version. Or you can test now, with the github binary, for which you need a github account

See https://forums.sabnzbd.org/viewtopic.php?t=26668 for a looooong thread

[DutchG]

I guess that's my problem too as I'm running an ARM version of Windows 11 on my M1 Macbook through parallels. I'll read that topic with great interest.

[sander]

I guess that's my problem too as I'm running an ARM version of Windows 11 on my M1 Macbook through parallels. I'll read that topic with great interest.

Yes! Did you install the github version, which solves the problem for SABnzbd on Windows on ARM?

[DutchG]

Yes! Did you install the github version, which solves the problem for SABnzbd on Windows on ARM?

I was planning to wait for the official release of the next version of sab if that's okay. Then I'll report back here

Thanks for all your efforts though!

[sander]

https://sabnzbd.org/downloads now has SABnzbd 4.3.3 Beta 1

Bug fix: Windows: Could not repair or extract on ARM platforms.

[DutchG]

https://sabnzbd.org/downloads now has SABnzbd 4.3.3 Beta 1

Bug fix: Windows: Could not repair or extract on ARM platforms.

Installed that version and no errors this time

[Jagdente]

repairing does not work anymore on my Xeon E5450 aka C2Q Q9650 since 4.3.0 (Win11 22H2)

4.3.3. beta2 does not fix it either