On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019

[Dave-H]

Thanks, that's better.
I was now prompted to switch to Microsoft Update, but when i did it said the necessary files weren't registered and offered to do it for me.

If I click continue, the window goes blank but nothing then appears to happen.

[maile3241]

5 minutes ago, Dave-H said:

Thanks, that's better.
I was now prompted to switch to Microsoft Update, but when i did it said the necessary files weren't registered and offered to do it for me.

If I click continue, the window goes blank but nothing then appears to happen.

Register muweb.dll again with regsvr32 then reload the page.

[Dave-H]

I tried that, and registering wuaueng.dll.
No difference.

[maile3241]

3 minutes ago, Dave-H said:

I tried that, and registering wuaueng.dll.
No difference.

Substitute www at returnurl instead of fe2.

[Dave-H]

It just immediately redirects to the fe2 address.

[maile3241]

3 minutes ago, Dave-H said:

It just immediately redirects to the fe2 address.

Try Windows Update: http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?ln=en

[AstroSkipper]

1 hour ago, maile3241 said:

Delete the sites and add the 3 back

@Dave-H I agree to @maile3241. Only the three mentioned sites may be listed in your Trusted Zone. Otherwise http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en will be blocked.

"Trusted Zone to high with only these three urls related to MU: http://www.update.microsoft.com, https://www.update.microsoft.com and http://update.microsoft.com. Disable in IE settings "Check for server certificate revocation"."

And once again your problem is most likely caused by a not properly working Windows Update Agent. I will post a more detailed procedure published by Microsoft later.

Edited January 27, 2022 by AstroSkipper
correction

[Dave-H]

17 minutes ago, maile3241 said:

Try Windows Update: http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?ln=en

Windows Update looks more promising.

Scanning immediately produces the same error though.

 

[maile3241]

5 minutes ago, Dave-H said:

Windows Update looks more promising.

Scanning immediately produces the same error though.

 

Run Restore_WU_XP_2003 again.

[AstroSkipper]

3 minutes ago, Dave-H said:

Windows Update looks more promising

I agree. You are on the right way. 

[Dave-H]

OK, I ran the cmd file again, and got this.

Presumably this is because the cmd didn't stop the Automatic Updates service.
I assume the file manipulation should happen on reboot.

It has made a difference, on reboot, trying Windows Update again gave this again!

[maile3241]

8 minutes ago, Dave-H said:

OK, I ran the cmd file again, and got this.

Presumably this is because the cmd didn't stop the Automatic Updates service.
I assume the file manipulation should happen on reboot.

It has made a difference, on reboot, trying Windows Update again gave this again!

Try restoring the default values. Then activate Tls 1.2 again.

[Dave-H]

Actually I've just noticed something.
My WU7.6 installation file, which I've had for ages, is 6.47MB.
Just in case I looked for another download of it, and the one I've got now is 9.27MB.
I'm now wondering if I've got an out of date version.
The file version information is no help at all of course, but my archived file says it's 6.2.29.0, the one I've just downloaded says it's 6.3.21.0.

[AstroSkipper]

32 minutes ago, Dave-H said:

The file version information is no help at all of course, but my archived file says it's 6.2.29.0, the one I've just downloaded says it's 6.3.21.0.

Of course the Windows Update Agent with file version 6.3.21.0 has to be installed. This is the version I have. Install it with command option: WindowsUpdateAgent-7.6-x86 /WUforce.

Then install Restore_WU_XP_2003 again. No reboot at this time.

Then do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary but injecting wuaueng.dll in any case. Then reboot your computer. Try MU again.

P.S. No more further editing. I swear! 

 

Edited January 27, 2022 by AstroSkipper
correction

[Dave-H]

OK, I did that.
Absolutely no difference I'm afraid, same error message.

I guess maybe I should do the whole process again now I have the right version of WU 7.6!