Jump to content

General and specific solutions for problems regarding AU/WU/MU in Windows XP


AstroSkipper
 Share

Recommended Posts

General and specific solutions for problems regarding AU/WU/MU in Windows XP

List of used abbreviations: 

AU = Automatic Updates
AV = Antivirus
IE = Internet Explorer
KB = Knowledge Base
MDL = My Digital Life Forums. Link: https://forums.mydigitallife.net/
MKB = Microsoft Knowledge Base
MU = Microsoft Update
OS = operating system
OSs = operating systems
WU = Windows Update
WUMT = Windows Update MiniTool

We all are well informed about restoring WU/MU in Windows XP. A lot of threads and solutions to get access to WU/MU website. But we are here in a Windows XP forum. Therefore this thread is targeted on Windows XP only and is meant to collect and provide solutions for general or specific problems which can occur after or while restoring update functionality. The main WU/MU related thread, which is targeted on Windows 2000, Windows XP and Windows Vista, is totally bloated and completely out of control, many post are definitely off-topic. To find general or specific solutions you have to be a Sherlock Holmes or you'll need a lot of time to read tons of posts with no or low quality of information. And a lot of  solutions are simply missing. I am no longer interested in posting new solutions or self-created fixes which can never be found again in such threads. From now on I rather try to avoid posting in threads where people are talking permanently off-topic. Therefore I decided to create my own one. Anyway, this main thread can be found here: https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/

The second post of this thread contains a numbered list of general solutions for problems regarding AU/WU/MU and methods of restoring WU/MU functionality in Windows XP. After performing these general solutions and methods, users are able to exclude errors or misconfiguration relating to AU/WU/MU in their Windows XP system. It is senseless to solve a specific problem if there is a general one. If WU/MU can't be restored generally and a user thinks about a reinstallation, the general solutions listed in second post can be tried first. There are different solutions to do this restoring successfully.

General solutions: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216506

The third post of this thread contains a numbered list of specific solutions for problems regarding AU/WU/MU in Windows XP. These specific solutions will be provided with a meaningful title and a link to the creator's post in this thread.

Specific solutions: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216507

The ninth post of this thread contains a numbered list of additional resources which can be helpful or informative to find an efficient solution for a specific problem. I'll only add resources relating to the topic of this thread.

Additional resources: Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216513

More solutions or resources can be added by posting in commenting zone. The idea is one solution, one post. The same applies to additional resources. Today I start to post some general solutions and methods, a brand-new specific solution and an additional resource. If you want to post an AU/WU/MU related solution or an additional resource in this thread, you can use the commenting zone to do this. Please post it by choosing a meaningful headline in bold and font size 18 for better visibility! If it seems to be a real solution (it's not my job to test them all) or an interesting resource, I will list it in second, third or ninth post with a link to the member's original comment for better overview. Due to the modular character of this thread each posted solution or resource can be upvoted or liked separately with credits to their poster. Any discussions or questions about these solutions or resources are explicitly welcome. But one thing must be totally clear, everything should relate to this topic. That means please stay on-topic!

If you enjoyed this thread or maybe you found it interesting and helpful, we would be pleased about any reaction by liking or upvoting and of course commenting.

Kind regards, AstroSkipper :)
 

Edited by AstroSkipper
Update of content
  • Like 4
  • Upvote 1
Link to comment
Share on other sites


Posted (edited)

Specific solutions:

1. Restoring of AU notification popup shield in Windows XP by @AstroSkipper

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216512

2. All options of Automatic Updates (AU) applet are greyed out

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217286

3. Experimental solution for error code 0x80072F78 while accessing WU/MU website

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217616

4. Less-than-ideal solution for error code 0x80072efe or 0x80096010 caused by AU client in Windows XP

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217704

5. Temporary solution to grant access to MU/WU using nginx method due to interference of AV/firewall

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1218247

6. Solution for error code 0x80072f8f while accessing WU/MU website using ProxHTTPSProxy or HTTPSProxy

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1219879

Additional resources: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216513

 

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Here is the official instruction from Microsoft how to reset Windows Update. I've crossed out instructions that aren't referring to Windows XP or 2000. Furthermore I've added steps I found that they are missing or could be helpful. Make a backup if you want to perform this. In any case read carefully!

Manually reset Windows Update components (KB971058)

Important: Follow the steps in this section carefully! Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur! To reset the Windows Update components, follow these steps:
1. Open a command prompt. To do this, use one of the following methods, depending on your version of Windows:
Windows 8.1 and Windows 8: From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click Command Prompt, and then select Run as Administrator.
Windows XP and earlier versions: Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator.
2. Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
3. Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter: Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
4a. If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.).
Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
Ren %systemroot%\system32\catroot2 catroot2.bak
4b. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
5. At a command prompt, type the following command, and then press Enter: cd /d %windir%\system32
6. Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll
And following added by me (@AstroSkipper):
regsvr32.exe mssip32.dll
7. Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter: netsh winsock reset
8. If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter: proxycfg.exe -d
If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter: netsh winhttp reset proxy
9. Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
10. Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter: bitsadmin.exe /reset /allusers
11. Install the latest Windows Update Agent.
12. Restart the computer.

Article ID: 971058 - Last Review: 12/08/2015 06:57:00 - Revision: 42.0
Applies to
Microsoft Windows Update

Here is a link of the original document: 
https://web.archive.org/web/20160307084624/https://support.microsoft.com/en-us/kb/971058
And here is the the latest Windows Update Agent:  http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe. It's version 7.6.7600.256.
Supposedly all these steps should be done by a Microsoft Fixit Tool. No guarantee! Not tested! Here is the link: https://www.mediafire.com/file/r98pvby076rub6j/Mats_Run.WindowsUpdate.exe/file
Although I am not a friend of automatisms, I also offer a another tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to backup your system partition completely at first.
This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk.
The last XP compatible version is 10.5.3.7
https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file
and a less recent version 10.5.3.4 with a help file included: 
https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file

Have a lot of fun!  :cheerleader:

Kind regards, AstroSkipper  :)

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

I have made a complete guide with all the tips and steps which have to be performed to restore access to Microsoft Update website by using IE and ProxHTTPSProxy or HTTPSProxy. Of course at your own risk without any guarantee! And just to clarify: I am not the author or contributor of these patches and tools. I am a user and have examined my problems while restoring MU in Windows XP. This guide is the result of my examinations to help other users. Of course, I did some modifications due to the fact that some patches don't work properly or something is missing. If you want improvements to these tools and patches, please contact the authors! This guide is based on patch + proxy method created by @Windows7fan from MDL. 

Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP

To be successful in restoring of access to MU website, you have to keep the order of following steps. Please, do not change this order!
1. Check BIOS and Windows due to correct date, time and time zone. Perform a time sync!
2. If you have used "WSUS server" in combination with "WUMT" in the past, remove it completely by "Remove_wsus.cmd". This batch file does not work properly, so you have to remove this registry key manually: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate. You can let "Remove_wsus.cmd" perform this by adding the following line (without quotes): "reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f". Start Automatic Update service. In the system panel, Automatic Update may not be shown greyed out.
3. Go to Windows Services. Three system services are absolutely important for MU: BITS, wuauserv and Cryptsvc. These services should have been started and set to automatic.
4. Configure Internet Explorer. Internet Zone to standard, Trusted Zone to high with only these three URLs associated with MU: http://www.update.microsoft.com/https://www.update.microsoft.com/ and  http://update.microsoft.com/. Credits to @maile3241 and @AstroSkipper. Go to Internet Explorer Options, Advanced. Check if TLS 1.2 is enabled. Uncheck entry "Check for server certificate revocation".
5. Before installing updates, apply "PosReady.reg" if not already done.
6. Install these four updates  KB4467770, KB4019276, KB4493435, KB942288-V3. Credits to @maile3241.
7. Apply "Tls 1.2.reg". Credits to @maile3241.
8. Execute "rootsupd.exe".
9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256. Download link: 
http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe
10. Install "ProxHTTPSProxy". Download link: https://i430vx.net/files/XP/ProxHTTPSProxyMII_REV3d_PY344.7z, credits to @heinoganda.
Here you have to edit the config file "config.ini". Under section [SSL No-Verify] I added fe2.update.microsoft.com and deleted update.microsoft.com under sections [SSL Pass-Thru] and [BYPASS URL]. This is working for me.
11. Download and install one of these packages: 
an English all in one version, credits to @Windows7fan from MDL, @xpandvistafan, @maile3241 and @AstroSkipper from MSFN: https://drive.google.com/u/0/uc?id=1z5NGORov8OS7iBkoFVsvWOTOE1_LCjoQ&export=download
or a German all in one version, based on the version above, modified and updated by @AstroSkipper: https://www.mediafire.com/file/0y1zmwv8z4lch9s/Restore_WU_XP_DE.7z/file. Credits to @Windows7fan from MDL, of course.
Here you have to check if "install.cmd" did its job properly, i.e., all commands in "install.cmd" should have been performed completely. Additionally, you have to verify the existence of patched "wuaueng.dll" in both folders system32 and system32\dllcache in form of a binary comparison. Be aware of SFC which tries to restore an original old version of this file! After patching, restart your computer and recheck! Verify if really all registry entries have been added.
All bold files mentioned here are in these all in one versions included. They can be installed manually (all registry entries of "install.cmd" have to be added manually too) or automatically by applying "install.cmd".
12. If you have problems in configuring ProxHTTPSProxy, or you get error code 0x80072f8f while trying to access MU website, have a look at my thread:

13. Use "CAupdater" or "Certificate Updater 1.6" to update your root certificates. The download link of Certificate Updater 1.6 can be found here:
https://msfn.org/board/topic/175170-root-certificates-and-revoked-certificates-for-windows-xp/?do=findComment&comment=1095349
14. If the button "Check for updates" doesn't work on MU, close Internet Explorer, open MU from Start Menu again, and in most cases it will load successfully.
15. If you have a fresh installation or a reinstallation of Windows XP, it seems to be necessary to install MU ActiveX Control manually because it won't be downloaded automatically any longer. Without any confirmation by me (no opportunity to check it), here is a guide how you can do that. Credits to @maile3241:
https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/?do=findComment&comment=1213831
16. If on MU web page error code 0x80072F78 appears, turn off your firewall temporarily. If MU is working now, add the program "wuauClt.exe" into the exception list of your firewall and turn your firewall back on. In any case ProxHTTPSProxy or HTTPSProxy must not be blocked by your firewall. Same for Internet Explorer, of course.
If on MU web page other error codes appear, rename the Windows folder "SoftwareDistribution" to "SoftwareDistribution.old" and let MU generate a fresh one. Maybe you have to disable an "HTTPS scanning" feature of your security software temporarily or make exclusions for MU related sites.
17. Do not use the same "DataStore.edb" in "SoftwareDistribution" for access methods WSUS server/WUMT and MU web version! I have two DataStore.edb files, one for WSUS server and one for MU. One for all doesn't work in my system.
18. Use only http-links to open MU in IE. Direct link is http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en or http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1
19. MU works only if ProxHTTPSProxy is enabled.
20. For testing, I added a link to my working ProxHTTPSProxy's config.ini: https://www.mediafire.com/file/vr1klatuzjh6v5c/ProxHTTPSProxy_-_config.ini/file
21. If completing all of these steps didn't help you at all, even after repeated execution, you may have a rather general problem relating to MU in your Windows XP installation. In this case, you can try to manually reset Windows Update components. Here is my post how you can do that:
https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216508
After that kind of reset, I recommend performing all steps once again (from step 1 to 20 inclusive). Of course, some steps won't be necessary any more but checking which to perform or not will cost a lot of time, therefore senseless. Although I am not a friend of automatisms, I also offer a tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to back up your system partition completely at first or at least the Windows folder SoftwareDistribution. This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk.
The last XP compatible version is 10.5.3.7:
https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file
and a less recent version 10.5.3.4 with a help file included: 
https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file
22. If unfortunately none of all these 21 steps helped you, then you should presumably think about a complete reinstallation of Windows XP.

I did all these steps (except steps 21 and 22) and for me MU is working flawlessly in my Windows XP Professional system.

If you enjoyed this guide, or maybe you found it interesting and helpful, I would be pleased about any reaction by liking or upvoting.  :thumbup

Greetings from Germany,  :hello:

AstroSkipper

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Restoring WU/MU by using WSUS + WUMT method

This is an alternative method to search for updates using a WSUS server and the tool WUMT. IE or an additional proxy isn't needed. In my system it's working fine and is used as an additional method. This is the original link:

https://forums.mydigitallife.net/posts/1628508. Credits to @abbodi1406 at MDL and MSFN. 

Edited by AstroSkipper
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Restoring WU/MU by using nginx method

I didn't test this method but it is said to be working and didn't apparently need ProxHTTPSProxy, This method requires only Internet Explorer 8 and update of Windows Update client. Here is the original link:

https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/page-11#post-1724717. Credits to @owouwu at MDL. 

Edited by AstroSkipper
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Restoring of AU notification popup shield in Windows XP by @AstroSkipper

Last week I was engaged in troubleshooting regarding AU in Windows XP. In my system AU notification popup shield always worked in the past. In February I disabled AU and it disappeared as usual. But last week, after I had enabled AU again, it didn't appear in systray although an important update was found by MU. I could restore it exactly for one Windows session. After restart it didn't work anymore. I had to find out what was going wrong in my system. And I found presumably the cause of this problem, a not properly working Windows system service called BITS. Many Windows users have a lot of problems due to a malfunction of this service. It should be started by system if necessary. But this doesn't happen in all cases. As I already recommended in my "Complete guide for restoring IE's access to WU/MU website using ProxHTTPSProxy or HTTPSProxy in Windows XP", item 2 of General solutions's list, step 3

Quote

Three system services are absolutely important for MU: bits, wuauserv and cryptsvc. These services should have been started and set to automatic.

system service BITS has to be started for a working WU/MU/AU. But very often Windows doesn't do that. Therefore I created a fix to restore AU functionality and missing notification shield.
Here is the link: https://www.mediafire.com/file/6cvbrxg17oth5pz/FixAUWinXP.7z/file. Credits to @AstroSkipper.
This fix is no virus and doesn't contain any malware. I know that because I am the creator. If you have problems with your security scanner, add this fix to AV's exclusion list. Scanned by Avast with no results.

My fix performs a couple of tasks to eliminate typical problems preventing a popup of notification shield: restoring proper functionality of system services BITS, wuauserv and Cryptsvc, setting system to "No proxy", copying a system file to AU selfupdate, setting AU to "Notify me but don't automatically download or install them", triggering AU to detect updates, improving communication between client and server. Finally it restarts system. Here is a screenshot showing the restored notification shield and a window of an important update offered by AU in my Windows XP system:

AU-success-08-04-2022.png

Fix was tested and is working in my system.

Additionally AU can be triggered to show notification shield if it hasn't popped up yet:

1. Check if system service BITS is running. If not, start it.
2. Search for updates using MU website in IE and ProxHTTPSProxy. When searching has been finished, close IE.
3. Uninstall update KB4486463 (2019-02 Security Update for WES09 and POSReady 2009 for x86-based Systems (KB4486463)).
4. Restart computer.
5. After restart check once again if system service BITS is running. If not, start it.
6. AU notification shield should pop up. If not, trigger AU by executing two commands: wuauclt /resetauthorization /detectnow and then wuauclt /reportnow.
7. Now AU notification shield should pop up finally and showing missing update KB4486463.
8. Install offered update KB4486463 via AU.

If update KB4486463 doesn't exist in your system or you don't use POSReady trick, choose another unimportant update which was recently installed.

Edited by AstroSkipper
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Additional resources:

1. Windows Update Error Codes

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217891

2. Windows Event Logs and their Event IDs

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1216671

3. Microsoft Knowledge Base (MKB) and their KB articles

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1217085

4. My essential tools for solving problems in Windows XP

4.1. My essential tools for solving problems in Windows XP — Part 1 — WU/MU tools

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1220689

4.2. My essential tools for solving problems in Windows XP — Part 2 — File extractors and packers

Link: https://msfn.org/board/topic/183498-general-and-specific-solutions-for-problems-regarding-auwumu-in-windows-xp/?do=findComment&comment=1221226
 

 

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Windows Event Logs and their Event IDs

Due to the circumstance that eventid.net doesn't exist anymore (shutdown years ago) an alternative source or database is necessary to search for Windows Event IDs in case of system errors and warnings. Best alternative database: https://kb.eventtracker.com/.
Others: https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/https://www.myeventlog.com/http://www.chicagotech.net/wineventid.htm.

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Hi @Dave-H, I don't know whether you've already tried my fix or not, but just to clarify it, my recommended fix is meant to solve the disappearance of AU notification shield in systray. In my system the fix did its job perfectly. AU notification shield didn't disappear anymore. Additionally I had the hope it would solve the error message with Event ID 16 too. But that does not seem to be the case. It had disappeared in my log, but after two days it came back as in yours. After a bit deeper examination the reason for this error message is totally clear.

Case 1:

System is set to "No proxy". AU tries to download a file called wuident.cab from link https://fe2.update.microsoft.com/v11/3/win7sp1/windowsupdate/selfupdate/wuident.cab. But without ProxHTTPSProxy or HTTPSProxy, no chance. This leads to the error 0x80072efe and, after two days of trying, to Event ID 16.

Case 2:

System is set to use ProxHTTPSProxy or HTTPSProxy "system-wide". Now AU is able to download file wuident.cab, but due to its invalid signature AU can't verify this file which leads to the error 0x80096010 and, after two days of trying, to another Event ID. BTW It would be the wrong version anyway. Unfortunately the address of a matching version is http://download.windowsupdate.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab or http://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab

We, you and me, are using the method of patch in combination with one of our proxies. The patch in combination with all additional steps restores successfully access to MU web site using IE8. But the creator of this patch didn't take account of AU's malfunction.

Case 3

Same proxy settings as in case 2. Due to download of wrong file version I modified the patch i.e. I changed some registry keys the patch had created. After these changes, AU could download and verify wuident.cab successfully, but wasn't able to download the next file, called wsus3setup.cab. Microsoft had deleted the file on the server which AU wanted to download from, therefore it leads to error 0x80190194.

Conclusion:

Either the patch will be modified to restore AU's functionality in online searching, or AU will only be able to find updates offline after a successful and cached search of MU. Provided that we use patch plus proxy method, AU notification pop-up shield can only remind us to download and install the updates MU has found in its search before. If you want to get rid of these errors in your system event log in any case, you have to turn off Automatic Updates in AU applet located in control panel. And one thing we know for a long time: What shall AU still find today? In a fully updated system, simply nothing:no: 
In other systems where updates are still missing, AU's notification pop-up shield can be taken as a reminder:yes: And installation of updates by using AU is working fine as usual.

Kind regards, AstroSkipper  :)

PS: In logical consequence, I turned off AU (via applet in control panel) in my fully updated system, as I used to do it before. I don't need AU trying to download a wrong file in background without any success. So bye, bye AU!  :hello:

Edited by AstroSkipper
Update of content
  • Upvote 1
Link to comment
Share on other sites

Thanks @AstroSkipper.
That all makes perfect sense, and as you say if AU can't be made to work properly, it might as well just be disabled.
It's not like it's ever going to find anything now!
Cheers for the great help as always, and sorry for the delay in responding.
Dave.
:worship:

Link to comment
Share on other sites

I've now discovered that if I disable the Automatic Updates service, I get this on every boot in the Event Log.

Clipboard-1.png.14ab88efb3fcaa2e52e7487483f0523d.png

I guess you just can't win!
I'll re-enable it again.
:D

Link to comment
Share on other sites

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

I've now discovered that if I disable the Automatic Updates service, I get this on every boot in the Event Log.

You shouldn't disable Automatic Updates service, you simply have to turn off Automatic Updates via control panel.

Edited by AstroSkipper
correction
Link to comment
Share on other sites

Posted (edited)
46 minutes ago, AstroSkipper said:
52 minutes ago, Dave-H said:

I've now discovered that if I disable the Automatic Updates service, I get this on every boot in the Event Log.

You shouldn't disable Automatic Updates service, you simply have to disable Automatic Updates in your control panel.

@Dave-H Automatic Updates service should always be started and has to be set to auto. My system event log never showed this error and it doesn't show up now either. :no: I just checked that. :yes:

Edited by AstroSkipper
addition
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

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...