The mfg (Manufacturer) entry should show the synthesized oem###.inf, corresponding to (same date) oem###.inf under C:\Windows\INF\ If the driver has been installed successfully, you should now be able to use your device with a libusb based application. Example of a zadig preset device config file # This is a sample preset device configuration for Zadig

This is usually because you have copied the SDR# files into a folder that is read only. In Windows folders located in "C:\Program Files" are usually automatically read only. To fix, install SDR# into a non read only folder that is not located in Program Files, for example "C:\SDR". Now I run Zadig and replace the driver with WinUSB. Here's the result. Note the SUCCESS and the changed Driver on the left. The Mac and Linux instructions usually say something like "plug it in and party on" but folks like myself with Windows have to set up a WinUSB Driver (libusb-win32 or libusbK) as dfu-util uses those libraries to speak to USB devices. Before following the next steps, please make sure you have installed the Microsoft Visual C++ x64 redistributable. Most PCs will have this already installed, but on some fresh installs this may not be the case. Installing Zadig drivers This is because you did not unzip the files and you are trying to run install-rtlsdr.bat from within the zip file. Remember to extract the files first, before running them.And remember to select the correct demodulation mode for the signal you are tuned to via the "Radio" menu on the left. utl: Driver INF - oem37.inf (C:\WINDOWS\System32\DriverStore\FileRepository\ooi_flamenir.inf_amd64_c49d37bc221e3c4a\ooi_flamenir.inf) of the time this is because Windows automatic driver updates has automatically removed the SDR drivers and installed DVB-T drivers in its place. Make sure Windows automatic driver updates are turned off, and rerun zadig to reinstall the WinUSB driver.

When I run install-rtlsdr.bat a CMD/DOS window flashes on the screen briefly then disappears. Nothing is installed.At this point I can follow along and flash my devices per whatever instructions my manufacturer/project/boardmaker intends. While using rtl_eeprom, I bumped or disconnected my dongle during an EEPROM write, and now the VID and PID's are all 0000 and the dongle isn't recognized! I get decoding, audio and/or visual spectrum glitches when I set the PPM offset to a non-zero value. V4 Features Guide: rtl-sdr.com/V4 - Learn how to use special V4 features and how to install the required drivers for V4 models.

If you cannot see your device listed, then it probably means that it already has a driver installed, in which case you need to be very cautious about replacing it, as other applications or the OS itself may no longer be able to access it afterwards. For instance, if you replace the existing driver for an USB keyboard or mouse, it will no longer be usable for input in Windows but instead will only work with a custom application, which is probably not what you want. These are the instructions for installing our RTL-SDR Blog drivers. Type them into the Linux terminal one by one. I'd love to see this extra step in Windows removed, but for now, I hope this write up makes it clearer and helps the lone Googler who finds this post.SDR# is the most commonly used SDR program on Windows. We recommend it as one of the easiest to setup and use with the RTL-SDR. Please note that the RTL-SDR is not a plug and play device. You will need to have sufficient skills to perform basic PC operations such as unzipping files, installing software, moving and copying files and have the motivation to learn new software. This appears to be a bug with SDR# or Windows. The solution right now is to simply turn display sleep off. If you are using a RTL-SDR.com V3 dongle, view our V3 users guide to learn how to use the special features like HF direct sampling and the bias tee. If it is a newer V4 dongle, visit our V4 users guide. This can happen if you have set the sampling rate to the maximum stable rate at 2.56 MSPS. Adjusting the PPM value actually slightly modifies the sampling rate, so you may be pushing it over the stable limit. To solve this you will need to go down to a sampling rate of 2.4 MSPS.