Vista - Re: Error code 8007000B when trying to install updates

(cross-post added to Vista General)
"Kim Nyberg" <kny@tekla.fi> wrote in message
news:416A3014-9AAC-40F4-AE82-CF49906C8662@microsoft.com...
> Same problem here. I only experience it on my laptop though (32-bit Vista
> Ultimate),
> my 64-bit Vista Ultimate desktop at work has no problems, neither does my
> 32-bit
> Vista Ultimate desktop at home. This is driving me nuts ...
>
> Some relevant log lines (trying to apply KB930857):

....
> 2007-02-07 09:38:35:579 1168 350 DnldMgr *********** DnldMgr: New download
> job [UpdateId = {9E18D463-1862-4636-9461-EED74D92CE73}.100] ***********
> 2007-02-07 09:38:35:582 1168 350 DnldMgr * Queueing update for download
> handler request generation.
> 2007-02-07 09:38:35:582 1168 350 DnldMgr Generating download request for
> update {9E18D463-1862-4636-9461-EED74D92CE73}.100
> 2007-02-07 09:38:35:833 1168 350 Handler Generating request for CBS update
> 9E18D463-1862-4636-9461-EED74D92CE73 in sandbox
> C:\Windows\SoftwareDistribution\Download\288344d10e06b833976013b26a11d979
> 2007-02-07 09:38:35:834 1168 12d0 AU AU checked download status and it
> changed: Downloading is not paused
> 2007-02-07 09:38:35:841 1168 350 Handler Selected payload type is ptExpress
> 2007-02-07 09:38:35:955 1168 350 Handler UH: DpxRestoreJob returned
> 0x80070002

> 2007-02-07 09:38:35:956 1168 350 Handler Detected download state is
> dsHavePackage
> 2007-02-07 09:38:37:398 1168 1240 Handler FATAL: CBS called Error with
> 0x8007000b,


This looks as if the code being reported is a secondary code.
The first code may be a primary code, in which case there are
standard resolutions which you could try.

Try a search?

http://support.microsoft.com/kb/910336

(Live Search for
0x80070002 site:support.microsoft.com
)


That's just the most common suggestion, clear or rename
the SoftwareDistribution folder.


Otherwise, as usual, I think that this log does not show enough detail.
E.g. 0x80070002 may mean file not found but then *which* file is not being found?

http://msdn2.microsoft.com/en-us/library/ms695782.aspx


In order to answer that question I think you would need to activate
verbose logging (ref. KB902093) or, what I would do, run ProcMon
(or FileMon) to see what other file access errors are occurring just before
that log record is written. Note that although ProcMon can show you
AU's log records being written you will still need to *infer* which ones
are which based on the order they are written and their respective sizes.


BTW I don't know how usable ProcMon is with your OS.
Seems it may be?

http://www.microsoft.com/technet/sys...ssmonitor.mspx

(Live Search for
("process monitor" OR procmon) vista
)

Cross-posted to Vista General.


Good luck

Robert Aldwinckle
---

f you are having the same problem I had with updates for windows not
updateing try this.


Click start All programs >Accessories>Right click on Promt Command and
select
"run as Administrator"and click "allow" for the eval prompt
In the command Promt Type "fsutil resource setautoreset true C:\"

Prompt should read "completed successful"
Close/Exit Command promt
Reboot computer
After reboot Open windows Update and reinstall updates again

this is what I got from Microsdoft Support 11/1/2007

And it works


--
Upper-Chick
------------------------------------------------------------------------
Upper-Chick's Profile: http://forums.techarena.in/member.php?userid=34181
View this thread: http://forums.techarena.in/showthread.php?t=676951

http://forums.techarena.in

It worked perfect Thanks man.