This traps a change to the USB device; example: I can plug in a USB printer and it launches usbWhat.vbs. I can also plug in any other USB device and it runs the VBS code.

What happens is that it traps the message but doesn't let it go on. The VBS code is for a USB printer that gets attached. I don't want to handle any other USB device but you plug in a USB drive and the code kicks off but the computer doesn't recognize that the drive is plugged in so it doesn't ready it for use!

In trying to understand this type of code, I read that I need to pass on the changenotify message so that the computer can handle it normally. The problem is that I don't know how to do that. The code above is torn from code used to identify the insertion of a USB drive. I practically stripped it to run the internal VBS code on any USB device that's plugged in.

It would be a success if I can capture the message but also send it along so the computer can process it as normal.