Prev: KB898461 consistently fails to install
Next: Error details: Code 80072EFE
From: Robert Aldwinckle on 27 Jan 2010 17:40

"Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:7ED786C0-28C2-4E90-A9AA-63432E909797(a)microsoft.com...
> Hello Roebert. I still do NOT have any KB logs for the 923561 in the windows
> directy. there is alot of other log files there but NONE for KB923561! I am
> sorry!


Then I suggest running it again with a /verbose option
and monitoring what it's doing with ProcMon because
there *should* be a KB923561.log in your %windir%.

In any case running ProcMon would give you some clue
about the code 2 you are getting.


Good luck

Robert
---


>
>
>
> "Robert Aldwinckle" wrote:
>
>>
>> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:B82A1D6F-43B2-42AF-8B25-0ABBE7D7F99A(a)microsoft.com...
>> > Hello RObert.
>> >
>> > I tried to install the file manually. I download the file from clicking on
>> > the link lon the update and found the DOWNLOAD button. I saved it to my hard
>> > drive and ran it. It came up wiht an error that said it cant find a file,
>> > but it did NOT say WHAT file. I did not try the other problematic update
>> > yet. I am just trying one at a time.
>>
>>
>> Then WindowsUpdate.log will now be irrelevant
>> and you will now have KB logs to look at.
>> In addition you may find that you can invoke verbose logging
>> for the manual installs.
>>
>>
>> >
>> > The Verbose Tracing i checked the registrey according to that KB number you
>> > sent and there is NO TRACE entry. So i researched that and found on another
>> > ms page that it was common.. then it said that since it wasnt there to
>> > register the files again. Which i did. and tried the MANUAL install again.
>>
>>
>> If you are trying a manual install the WU log verbose or not will be irrelevant
>> to your new symptoms.
>>
>>
>>
>> > Same thing.. Missing file! :-(
>>
>>
>> Look in the KB logs.
>>
>>
>> Good luck
>>
>> Robert
>> ---
>>
>>
>> >
>> > Thank you for your help!
>> >
>> > Sincerely,
>> > L.K.
>> >
>> >
>> >
>> >
>> >
>> > "Robert Aldwinckle" wrote:
>> >
>> >>
>> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:A490895C-24C8-4658-B6B6-EC4678982D18(a)microsoft.com...
>> >>
>> >> > I rebooted the pc.. and
>> >> > tried the updates again this time ONE at a time.. I still get the Error
>> >> > Code: 0x80070002.
>> >> >
>> >>
>> >> > There ARE NO "KBxxxxxxx.log" files in the main windows folder either for
>> >> > the two updates in question. There are there for the other ones that were
>> >> > successfully updated a few days back.
>> >> >
>> >> > There is however, a "WindowsUpdate.log" and the last few lines on that
>> >> > file, for the present time and date shows this:
>> >> >
>> >> > "Failure Content Install Installation Failure: Windows failed to install the
>> >> > following update with error 0x80070002: Security Update for Windows XP
>> >> > (KB973904)."
>> >>
>> >>
>> >> That's not enough detail. Your code means
>> >> The system cannot find the file specified.
>> >> So you need to figure out *which* file. To do that you could try running
>> >> ProcMon to supplement whatever diagnostics you are getting.
>> >> It might also help then to activate verbose logging for WU (ref. KB902093)
>> >>
>> >> However, if you just want to get the updates installed, do them manually.
>> >> E.g. the fact that you don't have any install logs to look at means
>> >> that your updating is failing during the download phase and indicates
>> >> some kind of problem with AU/WU.
>> >>
>> >>
>> >> Good luck
>> >>
>> >> Robert Aldwinckle
>> >> ---
>> >>
>> >>
>> >> .
>> >>
>>
>>
>> .
>>


From: Leona K. on 28 Jan 2010 03:09
Good Morning PA BEAR!

We last downloaded updates back in October JUST before halloween. And i
think i recall having the problem then too with these two. Not sure if it was
the SAME ones. The HISTORY has since been clean. But i do remeber having
probloems with two!.

As far as SP3 that was installed even prior to that like back during
summer time or when ever i dont remeber exactly but it is for sure that it
WAS before trying the halloween updates.. SO that is why i thought THAT is
what could be the problem.

I apogolize if my original posts are lenghty for one to want to skip over
it.. . but i wanted to make sure i was coovering all the detials.. I did
mentioin in my second post what i was running for Anti mallware and superspy
programs all uptodate... I did not mention that i was running Mcafee as welll
and that is ALSO uptodate. I am not running any third party firewall. I
hope that answers your question this time! :-)

I have already started a request form the other day too!.. I am just
waiting for them to reply.. They already gave me a list of stuff to do and i
tired it all taking one step at a time and still no luck. So i responded
back to her as per her request and now i am just waiting for her reply
back!.

Sincerely

Leona K







"PA Bear [MS MVP]" wrote:

> >>> I just tried update my windows XP HOME SP3 system yesterday. There was
> >>> quite a few of them i installed...
>
> How long has it been since you last installed updates? Did you install SP3
> the other day, too?
>
> What anti-virus application or security suite is installed and is your
> subscription current? What anti-spyware applications (other than Defender)?
> What third-party firewall (if any)?
>
> Has a(another) Norton or McAfee application ever been installed on the
> computer (e.g., a free-trial version that came preinstalled when you bought
> it)?
>
> The above notwithstanding, you could always open a free support incident.
> See the "How to obtain help" section of, e.g.,
> http://support.microsoft.com/kb/973904
>
>
> Leona K. wrote:
> > To personally respond in regards to the workaround for the 923561 issue.
> > I
> > did not install or perform any previous workaround. There was never an
> > issue that has ever risen to make one want to do any workaround. All of
> > the
> > updates are done right on the MS UPDATE website.
> >
> > But for all intent and purpose, I did what that notice said about the
> > various lines to enter in the command prompt and that ALSO did NOT work.
> > After doing that i tried to do the 923561 again and still error.
> >
> > "PA Bear [MS MVP]" wrote:
> >> Error message when you use the Windows Update Web site or Microsoft
> >> Update
> >> Web site to install updates: "0x80070002"
> >> http://support.microsoft.com/kb/956698
> >>
> >> How do I reset Windows Update components?:
> >> http://support.microsoft.com/kb/971058
> >>
> >> See the Known Issues section of http://support.microsoft.com/kb/923561
> >> (April 2009): Any chance you put that workaround in place after reading
> >> the
> >> related Security Advisory (960906)?
> >>
> >> The above notwithstanding...
> >>
> >> See the "How to obtain help" section of, e.g.,
> >> http://support.microsoft.com/kb/973904
> >>
> >> For home users, no-charge support is available by calling 1-866-PCSAFETY
> >> and/or 1-866-234-6020 in the United States and in Canada or by contacting
> >> your local Microsoft subsidiary. There is no-charge for support calls
> >> that
> >> are associated with security updates. When you call, clearly state that
> >> your problem is related to a Security Update and cite the update's KB
> >> number (e.g., KB973904).
> >>
> >> Or you can...
> >>
> >> Start a free Windows Update support incident request:
> >> https://support.microsoft.com/oas/default.aspx?gprid=6527
> >>
> >> Consumer Security Support home page includes links for free security
> >> update
> >> support, too
> >> https://consumersecuritysupport.microsoft.com/
> >>
> >> For more information about how to contact your local Microsoft subsidiary
> >> for security update support issues, visit the International Support Web
> >> site: http://support.microsoft.com/common/international.aspx
> >>
> >> For enterprise customers, support for security updates is available
> >> through
> >> your usual support contacts.
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-IE, Mail, Security, Windows Client - since 2002
> >> www.banthecheck.com
> >>
> >>
> >> Leona K. wrote:
> >>> I just tried update my windows XP HOME SP3 system yesterday. There
> >>> was
> >>> quite a few of them i installed.. but I noticed when i tried to install
> >>> the
> >>> two mention in the subject. I get all sorts of issues. AAt first
> >>> yesterdasy after downloading it was saying CANCELLED.
> >>>
> >>> I have been doing alot of research for this problem all yesterday and
> >>> tried
> >>> everything i read.. From renaming the system distribution folder..
> >>> catroots. to reregister the update system files (for example the wups
> >>> and
> >>> wups2. etc etc) just as the MS websitre said to when i was getting the
> >>> cancelling error.
> >>>
> >>> Now I been trying all morning and still can NOT get them to sintall. I
> >>> get
> >>> FAILED ERROR.. with that 80070002 error. Thats when i did the renaming
> >>> of
> >>> the folder and rtreied again!.. Yes i stopped the AUTOMATIC UPDATES
> >>> first
> >>> in the services section prior to renaming the folders. The folder
> >>> would
> >>> come back and then it still wouldnt NOT install.
>
> .
>
From: Leona K. on 28 Jan 2010 04:13
Robert, I ran procmon (process monitor) as you suggested. and i noticed
that when i run the KB923561 update that it seems to narchive itself to
the E: drive partition. Now that kinda struck me odd. So i used explorer
and ran it again and sure enough ti could see the archive folder set up
andthen delete itself after the process ended dure to error. I didnt know
why it would use the E: drive. I never set any settings in it to use E
drive.. so i was curious on why that did that..

Now correct me if i am wrong, but i DID research on that and found that
Windows automacially uses the drive that has the MOST amount a free space to
unarchive and install the updates.. in which my case is the E drive?! Am i
correct to eblive that is the case?!

i dontknwo if thats the case why i get the missing file error .. but on the
procmon ijt seems that it cant find ANY of the unrchived files.. but it seems
that it is SUCCESSFUL according to the Procmon log when the KB update is
trying to install it shows some successfull entrys.

L.K.

"Robert Aldwinckle" wrote:

>
> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:7ED786C0-28C2-4E90-A9AA-63432E909797(a)microsoft.com...
> > Hello Roebert. I still do NOT have any KB logs for the 923561 in the windows
> > directy. there is alot of other log files there but NONE for KB923561! I am
> > sorry!
>
>
> Then I suggest running it again with a /verbose option
> and monitoring what it's doing with ProcMon because
> there *should* be a KB923561.log in your %windir%.
>
> In any case running ProcMon would give you some clue
> about the code 2 you are getting.
>
>
> Good luck
>
> Robert
> ---
>
>
> >
> >
> >
> > "Robert Aldwinckle" wrote:
> >
> >>
> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:B82A1D6F-43B2-42AF-8B25-0ABBE7D7F99A(a)microsoft.com...
> >> > Hello RObert.
> >> >
> >> > I tried to install the file manually. I download the file from clicking on
> >> > the link lon the update and found the DOWNLOAD button. I saved it to my hard
> >> > drive and ran it. It came up wiht an error that said it cant find a file,
> >> > but it did NOT say WHAT file. I did not try the other problematic update
> >> > yet. I am just trying one at a time.
> >>
> >>
> >> Then WindowsUpdate.log will now be irrelevant
> >> and you will now have KB logs to look at.
> >> In addition you may find that you can invoke verbose logging
> >> for the manual installs.
> >>
> >>
> >> >
> >> > The Verbose Tracing i checked the registrey according to that KB number you
> >> > sent and there is NO TRACE entry. So i researched that and found on another
> >> > ms page that it was common.. then it said that since it wasnt there to
> >> > register the files again. Which i did. and tried the MANUAL install again.
> >>
> >>
> >> If you are trying a manual install the WU log verbose or not will be irrelevant
> >> to your new symptoms.
> >>
> >>
> >>
> >> > Same thing.. Missing file! :-(
> >>
> >>
> >> Look in the KB logs.
> >>
> >>
> >> Good luck
> >>
> >> Robert
> >> ---
> >>
> >>
> >> >
> >> > Thank you for your help!
> >> >
> >> > Sincerely,
> >> > L.K.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > "Robert Aldwinckle" wrote:
> >> >
> >> >>
> >> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:A490895C-24C8-4658-B6B6-EC4678982D18(a)microsoft.com...
> >> >>
> >> >> > I rebooted the pc.. and
> >> >> > tried the updates again this time ONE at a time.. I still get the Error
> >> >> > Code: 0x80070002.
> >> >> >
> >> >>
> >> >> > There ARE NO "KBxxxxxxx.log" files in the main windows folder either for
> >> >> > the two updates in question. There are there for the other ones that were
> >> >> > successfully updated a few days back.
> >> >> >
> >> >> > There is however, a "WindowsUpdate.log" and the last few lines on that
> >> >> > file, for the present time and date shows this:
> >> >> >
> >> >> > "Failure Content Install Installation Failure: Windows failed to install the
> >> >> > following update with error 0x80070002: Security Update for Windows XP
> >> >> > (KB973904)."
> >> >>
> >> >>
> >> >> That's not enough detail. Your code means
> >> >> The system cannot find the file specified.
> >> >> So you need to figure out *which* file. To do that you could try running
> >> >> ProcMon to supplement whatever diagnostics you are getting.
> >> >> It might also help then to activate verbose logging for WU (ref. KB902093)
> >> >>
> >> >> However, if you just want to get the updates installed, do them manually.
> >> >> E.g. the fact that you don't have any install logs to look at means
> >> >> that your updating is failing during the download phase and indicates
> >> >> some kind of problem with AU/WU.
> >> >>
> >> >>
> >> >> Good luck
> >> >>
> >> >> Robert Aldwinckle
> >> >> ---
> >> >>
> >> >>
> >> >> .
> >> >>
> >>
> >>
> >> .
> >>
>
>
> .
>
From: Robert Aldwinckle on 28 Jan 2010 11:29
"Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:103E6AAC-9865-41A6-8BFC-27C90827846C(a)microsoft.com...
> Robert, I ran procmon (process monitor) as you suggested. and i noticed
> that when i run the KB923561 update that it seems to narchive itself to
> the E: drive partition. Now that kinda struck me odd. So i used explorer
> and ran it again and sure enough ti could see the archive folder set up
> andthen delete itself after the process ended dure to error. I didnt know
> why it would use the E: drive. I never set any settings in it to use E
> drive.. so i was curious on why that did that..
>
> Now correct me if i am wrong, but i DID research on that and found that
> Windows automacially uses the drive that has the MOST amount a free space to
> unarchive and install the updates.. in which my case is the E drive?! Am i
> correct to eblive that is the case?!


I think that that is what is generally understood, yes.


>
> i dontknwo if thats the case why i get the missing file error .. but on the
> procmon ijt seems that it cant find ANY of the unrchived files.. but it seems
> that it is SUCCESSFUL according to the Procmon log when the KB update is
> trying to install it shows some successfull entrys.


Well, a common related problem is that the install finds a drive that
a user is not authorized to create new directories on. So, I would suspect
you have some kind of permissions issues on that drive. If you can't fix
the permissions issue perhaps you could detach the problem drive or
attach a different one that has more room or even create a large enough
file on the problem drive that it won't get picked any more?

Also, it sounds as if you are getting some kind of message window.
Are you noticing the temporary files being deleted *after* you dismiss
that message window? If so, you may be able to find the extracted
files on the problem drive first and then move them somewhere else
to do the final install super manually. (I have never heard of anybody
having to do this but it seems as if it would be feasible.)


Good luck

Robert
---


>
> L.K.
>
> "Robert Aldwinckle" wrote:
>
>>
>> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:7ED786C0-28C2-4E90-A9AA-63432E909797(a)microsoft.com...
>> > Hello Roebert. I still do NOT have any KB logs for the 923561 in the windows
>> > directy. there is alot of other log files there but NONE for KB923561! I am
>> > sorry!
>>
>>
>> Then I suggest running it again with a /verbose option
>> and monitoring what it's doing with ProcMon because
>> there *should* be a KB923561.log in your %windir%.
>>
>> In any case running ProcMon would give you some clue
>> about the code 2 you are getting.
>>
>>
>> Good luck
>>
>> Robert
>> ---
>>
>>
>> >
>> >
>> >
>> > "Robert Aldwinckle" wrote:
>> >
>> >>
>> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:B82A1D6F-43B2-42AF-8B25-0ABBE7D7F99A(a)microsoft.com...
>> >> > Hello RObert.
>> >> >
>> >> > I tried to install the file manually. I download the file from clicking on
>> >> > the link lon the update and found the DOWNLOAD button. I saved it to my hard
>> >> > drive and ran it. It came up wiht an error that said it cant find a file,
>> >> > but it did NOT say WHAT file. I did not try the other problematic update
>> >> > yet. I am just trying one at a time.
>> >>
>> >>
>> >> Then WindowsUpdate.log will now be irrelevant
>> >> and you will now have KB logs to look at.
>> >> In addition you may find that you can invoke verbose logging
>> >> for the manual installs.
>> >>
>> >>
>> >> >
>> >> > The Verbose Tracing i checked the registrey according to that KB number you
>> >> > sent and there is NO TRACE entry. So i researched that and found on another
>> >> > ms page that it was common.. then it said that since it wasnt there to
>> >> > register the files again. Which i did. and tried the MANUAL install again.
>> >>
>> >>
>> >> If you are trying a manual install the WU log verbose or not will be irrelevant
>> >> to your new symptoms.
>> >>
>> >>
>> >>
>> >> > Same thing.. Missing file! :-(
>> >>
>> >>
>> >> Look in the KB logs.
>> >>
>> >>
>> >> Good luck
>> >>
>> >> Robert
>> >> ---
>> >>
>> >>
>> >> >
>> >> > Thank you for your help!
>> >> >
>> >> > Sincerely,
>> >> > L.K.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Robert Aldwinckle" wrote:
>> >> >
>> >> >>
>> >> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:A490895C-24C8-4658-B6B6-EC4678982D18(a)microsoft.com...
>> >> >>
>> >> >> > I rebooted the pc.. and
>> >> >> > tried the updates again this time ONE at a time.. I still get the Error
>> >> >> > Code: 0x80070002.
>> >> >> >
>> >> >>
>> >> >> > There ARE NO "KBxxxxxxx.log" files in the main windows folder either for
>> >> >> > the two updates in question. There are there for the other ones that were
>> >> >> > successfully updated a few days back.
>> >> >> >
>> >> >> > There is however, a "WindowsUpdate.log" and the last few lines on that
>> >> >> > file, for the present time and date shows this:
>> >> >> >
>> >> >> > "Failure Content Install Installation Failure: Windows failed to install the
>> >> >> > following update with error 0x80070002: Security Update for Windows XP
>> >> >> > (KB973904)."
>> >> >>
>> >> >>
>> >> >> That's not enough detail. Your code means
>> >> >> The system cannot find the file specified.
>> >> >> So you need to figure out *which* file. To do that you could try running
>> >> >> ProcMon to supplement whatever diagnostics you are getting.
>> >> >> It might also help then to activate verbose logging for WU (ref. KB902093)
>> >> >>
>> >> >> However, if you just want to get the updates installed, do them manually.
>> >> >> E.g. the fact that you don't have any install logs to look at means
>> >> >> that your updating is failing during the download phase and indicates
>> >> >> some kind of problem with AU/WU.
>> >> >>
>> >> >>
>> >> >> Good luck
>> >> >>
>> >> >> Robert Aldwinckle
>> >> >> ---
>> >> >>
>> >> >>
>> >> >> .
>> >> >>
>> >>
>> >>
>> >> .
>> >>
>>
>>
>> .
>>


From: Leona K. on 29 Jan 2010 03:06
Hello Robert,

I understand you are saying that it could be a drive access issue.. but let
me ask you. If that was the case then why did all the other updates install
wiht no problem?! it seems that the only two i am having a problem with is
the ones that have somethine to do with WORD converters.

I seriously do not think the issue is wiht the drive space either as the two
partitions on this HDD is over 100 gigs each!, with only a little of each
even being used.

I do not know what else to do right now. I am also still waiting for Annie
from the support place to reply but it has been like 4 days now!. She gave
me steps to take i printed themout and i performed them and then sent back
the results to her.. upon her request and i havent heard back :(




"Robert Aldwinckle" wrote:

> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:103E6AAC-9865-41A6-8BFC-27C90827846C(a)microsoft.com...
> > Robert, I ran procmon (process monitor) as you suggested. and i noticed
> > that when i run the KB923561 update that it seems to narchive itself to
> > the E: drive partition. Now that kinda struck me odd. So i used explorer
> > and ran it again and sure enough ti could see the archive folder set up
> > andthen delete itself after the process ended dure to error. I didnt know
> > why it would use the E: drive. I never set any settings in it to use E
> > drive.. so i was curious on why that did that..
> >
> > Now correct me if i am wrong, but i DID research on that and found that
> > Windows automacially uses the drive that has the MOST amount a free space to
> > unarchive and install the updates.. in which my case is the E drive?! Am i
> > correct to eblive that is the case?!
>
>
> I think that that is what is generally understood, yes.
>
>
> >
> > i dontknwo if thats the case why i get the missing file error .. but on the
> > procmon ijt seems that it cant find ANY of the unrchived files.. but it seems
> > that it is SUCCESSFUL according to the Procmon log when the KB update is
> > trying to install it shows some successfull entrys.
>
>
> Well, a common related problem is that the install finds a drive that
> a user is not authorized to create new directories on. So, I would suspect
> you have some kind of permissions issues on that drive. If you can't fix
> the permissions issue perhaps you could detach the problem drive or
> attach a different one that has more room or even create a large enough
> file on the problem drive that it won't get picked any more?
>
> Also, it sounds as if you are getting some kind of message window.
> Are you noticing the temporary files being deleted *after* you dismiss
> that message window? If so, you may be able to find the extracted
> files on the problem drive first and then move them somewhere else
> to do the final install super manually. (I have never heard of anybody
> having to do this but it seems as if it would be feasible.)
>
>
> Good luck
>
> Robert
> ---
>
>
> >
> > L.K.
> >
> > "Robert Aldwinckle" wrote:
> >
> >>
> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:7ED786C0-28C2-4E90-A9AA-63432E909797(a)microsoft.com...
> >> > Hello Roebert. I still do NOT have any KB logs for the 923561 in the windows
> >> > directy. there is alot of other log files there but NONE for KB923561! I am
> >> > sorry!
> >>
> >>
> >> Then I suggest running it again with a /verbose option
> >> and monitoring what it's doing with ProcMon because
> >> there *should* be a KB923561.log in your %windir%.
> >>
> >> In any case running ProcMon would give you some clue
> >> about the code 2 you are getting.
> >>
> >>
> >> Good luck
> >>
> >> Robert
> >> ---
> >>
> >>
> >> >
> >> >
> >> >
> >> > "Robert Aldwinckle" wrote:
> >> >
> >> >>
> >> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:B82A1D6F-43B2-42AF-8B25-0ABBE7D7F99A(a)microsoft.com...
> >> >> > Hello RObert.
> >> >> >
> >> >> > I tried to install the file manually. I download the file from clicking on
> >> >> > the link lon the update and found the DOWNLOAD button. I saved it to my hard
> >> >> > drive and ran it. It came up wiht an error that said it cant find a file,
> >> >> > but it did NOT say WHAT file. I did not try the other problematic update
> >> >> > yet. I am just trying one at a time.
> >> >>
> >> >>
> >> >> Then WindowsUpdate.log will now be irrelevant
> >> >> and you will now have KB logs to look at.
> >> >> In addition you may find that you can invoke verbose logging
> >> >> for the manual installs.
> >> >>
> >> >>
> >> >> >
> >> >> > The Verbose Tracing i checked the registrey according to that KB number you
> >> >> > sent and there is NO TRACE entry. So i researched that and found on another
> >> >> > ms page that it was common.. then it said that since it wasnt there to
> >> >> > register the files again. Which i did. and tried the MANUAL install again.
> >> >>
> >> >>
> >> >> If you are trying a manual install the WU log verbose or not will be irrelevant
> >> >> to your new symptoms.
> >> >>
> >> >>
> >> >>
> >> >> > Same thing.. Missing file! :-(
> >> >>
> >> >>
> >> >> Look in the KB logs.
> >> >>
> >> >>
> >> >> Good luck
> >> >>
> >> >> Robert
> >> >> ---
> >> >>
> >> >>
> >> >> >
> >> >> > Thank you for your help!
> >> >> >
> >> >> > Sincerely,
> >> >> > L.K.
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > "Robert Aldwinckle" wrote:
> >> >> >
> >> >> >>
> >> >> >> "Leona K." <LeonaK(a)discussions.microsoft.com> wrote in message news:A490895C-24C8-4658-B6B6-EC4678982D18(a)microsoft.com...
> >> >> >>
> >> >> >> > I rebooted the pc.. and
> >> >> >> > tried the updates again this time ONE at a time.. I still get the Error
> >> >> >> > Code: 0x80070002.
> >> >> >> >
> >> >> >>
> >> >> >> > There ARE NO "KBxxxxxxx.log" files in the main windows folder either for
> >> >> >> > the two updates in question. There are there for the other ones that were
> >> >> >> > successfully updated a few days back.
> >> >> >> >
> >> >> >> > There is however, a "WindowsUpdate.log" and the last few lines on that
> >> >> >> > file, for the present time and date shows this:
> >> >> >> >
> >> >> >> > "Failure Content Install Installation Failure: Windows failed to install the
> >> >> >> > following update with error 0x80070002: Security Update for Windows XP
> >> >> >> > (KB973904)."
> >> >> >>
> >> >> >>
> >> >> >> That's not enough detail. Your code means
> >> >> >> The system cannot find the file specified.
> >> >> >> So you need to figure out *which* file. To do that you could try running
> >> >> >> ProcMon to supplement whatever diagnostics you are getting.
> >> >> >> It might also help then to activate verbose logging for WU (ref. KB902093)
> >> >> >>
> >> >> >> However, if you just want to get the updates installed, do them manually.
> >> >> >> E.g. the fact that you don't have any install logs to look at means
> >> >> >> that your updating is failing during the download phase and indicates
> >> >> >> some kind of problem with AU/WU.
> >> >> >>
> >> >> >>
> >> >> >> Good luck
> >> >> >>
> >> >> >> Robert Aldwinckle
> >> >> >> ---
> >> >> >>
> >> >> >>
> >> >> >> .
> >> >> >>
> >> >>
> >> >>
> >> >> .
> >> >>
> >>
> >>
> >> .
> >>
>
>
> .
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: KB898461 consistently fails to install
Next: Error details: Code 80072EFE