search for: 72f380c

...his looks better. Could it be related to the missing libusb.dll? > Agreed that it looks better, but it wouldn't get that far if it didn't have the proper libusb files. > C:\Users\Admin>usbhid-ups.exe -a ups -D > Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c) The last part is what tells us exactly where to look. Incidentally, that means there was another release (v2.6.5-6...) after the version you have. The version string looks like a mess, but it's the "Windows" branch, based on the main NUT v2.6.5 codebase, 5th release (but the 7th Git...

...bhid-ups is still > running). If the server is not running, you can try starting it manually with > one or more "-D" flags to see what is going wrong. Not much here: --------------- C:\Users\Admin>upsdrvctl -DD start Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c 0.000000 If you're not a NUT core developer, chances are that you're told to enable debugging to see why a driver isn't working for you. We're sorry for the confusion, but this is the 'upsdrvctl' wrapper, not the driver you're interested in. Below you'll find one...