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

[Mcinwwl]

Hey folks, I've been out of discussion recently, but I'm back and I've updated myself with recent news in this topic. I have two questions where the answer is most likely "no", but why shouldn't I ask to make sure?

1. Has anyone laid his hands on post-POSREady out-of-support XP updates?

2. Is there any reliable and working way to connect winXP to windows update again?

[XPerceniol]

On 4/30/2021 at 11:40 AM, XPerceniol said:

Yes, Dave, I was expecting a page to come up with all the updates available as it used to be in IE (I realized this morning I have activeX disabled anyway lol). I'm able to search and download updates with no issues.

However, as I share your instinct(s) - I'll leave well enough alone so long as this old Ford Pinto starts up and still shifts into "drive".

That being said.. I bookmarked the "Portable Update" tool in case the need be to give life support to this beast

Cheers

EDIT:

Ok I found it - sorry for my ignorance I downloaded the tool and enabled the services (I thought) were/are required and the log is as shows after running it 5 times.

30/04/2021 11:51:29 AM    1272    Main error: The remote server machine does not exist or is unavailable - PortUp
30/04/2021 11:51:38 AM    532    Main error: The remote server machine does not exist or is unavailable - PortUp
30/04/2021 11:51:49 AM    380    Main error: The remote server machine does not exist or is unavailable - PortUp
30/04/2021 11:52:17 AM    1620    Main error: The remote server machine does not exist or is unavailable - PortUp
30/04/2021 11:53:17 AM    912    Main error: The remote server machine does not exist or is unavailable - PortUp

Below was from the first link on that page on our forum. I'll have to put on my 'thinking cap' for this one I seems. I found a good deal online for a 'thinking cap' as I have a coupon somewhere in my dresser drawer still ... hopefully anyway 

FINAL EDIT: (I promise - I guess I'm not as dumb as I look)

Turns out: I had to (also) enable (as I usually have it disabled) DCOM Server Process Launcher - and boomshakalaa - 6 updates available.

Hello, I was able to get the portable updater to grab updates last April.

This thread was also helpful.

https://msfn.org/board/topic/182664-microsoft-expiring-sha-1-updates-will-this-kill-xp/page/6/#comment-1199409

 

Edited December 8, 2021 by XPerceniol

[XPerceniol]

28 minutes ago, Mcinwwl said:

Hey folks, I've been out of discussion recently, but I'm back and I've updated myself with recent news in this topic. I have two questions where the answer is most likely "no", but why shouldn't I ask to make sure?

1. Has anyone laid his hands on post-POSREady out-of-support XP updates?

2. Is there any reliable and working way to connect winXP to windows update again?

Good luck!

[DosFreak]

To download Windows Updates for 2000 to Vista:

1. Use your own WSUS server (Win 2022 WSUS goes all the way back to Windows 2000) and point XP to it

or

2. Go here https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/ and follow the instructions in the readme for WSUS proxy.
The proxy works fine on XP itself so no need to run it on another machine unless you want to update Windows 2000 then you'll need to run the proxy on XP+ and run the minitool on 2000.
Verified all this last week on both 2000, XP 32bit and 64bit and Vista 32bit and 64bit (for Vista I used the Windows Update client fix for Vista 6003 instead)
https://forums.mydigitallife.net/threads/restore-windows-update-for-windows-xp-server-2003.82538/

For POS just add the registry key but beware if the CPU doesn't support SSE2.



 

Edited December 8, 2021 by DosFreak

[maile3241]

Hello everyone and a happy new year 2022!

This is my first post.

Sorry, I have to translate from German to English.

Since July 2021 I have been working on the update problem in Xp. As many people may know, the page has not been accessible for about 1 year. I found a workaround solution. To do this, click Internet Options in Internet Explorer, then go to the Trusted Sites option in the Security tab, then click Sites and add the pages http://www.update.microsoft.com and https://www.update.microsoft.com . Then set the security level to high and call up Windows Update. The page is already reloading. Unfortunately you get the error code 0x80072eff. The problem is that Internet Explorer is trying to download a file in the https protocol. After adding Tls 1.2 I still got the same error code. A few months have now passed. Until I got the idea that it could also be due to the certificate. I then downloaded a certificate trust list from Microsoft (https://docs.microsoft.com/de-de/security/trusted-root/release-notes). After I installed this certificate trust list, with a lot of luck and patience I was able to access the page. But unfortunately the search for updates failed. But after I downloaded the sha-2 patch from @max-h, I was actually able to search for and install updates again. The strange thing is that shortly after loading the page you have to click on Quick Search or Custom Search immediately, otherwise the search will fail with 0x80072efe. What is also strange is that I cannot open the page in a second window, otherwise the error 0x80072eff pops up again. What's also strange, when this page is open, the links in the Help and Support Center work too. Unfortunately, strangely enough, I am currently unable to access this website at all. But I am sure that the problem is with the certificate.

Sorry, the pictures are only in German.

Maybe someone can help.

Edited April 1, 2022 by maile3241

[maile3241]

Edited February 1, 2022 by maile3241

[maile3241]

Edited February 1, 2022 by maile3241

[maile3241]

And here you can see the error that occurs when calling the page.

Edited February 1, 2022 by maile3241

[xpandvistafan]

20 hours ago, maile3241 said:

Hello everyone and a happy new year 2022!

Sorry, I have to translate from German to English.

Since July 2021 I have been working on the update problem in Xp. As many people may know, the page has not been accessible for about 1 year. I found a workaround solution. To do this, click Internet Options in Internet Explorer, then go to the Trusted Sites option in the Security tab, then click Sites and add the pages http://www.update.microsoft.com and https://www.update.microsoft.com . Then set the controller to and call up Windows Update. The page is already reloading. Unfortunately you get the error code 0x80072eff. The problem is that Internet Explorer is trying to download a file in the https protocol. After adding Tls 1.2 I still got the same error code. A few months have now passed. Until I got the idea that it could also be due to the certificate. I then downloaded a certificate trust list from Microsoft (https://docs.microsoft.com/de-de/security/trusted-root/release-notes). After I installed this certificate trust list, with a lot of luck and patience I was able to access the page. But unfortunately the search for updates failed. But after I downloaded the sha-2 patch from @max-h, I was actually able to search for and install updates again. The strange thing is that shortly after loading the page you have to click on Quick Search or Custom Search immediately, otherwise the search will fail with 0x80072efe. What is also strange is that I cannot open the page in a second window, otherwise the error 0x80072eff pops up again. What's also strange, when this page is open, the links in the Help and Support Center work too. Unfortunately, strangely enough, I am currently unable to access this website at all. But I am sure that the problem is with the certificate.

Sorry, the pictures are only in German.

Maybe someone can deal with it.

So what you are saying is that it does not do infinite redirect between update.microsoft.com and fe2.update.microsoft.com?

[maile3241]

2 hours ago, xpandvistafan said:

So what you are saying is that it does not do infinite redirect between update.microsoft.com and fe2.update.microsoft.com?

I fixed this infinite loop as described above. The forwarding stops and the page loads. Unfortunately, for now you get the error 0x80072eff because I think something is wrong with the Microsoft Root Certificate Authority 2011. But I can't say for sure. This is currently just a guess. But there could also be something wrong with Internet Explorer. What is strange is that the page https://fe2.update.microsoft.com cannot be called up and the page https://fe2.ws.microsoft.com can.  Maybe the problem could be solved with the ProxHttpsProxy software. Unfortunately I don't have access to the download.

 

Edited January 11, 2022 by maile3241

[xpandvistafan]

55 minutes ago, maile3241 said:

Unfortunately, it is. If you apply these settings as I have described, the forwarding stops and the page loads. Unfortunately, for now you get the error 0x80072eff because I think something is wrong with the Microsoft Root Certificate Authority 2011. But I can't say for sure. This is currently just a guess. But there could also be something wrong with Internet Explorer. What is strange is that the page https://fe2.update.microsoft.com cannot be called up and the page https://fe2.ws.microsoft.com can. 

 

Well, I got that error to go away last May by installing all PosReady Updates as well as TLS 1.2. I think the Root Certificate Authority 2011 is SHA-1, and it expired last May. What is interesting though is you got it to work after that.

[maile3241]

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

Nun, ich habe diesen Fehler letzten Mai verschwinden lassen, indem ich alle PosReady-Updates sowie TLS 1.2 installiert habe. Ich denke, die Root-Zertifizierungsstelle 2011 ist SHA-1 und sie ist letzten Mai abgelaufen. Interessant ist jedoch, dass Sie es danach zum Laufen gebracht haben.

Note the following settings: 

Edited February 1, 2022 by maile3241

[maile3241]

13 hours ago, xpandvistafan said:

Nun, ich habe diesen Fehler letzten Mai verschwinden lassen, indem ich alle PosReady-Updates sowie TLS 1.2 installiert habe. Ich denke, die Root-Zertifizierungsstelle 2011 ist SHA-1 und sie ist letzten Mai abgelaufen. Interessant ist jedoch, dass Sie es danach zum Laufen gebracht haben.

No, the Microsoft Root Certificate Authority 2011 is the current sha-2 certificate. What you mean is the Microsoft Root Certificate Authority which expired on May 10th, 2021. Since then there has been a redirect to fe2.update.microsoft.com

[xpandvistafan]

6 hours ago, maile3241 said:

No, the Microsoft Root Certificate Authority 2011 is the current sha-2 certificate. What you mean is the Microsoft Root Certificate Authority which expired on May 10th, 2021. Since then there has been a redirect to fe2.update.microsoft.com

Sorry, my mistake. Yes, it did stop working around that time, I believe April 28, when Microsoft switched update.microsoft.com to an SHA-2 certificate. What SSL and TLS settings do you have?

[maile3241]

17 hours ago, xpandvistafan said:

Sorry, my mistake. Yes, it did stop working around that time, I believe April 28, when Microsoft switched update.microsoft.com to an SHA-2 certificate. What SSL and TLS settings do you have?

I have SSL 3.0, Tls 1.0 and 1.2 enabled by default. But it doesn't fix the redirect!