I regret that I am also experiencing the same problem with my Vista Ultimate
since about the 9th January 2008. To date I have 51 failed updates and need
to find a solution as a matter of urgency.
I did try going to All Programs/Accessories/Command Prompt/Run as
When the Command Prompt opened it was showing the following:
I typed in the recommended string but it did not resolve the problem.
I then assumed this was because I had not changed the directory to C: only
which I then did and entered the string "fsutil resource setautoreset C:" as
Rebooted the computer but the updates still refuse to update.
I hope that I have not caused the problem by initially typing the string
into the incorrect location and hope that you are able to assist me in
resolving this problem.
Any assistance would be much appreciated.
"Sudheer GN [MSFT]" wrote:
> We are sorry for issues in installing the updates.
> Can you please follow the instructions below and let me know if it resolves
> the updates failing with 8007000b issue.
> 1. Open an Administrator command prompt by right clicking on Start -> All
> Programs -> Accessories -> Command Prompt and selecting "Run as
> Administrator" and clicking "Allow" for the elevation prompt
> 2. In the command prompt, type the command below
> fsutil resource setautoreset C:
> (This assumes that C: is the drive in which Vista is installed. If it is
> installed on another drive like D:, please change the drive letter
> 3. Reboot the machine
> After reboot, please try to install the updates again and let me know if
> that resolves the issue.
> Sudheer GN
> Microsoft, WU Client
> This posting is provided "As Is" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> "chrisminett" <firstname.lastname@example.org> wrote in message
> > "Robert Aldwinckle" wrote:
> >> What filter were you using? E.g. perhaps try filtering on the program
> >> name which is doing the write to WindowsUpdate.log?
> >> I suspect you are probably chopping off useful context here.
> >> E.g. what was happening just before this?
> > The line before was simply the download process reporting that it had the
> > file OK, followed by a rather long gap in time (abot 0.5 seconds) where
> > the
> > process monitor shows a few thousand entries.
> >> Similarly if you find the write for this record in your ProcMon trace
> >> what was happening before that regarding *other* file accesses
> >> by the same program? Etc.
> > Yeah, the problem is that I can't see anything particularly obviously
> > wrong,
> > and there are so many entries, I'm not really sure where to begin looking
> > anyway.
> >> The rest of this will only be useful to someone who has access
> >> to internal documentation. E.g. that would be where things like
> >> CBS and 106 would be defined and described, as well as the
> >> overall program flow.
> > I did look in the CBS log for the same time, and found a code (possibly
> > error code) which appeared in process monitor for some entries too:
> > 0xc0190005
> > That mean anthing to anyone?