Windows Update Failures

The following notes apply to Windows 98 running Internet Explorer 6, with a DSL connection running PPPoE (like Sympatico (Canada) 'Access Manager', or Ameritech or Verizon), where the Microsoft Windows Update fails with error code '0x80072EF7' very shortly after connecting to the Windows Update Site.

Scrounging around in the user self-help site turned up some interesting and useful articles...

"Kevin J. Kile" <papaefidelis@ameritech.net> suggested the following procedure:

  1. Disconnect from the Internet (right-click --> disconnect).
  2. In the '\Windows\System' directory, rename 'loadwc.exe' as 'DONTloadwc.exe'
  3. In the registry (use 'Start', then 'Run' and enter 'regedit'), navigate to [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck] and make the following changes by clicking the key name on the left: Exit the editor.
    If you are unfamiliar with editing the registry, ask someone for help. Making registry changes willy-nilly is like a neurosurgeon operating on the brain while wearing boxing gloves, blindfolded.
  4. Reboot.
  5. Retry the Windows Update.
[Mike's Comments:]

I have used these instructions, and they worked for me - many thanks to Kevin!!!

After the Windows Update completed, which included the installation of 'Windows Critical Update Notification 4.0', I renamed 'DONTloadwc.exe' back to 'loadwc.exe' in the '\Windows\System' directory, and restored the registry values for 'LoadSENS' and 'LoadLCE' to 'Auto' (something changes 'LoadLCE' back to 'Yes' during the boot process).
NOTE: I have tried to use Windows Update since, and it now appears to work properly, with no more fiddling!


Iain McCracken found a similar solution:

"My big clue was that I could access windows update over my 56k modem, but not with my DSL connection. No changes to anything at all, I just hung up the dsl and dialed the modem and hey presto!"

"After extensive poking and prodding, I've narrowed it down to a couple of stray registry settings (mentioned in Q303346) and problems with MSN Messenger."

"I can now get into windows update every time, but it requires a journey into the registry to change these two settings, and a reboot."

"The registry settings are "LoadLCE" and "LoadSENS" under "HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/WebCheck/" -- these should both be set to "auto" but starting MSN Messenger immediately sets at least one of them to "yes" which is the wrong setting for DSL, and the cause of the windows update failure. Outlook automatically loads Messenger so starting either application will screw you for windows update."

"So, here's the (extremely nasty) workaround."

  1. First make sure that neither Messenger nor Outlook starts when Windows starts. If you don't, you're up the creek without a paddle.
  2. Start 'regedit' (use 'Start', then 'Run' and enter 'regedit'), or your favorite windows registry editor; navigate to [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\WebCheck] and make the following changes by clicking the key name on the left: Exit the editor.
  3. Reboot.
  4. Retry the Windows Update, BEFORE starting Messenger or Outlook.
"This works every time for me, but it is a royal pain in the ass, and as far as I'm concerned, it's a bug in Messenger (or in tapisrv/rnaapp) which should be fixed."

"Iain."

"Alain Maquet" <amaquet@nordnet.fr> wrote additionally:

"In my case, in addition to the various steps mentioned in Iain's message, I had to delete MS Messenger completely; and change the configuration on my DSL connection to prevent IE from loading at start-up. Now, I don't have to change anything. Upon booting, I just click on Windows Update, the connection is made, and bingo, the Updater works."

[Mike's Comments:]

I initially tried this, but found that something was changing 'LoadLCE' back to 'Yes' during the boot process. That seems to cause the Windows Update to fail, so I followed Kevin's scheme instead. Note that I had already deleted Messenger before trying this.


Another Possible Cause Of Failed Updates

Lots of readers have trouble with Windows Update--- either the site itself, or the process of updating from one version of Windows to another. Here's one specific glitch (and a solution), plus additional links that may help if you run into this or any of a wider range of Update problems:

Hi Fred, I had some problems with updates failing to install on my XP machine. I received help from a Microsoft Tech devoted only to the Windows Update site. He was able to help me. A recent visit to one of Microsoft's Community Forums revealed many others with the same difficulties....Darrin
-----
Hello Darrin, Thank you for contacting Microsoft Update Support.

Thank you for providing me the log files and updating me that the steps provided did not help to install the updates, after viewing the log files and as suggested by you the installation of updates fails as it gives a message to run cryptographic service to run on your system.

This error message occurs when the Catroot2 folder on your system is corrupt. Please follow the steps mentioned below to rename the Catroot2 folder:

  1. Close all open programs, including McAfee or other Anti- virus program.

  2. Rename the C:\Windows\System32\catroot2 folder to C:\Windows\System32\CR2OLD by rightclicking on catroot2 and choosing rename. (If you have upgraded to Windows XP from Windows 2000, the CATROOT2 folder should be located in C:\Winnt\System32 folder).

  3. Now try installing the updates. Please let me know if this works for you... Thank you, [support tech]

Thanks, Darrin. Actually, deleting or hiding the Catroot files (catalog root) solves a number of problems, because it forces the Update "wizard" to look at what's actually on your system, rather than what was recorded (perhaps incorrectly) in the catalog.

More help, moving from the specific to the general:

"Catroot" issues:

Source: LangaList Standard Edition 2003-05-05.


This page is maintained by Mike Peterson, mikep@rubberchickencult.ca.
Created November 25, 2002. Last updated June 27, 2017.