SOLUTION TO WINDOWS UPDATE PROBLEM

After many attempts to try and correct this problem which too many people
seem to be having I finally found a solution buried in this forum. Thank you
to David Arnstein and Mr Bill. I copied and pasted it on here so people can
see how to do it. Here it is...Oh yeah you need something called psexec which
is sorta a program. YOu can download it from here..
http://www.sysinternals.com/Utilities/PsExec.html
Put the file in your C:\ drive...and follow the directions below. Hope this
works for everyone...I dunno how it works, alls i knows is it works.


YES! Finally something worked. Here's what I did:

- First I downloaded the WGA update executable
http://www.download.windowsupdate.co...82dcea49a0.exe

- I put it into my c:\temp\ folder.
- I renamed it "a.exe" just to cut down on my typing.
- From the command prompt I entered "psexec -i -s c:\temp\a.exe.

This ran successfully, and when I tried the Windows update again I did
NOT get this error and was able to download the rest of the updates
for my OS . . . HALLELUJAH!

Then I rebooted the PC.

Now . . . since I tried just about every fix that was posted in this
news group, I guess I need to sit back and observe just to make sure I
haven't FUBAR'd anything else. But since the reboot went fine, I'm
hopeful that my problems are behind me.

Thanks for the help David!!

- Bill

Thanks doc,David and MrBill......will try all this if MS fail to correct the
problem.

Just a TEENSY little bit of help for those of us who never thought they
would have to use the command prompt, manually 'PUT' a system file into the C
drive or rename an executable........................................ ..

Could you (or some other kind soul) just walkthrough the steps required to
do your clever stuff with this download in computer 'Baby-Talk' for those of
us who can only just about manage to tweak our settings?
I'm not daft , but I have never used a command prompt in my life and,to be
honest,don't even know where to find such a thing or even 'where' to type
this mysterious prompt.....although I've seen something about it on the safe
mode boot screen-I think-(some kind of black screen with mysterious numbers
and a blinking cursor?)

Sorry to be such a klutz.....but I'm sure lots of people are new to these
sort of games...I know I am!
MS ought to just fix it for us really!

Thanks
flo

"doc4life76" wrote:

> After many attempts to try and correct this problem which too many people
> seem to be having I finally found a solution buried in this forum. Thank you
> to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> see how to do it. Here it is...Oh yeah you need something called psexec which
> is sorta a program. YOu can download it from here..
> http://www.sysinternals.com/Utilities/PsExec.html
> Put the file in your C:\ drive...and follow the directions below. Hope this
> works for everyone...I dunno how it works, alls i knows is it works.
>
>
> YES! Finally something worked. Here's what I did:
>
> - First I downloaded the WGA update executable
> http://www.download.windowsupdate.co...82dcea49a0.exe
>
> - I put it into my c:\temp\ folder.
> - I renamed it "a.exe" just to cut down on my typing.
> - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
>
> This ran successfully, and when I tried the Windows update again I did
> NOT get this error and was able to download the rest of the updates
> for my OS . . . HALLELUJAH!
>
> Then I rebooted the PC.
>
> Now . . . since I tried just about every fix that was posted in this
> news group, I guess I need to sit back and observe just to make sure I
> haven't FUBAR'd anything else. But since the reboot went fine, I'm
> hopeful that my problems are behind me.
>
> Thanks for the help David!!
>
> - Bill
>

"floricicia" wrote:

> Thanks doc,David and MrBill......will try all this if MS fail to correct the
> problem.
>
> Just a TEENSY little bit of help for those of us who never thought they
> would have to use the command prompt, manually 'PUT' a system file into the C
> drive or rename an executable........................................ ..
>
> Could you (or some other kind soul) just walkthrough the steps required to
> do your clever stuff with this download in computer 'Baby-Talk' for those of
> us who can only just about manage to tweak our settings?
> I'm not daft , but I have never used a command prompt in my life and,to be
> honest,don't even know where to find such a thing or even 'where' to type
> this mysterious prompt.....although I've seen something about it on the safe
> mode boot screen-I think-(some kind of black screen with mysterious numbers
> and a blinking cursor?)
>
> Sorry to be such a klutz.....but I'm sure lots of people are new to these
> sort of games...I know I am!
> MS ought to just fix it for us really!
>
> Thanks
> flo
>
> "doc4life76" wrote:
>
> > After many attempts to try and correct this problem which too many people
> > seem to be having I finally found a solution buried in this forum. Thank you
> > to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> > see how to do it. Here it is...Oh yeah you need something called psexec which
> > is sorta a program. YOu can download it from here..
> > http://www.sysinternals.com/Utilities/PsExec.html
> > Put the file in your C:\ drive...and follow the directions below. Hope this
> > works for everyone...I dunno how it works, alls i knows is it works.
> >
> >
> > YES! Finally something worked. Here's what I did:
> >
> > - First I downloaded the WGA update executable
> > http://www.download.windowsupdate.co...82dcea49a0.exe
> >
> > - I put it into my c:\temp\ folder.
> > - I renamed it "a.exe" just to cut down on my typing.
> > - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
> >
> > This ran successfully, and when I tried the Windows update again I did
> > NOT get this error and was able to download the rest of the updates
> > for my OS . . . HALLELUJAH!
> >
> > Then I rebooted the PC.
> >
> > Now . . . since I tried just about every fix that was posted in this
> > news group, I guess I need to sit back and observe just to make sure I
> > haven't FUBAR'd anything else. But since the reboot went fine, I'm
> > hopeful that my problems are behind me.
> >
> > Thanks for the help David!!
> >
> > - Bill
> >

I just wanted to thank David Arnstein and Mr Bill. This worked for me.
Everything is fine now.

Thanks again.

"doc4life76" wrote:

> After many attempts to try and correct this problem which too many people
> seem to be having I finally found a solution buried in this forum. Thank you
> to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> see how to do it. Here it is...Oh yeah you need something called psexec which
> is sorta a program. YOu can download it from here..
> http://www.sysinternals.com/Utilities/PsExec.html
> Put the file in your C:\ drive...and follow the directions below. Hope this
> works for everyone...I dunno how it works, alls i knows is it works.
>
>
> YES! Finally something worked. Here's what I did:
>
> - First I downloaded the WGA update executable
> http://www.download.windowsupdate.co...82dcea49a0.exe
>
> - I put it into my c:\temp\ folder.
> - I renamed it "a.exe" just to cut down on my typing.
> - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
>
> This ran successfully, and when I tried the Windows update again I did
> NOT get this error and was able to download the rest of the updates
> for my OS . . . HALLELUJAH!
>
> Then I rebooted the PC.
>
> Now . . . since I tried just about every fix that was posted in this
> news group, I guess I need to sit back and observe just to make sure I
> haven't FUBAR'd anything else. But since the reboot went fine, I'm
> hopeful that my problems are behind me.
>
> Thanks for the help David!!
>
> - Bill
>

doc4life76 wrote:
> After many attempts to try and correct this problem which too many
> people seem to be having I finally found a solution buried in this
> forum. Thank you to David Arnstein and Mr Bill. I copied and
> pasted it on here so people can see how to do it. Here it is...Oh
> yeah you need something called psexec which is sorta a program. YOu
> can download it from here..
> http://www.sysinternals.com/Utilities/PsExec.html
> Put the file in your C:\ drive...and follow the directions below.
> Hope this works for everyone...I dunno how it works, alls i knows
> is it works.
>
>
> YES! Finally something worked. Here's what I did:
>
> - First I downloaded the WGA update executable
> http://www.download.windowsupdate.co...82dcea49a0.exe
>
> - I put it into my c:\temp\ folder.
> - I renamed it "a.exe" just to cut down on my typing.
> - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
>
> This ran successfully, and when I tried the Windows update again I
> did
> NOT get this error and was able to download the rest of the updates
> for my OS . . . HALLELUJAH!
>
> Then I rebooted the PC.
>
> Now . . . since I tried just about every fix that was posted in this
> news group, I guess I need to sit back and observe just to make
> sure I haven't FUBAR'd anything else. But since the reboot went
> fine, I'm
> hopeful that my problems are behind me.
>
> Thanks for the help David!!

So the fix was to run the WGA installation as your system user?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Hi doc-
Presume your 'empty' post above means I should just get on with it and stop
asking silly questions!

: )

flo

"doc4life76" wrote:

>
>
> "floricicia" wrote:
>
> > Thanks doc,David and MrBill......will try all this if MS fail to correct the
> > problem.
> >
> > Just a TEENSY little bit of help for those of us who never thought they
> > would have to use the command prompt, manually 'PUT' a system file into the C
> > drive or rename an executable........................................ ..
> >
> > Could you (or some other kind soul) just walkthrough the steps required to
> > do your clever stuff with this download in computer 'Baby-Talk' for those of
> > us who can only just about manage to tweak our settings?
> > I'm not daft , but I have never used a command prompt in my life and,to be
> > honest,don't even know where to find such a thing or even 'where' to type
> > this mysterious prompt.....although I've seen something about it on the safe
> > mode boot screen-I think-(some kind of black screen with mysterious numbers
> > and a blinking cursor?)
> >
> > Sorry to be such a klutz.....but I'm sure lots of people are new to these
> > sort of games...I know I am!
> > MS ought to just fix it for us really!
> >
> > Thanks
> > flo
> >
> > "doc4life76" wrote:
> >
> > > After many attempts to try and correct this problem which too many people
> > > seem to be having I finally found a solution buried in this forum. Thank you
> > > to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> > > see how to do it. Here it is...Oh yeah you need something called psexec which
> > > is sorta a program. YOu can download it from here..
> > > http://www.sysinternals.com/Utilities/PsExec.html
> > > Put the file in your C:\ drive...and follow the directions below. Hope this
> > > works for everyone...I dunno how it works, alls i knows is it works.
> > >
> > >
> > > YES! Finally something worked. Here's what I did:
> > >
> > > - First I downloaded the WGA update executable
> > > http://www.download.windowsupdate.co...82dcea49a0.exe
> > >
> > > - I put it into my c:\temp\ folder.
> > > - I renamed it "a.exe" just to cut down on my typing.
> > > - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
> > >
> > > This ran successfully, and when I tried the Windows update again I did
> > > NOT get this error and was able to download the rest of the updates
> > > for my OS . . . HALLELUJAH!
> > >
> > > Then I rebooted the PC.
> > >
> > > Now . . . since I tried just about every fix that was posted in this
> > > news group, I guess I need to sit back and observe just to make sure I
> > > haven't FUBAR'd anything else. But since the reboot went fine, I'm
> > > hopeful that my problems are behind me.
> > >
> > > Thanks for the help David!!
> > >
> > > - Bill
> > >

well i actually wrote a long detailed description on what to do..at the end i
was critical of carey the MVP for suggesting we all refomat our
computers...here is an abridged version..
dowload that psexec from that link. save it....and when you do that it will
give you an option of which folder to save to. Remember which folder that is
in. After downloading go to that folder and double click the psexec. I think
its zipped..so it'll give you an option to extract all files which you should
do, and and remember which folder its being extracted to..you can change the
name of the folder. after extracting go to that folder, right click on the
psexec and copy it. then go to my computer, c:\ and paste it over there.
then go through the steps outlined my bill. To go to the command prompt to to
start, programs, acessories, and then you should see the command prompt. type
"cd.." without the quotes and then "cd.." Again. Do that until you see c:\>
When thats all you see type psexec -i -s c:\temp\a.exe Your computer should
do some stuff and then after it did what it did you can close the command
prompt. Now update should run. Take care and good luck!

"floricicia" wrote:

> Thanks doc,David and MrBill......will try all this if MS fail to correct the
> problem.
>
> Just a TEENSY little bit of help for those of us who never thought they
> would have to use the command prompt, manually 'PUT' a system file into the C
> drive or rename an executable........................................ ..
>
> Could you (or some other kind soul) just walkthrough the steps required to
> do your clever stuff with this download in computer 'Baby-Talk' for those of
> us who can only just about manage to tweak our settings?
> I'm not daft , but I have never used a command prompt in my life and,to be
> honest,don't even know where to find such a thing or even 'where' to type
> this mysterious prompt.....although I've seen something about it on the safe
> mode boot screen-I think-(some kind of black screen with mysterious numbers
> and a blinking cursor?)
>
> Sorry to be such a klutz.....but I'm sure lots of people are new to these
> sort of games...I know I am!
> MS ought to just fix it for us really!
>
> Thanks
> flo
>
> "doc4life76" wrote:
>
> > After many attempts to try and correct this problem which too many people
> > seem to be having I finally found a solution buried in this forum. Thank you
> > to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> > see how to do it. Here it is...Oh yeah you need something called psexec which
> > is sorta a program. YOu can download it from here..
> > http://www.sysinternals.com/Utilities/PsExec.html
> > Put the file in your C:\ drive...and follow the directions below. Hope this
> > works for everyone...I dunno how it works, alls i knows is it works.
> >
> >
> > YES! Finally something worked. Here's what I did:
> >
> > - First I downloaded the WGA update executable
> > http://www.download.windowsupdate.co...82dcea49a0.exe
> >
> > - I put it into my c:\temp\ folder.
> > - I renamed it "a.exe" just to cut down on my typing.
> > - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
> >
> > This ran successfully, and when I tried the Windows update again I did
> > NOT get this error and was able to download the rest of the updates
> > for my OS . . . HALLELUJAH!
> >
> > Then I rebooted the PC.
> >
> > Now . . . since I tried just about every fix that was posted in this
> > news group, I guess I need to sit back and observe just to make sure I
> > haven't FUBAR'd anything else. But since the reboot went fine, I'm
> > hopeful that my problems are behind me.
> >
> > Thanks for the help David!!
> >
> > - Bill
> >

Thanks so much for your post. I've had multiple go-arounds with Microsoft
with no solution yet, but your fix solved the problem

"doc4life76" wrote:

> After many attempts to try and correct this problem which too many people
> seem to be having I finally found a solution buried in this forum. Thank you
> to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> see how to do it. Here it is...Oh yeah you need something called psexec which
> is sorta a program. YOu can download it from here..
> http://www.sysinternals.com/Utilities/PsExec.html
> Put the file in your C:\ drive...and follow the directions below. Hope this
> works for everyone...I dunno how it works, alls i knows is it works.
>
>
> YES! Finally something worked. Here's what I did:
>
> - First I downloaded the WGA update executable
> http://www.download.windowsupdate.co...82dcea49a0.exe
>
> - I put it into my c:\temp\ folder.
> - I renamed it "a.exe" just to cut down on my typing.
> - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
>
> This ran successfully, and when I tried the Windows update again I did
> NOT get this error and was able to download the rest of the updates
> for my OS . . . HALLELUJAH!
>
> Then I rebooted the PC.
>
> Now . . . since I tried just about every fix that was posted in this
> news group, I guess I need to sit back and observe just to make sure I
> haven't FUBAR'd anything else. But since the reboot went fine, I'm
> hopeful that my problems are behind me.
>
> Thanks for the help David!!
>
> - Bill
>

In article <>,
Shenan Stanley <> wrote:
>So the fix was to run the WGA installation as your system user?

I posted the original suggestion to use psexec. You can read it in the
thread with subject "KB892130 Failure: Another Solution."

My report gives powerful (but not absolute) evidence that there are at
least two problems that users have with KB892130 installation. The first
problem is the lack of a needed privelege, which is indeed addressed by
running software under the SYSTEM account. But there is another issue
as well:

The install programs downloaded through Internet Explorer break on many
user machines. My evidence of this second claim is that when I launched
IE under the SYSTEM account, the KB892130 installation still failed.
The failure was no longer a matter of priveleges. The log files in
C:\Windows indicated a missing file "oem20.cat."
--
David Arnstein | Have fun with your spams:
arnstein+ | http://www.bluesecurity.com

thanks!!! after hours - and many tries.... this did work - but not being too
computer saavy - it took me a bit to figure out the command line was the DOS
command line found in Windows accessories and not the run command ... but
eventually i figured out enough steps to make this work, following you steps.
again, many thanks ....

"doc4life76" wrote:

> After many attempts to try and correct this problem which too many people
> seem to be having I finally found a solution buried in this forum. Thank you
> to David Arnstein and Mr Bill. I copied and pasted it on here so people can
> see how to do it. Here it is...Oh yeah you need something called psexec which
> is sorta a program. YOu can download it from here..
> http://www.sysinternals.com/Utilities/PsExec.html
> Put the file in your C:\ drive...and follow the directions below. Hope this
> works for everyone...I dunno how it works, alls i knows is it works.
>
>
> YES! Finally something worked. Here's what I did:
>
> - First I downloaded the WGA update executable
> http://www.download.windowsupdate.co...82dcea49a0.exe
>
> - I put it into my c:\temp\ folder.
> - I renamed it "a.exe" just to cut down on my typing.
> - From the command prompt I entered "psexec -i -s c:\temp\a.exe.
>
> This ran successfully, and when I tried the Windows update again I did
> NOT get this error and was able to download the rest of the updates
> for my OS . . . HALLELUJAH!
>
> Then I rebooted the PC.
>
> Now . . . since I tried just about every fix that was posted in this
> news group, I guess I need to sit back and observe just to make sure I
> haven't FUBAR'd anything else. But since the reboot went fine, I'm
> hopeful that my problems are behind me.
>
> Thanks for the help David!!
>
> - Bill
>