Dead Pro Stick?

This problem is specific to Windows 10.

Try your Pro Stick on a Computer with Windows 8.1 or Windows 7. If the ProStick is OK, it should show in these versions of Windows (after you install driver Zadig).

If the ProStick does not shown in Win 7 or Win 8 also, then most likely it is defective.

You are right, but sometimes Windows 10 picks an imaginary garbage device as device #0, and real device (ProStick or DVB-T) as dvice #1.

As the decoder software look for device #0 by default, these cannot find a device. The workaround is to change device=0 to device=1 in settings of decoder software.

1 Like

The seller has given wrong info.

.

  1. Did you click menu item Options, and placed a check mark besides “List All Devices”?

    .
    zadig-2

    .

  2. When at stage shown in screenshot below, if in the drop down box you dont see RTL2838UFA, look for and choose Bulk-In, Interface (Interface 0). Make sure that WinUSB is selected as the target driver and click on Reinstall Driver.

    zadig-3

Yes. I did. I followed the instructions.

And it still did not show RTL2832UFA, STRANGE!!!

I have just now tested on my Windows 10 Laptop, and it shows the Pro Stick as RTL2832UFA


.

Going back a step (you may have done this, but it doesn’t make it clear in your first post). When you insert the dongle does it show in Windows Device Manager at all? My Pro Stick Plus shows just as a RTL2832U (not a UFA).

If its not showing in device manager or Zadig, then its looks more like a defective dongle.

I have launched device manager and looked into the USB devices list…is not there. I took out an RTLSDR dongle I have laying around, plugged it into the same pc and it does show up so, I’m leaning towards the PS being bad. Wrote again to the seller, hopefully I’ll get a reply sometime today.

Good luck; hopefully he was just mistaken in the wrong info he gave you.

@belzybob
@gcopter

Just to test, I simultaneously plugged-in one Generic DVB-T and one Pro Stick in Windows 10 Laptop on which Zadig is not yet installed.

  1. None of the two Dongles were shown in Device Manager.
  2. In task bar, Only the Generic DVB-T (RTL2838U) was listed, but was dimmed out, and only the Infrared Remote Receiver appeared as active. The reason is that generic DVB-T is supplied with an IR remote control receiver, while Pro Stick does not have the IR receiver.

Click on screenshot below to see larger size.
First click on image will moderately enlarge it.
Second click on image will show full size image.

I did the same test and found them both shown under “USB Serial Bus Devices” not under “USB Serial Bus Controllers”. Its the same on both of my Windows 10 PCs.

DM

@belzybob

My Windows 10 laptop did not display “USB Serial Bus Devices” category. It displayed only “USB Serial Bus Controllers" category. May be this is because the screenshot is from the Win10 laptop on which Zadig is NOT installed.

Is your screenshot from a Win10 laptop on which Zadig has been installed?

Tonight I will plug DVB-T and Pro Stick in the other Win10 laptop on which I have installed Zadig, and see if these are shown in the Device Manager and the Taskbar

As the OP has already said that he had installed drivers with Zadig, it seemed more relevant to the actual situation to check with it in-situ.

Yor are right, will do it tonight and post results.

@belzybob
@gcopter

Tested by installing Zadig.
Had to install TWICE,
In first installation, selected RTL2832UFA (=Pro Stick)
In second installation, selected Bulk-In, Interface (Interface 0) (=DVBT)

.
Zadig installation step for ProStick
zadig installation for ProStick

.
Zadig installed for ProStick.
Note that Device Manager is showing only RTL2832UFA (Pro Stick)
Task bar is showing only RTL2832UFA, and RTL2838UHIDIR (DVBT) is dimmed, and its HID Infrared Remote Control Receiver is shown as the detected device

.
Zadig installation step for DVBT
zadig installation for DVBT

.
Zadig installed for ProStick + for DVBT
Note that Device Manager is showing both RTL2832UFA (Pro Stick) and Bulk-In, Interface (DVBT)
Task bar is also showing both RTL2832UFA, and RTL2838UHIDIR (DVBT)

Its strange that you have so many issues with the RTL devices, maybe I’m just lucky with both Windows machines.

Anyway, hopefully @gcopter will have enough info now to confirm one way or the other that his dongle is working or not.

Hey all, thanks for your replies. Currently I’m in the process of returning the stick to the seller. I have no other Windows laptop to test it. I have followed all the instructions you provided and there’s no sign of the stick showing up anywhere. I have an RTL2832 dongle that I use routinely with the same laptop with no problems whatsoever. Because I currently live in an apartment, I plan to install the ProStick along with a Raspi 3 up in the attic. Whenever I get the new ProStick back, I’ll repost here the results. I’m convinced the one I’m returning is defective.

This is the blue one, the Pro Stick.

@gcopter
@belzybob

As we are in the subject of using ProStick on Windows, following thread will be useful reference:

Installation of Pro Stick on Windows

The 2nd post of this thread describes method of installation & configuration of following:

(A) Driver Zadig

(B) Following Receiver-Decoder Software:

  • dump1090 (Malcolm Robb) for Windows
  • ModeSDeco2
  • RTL1090
    .

@Dxista
@gcopter

I have both the ProStick (orange) and ProStick Plus (blue). Both work OK with Windows and Pi.

There is no difference between the blue and orange ones as far as interface with Windows & Pi is concerned. The difference is in the RF stage where blue has a filter, and orange does not have a filter, but this difference in no way affects interface with Windows or PI.

Both blue and orange are in use for about two years now.

I have noticed both in WindoZe 7 and 10, clean installation, and driver option automatic download
the rtl-sdr device is been detected as a sound device and in device manager is under ‘Sound’ not "USB’.
a. change the setting for manual driver installation ( Never… etc.)
b. uninstall the device under ‘Sound’ and then unplug it.
c. re-plug the device and this time will show as Bulk-in interface. from there you follow the tutorials ref zadig etc.

driverinf

i am sure though under win 10 will be a lot more complicated…

a quick check for a dead device : plug it in , if there is no sound (beep) and no detection bottom right in task bar, then there is something wrong with the device.

HTH / brgds / Evangel

1 Like