I have an interesting problem. We have a filter driver that attaches to the
storage stack using UpperFilters of the Volume class. This is/has been
working for years now. During QA testing they use DriveImage/Ghost to image
these systems. When they restore an image onto a “new” hard drive, the
AddDevice routine is not called until you reboot after this message “Windows
has detected new hardware and needs to reboot your computer to use it”
(paraphrased). After the reboot AddDevice is called again.
My guess is since this is a new volume Windows hasn’t associated it with the
volume class yet thus the reason it asks for the reboot. Since this is a
likely scenario is there a way to get our driver attached to these newly
found devices?
Thanks,
Rob