Although the MS Update webpage opens for me again now, it's still not working.
It scans for a few seconds, and then fails with error 0x80244019.
WUMT still isn't working either for me, still just shows error 0x80244004.
MBSA also still fails to download the scanning database every time I try a scan, with the ESENT error 623 in the Windows Application Event log.
So as far as I'm concerned, still nothing is working!

Was working a few hours ago.

Now they killed it for sure:

WARNING: SyncUpdates failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404

Database was deleted. RIP.

Edited August 6, 20206 yr by daniel_k

4 hours ago, Dave-H said:

Although the MS Update webpage opens for me again now, it's still not working.
It scans for a few seconds, and then fails with error 0x80244019.

MS/W Update is also broken on Windows Vista SP2 (with or without SHA-2 code-signing support):

I think this time it's for good...

EDIT: @daniel_k just beat me to it...

3 hours ago, daniel_k said:

Database was deleted. RIP.

Edited August 7, 20206 yr by VistaLover

Well we had it for over a year longer than we thought we were going to.
Had to end sometime.
I guess it will have to be manual updates from the catalogue for the last few months of Office 2010 updates.

Well it's a good thing I scraped the download links of installed updates for a fully updated XP SP3 (with selectall + selected by windows update; I assume the latter option was to satisfy WU). It seems to be redundant considering we have update packs from ryanvm but still.

One thing that I add is that checking by been-alive MU resulted into more results of updates installed shown compared to WSUSSCN2.cab file.

https://anonfiles.com/l7TaX6Kco7/WinXPscrappedDLupdatesmicrosoft_zip

scraped download links of installed updates that were detected by Microsoft Update, scrapped by WUMT (might release an another zipfile with the installed ones that were detected by the offline wsusscn2.cab that i mentioned was less). The selected by WU txt (used the namesake option) seems to be the ones that were to satisfy windows update while the all selected txt is all of the updates installed. the pending.txt is the silverlight/mse/windows live stuff. they're nastily ordered cause the WUMT sorting weirdly functioned.

pass is the name of site where you're currently on (with the tld on; all lowercase)

I suggest to do the same thing for Win2K and vista if it's fully updated (let's assume for vista to the point of official EOL, but is that necessary though, considering daniel_k's scrapped the links already?)

Anyway best to save the links to wayback machine/web archive just in case.

Edited August 7, 20206 yr by IntMD

Thanks for that!

I just tried using WUMT in offline mode with the newly downloaded wsusscn2.cab.
I'm just getting an error message "An error has occurred: 0x800B0100 No signature was present in the subject".
Is that the SHA signing problem, and is that version of wsusscn2.cab actually useless in XP?

46 minutes ago, Dave-H said:

I just tried using WUMT in offline mode with the newly downloaded wsusscn2.cab.
I'm just getting an error message "An error has occurred: 0x800B0100 No signature was present in the subject".
Is that the SHA signing problem, and is that version of wsusscn2.cab actually useless in XP?

For me MS simply blocks user access to Windows Update with SHA-1. This is the reason because v6 loads but don't search updates.

Also I don't have a sure reason, I don't know why v6 is still active if NT 5.X systems don't supports SHA-2.

Edited August 7, 20206 yr by WinFX

37 minutes ago, Dave-H said:

I just tried using WUMT in offline mode with the newly downloaded wsusscn2.cab.
I'm just getting an error message "An error has occurred: 0x800B0100 No signature was present in the subject".
Is that the SHA signing problem, and is that version of wsusscn2.cab actually useless in XP?

make sure the cabinet is modified 14 july 2020 and has this SHA1 hash: 5fcdbed0e904f233ccc6de6fe3abac713dac706f

My wsusscn2.cab file is dated the 5th August, which is when i downloaded it.
The SHA1 checksum is correct though.

Still gives the same error in WUMT.

26 minutes ago, Dave-H said:

My wsusscn2.cab file is dated the 5th August, which is when i downloaded it.
The SHA1 checksum is correct though.

Still gives the same error in WUMT.

Where did you get WUMT from? MDL?

I honestly can't remember where it came from, I've had it for a long time.
Although the version is now quite a few years old, I think it is still the latest version, it hasn't been updated for ages.

On 8/7/2020 at 11:55 AM, IntMD said:

Where did you get WUMT from? MDL?

Looks like MajorGeeks and Softpedia are the top search results. Edit: But see this post for the recommended version.

Edited September 6, 20205 yr by Vistapocalypse
bad information

Just checked the WindowsUpdate.log on Vista, XP and Win7, the block is in the remote WU servers.
On supported OSes, this url is used to check for updates:
https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx

On unsupported OSes, this url is used to check for updates:
http://www.update.microsoft.com/v6/ClientWebService/client.asmx
But it was deleted.

If we could redirect it to the link above, maybe it would still work.
Any ideas?