Jump to content

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

Mcinwwl

By Mcinwwl
in Windows XP

 Share

Recommended Posts


AstroSkipper

AstroSkipper

Posted
Posted

@Dave-H Once again I have reflected what additional steps I'd performed to solve MU related error codes. And the winner is: flushing the DNS cache which means clearing the DNS cache. Reasons for doing this: "It's important to flush a DNS cache for a few reasons. The first is the cache may contain outdated information. You might experience this as difficulty accessing websites or applications. If the domain name in the cache points to an old or incorrect IP address, the website won't return the correct information." quoted from https://www.google.de/url?sa=t&source=web&rct=j&url=https://www.dnsstuff.com/clear-flush-dns-server-cache-windows&ved=2ahUKEwjpz-K4utD1AhWO3KQKHdpBCWoQFnoECAUQBQ&usg=AOvVaw1UbhoAs53jSD5-BeNl42B4.

Command in cmd console: ipconfig /flushdns

Don't know if it can help in your case but I did it definitely.

1
Link to comment
Share on other sites
AstroSkipper

AstroSkipper

Posted
Posted (edited)
21 minutes ago, Dave-H said:

Well here's my equivalent.
I assume we're looking at the Current User certificates, not the Local Machine certificates, sorry I don't know any German.

Clipboard-1.thumb.png.1fed2d3bf128d775b83ceceff0dd22cb.png

Does anything look wrong there?

You're absolutely right. My screenshot belongs to current user. When you compare yours to mine there is one thing strange and this is your Microsoft Root Cerificate Authority 2011. You have twice and I don't know why.

If it were my system I would delete the one with "Friendly Name" <none>.

Edited by AstroSkipper
addition
Link to comment
Share on other sites
Dave-H

Dave-H

Posted
Posted

I tried flushing the DNS cache but no difference I'm afraid.
:no:
The Microsoft Root Certificate Authority 2011 entry that I have and you don't is the one with <None> as its friendly name.
I wonder if I should just delete it?
:dubbio:

Link to comment
Share on other sites
AstroSkipper

AstroSkipper

Posted
Posted
8 minutes ago, AstroSkipper said:

You're absolutely right. My screenshot belongs to current user. When you compare yours to mine there is one thing strange and this is your Microsoft Root Cerificate Authority 2011. You have twice and I don't know why.

If it were my system I would delete the one with "Friendly Name" <none>.

@Dave-H You was too quick in replying! :yes: But I agree. Delete it!

Link to comment
Share on other sites
AstroSkipper

AstroSkipper

Posted
Posted (edited)
11 hours ago, Dave-H said:

Anyway, I have deleted it, but still no effect I'm afraid.

Sometimes a reboot is necessary especially after changing system settings and configurations. And delete the Internet Explorer cache. By the way have you ever tried reregistering following components in the command prompt? Here if not:
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s

Your system is a brainteaser but a hard nut has to be cracked! :buehehe:

Edited by AstroSkipper
correction
Link to comment
Share on other sites
AstroSkipper

AstroSkipper

Posted
Posted (edited)
On 1/27/2022 at 2:02 PM, Dave-H said:

And this is my current one, which may provide some clue as to why it's not working!

Alright, here is the Windows Update Log from my flawlessly MU accessing system:
https://www.mediafire.com/file/iflfdi6ncoceop8/Windows_Update_2022_-_AstroSkipper.7z/file

@Dave-H Comparing my log file to yours you can see what entries you have to have access MU successfully:

2022-01-27    11:49:29:484    1128    b48    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: +0100)  ===========
2022-01-27    11:49:29:625    1128    b48    Misc      = Process: C:\WINDOWS\System32\svchost.exe
2022-01-27    11:49:29:625    1128    b48    Misc      = Module: C:\WINDOWS\system32\wuaueng.dll
2022-01-27    11:49:29:484    1128    b48    Service    *************
2022-01-27    11:49:29:625    1128    b48    Service    ** START **  Service: Service startup
2022-01-27    11:49:29:625    1128    b48    Service    *********
2022-01-27    11:49:30:812    1128    b48    Agent      * WU client version 7.6.7600.256
2022-01-27    11:49:30:812    1128    b48    Agent      * Base directory: C:\WINDOWS\SoftwareDistribution
2022-01-27    11:49:30:843    1128    b48    Agent      * Access type: No proxy
2022-01-27    11:49:30:875    1128    b48    Agent      * Network state: Connected
2022-01-27    11:50:21:546    1128    b48    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
2022-01-27    11:50:21:546    1128    b48    Agent    ***********  Agent: Initializing global settings cache  ***********
2022-01-27    11:50:21:546    1128    b48    Agent      * WSUS server: <NULL>
2022-01-27    11:50:21:546    1128    b48    Agent      * WSUS status server: <NULL>
2022-01-27    11:50:21:562    1128    b48    Agent      * Target group: (Unassigned Computers)
2022-01-27    11:50:21:562    1128    b48    Agent      * Windows Update access disabled: No
2022-01-27    11:50:21:562    1128    b48    DnldMgr    Download manager restoring 0 downloads
2022-01-27    11:50:21:593    1128    b48    AU    ###########  AU: Initializing Automatic Updates  ###########
2022-01-27    11:50:21:593    1128    b48    AU    AU setting next sqm report timeout to 2022-01-27 10:50:21
2022-01-27    11:50:21:609    1128    b48    AU      # AU disabled through User preference
2022-01-27    11:50:21:609    1128    b48    AU    Initializing featured updates
2022-01-27    11:50:21:625    1128    b48    AU    Found 0 cached featured updates
2022-01-27    11:50:21:625    1128    b48    AU    AU finished delayed initialization
2022-01-27    11:50:22:890    1128    b48    Report    ***********  Report: Initializing static reporting data  ***********
2022-01-27    11:50:22:890    1128    b48    Report      * OS Version = 5.1.2600.3.0.65792
2022-01-27    11:50:23:078    1128    b48    Report      * Computer Brand = MICRO-STAR INTERNATIONAL CO., LTD
2022-01-27    11:50:23:093    1128    b48    Report      * Computer Model = AWRDACPI
2022-01-27    11:50:23:109    1128    b48    Report      * Bios Revision = 6.00 PG
2022-01-27    11:50:23:109    1128    b48    Report      * Bios Name = Award Modular BIOS v6.00PG
2022-01-27    11:50:23:109    1128    b48    Report      * Bios Release Date = 2002-10-24T00:00:00
2022-01-27    11:50:23:109    1128    b48    Report      * Locale ID = 1031
2022-01-27    12:50:23:968    1128    b48    AU    AU received policy change subscription event
2022-01-27    12:50:33:703    1128    b48    AU    AU received policy change subscription event

There are no "warnings" related to wuident.cab as show in your log file:

2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: Send failed with hr = 80072efe.
2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe
2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
2022-01-27    12:29:25:214    1860    1504    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: Send failed with hr = 80072efe.
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
2022-01-27    12:29:25:558    1860    1504    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: Send failed with hr = 80072efe.
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
2022-01-27    12:29:25:902    1860    1504    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: Send failed with hr = 80072efe.
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Misc    WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Setup    FATAL: IsUpdateRequired failed with error 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Setup    WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80072efe
2022-01-27    12:29:26:261    1860    1504    Setup    WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80072EFE
2022-01-27    12:29:26:261    1860    1504    Agent      * WARNING: Skipping scan, self-update check returned 0x80072EFE
2022-01-27    12:29:26:339    1860    1504    Agent      * WARNING: Exit code = 0x80072EFE
2022-01-27    12:29:26:339    1860    1504    Agent    *********
2022-01-27    12:29:26:339    1860    1504    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2022-01-27    12:29:26:339    1860    1504    Agent    *************
2022-01-27    12:29:26:339    1860    1504    Agent    WARNING: WU client failed Searching for update with error 0x80072efe

So my first quick conclusion is you have to reset your Windows Update client and install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead. :rolleyes:

Edited by AstroSkipper
deletion
Link to comment
Share on other sites
Dave-H

Dave-H

Posted
Posted

One thing I don't want is to lose my update history, and I guess resetting will do that.
I do have backups though, so I guess I can always restore it if this does not restore the updates to working.
:)

Link to comment
Share on other sites
Dave-H

Dave-H

Posted
Posted

I just tried completely removing my SoftwareDistribution folder, and trying again.
This should have forced Microsoft Update to have to be set up again from scratch with an empty database, and it was.
Still the same error after a short scan though.
:(

Link to comment
Share on other sites
AstroSkipper

AstroSkipper

Posted
Posted (edited)
On 1/27/2022 at 3:58 PM, Dave-H said:

One thing I don't want is to lose my update history, and I guess resetting will do that.
I do have backups though, so I guess I can always restore it if this does not restore the updates to working.

Of course you'll lose your update history. My suggestion was to make an image of your OS partition to revert back at any time you want. I can restore my whole system in less than a half hour (very old computer, very slow). Your Windows Update history is located in "DataStore.edb". So you can backup this file at first. In your Windows Update Log you can see clearly:

2022-01-27    12:28:48:824    1860    1560    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
2022-01-27    12:28:48:824    1860    1504    Report    WARNING: Reporter failed to upload events with hr = 80240004.

I guess there is a problem with your Windows Update Agent.

I have added a link of "winUpdRestore!v28" right down at the bottom, a more recent version of "winUpdRestore!v23". I used it first.

Then you have to reinstall Windows Update Agent. Resetting of SoftwareDistribution folder is not the same. I suggested you:

On 1/27/2022 at 3:25 PM, AstroSkipper said:

...install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead.

After this procedure you have to reinstall "Restore_WU_XP_2003". Here you have to check if "install.cmd" did its job properly i.e. all commands in "install.cmd" have to be performed properly. Check the correct version of "wuaueng.dll" in both folder system32 and system32\dllcache. Check if all registry entries have been added. If not do it manually by creating a reg file for importing necessary entries from "install.cmd" and copying  wuaueng.dll first in folder system32\dllcache and then in folder system32. And what about some posts before where

On 1/27/2022 at 12:27 AM, AstroSkipper said:

By the way have you ever tried reregistering following components in the command prompt? Here if not:
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /s

So a lot to do! :)
https://www.mediafire.com/file/xn2a1rlriapkhym/winUpdRestore%21v28.zip/file

Edited by AstroSkipper
correction
1
Link to comment
Share on other sites
Dave-H

Dave-H

Posted
Posted

I did re-register those files some time ago, but it didn't change anything.
Initpki.dll took a long time before it reported that it was registered, the other three were pretty instant.

Anyway, I've given all that a try, and the only thing which didn't seem to work in the cmd file was replacing wuaueng.dll.
After rebooting I found there was no wuaueng.dll in the DLLCache folder, and the one in System32 was version 5.4.3790.5512, the one from SP3.
Anyway, I corrected that manually, and the version now in System32 and the DLLCache is 7.6.7600.256.

I'm now getting this -

Clipboard-1.thumb.png.0a67b904a406b110da43247c010258b0.png

There are a number of sites now listed in the Trusted Sites list, more than before, and more than the message says.
They are -

*.microsoft.com
*update.microsoft.com
*windowsupdate.com
*windowsupdate.microsoft.com
http://update.microsoft.com
http://www.update.microsoft.com
https://www.update.microsoft.com

ProxHTTPSProxy appears to be working fine on other sites, but shows no output now on Microsoft Update.
:dubbio:

Link to comment
Share on other sites
maile3241

maile3241

Posted
Posted
1 minute ago, Dave-H said:

I did re-register those files some time ago, but it didn't change anything.
Initpki.dll took a long time before it reported that it was registered, the other three were pretty instant.

Anyway, I've given all that a try, and the only thing which didn't seem to work in the cmd file was replacing wuaueng.dll.
After rebooting I found there was no wuaueng.dll in the DLLCache folder, and the one in System32 was version 5.4.3790.5512, the one from SP3.
Anyway, I corrected that manually, and the version now in System32 and the DLLCache is 7.6.7600.256.

I'm now getting this -

Clipboard-1.thumb.png.0a67b904a406b110da43247c010258b0.png

There are a number of sites now listed in the Trusted Sites list, more than before, and more than the message says.
They are -

*.microsoft.com
*update.microsoft.com
*windowsupdate.com
*windowsupdate.microsoft.com
http://update.microsoft.com
http://www.update.microsoft.com
https://www.update.microsoft.com

ProxHTTPSProxy appears to be working fine on other sites, but shows no output now on Microsoft Update.
:dubbio:

Delete the sites and add the 3 back.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...