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

[maile3241]

On 1/12/2022 at 1:33 PM, maile3241 said:

Note the following settings:

@xpandvistafan In order to stop the forwarding, this must be observed.

[xpandvistafan]

2 hours ago, maile3241 said:

@xpandvistafan In order to stop the forwarding, this must be observed.

Yes, I will try it on a real XP machine from 2003 soon. Perhaps you should inform a moderator @Dave-H about your finding. Even though updates through the page does not work at the moment, it is a big step forward, since nobody knew how to see the old website again. 

[maile3241]

8 minutes ago, xpandvistafan said:

Yes, I will try it on a real XP machine from 2003 soon. Perhaps you should inform a moderator @Dave-H about your finding. Even though updates through the page does not work at the moment, it is a big step forward, since nobody knew how to see the old website again. 

Okay, that makes me happy.  Now only the error 0x80072eff would have to be fixed. This is because Internet Explorer cannot access the page in https. Despite Tls 1.2. The problem can be seen in the Windows Update log file.

[xpandvistafan]

1 minute ago, maile3241 said:

Okay, that makes me happy.  Now only the error 0x80072eff would have to be fixed. This is because Internet Explorer cannot access the page in https. Despite Tls 1.2. The problem can be seen in the Windows Update log file.

Yes, that was always an issue, even before the website went down. update.microsoft.com started requiring more secure ciphers and TLS 1.2 in January 2021. Before that, you would get the error 80244019 since the update.microsoft.com page gave a 404. Back then, nobody knew how to redirect update.microsoft.com to fe2.update.microsoft.com. Do you have a log file of when it worked in December 2021? Perhaps something has changed since then. 

[maile3241]

22 minutes ago, xpandvistafan said:

Yes, that was always an issue, even before the website went down. update.microsoft.com started requiring more secure ciphers and TLS 1.2 in January 2021. Before that, you would get the error 80244019 since the update.microsoft.com page gave a 404. Back then, nobody knew how to redirect update.microsoft.com to fe2.update.microsoft.com. Do you have a log file of when it worked in December 2021? Perhaps something has changed since then. 

As far as I know nothing has changed. As I said, it was always a matter of luck. Theres a Picture: https://photos.app.goo.gl/WMtU1vTEHX33xPgM6

Edited January 13, 2022 by maile3241

[maile3241]

@xpandvistafan Also, I have the update page running in Windows 10 and it works without any issues.

 

Edited February 1, 2022 by maile3241

[xpandvistafan]

 

3 minutes ago, maile3241 said:

@xpandvistafan Also, I have the update page running in Windows 10 and it works without any issues.

. How did you get it to work in Windows 10? It would either redirect you or say you need to update your browser.

 

[maile3241]

On 1/13/2022 at 11:11 PM, xpandvistafan said:

 

. How did you get it to work in Windows 10? It would either redirect you or say you need to update your browser.

 

I have registered wuweb.dll (For Windows Update) and muweb.dll (For Microsoft Update) under c:/windows/syswow64 and added this page to Trusted Sites in Internet Options. And from Xp took the Windows Update Manager and copied it to Windows 10 on the desktop.

 

Edited February 1, 2022 by maile3241

[xpandvistafan]

On 1/12/2022 at 6:33 AM, maile3241 said:

Note the following settings:

Yes, it worked for me. I get 80072eff as you said. But mine is vanilla XP with only TLS 1.0.

Edited January 13, 2022 by xpandvistafan

[Dave-H]

FWIW I'm getting error 0x80072F7D, not 0x80072EFF.

[xpandvistafan]

1 hour ago, Dave-H said:

FWIW I'm getting error 0x80072F7D, not 0x80072EFF.

Can you send a screenshot? I assume that your system is PosReady fully upgraded. Apparently, he got it to work in December by luck, with max-h's SHA2 patch. I do not know about this patch though.

[Dave-H]

Here you go.

My system is fully POSReady updated and has TLS 1.2 enabled (I think!)

[maile3241]

1 minute ago, Dave-H said:

Here you go.

This can have many causes. Is the date correct? Are the Tls settings correct? Possibly do a root certificate update

[maile3241]

 

On 1/14/2022 at 2:08 AM, xpandvistafan said:

Can you send a screenshot? I assume that your system is PosReady fully upgraded. Apparently, he got it to work in December by luck, with max-h's SHA2 patch. I do not know about this patch though.

I correct: I got the page up and running with a CTL and with a lot of patience. The patch just replaced the old endpoint (https://www.update.microsoft.com/v6/clientwebservice/client.asmx) with the new one. (https://fe2.update.microsoft.com/v6/clientwebservice/client.asmx)

Download link from the CTL: https://aka.ms/CTLDownload

Edited February 23, 2022 by maile3241

[Dave-H]

Everything is as it should be.
I checked for root certificate updates only a couple of days ago.

The page doesn't tell you what the asterisks mean!