Event Source: PlugPlayManager
Event ID: 256
Description: Timed out sending notification of device interface change to window of <program or service name and/or GUID.>

Reader Comments

This did not use to happen - only recently begun. Also, just the "" in the message is not informative - shouldn't it have a program or service name? I think this is the reason my initial logon dialog box sits there with an hourglass for a long time before it lets me type in my password. I get a bunch of these at every logon, not just a single one. I want it to go away.

I get the same message, only it is Event ID 257. I cannot find information on it anywhere. I too would like this to go away. I do not believe that there is such a thing as a "warning message that you can safely ignore". I think it is ridiculous that someone would propose such an idea. Would you ignore the service engine soon light in your car, after all it is just a warning. Warnings will soon become errors if left unchecked. sorry for the rant.

Never had this problem before I installed Microsoft security update KB835732, besides the warning in my eventviewer my computer takes also much more time to start up, it's seems to be hanging just before logon, have to wait al least a minut before I can enter my password. Never !!!! switch off plugplaymanager in admistrativetools-services. On my computer I will not be able anymore to logon, it's hanging in logonscreen forever !, also a startup in safemode is than not possible. After removing this Microsoft update everything went back to normal. I'm running windows2K professional.

Recently, Microsoft did several security patches that apparently affected the PlugPlayManager. It is an annoying thing when you reboot and have to wait about 30 seconds to sign onto your machine because of it. If there was a way to disable that warning I would, but I need the application log. Before updates, I had no trouble at all with the application log. They say ignore it. It's ANNOYING. Wish Microsoft would get off their butt and look at their security fixes a little more closely and see what they actually do to the PlugPlayManager instead.

I have a user with the same warning in the event log. The user has problems browsing the internet. Pages take for ever to load. I wonder if it related to this warning message.

On Windows2000 (and perhaps other versions of Windows), MS04-011 (KB835732) released April 2004 might cause this message. Most annoying is that keyboard does not respond for some seconds after a reboot. Seen this for many of my customers. Removing the hotfix fixes the problem (but leaves your computer vulnerable). Hopefully, Microsoft will release another hotfix in the near future. :)

I get Event ID 256 on our w2000 computers (at work) after updating with hotfix MS04-011(KB835732). One solution to this warning is to. Go into device manager | Ide/atapi controller. For Primary and Secondary contollers: Advanced Settings: For any non-existent devices, change Device Type from Auto to None. Reboot after changing both controllers. (ref. http://www.tek-tips.com/gviewthread.cfm/pid/616/qid/825923).

I have the same issue as Ted P. A fresh install and no issues until all the updates are done. Any further news on this?

I don't have this hotfix AND STILL GET THE ERROR. What gives?

If your problem is SoundBlaster PCI128 related - Rolling back the Driver fixed the problem for me. I am using a SoundBlaster 4750 Soundcard without problems before W2K Service Pack 4 - after installing the Service Pack ... the system would hang at the logon screen for as much as 30 seconds, literally filling the Application Log with Message 256 Warnings. Prior to the rollback, I was using Creative Labs PCI128 driver dated December 19, 2002 - which for whatever reason makes the call to the Plug and Play Mangager. Download from Creative Labs Driver dated January 5, 2001 - Note ... you must download two files - the driver library, and the installer. Driver Library ... p128w2k.lib (2,399,215 bytes) Installer ... SBPCI128setupus.exe (2,074,624 bytes) First - Uninstall existing drivers Second - Use the Search Function and find ... sbpci.sys ... file and delete it from all directories where found (I found it in the System32 Folder only). If you do not remove this file, the fix does not work...! I used Winzip 8.1 to extract all files from the two downloaded files into an install directory, and then run ... Setup.exe The system installed on has now went for nearly two weeks without a single warning. We always disable the GamePort with all SoundBlaster Audio cards ... many computers do not have available resources for the specific I/O range for this port. Jim White

wretyhjkl;