-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change readme restoring old drivers section #290
Comments
Yes I always use this method myself. |
I want to add another piece of information on that topic: Drivers generated by Zadig (driver provider This means that performing the uninstall process (Device Manager > Uninstall device > Delete the driver software for this device) will only remove ONE layer of driver, letting another driver of the stack be used in turn. Performing the steps above can work, as at step 3 you will see all the drivers next to each other, and at the bottom of the list the original one from Mricrosoft. Performing the current uninstall procedure multiple times might be safe as Windows won't suggest "Delete the driver software for this device" when you have reached the bottom (removed all Zadig and other installed drivers for that device). Though dont take me at my word, I have NOT analyzed the full ramifications of doing this yet (it fixed my problem for one device but I cannot attest that it will be the right solution overall, nor that it won't break other things ! |
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!! |
what I do |
Hey, your uninstall process might fail on windows 10, as there is an additional step involved to get the proper windows drivers for certain devices.
Your app seems to sign and add a device driver certificate, which windows will believe is the better driver for the device than it's own.
To undo this step:
This fixed my device.
Thanks for your tool <3
cheers,
The text was updated successfully, but these errors were encountered: