Tuesday, March 18, 2008 8:21 AM
doronh
Once not disableable, forever not disableable
One interesting quirk about the PNP_DEVICE_NOT_DISABLEABLE state is that once it has been set and the PnP manager has processed it, the state is sticky. By sticky I mean that even if you attempt to clear this bit on a subsequent IRP_MN_QUERY_PNP_DEVICE_STATE IRP, the PnP manager ignores your changes to this state. This state remains stuck until any of the following occur
- The machine is rebooted and the device is reenumerated
- The device (or any device in its ancestry) is surprise removed
- The device (or any device in its ancestry) is ejected
Anonymous comments are disabled
About doronh
I am an architect is the Device and Storage Technologies team, focusing on how drivers are developed and how driver developers can develop a quality driver that is stable and performant.
Previously (in descending order) I was a developer and technical lead on the KMDF team, architect of the v1.0 Bluetooth stack, and owner of the input stacks. The USB team reported to my manager during the input days so I also have a good working knowledge of the USB core.
