Re:USB and Windows Drivers
When you connect a new USB devise to PC (personal computer), PC searches and installs the appropriate devise driver (mchpusb.sys etc). It would take time for searching and installing the driver for new devise. As PC stores the information (identified by VID/PID) on the driver in its registry-keys etc. at the first connection, you can connect the devise without installing the driver newly after the second connection. You know that the connection-time becomes shorter after the second connection.
If the usage of the same VID/PID were accepted both for mchpusb.sys and hidclass.sys (etc.) in the USB protocol, PC would have to install the appropriated devise driver “every time”. It would be a waste of time. I suppose that this is one of reasons why one VID/PID cannot be used for different devise “drivers” (not devises).
I think that VID is assigned to Microchip and that PIDs are determined by Microchip for its products. We do not have any right to change Microchip’s VID/PID at all. However if you enjoy “personally” USB connections, you can use any combination of VID and PID.
Only for the personal usage:
If you would like to use the VID/PID (which you used for mchpusb.sys) for hidclass.sys, please erase “the registry-key and devise driver " (used for mchpusb.sys) stored in PC.Once you install the HID drive, you cannot use the same VID/PID for mchpusb.sys, though. You should determine for which you use one VID/PID, mchpusb.sys or hidclass.sys.