KB920872 update

I too am having problems with this update continually trying to install after
several previous installations. I tried rebooting, cancelling but nothing
works. On the update history page it shows I've installed this update
several times.
Microsoft needs to fix this for us...please.

I'm having the same exact issue ---- running xp with sp2. First time I've
EVER had any problems whatsoever with auto-updates from MS. It's getting
stuck on the very first update and just hangs. I have to hard reboot.

"PCnerd" wrote:

> I too am having problems with this update continually trying to install after
> several previous installations. I tried rebooting, cancelling but nothing
> works. On the update history page it shows I've installed this update
> several times.
> Microsoft needs to fix this for us...please.

Update for Windows XP (KB920872) is constantly re-installing itself. It's
been installed on my pc like 10 times now. I have had the same problems as
the previous posters. MS needs to fix this ASAP plz.

"PCnerd" wrote:

> I too am having problems with this update continually trying to install after
> several previous installations. I tried rebooting, cancelling but nothing
> works. On the update history page it shows I've installed this update
> several times.
> Microsoft needs to fix this for us...please.

Yes i´ve been having this as well since the fist time I installed it.
Keeps returning, and have done that 5 times now.

"PCnerd" wrote:

> I too am having problems with this update continually trying to install after
> several previous installations. I tried rebooting, cancelling but nothing
> works. On the update history page it shows I've installed this update
> several times.
> Microsoft needs to fix this for us...please.

Hi,



The most common cause for this is that you have an OEM PC on which the PC
manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys drivers as
unsigned. Update.exe will treat these drivers as OEM drivers and not
overwrite them. Please try the following:





1. Download the update from
http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
and save to their C: drive

2. Click on the Start/Run

3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK



Thank you


Eric

"PCnerd" <> wrote in message
news:2FF1E7B5-BF8A-48D5-9DCF-...
>I too am having problems with this update continually trying to install
>after
> several previous installations. I tried rebooting, cancelling but nothing
> works. On the update history page it shows I've installed this update
> several times.
> Microsoft needs to fix this for us...please.

if in fact the file is overwritten, when checking the file(s) properties
what is the actual creation date of the new file?

"Eric Brodish [MSFT]" <> wrote in message
news:...
> Hi,
>
>
>
> The most common cause for this is that you have an OEM PC on which the PC
> manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys drivers as
> unsigned. Update.exe will treat these drivers as OEM drivers and not
> overwrite them. Please try the following:
>
>
>
>
>
> 1. Download the update from
> http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
> and save to their C: drive
>
> 2. Click on the Start/Run
>
> 3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
>
>
>
> Thank you
>
>
> Eric
>
> "PCnerd" <> wrote in message
> news:2FF1E7B5-BF8A-48D5-9DCF-...
>>I too am having problems with this update continually trying to install
>>after
>> several previous installations. I tried rebooting, cancelling but
>> nothing
>> works. On the update history page it shows I've installed this update
>> several times.
>> Microsoft needs to fix this for us...please.
>
>

I found the date here:
http://support.microsoft.com/?kbid=920872

06/14/2006 is the date for the new files!

"MedRxman" <> wrote in message
news:...
> if in fact the file is overwritten, when checking the file(s) properties
> what is the actual creation date of the new file?
>
> "Eric Brodish [MSFT]" <> wrote in message
> news:...
>> Hi,
>>
>>
>>
>> The most common cause for this is that you have an OEM PC on which the PC
>> manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys drivers
>> as unsigned. Update.exe will treat these drivers as OEM drivers and not
>> overwrite them. Please try the following:
>>
>>
>>
>>
>>
>> 1. Download the update from
>> http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
>> and save to their C: drive
>>
>> 2. Click on the Start/Run
>>
>> 3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
>>
>>
>>
>> Thank you
>>
>>
>> Eric
>>
>> "PCnerd" <> wrote in message
>> news:2FF1E7B5-BF8A-48D5-9DCF-...
>>>I too am having problems with this update continually trying to install
>>>after
>>> several previous installations. I tried rebooting, cancelling but
>>> nothing
>>> works. On the update history page it shows I've installed this update
>>> several times.
>>> Microsoft needs to fix this for us...please.
>>
>>
>
>

Hi,

If you look in the %windir%/KB920872.log and you see errors like:

SetupDiCallClassInstaller in CollectThirdPartyDriversFromDevice Failed with
error: -536870387

Then you are experiencing this issue with unsigned OEM drivers.

Thank you

Eric
"MedRxman" <> wrote in message
news:...
>I found the date here:
> http://support.microsoft.com/?kbid=920872
>
> 06/14/2006 is the date for the new files!
>
> "MedRxman" <> wrote in message
> news:...
>> if in fact the file is overwritten, when checking the file(s) properties
>> what is the actual creation date of the new file?
>>
>> "Eric Brodish [MSFT]" <> wrote in message
>> news:...
>>> Hi,
>>>
>>>
>>>
>>> The most common cause for this is that you have an OEM PC on which the
>>> PC manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys
>>> drivers as unsigned. Update.exe will treat these drivers as OEM drivers
>>> and not overwrite them. Please try the following:
>>>
>>>
>>>
>>>
>>>
>>> 1. Download the update from
>>> http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
>>> and save to their C: drive
>>>
>>> 2. Click on the Start/Run
>>>
>>> 3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
>>>
>>>
>>>
>>> Thank you
>>>
>>>
>>> Eric
>>>
>>> "PCnerd" <> wrote in message
>>> news:2FF1E7B5-BF8A-48D5-9DCF-...
>>>>I too am having problems with this update continually trying to install
>>>>after
>>>> several previous installations. I tried rebooting, cancelling but
>>>> nothing
>>>> works. On the update history page it shows I've installed this update
>>>> several times.
>>>> Microsoft needs to fix this for us...please.
>>>
>>>
>>
>>
>
>

Mr. Brodish:
The "/ o" switch added to the end of the executable file
"WindowsXP-KB920872-x86-ENU" is not valid and prevents installation. Should
the switch be "/overwriteoem" instead? This update is a problem and
Microsoft needs to fix it.

"Eric Brodish [MSFT]" wrote:

> Hi,
>
> If you look in the %windir%/KB920872.log and you see errors like:
>
> SetupDiCallClassInstaller in CollectThirdPartyDriversFromDevice Failed with
> error: -536870387
>
> Then you are experiencing this issue with unsigned OEM drivers.
>
> Thank you
>
> Eric
> "MedRxman" <> wrote in message
> news:...
> >I found the date here:
> > http://support.microsoft.com/?kbid=920872
> >
> > 06/14/2006 is the date for the new files!
> >
> > "MedRxman" <> wrote in message
> > news:...
> >> if in fact the file is overwritten, when checking the file(s) properties
> >> what is the actual creation date of the new file?
> >>
> >> "Eric Brodish [MSFT]" <> wrote in message
> >> news:...
> >>> Hi,
> >>>
> >>>
> >>>
> >>> The most common cause for this is that you have an OEM PC on which the
> >>> PC manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys
> >>> drivers as unsigned. Update.exe will treat these drivers as OEM drivers
> >>> and not overwrite them. Please try the following:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 1. Download the update from
> >>> http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
> >>> and save to their C: drive
> >>>
> >>> 2. Click on the Start/Run
> >>>
> >>> 3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
> >>>
> >>>
> >>>
> >>> Thank you
> >>>
> >>>
> >>> Eric
> >>>
> >>> "PCnerd" <> wrote in message
> >>> news:2FF1E7B5-BF8A-48D5-9DCF-...
> >>>>I too am having problems with this update continually trying to install
> >>>>after
> >>>> several previous installations. I tried rebooting, cancelling but
> >>>> nothing
> >>>> works. On the update history page it shows I've installed this update
> >>>> several times.
> >>>> Microsoft needs to fix this for us...please.
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

My mistake. As you know, spacing in a dos command line is everything. I
tried the switch with no space between the "slash" and the "o" and it
installed properly; no more icon indicating an update is needed. Sorry for
the mistake and thanks for the help.

"Eric Brodish [MSFT]" wrote:

> Hi,
>
> If you look in the %windir%/KB920872.log and you see errors like:
>
> SetupDiCallClassInstaller in CollectThirdPartyDriversFromDevice Failed with
> error: -536870387
>
> Then you are experiencing this issue with unsigned OEM drivers.
>
> Thank you
>
> Eric
> "MedRxman" <> wrote in message
> news:...
> >I found the date here:
> > http://support.microsoft.com/?kbid=920872
> >
> > 06/14/2006 is the date for the new files!
> >
> > "MedRxman" <> wrote in message
> > news:...
> >> if in fact the file is overwritten, when checking the file(s) properties
> >> what is the actual creation date of the new file?
> >>
> >> "Eric Brodish [MSFT]" <> wrote in message
> >> news:...
> >>> Hi,
> >>>
> >>>
> >>>
> >>> The most common cause for this is that you have an OEM PC on which the
> >>> PC manufacturer imaged the kmixer.sys, wdmaud.sys and splitter.sys
> >>> drivers as unsigned. Update.exe will treat these drivers as OEM drivers
> >>> and not overwrite them. Please try the following:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 1. Download the update from
> >>> http://www.microsoft.com/downloads/d...n&Hash=7LFJN64
> >>> and save to their C: drive
> >>>
> >>> 2. Click on the Start/Run
> >>>
> >>> 3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
> >>>
> >>>
> >>>
> >>> Thank you
> >>>
> >>>
> >>> Eric
> >>>
> >>> "PCnerd" <> wrote in message
> >>> news:2FF1E7B5-BF8A-48D5-9DCF-...
> >>>>I too am having problems with this update continually trying to install
> >>>>after
> >>>> several previous installations. I tried rebooting, cancelling but
> >>>> nothing
> >>>> works. On the update history page it shows I've installed this update
> >>>> several times.
> >>>> Microsoft needs to fix this for us...please.
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>