Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Update > No Windows Update - Automatic Updates Service 'hung on starting' .dll problems .?

Reply
Thread Tools Display Modes

No Windows Update - Automatic Updates Service 'hung on starting' .dll problems .?

 
 
WD
Guest
Posts: n/a

 
      02-25-2005
Hi

I scanned this group for this problem and tried several of the posted
fixes but I still have some problems.

I cannot do Windows Update - IE practically hangs but after several
minutes will try and scan but fails with error 0x800A01AD. (I also
note today that I cannot get the new verson of Windows Update)

I followed previous postings and checked the WUWebControl class is
enabled.
I also went to the registry to confirm that WU is enabled and settings
are correct.

Another post sent me to Services, Automatic Updates Service - which
has the error 'hung on Startup' from the Event Viewer.

This led me to a post to re-register many .dll and also to run "SFC
/Scannow".

This update required my XP Pro CD and seemed to re-load many system
..dll

2 observations :
o If I right-click My Computer and Properties I get 'rundll.exe -
Unable to locate Component' error with the message 'This application
failed to start because mspatcha.dll was not found. Re-installing the
application may fix this problem' If I OK this the System Properties
opens OK
o If I re-run "SFC /Scannow" it goes back to the XP Pro CD again - as
if the first time I ran it had not made a difference.

I have re-booted between all fixes I have tried.

Sorry for the long description - I tried to fit in all the detail I
could - I have SP2 installed and most other things work fine.

All help received with thanks - mail address goes into 'spam' so
replies here please.

Regards
 
Reply With Quote
 
 
 
 
Pat Walters [MSFT]
Guest
Posts: n/a

 
      02-26-2005
"WD",

This is an interesting problem but even deeper than Windows Update. I was
going to recommend deleting the Windows Update ActiveX files, and let the
website download new ones to you. However, you point out that Automatic
Updates service hangs on startup--according to the event viewer.

I recommend the following:
1. Click Start
2. Click Search, then Files and folders
3. In the filename window, copy and paste the following:
WUAUCLT1,WUAUENG1.DLL,WUAUENG.DLL,WUAUSERV.DLL,CDM .DLL,WUAPI.DLL,WUPS.DLL,WU
CLTUI.DLL,IUENGINE.DLL
4. In the More advanced options section, make sure the top 3 checkboxes are
checked.
5. In the "Look in", make sure this is set to the same drive letter as the
Windows Installation.
6. Click Search
7. You might find many matches to the files they were using.
8. Eliminate all matches that are NOT in the following directories:
System32, ServicePackFiles\i386, or $NTServicePackUninstall$. Please leave
those files alone for the moment.
9. Next, eliminate all matches in the System32 folder only.
10. This will defeat System File Protection. Close the Search window.
11. Next, go to the Windows Update website.
12. Try to install just ONE update. If that fails, please do the following:

We need a little more information. Would you mind running through an
attempted installation on the Windows Update website and sending us back the
results? Here's how:

On Windows XP:
1. Close all Internet browsers
2. Open a single Internet Explorer window.
3. In the Internet Explorer window, click Tools
4. Click Windows Update
5. When you reach the Windows Update site, click Custom Install
6. Click Review and Install Updates
7. When presented with multiple updates, uncheck all of them except for one
update (your choice)
8. Look down at the System clock and note the time. Let the minute move
forward one, so that there is no other activity associated with this
attempt.
9. Click Install. Wait for Windows Update to fail. If it succeeds, reply
back and let us know.
10. Assuming it failed, Click Start
11. Click Run
12. Type: %WINDIR%\WindowsUpdate.log
13. Press <Enter> or Click OK
14. When the log opens, scroll down to the hour and minute you memorized in
step 8.
15. Starting at the beginning of the first entry for that minute, click and
drag down and to the right selecting the rest of the log.
16. Click Edit, then Copy, or just press the <CTRL> and <C> keys.
17. Reply to this posting.
18. When that window opens, Tell us what update you attempted to install,
and where it failed from your observation.
19. After this, on a new line, state the following and press <Enter>: Log
entries follow:
20. Place the cursor on the line under the entry from step 19, and then
click Edit, then Paste, or just press the <CTRL> and <V> keys.
21. The log entries copied in steps 15-16 should have copied into your
posting.
22. Send it to us, and let us take a look at this failure.

Sincerely,

Pat Walters [MSFT]


"WD" <W.D.@dickthebuilder.com> wrote in message
news: om...
> Hi
>
> I scanned this group for this problem and tried several of the posted
> fixes but I still have some problems.
>
> I cannot do Windows Update - IE practically hangs but after several
> minutes will try and scan but fails with error 0x800A01AD. (I also
> note today that I cannot get the new verson of Windows Update)
>
> I followed previous postings and checked the WUWebControl class is
> enabled.
> I also went to the registry to confirm that WU is enabled and settings
> are correct.
>
> Another post sent me to Services, Automatic Updates Service - which
> has the error 'hung on Startup' from the Event Viewer.
>
> This led me to a post to re-register many .dll and also to run "SFC
> /Scannow".
>
> This update required my XP Pro CD and seemed to re-load many system
> .dll
>
> 2 observations :
> o If I right-click My Computer and Properties I get 'rundll.exe -
> Unable to locate Component' error with the message 'This application
> failed to start because mspatcha.dll was not found. Re-installing the
> application may fix this problem' If I OK this the System Properties
> opens OK
> o If I re-run "SFC /Scannow" it goes back to the XP Pro CD again - as
> if the first time I ran it had not made a difference.
>
> I have re-booted between all fixes I have tried.
>
> Sorry for the long description - I tried to fit in all the detail I
> could - I have SP2 installed and most other things work fine.
>
> All help received with thanks - mail address goes into 'spam' so
> replies here please.
>
> Regards



 
Reply With Quote
 
WD
Guest
Posts: n/a

 
      03-02-2005
Hi Pat

Firstly thanks for the comprehensive reply - and apologies for the
delay in replying. I looked for replies for a few days and all the
posts before and after had comments except mine so I thought it had
slipped by un-noticed.

OK - here's what happened :

I searched the files and deleted 3-or-4 from other locations. One
file could not be deleted from the System32 folder 'wuauserv.dll' as
it was 'access denied'

I ran WU but it failed - see error log :
-snip!-
2005-03-02 11:22:09-0000 3648 c7c Unable to connect to the service
(hr=80080005)
2005-03-02 11:22:09-0000 3648 c7c Unable to establish connection to
the service. (hr=80080005)
2005-03-02 11:24:17-0000 3648 c7c Unable to connect to the service
(hr=80080005)
2005-03-02 11:24:17-0000 3648 c7c Unable to establish connection to
the service. (hr=80080005)
2005-03-02 11:25:01-0000 3648 c7c Checking for different Redirector
at: http://download.windowsupdate.com/ms...ir/wuredir.cab
2005-03-02 11:25:01-0000 3648 c7c WinInet: Server file is not newer.
Skipping download.
2005-03-02 11:25:02-0000 3648 c7c Successfully refreshed Redirector
cab.
2005-03-02 11:25:02-0000 3648 c7c WinInet: Server file is not newer.
Skipping download.
2005-03-02 11:25:06-0000 3648 c7c WinInet: Download speed is 3719
bytes/sec
2005-03-02 11:25:06-0000 3648 c7c WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...en/wusetup.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
2005-03-02 11:25:07-0000 3648 c7c Loading inf file
C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
2005-03-02 11:25:07-0000 3648 c7c Section name: cdm: Index: 0
2005-03-02 11:25:07-0000 3648 c7c Section name: iuengine: Index: 1
2005-03-02 11:25:07-0000 3648 c7c Section name: wuapi: Index: 2
2005-03-02 11:25:07-0000 3648 c7c Section name: wuauclt: Index: 3
2005-03-02 11:25:07-0000 3648 c7c Section name: wuauclt1: Index: 4
2005-03-02 11:25:07-0000 3648 c7c Section name: wuaucpl: Index: 5
2005-03-02 11:25:07-0000 3648 c7c Section name: wuaueng_WebSetup:
Index: 6
2005-03-02 11:25:07-0000 3648 c7c Section name: wuaueng1: Index: 7
2005-03-02 11:25:07-0000 3648 c7c Section name: wuauserv_WebSetup:
Index: 8
2005-03-02 11:25:07-0000 3648 c7c Section name: wucltui: Index: 9
2005-03-02 11:25:07-0000 3648 c7c Section name: wups: Index: 10
2005-03-02 11:25:07-0000 3648 c7c Section name: winhttp: Index: 11
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary: C:\WINDOWS\system32\cdm.dll:
Target version: 5.5.3790.2182 Required: 5.5.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\iuengine.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\iuengine.dll: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuapi.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuapi.dll: Target version: 5.4.3790.2182 Required:
5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuauclt.exe is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuauclt.exe: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuauclt1.exe is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuauclt1.exe: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuaucpl.cpl is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuaucpl.cpl: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuaueng.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuaueng.dll: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wuaueng1.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wuaueng1.dll: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wucltui.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wucltui.dll: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-02 11:25:07-0000 3648 c7c Required Version for binary
C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
2005-03-02 11:25:07-0000 3648 c7c Binary:
C:\WINDOWS\system32\wups.dll: Target version: 5.4.3790.2182 Required:
5.4.3790.2182
2005-03-02 11:28:30-0000 3648 c7c Unable to connect to the service
(hr=80080005)
2005-03-02 11:28:30-0000 3648 c7c Unable to establish connection to
the service. (hr=80080005)
2005-03-02 11:28:30-0000 3648 c7c Unable to initiate asynchronous
search, hr=80080005
-snip!-

I am about to drop you a mail to say I posted a reply - hope that is
OK.

I'm also going to reboot to see if the Automatic Updates Service will
start after those file deletions.

Thanks in advance for your help, regards



"Pat Walters [MSFT]" <a-> wrote in message news:<422089e7$>...
> "WD",
>
> This is an interesting problem but even deeper than Windows Update. I was
> going to recommend deleting the Windows Update ActiveX files, and let the
> website download new ones to you. However, you point out that Automatic
> Updates service hangs on startup--according to the event viewer.
>
> I recommend the following:
> 1. Click Start
> 2. Click Search, then Files and folders
> 3. In the filename window, copy and paste the following:
> WUAUCLT1,WUAUENG1.DLL,WUAUENG.DLL,WUAUSERV.DLL,CDM .DLL,WUAPI.DLL,WUPS.DLL,WU
> CLTUI.DLL,IUENGINE.DLL
> 4. In the More advanced options section, make sure the top 3 checkboxes are
> checked.
> 5. In the "Look in", make sure this is set to the same drive letter as the
> Windows Installation.
> 6. Click Search
> 7. You might find many matches to the files they were using.
> 8. Eliminate all matches that are NOT in the following directories:
> System32, ServicePackFiles\i386, or $NTServicePackUninstall$. Please leave
> those files alone for the moment.
> 9. Next, eliminate all matches in the System32 folder only.
> 10. This will defeat System File Protection. Close the Search window.
> 11. Next, go to the Windows Update website.
> 12. Try to install just ONE update. If that fails, please do the following:
>
> We need a little more information. Would you mind running through an
> attempted installation on the Windows Update website and sending us back the
> results? Here's how:
>
> On Windows XP:
> 1. Close all Internet browsers
> 2. Open a single Internet Explorer window.
> 3. In the Internet Explorer window, click Tools
> 4. Click Windows Update
> 5. When you reach the Windows Update site, click Custom Install
> 6. Click Review and Install Updates
> 7. When presented with multiple updates, uncheck all of them except for one
> update (your choice)
> 8. Look down at the System clock and note the time. Let the minute move
> forward one, so that there is no other activity associated with this
> attempt.
> 9. Click Install. Wait for Windows Update to fail. If it succeeds, reply
> back and let us know.
> 10. Assuming it failed, Click Start
> 11. Click Run
> 12. Type: %WINDIR%\WindowsUpdate.log
> 13. Press <Enter> or Click OK
> 14. When the log opens, scroll down to the hour and minute you memorized in
> step 8.
> 15. Starting at the beginning of the first entry for that minute, click and
> drag down and to the right selecting the rest of the log.
> 16. Click Edit, then Copy, or just press the <CTRL> and <C> keys.
> 17. Reply to this posting.
> 18. When that window opens, Tell us what update you attempted to install,
> and where it failed from your observation.
> 19. After this, on a new line, state the following and press <Enter>: Log
> entries follow:
> 20. Place the cursor on the line under the entry from step 19, and then
> click Edit, then Paste, or just press the <CTRL> and <V> keys.
> 21. The log entries copied in steps 15-16 should have copied into your
> posting.
> 22. Send it to us, and let us take a look at this failure.
>
> Sincerely,
>
> Pat Walters [MSFT]
>
>
> "WD" <W.D.@dickthebuilder.com> wrote in message
> news: om...
> > Hi
> >
> > I scanned this group for this problem and tried several of the posted
> > fixes but I still have some problems.
> >
> > I cannot do Windows Update - IE practically hangs but after several
> > minutes will try and scan but fails with error 0x800A01AD. (I also
> > note today that I cannot get the new verson of Windows Update)
> >
> > I followed previous postings and checked the WUWebControl class is
> > enabled.
> > I also went to the registry to confirm that WU is enabled and settings
> > are correct.
> >
> > Another post sent me to Services, Automatic Updates Service - which
> > has the error 'hung on Startup' from the Event Viewer.
> >
> > This led me to a post to re-register many .dll and also to run "SFC
> > /Scannow".
> >
> > This update required my XP Pro CD and seemed to re-load many system
> > .dll
> >
> > 2 observations :
> > o If I right-click My Computer and Properties I get 'rundll.exe -
> > Unable to locate Component' error with the message 'This application
> > failed to start because mspatcha.dll was not found. Re-installing the
> > application may fix this problem' If I OK this the System Properties
> > opens OK
> > o If I re-run "SFC /Scannow" it goes back to the XP Pro CD again - as
> > if the first time I ran it had not made a difference.
> >
> > I have re-booted between all fixes I have tried.
> >
> > Sorry for the long description - I tried to fit in all the detail I
> > could - I have SP2 installed and most other things work fine.
> >
> > All help received with thanks - mail address goes into 'spam' so
> > replies here please.
> >
> > Regards

 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      03-06-2005
"WD" <W.D.@dickthebuilder.com> wrote in message
news: om
....
> I searched the files and deleted 3-or-4 from other locations. One
> file could not be deleted from the System32 folder 'wuauserv.dll' as
> it was 'access denied'


Try stopping the wuauserv service or reboot in safe mode
before you do that. Probably the service had that file open before.

If you have the tasklist utility you could check which task has it open

tasklist /fi "Modules eq wuauserv.dll"

If the task turns out to be svchost.exe (likely) you would also need
to do something like:

tasklist /svc /fi "Modules eq wuauserv.dll"

When I do that there is a long list of services for ones which could
possibly be preventing you from deleting that module.
The most obvious one would be wuauserv; so then you would try:

net stop wuauserv

Then repeat everything, either to delete the module (if that is what
you are doing) or prove that it is no longer in use by any task or service.

BTW in case using command line commands is too intimidating for you
I think you might also achieve the same objective (stopping use of
the module wuauserv.dll) by rebooting in safe mode and retrying
your operation with it then. E.g. others who only wanted to re-register
other modules used by that service (in particular wuaueng.dll) were
successful doing it that way.

http://www.microsoft.com/windowsxp/e...xp=&sloc=en-us

(Web interface search for
wuaueng 80070005 aldwinckle
)


Good luck

Robert Aldwinckle
---


 
Reply With Quote
 
WD
Guest
Posts: n/a

 
      03-08-2005
"Robert Aldwinckle" <> wrote in message news:<>...
> "WD" <W.D.@dickthebuilder.com> wrote in message
> news: om
> ...
> > I searched the files and deleted 3-or-4 from other locations. One
> > file could not be deleted from the System32 folder 'wuauserv.dll' as
> > it was 'access denied'

>
> Try stopping the wuauserv service or reboot in safe mode
> before you do that. Probably the service had that file open before.
>
> If you have the tasklist utility you could check which task has it open
>
> tasklist /fi "Modules eq wuauserv.dll"
>
> If the task turns out to be svchost.exe (likely) you would also need
> to do something like:
>
> tasklist /svc /fi "Modules eq wuauserv.dll"
>
> When I do that there is a long list of services for ones which could
> possibly be preventing you from deleting that module.
> The most obvious one would be wuauserv; so then you would try:
>
> net stop wuauserv
>
> Then repeat everything, either to delete the module (if that is what
> you are doing) or prove that it is no longer in use by any task or service.
>
> BTW in case using command line commands is too intimidating for you
> I think you might also achieve the same objective (stopping use of
> the module wuauserv.dll) by rebooting in safe mode and retrying
> your operation with it then. E.g. others who only wanted to re-register
> other modules used by that service (in particular wuaueng.dll) were
> successful doing it that way.
>
> http://www.microsoft.com/windowsxp/e...xp=&sloc=en-us
>
> (Web interface search for
> wuaueng 80070005 aldwinckle
> )
>
>
> Good luck
>
> Robert Aldwinckle
> ---



Hi Robert

Thanks for the further tips. Here's where we are :

I re-booted to safe mode to removed the wuauserv.dll from the system32
folder.

I used the command lines above but the 'net stop wuauserv' would not
let me execute it in regular mode.

I re-booted back from safe to regular mode - re-searched the list of
..dll and none show in System32.

I then checked Automatic Updates Service - which is now in Manual
startup mode. It fails with 'module is not found'

I tried a Windows Update which looked as if it was working - in fact
it went to download a new version. Sadly it failed with an error :

-snip!-
"2005-03-08 11:24:12-0000 1564 82c CreateObject for
Microsoft.Update.ServiceManager failed: error 0x8007007e
2005-03-08 11:24:19-0000 1564 82c CreateObject for
Microsoft.Update.ServiceManager failed: error 0x8007007e
2005-03-08 11:24:46-0000 1564 82c Checking for different Redirector
at: http://download.windowsupdate.com/ms...ir/wuredir.cab
2005-03-08 11:24:46-0000 1564 82c WinInet: Server file is not newer.
Skipping download.
2005-03-08 11:24:46-0000 1564 82c Successfully refreshed Redirector
cab.
2005-03-08 11:24:47-0000 1564 82c WinInet: Server file is not newer.
Skipping download.
2005-03-08 11:24:49-0000 1564 82c WinInet: Download speed is 7185
bytes/sec
2005-03-08 11:24:49-0000 1564 82c WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...en/wusetup.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
2005-03-08 11:24:49-0000 1564 82c Loading inf file
C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
2005-03-08 11:24:49-0000 1564 82c Section name: cdm: Index: 0
2005-03-08 11:24:49-0000 1564 82c Section name: iuengine: Index: 1
2005-03-08 11:24:49-0000 1564 82c Section name: wuapi: Index: 2
2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt: Index: 3
2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt1: Index: 4
2005-03-08 11:24:49-0000 1564 82c Section name: wuaucpl: Index: 5
2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng_WebSetup:
Index: 6
2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng1: Index: 7
2005-03-08 11:24:49-0000 1564 82c Section name: wuauserv_WebSetup:
Index: 8
2005-03-08 11:24:49-0000 1564 82c Section name: wucltui: Index: 9
2005-03-08 11:24:49-0000 1564 82c Section name: wups: Index: 10
2005-03-08 11:24:49-0000 1564 82c Section name: winhttp: Index: 11
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary: C:\WINDOWS\system32\cdm.dll:
Target version: 0.0.0.0 Required: 5.5.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\iuengine.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\iuengine.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuapi.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuapi.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuauclt.exe is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuauclt.exe: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuauclt1.exe is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuauclt1.exe: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuaucpl.cpl is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuaucpl.cpl: Target version: 5.4.3790.2182
Required: 5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuaueng.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuaueng.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuaueng1.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuaueng1.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wuauserv.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wuauserv.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wucltui.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wucltui.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:24:49-0000 1564 82c Required Version for binary
C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
2005-03-08 11:24:49-0000 1564 82c Binary:
C:\WINDOWS\system32\wups.dll: Target version: 0.0.0.0 Required:
5.4.3790.2182
2005-03-08 11:25:15-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co.../XP/en/cdm.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\cdm.cab
2005-03-08 11:25:15-0000 1564 884 Local CAB
C:\WINDOWS\SoftwareDistribution\WebSetup\iuengine. cab will be used
2005-03-08 11:25:36-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...P/en/wuapi.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.cab
2005-03-08 11:25:49-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...n/wuauclt1.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt1. cab
2005-03-08 11:27:12-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...en/wuaueng.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng.c ab
2005-03-08 11:27:32-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...n/wuaueng1.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng1. cab
2005-03-08 11:27:35-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...n/wuauserv.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauserv. cab
2005-03-08 11:27:44-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...en/wucltui.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wucltui.c ab
2005-03-08 11:27:50-0000 1564 884 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.co...XP/en/wups.cab
to file C:\WINDOWS\SoftwareDistribution\WebSetup\wups.cab
2005-03-08 11:27:50-0000 1564 884 Starting File operations for section
cdm
2005-03-08 11:27:50-0000 1564 884 Target file
C:\WINDOWS\system32\cdm.dll doesn't exist
2005-03-08 11:27:50-0000 1564 884 File operations for section cdm
completed successfully
2005-03-08 11:27:50-0000 1564 884 Starting File operations for section
iuengine
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\iuengine.dll doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section iuengine
completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wuapi
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\wuapi.dll doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section wuapi
completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wuauclt1
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\wuauclt1.exe doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section wuauclt1
completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wuaueng_WebSetup
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\wuaueng.dll doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section
wuaueng_WebSetup completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wuaueng1
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\wuaueng1.dll doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section wuaueng1
completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wuauserv_WebSetup
2005-03-08 11:27:51-0000 1564 884 Target file
C:\WINDOWS\system32\wuauserv.dll doesn't exist
2005-03-08 11:27:51-0000 1564 884 File operations for section
wuauserv_WebSetup completed successfully
2005-03-08 11:27:51-0000 1564 884 Starting File operations for section
wucltui
2005-03-08 11:27:52-0000 1564 884 Target file
C:\WINDOWS\system32\wucltui.dll doesn't exist
2005-03-08 11:27:52-0000 1564 884 File operations for section wucltui
completed successfully
2005-03-08 11:27:52-0000 1564 884 Starting File operations for section
wups
2005-03-08 11:27:52-0000 1564 884 Target file
C:\WINDOWS\system32\wups.dll doesn't exist
2005-03-08 11:27:52-0000 1564 884 File operations for section wups
completed successfully
2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
section cdm..
2005-03-08 11:27:52-0000 1564 884 Completed registration operations
for section cdm: status 0
2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
section iuengine..
2005-03-08 11:27:52-0000 1564 884 Completed registration operations
for section iuengine: status 0
2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
section wuapi..
2005-03-08 11:27:52-0000 1564 884 Registration:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuapi.dll"
2005-03-08 11:27:52-0000 1564 884 Completed registration operations
for section wuapi: status 0
2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
section wuauclt1..
2005-03-08 11:27:52-0000 1564 884 Completed registration operations
for section wuauclt1: status 0
2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
section wuaueng_WebSetup..
2005-03-08 11:27:52-0000 1564 884 Registration:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
2005-03-08 11:27:52-0000 1564 884 Registration failed with error
0x80070003
2005-03-08 11:27:52-0000 1564 884 Completed registration operations
for section wuaueng_WebSetup: status 0x80070003
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\cdm.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\iuengine.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wuapi.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wuauclt1.exe successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wuaueng.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
C:\WINDOWS\help\wuauhelp.chm.wusetup.1241031.bak back to
C:\WINDOWS\help\wuauhelp.chm successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
C:\WINDOWS\INF\wuau.adm.wusetup.1241250.bak back to
C:\WINDOWS\INF\wuau.adm successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wuaueng1.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wuauserv.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wucltui.dll successfully
2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
C:\WINDOWS\system32\wups.dll successfully
2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
error 0x80070003
2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
error:0x80070003
2005-03-08 11:27:52-0000 1564 884 UpdateClientWorker failed: error
0x80070003"
-snip!-

Now if I go back to Automatic Updates Service it hangs on startup with
the same error as before.

Again, all help received with thanks

RG
(WD)
 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      03-08-2005
(interleaved reply - trace annotated)
"WD" <W.D.@dickthebuilder.com> wrote in message news: om...
> "Robert Aldwinckle" <> wrote in message news:<>...
>> "WD" <W.D.@dickthebuilder.com> wrote in message
>> news: om
>> ...
>> > I searched the files and deleted 3-or-4 from other locations. One
>> > file could not be deleted from the System32 folder 'wuauserv.dll' as
>> > it was 'access denied'

>>
>> Try stopping the wuauserv service or reboot in safe mode
>> before you do that. Probably the service had that file open before.

....

> Hi Robert
>
> Thanks for the further tips. Here's where we are :
>
> I re-booted to safe mode to removed the wuauserv.dll from the system32
> folder.
>
> I used the command lines above but the 'net stop wuauserv' would not
> let me execute it in regular mode.


Did you forget why I suggested that you boot in safe mode? <eg>

<quote>
>> I think you might also achieve the same objective (stopping use of
>> the module wuauserv.dll) by rebooting in safe mode and retrying
>> your operation with it then.

</quote>

Booting in safe mode means that you are running without starting
non-essential services such as wuauserv; so it would have been
already "stopped" and trying to stop it would have been an error.


>
> I re-booted back from safe to regular mode - re-searched the list of
> .dll and none show in System32.
>
> I then checked Automatic Updates Service - which is now in Manual
> startup mode. It fails with 'module is not found'


This is Pat's show. Deleting all these modules is new to me.
I would expect that observation because you have deleted modules
needed to run the service.


>
> I tried a Windows Update which looked as if it was working - in fact
> it went to download a new version. Sadly it failed with an error :
>
> -snip!-
> "2005-03-08 11:24:12-0000 1564 82c CreateObject for
> Microsoft.Update.ServiceManager failed: error 0x8007007e
> 2005-03-08 11:24:19-0000 1564 82c CreateObject for
> Microsoft.Update.ServiceManager failed: error 0x8007007e


Those codes all mean that a module was missing.
Again, not unsurprising. Disappointing that it doesn't tell you which
modules are missing though. If this was a problem you could run
FileMon, perhaps filtering on wu, to try to get more clues about
what it means.


> 2005-03-08 11:24:46-0000 1564 82c Checking for different Redirector
> at: http://download.windowsupdate.com/ms...ir/wuredir.cab
> 2005-03-08 11:24:46-0000 1564 82c WinInet: Server file is not newer.
> Skipping download.
> 2005-03-08 11:24:46-0000 1564 82c Successfully refreshed Redirector
> cab.
> 2005-03-08 11:24:47-0000 1564 82c WinInet: Server file is not newer.
> Skipping download.
> 2005-03-08 11:24:49-0000 1564 82c WinInet: Download speed is 7185
> bytes/sec
> 2005-03-08 11:24:49-0000 1564 82c WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...en/wusetup.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
> 2005-03-08 11:24:49-0000 1564 82c Loading inf file
> C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
> 2005-03-08 11:24:49-0000 1564 82c Section name: cdm: Index: 0
> 2005-03-08 11:24:49-0000 1564 82c Section name: iuengine: Index: 1
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuapi: Index: 2
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt: Index: 3
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt1: Index: 4
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuaucpl: Index: 5
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng_WebSetup:
> Index: 6
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng1: Index: 7
> 2005-03-08 11:24:49-0000 1564 82c Section name: wuauserv_WebSetup:
> Index: 8
> 2005-03-08 11:24:49-0000 1564 82c Section name: wucltui: Index: 9
> 2005-03-08 11:24:49-0000 1564 82c Section name: wups: Index: 10
> 2005-03-08 11:24:49-0000 1564 82c Section name: winhttp: Index: 11
> 2005-03-08 11:24:49-0000 1564 82c Required Version for binary
> C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
> 2005-03-08 11:24:49-0000 1564 82c Binary: C:\WINDOWS\system32\cdm.dll:
> Target version: 0.0.0.0 Required: 5.5.3790.2182
> 2005-03-08 11:24:49-0000 1564 82c Required Version for binary

....
> C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
> 2005-03-08 11:24:49-0000 1564 82c Binary:
> C:\WINDOWS\system32\wups.dll: Target version: 0.0.0.0 Required:
> 5.4.3790.2182


Notice all the "Target version: 0.0.0.0" I suspect that this is a quirky
way of telling us that a module was not found.


> 2005-03-08 11:25:15-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co.../XP/en/cdm.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\cdm.cab
> 2005-03-08 11:25:15-0000 1564 884 Local CAB
> C:\WINDOWS\SoftwareDistribution\WebSetup\iuengine. cab will be used
> 2005-03-08 11:25:36-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...P/en/wuapi.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.cab
> 2005-03-08 11:25:49-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...n/wuauclt1.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt1. cab
> 2005-03-08 11:27:12-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...en/wuaueng.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng.c ab
> 2005-03-08 11:27:32-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...n/wuaueng1.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng1. cab
> 2005-03-08 11:27:35-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...n/wuauserv.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauserv. cab
> 2005-03-08 11:27:44-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...en/wucltui.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wucltui.c ab
> 2005-03-08 11:27:50-0000 1564 884 WinInet: Successfully downloaded
> http://v5.windowsupdate.microsoft.co...XP/en/wups.cab
> to file C:\WINDOWS\SoftwareDistribution\WebSetup\wups.cab


It might be interesting to drill down to all those .cab files and open
them up to verify that they contain what we think that they should contain
---e.g. replacement modules for all the ones that you deleted,
especially replacement modules for the ones above which showed
that "Target version: 0.0.0.0" that I previously commented on
and which should have versions equal to the stated "Required version".


> 2005-03-08 11:27:50-0000 1564 884 Starting File operations for section
> cdm
> 2005-03-08 11:27:50-0000 1564 884 Target file
> C:\WINDOWS\system32\cdm.dll doesn't exist
> 2005-03-08 11:27:50-0000 1564 884 File operations for section cdm
> completed successfully

....
> 2005-03-08 11:27:52-0000 1564 884 Starting File operations for section
> wups
> 2005-03-08 11:27:52-0000 1564 884 Target file
> C:\WINDOWS\system32\wups.dll doesn't exist
> 2005-03-08 11:27:52-0000 1564 884 File operations for section wups
> completed successfully


I think that there is a lot of ambiguity in those messages.
What "file operations" "completed successfully"?
Proving that the file doesn't exist?
(Hopefully) extracting each from its respective .cab file
and copying it to its proper System directories?
Something intermediate?
Again, monitoring with FileMon would clarify what these
messages really are summarizing and again, after the fact,
you may be able to check manually what has been done.


> 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> section cdm..
> 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> for section cdm: status 0
> 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> section iuengine..
> 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> for section iuengine: status 0
> 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> section wuapi..
> 2005-03-08 11:27:52-0000 1564 884 Registration:
> C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuapi.dll"
> 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> for section wuapi: status 0
> 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> section wuauclt1..
> 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> for section wuauclt1: status 0
> 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> section wuaueng_WebSetup..
> 2005-03-08 11:27:52-0000 1564 884 Registration:
> C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
> 2005-03-08 11:27:52-0000 1564 884 Registration failed with error
> 0x80070003
> 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> for section wuaueng_WebSetup: status 0x80070003


So, finally we see the problem. It seems to be a variant of the
problem that I referred you to with my older thread (the one which
gave us the idea to try re-registering wuaueng.dll after booting
in safe mode.) However, since it is a different code it is probably
more of an error condition than that one was.

In fact, this particular code in the context of WU has often
been successfully interpreted as a sign that the SoftwareDistribution
directory was somehow corrupt (or in your case perhaps incompatible
if you now have newer versions of the modules which you deleted.)

http://groups-beta.google.com/groups...t=0&scoring=d&

(Google Groups search for
SoftwareDistribution 80070003 OR 0x80070003 MSFT OR MVP group:microsoft.public.windowsupdate
- sorted by date to capture current thinking on the matter
)


> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\cdm.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\iuengine.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wuapi.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wuauclt1.exe successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wuaueng.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
> C:\WINDOWS\help\wuauhelp.chm.wusetup.1241031.bak back to
> C:\WINDOWS\help\wuauhelp.chm successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
> C:\WINDOWS\INF\wuau.adm.wusetup.1241250.bak back to
> C:\WINDOWS\INF\wuau.adm successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wuaueng1.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wuauserv.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wucltui.dll successfully
> 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> C:\WINDOWS\system32\wups.dll successfully


I wonder what else was "rolled back"? <eg>
It may be difficult for you to diagnose what went wrong
if everything was deleted before you get a chance to inspect it!


> 2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
> error 0x80070003
> 2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
> error:0x80070003
> 2005-03-08 11:27:52-0000 1564 884 UpdateClientWorker failed: error
> 0x80070003"
> -snip!-
>
> Now if I go back to Automatic Updates Service it hangs on startup with
> the same error as before.


I wouldn't expect the service to run until you get its modules replaced.
I'm slightly amazed to see that it appears that eventually everything
which you deleted may be restored so (relatively) automatically.


>
> Again, all help received with thanks
>
> RG
> (WD)



Good luck

Robert
---


 
Reply With Quote
 
WD
Guest
Posts: n/a

 
      03-10-2005
"Robert Aldwinckle" <> wrote in message news:<e1sMBs$>...
> (interleaved reply - trace annotated)
> "WD" <W.D.@dickthebuilder.com> wrote in message news: om...
> > "Robert Aldwinckle" <> wrote in message news:<>...
> >> "WD" <W.D.@dickthebuilder.com> wrote in message
> >> news: om
> >> ...
> >> > I searched the files and deleted 3-or-4 from other locations. One
> >> > file could not be deleted from the System32 folder 'wuauserv.dll' as
> >> > it was 'access denied'
> >>
> >> Try stopping the wuauserv service or reboot in safe mode
> >> before you do that. Probably the service had that file open before.

> ...
>
> > Hi Robert
> >
> > Thanks for the further tips. Here's where we are :
> >
> > I re-booted to safe mode to removed the wuauserv.dll from the system32
> > folder.
> >
> > I used the command lines above but the 'net stop wuauserv' would not
> > let me execute it in regular mode.

>
> Did you forget why I suggested that you boot in safe mode? <eg>
>
> <quote>
> >> I think you might also achieve the same objective (stopping use of
> >> the module wuauserv.dll) by rebooting in safe mode and retrying
> >> your operation with it then.

> </quote>
>
> Booting in safe mode means that you are running without starting
> non-essential services such as wuauserv; so it would have been
> already "stopped" and trying to stop it would have been an error.
>
>
> >
> > I re-booted back from safe to regular mode - re-searched the list of
> > .dll and none show in System32.
> >
> > I then checked Automatic Updates Service - which is now in Manual
> > startup mode. It fails with 'module is not found'

>
> This is Pat's show. Deleting all these modules is new to me.
> I would expect that observation because you have deleted modules
> needed to run the service.
>
>
> >
> > I tried a Windows Update which looked as if it was working - in fact
> > it went to download a new version. Sadly it failed with an error :
> >
> > -snip!-
> > "2005-03-08 11:24:12-0000 1564 82c CreateObject for
> > Microsoft.Update.ServiceManager failed: error 0x8007007e
> > 2005-03-08 11:24:19-0000 1564 82c CreateObject for
> > Microsoft.Update.ServiceManager failed: error 0x8007007e

>
> Those codes all mean that a module was missing.
> Again, not unsurprising. Disappointing that it doesn't tell you which
> modules are missing though. If this was a problem you could run
> FileMon, perhaps filtering on wu, to try to get more clues about
> what it means.
>
>
> > 2005-03-08 11:24:46-0000 1564 82c Checking for different Redirector
> > at: http://download.windowsupdate.com/ms...ir/wuredir.cab
> > 2005-03-08 11:24:46-0000 1564 82c WinInet: Server file is not newer.
> > Skipping download.
> > 2005-03-08 11:24:46-0000 1564 82c Successfully refreshed Redirector
> > cab.
> > 2005-03-08 11:24:47-0000 1564 82c WinInet: Server file is not newer.
> > Skipping download.
> > 2005-03-08 11:24:49-0000 1564 82c WinInet: Download speed is 7185
> > bytes/sec
> > 2005-03-08 11:24:49-0000 1564 82c WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...en/wusetup.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.c ab
> > 2005-03-08 11:24:49-0000 1564 82c Loading inf file
> > C:\WINDOWS\SoftwareDistribution\WebSetup\wusetup.i nf
> > 2005-03-08 11:24:49-0000 1564 82c Section name: cdm: Index: 0
> > 2005-03-08 11:24:49-0000 1564 82c Section name: iuengine: Index: 1
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuapi: Index: 2
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt: Index: 3
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuauclt1: Index: 4
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuaucpl: Index: 5
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng_WebSetup:
> > Index: 6
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuaueng1: Index: 7
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wuauserv_WebSetup:
> > Index: 8
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wucltui: Index: 9
> > 2005-03-08 11:24:49-0000 1564 82c Section name: wups: Index: 10
> > 2005-03-08 11:24:49-0000 1564 82c Section name: winhttp: Index: 11
> > 2005-03-08 11:24:49-0000 1564 82c Required Version for binary
> > C:\WINDOWS\system32\cdm.dll is: 5,5,3790,2182
> > 2005-03-08 11:24:49-0000 1564 82c Binary: C:\WINDOWS\system32\cdm.dll:
> > Target version: 0.0.0.0 Required: 5.5.3790.2182
> > 2005-03-08 11:24:49-0000 1564 82c Required Version for binary

> ...
> > C:\WINDOWS\system32\wups.dll is: 5,4,3790,2182
> > 2005-03-08 11:24:49-0000 1564 82c Binary:
> > C:\WINDOWS\system32\wups.dll: Target version: 0.0.0.0 Required:
> > 5.4.3790.2182

>
> Notice all the "Target version: 0.0.0.0" I suspect that this is a quirky
> way of telling us that a module was not found.
>
>
> > 2005-03-08 11:25:15-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co.../XP/en/cdm.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\cdm.cab
> > 2005-03-08 11:25:15-0000 1564 884 Local CAB
> > C:\WINDOWS\SoftwareDistribution\WebSetup\iuengine. cab will be used
> > 2005-03-08 11:25:36-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...P/en/wuapi.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuapi.cab
> > 2005-03-08 11:25:49-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...n/wuauclt1.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauclt1. cab
> > 2005-03-08 11:27:12-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...en/wuaueng.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng.c ab
> > 2005-03-08 11:27:32-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...n/wuaueng1.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuaueng1. cab
> > 2005-03-08 11:27:35-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...n/wuauserv.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wuauserv. cab
> > 2005-03-08 11:27:44-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...en/wucltui.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wucltui.c ab
> > 2005-03-08 11:27:50-0000 1564 884 WinInet: Successfully downloaded
> > http://v5.windowsupdate.microsoft.co...XP/en/wups.cab
> > to file C:\WINDOWS\SoftwareDistribution\WebSetup\wups.cab

>
> It might be interesting to drill down to all those .cab files and open
> them up to verify that they contain what we think that they should contain
> ---e.g. replacement modules for all the ones that you deleted,
> especially replacement modules for the ones above which showed
> that "Target version: 0.0.0.0" that I previously commented on
> and which should have versions equal to the stated "Required version".
>
>
> > 2005-03-08 11:27:50-0000 1564 884 Starting File operations for section
> > cdm
> > 2005-03-08 11:27:50-0000 1564 884 Target file
> > C:\WINDOWS\system32\cdm.dll doesn't exist
> > 2005-03-08 11:27:50-0000 1564 884 File operations for section cdm
> > completed successfully

> ...
> > 2005-03-08 11:27:52-0000 1564 884 Starting File operations for section
> > wups
> > 2005-03-08 11:27:52-0000 1564 884 Target file
> > C:\WINDOWS\system32\wups.dll doesn't exist
> > 2005-03-08 11:27:52-0000 1564 884 File operations for section wups
> > completed successfully

>
> I think that there is a lot of ambiguity in those messages.
> What "file operations" "completed successfully"?
> Proving that the file doesn't exist?
> (Hopefully) extracting each from its respective .cab file
> and copying it to its proper System directories?
> Something intermediate?
> Again, monitoring with FileMon would clarify what these
> messages really are summarizing and again, after the fact,
> you may be able to check manually what has been done.
>
>
> > 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> > section cdm..
> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> > for section cdm: status 0
> > 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> > section iuengine..
> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> > for section iuengine: status 0
> > 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> > section wuapi..
> > 2005-03-08 11:27:52-0000 1564 884 Registration:
> > C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuapi.dll"
> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> > for section wuapi: status 0
> > 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> > section wuauclt1..
> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> > for section wuauclt1: status 0
> > 2005-03-08 11:27:52-0000 1564 884 Starting Registry operations for
> > section wuaueng_WebSetup..
> > 2005-03-08 11:27:52-0000 1564 884 Registration:
> > C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
> > 2005-03-08 11:27:52-0000 1564 884 Registration failed with error
> > 0x80070003
> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> > for section wuaueng_WebSetup: status 0x80070003

>
> So, finally we see the problem. It seems to be a variant of the
> problem that I referred you to with my older thread (the one which
> gave us the idea to try re-registering wuaueng.dll after booting
> in safe mode.) However, since it is a different code it is probably
> more of an error condition than that one was.
>
> In fact, this particular code in the context of WU has often
> been successfully interpreted as a sign that the SoftwareDistribution
> directory was somehow corrupt (or in your case perhaps incompatible
> if you now have newer versions of the modules which you deleted.)
>
> http://groups-beta.google.com/groups...t=0&scoring=d&
>
> (Google Groups search for
> SoftwareDistribution 80070003 OR 0x80070003 MSFT OR MVP group:microsoft.public.windowsupdate
> - sorted by date to capture current thinking on the matter
> )
>
>
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\cdm.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\iuengine.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wuapi.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wuauclt1.exe successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wuaueng.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
> > C:\WINDOWS\help\wuauhelp.chm.wusetup.1241031.bak back to
> > C:\WINDOWS\help\wuauhelp.chm successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Copied
> > C:\WINDOWS\INF\wuau.adm.wusetup.1241250.bak back to
> > C:\WINDOWS\INF\wuau.adm successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wuaueng1.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wuauserv.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wucltui.dll successfully
> > 2005-03-08 11:27:52-0000 1564 884 Rollback: Deleted file
> > C:\WINDOWS\system32\wups.dll successfully

>
> I wonder what else was "rolled back"? <eg>
> It may be difficult for you to diagnose what went wrong
> if everything was deleted before you get a chance to inspect it!
>
>
> > 2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
> > error 0x80070003
> > 2005-03-08 11:27:52-0000 1564 884 InstallUpdatedBinaries failed with
> > error:0x80070003
> > 2005-03-08 11:27:52-0000 1564 884 UpdateClientWorker failed: error
> > 0x80070003"
> > -snip!-
> >
> > Now if I go back to Automatic Updates Service it hangs on startup with
> > the same error as before.

>
> I wouldn't expect the service to run until you get its modules replaced.
> I'm slightly amazed to see that it appears that eventually everything
> which you deleted may be restored so (relatively) automatically.
>
>
> >
> > Again, all help received with thanks
> >
> > RG
> > (WD)

>
>
> Good luck
>
> Robert
> ---



Hi

Thanks for being so thorough - there was a lot to get through.

The Roll-back messages above seem to be mis-leading - the .cab files
all contain what seem to be working and up-to-date copies of the files
Pat had me delete. These seem to have been unpaked to the correct
locations (in system32) and are still resident there - ie not deleted
during some Rollback.

I tried checking the fixes in the link you posted, namely checking the
SoftwareDistribution folders - all seems well; they are folders, I
cleared out the Download and DataStore foldres.

The Registry settings for Program Files etc are as required.

I started to follow the thread about re-registering the .dll and
dependant .dll (the one that has a typo and corrections) all .dll
register OK apart from wuaueng.dll (as per the error log from Windows
Update above) so I guess this is our focus. The error from RegSvr32
is 'LoadLibruary("wuaueng.dll") failed - The Specified module could
not be found'

This is by running up a CMD in System 32 and regsvr32 wuaueng.dll -
unless I have got that wrong or in the wrong location.

All else remains the same - Windows Update returns 80070420 error
(because I have changed AU Service to manual to allow access to wu*
..dll files) and with the service running (but never leaving the
'Starting' status) with error 'did not start in a timely fashion' WU
tries to download the new version - the WU log shows that it is happy
with the .cab files downloaded the other day but fails on the regsvr32
function as above.

Thanks for continued help, regards

RG
(WD)

I'm not aware of the file
 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      03-13-2005
"WD" <W.D.@dickthebuilder.com> wrote in message
news: om
....

WD,

There seems to be a contradiction in your last description.
On the one hand the wuaueng.dll exists:

>> It might be interesting to drill down to all those .cab files and open
>> them up to verify that they contain what we think that they should contain
>> ---e.g. replacement modules for all the ones that you deleted,

....
> The Roll-back messages above seem to be mis-leading - the .cab files
> all contain what seem to be working and up-to-date copies of the files
> Pat had me delete. These seem to have been unpaked to the correct
> locations (in system32) and are still resident there - ie not deleted
> during some Rollback.



On the other hand wuaueng.dll doesn't exist:

>> > C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
>> > 2005-03-08 11:27:52-0000 1564 884 Registration failed with error
>> > 0x80070003
>> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
>> > for section wuaueng_WebSetup: status 0x80070003

>>
>> So, finally we see the problem. It seems to be a variant of the
>> problem that I referred you to with my older thread (the one which
>> gave us the idea to try re-registering wuaueng.dll after booting
>> in safe mode.) However, since it is a different code it is probably
>> more of an error condition than that one was.

....
> The error from RegSvr32 is 'LoadLibruary("wuaueng.dll") failed
> - The Specified module could not be found'
>
> This is by running up a CMD in System 32 and regsvr32 wuaueng.dll -
> unless I have got that wrong or in the wrong location.



If the module is in System32 and you are positioned there
(i.e., the current directory is that) then that command should
work; otherwise you could give it a complete path specification
and run the command from anywhere. Sometimes it is easier
just to Run... the command (e.g. press Win-R and enter it
in the Run... dialog since it seems to have a larger set of
paths to execute from than even the PATH shell variable.)

Also, was there a code besides that message?
A code could signal that the missing module
is a *dependent* module of the module that you are
trying to register. E.g. compare the distinction
between "...GetLastError returns 0x00000485"
and "...GetLastError returns 0x000000002"
in this article:

<title>KB249873 - Explanation of Regsvr32 Usage and Error Messages</title>


While you are there in your cmd window in System32
please enter the following command and capture
the results: dir wuau*
so we are clearer about what you actually have installed
still, in spite of all those "misleading" rollback messages.


If everything still seems OK and regsvr32 wuaueng.dll
is still failing please try doing it in safe mode too
the way that poster hixcks discovered helped with
a similar problem (link available in my first reply to this
thread).


Good luck

Robert
---



 
Reply With Quote
 
WD
Guest
Posts: n/a

 
      03-14-2005
Hi

C:\WINDOWS\system32>dir wuau*
Volume in drive C has no label.
Volume Serial Number is E454-D829

Directory of C:\WINDOWS\system32

03/08/2004 13:02 113,944 wuauclt.exe
03/08/2004 14:01 167,704 wuauclt1.exe
03/08/2004 13:03 167,704 wuaucpl.cpl
03/08/2004 13:07 1,081,112 wuaueng.dll
03/08/2004 14:03 186,136 wuaueng1.dll
03/08/2004 23:56 6,656 wuauserv.dll
6 File(s) 1,723,256 bytes
0 Dir(s) 45,334,650,880 bytes free

I booted to safe mode - and went back to basics - doing :
REGSVR32 /u atl.dll
REGSVR32 /u wuapi.dll
REGSVR32 /u wuaueng.dll
REGSVR32 /u wucltui.dll
REGSVR32 /u wups.dll

REGSVR32 atl.dll
REGSVR32 wuapi.dll
REGSVR32 wuaueng.dll
REGSVR32 wucltui.dll
REGSVR32 wups.dll

all fine *except* wuaueng.dll <-- same error as in normal mode;
pop-up from 'RegSvr32' with the error [LoadLibruary("wuaueng.dll")
failed - The specified module could not be found.] No other error of
GetLastError info.

I wonder if it is a dependant file that is missing .? How do I check
..? I will prob have to get some tools so download points for those
gratefully recieved also

RG
(WD)


"Robert Aldwinckle" <> wrote in message news:<Oy#74e#>...
> "WD" <W.D.@dickthebuilder.com> wrote in message
> news: om
> ...
>
> WD,
>
> There seems to be a contradiction in your last description.
> On the one hand the wuaueng.dll exists:
>
> >> It might be interesting to drill down to all those .cab files and open
> >> them up to verify that they contain what we think that they should contain
> >> ---e.g. replacement modules for all the ones that you deleted,

> ...
> > The Roll-back messages above seem to be mis-leading - the .cab files
> > all contain what seem to be working and up-to-date copies of the files
> > Pat had me delete. These seem to have been unpaked to the correct
> > locations (in system32) and are still resident there - ie not deleted
> > during some Rollback.

>
>
> On the other hand wuaueng.dll doesn't exist:
>
> >> > C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wuaueng.dll"
> >> > 2005-03-08 11:27:52-0000 1564 884 Registration failed with error
> >> > 0x80070003
> >> > 2005-03-08 11:27:52-0000 1564 884 Completed registration operations
> >> > for section wuaueng_WebSetup: status 0x80070003
> >>
> >> So, finally we see the problem. It seems to be a variant of the
> >> problem that I referred you to with my older thread (the one which
> >> gave us the idea to try re-registering wuaueng.dll after booting
> >> in safe mode.) However, since it is a different code it is probably
> >> more of an error condition than that one was.

> ...
> > The error from RegSvr32 is 'LoadLibruary("wuaueng.dll") failed
> > - The Specified module could not be found'
> >
> > This is by running up a CMD in System 32 and regsvr32 wuaueng.dll -
> > unless I have got that wrong or in the wrong location.

>
>
> If the module is in System32 and you are positioned there
> (i.e., the current directory is that) then that command should
> work; otherwise you could give it a complete path specification
> and run the command from anywhere. Sometimes it is easier
> just to Run... the command (e.g. press Win-R and enter it
> in the Run... dialog since it seems to have a larger set of
> paths to execute from than even the PATH shell variable.)
>
> Also, was there a code besides that message?
> A code could signal that the missing module
> is a *dependent* module of the module that you are
> trying to register. E.g. compare the distinction
> between "...GetLastError returns 0x00000485"
> and "...GetLastError returns 0x000000002"
> in this article:
>
> <title>KB249873 - Explanation of Regsvr32 Usage and Error Messages</title>
>
>
> While you are there in your cmd window in System32
> please enter the following command and capture
> the results: dir wuau*
> so we are clearer about what you actually have installed
> still, in spite of all those "misleading" rollback messages.
>
>
> If everything still seems OK and regsvr32 wuaueng.dll
> is still failing please try doing it in safe mode too
> the way that poster hixcks discovered helped with
> a similar problem (link available in my first reply to this
> thread).
>
>
> Good luck
>
> Robert
> ---

 
Reply With Quote
 
Robert Aldwinckle
Guest
Posts: n/a

 
      03-14-2005
"WD" <W.D.@dickthebuilder.com> wrote in message
news: om...
> Hi
>
> C:\WINDOWS\system32>dir wuau*
> Volume in drive C has no label.
> Volume Serial Number is E454-D829
>
> Directory of C:\WINDOWS\system32
>
> 03/08/2004 13:02 113,944 wuauclt.exe
> 03/08/2004 14:01 167,704 wuauclt1.exe
> 03/08/2004 13:03 167,704 wuaucpl.cpl
> 03/08/2004 13:07 1,081,112 wuaueng.dll
> 03/08/2004 14:03 186,136 wuaueng1.dll
> 03/08/2004 23:56 6,656 wuauserv.dll
> 6 File(s) 1,723,256 bytes
> 0 Dir(s) 45,334,650,880 bytes free


There's a discrepancy in there it may be worthwhile investigating.
Both of the dependent(?) modules, e.g. wuau*1.* have timestamps
which are 1 hour out from mine. If they also have different versions
associated with them then that could be sufficient to cause your
symptom. OTOH it might only be due to localization. Mine are all
en-us.

If you have the Support Tools installed you would have a tool called
filever which can give more detailed information about executables.

E.g. you could then supplement the above information with the output
from:

filever wuau*1.* /v

Actually, it would probably be more useful to compare the two pairs
separately. E.g. for the one we think you are having trouble with:

filever wuaueng*.* /v

Unfortunately, the tool doesn't list the timestamp (just the date)
so to capture the modification time at the same time try:

dir/tw wuaueng*.*

Note that I don't know if this will yield anything significant or not.
E.g. what we saw in your log prior to rollback showed consistency
in version at least for these modules. Thinking about it now,
it almost has to be something at an even lower level of module.


>
> I booted to safe mode - and went back to basics - doing :
> REGSVR32 /u atl.dll
> REGSVR32 /u wuapi.dll
> REGSVR32 /u wuaueng.dll
> REGSVR32 /u wucltui.dll
> REGSVR32 /u wups.dll
>
> REGSVR32 atl.dll
> REGSVR32 wuapi.dll
> REGSVR32 wuaueng.dll
> REGSVR32 wucltui.dll
> REGSVR32 wups.dll
>
> all fine *except* wuaueng.dll <-- same error as in normal mode;
> pop-up from 'RegSvr32' with the error [LoadLibruary("wuaueng.dll")
> failed - The specified module could not be found.] No other error of
> GetLastError info.


Well then let's check if there's something odd about your regsvr32
command:

filever regsvr32.exe /v


>
> I wonder if it is a dependant file that is missing .? How do I check
> .? I will prob have to get some tools so download points for those
> gratefully recieved also


Also in the Support Tools package is Dependency Walker (depends.exe)
You can also get it from www.dependencywalker.com
I have just noticed that it has a profiling feature which might be ideal
for detecting what your problem is. This is just a heads up about the
option. I'll have to try it myself to learn how to use it. <g>

Wow! There is a FAQ there which exactly deals with your problem.

<quote>
The best way to debug a module that fails to register is by opening
REGSVR32.EXE in Dependency Walker rather than your DLL.
</quote>

Again, this is a heads up for something that I haven't experimented with
yet myself.


BTW in case you don't have the Support Tools package on your CD,
(and I am still very unclear about XP Home's status for this) you could try
the download implied by this article: KB838079

Another tool which could be useful for seeing cross-module dependencies
in action is FileMon (freeware from SysInternals.)


Good luck

Robert
---


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Automatic Updates Service stuck in "Starting" Status Stan Smiley Windows Update 6 09-24-2009 01:37 PM
Event Log Service Problems Not Starting AU Windows Vista General Discussion 11 02-23-2007 12:29 AM
Windows Automatic Update Service Problem CLW Windows Update 0 10-18-2004 01:58 PM
Windows Update v5 problem:Starting Automatic Update service Ottoman Windows Update 7 08-24-2004 07:59 AM
Windows Automatic Update Service Pack 4 Restart Required Vinay Windows Update 0 09-10-2003 03:24 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59