Windows Update Error:

I get this error when trying to run windows update after having successfully applied the WinXP SP1:

0x80070057

I checked the http://v4.windowsupdate.microsoft.com/troubleshoot/ page on Microsoft and it suggests 2 possible fixes, but the first says I don't need the fix and the second suggests I change key 'HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Class \ {4D36E96C-E325-11CE-BFC1-08002BE10318} \ 0020'
to a particular value BUT I don't even have that key.. mine stops at '0017' (so there is NO 0020).

Anyone else have this problem? As it stands I can't apply any of the fixes after the WinXP SP1!


-----


Here are the details from the above link:

***
Problem Description:
Customer will see error 0x800A138F when scanning for updates, but the Windows Update.log file will show error 0x80070057.

This appears to be an issue with the program Netop which enters a driver entry into the enum\root\unknown key in the registry.

[HKEY_LOCAL_MACHINE \ SYSTEM \ ControlSet001 \ Control \ Class \ {63C35530-D3DF-11D3-8F5D-0060B0A3612B} \ 0000]
"ProviderName "= "Danware Data A/S "
"DriverDesc "= "NetOp Driver 3 ver. 7.00 (2002014) "
"DriverDate "= "Jan 14 2002 "
"DriverVer "= "7.00 (2002014) "
"MatchingDeviceId "= "danware_netop_driver3 "

Both the DriverDate and DriverVer are not formatted properly

--

Resolutions:
A) Visit http://www.netop.com/tech/download/fix/fixwinup.exe and run this executable If you are running the Netop software.

B) If you have a Lynx device
1. Click on Start, Run and type "REGEDIT" (w/o the quotes). The Registry Editor will open.
*WARNING*
Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

2. Navigate to the following key:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Class \ {4D36E96C-E325-11CE-BFC1-08002BE10318} \ 0020

3. change date from August 16, 2000 to 8/16/2000)
This should resolve the problem

***

 

Do you run Netop? And how about the lynx device, whatever that might be?

 

No, I've never heard of either.

In any case, the problem disappeared after a while. Perhaps their update site was being refurbished or that part of the cycle was down. <shrug>