Getting the RTL-SDR to work in Windows 10

The RTL-SDR is fully compatible with Windows 10. However with the recent release of Windows 10 some users have been having trouble using their RTL-SDR after upgrading. We thought that we’d announce that the simple solution to most problems is to reinstall the SDR drivers with Zadig. The latest version of Zadig can be downloaded from or if you use SDR# then it will already be in your SDR# folder. The process is:

  1. Plug in the RTL-SDR.
  2. Run Zadig as administrator by right clicking it and choosing run as administrator.
  3. Go to Options -> List all devices and make sure it is checked.
  4. In the drop down box choose Bulk-In, Interface (Interface 0). This may also sometimes show up as something prefixed with “RTL28328U”. That choice is also valid.
  5. Make sure that WinUSB is selected as the target driver and click on Replace Driver.

If you need more help see the Quickstart Guide.

The Windows 10 upgrade process appears to replace the WinUSB drivers with the Windows DVB-T ones, so reinstalling the SDR drivers is necessary. It shouldn’t be necessary, but one user also reported the need to log in to Windows with an administrator account and to uninstall the current drivers before running Zadig, so try that if you continue to have problems.

As in our previous post we can confirm that several popular SDR apps such as SDR#, HDSDR, SDR-Radio, CubicSDR and Unitrunker all work fine in Windows 10.


  1. Dave

    The driver install fails. Requires 64 bit driver.
    Zadig 2.4.720
    Windows 10 64-bit (Build 17134)
    ini file ‘zadig.ini’ not found – default parameters will be used
    default driver set to ‘WinUSB’
    0 devices found.
    6 devices found.
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_03F0&PID_0024&REV_0130
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_01
    libwdi:debug [wdi_create_list] Driver version: 10.0.17134.112
    libwdi:debug [wdi_create_list] HidUsb USB device (1): USB\VID_03F0&PID_0024\6&1778337&0&4
    libwdi:debug [wdi_create_list] Device description: ‘HP Basic USB Keyboard’
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_00
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
    libwdi:debug [wdi_create_list] Upper filter: RTL2832UBDA
    libwdi:debug [wdi_create_list] Driver version: 64.1.802.2010
    libwdi:debug [wdi_create_list] RTL2832UUSB USB device (4): USB\VID_0BDA&PID_2838&MI_00\7&38A180A5&0&0000
    libwdi:debug [wdi_create_list] Device description: ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_04F2&PID_0939&REV_0100
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_02
    libwdi:debug [wdi_create_list] Driver version: 10.0.17134.112
    libwdi:debug [wdi_create_list] HidUsb USB device (5): USB\VID_04F2&PID_0939\6&1778337&0&3
    libwdi:debug [wdi_create_list] Device description: ‘USB Optical Mouse’
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_051D&PID_0002&REV_0006
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_03&SubClass_01&Prot_00
    libwdi:debug [wdi_create_list] Driver version: 10.0.17134.112
    libwdi:debug [wdi_create_list] HidUsb USB device (6): USB\VID_051D&PID_0002\NB9850002122
    libwdi:debug [wdi_create_list] Device description: ‘BackUPS Pro 350 FW:15.3.D USB FW: 3’
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0BDA&PID_2838&REV_0100&MI_01
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_ff&SubClass_ff&Prot_ff
    libwdi:debug [wdi_create_list] Driver version: 8664.1.1019.2010
    libwdi:debug [wdi_create_list] RTL2832U_IRHID USB device (7): USB\VID_0BDA&PID_2838&MI_01\7&38A180A5&0&0001
    libwdi:debug [wdi_create_list] Device description: ‘Bulk-In, Interface (Interface 1)’
    libwdi:debug [wdi_create_list] Hardware ID: USB\VID_0403&PID_6001&REV_0600
    libwdi:debug [wdi_create_list] Compatible ID: USB\Class_FF&SubClass_FF&Prot_FF
    libwdi:debug [wdi_create_list] Driver version:
    libwdi:debug [wdi_create_list] FTDIBUS USB device (8): USB\VID_0403&PID_6001\A505MM0A
    libwdi:debug [wdi_create_list] Device description: ‘FT232R USB UART’
    Using inf name: Bulk-In_Interface_(Interface_0).inf
    Successfully extracted driver files.
    Installing driver. Please wait…
    libwdi:info [extract_binaries] successfully extracted driver files to C:\Users\dzari\usb_driver
    libwdi:info [wdi_prepare_driver] successfully created ‘C:\Users\dzari\usb_driver\Bulk-In_Interface_(Interface_0).inf’
    libwdi:info [wdi_prepare_driver] Creating and self-signing a .cat file…
    libwdi:debug [AddFileHash] ‘wdfcoinstaller01011.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\dzari\usb_driver\amd64\wdfcoinstaller01011.dll’
    libwdi:debug [AddFileHash] ‘winusbcoinstaller2.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\dzari\usb_driver\amd64\winusbcoinstaller2.dll’
    libwdi:debug [AddFileHash] ‘bulk-in_interface_(interface_0).inf’: INF type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\dzari\usb_driver\bulk-in_interface_(interface_0).inf’
    libwdi:debug [AddFileHash] ‘wdfcoinstaller01011.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\dzari\usb_driver\x86\wdfcoinstaller01011.dll’
    libwdi:debug [AddFileHash] ‘winusbcoinstaller2.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\dzari\usb_driver\x86\winusbcoinstaller2.dll’
    libwdi:info [CreateCat] successfully created file ‘C:\Users\dzari\usb_driver\Bulk-In_Interface_(Interface_0).cat’
    libwdi:info [RemoveCertFromStore] deleted existing certificate ‘CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)’ from ‘Root’ store
    libwdi:info [RemoveCertFromStore] deleted existing certificate ‘CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)’ from ‘TrustedPublisher’ store
    libwdi:debug [CreateSelfSignedCert] set Enhanced Key Usage, URL and CPS
    libwdi:debug [CreateSelfSignedCert] created new key container
    libwdi:debug [CreateSelfSignedCert] generated new keypair
    libwdi:info [CreateSelfSignedCert] created new self-signed certificate ‘CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)’
    libwdi:debug [SelfSignFile] successfully created certificate ‘CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)’
    libwdi:info [SelfSignFile] added certificate ‘CN=USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)’ to ‘Root’ and ‘TrustedPublisher’ stores
    libwdi:info [SelfSignFile] successfully signed file ‘C:\Users\dzari\usb_driver\Bulk-In_Interface_(Interface_0).cat’
    libwdi:info [SelfSignFile] successfully deleted private key
    libwdi:debug [wdi_install_driver] using progress bar mode
    libwdi:error [install_driver_internal] this application does not contain the required 64 bit installer
    libwdi:error [install_driver_internal] please contact the application provider for a 64 bit compatible version
    Driver Installation: FAILED (Requested resource not found)

  2. Henry

    Hi, Server timed out on initial post. Sorry if this shows up twice. Having trouble getting RTL-SDR V.3 to show up as a source in AirSpy. Device manager shows USB devices / Bulk-In, Interface (Interface 0), and Human Interface devices / HID Infrared Remote Receiver. They both go away if I remove the RTL-SDR, so I assume that it installed OK. Any help appreciated.

  3. Jon Kreski

    Have a new Dell Windows 10 PC and have used RTL-SDR, SDR# and Zadig extensively – always worked. When I install the RTL-SDR driver and look in SDR# it shows EZCAP instead of RTL-SDR and crashes when I try to start the tuner. What am I missing? I tried running as Administrator with no luck.

    • Jon Kreski

      I fixed it. Followed Step 5 – above. Ran the install batch file. That downloaded the required driver files. Then I went back into Zadig (ran as Administrator) and did the re-install driver process. Started SDR# and SDR-Console – both worked like a charm. Great pieces of free software. Thanks to whomever put all the effort into those gems!

  4. jaakko

    Gqrx SDR Ubuntu work easily, win 10 is not intended for other than its own programs and browsing the web

  5. R vd Meer

    The procedure i follow with windows 10 is insert the dongle,start zadig 2.3.
    Make sure that list all devices is selected,from the pull down menu select bulkinterface 0
    Replace driver with winusb.if it failed just do a reboot and try again it should work fine.
    Download the zipfile relwithdebinfo,
    extract the zipfile.
    Now copy the 32bit version of the driver to the sdr# folder not the 64 bit.
    Startup sdr# and select from the pulldown menu rtlsdr usb.
    Now you can go to settings and adjust the gain and select the dongle you want to use.
    The number of dongles i use is about 4 to 6,
    What i also noticed is if you put different drivers in the sdr# folder,example for plugins it can result in a crash of sdr#.
    Hopefully it helps you guys with windows 10.

  6. KK0DJ

    I have two dongles… neither have I ever had them working. I have tried Zadig, I have gone through the steps on the sites that I have found through searching out this issue. It seems that it’s all a waste of time! Isn’t there someone who manufactures these things that provides software AND drivers that work in Windows 10? Very disgruntled and tired of the hours and hours chasing this stupid thing.

  7. Andy

    I can’t get SDSharp to run just get the crash folder with this in it:
    The type initializer for ‘PortAudioSharp.PortAudioAPI’ threw an exception.
    at SDRSharp.Radio.dll.PortAudioAPI.Pa_GetDefaultInputDevice (IL offset: 0xffffffff)
    at SDRSharp.Radio.dll.AudioDevice.GetDevices (IL offset: 0x6)
    at SDRSharp.exe.MainForm.InitializeGUI (IL offset: 0x153)
    at SDRSharp.exe.MainForm..ctor (IL offset: 0x150)
    at SDRSharp.exe.Program.Main (IL offset: 0x6e)

    Any Luck? I’m getting the same error:
    The type initializer for ‘PortAudioSharp.PortAudioAPI’ threw an exception.
    at SDRSharp.Radio.dll.PortAudioAPI.Pa_GetDefaultInputDevice (IL offset: 0xffffffff)
    at SDRSharp.Radio.dll.AudioDevice.GetDevices (IL offset: 0x6)
    at SDRSharp.exe.MainForm.InitializeGUI (IL offset: 0x153)
    at SDRSharp.exe.MainForm..ctor (IL offset: 0x150)
    at SDRSharp.exe.Program.Main (IL offset: 0x6e)

  8. Anonymous

    I got it up on windows 10
    I can not however connect to it via tcp, the machine actively refused the connection.
    I am trying to use to listen to my meter

    I have tried “CheckNetIsolation LoopbackExempt -c” to remove all apps but I think maybe this may be only for windows apps.

  9. AC9BX

    Options for Windows 10:
    open your Group Policy Editor (as Admin) – one way to do this is to search on your start menu or enter in a Run box gpedit.msc
    Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update
    There you will find an entry “do not include drivers with Windows Update”
    set it to enabled. This will be for all drivers, be warned.

    There are other options there you may be interested in such as “no auto-restart with logged on users” – tired of Windows logging you out while you’re working?
    Or disable “allow automatic updates immediate installation”, this means you will have to do it on your own.

    Start Menu problems, Windows 10 has known issues with the Start Menu failing. Microsoft has a tool you can download to attempt to fix it. It may or may not work. Sometimes the tool will report that it didn’t fix it but it did indeed fix it. Windows 10 is a kludge. Go here and look for “try the troubleshooter”.
    Attempting to uninstall built-in apps for Windows 10 will often break the Start Menu, other things apparently do as well.


    Using zadig to install rtl-sdr driver , it cannot complete the installation giving me a windows 1018 error. The name of dongle name appears with bulk 0 but driver installation cannot be completed and obviously the device is not found in sdrsharp 🙁 … any idea ? thanks !!!

  11. Luis

    With the upgrade to Windows 10 I have had to choose to either have Windows working correctly or being able to use HDSDR with the Zadig driver. If I install the Zadig driver, HDSDR works fine, but causes many important features to stop working on Windows 10, for example, the Windows 10 Start Menu/Button stops working, clicking on the search or Cortana search box does nothing, when trying to preview open applications on the task bar the menu that normally pops up to be able to close, minimize, etc. does not come out anymore by right clicking the application’s icon. Since the Start Menu/Button stops working, only way to restart or shut down the computer is to use ctrl, alt, delete to be able to do so. Researched the possible causes of the Windows 10 issues with no fix, by chance I ended up uninstalling the Zadig driver and Windows 10 started to work normally again. Just to make sure, I then tried on a different computer with Windows 10 and the same thing happened. I need my PC working correctly so no HDSDR and Zadig for me anymore…

  12. clifford wright

    A new problem with Windows 10. BTW I have reinstalled using Zadig several times and turned off (I think) the automatic USB upgrades. It works perfectly, for about 5 to 10 minutes and then crashes. Sometimes it can be restarted but it crashes very soon after that. Does anyone know if Win 10 is somehow still snaking in an upgrade,behind my back?

    • Peter G

      I’m having the exact same problem, SDR# crashes after about 5 minutes. Started happening out of nowhere, so suspecting one of the recent Windows updates as well.

    • Alphie

      Hi. Im having a similar problem after upgrade to win10 64 bits. Sdr# crashes randomly with Realtek dongle. It sometimes works well for just 5 mins and other Times 30 minutes Or more. Tried replacing driver with older zadig, disable anti vírus, checking mouse options as the crashes are more often when i use the trackpad. I also have various copies of sdr# on diferent folders for the keneerd and hf experimental drivers but Guess this is not the problem since all use the same zadig driver i think. Any suggestion?

      • Alphie

        After some time looking for options to change i finaly solved my problem. Looks like on order for this to work, at least on my win10, i nedded to go to advanced power saving options and disable the option as when my laptop is conected to plug and battery. After that all is working as it should.

  13. mitch

    Hi, had the same problem sdr# not seeing the rtl-sdr device. using zadig driver. to fix i copied the rtlsdr.dll file in the zadig directory to the sdr# directory, it copied ok and did not over wright any files(i was missing the dll), and then started sdr# – it is able to access the rtl-sdr device and is working ok now.
    Hope this helps.

  14. Tony

    The zadig did the trick for Windows 10. No problem. My next project will by trying skywave Linux on my laptop. The windows laptop is my girlfriend’s.

  15. Dean Denton

    When I ‘try’ to open SDR Sharp, nothing happens, and a file called ‘crash.txt’ is created. This happens every time! It’s annoying. In crash.txt this is shown:

    Configuration system failed to initialize
    at System.Configuration.dll.ClientConfigurationSystem.EnsureInit (IL offset: 0x120)
    at System.Configuration.dll.ClientConfigurationSystem.PrepareClientConfigSystem (IL offset: 0x8)
    at System.Configuration.dll.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection (IL offset: 0x0)
    at System.Configuration.dll.ConfigurationManager.get_AppSettings (IL offset: 0x0)
    at SDRSharp.exe.Program.Main (IL offset: 0x3d)

    Please Help me!!! Thank You


  16. Jonathon Pearce

    Can anyone help…..
    I have an SDR R820T Nooelec dongle and it works fine under HDSDR but always get device not found. Running Win10 on Surface Pro and suspect it may be the USB3. If it wasn’t running on HDSDR I would suspect a driver but having run zadig and also can see it in device manager it is not the driver. Also downloaded and run the install file so if it is not the USB3 which I suspect is fine as HDSDR works fine it must be SDR# and a missing dll.

    Please help as I am seriously frustrated!

    • Jonathon Pearce

      Sorry to clarify its device not found in SDR#. HDSDR is great!
      Also please don’t suggest zadig been there, done that to death!

  17. Adam Ebel

    I tried to the same thing, and there is no joy, and I am running a Windows 10 32 bit operating system. Now I know I need to get a 64 bit operating system installed soon just to get this software to work. For the time being until I switch to 64 bit, I have to use linux based RTL SDR software on a flash drive. I know, the struggle is real.

  18. Larry Dighera

    Just installed CubicSDR on a Pipo9 “tablet” running Windows 10 32-bit, and don’t see any spectrum nor waterfall. SDR#, HDSDR, and SDR-Console work fine with the RTL-SDR dongle (love the TCXO by the way). What do I need to do to see signals?


    Best regards,

  19. Lee Donaghy

    Right pain getting it working on Win10 after i reinstalled windows, kept messing about with zadig and trying to install them manually in device manager but to no avail.
    then i tried rtl_test and it saw it, so the problem was sdrsharp! it was missing rtlsdr.dll sigh.
    downloaded it and all was working…

  20. alexandre27

    I had two PCS on W8. One ran SDR# without pb I could never get it the other to work (no explanation found). On W10 my new PC runs reliably SDR# . Try to desinstall and reinstall the driver ?

  21. Hiram

    For the life of me I can’t get Zadig 2.1.2 drivers to work on Windows 10. They install, but when I run SDR# with my RTL connected – it says “device not found”. I have had them working on 8.1, but for some reason they don’t seem to work on Windows 10 – any thoughts?

Post a comment

You may use the following HTML:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

This site uses Akismet to reduce spam. Learn how your comment data is processed.