Windows Update Fails - 0x80070005

What do I need to do to fix it? Looks like some registry key, but which
one? Process Monitor just seems to crash the computer so I can't review it
(the thing fill up so fast it's unbelievable).

Here's part of the windowsupdate.log file where it fails:

2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
wuaucpl
2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
section wuaucpl: status 0
2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
wuaueng_WebSetup
2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
section wuaueng_WebSetup: status 0x80070005
2007-07-04 20:41:35 3112 df4 Setup WARNING: Setup failed while processing
registry operations, error = 0x80070005. Rolling back changes.
2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wuauclt.exe.wusetup.137859.bak back to
C:\WINDOWS\system32\wuauclt.exe
2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wuaucpl.cpl.wusetup.138750.bak back to
C:\WINDOWS\system32\wuaucpl.cpl
2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wuaueng.dll.wusetup.139468.bak back to
C:\WINDOWS\system32\wuaueng.dll
2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
C:\WINDOWS\system32\wucltui.dll.wusetup.139656.bak back to
C:\WINDOWS\system32\wucltui.dll
2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
C:\WINDOWS\INF\wuau.adm.wusetup.140312.bak back to C:\WINDOWS\INF\wuau.adm
2007-07-04 20:41:35 1324 e78 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0700) ===========
2007-07-04 20:41:35 1324 e78 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2007-07-04 20:41:35 1324 e78 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2007-07-04 20:41:35 1324 e78 Service *************
2007-07-04 20:41:35 1324 e78 Service ** START ** Service: Service startup
2007-07-04 20:41:35 1324 e78 Service *********
2007-07-04 20:41:35 1324 e78 Agent * WU client version 5.8.0.2469
2007-07-04 20:41:35 1324 e78 Agent * SusClientId =
'e09c44db-4702-4b90-a4d6-cbd6525f0902'
2007-07-04 20:41:35 1324 e78 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2007-07-04 20:41:35 1324 e78 Agent * Access type: No proxy
2007-07-04 20:41:35 1324 e78 Agent * Network state: Connected
2007-07-04 20:41:37 3112 df4 Setup * WARNING: Exit code = 0x80070005
2007-07-04 20:41:37 3112 df4 Setup *********
2007-07-04 20:41:37 3112 df4 Setup ** END ** Setup: Installing client
binaries
2007-07-04 20:41:37 3112 df4 Setup *************
2007-07-04 20:41:37 3112 df4 Setup FATAL: InstallUpdatedBinaries failed with
error 0x80070005
2007-07-04 20:41:37 3112 df4 WUWeb FATAL: InstallUpdatedBinaries failed with
error:0x80070005
2007-07-04 20:41:37 3112 df4 WUWeb FATAL: UpdateClientWorker failed: error
0x80070005
2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing Windows
Update Agent ***********
2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing global
settings cache ***********
2007-07-04 20:42:20 1324 e78 Agent * WSUS server: <NULL>
2007-07-04 20:42:20 1324 e78 Agent * WSUS status server: <NULL>
2007-07-04 20:42:20 1324 e78 Agent * Target group: (Unassigned Computers)
2007-07-04 20:42:20 1324 e78 Agent * Windows Update access disabled: No
2007-07-04 20:42:20 1324 e78 DnldMgr Download manager restoring 0 downloads
2007-07-04 20:42:20 1324 e78 AU ########### AU: Initializing Automatic
Updates ###########
2007-07-04 20:42:20 1324 e78 AU # AU disabled through User preference
2007-07-04 20:42:20 1324 e78 AU # AU is disabled, not initializing any
handlers

David,

What security software is installed [i.e. Spybot, etc.] ?
Please see this: Solving setup errors by using the SubInACL tool to
repair file and registry permissions
http://blogs.msdn.com/astebner/archi...04/739820.aspx

That will reset file and registry ACLs [access control list] by running
SubInACL, but if there is an installed security program that guards the
registry from changes, then the ACLs will be reset by said program.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


David F. wrote:

> What do I need to do to fix it? Looks like some registry key, but which
> one? Process Monitor just seems to crash the computer so I can't review it
> (the thing fill up so fast it's unbelievable).
>
> Here's part of the windowsupdate.log file where it fails:
>
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaucpl
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaucpl: status 0
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaueng_WebSetup
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaueng_WebSetup: status 0x80070005
> 2007-07-04 20:41:35 3112 df4 Setup WARNING: Setup failed while processing
> registry operations, error = 0x80070005. Rolling back changes.
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuauclt.exe.wusetup.137859.bak back to
> C:\WINDOWS\system32\wuauclt.exe
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuaucpl.cpl.wusetup.138750.bak back to
> C:\WINDOWS\system32\wuaucpl.cpl
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuaueng.dll.wusetup.139468.bak back to
> C:\WINDOWS\system32\wuaueng.dll
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wucltui.dll.wusetup.139656.bak back to
> C:\WINDOWS\system32\wucltui.dll
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\INF\wuau.adm.wusetup.140312.bak back to C:\WINDOWS\INF\wuau.adm
> 2007-07-04 20:41:35 1324 e78 Misc =========== Logging initialized (build:
> 5.8.0.2469, tz: -0700) ===========
> 2007-07-04 20:41:35 1324 e78 Misc = Process:
> C:\WINDOWS\System32\svchost.exe
> 2007-07-04 20:41:35 1324 e78 Misc = Module:
> C:\WINDOWS\system32\wuaueng.dll
> 2007-07-04 20:41:35 1324 e78 Service *************
> 2007-07-04 20:41:35 1324 e78 Service ** START ** Service: Service startup
> 2007-07-04 20:41:35 1324 e78 Service *********
> 2007-07-04 20:41:35 1324 e78 Agent * WU client version 5.8.0.2469
> 2007-07-04 20:41:35 1324 e78 Agent * SusClientId =
> 'e09c44db-4702-4b90-a4d6-cbd6525f0902'
> 2007-07-04 20:41:35 1324 e78 Agent * Base directory:
> C:\WINDOWS\SoftwareDistribution
> 2007-07-04 20:41:35 1324 e78 Agent * Access type: No proxy
> 2007-07-04 20:41:35 1324 e78 Agent * Network state: Connected
> 2007-07-04 20:41:37 3112 df4 Setup * WARNING: Exit code = 0x80070005
> 2007-07-04 20:41:37 3112 df4 Setup *********
> 2007-07-04 20:41:37 3112 df4 Setup ** END ** Setup: Installing client
> binaries
> 2007-07-04 20:41:37 3112 df4 Setup *************
> 2007-07-04 20:41:37 3112 df4 Setup FATAL: InstallUpdatedBinaries failed with
> error 0x80070005
> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: InstallUpdatedBinaries failed with
> error:0x80070005
> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: UpdateClientWorker failed: error
> 0x80070005
> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing Windows
> Update Agent ***********
> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing global
> settings cache ***********
> 2007-07-04 20:42:20 1324 e78 Agent * WSUS server: <NULL>
> 2007-07-04 20:42:20 1324 e78 Agent * WSUS status server: <NULL>
> 2007-07-04 20:42:20 1324 e78 Agent * Target group: (Unassigned Computers)
> 2007-07-04 20:42:20 1324 e78 Agent * Windows Update access disabled: No
> 2007-07-04 20:42:20 1324 e78 DnldMgr Download manager restoring 0 downloads
> 2007-07-04 20:42:20 1324 e78 AU ########### AU: Initializing Automatic
> Updates ###########
> 2007-07-04 20:42:20 1324 e78 AU # AU disabled through User preference
> 2007-07-04 20:42:20 1324 e78 AU # AU is disabled, not initializing any
> handlers
>
>

"David F." <> wrote in message
news:...
> What do I need to do to fix it? Looks like some registry key, but which
> one? Process Monitor just seems to crash the computer so I can't review it
> (the thing fill up so fast it's unbelievable).


If you're only using ProcMon to try to capture registry accesses and don't have
a controlled scenario to monitor, RegMon might be a better tool.
E.g. with RegMon when you set a filter it actually excludes records from being
captured, instead of just excluding records from being seen.

Also, if ProcMon is crashing the computer it may be useful to know
the version of it. FWIW I think that the latest version does that more
frequently than an earlier version.

BTW there is a newsgroup which discusses those tools:
news:microsoft.public.winternals


>
> Here's part of the windowsupdate.log file where it fails:
>
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaucpl
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaucpl: status 0
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaueng_WebSetup
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaueng_WebSetup: status 0x80070005


RegMon would show you the key to which write access is inhibited.


FYI

Robert Aldwinckle
---

RegMon showed access denied for a key something.Update (and next to it was
something.Update.1) - I wrote it down, but I can't find it on all these
papers I have on my desk (I hate that). Anyway, it didn't fix the Windows
Update, but I was able to use Microsoft Update (had to sign on as admin, if
right click and run IE from my sign-on as admin, it wouldn't work). So
Windows Update still doesn't work but Microsoft Update does.

"MowGreen [MVP]" <> wrote in message
news:%23iFslr$...
> David,
>
> What security software is installed [i.e. Spybot, etc.] ?
> Please see this: Solving setup errors by using the SubInACL tool to repair
> file and registry permissions
> http://blogs.msdn.com/astebner/archi...04/739820.aspx
>
> That will reset file and registry ACLs [access control list] by running
> SubInACL, but if there is an installed security program that guards the
> registry from changes, then the ACLs will be reset by said program.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> David F. wrote:
>
>> What do I need to do to fix it? Looks like some registry key, but which
>> one? Process Monitor just seems to crash the computer so I can't review
>> it (the thing fill up so fast it's unbelievable).
>>
>> Here's part of the windowsupdate.log file where it fails:
>>
>> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
>> section wuaucpl
>> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
>> section wuaucpl: status 0
>> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
>> section wuaueng_WebSetup
>> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
>> section wuaueng_WebSetup: status 0x80070005
>> 2007-07-04 20:41:35 3112 df4 Setup WARNING: Setup failed while processing
>> registry operations, error = 0x80070005. Rolling back changes.
>> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
>> C:\WINDOWS\system32\wuauclt.exe.wusetup.137859.bak back to
>> C:\WINDOWS\system32\wuauclt.exe
>> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
>> C:\WINDOWS\system32\wuaucpl.cpl.wusetup.138750.bak back to
>> C:\WINDOWS\system32\wuaucpl.cpl
>> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
>> C:\WINDOWS\system32\wuaueng.dll.wusetup.139468.bak back to
>> C:\WINDOWS\system32\wuaueng.dll
>> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
>> C:\WINDOWS\system32\wucltui.dll.wusetup.139656.bak back to
>> C:\WINDOWS\system32\wucltui.dll
>> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
>> C:\WINDOWS\INF\wuau.adm.wusetup.140312.bak back to
>> C:\WINDOWS\INF\wuau.adm
>> 2007-07-04 20:41:35 1324 e78 Misc =========== Logging initialized
>> (build: 5.8.0.2469, tz: -0700) ===========
>> 2007-07-04 20:41:35 1324 e78 Misc = Process:
>> C:\WINDOWS\System32\svchost.exe
>> 2007-07-04 20:41:35 1324 e78 Misc = Module:
>> C:\WINDOWS\system32\wuaueng.dll
>> 2007-07-04 20:41:35 1324 e78 Service *************
>> 2007-07-04 20:41:35 1324 e78 Service ** START ** Service: Service
>> startup
>> 2007-07-04 20:41:35 1324 e78 Service *********
>> 2007-07-04 20:41:35 1324 e78 Agent * WU client version 5.8.0.2469
>> 2007-07-04 20:41:35 1324 e78 Agent * SusClientId =
>> 'e09c44db-4702-4b90-a4d6-cbd6525f0902'
>> 2007-07-04 20:41:35 1324 e78 Agent * Base directory:
>> C:\WINDOWS\SoftwareDistribution
>> 2007-07-04 20:41:35 1324 e78 Agent * Access type: No proxy
>> 2007-07-04 20:41:35 1324 e78 Agent * Network state: Connected
>> 2007-07-04 20:41:37 3112 df4 Setup * WARNING: Exit code = 0x80070005
>> 2007-07-04 20:41:37 3112 df4 Setup *********
>> 2007-07-04 20:41:37 3112 df4 Setup ** END ** Setup: Installing client
>> binaries
>> 2007-07-04 20:41:37 3112 df4 Setup *************
>> 2007-07-04 20:41:37 3112 df4 Setup FATAL: InstallUpdatedBinaries failed
>> with error 0x80070005
>> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: InstallUpdatedBinaries failed
>> with error:0x80070005
>> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: UpdateClientWorker failed:
>> error 0x80070005
>> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing
>> Windows Update Agent ***********
>> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing
>> global settings cache ***********
>> 2007-07-04 20:42:20 1324 e78 Agent * WSUS server: <NULL>
>> 2007-07-04 20:42:20 1324 e78 Agent * WSUS status server: <NULL>
>> 2007-07-04 20:42:20 1324 e78 Agent * Target group: (Unassigned
>> Computers)
>> 2007-07-04 20:42:20 1324 e78 Agent * Windows Update access disabled: No
>> 2007-07-04 20:42:20 1324 e78 DnldMgr Download manager restoring 0
>> downloads
>> 2007-07-04 20:42:20 1324 e78 AU ########### AU: Initializing Automatic
>> Updates ###########
>> 2007-07-04 20:42:20 1324 e78 AU # AU disabled through User preference
>> 2007-07-04 20:42:20 1324 e78 AU # AU is disabled, not initializing any
>> handlers
>>
>>
>

It was the latest version - I never had a problem with the older versions
I've used. I did end up using regmon. thanks.

"Robert Aldwinckle" <> wrote in message
news:...
> "David F." <> wrote in message
> news:...
>> What do I need to do to fix it? Looks like some registry key, but which
>> one? Process Monitor just seems to crash the computer so I can't review
>> it
>> (the thing fill up so fast it's unbelievable).
>
>
> If you're only using ProcMon to try to capture registry accesses and don't
> have
> a controlled scenario to monitor, RegMon might be a better tool.
> E.g. with RegMon when you set a filter it actually excludes records from
> being
> captured, instead of just excluding records from being seen.
>
> Also, if ProcMon is crashing the computer it may be useful to know
> the version of it. FWIW I think that the latest version does that more
> frequently than an earlier version.
>
> BTW there is a newsgroup which discusses those tools:
> news:microsoft.public.winternals
>
>
>>
>> Here's part of the windowsupdate.log file where it fails:
>>
>> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
>> section
>> wuaucpl
>> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
>> section wuaucpl: status 0
>> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
>> section
>> wuaueng_WebSetup
>> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
>> section wuaueng_WebSetup: status 0x80070005
>
>
> RegMon would show you the key to which write access is inhibited.
>
>
> FYI
>
> Robert Aldwinckle
> ---
>
>
>

I ran into this on a couple of occasions (today for instance) and what has
worked for me was resetting the permissions on the automatic updates service
using sc.exe. I'm not sure how it gets into this state but somehow the
permissions get screwed up and the local system doesnt have rights to stop
and start the service. Anyway, take a healthy machine (same os and SP) and
run sc.exe sdshow wuauserv >file.txt. This will spit out a long acl string
to the file. Take the file move it to the machine with the problem and run
sc.exe sdset wuauserv "acl string from file" for example:
sc.exe sdset wuauserv
DA;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLO CRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRP WPDTLOCRRC;;;PU)

hope this helps
"David F." wrote:

> What do I need to do to fix it? Looks like some registry key, but which
> one? Process Monitor just seems to crash the computer so I can't review it
> (the thing fill up so fast it's unbelievable).
>
> Here's part of the windowsupdate.log file where it fails:
>
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaucpl
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaucpl: status 0
> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for section
> wuaueng_WebSetup
> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> section wuaueng_WebSetup: status 0x80070005
> 2007-07-04 20:41:35 3112 df4 Setup WARNING: Setup failed while processing
> registry operations, error = 0x80070005. Rolling back changes.
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuauclt.exe.wusetup.137859.bak back to
> C:\WINDOWS\system32\wuauclt.exe
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuaucpl.cpl.wusetup.138750.bak back to
> C:\WINDOWS\system32\wuaucpl.cpl
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wuaueng.dll.wusetup.139468.bak back to
> C:\WINDOWS\system32\wuaueng.dll
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\system32\wucltui.dll.wusetup.139656.bak back to
> C:\WINDOWS\system32\wucltui.dll
> 2007-07-04 20:41:35 3112 df4 Setup Rollback: Successfully copied
> C:\WINDOWS\INF\wuau.adm.wusetup.140312.bak back to C:\WINDOWS\INF\wuau.adm
> 2007-07-04 20:41:35 1324 e78 Misc =========== Logging initialized (build:
> 5.8.0.2469, tz: -0700) ===========
> 2007-07-04 20:41:35 1324 e78 Misc = Process:
> C:\WINDOWS\System32\svchost.exe
> 2007-07-04 20:41:35 1324 e78 Misc = Module:
> C:\WINDOWS\system32\wuaueng.dll
> 2007-07-04 20:41:35 1324 e78 Service *************
> 2007-07-04 20:41:35 1324 e78 Service ** START ** Service: Service startup
> 2007-07-04 20:41:35 1324 e78 Service *********
> 2007-07-04 20:41:35 1324 e78 Agent * WU client version 5.8.0.2469
> 2007-07-04 20:41:35 1324 e78 Agent * SusClientId =
> 'e09c44db-4702-4b90-a4d6-cbd6525f0902'
> 2007-07-04 20:41:35 1324 e78 Agent * Base directory:
> C:\WINDOWS\SoftwareDistribution
> 2007-07-04 20:41:35 1324 e78 Agent * Access type: No proxy
> 2007-07-04 20:41:35 1324 e78 Agent * Network state: Connected
> 2007-07-04 20:41:37 3112 df4 Setup * WARNING: Exit code = 0x80070005
> 2007-07-04 20:41:37 3112 df4 Setup *********
> 2007-07-04 20:41:37 3112 df4 Setup ** END ** Setup: Installing client
> binaries
> 2007-07-04 20:41:37 3112 df4 Setup *************
> 2007-07-04 20:41:37 3112 df4 Setup FATAL: InstallUpdatedBinaries failed with
> error 0x80070005
> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: InstallUpdatedBinaries failed with
> error:0x80070005
> 2007-07-04 20:41:37 3112 df4 WUWeb FATAL: UpdateClientWorker failed: error
> 0x80070005
> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing Windows
> Update Agent ***********
> 2007-07-04 20:42:20 1324 e78 Agent *********** Agent: Initializing global
> settings cache ***********
> 2007-07-04 20:42:20 1324 e78 Agent * WSUS server: <NULL>
> 2007-07-04 20:42:20 1324 e78 Agent * WSUS status server: <NULL>
> 2007-07-04 20:42:20 1324 e78 Agent * Target group: (Unassigned Computers)
> 2007-07-04 20:42:20 1324 e78 Agent * Windows Update access disabled: No
> 2007-07-04 20:42:20 1324 e78 DnldMgr Download manager restoring 0 downloads
> 2007-07-04 20:42:20 1324 e78 AU ########### AU: Initializing Automatic
> Updates ###########
> 2007-07-04 20:42:20 1324 e78 AU # AU disabled through User preference
> 2007-07-04 20:42:20 1324 e78 AU # AU is disabled, not initializing any
> handlers
>
>
>

Hi All,

I would go for process explorer which gives more than file monitor and reg
monitor and another way of comparing registry is using

a) winmerge tool / utility which will compare 2 registry

b) Regsnap tool / utility.

Regards
Sainath

"David F." wrote:

> It was the latest version - I never had a problem with the older versions
> I've used. I did end up using regmon. thanks.
>
> "Robert Aldwinckle" <> wrote in message
> news:...
> > "David F." <> wrote in message
> > news:...
> >> What do I need to do to fix it? Looks like some registry key, but which
> >> one? Process Monitor just seems to crash the computer so I can't review
> >> it
> >> (the thing fill up so fast it's unbelievable).
> >
> >
> > If you're only using ProcMon to try to capture registry accesses and don't
> > have
> > a controlled scenario to monitor, RegMon might be a better tool.
> > E.g. with RegMon when you set a filter it actually excludes records from
> > being
> > captured, instead of just excluding records from being seen.
> >
> > Also, if ProcMon is crashing the computer it may be useful to know
> > the version of it. FWIW I think that the latest version does that more
> > frequently than an earlier version.
> >
> > BTW there is a newsgroup which discusses those tools:
> > news:microsoft.public.winternals
> >
> >
> >>
> >> Here's part of the windowsupdate.log file where it fails:
> >>
> >> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
> >> section
> >> wuaucpl
> >> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> >> section wuaucpl: status 0
> >> 2007-07-04 20:41:35 3112 df4 Setup Starting registry operations for
> >> section
> >> wuaueng_WebSetup
> >> 2007-07-04 20:41:35 3112 df4 Setup Completed registration operations for
> >> section wuaueng_WebSetup: status 0x80070005
> >
> >
> > RegMon would show you the key to which write access is inhibited.
> >
> >
> > FYI
> >
> > Robert Aldwinckle
> > ---
> >
> >
> >
>
>
>

"Sainath , SMB KID" <> wrote in message
news:16A72132-DC78-41ED-A33F-...
> Hi All,
>

> I would go for process explorer which gives more than file monitor and reg monitor


Typo? ; ) ProcMon has those features not ProcExp.


---