KB835732 produce event 256 on startup

[Richard Manson]

Hi,

Since I installed the MS04-011 hotfix (KB835732 ) I get errors in the
application event log at startup.

At boot-up, I get 5 times the following event :
EventID 256, source : PlugPlayManager and the description says :
Timed out sending notification of device interface change to window of ""

My computers are running Windows 2000 SP3 and SP4. It is Compaq Deskpro
EN/866 and Dell Gx150 or Gx260.

I observe this behavior on 1/3rd of the patched computers.
Same computers build using exactly the same master image can exhibit this
problem or not. They have strictly the same hardware and using the same
software will not respond to the patch in a different way. Weird.

How to track down the origin for the problem ? Perhaps this is caused by a
driver which needs to be updated to function correctly with the new patch.
But how to pinpoint it ?

Thanks for any input.

--Richard.

 

[Ruud Van Clem]

Hi,

Since I installed the MS04-011 hotfix (KB835732 ) I get errors in the
application event log at startup.

At boot-up, I get 5 times the following event :
EventID 256, source : PlugPlayManager and the description says :
Timed out sending notification of device interface change to window of ""

My computers are running Windows 2000 SP3 and SP4. It is Compaq Deskpro
EN/866 and Dell Gx150 or Gx260.

I observe this behavior on 1/3rd of the patched computers.
Same computers build using exactly the same master image can exhibit this
problem or not. They have strictly the same hardware and using the same
software will not respond to the patch in a different way. Weird.

How to track down the origin for the problem ? Perhaps this is caused by a
driver which needs to be updated to function correctly with the new patch.
But how to pinpoint it ?

Thanks for any input.

--Richard.

I have a similar problem. After some testing, I think the problem (on my pc)
is due to an incompatibility
between the KB835732 update and the soundcard driver (Sound Blaster PCI128)
from Creative.

 

[hlanier]

Try removing the network cards and see if problem goes
away... I am having same problem and this is the only way
I can boot the computer. Have uninstalled KB835732 and
everything works fine.

So How do I tell MSFT that there is a problem with the
upgrade?

 

[Andrew]

My computer was hanging at the log-on screen for almost a
full minute. This is what worked for me, go into Device
Manager, double-click the 'Secondary IDE Channel>Advanced
Settings', and if Device 0 shows that the 'Current
Transfer Mode' is 'Not Available' then change the Device
Type to 'None' and the 'Transfer Mode' to 'PIO Only'.
For some reason the KB835732 security patch causes
multiple 'Time-Outs' to the 'Plug and Play Manager'.
Other users have changed the settings on Device 1 also of
the Secondary IDE Channel with apparent success.

 

[Richard Manson]

"hlanier"

Try removing the network cards and see if problem goes
away... I am having same problem and this is the only way
I can boot the computer. Have uninstalled KB835732 and
everything works fine.

I can hardly test your suggestion : my computers have NIC integrated on the
motherboard (3Com 3C920 or Intel Pro100 or Pro1000) !

But so far, every computer was able to boot after the patch. Except that I
get those message in the event log which makes me a little unconfortable.

So How do I tell MSFT that there is a problem with the
upgrade?

If you get the answer for that question...

--Richard.

 

[Richard Manson]

"Ruud Van Clem"

by

I have a similar problem. After some testing, I think the problem (on my pc)
is due to an incompatibility
between the KB835732 update and the soundcard driver (Sound Blaster PCI128)
from Creative.

I don't have SB PCI128 in any computer. (I guess that each computer is
build around a SoundMax chip, I think).

The trouble is that computers with the same hardware and the same software
(including drivers) may or may not exhibit this error message.
So far I have patched over 900 computers in my company. And a third is
having those error messages in the event log.
That's annoying.

--Richard.

 

[Hans]

Thank's a lot for the Tip, it resolved the Event id 256 problem. (I have had
to change the Device type to "None" only)

Hans