KB892130 Failure: Another Solution

Here is my experience with the KB892130 problem. I was able to defeat
it. I don't know how useful this will be to the rest of you. I hope
that my method works for some of you, at least.

Actually, I will describe four methods that I tried. Only the fourth
method worked for me, but perhaps there are useful clues present here.

Background
----------
The computer is a Dell XPS, 2.5 years old. It uses Windows XP
Professional, and I have applied service pack 2. I have applied all
suggested updates from the "Windows Update" function that is built
into Internet Explorer. Until 2006 February 28, that is. On that day,
Windows Update ceased to function. I detail this in the section
"Method 1," immediately following.

Method 1: Windows Update from Internet Explorer
-----------------------------------------------

This is simply the normal way to access the Microsoft Windows Update
service. From the Tools menu of Internet Explorer (IE), I selected the
Windows Update function. After a bit of work, IE presented a message
stating that a new version of Microsoft's "Genuine Advantage
Validation Tool" was required. IE attempted to install it, but failed.
I read through some of the .log files in my C:\Windows directory after
this. I found words to the effect that there was a problem with
"permissions." I don't remember the details.

Method 2: Running Internet Explorer Under The SYSTEM Account
------------------------------------------------------------

For my next act, I launched IE as a process owned by the SYSTEM user
account. This is generally the maximum privelege account on a Windows
box. I used the utility PsExec (from http://www.sysinternals.com) to
do this.

This also failed. But this time, there was no mention of priveleges in
the latest messages in the .log files, in C:\Windows. Instead, there
was a complaint about a failure to access a certain file oem20.inf.
This was reasonable, since I could find no such file anywhere on my
computer. What I learned from this is that my computer has at least
two different problems with Windows Update: a permissions problem, and
a missing file problem.

Method 3: Transfer Files From A Healthy Computer
------------------------------------------------

I found the KB892130 files on
another computer. On this computer, the KB892130 installation went
flawlessly. I found the files in
c:\windows\SoftwareDistribution\download\8b8c30d92 a5a722c5d42566e03bea22d,
but your mileage will vary. I was careful to preserve the directory
structure. It looked like this:

4 Feb 28 19:13 _downloadprogress_.state*
17 Feb 28 19:13 _file_to_execute_.txt*
34 Feb 28 19:13 _unpacked_.state*
50 Feb 28 19:13 _useselfcontained_.state*
550120 Feb 14 09:20 legitcheckcontrol.dll*
8632 Feb 13 19:03 spmsg.dll*
./update:
710584 Feb 13 19:03 update.exe*
8848 Jan 25 16:35 update.inf*
108 Feb 13 19:03 update.ver*
366008 Feb 13 19:03 updspapi.dll*
7086 Feb 14 09:20 wga.cat*

I put these files in a scratch directory (C:\TEMP, actually) on my
problematic XPS computer. As I said, I preserved the directory structure,
although I don't know if this matters. I executed the file update.exe.
Again, the process failed. I *think* there was a brief message about
permissions, but I'm not sure.

Method 4: Try Again Using The SYSTEM Account
--------------------------------------------

This is what finally worked for me. Once again, I used the utility
program PsExec from Sysinternals. But this time, I used it to execute the
update.exe program. It succeeded!

Conclusion
----------

I don't remember if I rebooted or not. I ran Windows Update from IE,
and it did not try to install KB892130 again. It successfully
installed six patches from Microsoft. What a relief!

I suspect that I still have a permisions problem lurking on my
computer. I don't know if it is a registry key, a file, a directory,
or some combination of these. I expect to make occasional use of
PsExec in the future, too.

Good luck to all of you! I hope to get some feedback and learn from
it.
--
David Arnstein | Have fun with your spams:
arnstein+ | http://www.bluesecurity.com

Thanks for this. Had the KB892130 problem on a valide / clean machine. I
went to download Defender and that validated ok. But when I used IE and
windows update i got an error and installation failed!!

Anyway tried method four, installed fine and i'm getting more updates now!
Weird!!

Not really sure what the problem was but thanks for the insight.

"David Arnstein" wrote:

> Here is my experience with the KB892130 problem. I was able to defeat
> it. I don't know how useful this will be to the rest of you. I hope
> that my method works for some of you, at least.
>
> Actually, I will describe four methods that I tried. Only the fourth
> method worked for me, but perhaps there are useful clues present here.
>
> Background
> ----------
> The computer is a Dell XPS, 2.5 years old. It uses Windows XP
> Professional, and I have applied service pack 2. I have applied all
> suggested updates from the "Windows Update" function that is built
> into Internet Explorer. Until 2006 February 28, that is. On that day,
> Windows Update ceased to function. I detail this in the section
> "Method 1," immediately following.
>
> Method 1: Windows Update from Internet Explorer
> -----------------------------------------------
>
> This is simply the normal way to access the Microsoft Windows Update
> service. From the Tools menu of Internet Explorer (IE), I selected the
> Windows Update function. After a bit of work, IE presented a message
> stating that a new version of Microsoft's "Genuine Advantage
> Validation Tool" was required. IE attempted to install it, but failed.
> I read through some of the .log files in my C:\Windows directory after
> this. I found words to the effect that there was a problem with
> "permissions." I don't remember the details.
>
> Method 2: Running Internet Explorer Under The SYSTEM Account
> ------------------------------------------------------------
>
> For my next act, I launched IE as a process owned by the SYSTEM user
> account. This is generally the maximum privelege account on a Windows
> box. I used the utility PsExec (from http://www.sysinternals.com) to
> do this.
>
> This also failed. But this time, there was no mention of priveleges in
> the latest messages in the .log files, in C:\Windows. Instead, there
> was a complaint about a failure to access a certain file oem20.inf.
> This was reasonable, since I could find no such file anywhere on my
> computer. What I learned from this is that my computer has at least
> two different problems with Windows Update: a permissions problem, and
> a missing file problem.
>
> Method 3: Transfer Files From A Healthy Computer
> ------------------------------------------------
>
> I found the KB892130 files on
> another computer. On this computer, the KB892130 installation went
> flawlessly. I found the files in
> c:\windows\SoftwareDistribution\download\8b8c30d92 a5a722c5d42566e03bea22d,
> but your mileage will vary. I was careful to preserve the directory
> structure. It looked like this:
>
> 4 Feb 28 19:13 _downloadprogress_.state*
> 17 Feb 28 19:13 _file_to_execute_.txt*
> 34 Feb 28 19:13 _unpacked_.state*
> 50 Feb 28 19:13 _useselfcontained_.state*
> 550120 Feb 14 09:20 legitcheckcontrol.dll*
> 8632 Feb 13 19:03 spmsg.dll*
> ./update:
> 710584 Feb 13 19:03 update.exe*
> 8848 Jan 25 16:35 update.inf*
> 108 Feb 13 19:03 update.ver*
> 366008 Feb 13 19:03 updspapi.dll*
> 7086 Feb 14 09:20 wga.cat*
>
> I put these files in a scratch directory (C:\TEMP, actually) on my
> problematic XPS computer. As I said, I preserved the directory structure,
> although I don't know if this matters. I executed the file update.exe.
> Again, the process failed. I *think* there was a brief message about
> permissions, but I'm not sure.
>
> Method 4: Try Again Using The SYSTEM Account
> --------------------------------------------
>
> This is what finally worked for me. Once again, I used the utility
> program PsExec from Sysinternals. But this time, I used it to execute the
> update.exe program. It succeeded!
>
> Conclusion
> ----------
>
> I don't remember if I rebooted or not. I ran Windows Update from IE,
> and it did not try to install KB892130 again. It successfully
> installed six patches from Microsoft. What a relief!
>
> I suspect that I still have a permisions problem lurking on my
> computer. I don't know if it is a registry key, a file, a directory,
> or some combination of these. I expect to make occasional use of
> PsExec in the future, too.
>
> Good luck to all of you! I hope to get some feedback and learn from
> it.
> --
> David Arnstein | Have fun with your spams:
> arnstein+ | http://www.bluesecurity.com
>

On Thu, 2 Mar 2006 07:56:30 -0800, clankk
<> wrote:
>> Method 4: Try Again Using The SYSTEM Account
>> --------------------------------------------
>>
>> This is what finally worked for me. Once again, I used the utility
>> program PsExec from Sysinternals. But this time, I used it to execute the
>> update.exe program. It succeeded!

I downloaded and ran PsExec as follows:

Start
Run
psexec -s update.exe

A DOS window popped up and disappeared immediately - too fast for me
to read what was happening. WU failed again, so I'm probably using
PsExec wrong. Can anyone help?

Thanks, Bill

In article <>,
MrBill <> wrote:
>I downloaded and ran PsExec as follows:
>
>Start
>Run
>psexec -s update.exe

It would probably be best for you to run psexec from a "Command
Prompt" box until you get the hang of it.

If you type
psexec -help
you will get a long list of options for using the program.

There is also information to read at http://www.sysinternals.com,
where you obtained the program (I hope).

In your case, you should type something like
psexec -s -i -d "complete path to update.exe, including drive letter"

For your security, you should get into the habit of understanding what
such a command does, before you execute it. You don't know who I am, I
might be doing something evil!
--
David Arnstein | Have fun with your spams:
arnstein+ | http://www.bluesecurity.com

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

-------------------
On Thu, 2 Mar 2006 17:34:48 +0000 (UTC), (David
Arnstein) wrote:

>In article <>,
>MrBill <> wrote:
>>I downloaded and ran PsExec as follows:
>>
>>Start
>>Run
>>psexec -s update.exe
>
>It would probably be best for you to run psexec from a "Command
>Prompt" box until you get the hang of it.
>
>If you type
> psexec -help
>you will get a long list of options for using the program.
>
>There is also information to read at http://www.sysinternals.com,
>where you obtained the program (I hope).
>
>In your case, you should type something like
> psexec -s -i -d "complete path to update.exe, including drive letter"
>
>For your security, you should get into the habit of understanding what
>such a command does, before you execute it. You don't know who I am, I
>might be doing something evil!

this method worked for me. Thanks MrBill for the simplification and D
Arnstein for the analysis work.

My updates are working again.


"MrBill" wrote:

> 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
>
> -------------------
> On Thu, 2 Mar 2006 17:34:48 +0000 (UTC), (David
> Arnstein) wrote:
>
> >In article <>,
> >MrBill <> wrote:
> >>I downloaded and ran PsExec as follows:
> >>
> >>Start
> >>Run
> >>psexec -s update.exe
> >
> >It would probably be best for you to run psexec from a "Command
> >Prompt" box until you get the hang of it.
> >
> >If you type
> > psexec -help
> >you will get a long list of options for using the program.
> >
> >There is also information to read at http://www.sysinternals.com,
> >where you obtained the program (I hope).
> >
> >In your case, you should type something like
> > psexec -s -i -d "complete path to update.exe, including drive letter"
> >
> >For your security, you should get into the habit of understanding what
> >such a command does, before you execute it. You don't know who I am, I
> >might be doing something evil!
>

Thank you!!
This method also worked for me! Was figuring I had to run it using the
system account and totally forgot about psexec.

"AncientWisdom" wrote:

> this method worked for me. Thanks MrBill for the simplification and D
> Arnstein for the analysis work.
>
> My updates are working again.
>
>
> "MrBill" wrote:
>
> > 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
> >
> > -------------------
> > On Thu, 2 Mar 2006 17:34:48 +0000 (UTC), (David
> > Arnstein) wrote:
> >
> > >In article <>,
> > >MrBill <> wrote:
> > >>I downloaded and ran PsExec as follows:
> > >>
> > >>Start
> > >>Run
> > >>psexec -s update.exe
> > >
> > >It would probably be best for you to run psexec from a "Command
> > >Prompt" box until you get the hang of it.
> > >
> > >If you type
> > > psexec -help
> > >you will get a long list of options for using the program.
> > >
> > >There is also information to read at http://www.sysinternals.com,
> > >where you obtained the program (I hope).
> > >
> > >In your case, you should type something like
> > > psexec -s -i -d "complete path to update.exe, including drive letter"
> > >
> > >For your security, you should get into the habit of understanding what
> > >such a command does, before you execute it. You don't know who I am, I
> > >might be doing something evil!
> >

Thank you Thank you!

Mr Bill, David, you have been the best help! I followed the advice below -
one thing to mention, when entering "psexec -i -s c:\temp\a.exe" into command
prompt, also add the directory you put psexec into - this stumped me for a
while! (it's late).
I dropped psexec into my C drive and ended up with"C:\psexec -i -s
c:\temp\a.exe"
Updating fine again now.
I have, of course, a GENUINE COPY of XP home.

"MrBill" wrote:

> 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
>
> -------------------
> On Thu, 2 Mar 2006 17:34:48 +0000 (UTC), (David
> Arnstein) wrote:
>
> >In article <>,
> >MrBill <> wrote:
> >>I downloaded and ran PsExec as follows:
> >>
> >>Start
> >>Run
> >>psexec -s update.exe
> >
> >It would probably be best for you to run psexec from a "Command
> >Prompt" box until you get the hang of it.
> >
> >If you type
> > psexec -help
> >you will get a long list of options for using the program.
> >
> >There is also information to read at http://www.sysinternals.com,
> >where you obtained the program (I hope).
> >
> >In your case, you should type something like
> > psexec -s -i -d "complete path to update.exe, including drive letter"
> >
> >For your security, you should get into the habit of understanding what
> >such a command does, before you execute it. You don't know who I am, I
> >might be doing something evil!
>

Many,Many, Thanks to David Arnstein, Mr. Bill, and everyone else that posted
their actions to solve this problem! I followed your advise and used psexec
from the command prompt and it worked! Thank you to all.
Marc

"Stretchadams" wrote:

> Thank you Thank you!
>
> Mr Bill, David, you have been the best help! I followed the advice below -
> one thing to mention, when entering "psexec -i -s c:\temp\a.exe" into command
> prompt, also add the directory you put psexec into - this stumped me for a
> while! (it's late).
> I dropped psexec into my C drive and ended up with"C:\psexec -i -s
> c:\temp\a.exe"
> Updating fine again now.
> I have, of course, a GENUINE COPY of XP home.
>
> "MrBill" wrote:
>
> > 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
> >
> > -------------------
> > On Thu, 2 Mar 2006 17:34:48 +0000 (UTC), (David
> > Arnstein) wrote:
> >
> > >In article <>,
> > >MrBill <> wrote:
> > >>I downloaded and ran PsExec as follows:
> > >>
> > >>Start
> > >>Run
> > >>psexec -s update.exe
> > >
> > >It would probably be best for you to run psexec from a "Command
> > >Prompt" box until you get the hang of it.
> > >
> > >If you type
> > > psexec -help
> > >you will get a long list of options for using the program.
> > >
> > >There is also information to read at http://www.sysinternals.com,
> > >where you obtained the program (I hope).
> > >
> > >In your case, you should type something like
> > > psexec -s -i -d "complete path to update.exe, including drive letter"
> > >
> > >For your security, you should get into the habit of understanding what
> > >such a command does, before you execute it. You don't know who I am, I
> > >might be doing something evil!
> >

I have also to say THANK YOU very much to David Arnstein and Mr. Bill, too.

To MS I would like to suggest to provide a German Translation and/or a Link
into the Knowledge Database. It's terrible, if somebody like me, who isn't
much experienced in the English language as well in all the technicals of XP,
to read and read and read the lot of entries in this forum and to find the
right solution.

I have spent more than 5 hours to solve the problem. And think about - time
is money.

Thanks, from XP Home user who can go on with his work!


"MrBill" wrote:

> On Thu, 2 Mar 2006 07:56:30 -0800, clankk
> <> wrote:
> >> Method 4: Try Again Using The SYSTEM Account
> >> --------------------------------------------
> >>
> >> This is what finally worked for me. Once again, I used the utility
> >> program PsExec from Sysinternals. But this time, I used it to execute the
> >> update.exe program. It succeeded!
>
> I downloaded and ran PsExec as follows:
>
> Start
> Run
> psexec -s update.exe
>
> A DOS window popped up and disappeared immediately - too fast for me
> to read what was happening. WU failed again, so I'm probably using
> PsExec wrong. Can anyone help?
>
> Thanks, Bill
>