Re: WindowsUpdate_80070005 WindowsUpdate_dt000

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



"Robert Aldwinckle" wrote:

"OlsBean" <OlsBean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ECEDF31B-C22F-4272-A1BE-CBBFD56206C1@xxxxxxxxxxxxxxxx
Running Vista X64 Ultimate

I've searched and searched and none of the relevant threads found have
provided a solution to the error I have.


<repost date="Sept 7, 2007">
If the log(s) (including the Event log) aren't giving you enough clues
about what your symptom means you could try running ProcMon
to supplement them.


</repost>


BTW I am surprised that searches for this common code aren't giving
better results on Google Groups. E.g. this search which was to have
demonstrated how to avoid a possible mistake of searching for only unprefixed
hex codes (e.g. you never mentioned 0x80070005 in your post)
and not filtering for threads with answers or helpful threads, didn't show
what I was expecting it could:

(0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*


E.g. I had to add an extra expression to find what I wanted and even
then none of the hits mentioned ProcMon, only FileMon.

http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/385c9dec95e58f01/c75626350e87e559?lnk=st&q=(filemon+OR+procmon)+(0x80070005+OR+80070005)++(MSFT+OR+MVP)++group%3Amicrosoft.*#c75626350e87e559

(Google Groups search for
(filemon OR procmon) (0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*
- sorted by date to try to capture current thinking
)

That post is now over a year old. High time for rediscovery.

BTW the web interface still has it and (to my surprise)
it has even been voted on so it could at least be found more
easily by using that facility's Threads with helpful posts filter.
Admittedly it does help to know about FileMon as a search term... ; )


FYI the excerpt from your log is not helpful because it does not show
the context of the code that you are reporting.


Good luck

Robert Aldwinckle
---




Thank you, the only access denied process I could find while WU was running
is the following;

########################
Sequence: 18002
Date & Time: 13/01/2008 20:04:51
Event Class: Registry
Operation: RegOpenKey
Result: ACCESS DENIED
Path: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based
Servicing\Packages\Package_1_for_KB905866~31bf3856ad364e35~amd64~~6.0.13.0
TID: 3956
Duration: 0.0000096
Desired Access: Read/Write
####################

Not sure how to fix this, not sure if it gives anyone else an insight.

TIA


.

Relevant Pages

  • Re: WindowsUpdate_80070005 WindowsUpdate_dt000
    ... If the log(including the Event log) aren't giving you enough clues ... then none of the hits mentioned ProcMon, ... easily by using that facility's Threads with helpful posts filter. ... Admittedly it does help to know about FileMon as a search term... ...
    (microsoft.public.windowsupdate)
  • Re: XP service pack 2
    ... down and devote some time to it and see what I come up with. ... Robert Aldwinckle wrote: ... discovered that branches.inf had somehow been marked Read-Only ... More generally you could use FileMon ...
    (microsoft.public.windowsupdate)