Quick Start Guide

This page is a guide aimed at helping anyone set up a cheap radio scanner based on the RTL-SDR software defined radio as fast as possible on a Windows system. If you have any trouble during the installation, please see the troubleshooting guide further down the page. We also have brief instructions for getting started on Linux and OSX at the end of this page.

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.

Equipment Guide

Currently, the most common RTL-SDR dongle is the R820T/R820T2 which usually sells for under $20 USD. See the Buy RTL-SDR dongles page for more information on purchasing.

Generally at least a dual core processor will be required to run most SDR software smoothly. Some command line software and ADS-B decoders may work on less powerful hardware.

To get the most enjoyment out of RTL-SDR you will need a decent antenna. Our packages that come with two telescopic antennas are a great start. Be sure to get them up high and place them on a metallic surface for best results. Units not sold by us may come with a smaller fixed length whip antenna that is okay for testing, but overall is not that great. As an upgrade for beginners who have the fixed length whip, a cheap bunny ears antenna mounted vertically should work well. Use the simple kind like this so that it can easily be mounted vertically. The most recommended outdoor antenna for general scanning is a scantenna or discone due to their wide band receiving properties. You can also cheaply build a wideband planar disk antenna (pdf warning) out of some metal pizza pans.

RTL-SDR Blog V3 Users: Please also see our V3 users guide for information on using the bias tee, direct sampling HF tuning and expansion header features.

SDR# (SDRSharp) Set Up Guide (Tested on Windows 10/8/7 32/64 Bit) (XP Incompatible)

SDR# is the most commonly used SDR program on Windows. We recommend it as one of the easiest to use and setup with the RTL-SDR.

  1. Purchase an RTL-SDR dongle. The cheapest and best for most applications is the R820T/R820T2 dongle. Information on purchasing one can be found here.
  1. You must have the Microsoft .NET 4.6 redistributable installed to use SDRSharp. Follow the link and install the redistributable. Most Windows 10 PCs should already have this installed by default, but PCs with older operating systems may need this to be installed in order to run SDR#. Note that .NET 4.6 is not compatible with Windows XP. If you are running XP please scroll down on this page and look for the HDSDR or SDR-Console install guides. Note that on some computers you may also need to install the Visual C++ Runtime if it is not already installed.
  1. Go to www.airspy.com and find the downloads button on the top menu. Next to the “SDR Software Package” heading click on the download button to download sdrsharp.zip.
  1. Extract (unzip) sdrsharp.zip to a folder on your PC. (Important! Many people who have issues forget this step! Do not run the files from within the zip file or the following steps will fail). (Also, do not extract into a folder within the Program Files directory, or installation may fail as these folders are often automatically made read only by Windows).
  1. Double click on install-rtlsdr.bat from within the extracted folder. This will start a command prompt that will download all the drivers required to make SDRSharp work with RTL-SDR. The command prompt will automatically close after a few seconds when it is done. It the bat file ran successfully the files rtlsdr.dll and zadig.exe will be downloaded into the SDR# directory. If they were not downloaded then your PC or anti virus solution may be misconfigured and may have trouble running batch files (Check that the folder is not read only, and not located in the Program Files directory). If install-rtlsdr.dll fails, do a manual driver installation

install-bat_sdrsharp

  1. Plug in your dongle. Do not install any of the software that it came with (if any), and ensure that you wait a few seconds for plug and play to finish attempting to install the dongle (it will either fail or install Windows DVB-T drivers). If you’ve already installed the DVB-T drivers that came on the CD bundled with some dongles, uninstall them first.
  1. In the folder where you extracted the sdrsharp files find the file called zadig.exe. Right click this file and select “Run as administrator”.
  1. In Zadig, go to “Options->List All Devices” and make sure this option is checked.

zadig_1

  1. Select “Bulk-In, Interface (Interface 0)” from the drop down list. Note on some PCs you may see something like RTL2832UHIDIR or RTL2832U instead of the bulk in interface. This is also a valid selection. Do not select “USB Receiver (Interface 0)” however. 
  1. We need to install the WinUSB driver, so also ensure that WinUSB is selected in the box after the arrow next to where it says Driver (this is the default selection). – Note that there has been some confusion for a few people over this step. The goal is to install the WinUSB driver. So to be clear, the box to the left of the arrow shows the currently installed driver, whereas the box to the right of the arrow shows the driver that will be installed in the next step. The first time you open zadig the box on the left will show either ‘None’, or the default DVB-T drivers installed by Windows (RTL2832UUSB), depending on your Windows configuration and version.

zadig_3

  1. Click Replace Driver. On some PC’s you might get a warning that the publisher cannot be verified, but just accept it by clicking on “Install this driver software anyway”. This will install the drivers necessary to run the dongle as a software defined radio. Note that you may need to run zadig.exe again if you move the dongle to another USB port, or want to use two or more dongles together.

zadig_warning

  1. Open SDRSharp.exe (note that the first time you do this you may get a smartscreen message indicating that Windows has protected your PC, this is a false alarm. Simply click on “more info” and then “run anyway”). Set the drop down box in the “Source” tab on the top left to ‘RTL-SDR (USB)’.
  1. Press the Play button (the right facing triangle). Your RTL-SDR software radio should now be set up and ready to use! If everything has worked you should be able to start tuning to frequencies.

rtlsdrsource

  1. Important! Don’t forget to also adjust the RF gain settings by pressing the Configure button (looks like a cog) up the top next to the Play button. By default the RF gain is set at zero. A gain of zero will probably receive nothing but very strong broadcast FM – increase the gain until you start seeing other signals.

gain

Next Steps

After getting your RTL-SDR set up with SDR# we recommend investigating the following:

  1. Check out all our featured articles on this blog for various RTL-SDR related projects and tutorials.
     
  2. Upgrade from the stock antenna. For optimal reception you should use an outdoor roof mounted antenna. The optimal antenna will depend on the frequency and project you are interested in, but for a general all purpose antenna we recommend a Discone or planar disk antenna (pdf).
     
  3. If you are using your RTL-SDR for HF with an upconverter such as the SpyVerter then we recommended using SDR# with the special decimation drivers. This will allow you to zoom in on the small bandwidth signals used on HF without loosing resolution.
     
  4. Check out our store for various RF accessories such as filters, LNA’s and antennas.

Troubleshooting

  • I get the error “No Device Selected” when trying to start the dongle in SDR#.
    Make sure you have run the install-rtlsdr.bat file, and that it has sucessfully downloaded the rtlsdr.dll file into the SDR# folder. If it is not downloaded, check that your folder is not set to “read only” (this sometimes happens automatically if you install into Program Files, so do not install into that folder). Another source of problems is if you have accidentally installed the WinUSB drivers to Bulk Interface 1 instead of with Zadig. If you have done this, then SDR# will not recognise your dongle. TO fix it go into device manager or Devices and Printers and uninstall the driver for Bulk Interface 1.
  • I get the error “No compatible devices found” when trying to start the dongle in SDR#
    Long low quality USB extension cables can sometimes cause this error. Some USB 3.0 ports are also incompatible with the dongle and cause this error. One user has had luck with this error by installing zadig from safe mode. Finally, there is a small chance that the dongle is actually faulty. If the dongle produces the same error on multiple computers the dongle is probably faulty and should be refunded or replaced.
  • Zadig just hangs when I try to install the driver
    People with this problem have usually had success with an alternative zadig tool available at visualgdb.com/UsbDriverTool. Use the tool to install the WinUSB driver.
  • Zadig shows NONE in the driver install screen.
    This is normal. The box on the left indicates the CURRENTLY installed driver. The box on the right indicates the driver THAT WILL BE installed after clicking on the install button.
  • My dongle was working before but today it no longer works and displays an error when I click on Play.
    99% 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.
  • I get the error “1 compatible devices have been found but are all busy” or “libusb Open error -12”
    First check that another program is not using the RTL-SDR. To fix this it may be necessary to reinstall the drivers via zadig and to try every USB port on the PC. You may want to also try disconnecting all other USB devices connected to the PC. Also some USB 3.0 ports are buggy, switch to a USB 2.0 port. Some users have also had success with installing everything from Windows safe mode. Make sure you are not selecting the “USB Receiver (Interface 0)” in zadig, and instead are selecting the Bulk in interface, or one that may say RTL2838UHIDIR or something else prefixed with RTL. If you don’t see this make sure that “Options->List All Devices” is checked and that “Ignore Hubs or Composite Parents” is unchecked.Another thing to try may be to disable Windows automatic driver installation. Instructions for disabling this can be found here. This error also sometimes occurs after the computer has been suspended – to fix it simply disconnect and reconnect the dongle.
  • I get the error “Unable to load DLL ‘rtlsdr’: the specified module could not be found. (Exception from HRESULT: 0x8007007E)”
    Usually installing the Visual C++ Runtime solves this problem. Most PCs have this installed already, but if you are on a freshly installed version of Windows it may not have been installed yet.
  • There is a constant spike in the middle of the spectrum that won’t go away
    This is normal and is a side effect of the design of most RTL-SDR dongles. It can be removed algorithmically in the SDR# software by checking the “Correct IQ” box.
  • Zadig takes a long time to install the driver, then fails
    You have probably not run zadig in administrator mode. Make sure to right click zadig, and select “Run as Administrator”. If that fails to work try the alternative WinUSB installer at visualgdb.com/UsbDriverTool.
  • I don’t see Bulk-In, Interface (Interface 0)
    Ensure “Options->List All Devices” is checked. Sometimes you may also need to uncheck “Ignore Hubs or Composite Parents”. Some people report seeing something else other than the bulk in interface. It may also show up as the brand of your dongle or something prefixed with “RTL”, e.g. RTL2832U or RTL2832UHIDR. Any of those options should work too. In rare cases you may receive a faulty dongle that will not show up in Zadig no matter what USB port or computer you try it on. You should ask for a replacement in this case.
  • I don’t see RTL-SDR/USB in SDRSharp
    You may have downloaded a version without rtl-sdr support. Check that you have downloaded the official version from the airspy.com website.
  • USB 3.0 ports don’t work
    Unfortunately many USB 3.0 controllers are buggy and don’t work with some USB 2.0 devices. Generally, USB 3.0 works fine with the RTL-SDR, but there are some controllers that will just not recognise the dongle. In this case use a USB 2.0 port instead.
  • When running install-rtlsdr.bat I get errors on the command line like “The system cannot find the file specified” and the sdrsharp folder is not downloaded
    This is probably 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. 
  • When I run install-rtlsdr.bat a CMD/DOS window flashes on the screen briefly then disappears. Nothing is installed.
    There seems to be a bug or misconfiguration with some versions of Windows where batch files cannot be run. One way around this is to install the RTL-SDR drivers manually. We have instructions for this here: rtl-sdr.com/manual-installation-of-sdr. Some antivirus solutions are also overly restrictive and do not allow .bat files to be run. In this case either disable or install a better antivirus, or perform a manual driver install.
  • Reception in SDR# seems very poor/receiver is insensitive
    Make sure you have increased the RF gain slider which can be accessed by clicking on the configure button. Also, in poor reception areas using the stock antenna indoors may not be sufficient. First test with the antenna placed up high outside. In some cases with the stock antenna the connection to the antenna can become disconnected in the antenna base causing unexpectedly poor reception. In rare cases if you still cannot receive any strong signals and another radio can, then you may have received a broken dongle and should ask for a replacement.
  • SDR# gives error “Application failed to initialize properly (0xc0000135).  Click OK to terminate.”
    This might mean that you do not have the correct .NET Framework installed.
  • SDR# gives error “Object reference not not to an instance of an object”
    This may mean that you do not have an audio driver properly installed on your PC, or that you do not have any output audio devices enabled. Enable them in the windows Sound Playback properties.
  • The dongle constantly disconnects from the USB port
    First test to make sure that it is not the fault of a dodgy USB extension cable by plugging the dongle directly into the PC. If it still disconnects often the dongle may be faulty and you should ask for a replacement.
  • The dongle won’t connect and the LED does not illuminate on models with an LED
    The dongle is faulty and should be refunded or replaced.
  • It seems that my PC is not powerful enough to run SDR# as it uses near 100% CPU
    For graphical GUI SDR software like SDR#, at least a dual core processor is recommended. If you have a borderline decent CPU and still experience high CPU usage, try reducing the sample rate to 1 MSPS or less, reducing the FFT display resolution (or turning it off), turning off Correct IQ and reducing the filter order.
  • I used zadig but it broke my keyboard/mouse/other device somehow
    This is because you would have clicked the install button in Zadig after selecting the wrong device in the drop down menu. Make sure you select the correct RTL-SDR device, (Bulk-In Interface, Interface 0) first. Zadig overwrites previous drivers. To get the old drivers back you should be able to do so in Windows device manager, update driver software.
  • My R820T2 RTL-SDR shows up as an R820T when I run the diagnostic tool rtl_test
    The R820T2 and R820T are identical electronically except for some minor changes in the maximum IF filter widths that occurred by accident from using higher quality silicon in the R820T2. The accidentally different filters and higher quality silicon may be the reason the R820T2 has generally better performance and less manufacturing variability. Thus a R820T2 will show up as an R820T on the PC, since there is no distinction between them in the digital part of the circuit. You can confirm that you have a R820T2 by checking the markings on the chip.
  • My antivirus shows SDR# as a virus.
    This is almost 100% a false positive. SDR# is updated often and thus a new .zip file is sometimes released almost daily. Poorly designed antivirus programs will sometimes assume that any file that is not downloaded often is a virus. With SDR# being updated so often it takes a while for many people to download the new version and build up trust with the antivirus company.
  • The Mode selection buttons in SDR# are graphically glitching and I cannot click on them.
    Some users have found that this bug is caused due to selection of a “custom scaling level” or “custom sizing options” in Windows. Reset this option back to default in Windows display settings to fix the bug.
  • When closing SDR# I get an error like “An error occurred loading a configuration file: Access to the path ‘C:\Program Files\SDR\s14i12qq.tmp’ is denied. (C:\Program Files\SDR\SDRSharp.exe.Config) —> System.UnauthorizedAccessException: Access to the path ‘C:\Program Files\SDR\s14i12qq.tmp’ is denied.”
    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”.
  • My dongle came with a remote control. What is it for?
    Some sellers opt to include the remote control that is used for changing TV channels. It is only useful for when the dongle is used for its original purpose – as a DVB-T HDTV receiver. The remote control has no purpose when the dongle is used as an SDR.
  • I want to watch DVB-T with my dongle, how do I do it?
    The original purpose of the dongle was for DVB-T TV, and it can still do this. But please note that the DVB-T drivers and the SDR drivers are different, and they cannot both be installed at the same time. You can download the DVB-T drivers here. We recommend using Prog-DVB as the TV software.

If you continue to have issues please feel free to post in the troubleshooting section of our Forums.

How to set the Gain

The gain can be adjusted in SDR# by clicking on the Configure button which looks like a cog. When tuning the RF gain you are trying to get the signal as strong as possible, whilst keeping the noise floor as low as possible. Start with a low gain setting, and slowly increase the gain slider. Watch in the frequency spectrum as the signal strength increases, but stop just before the point at which the noise floor starts to rise.

The noise floor is the part of the frequency spectrum where there are no signals.

SDRSharp Plugins

The official list of SDRSharp plugins can be found here and our unofficial list of plugins can be found here.

SDRSharp Guide

A good guide to learning how to use SDRSharp and what all the options do can be found here. Another great illustrated guide can be found here.

HDSDR Setup Guide (Tested on Win XP and above)

  1. Purchase an RTL-SDR dongle. The cheapest and best for most applications is the R820T/R820T2 dongle. Information on purchasing one can be found here.
  1. Plug in your dongle and do not install any of the software that it came with, but ensure you let plug and play finish trying to install it. If you’ve already installed the software drivers it came with previously, uninstall them first.
  1. Go to http://zadig.akeo.ie/ and download Zadig.
  1. In Zadig, go to Options->List All Devices and make sure this option is checked.
  1. Select “Bulk-In, Interface (Interface 0)” from the drop down list. Ensure that WinUSB is selected in the box next to where it says Driver. (Note on some PCs you may see something like RTL2832UHIDIR or RTL2832U instead of the bulk in interface. This is also a valid selection). (Do not select “USB Receiver (Interface 0)” however).

zadig_3

  1. Click Install Driver. You might get a warning that the publisher cannot be verified, but just accept it by clicking on Install this driver software anyway. This will install the drivers necessary to run the dongle as a software defined radio. Note that you may need to run zadig.exe again if you move the dongle to another USB port, or want to use two or more dongles together.

zadig_warning

  1. Download HDSDR from http://hdsdr.de/, using the download button at the bottom of the page.
  1. Use the installer you just downloaded to install HDSDR.
  1. Go to http://hdsdr.de/hardware.html and download the ExtIO_RTL2832U.dll dll file from the table entry “RTLSDR (DVB-T/DAB with RTL2832) USB” (Direct Link).
  1. Copy the ExtIO_RTL2832U.dll file into the HDSDR install folder which is by default set to C:\Program Files (x86)\HDSDR.
  1. Open HDSDR. You might be asked to select a .dll file. Choose the ExtIO_RTL2832U.dll file you just copied over and then click Open. It is okay if you do not see this screen as long as you have copied the ExtIO_RTL2832U.dll file over properly in the last step.

image017

  1. Choose your output sound card by clicking on the Soundcard button  in the bottom left corner, or alternatively by pressing F5. The only important setting here is the “RX Output (to Speaker)” setting which you should set to your speakers, or desired audio piping software.

image019

  1. Click on the Bandwidth button  or alternatively press F6. Choose an output Sampling Rate of 48000 Hz for general use.

image021

  1. Press Start or alternatively press F2. This will start the SDR.
  1. To set the RTL-SDR sample rate, gain and frequency correction click on the ExtIO button .

image023

  1. To tune to a station, change the Local Oscillator frequency to a frequency near the frequency you are interested in. Then tune to the desired frequency either by clicking in the RF spectrum, or using the Tune numbers.

image024

  1. You can zoom in and out of the spectrum by using the Zoom slider which is to the left of the word zoom.

image025

  1. The mode can be altered by clicking on the mode buttons.

image026

  1. After clicking on the FM mode button, the FM bandwidth can be manually modified with the FM-BW slider.

image027

  1. To listen to a typical wideband broadcast FM station, you will need to change the audio sampling rate to 192000 Hz. Do this by clicking on the Bandwidth button or alternatively by pressing F6 and then selecting the output sampling rate as 192000 Hz.

SDR-RADIO V2 Setup Up Guide (Tested on Win XP and above)

To install SDR-RADIO for the RTL-SDR follow the steps below

  1. Purchase an RTL-SDR dongle. The cheapest and best for most applications is the R820T/R820T2 dongle. Information on purchasing one can be found here.
  1. Plug in your dongle and do not install any of the software that it came with, but ensure you let plug and play finish trying to install it. If you’ve already installed the software drivers it came with previously, uninstall them first.
  1. Go to http://zadig.akeo.ie/ and download Zadig.
  1. In Zadig, go to Options->List All Devices and make sure this option is checked.
  1. Select “Bulk-In, Interface (Interface 0)” from the drop down list. Ensure that WinUSB is selected in the box next to where it says Driver. (Note on some PCs you may see something like RTL2832UHIDIR or RTL2832U instead of the bulk in interface. This is also a valid selection). (Do not select “USB Receiver (Interface 0)” however).

zadig_3

  1. Click Install Driver. You might get a warning that the publisher cannot be verified, but just accept it by clicking on Install this driver software anyway. This will install the drivers necessary to run the dongle as a software defined radio. Note that you may need to run zadig.exe again if you move the dongle to another USB port, or want to use two or more dongles together.

zadig_warning

  1. Download the SDR-RADIO installer from http://v2.sdr-radio.com/Software/Download1.
  1. Use the installer to install SDR-RADIO.
  1. Download the RTL-SDR support package from the link at http://m3ghe.blogspot.com.au/p/adding-support-for-rtl-sdr-usb-dongles.html (MIRROR).
  1. Extract the SDRSourceRTL2832U.dll, rtlsdr.dll and libusb-1.0.dll files from the x64 folder into the C:\Program Files\SDR-RADIO-PRO.com folder. Or if you have a 32-bit PC extract the files from the x32 folder into C:\Program Files (x86)\SDR-RADIO-PRO.com folder.
  1. Open SDR-RADIO. Upon opening it you will be greeted with the Select Radio screen and a prompt saying “List is empty – add radio definition now?” Click Yes. If this prompt does not display, click the + Definitions button.
  1. In the new window open the Search drop down menu and select RTL SDR (USB). After clicking it the RTL-SDR will be added to the Radio Definitions list. Click OK.

image030

image031

  1. Click on the RTL-SDR click to select it, choose your desired sample rate then click Start.

image032

  1. Click on the Span button and adjust the span to the sample rate bandwidth you chose in the last step. This will let you see the whole spectrum.

image033

  1. To change the receive mode use the left menu under the frequency tab. You can also change the signal bandwidth here. NFM signals are typically around 12 kHz wide and broadcast FM is typically around 192 kHz wide.

image034

  1. To adjust the frequency, use the VFO tuning box on the right side. If you don’t see it you may need to click on the VFO tuning tab. Also if the screen is too small you may need to expand it’s size to show it. You can also click on the waterfall to instantly tune to the clicked frequency.

image035

  1. Be sure to adjust the gain settings using the RF gain button in the top which is under the Home tab. By default it is set to automatic.

sdrconsolegain

  1. Also to adjust the waterfall colors so that signals are more clearly seen go to the Display tab up the top and then click on the Automatic Calibration button on the very top right.

sdrconsoleautocal

CubicSDR Set Up Guide (Tested on XP and above)

Warning: CubicSDR is software that is in alpha stages of development. That said, at the moment it is fairly stable and quite easy to set up.

  1. Purchase an RTL-SDR dongle. The cheapest and best for most applications is the R820T/R820T2 dongle. Information on purchasing one can be found here.
  1. Plug in your dongle and do not install any of the software that it came with, but ensure you let plug and play finish trying to install it. If you’ve already installed the software drivers it came with previously, uninstall them first.
  1. Go to http://zadig.akeo.ie/ and download Zadig.
  1. In Zadig, go to Options->List All Devices and make sure this option is checked.
  1. Select “Bulk-In, Interface (Interface 0)” from the drop down list. Ensure that WinUSB is selected in the box next to where it says Driver. (Note on some PCs you may see something like RTL2832UHIDIR or RTL2832U instead of the bulk in interface. This is also a valid selection). (Do not select “USB Receiver (Interface 0)” however).

zadig_3

  1. Click Install Driver. You might get a warning that the publisher cannot be verified, but just accept it by clicking on Install this driver software anyway. This will install the drivers necessary to run the dongle as a software defined radio. Note that you may need to run zadig.exe again if you move the dongle to another USB port, or want to use two or more dongles together.

zadig_warning

  1. Go to cubicsdr.com and go to the downloads page. Find the download link for the latest version. Download the version suitable for your particular version of Windows. 
  1. Run the CubicSDR installer.
  1. Plug in your dongle and run CubicSDR from your start menu.
  1. You will be greeted with a SDR Devices menu. Choose your RTL-SDR from the menu and click on the “Use Selected” button.
  1. CubicSDR will automatically start.
  1. Click anywhere on the waterfall to start listening.

Other SDR Windows Software Compatible with RTL-SDR

See the Software Guide for a big list of other compatible RTL-SDR software.

Getting Started on Linux

Linux instructions for installing the RTL-SDR libraries can be found at http://sdr.osmocom.org/trac/wiki/rtl-sdr. Repeated below is the code:

git clone git://git.osmocom.org/rtl-sdr.git
cd rtl-sdr/
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make
sudo make install
sudo cp ../rtl-sdr.rules /etc/udev/rules.d/
sudo ldconfig

After installing the libraries you will likely need to unload the DVB-T drivers, which Linux uses by default. To unload them temporarily type “sudo rmmod dvb_usb_rtl28xxu” into terminal. This solution is only temporary as when you replug the dongle or restart the PC, the DVB-T drivers will be reloaded. For a permanent solution, create a text file “rtlsdr.conf” in /etc/modprobe.d and add the line “blacklist dvb_usb_rtl28xxu”. You can use the one line command shown below to automatically write and create this file.

sudo echo "blacklist dvb_usb_rtl28xxu" > /etc/modprobe.d/blacklist-dvb_usb_rtl28xxu.conf

Now you can restart your device. After it boots up again run “rtl_test” at the terminal with the RTL-SDR plugged in. It should start running.

After installing the libraries and black listing the DVB-T drivers we recommend starting off with GQRX, a SDR program similar in operation to SDR#. It can be downloaded via the package manager in your Linux distribution or from http://gqrx.dk/download. We can now also recommend the multi-platform CubicSDR which can be downloaded from http://www.cubicsdr.com/.

If you want to install GNU Radio we recommend using Marcus Leech’s script by typing the following into terminal. This installs the RTL-SDR drivers as well.

wget http://www.sbrac.org/files/build-gnuradio && chmod a+x ./build-gnuradio && ./build-gnuradio

Note that if you want to run Linux in a virtual machine it has been reported that RTL-SDR performance with VirtualBox is rather poor due to it’s slow USB connection. VMWare Player on the other hand has good performance – just remember to set the USB controller to use the USB 2.0 protocol as by default it is set to USB 1.1.

Another good Linux quick start guide written by Kenn Ranous can be found here (pdf).

Getting Started on OSX

As there is a severe lack of SDR software for OSX, we recommend using either Linux or Windows. However, GQRX is a SDR program that works well on OSX. Instructions for its installation on a Mac can be found on this post http://www.smittix.co.uk/rtlsdr-up-and-running-in-mac-osx-yosemite-with-gqrx-gnuradio.

We can now also recommend the multi-platform CubicSDR which can be downloaded from http://www.cubicsdr.com/.


For a comprehensive book about the RTL-SDR you may be interested in our book available on Amazon. Available in physical and eBook formats.

The Hobbyist’s Guide to the RTL-SDR: Really Cheap Software Defined radio.

232 comments

  1. RFD

    I tried installing using these instructions to install build 1452 on two different Windows 7 machines, but on both, SDR# would immediately give an error. The details of which said that the Event Name was CLR20r3. I installed C++ 2010 following the above link, but apparently needed to also install C++ 2012. Once I did, everything seems to working ok… I hope this helps someone else from pulling their hair out.

  2. BDB

    I followed instructions exactly for HDSR on a dual boot mac with xp, selected 100.3 on VFO. When I changed the bandwidth for FM broadcast to 192000. It switched from static to 99 Red Balloons. Epic. THANKS.

  3. bob

    when i press play in sdr sharp i get a message that says “paInvalidsamplerate”
    how do i fix this issue

  4. Bill Dillon

    Summary: I’m trying to use the NooElec dongle and SDR# software on a Windows 10 machine, but when I run SDR# and hit the Play triangle, I get a “No device selected” error message. Basically the software is not seeing the dongle.

    Your instructions are nicely detailed, but I got off the Happy Path really quickly. Zadig did not come in the SDR# zip package. However, I did find instructions on how to get it your HDSDR section. Next anomaly: when I opened Zadig, and followed your instructions, I noted that the Driver field was blank, and there was no “Replace Driver” option. There was an “Install” option, I tried that, and WinUSB then appeared in the Driver field. However, when I brought SDR# up, it claimed there was “No Device” selected when I hit the play button.

    Any ideas? I’ll try it all again in the morning with fresh eyes. I suppose I could punt SDR# and try HDSDR. Thanks for any input!

    • admin

      Take another closer look at step 5, I think you must have missed that step completely. That step downloads zadig and the rtlsdr.dll file, which is what your install seems to be missing.

    • walt N5EQY

      I have been wrestiling with his also. I am NOT a PC nerd. But, try installing ZADIG and extl0…file download in step 9 of the HDSDR setup. Use the Mirror site to DL that file and put them all in the HDSDR folder.in your PC.
      I am still wrestling with the frequency input and those two lines that interact. drives me nuts.

  5. John

    Probably asking for refund. I think the device has malfunctions

    Bought the version offered by the blog with a metal case and 2 X Antennas
    Was working ok for a few minutes (windows 7) but after clicking sometimes the buttons “Stop” and “Play” on SDR# i’ve got a problem: I cannot activate the dongle anymore to do any reading, because i get the error message “Cannot Access RTL Device”. It worked for total of about 30 minutes. I dont have a thermometer, but i have the impression the dongle is heating too much. even when not in use (but if connected to the USB)
    I installe the driver again, by using the zadig, but nothing helped my case. installed sdr# again, but nothing happens.

    Decided to install everything at my GF’s computer. the dongle was working fine, (she was windows 8) for about 5 minutes, then, i noticed that all the waterfall was showing only static, or white noise in all the frequencies
    no matter how much i browsed up or down in the frequency range. after that i couldn’t hear any transmission from whatsoever. decided to close and open SDR# again, but after opening it i get some message like “no device selected” after pressing “play” . Tried to install again the driver by using the zadig. but nothing happens. The device stills overheating.
    even when not in use (but connected to USB)
    Installed the SDR# again, but still no solution

    If i cant solve the problem will ask for refund. i think the device is broken

  6. Roshan

    I am try to use “DVBT” dongle. i fallowed the steps very carefully. but it unsuccessful. once i run the zdag.exe, under the dop down, it shows “dvb-t 2”. it doesn’t show bulk-in interface. every thing success when i try to install with dvb-t 2. but with SDRsharp, once i select rtl-sdr-usb, it says no device found. i checked all troubleshooting tips. but still unsuccessful. any comments from your side or any one use this dvb-t dongle.

    (This dongle is bit old for more than 2 years)

  7. Ben

    Everything works for me up until the part where I hit play. I get an error saying no device is selected, but when I go into settings, the drop-down menu for devices won’t even open. I have tried this on 2 computers following the same instructions, one running 10, the other running Vista. Any suggestions?

  8. Chad Taylor

    I have tried my NooElec on 3 different computers now and none of them will make this thing work at all. I cannot get even a transmitter in the same room to be received. I get some crazy static and I can see some forms showing on the waterfall during a transmit. It is crazy!!

  9. FABRIZIO SEVERINI

    Hello, I have this problem:with Zadig.exe: when I right click this file and select “Run as administrator”, I can see ” C:/Users/…:/SDR/Zadig.exe isn’t a valid aplication of Win32″. Why? Can you help me?
    Samsung cpu I5 windows 7.
    Thanks. Fabrizio

  10. Joe

    Hi, I just installed all the steps correctly and had no problems, until I opened SDR# for the first time, and I got a message that says, “There are no Creative audio products installed and running on the system that support ASIO.”

    I have a high-end computer running Windows 7.

  11. Warren

    Hi,
    Thanks for writing such an informative and complete guide, Despite my complete lack of Windoze knowledge I managed with ref to your instructions to set the software up on a fellow amateurs laptop, he is playing with the software with a big smile on his face as I write this.
    Thanks once again.

    • Hugh

      Had same issues with the latest SDR sharp, with Win7 SP1 and the 4.6.1 .NET stuff (zadig works, driver installed, but SDRsharp refuses to see the driver, and gives E4000 as device, and does not see R820T).
      Fortunately, I had an earlier SDRsharp (v 1.0.0.1126) which does not use NET 4.6. Copied over, and all was well again! Using earlier version works every time!
      Conclusion: zadig seems to load driver OK, Problem seems to be between driver and .NET4.6.1..??

    • Hugh

      Thanks Jimmy… this also worked for me..
      “Download the dll’s at http://sdr.osmocom.org/trac/raw-attachment/wiki/rtl-sdr/RelWithDebInfo.zip tmp\RelWithDebInfo.zip and extract the files from the x32 folder into the SDR# folder.”

      Did this, replacing the original files in the directory even through I am running win7 64. The device appears now as “Generic RLT2932U OEM (0) “. One other thing I noticed with the non-working setup, in the configuration setup, with the RTL controller, the name would give a detectable flash every second, as if it was constantly searching. This has now stopped, with “Generic RLT2932U OEM (0)” appearing to not flash.
      Hope these comments are of use to others! good luck everyone.

  12. William C. Corwin

    The RTL-SDR Controller window, which pops up when the configureButton-cog-gear icon
    is clicked on,shows E4000 not the R820T chip which comes with the RTL-SDR Blog
    ‘R820T RTL2832U 1PPM TCXO’ dongle. Also the Device window is blank. Could this
    be why I get an “An error occurred loading a configuration file: Access to the path
    C:\Program Files (x86)\SDRsharp-x86\fmgptr4s.tmp is denied
    (C:\Program Files (x86)\SDRsharp-x86\SDRSharp.exe.Config).” error message?

    • admin

      Sounds like something is very wrong with your SDR# install. Can you try other software like HDSDR or SDR-Console and see if they work? Also what OS, and SDR# version are you using, and did you follow the quickstart guide?

    • Matt

      My device is coming up as E4000 as well but I am getting the “No Device Selected” error. I’ve attempted every fix suggested here and elsewhere with no luck. Running Windows7 64bit. The only source to this problem that I can reasonably assume to be the culprit would be the .net 4.6 being “blocked” from installation. I am going to attempt to track down an older version of SDR# before the 4.6 change and see if that helps.

      • Matt

        *UPDATE* After installing windows updates and the .net 4.6 framework, I continued to receive the “No Device Error”. I decided to try HDSDR instead and was able to install/run successfully. After playing around with HDSDR for a while I went back to SDR# and IT WORKS NOW!
        I suspect Zadig was not able to load the drivers correctly in SDR# but once it was run to install HDSDR it achieved its function. Hopefully this will help some of you that are experiencing this same error.

        • Paul

          I have done everything mentioned:
          1. disabling driver signature enforcement
          2. loading HDSDR
          3. reloading drivers with ZADIG.
          Nothing is working to get SDR# working. I can get HDSDR working, but not SDR#. It continues to show the error “No Device Selected”

          • admin

            Is there a file called rtlsdr.dll inside the SDR# folder? Did you run install-rtlsdr.bat?

            I’ve discovered recently that the error in the OP’s question is related to installing the SDR# files in a read only directory, like in Program Files. This can prevent the install-rtlsdr.bat file from running correctly, and thus the dll files won’t be downloaded. Move the SDR# folder into a non read only folder like in C:\.

            • Pete

              Same here. HDSDR works fine, but SDR# does not. I followed everything above, to the letter, repeated it again, and I still get the “No Device Selected” error.

    • James

      Make sure SDR# is not running. Run ZAdig and click ‘options’ and select list all devices. Then select RTL2838UHIDIR. Next, click on reinstall driver. Once that is done, launch SDR# and try it again. This is what resolved the problem for me. Let me know if this has helped.

    • admin

      1) Did you run install-rtlsdr.bat and confirm that rtlsdr.dll is in your SDR# folder?

      2) Check that you have not accidentally installed a driver with zadig to Bulk Interface 1. If you install a driver to that interface it seems to cause trouble.

  13. manyacarb

    Got the same problem as napalm post, after clicking on play I get “no device selected”. Don’t have older version of SDRsharp but I am looking for that,
    Regards

  14. Napalm

    Got a weird issue. I’ve got an older version of SDR# that works fine, but just today I downloaded the new version of SDR# that was released recently. Now it says “no device selected”. Everything is still fine and working with the old version.

    • admin

      Run install-rtlsdr.bat, the install procedure changed in recent versions. After you’ve run it confirm that it worked correctly by checking if there is an rtlsdr.dll file in the SDR# folder.

    • James

      Make sure SDR# is not running. Run ZAdig and click ‘options’ and select list all devices. Then select RTL2838UHIDIR. Next, click on reinstall driver. Once that is done, launch SDR# and try it again. This is what resolved the problem for me. Let me know if this has helped.

  15. praneeth

    according your quick guide i installed drivers using “zadig.exe”.
    next step in configuration window of sdrsharp application not allowing to select other devices it fixed at E4000.
    when i play the radio there comming a dialog-box with no devices selected.
    please help me to go forward

    • Lynne

      I’m also having this exact same problem. I’ve tried two different laptops and two different dongles on each and it happens every time. I have no idea why because it was working fine last week until someone must have deleted SDR Sharp and I had to reinstall it today.

      Can someone please help?

        • jaake

          Same problem, everything has been installed already few times. Sharp is newest version .1427, zadig has been used for usb-drivers(few times). net4.6 is installed.

          .bat has been used also used few times, there’s something strange with that, it doesn’t seemingly do nothing. In 30 min it doesn’t dl anything in temp-folder or update anything.

          Dongle is dxpatrol mk3, rtl 2838U. Pc is Windows 7 sp1 64bit. There’s also sdr v2 in computer, could it somehow affect to sdrsharp?

          • admin

            Something is very wrong if the bat file stays open for 30 mins. It should open, download the files and then close in under 1 minute. Make sure you’re connected to the internet and that the bat file is not being blocked by a firewall or antivirus program. SDR V2 won’t affect the operation of SDR#.

  16. Sonnie

    My cab company does NOT use Voice transmissions anymore. They send orders on the MDT screen and drivers accepts the orders if they want to.

    I just ordered this RTL SDR dongle. Will i still be able to use it in anyway in my cab ????

    • admin

      If there is a decoder written for your MDT, or you can write one yourself then it is possible. The software called “Taxi MDT Decoder” may already do this for you if your company uses Auriga or Autocab.

  17. Theo Bosch

    Good day,
    If I am off topic, sorry, but I need to know to increase the waterfall/frequency spectrum bandwidth? Currently it is only about 1.5MHz but I would like to increase it up to what the RTL dongle and my pc is capable of, which I believe is substantially bigger. Regards

  18. Kirk

    Thanks for all of the great tutorials! I managed to get my RTL-SDR USB dongle working with SDSharp, HDSDR, and SDRConsole without much trouble at all. When I did goof up, I looked here again and usually found out that I had skipped a listed step in the set-up.

  19. ROSS C.

    I tried using an old and inexpensive terratec dongle, followed the whole instruction and WORK WELL ON WIN 10! (recently free upgraded from win 8).
    I state that dongle worls only as SDR tuner and can’t do tv tuner function at the same time.
    I’m wondering to buy a better antenna, the provided one works well for fm wide commercial stations, but i can’t receive no other signals.
    Wich one is the best prize for bucks?
    Maybe an external discone?
    Someone can answer me?

  20. asdf

    there is problem with current driver for rtl-sdr to connect through window 7. There is another way to connect rtl-sdr manually through window except zadig

  21. Gabriela G

    Hello! I want to log files with RTL1090, but it writes in file with a buffer, and i need it to write in real time, without delay. Can i set this buffer zero?

  22. Goobius

    I am trying to use a KWorld USB Tuner KW-UB435-Q and SDR# says No Compatible Devices. The thing is the drivers successfully installed through Zadig. Is this tuner compatible? Has anyone been able to use it?

    Thanks!

    • admin

      Does that dongle have a RTL2832U chip and compatible tuner inside? I quickly Googled it and it looks like it’s an ATSC receiver – only RTL2832U DVB-T dongles will work.

      Zadig will install drivers on anything, it’s not really a driver, more like a place holder for a custom driver that is provided with the software like with SDR#.

      • Goobius

        Thanks for the response! I had this laying around but I wasn’t able to locate the information you did. Are there other options available for this type of dongle or is this only done on RTL tuners?

  23. On5AM

    Hi,
    I don’t understand why on my laptop, the RTL-SDR dongle works very well. Now on new PC, I can’t see or hear anything? yet I have installed the right key on the new PC. Do you think that the new Os win 7 professional at something to do?
    Help me please ?

    • admin

      There could be a number of reasons. Try some of the suggestions in the troubleshooting section above, even if it isn’t directly for your problem.

      • On5AM

        Tks for reply.
        Sorry, but when I make the choice, I don’t see Bulk-in, Interface (Interface 0) How see it ?

        • MarioMan

          Ensure “Options->List All Devices” is checked and that “Ignore Hubs or Composite Parents” is unchecked. Some people report seeing something else other than the bulk in interface. It may also show up as the brand of your dongle or something prefixed with “RTL”. This option should work too. In rare cases you may receive a faulty dongle that will not show up in Zadig no matter what USB port or computer you try it on. You should ask for a replacement in this case.

  24. Bob

    Well, pretty effective way to consume a lot of hours. Works amazingly well for a $10 investment. Couple issues. I’m no Windows guru but do have a couple decades experience. The Zadig thing for installing the driver. I’ve never had a driver install that weird or that long. I suppose I could look up why but somebody might know offhand.

    Also, it trashed my keyboard driver. Had to reboot to get it back. Mouse kept working. This is on Win7. I think maybe I’ll bring up an older machine for playing with this.

  25. j

    I was thinking of getting one of these dongles but after reading these problems I doubt I will, its a shame im a extra class ham from the old days when you needed to know something about radios and antennas, but like everything else instead of having too work hard, they just make it easier. But the dongles sound like fun, to bad there a pain in the ass to set up.

    • admin

      They’re pretty easy to set up in i’d say 95% of cases, but like with anything to do with computers, when something goes wrong you’ll need decent computer skills to figure it out.

    • Gordonjcp

      So, you’re an oldschool amateur from when people used to have to work at things to get on the air, but you don’t want to put any work into using an RTLSDR?

      Jeez, and people wonder why the hobby is dying, with shining examples like you to look up to…

  26. Daryl Zimmerman

    Please help me I can not install driver on Win 7 Here is zadig log file. Let me know what I am doing wrong! Thanks!

    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\DZ Electronics\usb_driver
    libwdi:info [wdi_prepare_driver] successfully created ‘C:\Users\DZ Electronics\usb_driver\Bulk-In_Interface_(Interface_0).inf’
    libwdi:info [wdi_prepare_driver] Vista or later detected – creating and self-signing a .cat file…
    libwdi:debug [AddFileHash] ‘wdfcoinstaller01011.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\DZ Electronics\usb_driver\amd64\wdfcoinstaller01011.dll’
    libwdi:debug [AddFileHash] ‘winusbcoinstaller2.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\DZ Electronics\usb_driver\amd64\winusbcoinstaller2.dll’
    libwdi:debug [AddFileHash] ‘bulk-in_interface_(interface_0).inf’: INF type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\DZ Electronics\usb_driver\bulk-in_interface_(interface_0).inf’
    libwdi:debug [AddFileHash] ‘wdfcoinstaller01011.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\DZ Electronics\usb_driver\x86\wdfcoinstaller01011.dll’
    libwdi:debug [AddFileHash] ‘winusbcoinstaller2.dll’: PE type
    libwdi:info [ScanDirAndHash] added hash for ‘C:\Users\DZ Electronics\usb_driver\x86\winusbcoinstaller2.dll’
    libwdi:info [CreateCat] successfully created file ‘C:\Users\DZ Electronics\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\DZ Electronics\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:debug [installer process] got parameter Bulk-In_Interface_(Interface_0).inf
    libwdi:debug [process_message] got request for device_id
    libwdi:debug [installer process] got device_id: ‘USB\VID_0BDA&PID_2838&MI_00\6&38A180A5&0&0000’
    libwdi:debug [process_message] got request for hardware_id
    libwdi:debug [installer process] got hardware_id: ‘USB\VID_0BDA&PID_2838&REV_0100&MI_00’
    libwdi:debug [installer process] got user_sid: ‘S-1-5-21-2702922908-2409939420-2157780372-1003’
    libwdi:debug [installer process] using syslog ‘C:\Windows\inf\setupapi.dev.log’
    libwdi:debug [installer process] sylog reader thread started
    libwdi:debug [process_message] switching timeout to infinite
    libwdi:debug [installer process] Installing driver for USB\VID_0BDA&PID_2838&REV_0100&MI_00 – please wait…
    libwdi:debug [syslog] ERROR: Unable to convert log entry to UTF-8
    libwdi:debug [syslog] >>> [Device Install (UpdateDriverForPlugAndPlayDevices) – USB\VID_0BDA&PID_2838&REV_0100&MI_00]
    libwdi:debug [syslog] >>> Section start 2014/11/24 14:27:44.220
    libwdi:debug [syslog] cmd: “C:\Users\DZ Electronics\usb_driver\installer_x86.exe” “Bulk-In_Interface_(Interface_0).inf”
    libwdi:debug [syslog] dvi: Set selected driver complete.
    libwdi:debug [syslog] dvi: {Build Driver List} 14:27:44.237
    libwdi:debug [syslog] cpy: Policy is set to make all digital signatures equal.
    libwdi:debug [syslog] dvi: Processing a single INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] inf: Opened INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:44.248
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = c:\users\dz electronics\usb_driver\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:27:44.319
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:44.319
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = c:\users\dz electronics\usb_driver\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] sig: Success: File is signed in Authenticode(tm) catalog.
    libwdi:debug [syslog] sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:27:44.336
    libwdi:debug [syslog] dvi: Created Driver Node:
    libwdi:debug [syslog] dvi: HardwareID – USB\VID_0BDA&PID_2838&MI_00
    libwdi:debug [syslog] dvi: InfName – c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] dvi: DevDesc – Bulk-In, Interface (Interface 0)
    libwdi:debug [syslog] dvi: DrvDesc – Bulk-In, Interface (Interface 0)
    libwdi:debug [syslog] dvi: Provider – libusbx.org
    libwdi:debug [syslog] dvi: Mfg – Realtek Semiconductor Corp.
    libwdi:debug [syslog] dvi: ModelsSec – libusbxDevice_WinUSB.NTx86
    libwdi:debug [syslog] dvi: InstallSec – USB_Install
    libwdi:debug [syslog] dvi: ActualSec – USB_Install
    libwdi:debug [syslog] dvi: Rank – 0x00ff0001
    libwdi:debug [syslog] dvi: Signer – USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)
    libwdi:debug [syslog] dvi: Signer Score – Authenticode
    libwdi:debug [syslog] dvi: DrvDate – 06/17/2013
    libwdi:debug [syslog] dvi: Version – 6.1.7600.16385
    libwdi:debug [syslog] dvi: {Build Driver List – exit(0x00000000)} 14:27:44.342
    libwdi:debug [syslog] dvi: {DIF_SELECTBESTCOMPATDRV} 14:27:44.342
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface’
    libwdi:debug [syslog] dvi: Using exported function ‘WdfCoInstaller’ in module ‘C:\Windows\system32\WdfCoInstaller01011.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 1 == WdfCoInstaller01011.dll,WdfCoInstaller
    libwdi:debug [syslog] dvi: Using exported function ‘CoDeviceInstall’ in module ‘C:\Windows\system32\WinUSBCoInstaller2.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 2 == WinUSBCoInstaller2.dll
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:44.353
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:44.354
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:44.354
    libwdi:debug [syslog] dvi: {Select Best Driver}
    libwdi:debug [syslog] dvi: Selected driver installs from section [USB_Install] in ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’.
    libwdi:debug [syslog] dvi: Set selected driver complete.
    libwdi:debug [syslog] dvi: Selected:
    libwdi:debug [syslog] dvi: Description – [Bulk-In, Interface (Interface 0)]
    libwdi:debug [syslog] dvi: InfFile – [c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf]
    libwdi:debug [syslog] dvi: Section – [USB_Install]
    libwdi:debug [syslog] dvi: Signer – [USB\VID_0BDA&PID_2838&MI_00 (libwdi autogenerated)]
    libwdi:debug [syslog] dvi: Rank – [0x00ff0001]
    libwdi:debug [syslog] dvi: {Select Best Driver – exit(0x00000000)}
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_SELECTBESTCOMPATDRV – exit(0x00000000)} 14:27:44.358
    libwdi:debug [syslog] inf: {SetupCopyOEMInf: c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf} 14:27:44.359
    libwdi:debug [syslog] sto: {Import Driver Package: c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf} 14:27:44.370
    libwdi:debug [syslog] sto: Importing driver package into Driver Store:
    libwdi:debug [syslog] sto: Driver Store = C:\Windows\System32\DriverStore (Online | 6.1.7601)
    libwdi:debug [syslog] sto: Driver Package = c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sto: Architecture = x86
    libwdi:debug [syslog] sto: Locale Name = neutral
    libwdi:debug [syslog] sto: Flags = 0x00000000
    libwdi:debug [syslog] sto: Copying driver package files to ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}’.
    libwdi:debug [syslog] inf: Opened INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\System32\DriverStore\FileRepository\winusb.inf_x86_neutral_6cb50ae9f480775b\winusb.inf’ ([strings.0409])
    libwdi:debug [syslog] inf: Opened INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘c:\users\dz electronics\usb_driver\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘c:\users\dz electronics\usb_driver’
    libwdi:debug [syslog] flq: SourceFilename – ‘Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘c:\users\dz electronics\usb_driver’
    libwdi:debug [syslog] flq: SourceFilename – ‘bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘c:\users\dz electronics\usb_driver\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {_commit_file_queue}
    libwdi:debug [syslog] flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=4
    libwdi:debug [syslog] flq: {_commit_copy_subqueue}
    libwdi:debug [syslog] flq: subqueue count=4
    libwdi:debug [syslog] flq: source media:
    libwdi:debug [syslog] flq: SourcePath – [c:\users\dz electronics\usb_driver\x86]
    libwdi:debug [syslog] flq: SourceFile – [WinUSBCoInstaller2.dll]
    libwdi:debug [syslog] flq: Flags – 0x00000000
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘c:\users\dz electronics\usb_driver\x86\WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\SETE511.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\SETE511.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘c:\users\dz electronics\usb_driver\x86\WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\SETE522.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\SETE522.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: source media:
    libwdi:debug [syslog] flq: SourcePath – [c:\users\dz electronics\usb_driver]
    libwdi:debug [syslog] flq: SourceFile – [Bulk-In_Interface_(Interface_0).cat]
    libwdi:debug [syslog] flq: Flags – 0x00000000
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘c:\users\dz electronics\usb_driver\Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\SETE523.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\SETE523.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\SETE533.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\SETE533.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copy_subqueue exit OK}
    libwdi:debug [syslog] flq: {_commit_file_queue exit OK}
    libwdi:debug [syslog] pol: {Driver package policy check} 14:27:44.459
    libwdi:debug [syslog] pol: {Driver package policy check – exit(0x00000000)} 14:27:44.459
    libwdi:debug [syslog] sto: {Stage Driver Package: C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\bulk-in_interface_(interface_0).inf} 14:27:44.460
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\System32\DriverStore\FileRepository\winusb.inf_x86_neutral_6cb50ae9f480775b\winusb.inf’ ([strings.0409])
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sto: Copying driver package files:
    libwdi:debug [syslog] sto: Source Path = C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}
    libwdi:debug [syslog] sto: Destination Path = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000010
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000010
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}’
    libwdi:debug [syslog] flq: SourceFilename – ‘Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000010
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}’
    libwdi:debug [syslog] flq: SourceFilename – ‘bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000010
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {_commit_file_queue}
    libwdi:debug [syslog] flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=4
    libwdi:debug [syslog] flq: {_commit_copy_subqueue}
    libwdi:debug [syslog] flq: subqueue count=4
    libwdi:debug [syslog] flq: source media:
    libwdi:debug [syslog] flq: SourcePath – [C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86]
    libwdi:debug [syslog] flq: SourceFile – [WinUSBCoInstaller2.dll]
    libwdi:debug [syslog] flq: Flags – 0x00000000
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\SETE56F.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\SETE56F.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\x86\WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\SETE57F.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\SETE57F.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86\WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: source media:
    libwdi:debug [syslog] flq: SourcePath – [C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}]
    libwdi:debug [syslog] flq: SourceFile – [Bulk-In_Interface_(Interface_0).cat]
    libwdi:debug [syslog] flq: Flags – 0x00000000
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\SETE580.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\SETE580.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\Bulk-In_Interface_(Interface_0).cat’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copyfile}
    libwdi:debug [syslog] flq: CopyFile: ‘C:\Users\DZELEC~1\AppData\Local\Temp\{58ef8610-b5d0-5ba4-ce37-f10a37370f34}\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\SETE591.tmp’
    libwdi:debug [syslog] flq: MoveFile: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\SETE591.tmp’
    libwdi:debug [syslog] flq: to: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: {_commit_copyfile exit OK}
    libwdi:debug [syslog] flq: {_commit_copy_subqueue exit OK}
    libwdi:debug [syslog] flq: {_commit_file_queue exit OK}
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE} 14:27:44.521
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:44.529
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:27:44.549
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:44.549
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] sig: Success: File is signed in Authenticode(tm) catalog.
    libwdi:debug [syslog] sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:27:44.559
    libwdi:debug [syslog] sto: Validating driver package files against catalog ‘Bulk-In_Interface_(Interface_0).cat’.
    libwdi:debug [syslog] sto: Driver package is valid.
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0x00000000)} 14:27:44.570
    libwdi:debug [syslog] sto: Verified driver package signature:
    libwdi:debug [syslog] sto: Digital Signer Score = 0xFF000000
    libwdi:debug [syslog] sto: Digital Signer Name =
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_BEGIN} 14:27:44.571
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sto: Create system restore point:
    libwdi:debug [syslog] sto: Description = Device Driver Package Install: libusbx.org Universal Serial Bus devices
    libwdi:debug [syslog] sto: Time = 15ms
    libwdi:debug [syslog] sto: Status = 0x00000422 (FAILURE)
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_BEGIN: exit(0x00000000)} 14:27:44.580
    libwdi:debug [syslog] sto: Importing driver package files:
    libwdi:debug [syslog] sto: Source Path = C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}
    libwdi:debug [syslog] sto: Destination Path = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372
    libwdi:debug [syslog] sto: {Copy Directory: C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}} 14:27:44.581
    libwdi:debug [syslog] sto: Target Path = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372
    libwdi:debug [syslog] sto: {Copy Directory: C:\Windows\System32\DriverStore\Temp\{7a7c3dfd-1a7d-3a6d-60a9-503bfb188545}\x86} 14:27:44.583
    libwdi:debug [syslog] sto: Target Path = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\x86
    libwdi:debug [syslog] sto: {Copy Directory: exit(0x00000000)} 14:27:44.585
    libwdi:debug [syslog] sto: {Copy Directory: exit(0x00000000)} 14:27:44.586
    libwdi:debug [syslog] sto: {Index Driver Package: C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf} 14:27:44.586
    libwdi:debug [syslog] idb: Registered driver store entry ‘bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’.
    libwdi:debug [syslog] idb: Published ‘bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ to ‘C:\Windows\INF\oem124.inf’
    libwdi:debug [syslog] idb: Published driver store entry ‘bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’.
    libwdi:debug [syslog] sto: Published driver package INF ‘oem124.inf’ was changed.
    libwdi:debug [syslog] sto: Active published driver package is ‘bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’.
    libwdi:debug [syslog] sto: {Index Driver Package: exit(0x00000000)} 14:27:44.797
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_END} 14:27:44.798
    libwdi:debug [syslog] ndv: No system restore point was set earlier.
    libwdi:debug [syslog] sto: {DRIVERSTORE_IMPORT_NOTIFY_END: exit(0x00000000)} 14:27:44.800
    libwdi:debug [syslog] sto: {Stage Driver Package: exit(0x00000000)} 14:27:44.803
    libwdi:debug [syslog] ndv: Doing device matching lookup!
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Saved PNF: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).PNF’ (Language = 0409)
    libwdi:debug [syslog] ndv: Found device that matches new INF!
    libwdi:debug [syslog] sto: Driver package was staged to Driver Store. Time = 827 ms
    libwdi:debug [syslog] sto: Imported driver package into Driver Store:
    libwdi:debug [syslog] sto: Filename = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sto: Time = 889 ms
    libwdi:debug [syslog] sto: {Import Driver Package: exit(0x00000000)} 14:27:45.261
    libwdi:debug [syslog] inf: Opened INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Opened INF: ‘c:\users\dz electronics\usb_driver\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Installing catalog Bulk-In_Interface_(Interface_0).cat as: oem124.CAT
    libwdi:debug [syslog] inf: {SetupCopyOEMInf exit (0x00000000)} 14:27:45.356
    libwdi:debug [syslog] inf: Opened PNF: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:45.359
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:27:45.363
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:45.363
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] sig: Success: File is signed in Authenticode(tm) catalog.
    libwdi:debug [syslog] sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:27:45.377
    libwdi:debug [syslog] dvi: Selected driver installs from section [USB_Install] in ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’.
    libwdi:debug [syslog] dvi: Set selected driver complete.
    libwdi:debug [syslog] dvi: {Plug and Play Service: Device Install for USB\VID_0BDA&PID_2838&MI_00\6&38A180A5&0&0000}
    libwdi:debug [syslog] ump: Creating Install Process: DrvInst.exe 14:27:45.396
    libwdi:debug [syslog] ndv: Infpath=C:\Windows\INF\oem124.inf
    libwdi:debug [syslog] ndv: DriverNodeName=bulk-in_interface_(interface_0).inf:libusbxDevice_WinUSB.NTx86:USB_Install:6.1.7600.16385:usb\vid_0bda&pid_2838&mi_00
    libwdi:debug [syslog] ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] ndv: Building driver list from driver node strong name…
    libwdi:debug [syslog] inf: Opened PNF: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:45.419
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:27:45.450
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE} 14:27:45.451
    libwdi:debug [syslog] sig: Key = bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf
    libwdi:debug [syslog] sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\Bulk-In_Interface_(Interface_0).cat
    libwdi:debug [syslog] sig: Success: File is signed in Authenticode(tm) catalog.
    libwdi:debug [syslog] sig: Error 0xe0000241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
    libwdi:debug [syslog] sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:27:45.460
    libwdi:debug [syslog] dvi: Selected driver installs from section [USB_Install] in ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’.
    libwdi:debug [syslog] dvi: Set selected driver complete.
    libwdi:debug [syslog] ndv: {Core Device Install} 14:27:45.462
    libwdi:debug [syslog] inf: Opened INF: ‘C:\Windows\INF\oem124.inf’ ([strings])
    libwdi:debug [syslog] inf: Saved PNF: ‘C:\Windows\INF\oem124.PNF’ (Language = 0409)
    libwdi:debug [syslog] dvi: {DIF_ALLOW_INSTALL} 14:27:45.472
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [syslog] dvi: Using exported function ‘WdfCoInstaller’ in module ‘C:\Windows\system32\WdfCoInstaller01011.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 1 == WdfCoInstaller01011.dll,WdfCoInstaller
    libwdi:debug [syslog] dvi: Using exported function ‘CoDeviceInstall’ in module ‘C:\Windows\system32\WinUSBCoInstaller2.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 2 == WinUSBCoInstaller2.dll
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.476
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:45.477
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:45.478
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_ALLOW_INSTALL – exit(0xe000020e)} 14:27:45.478
    libwdi:debug [syslog] ndv: Installing files…
    libwdi:debug [syslog] dvi: {DIF_INSTALLDEVICEFILES} 14:27:45.479
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.480
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:45.481
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:45.481
    libwdi:debug [syslog] dvi: {Install FILES}
    libwdi:debug [syslog] inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: Opened PNF: ‘C:\Windows\INF\winusb.inf’ ([strings.0409])
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install]}
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install] exit (0x00000000)}
    libwdi:debug [syslog] inf: {Install Inf Section [WINUSB.NT]}
    libwdi:debug [syslog] inf: CopyFiles=WINUSB.CopyFiles (winusb.inf line 26)
    libwdi:debug [syslog] cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault
    libwdi:debug [syslog] flq: QueueSingleCopy…
    libwdi:debug [syslog] flq: Inf : ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: SourceInf: ‘C:\Windows\INF\winusb.inf’
    libwdi:debug [syslog] flq: SourceSection: [sourcedisksfiles]
    libwdi:debug [syslog] flq: Source root path based on SourceInf
    libwdi:debug [syslog] flq: SourceRootPath: ‘C:\Windows\System32\DriverStore\FileRepository\winusb.inf_x86_neutral_6cb50ae9f480775b’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x01000000
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x01000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Windows\System32\DriverStore\FileRepository\winusb.inf_x86_neutral_6cb50ae9f480775b’
    libwdi:debug [syslog] flq: SourceFilename – ‘winusb.sys’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\system32\DRIVERS’
    libwdi:debug [syslog] flq: TargetFilename – ‘winusb.sys’
    libwdi:debug [syslog] flq: SourceDesc – ‘windows cd’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] inf: {Install Inf Section [WINUSB.NT] exit (0x00000000)}
    libwdi:debug [syslog] dvi: Processing co-installer registration section [USB_Install.CoInstallers].
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install.CoInstallers]}
    libwdi:debug [syslog] inf: CopyFiles=CoInstallers_CopyFiles (bulk-in_interface_(interface_0).inf line 69)
    libwdi:debug [syslog] flq: QueueSingleCopy…
    libwdi:debug [syslog] flq: Inf : ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: SourceInf: ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: SourceSection: [sourcedisksfiles.x86]
    libwdi:debug [syslog] flq: Source root path based on SourceInf
    libwdi:debug [syslog] flq: SourceRootPath: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’
    libwdi:debug [syslog] flq: SourcePath – ‘\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\system32’
    libwdi:debug [syslog] flq: TargetFilename – ‘WinUSBCoInstaller2.dll’
    libwdi:debug [syslog] flq: SourceDesc – ‘Bulk-In, Interface (Interface 0) Install Disk’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: QueueSingleCopy…
    libwdi:debug [syslog] flq: Inf : ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: SourceInf: ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’
    libwdi:debug [syslog] flq: SourceSection: [sourcedisksfiles.x86]
    libwdi:debug [syslog] flq: Source root path based on SourceInf
    libwdi:debug [syslog] flq: SourceRootPath: ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY}
    libwdi:debug [syslog] flq: CopyStyle – 0x00000000
    libwdi:debug [syslog] flq: SourceRootPath – ‘C:\Windows\System32\DriverStore\FileRepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372’
    libwdi:debug [syslog] flq: SourcePath – ‘\x86’
    libwdi:debug [syslog] flq: SourceFilename – ‘WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: TargetDirectory- ‘C:\Windows\system32’
    libwdi:debug [syslog] flq: TargetFilename – ‘WdfCoInstaller01011.dll’
    libwdi:debug [syslog] flq: SourceDesc – ‘Bulk-In, Interface (Interface 0) Install Disk’
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] flq: {FILE_QUEUE_COPY exit(0x00000000)}
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install.CoInstallers] exit (0x00000000)}
    libwdi:debug [syslog] dvi: Co-installers registered.
    libwdi:debug [syslog] dvi: {Install INTERFACES}
    libwdi:debug [syslog] dvi: Installing section [USB_Install.Interfaces]
    libwdi:debug [syslog] dvi: {Install INTERFACES exit 00000000}
    libwdi:debug [syslog] dvi: {Install FILES exit (0x00000000)}
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_INSTALLDEVICEFILES – exit(0x00000000)} 14:27:45.506
    libwdi:debug [syslog] ndv: Pruning file queue…
    libwdi:debug [syslog] dvi: {_SCAN_FILE_QUEUE}
    libwdi:debug [syslog] flq: ScanQ flags=620
    libwdi:debug [syslog] flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    libwdi:debug [syslog] flq: SPQ_SCAN_FILE_COMPARISON
    libwdi:debug [syslog] flq: SPQ_SCAN_ACTIVATE_DRP
    libwdi:debug [syslog] flq: ScanQ number of copy nodes=3
    libwdi:debug [syslog] flq: File ‘C:\Windows\system32\DRIVERS\winusb.sys’ pruned from copy.
    libwdi:debug [syslog] sig: Using catalog ‘C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514.cat’.
    libwdi:debug [syslog] cpy: DrpSetRegFileProt ‘C:\Windows\system32\DRIVERS\winusb.sys’ Status=0 Class=Inbox Windows protected
    libwdi:debug [syslog] flq: File ‘C:\Windows\system32\WinUSBCoInstaller2.dll’ pruned from copy.
    libwdi:debug [syslog] sig: Using catalog ‘C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem110.CAT’.
    libwdi:debug [syslog] flq: {SPFILENOTIFY_CABINETINFO}
    libwdi:debug [syslog] flq: {SPFILENOTIFY_CABINETINFO – exit(0x00000000)}
    libwdi:debug [syslog] flq: {SPFILENOTIFY_FILEEXTRACTED}
    libwdi:debug [syslog] flq: {SPFILENOTIFY_FILEEXTRACTED – exit(0x00000000)}
    libwdi:debug [syslog] ! sig: VerifyTrustFailed for C:\Windows\system32\WinUSBCoInstaller2.dll.
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] cpy: DrpSetRegFileProt ‘C:\Windows\system32\WinUSBCoInstaller2.dll’ Status=0 Class=OEM Legacy
    libwdi:debug [syslog] flq: File ‘C:\Windows\system32\WdfCoInstaller01011.dll’ pruned from copy.
    libwdi:debug [syslog] sig: Using catalog ‘C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem110.CAT’.
    libwdi:debug [syslog] ! sig: VerifyTrustFailed for C:\Windows\system32\WdfCoInstaller01011.dll.
    libwdi:debug [syslog] ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    libwdi:debug [syslog] cpy: DrpSetRegFileProt ‘C:\Windows\system32\WdfCoInstaller01011.dll’ Status=0 Class=OEM Legacy
    libwdi:debug [syslog] flq: ScanQ action=200 DoPruning=32
    libwdi:debug [syslog] flq: ScanQ end Validity flags=620 CopyNodes=0
    libwdi:debug [syslog] dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    libwdi:debug [syslog] ndv: Committing file queue…
    libwdi:debug [syslog] flq: {_commit_file_queue}
    libwdi:debug [syslog] flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    libwdi:debug [syslog] flq: CommitQ early exit: No nodes are queued
    libwdi:debug [syslog] flq: {_commit_file_queue exit OK}
    libwdi:debug [syslog] ndv: Registering CoInstallers…
    libwdi:debug [syslog] dvi: {DIF_REGISTER_COINSTALLERS} 14:27:45.605
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.606
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:45.607
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:45.608
    libwdi:debug [syslog] inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install.CoInstallers]}
    libwdi:debug [syslog] inf: AddReg=CoInstallers_AddReg (bulk-in_interface_(interface_0).inf line 68)
    libwdi:debug [syslog] inf: {Install Inf Section [USB_Install.CoInstallers] exit (0x00000000)}
    libwdi:debug [syslog] dvi: {DIF_DESTROYPRIVATEDATA} 14:27:45.614
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.615
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:45.615
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:45.617
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_DESTROYPRIVATEDATA – exit(0xe000020e)} 14:27:45.617
    libwdi:debug [syslog] dvi: Co-installers registered.
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_REGISTER_COINSTALLERS – exit(0x00000000)} 14:27:45.618
    libwdi:debug [syslog] ndv: Installing interfaces…
    libwdi:debug [syslog] dvi: {DIF_INSTALLINTERFACES} 14:27:45.619
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [syslog] dvi: Using exported function ‘WdfCoInstaller’ in module ‘C:\Windows\system32\WdfCoInstaller01011.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 1 == WdfCoInstaller01011.dll,WdfCoInstaller
    libwdi:debug [syslog] dvi: Using exported function ‘CoDeviceInstall’ in module ‘C:\Windows\system32\WinUSBCoInstaller2.dll’.
    libwdi:debug [syslog] dvi: CoInstaller 2 == WinUSBCoInstaller2.dll
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.622
    libwdi:debug [syslog] dvi: CoInstaller 1: Exit
    libwdi:debug [syslog] dvi: CoInstaller 2: Enter 14:27:45.623
    libwdi:debug [syslog] dvi: CoInstaller 2: Exit
    libwdi:debug [syslog] dvi: Default installer: Enter 14:27:45.624
    libwdi:debug [syslog] dvi: {Install INTERFACES}
    libwdi:debug [syslog] inf: Opened PNF: ‘c:\windows\system32\driverstore\filerepository\bulk-in_interface_(interface_0).inf_x86_neutral_e59bab95f8973372\bulk-in_interface_(interface_0).inf’ ([strings])
    libwdi:debug [syslog] dvi: Installing section [USB_Install.Interfaces]
    libwdi:debug [syslog] dvi: {Install INTERFACES exit 00000000}
    libwdi:debug [syslog] dvi: Default installer: Exit
    libwdi:debug [syslog] dvi: {DIF_INSTALLINTERFACES – exit(0x00000000)} 14:27:45.626
    libwdi:debug [syslog] ndv: Installing device…
    libwdi:debug [syslog] dvi: {DIF_INSTALLDEVICE} 14:27:45.627
    libwdi:debug [syslog] dvi: No class installer for ‘Bulk-In, Interface (Interface 0)’
    libwdi:debug [syslog] dvi: CoInstaller 1: Enter 14:27:45.634
    libwdi:debug [syslog] inf: Opened PNF: ‘C:\Windows\INF\oem124.inf’ ([strings])
    libwdi:debug [process_message] switching timeout back to finite
    libwdi:debug [installer process] unhandled error 422
    libwdi:debug [process_message] installer process completed
    Driver Installation: FAILED (Other error)
    12 devices found.

  27. Paul

    “No connection could be made because the target machine actively refused it 127.0.0.1:1234” That’s the message I get when pressing Play on SDR#1.0.0.1318

  28. Petri Toivonen

    install.bat is giving me file not found error. Every other batch file works normally. I’m using W7x64 FI.
    What to do?

  29. Brian

    I run 4 dongles and 2 upconverters on one computer. I use SDRSHARP ,SDR V2, and HDSDR and SEEDER.
    I have had no trubles with this. each one is on a seperate screen ,I have to load them in this way ,,(1) Sdrsharp (2)
    Sdr v2, (3) HDSdr , (4) SeeDer .. Conected to USB on computer ..Useing ship plotter and plane plotter at same time .. So Far so good .. It went wrong when I first started but sorted it out ,,

  30. mike

    Howdy
    I have 2x $9 dongles on one pc ( w7x64 ) working extremely well
    I can run two instances of SDR# and use both concurrently, it’s sweet

    some things I’ve noticed:
    My setup works only when both dongles are connected directly to the usb ports on the desktop,
    1. it doesn’t work very well through a (good quality) usb 2 hub with one or two dongles , despite re-running zadig etc, the dongle/s are detected and drivers look fine but SDR# says they are busy 🙁
    2. DSD+ VIA Vac is working beautifully!!!! plenty of p25 around me, salt cops are encrypted but it’s nice to run one dongle in analog mode and the other into vac to shop up the digital
    3. The sweet thing is I’ve found a broad band Mast head rf preamp with multiple outputs and even with my discone sitting inside my tin shed both tuners get great reception – use a preamp people
    4. Use the frequency scanner mod, it’s freaking awesome particularly with the above setup

    I’m currently looking for a way to run both dongles perhaps from raspberry pis or something

    I’m using good quality rg6 and f connectors etc

    I love sdr#

    mike

    • Dale

      I also had a similar problem with the device being detected but SDR# giving a device is busy error. This was on a computer (laptop) it had worked on in the past. Finally I unplugged ALL other USB devices and it worked fine. I think this is a power issue. If your getting the device is busy error, try removing all other USB devices, and/or a powered USB hub.

    • Gary

      Hi
      I have a question. I would like to start this is a great product it works great. I wanted to get creative and buy a usb to IP converter. It allows me to attach hard drives, webcams and other devices to a USB port them place it on the network. I thought I could set one up by the antenna and be able to go anywhere in the house with the laptop or even use port fordward to send it out across the Internet. The usb to ip device is working correctly with all other devices it even recognizes the NooElec. When I try to connect I receive “no RTLSDR devices found” has anyone else tried this and been successful. It is an SIIG USB over IP converter.
      Thanks for any advice gary.

      • admin

        Not sure if that will work. Most people who do remote dongles use a Raspberry Pi or similar at the antenna, and use that to stream data over the network.

        • Gary

          Thanks for the quick reply. I have been researching the raspberry pi for another project I may pick one up. If I have any luck with the USB to ip converter I’ll post an update.
          Thanks again
          Gary

  31. Alfredo Azcona

    Help:
    I can’t install the driver on windows 7.
    I run zadig in administrator mode
    I had the message:
    Using inf name: Bulk-In_Interface_(Interface_0).inf
    Successfully extracted driver files.
    Installing driver. Please wait…
    libwdi:error [install_driver_internal] installer failed to respond – aborting
    Driver Installation: FAILED (Operation timed out)
    6 devices found.
    tks

  32. Dennis

    I used the latest Zadig to set the drivers for my Nooelec USB device. It all seems to work but when I load SDR-RADIO version 2.2 from the site, there is no pulldown under Search called RTL SDR (USB) There is only the RTL SDR (TCP). What am I doing wrong. Also I tried to load version 2.1 and twice it said there was a virus in the down load. There is something different between it and Version 2.2 that was first loaded.
    Thanks.

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>