Prev: Error code 80072EFE
Next: Error Code: 0x13EC WinXP
From: fperez17 on 5 Jan 2008 14:43


"Sudheer GN [MSFT]" wrote:

> Hi,
> 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
> appropriately)
> 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
> http://www.microsoft.com/info/cpyright.htm
>
> "chrisminett" <chrisminett(a)discussions.microsoft.com> wrote in message
> news:9106C3BB-0E42-4F40-BD0B-88529BC99259(a)microsoft.com...
> >
> >
> > "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?
>
>
From: NikkiKavanagh on 14 Jan 2008 10:04
Can anyone help me - I can run my computer and trouble shoot basic problems
but do NOT understand code etc. I cannot install an update although the code
is slightly different to the one this string refers to. The error code I am
getting is:
Update for Windows Vista (KB930857)

Download size: 65 KB

You may need to restart your computer for this update to take effect.

Update type: Important

Install this update to fix an issue with Windows Error Reporting that may
cause some information about application errors to be sent to Microsoft
without notifying you. After you install this item, you may have to restart
your computer.

It says the update is important but hasn't been able to install it since
18th November 2007. I have done everything suggested including he
instructions given here for error 8007000B as it was the closest reference I
could find - but it still won't install. Any ideas would be much
appreciated!!

Thanks,

Nikki Kavanagh

"Sudheer GN [MSFT]" wrote:

> Hi,
> 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
> appropriately)
> 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
> http://www.microsoft.com/info/cpyright.htm
>
> "chrisminett" <chrisminett(a)discussions.microsoft.com> wrote in message
> news:9106C3BB-0E42-4F40-BD0B-88529BC99259(a)microsoft.com...
> >
> >
> > "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?
>
>
From: rizzlePEZZLE on 18 Jan 2008 00:57
hey i had the same problem but that did work i was on xp home but heres how
ifixed it
start > connect to > show all connections
right click the one you sign on the internet and click properties
press tcp/ip then press properties set dns to automatic and press ok
done
agin i searched forever for this so i thought id put it where i first looked!
 | 
Pages: 1
Prev: Error code 80072EFE
Next: Error Code: 0x13EC WinXP