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

[ItCoder]

Check into C:\winnt\softwaredistribution\wuredir if there is one file that contains fe2.update.microsoft.com

[Great_Life]

4 minutes ago, ItCoder said:

Check into C:\winnt\softwaredistribution\wuredir if there is one file that contains fe2.update.microsoft.com

I can't find that. Here is a picture about the folder.

[ItCoder]

Look into the folders

[Great_Life]

Just now, ItCoder said:

Look into the folders

[ItCoder]

Check if you have Windows Update Agent 7.6.7600.256, and the patched wuaueng.dll (it's not signed by Microsoft). Check also if you have the WuRedirOverride keys. Once everything is done and you start a scan, you should have a v6-win7sp1-wuredir.cab in one of those folders

[Great_Life]

7 hours ago, ItCoder said:

Check if you have Windows Update Agent 7.6.7600.256, and the patched wuaueng.dll (it's not signed by Microsoft). Check also if you have the WuRedirOverride keys. Once everything is done and you start a scan, you should have a v6-win7sp1-wuredir.cab in one of those folders

I found that everytime I tried to search the updates,the wuaueng.dll always restored into its own old verison.How can I stop this?

PS:The MU site's buttons suddenly stop working,too.Maybe they have some thing in common.

[ItCoder]

You should replace wuaueng.dll in system32 and in system32\dllcache, otherwise it gets restored. But the website should open anyway, only the scan should fail. Where does it exactly stop loading?

[Great_Life]

2 hours ago, ItCoder said:

You should replace wuaueng.dll in system32 and in system32\dllcache, otherwise it gets restored. But the website should open anyway, only the scan should fail. Where does it exactly stop loading?

Now I have re-installed Windows completely and followed all the steps again,it finally works!As you can see,it started to update itself! Hope no more errors will appear.

Edited July 10, 2023 by Great_Life

[WSC4]

On 3/5/2022 at 6:12 AM, maile3241 said:

Windows Update for Xp x64 edition and W2k3

I found a new opportunity. Cr to @whenever by Tuopf https://www.prxbx.com/forums/showthread.php?tid=2172. This version of ProxhttpsProxy creates a Sha1 certificate and is compatible with most Windows versions. With this version of ProxhttpsProxy, it is possible to update Windows Server 2003 (not tested) and Win Xp x64 edition. IE6 is sufficient.

download link: https://www.mediafire.com/file/ftq6dnsccuq54p4/ProxHTTPSProxyMII_1.3a.zip/file

WU-patch: http://www.mediafire.com/file/1ontv0vkh0ghfbi/Restore_WU_XP_2003.7z/file

I have already edited the Config.ini so that you can work directly with ProxhttpsProxy. When opening ProxhttpsProxy a new certificate is generated. This certificate must be stored in the local computer's trusted certificate store.

Make sure TLS 1.0 and Http 1.1 is enabled via proxy and the Windows Update patch is installed! It works without additional updates!

It is also suitable if the CPU does not support SSE2.

@AstroSkipper What do you say? Is it a good option?

I am running Windows XP 64-bit, and I have studied your post that you posted over a year ago.  I have downloaded the file and installed it and the WU Patch and have done everything that you said to do.  This is what I get when running Windows Update:

Are these setting correct?  Any help on this please?

[ItCoder]

You should click on Advanced on the last screen and put the IP address only into "Secure", leaving the other ones blank. The Proxy works only with HTTPS.

[WSC4]

14 hours ago, ItCoder said:

You should click on Advanced on the last screen and put the IP address only into "Secure", leaving the other ones blank. The Proxy works only with HTTPS.

Thank you and that worked.  I now get this:

The ProxHTTPSProxyMII screen is now showing this and looks a lot better:

Launching Windows Update:

I thought I was 100% there and spoke too soon.  Unfortunately, when I click either the Express or Custom button, This happens:

Any help on Error number 0x800706B5 please?

[ItCoder]

This is a system error. Try running sfc /scannow and reinstalling Windows Update Agent. Tell me also if ProxHTTPSProxy shows a call to fe2.update.microsoft.com/v6/ClientWebService/client.asmx

[AstroSkipper]

6 hours ago, WSC4 said:

Any help on Error number 0x800706B5 please?

FYI, the error code 0x800706B5 means RPC_S_Unknown_IF with the description:

Quote

Eventlog service is not running. BITS tries to initialize the event logger object during initialization and fails to start, if the initialization fails. If event log service is not running, then the initialization fails with RPC_S_UNKNOWN_IF error

Check if there are problems in your system with the event log service!

[WSC4]

Thank for all your help on this.  I did run his Install.cmd again to update the Windows Update Agent.  I may not have noticed what it said the first time, but I have noted this:

Installing KB2868626 to enable SHA-256 support
Adding registry entries

Updating Root Certificates

Installing latest Windows Update Agent

Replacing wuaueng.dll with patched file
Could Not Find C:\WINDOWS\System32\Dllcache\wuaueng.dll
A duplicate file name exists, or the file
cannot be found.
The process cannot access the file because it is being used by another process.

I'll try install.cmd again in safe mode.  I did check for problems in the event log service with ProxHTTPSProxy running and no errors showed up.

[AstroSkipper]

42 minutes ago, WSC4 said:

Thank for all your help on this.  I did run his Install.cmd again to update the Windows Update Agent.  I may not have noticed what it said the first time, but I have noted this:

Installing KB2868626 to enable SHA-256 support
Adding registry entries

Updating Root Certificates

Installing latest Windows Update Agent

Replacing wuaueng.dll with patched file
Could Not Find C:\WINDOWS\System32\Dllcache\wuaueng.dll
A duplicate file name exists, or the file
cannot be found.
The process cannot access the file because it is being used by another process.

I'll try install.cmd again in safe mode.  I did check for problems in the event log service with ProxHTTPSProxy running and no errors showed up.

TBH, I did all the steps of my guide manually. The verification of each step is much easier doing it this way. And keep an eye on SFC! I switched it off in my system, forever.