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

[legacyfan]

On 2/19/2023 at 9:20 AM, ItCoder said:

I've put online my proxy server: to use it add as "Secure" proxy 34.205.92.217:8079, import the CA.crt and install Windows Update Agent (remember to run "proxycfg -u" or "netsh winhttp import proxy source=ie" to make AU work as well).

Here is the link to the installers (run it on a fresh installation and it should work): https://1drv.ms/u/s!AsVjtW11rJfA3FQANrgg_QXRMgfx?e=7q2PhN

Great job @ItCoder! this should definitely be of good use to everyone on older windows 

 

 

[WULover]

@EZuser managed to get Windows Update to work on Windows 11.

[ItCoder]

Now installers for NT5.x work! Download from https://1drv.ms/u/s!AsVjtW11rJfA3FQANrgg_QXRMgfx?e=lCF2lV, run it on your system and everything will work!

Installers for NT6.x currently do not work. I'm testing them.

[ItCoder]

Now my installers works for any OS from 2000 to 7 SP1. Download your from https://1drv.ms/u/s!AsVjtW11rJfA3FQANrgg_QXRMgfx?e=lCF2lV and run it (follow eventual prompts). It restores WU, MU and AU (including website on Vista and 7).

Notes:
1)On Windows 2000, you need SP3 or SP4 and IE6 installed before you run this
2)On Windows XP RTM, SP1, SP2 AU doesn't work if MU is enabled (unsolvable)
3)On Windows Vista and 7 already used installations run the fix before installing
4)On Windows 7 SP1 error 0x8007000A is related to wuaueng.dll and cannot be solved. If you have it, install SHA-2 support
5)The installer can be run multiple times if you need

[luweitest]

Could windows update still accessible using a HTTPS proxy? I tried HTTPSProxy and ProxHTTPSProxy but both failed. I use the config.ini from which claimed successful.

First,  in the IE proxy setting,  the proxy for http has to be empty, or the error occurs when opening http://windowsupdate.microsoft.com/:

400: Bad Request

The following error occurred while trying to access http://windowsupdate.microsoft.com/

The proxy setting of the client is misconfigured. Please set the HTTPS proxy port to 8079 and check the Docs for other settings.

---

This is minor since we don't intend to use HTTPSProxy and ProxHTTPSProxy for http sites.

Second, when http proxy is empty and https proxy is set to 127.0.0.1:8079, http://windowsupdate.microsoft.com/ will pass and the address bar begin to switch between http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?ln=zh-cn  and  http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx endlessly, the page never shows up.

It seems a bug in the HTTPSProxy and ProxHTTPSProxy dropping the part "?ln=zh-cn" . Maybe this method only works for English version? But I doubt English version will have a part "ln=en-US".

ps. I can visit other pages like https://www.ssllabs.com correctly.

 

Edited April 13, 2023 by luweitest

[ItCoder]

You have to add ?g_sconsumersite=1 after aspx to open the website. But scanning won't work unless you apply redirects (patching wuaueng and registry or using another proxy). If you run my installer (any Windows) or the one in the 1st post (XP only) you'll have everything working

[luweitest]

On 4/13/2023 at 7:32 PM, ItCoder said:

You have to add ?g_sconsumersite=1 after aspx to open the website. But scanning won't work unless you apply redirects (patching wuaueng and registry or using another proxy). If you run my installer (any Windows) or the one in the 1st post (XP only) you'll have everything working

Patched wuaueng.dll, imported HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Test registry, Visit http://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?g_sconsumersite=1, Now it comes to service not running 0x8DDD0018 error, but all 3 required services are running.

[ItCoder]

Check if you have the correct agent version (version of wuweb.dll in system32 must be 7.x.7600.xxx). Check also if you have HTTP/1.1 over proxy and TLS1.0 enabled. If that's all ok, check the latest lines of windowsupdate.log. You can try to load the https version of Windows Update and see in ProxHTTPSProxy if wuredir.cab, wuident.cab and wsus3setup.cab (XP SP3 only) get downloaded to know where the error happens.

[WULover]

What are you exactly trying to do? If you want to restore Windows Update v6/Microsoft Update v6, there's a simple method:

Run the install.cmd in Restore_WU_XP or Restore_WU_XP_2003.

Click cancel at the prompt.

Install and run ProxHTTPSProxyMll v1.3a.

Install the certificate (CA.crt) on the client Windows XP machine.

Run the proxy, and go to the Windows Update website in the Windows XP machine, and there you go.

[luweitest]

Thanks ItCoder!    Problem solved. It is the wrong wuaueng.dll I use, and it did take some time for the IE window to respond...

What's the advantage to use 7.4 version? I find 7.6 version patched wuaueng.dll works OK.

And I wonder how the key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Test" was found? It seems not documented anywhere, and the filename "v6-win7sp1-wuredir.cab" suggests no relation with windows XP.

ps.  ProxHTTPSProxyMII 1.5 version works.

Edited April 17, 2023 by luweitest

[ItCoder]

7.4 is the same as 7.6 with AllowAnySSL key. It's only that I didn't want to use a patched version. The wuredir key forces Windows Update to download the correct wuredir.cab (XP's one has the old www.update.microsoft.com which doesn't work) but this method breaks Automatic Updates and doesn't work in Vista (error related to wuident.cab SHA-2-only signature). That's why I prefer setting the correct URLs in the proxy

[ItCoder]

I created a GUI installer for my method using Legacy Update's one as a base. You can download it and view sources at the same link (https://1drv.ms/u/s!AsVjtW11rJfA3FQANrgg_QXRMgfx?e=7q2PhN).
I've tested it on any version from 2000 to 7 and it works. Tell me if something doesn't.

[legacyfan]

thanks @ItCoder this will be really usefully for updates

[legacyfan]

windows can finally be used again! like it originally was

[ED_Sln]

Maybe a little off-topic, but I'll ask here. Does anyone have the KB946448 update for Server 2003 x86 and x64 , or the older replacement KB943545? Or if there is a newer one that replaces these, please tell me which one.