max-h

These are the links of the official thread : http://www.mediafire.com/file/1ontv0vkh0ghfbi https://anonfiles.com/P024Sfh0p6 https://download.ru/files/DMFZOv3t

Indeed... Here is a backup : http://dl.free.fr/fN2aPTeTs

/!\ Doesn't work anymore, use the proxy method : Guys, I have good news : A solution has been found to make XP and server 2003 compatible with SHA-2 updates! Special thanks to daniel_k and abbodi1406 on Mydigitalife for the work :https://forums.mydigitallife.net/threads/windows-update-for-2000-xp-2003-and-vista-is-die-august-2020.82143/page-5 Some registry hacks and patched wuaugen.dll and voilà! A 7zip file contains all necessary files : http://www.mediafire.com/file/1ontv0vkh0ghfbi https://anonfiles.com/P024Sfh0p6 https://download.ru/files/DMFZOv3t

For quick update you can also use KUC update checker : http://windows-update-checker.com/ On 7 for example, only about 40 updates are needed to be up to date (if we use the convenience rollup and ignore those for satisfy WU) Very helpful.

All security and cumulative updates released after January 14, 2020 require an ESU key to install on a classic Windows 7. Except the Licensing Preparation Package and SSUs.

This will not work, the system verifying that there is a valid ESU key, as well as other prerequisites :

Virtual machine or not, I don't see what that changes... the system is the same. And if this is the story of guest additions, on a real hardware it would also need drivers. You can test on real hardware if you want, but I think you will get the same error, I don't have any on hand unfortunately.

Windows 7 still get updates via ESU program which is paid, not free.

I confirm...

The installation is blank (from retail CD). On Pro there is no need to add something. And even after apply MSI 4.5, error is still there.

I noticed a weird bug on XP home. Agent version .320 doesn't install. It only works on Pro version.

This is why a blank Windows 7 started to find updates again. I didn't understand why. Here is the answer. And I confirm that it works also on XP EDIT : Windows 2000 is ok too

@abbodi1406 Thanks for the tip!

Microsoft cut a few days (or hours) ago I don't know precisely, the self-update of windows update agent. This means that WUMT will display "class not registered" until we manually update the agent. It's really the end this time. Fortunately, I found version 7.4.7600.226 as standalone package : https://support.microsoft.com/en-us/help/946928/information-for-network-administrators-about-how-to-obtain-the-latest As indicated, there is no standalone package for version 7.6.7600.256 but 7.4 works well.

@Usher : I know, the signature tab is missing. Little question of license/Service pack : I wanted to test French XP ISO with SP2 to see if I still had the 800b0003 error. So I went in search of an SP2 iso. I finally found the home edition N. The installation is going well and when I (normally) have the OOBE, I will land to the welcome page with the famous message telling me to activate windows, as if the 30 days had passed. What I don't understand is that I also have an SP3 home ISO and I have no problem, I have the normal activation delay. Could be a particularity of SP2? Because it seems to me that I already had this problem on an old PC, I had bought a so-called "new" SP2 home CD and I had the same message... as if it had already been activated. Or it's because the servers are unreachable? And before you ask : ISO is genuine. EDIT : I found the problem : just after network configuration, the system makes a request to download the certificate of revoked keys : Bad news : I downloaded French XP Pro SP1 iso and trying July 2020 version : it's works. BUT if i install the SP2 the error reappears... and same with SP3 of course. So there would be a problem somewhere with the files from SP2 and SP3? The most frustrating thing is that I kept testing other languages and all of them worked. I have not tested languages other than Latin because it is not understandable.

Even on windows 2000 it works... I'm desperate...

I don't think so. On english version, it works as you can see :

Pretty weird. When I pass the file into the File Signature Verification utility, it cannot find it. But if I take the sigcheck utility, it's okay. However, it says that sigcheck: "Calculate the hash of the file, find it in the appropriate security catalog file, and verify the signature of the security catalog file." This means that it compares well with the certificates present on the machine and does not only show whether there is just a signature or not. The question is: why does sigcheck find the signature but windows not?

Maybe a clean install could help?

Exactly. I tested with EN-GB configuration : it works. Unless I'm mistaken, there is no specific iso for en-gb. It's only the setting that changes in regional and languages option, right?

The sha1 of dec 2019 wsusscn2.cab is good. For my part I tested ES, IT, PT-PT and NL with that of July. Everything works.

You're right. I tested the German version after that and it worked too... What wrong with the French Version?

Very very strange. To make sure, I tested with the US version of XP and guess what? It works with the July 2020 cab! So there would be a problem with all XP versions other than US?

Same error here. I have tried updating the root certificates and it looks like there is a report because without it I get error 800B0003 "the form specified for the subject is not supported or known by the specified trust provider" and after 800B0100 like you and Dave. In my case I downloaded archive.org version from December 2019 and it worked : https://web.archive.org/web/20191209214827/http://download.windowsupdate.com/microsoftupdate/v6/wsusscan/wsusscn2.cab For Wsusoffilne, wsusscn2.cab is in client/wsus but when the process is launch it's erase the file, so... unusable.

It's impossible to install WSUS on Vista unfortunately (to my knowledge, you can just install the console to control the server)... Is your WSUS installation on a virtual machine? It's more flexible than a physical machine and you can backup and move easily. For me, on the contrary, WSUS has almost only advantages: -Update as many machines as you want, without copying the updates - WU does everything automatically and without consuming a lot of disk space (I have a problem doing it manually, precisely on vista, the disk fills up quite quickly, I have to plan at least 60 GB to install ~ 200 updates I think it's coming extracted .cabs that are not deleted over time after being installed. I have not tested with .msu, because you have to recover everything manually, and the pkgmgr tool does not support msu for an installation of several packages at the same time, it only works from windows 7.