I already have NIVISA installed for my other EasyTools (DMM, Power, ScopeX, and Wave) and all my other devices work fine. The older Easyscope 3.0 for SHS provides a different driver than the later tools (uoword.sys... USB\VID_F4EC&PID_EE38.DeviceDesc="Test Measure Devices Controller").
Regardless, when Windows first negotiates connection with a USB device, it reads the USB configuration descriptors from the device so that it knows which device class it is, power requirements, and its vendor and product IDs. This allows windows to install the proper driver. If they were valid, but Windows didn't have a driver, it would just report as an unknown device (but with valid configuration info).
This device is reported as a malfunctioning device - that it cannot even read the descriptors. In that case, it doesn't have enough information to even load the proper driver.
To add to the mystery, on another PC (Windows 10 laptop), when I put the scope in "Printer" USB mode, it does enumerate properly as a "camera" which would allow a printer to browse and load pictures from it. However, on that same laptop when the scope is in "Computer" USB mode, it presents the same invalid device descriptors.
So, I know its not the physical port (this port is also used for scope compensation and it works fine) and not the cable (I've used two). I think it is really just the very old firmware on the scope. I do have an older Windows 7 laptop with USB 2 ports that I have yet to try.
I guess I'm just looking to see if someone else has one of these and if they've ever connected it to a PC. I'm trying to ascertain the actual capabilities the connection offers, as I understand that the SHS devices do
not support SCPI. If it is only connection to the frankly, dreadful EasyScope 3.0 vintage 2011, I guess it's no big loss.
One final tidbit, the USB host capability of the scope works fine (when a USB mass storage device is plugged into the other A connector).