Zadig Does not provide a way to restore HIDUSB for devices

[samysousa]

It would be great if Zadig provides a way of rolling back to HIDUSB and Microsoft Original USB Drivers.

[pbatard]

Maybe I'll do that someday. But considering that uninstalling a driver is a feature that can already be achieved with the device manager and my time is exceedingly limited, this is not on top of my priorities for libwdi.

I'll be closing this call request for now, as it's extremely unlikely I will be able to add such a feature in any reasonable timeframe.

[52brandon]

I would LOVE this ability. I need to revert Nanofury ASIC miner back to hidusb from WinUSB to figure out if that's why the Nanofury runs perfect on my laptop and not at all on desktop. So far, that's the only difference between the setup of the 2. I don't dare try updating my laptop to WinUSB instead to see if it stops working because of it, as that would wipe out my only device capable of mining. I'm searching high and low for a way to get WinUSB off and just have hidusb

[pbatard]

The reason why Zadig does not provide this ability, is that it is very easy to uninstall/restore the default Windows driver (HID, Mass Storage, etc.) in Device Manager.

Just locate your device in Device Manager, right click on it, select "Uninstall" and make sure that "Delete the driver software for this device" is checked. Then if you unplug and replug your device, the default Windows driver for it will be reinstalled.

For a step by step guide, please see here.

As such, duplicating a Windows feature that is fairly easy to access doesn't seem like a good investment for the time being. Not to say that I wouldn't like to have it in Zadig, but my development time is limited so I have to prioritize features that are otherwise not made easily available by Windows.

[rtpm]

I'm affraid this does not remove drivers. It reverts back to the previous drivers. In my case it loops between libusb-win32 & libusbK drivers.

WIndows 8.1

[pbatard]

@rtpm Then you're doing it wrong, I guarantee it.
You need to make sure that the checkbox to delete the drivers is checked always, and go through the uninstallation for every USB port where you might have ever plugged the device. You also need to make sure that you unplug the device after the driver has been uninstalled.

I have uninstalled many drivers in Windows 8.1, and I can guarantee that the method highlighted does work just fine. I have never ever seen a WinUSB, libusb-win32 or libusbK driver that couldn't be uninstalled by insisting in the Device Manager.

[gawate]

Hi, sorry to revive such an old topic.
Windows 10 here, I apparently I screwed up whilst playing around with zadig and a RTL2838UHIDIR usb stick, my Logitech g500s mouse is now detected as "HID-compliant mouse". I can guarantee you that there IS no checkbox to check, just a popup saying "Warning: You are about to uninstall this device from your system". I can delete whatever I want, but it comes back like this when I plugin my mouse again / scan for new hardware. I can show you in a TeamViewer session or something like that if you'd like.

[pbatard]

my Logitech g500s mouse is now detected as "HID-compliant mouse"

How is this is not what you want? HID is the driver being used for mice and keyboards. So I really don't see anything wrong here about the HID driver being installed when you plug a mouse. That's what Windows does by default, and has nothing to do with Zadig.

[gawate]

Well, it used to be something like "Logitech G500S Mouse" (it still is on my W7 laptop), and my back- and forward button on the mouse are not working anymore those still work on my W7 laptop). It worked before I started fiddling with Zadig. Don't get me wrong, I knew what I was getting into, and still I screwed up something nevertheless, but more help would be welcome, although I fully understand zadig isn't responsible for my screwing up ;-)
And maybe I'm even linking 2 events together that have no connection (working with zadig vs mouse buttons not working anymore). I wish my restore point could actually be restored...but alas.

OK wtf it is working now...I see 2 HID-compliant mice and a "Logitech G500 Gaming mouse". I can delete the 2 HID..-mice but they come back. Whatever. All I did is take my mouse to work, and connect it again several hours later to my pc. It's not as if I didn't try disconnecting and connecting the mouse before. But this time, it just worked. We'll never know what the problem was, but I'm OK with that ;)

[robertj131]

Hi I updated a driver through zadig for my g502 rgb mouse and the device has stopped working I do not know what to do and was wondering if you could come into teamviewer and help me sorry for coming back to an old thread this seemed like the only place where I could get support

[pbatard]

was wondering if you could come into teamviewer and help me

Sorry but I don't provide this kind of personalized support.

The only help I can provide is point you to this relevant FAQ entry (which DOES work - but you may have to insist, repeat the steps, replug your hardware or reboot your computer).

[Zutatensuppe]

@robertj131 it is an old topic and u might have resolved the issue, but please see if u got something like a "usb devices" category in your device manager (has a grey symbol like the usb controllers category) and its next to "usb controllers" entry. I had to delete my device there and there was the checkbox to remove device driver software too. When I tried to remove the device drivers via the entry in the input devices category, it did not work. Hope this helps.

[vilu85]

Same issue here with Windows 10, after removing device and drivers it still reinstalls same drivers I once selected with Zadig.

[dm13dv1b]

Same here. Can not uninstall the driver. I think we need help. Trust me I tried everything I could with my 25 yrs experience.

[mvortex]

I would like to thank the author pbatard for his advice

You need to make sure that the checkbox to delete the drivers is checked always, and go through the uninstallation for every USB port where you might have ever plugged the device. You also need to make sure that you unplug the device after the driver has been uninstalled.

I had tried uninstalling (software also clicked) and unplugging/replugging to no avail, but I just tried again a few times, once from universal serial bus, then from libusb etc. Eventually it does get rolled back, persistance is key.

[TheCric]

maybe this can help
http://www.smallbulb.net/2013/287-detaching-ms-windows-libusb-driver
and to find where are the all inf files use NirSoft USB deView http://www.nirsoft.net/utils/usb_devices_view.html

[inakianduaga]

Same thing had happened to me (Win 10, bluetooth dongle).

This helped me:
https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal

Repeat these steps for every device on the node. Don't unplug the devices during this process! Then click the following icon to scan for hardware changes:

...

Now the removed devices should get equipped with their proper default drivers and the libusbK USB Devices node should've vanished.

If they still appear under libusbK USB Devices you need to repeat these steps multiple times until success, that's because the Windows Driver Store can hold multiple copies of the driver files and re-assign them if not deleted.

key is to not unplug the device after deleting driver w/ checkbox and trigger scan for hw changes

[slowizzm]

Uninstall then scan for hardware changes ... repeat until it resets.

[teckel12]

I just went through this problem with a Logitech Unifying USB dongle. No amount of deleting drivers, insert/removals, reboots would work. What did work was to download and install the Logitech SetPoint app. It reinstalled the correct drivers and everything worked without a reboot.

So, simply doing what was suggested previously is not enough in all cases. Sometimes you will need to use the manufacturer's driver install process as well.

[3DgeekStore]

Unfortunately
"The reason why Zadig does not provide this ability is that it is very easy to uninstall/restore the default Windows driver (HID, Mass Storage, etc.) in Device Manager."

This affirmation is false for hid keyboards, only 2 options, reinstall wiondows or use a new keyboard.

[mikbuch]

Had the same problem with Modecom MC-M9 Optical mouse on Windows 10.

I followed @slowizzm advice:

Uninstall then scan for hardware changes ... repeat until it resets.

It worked. I can add that at first I tried: (1) "Uninstall device" with "Delete driver" checked, (2) then unplugged, (3) then plugged in and (4) "Scan for hardware changes". It didn't work. A second try was: (1), (4) -- this worked like a charm. :)

[3DgeekStore]

Thanks, I followed another patch to solve the issue I used http://www.nirsoft.net/utils/usb_devices_view.html , and with this tool, I will be able to delete the driver

[usbsnotworking]

https://www.youtube.com/watch?v=uY4KeAzq-30 Here is a helpful video I put together for those having trouble. It'll walk you through everything you need.

[teckel12]

@usbsnotworking Only works some of the time. Other times you must load the drivers from the manufacture.

[robomechs]

It worked. I can add that at first I tried: (1) "Uninstall device" with "Delete driver" checked, (2) then unplugged, (3) then plugged in and (4) "Scan for hardware changes". It didn't work. A second try was: (1), (4) -- this worked like a charm. :)

(1),(2),(3),(4) or (1),(4) doesn't work for me (win10).
(1);(2);(3), but plugged in into other port - Ok!

[WindyJAmiller]

http://www.nirsoft.net/utils/usb_devices_view.html

Worked for me - Just plugged my HID Keyboard in all the ports and deleted the driver as it came up until windows detected it as a new device and bingo. The Zadig developer is wrong, I tired manually deleting the drivers using Device Manager, but they where not getting deleted, the option to 'Delete Driver' was not there on my machine, this has taken a good hour of my life to fix. Good software, frustrating it doesnt roll back. Thanks

[studiofuga]

The fix provided by @WindyJAmiller doesn't always work, especially if you changed the driver multiple times or you are unable to find all the instances of the driver.
But there's a workaround:

• Open the device manager and look for the offending device. If you aren't able to find it for some reason, you can use Zadig to change the driver to libusb and you'll find your device in the device manager under the libusb node.
• Right click on the device and select "Update the driver"! Windows will ask you what to do, select "search the driver locally" then "select the driver from a list". Ensure that "Show compatible hardware" checkbox is checked. You should see the original driver there!
• Profit!

[klausbert]

It worked for me by inserting the Logitech dongle on each USB port, every time it showed up as "Device" (not "controller") I uninstalled WITH checkbox. After one complete round, the mouse came back to life.
FWIW

[mrexodia]

The trick is to install the USB Serial (CDC) driver for the device you messed up. Then go to Device Manager and find the device with an exclamation pointer next to it. Then go to Properties -> Driver tab -> Update Driver... -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer

Then scroll down the list and try one of the drivers that doesn't have WinUSB or libusb next to it and install this driver.

[davidabsilva]

For those in the future who encounter this issue, my fix was to uninstall all software associated with zadig, and remove anything from my system32 folder, driver repository, with the name winusb and searched my system32 folder for libusb and libusbk. Of course keep in mind when those files were actually added, I didn't delete anything with a date of a few weeks or months before the incident. Nothing else worked for me.

A word to the man in charge, your "uninstall driver" fix, does not work. It will prompt a reboot system to complete even give you the "delete software for this drive" option but on startup it will install the same driver.

[pbatard]

A word to the man in charge, your "uninstall driver" fix, does not work.

And yet this is what I've used to uninstall many many devices, and I have never once seen it fail.

I gather that what people fail to understand is that if you plug your device to a different port, Windows will consider it as a completely different device and see the drivers as separate (even as the underlying files are the same), so you just have to insist and make sure you go through the motions for every port where you may have ever plugged your device.

Now, if you think can produce a detailed replicable sequence of events where you install a driver with Zadig for a device that you really can't uninstall by deleting the driver through the device manager, I'm interested, because I still have yet to see such a scenario.

[davidabsilva]

I didn't came here to argue, just giving more solutions to the problem, and it's not a different port issue.

I did my installation for a camera, installed libusb, did my things. When I did uninstall it, after rebooting it was recognising it has a COM port, not what I wanted nor what I had previously. If I updated the driver it would go to libusb again. So my conclusion to that endless loop was to "clear" my driver repository folder.

[pbatard]

Then you should be able to replicate the issue you saw, while making sure you provide logs from Zadig to document how you installed the driver as well as screenshots from the device manager, so that I can investigate your claim.

I hope you can appreciate that the "There so is an issue. But I'll leave it to the developer to figure it out" approach will not work, and the only thing I can work with is concrete documented evidence, especially when I am making an equally valid claim of never having experience such an allegedly common issue with uninstalling drivers before. Unless you are willing to do that, and have what you did properly scrutinized by at the very least providing your Zadig installation logs (I'm especially curious about those on account that you mention a COM port, which would tend to indicate that maybe you installed the USB Serial driver, or that you selected the wrong interface to install a driver on, if your camera provides multiple ones), then your conclusion can not be substantiated, and there is really nothing I can work on because I don't have your camera at hand, and I certainly wasn't looking over your shoulder when you tried to install and uninstall the driver to get some clues as to what might have caused the issue you saw. As all other software developers, the only thing I can work with to assert whether there is an issue or not is concrete logged evidence.

[davidabsilva]

You are describing the mechanism of Windows auto driver-installation, follow...

Props for coming with another solution, mine worked fine for me. Unfortunately I won't try to see if yours also works.

[agnostigo]

Zadig is a brutal and medieval software that never should have published in the first place ! How can you not add a backup restoring option to such a destructive software ? I spent 2 hours of surfing on net and doing more dangerous stuff to get my bluetooth dongle back. You are irresponsible developer !

[pbatard]

You are free to invest your own time and send a patch that adds the feature you want or pay someone to do that for you if you can't do it. The software is Open Source.

Despite what you may like to think, the provider of a free software application that is provided as is, in the hope that it will be useful is under no obligation whatsoever to add every feature you request. I have a life too, the time I can devote to Zadig is limited and furthermore, most of the people who appear to have an issue with this are users who appear to have no clue what they are doing and clicked to a device at random.

Well, this is not hand holding software. It is targeted at people who have some basic knowledge of what they are doing and as opposed to what you are claiming, there's nothing "destructive" about the operation since you are not going to lose any data (the driver can always be reverted).

If you need driver installation software that provides hand holding and foolproof usage features, then please use something different than Zadig, because that is not what it is designed for. You may not realize this but it was primarily designed to be used as a sample for application developers (the may project is a software library: libwdi, and Zadig is just a sample for that library). You didn't pay anyone for that software and I am under no obligation whatsoever to invest a lot of time, which I don't have because Zadig is far from being the only Open Source software project I'm working on, adding a feature that, when everything is considered, may only help foster users with the idea that clicking everywhere without understanding what they're doing should have no consequences.

But hey, feel free to tell me how I should drop everything else I'm doing and pretend I have the resources of Apple, Google or Microsoft in terms of software and UI development, just because you got frustrated after replacing a driver that you should not have replaced in the first place...

[johnybell]

had to enable windows update service in my case windows7 , said so in the log under options advanced mode.

[ArkadiyEpanov]

In a similar situation, this program helped me. The driver distr was removed, and stopped being reinstalled in a circle.
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.8.3

[TheButlah]

Uninstall then scan for hardware changes ... repeat until it resets.

I had replaced a parent/root component of my usb device. I followed these instructions, making sure that I never unplugged my device. It was almost as if instead of resetting it to microsoft defaults, it was ctrl-z'ing my changes one at a time. Because I spent so long adding many different zadig drivers, it took me literally maybe 30 attempts. At some point the single usb interface became two, and one of them no longer had the check box. The other one still had the checkbox, so I kept at the process on just that one. Eventually, both usb interfaces were the original stock microsoft drivers, and neither had the checkbox.

Absolutely crazy that it worked, and have no idea why.

[Leo-Aqua]

You can just uninstall every usb device and restart (Works for me)

[GreenTea5611]

OKAY, I figured out how to fix this problem at least this is what I did. So I messed my mouse driver up and it switched to a libusbK (v3.0.7.0) driver. So after fumbling around for about an hour now, I found that it switched the tab is showed up in on device manager not as a mouse but as something else showing up in a different tab called libusbK USB Devices. Tried to delete and reinstall and it didn't work. So I then did this, pressed update driver, clicked browse my computer for drivers, then there is a button that says "let me pick from a list of available drivers on my computer" so then i scrolled down the list and clicked "USB Input Device" and it FINALLY WORKED. I hope this helps someone because it sure did me lol.