Ask · Share · Build

Which Zadig Driver Should an RTL-SDR Use?

Pavel

SDRstore_Pavel
Administrator
Staff member
Joined
Jul 30, 2026
Messages
121
Short answer: For the common Windows RTL-SDR I/Q workflow, install WinUSB on the dongle's receiver interface. Select the interface that belongs to the RTL-SDR—often Interface 0 on composite devices—but verify it from the USB identity instead of changing every entry Zadig lists.

Before you start​

  • Identify the exact RTL-SDR revision and tuner before applying driver, bias-tee or HF instructions; V3, V4 and other RTL2832U designs do not have identical RF paths.
  • Test with one receiver application and one known signal while all feeders and background SDR programs are closed.

Step-by-step method​

  1. Step 1: Disconnect other nonessential USB devices, open Device Manager and observe which device appears when the RTL-SDR is connected. This protects keyboards, Bluetooth adapters and storage devices from an accidental driver replacement.
  2. Step 2: Run Zadig as administrator, enable List All Devices and select the RTL receiver interface. Confirm vendor/product identity where shown; do not select a generic interface solely because its number looks familiar.
  3. Step 3: Choose WinUSB as the replacement and install it once. Reconnect the dongle, then run rtl_test or open one RTL-SDR application with all other receiver software closed.
  4. Step 4: If a DVB-T television application is required later, understand that it may need a different vendor driver. Switching workflows can require restoring that driver rather than keeping both applications open.

Concrete example​

A typical composite RTL2832U exposes Interface 0 for the receiver and another interface for an optional infrared function. The common SDR workflow targets only the receiver interface with WinUSB. The interface numbering is a clue, not a substitute for identifying the device.

How to judge the result​

The driver is correct when the RTL-SDR enumerates consistently, rtl_test can open it and the chosen SDR application streams samples. If Device Manager shows an error before rtl_test runs, remain at the USB-driver layer.

What to record​

  • Use manual gain for comparisons and record the tuner gain value, sample rate, PPM correction and antenna.
  • At 1090 MHz, compare aircraft or message count over equal time windows rather than one instantaneous signal peak.
  • If new peaks appear at unrelated frequencies when gain increases, suspect overload or intermodulation rather than newly received stations.

Common mistakes​

  • Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
  • Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
  • Using Zadig on a HackRF, Pluto, USRP or unrelated USB interface can replace its intended driver and create a new failure unrelated to RTL-SDR.

Final check​

Disconnect and reconnect the RTL-SDR, then repeat the test using the recorded revision, driver, sample rate and gain. The instructions are valid only if they reproduce on that exact hardware.
 
Top