O In Device Manager, find entries marked “FUNcube Dongle V2.0 (Interface #)”, right click each and uninstall.
O Open an administrator command prompt and run “pnputil -f -d oem#.inf” for each oem#.inf file you found. They are text files, so you can open them in notepad. O Look in your C:\Windows\Inf directory and look for all the oem*.inf files which relate to the FCD or FCD+. In order to uninstall it’s a bit complex but here’s a recipe.
What’s worse is that Zadig doesn’t appear to present a clean way to uninstall its own work from the investigations I’ve done, so getting you back to square one isn’t as easy as it was to install those pesky Zadig configured drivers in the first place.
Using Zadig to override the operating system’s drivers for the FCD & FCD+ will not work! Increasingly recently we’ve been seeing problems where the symptoms suggest that folks have used a utility called Zadig to override the operating system’s own drivers, probably because there has been experience with an RTL dongle where it’s common to have to hack user-mode access to the device, overriding the device’s own drivers.įundamental to the FCD’s and FCD+’s design was to make it as easy to install as possible, and that means that it uses drivers that are native to your operating system so you don’t have to mess about fruitlessly searching the internet for the right driver, or, indeed use Zadig.