I've been fighting w/ a couple of WIN2K machines for a few weeks - Windows
Update has been very reliable for me up 'til now. (Wondering if this could be
a pre-Vista release Break Windows Update ploy to get ppl off Windows 2000?
lol). I had to resort to emailing SUM1 attached/affiliated to
Microsoft -
that's a first for me too. I'm not out of the woods yet, but am seeing some
progress on these test PCs. I wondering if there's some trouble with Windows
Update within
Microsoft itself...news we probably wouldn't hear.
The new MS Installer 3.1.x and the BITS (Background Intelligent Transfer
Service) 2.0 and WinHTTP 5.1 updates come down first prior (if needed on
older or newly imaged systems) to help Windows Update Work better, then the
Critical Updates come down. You also should have a current browser (IE 6 or 7
- I haven't tried 7).
I haven't tried this yet, but hope to tommorrow (on my 3rd reimage of this
PC):
1. Install latest Service Pack + Post SP4 Update Rollup 1
[url]http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=B54730CF-8850-4531-B52B-BF28B324C662&displaylang=en[/url]
2. Install IE 6.0 SP1.
[url]http://www.microsoft.com/downloads/details.aspx?FamilyID=1e1550cb-5e5d-48f5-b02b-20b602228de6&DisplayLang=en[/url]
3. Then load new MS Installer 3.1.x
[url]http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en[/url]
and the BITS 2.0 and WinHTTP 5.1 update:
[url]http://support.microsoft.com/kb/842773[/url]
After all that cr@p, check Automatic Updates, BITS, Event Log services to
make sure they are set to Automatic and ON. THEN try a Windows Update from
the Website.
Well, this is what the MS Windows Update tech sent me, see detailed info
below. I've condensed two of his emails into 6 seperate steps:
From the case log, I understand that an issue is encountered when trying to
access Windows Update with the error code 0x8DDD0009. The issue you are
currently experiencing can be caused by several issues. It can
be caused by Windows Update temporary folders that are corrupted, and also if
the Windows Update services is not working properly. At this time, I suggest
we
perform the following steps to test this issue.
Step1: Check the local Windows Update services.
This issue can occur if three services have not been configured correctly.
Please refer to the following steps to check them:
1. Click Start->Run, type "services.msc" (without quotation marks) in the open
box and click OK.
2. Double click the service "Automatic Updates".
3. Click on the Log On tab, please ensure the option "Local System account" is
selected and the option "Allow service to interact with desktop" is
unchecked.
4. Check if this service has been enabled on the listed Hardware Profile. If
not, please click the Enable button to enable it.
5. Click on the tab "General "; make sure the "Startup Type" is "Automatic".
Then please click the button "Start" under "Service Status" to start the
service.
6. Please repeat the above steps with the other two services:
Background Intelligent Transfer Service
Event log
Note: Event log service is enabled on all of the hardware profiles; this
service
does not have an option to enable or disable on certain hardware profile.
Step 2: Re-register system files.
This issue can also occur if the system files that will be used by the Windows
Update have not been registered. Since there are many system files need to be
checked, I suggest we use the following method to re-register these files:
1. Click Start, Run, type: notepad C:\register.bat and press Enter. Choose Yes
when you are prompted.
2. Copy the following commands and then paste them into the opened Notepad
window.
net stop wuauserv
regsvr32 wuapi.dll /s
regsvr32 wups.dll /s
regsvr32 wuaueng.dll /s
regsvr32 wucltui.dll /s
regsvr32 wuweb.dll /s
regsvr32 msxml.dll /s
regsvr32 msxml2.dll /s
regsvr32 msxml3.dll /s
regsvr32 urlmon.dll /s
net start wuauserv
regsvr32 softpub.dll /s
regsvr32 initpki.dll /s
regsvr32 mssip32.dll /s
regsvr32 wintrust.dll /s
regsvr32 dssenh.dll /s
regsvr32 rsaenh.dll /s
regsvr32 gpkcsp.dll /s
regsvr32 sccbase.dll /s
regsvr32 slbcsp.dll /s
regsvr32 cryptdlg.dll /s
regsvr32 jscript.dll /s
3. After you paste the above commands, please close the Notepad window. Choose
Yes when you are prompted to save the file.
4. Click Start, Run, type: C:\register.bat and press Enter to run the commands
we have pasted.
Step 3: Rename the temporary folder of Windows Update.
This behavior can also occur if the temporary folder of Windows Update
contains
corrupted files. In this situation, we can resolve this problem by following
the
steps below.
1. Click Start, Run, type: cmd and press Enter. Please run the following
command
in the opened window.
net stop WuAuServ
2. Click Start, Run, type: %windir% and press Enter.
3. In the opened folder, rename the folder SoftwareDistribution to SDold.
4. Click Start, Run, type: cmd and press Enter. Please run the following
command
in the opened window.
net start WuAuServ
If the issue persists, to provide you with the most accurate suggestions, I
need
to collect the latest information regarding the behavior of the issue. I have
attached the steps to collect the information as below:
System Information
===============
1. Click Start, click All Programs, click Accessories, click System Tools, and
click System Information.
2. On the popup window, on the menu bar, click File, click Save, click
"Desktop"
on the left pane, and type "NFO" as its file name.
3. Please find the file "NFO" on the desktop and send it as an attachment to
How to collect WindowsUpdate.log:
===========================
1. Click on Start, Run and type "WindowsUpdate.log" (With the quotation
marks)
2. Click on the OK button. You will see a file named "WindowsUpdate.log"
3. Now click on the "File" menu and then click on the "Save As" and select
"Desktop" in the "Save in" option on the top of the window.
4. Click on the Save button. The file will be saved on your Desktop, send the
file to me as an attachment in your email to
Based on the Knowledge Base, this issue can be also caused by corrupted
Windows
Update engine files. At this time, I also suggest we perform the following
steps
to test this issue.
Step 4: Restart the computer in Safe Mode
1. Reboot your computer and start pressing the F8 key on your keyboard.
2. When the Windows Advanced Options menu appears, select Safe Mode, and then
press Enter.
3. Log onto Windows.
NOTE: In Safe Mode, your system display and desktop will look and perform
differently than in normal mode.
Step 5: Remove the corrupted files
1. Click Start-> Search.
2. Select "All files and folders", and then search for the following files:
wuapi.dll
wuauclt1.exe
wuauclt.exe
wuaucpl.cpl
wuaueng1.dll
wuaueng.dll
wuauserv.dll
wucltui.dll
wupdmgr.exe
wups2.dll
wups.dll
wuweb.dll
Tip: when searching for multiple files in Windows, you may enter the file name
continuously like wucltui.dll; wuapi.dll; wuauclt.exe in the search field.
This
will speed up the whole process.
If you find any of the above files, please right click to rename this file to
(such as wuapi.old). Please understand that we may not find all the files
listed
above. If so, it is normal, and please continue to search for the rest of the
files.
After finishing the above steps, please restart the computer in Normal Mode
and
try to access the Windows Update site again.
If we still fail to update the system, I also suggest we reinstall Windows
Update engine to test this issue.
STEP 6. Reinstall Windows Update Engine
Please download and install the latest Windows Update Engine with the
following
link.
[url]http://download.windowsupdate.com/v6/windowsupdate/redist/standalone/WindowsUpdateAgent20-x86.exe[/url]
After that, please visit Windows Update site again to check if we can update
the
system now.
"Drew" wrote:
[color=blue]
> I am trying to update a W2K system. Started with SP3 then SP4 then IE6 and
> when I try to update with Windows update site, get this message. This is the
> second computer that I have this issue with. Some direction would be
> appreciated as I cannot find any articles or other information as to how to
> correct this after trying all the suggestions.
> Thanks in advance.
> --
> Drew[/color]
Linear Mode
