[Hackrf-dev] Windows Woes

[Chris Meta]

Hi all..

My name is Chris, and I come before you with a baffling problem.

My HackRF One (and my NooElec Nano2+) quit working under Windows 7. They
still work (to the extent I've learned to utilize them at this point) on 2
different Linux machines. The HackRF has the 2017.02.1 firmware on it,
which I upped it to sometime early this year.
These WERE working Windows. I don't know exactly when or what happened, but
at some point *both* devices - at the same time - just quit being
recognized by software. GnuRadio/GRC, Sdr.Comv2/v3, HDSdr, all of it.
Neither the HRF-O nor the Nano2+, in any USB port, in any application, work.

At some point, hackrf_info went from saying no HackRF was present to
throwing a dialog "The procedure entry point libusb_strerror could not be
loicated in the dynamic link library libusb-1.0.dll."
(I believe that is part of the driver from Zadig, no?) Nothing shows up in
the Windows Event Viewer logs when this happens, so I'm buggered for where
to look next. I actually was at that point approximately the moment I
discovered that the devices weren't being recognized by the software, but I
do TRY to clean up my own messes, Read That Fine (if often
incomprehensible) Manual, recheck my work, try to remember what mistakes I
might have made, cross-check with other hardware and software, "Ask Dr.
Google" etc, but I think I've got those bases well-covered five times over
and I'm at wit's (and patience's) end I I just want the friggin' thing to
work so I can get back to my radio hobby. I got tired of my computer hobby
when this problem beat me.

Anyone got any ideas? I'd be grateful...

[CJ Hicks]

I don’t know if it helps or not but I recently had a similar issue on a Win7 Pro machine where all my USB devices just disappeared including my mouse and keyboard. This was not with a Hack-RF since I have a dedicated Linux box for that work but it was similar. It originally presented after a reboot following updates from MSFT. I initially blamed some recently installed software for a USB device but ultimately it turned out to be an Intel driver that needed to be re-installed after the update package. It was the Intel USB 3.0 extensible host controller ver 5.0.4.43 that fixed my issue. Good luck.



From: HackRF-dev [mailto:hackrf-dev-***@greatscottgadgets.com] On Behalf Of Chris Meta
Sent: Monday, May 28, 2018 2:14 PM
To: hackrf-***@greatscottgadgets.com
Subject: [Hackrf-dev] Windows Woes



Hi all..



My name is Chris, and I come before you with a baffling problem.



My HackRF One (and my NooElec Nano2+) quit working under Windows 7. They still work (to the extent I've learned to utilize them at this point) on 2 different Linux machines. The HackRF has the 2017.02.1 firmware on it, which I upped it to sometime early this year.

These WERE working Windows. I don't know exactly when or what happened, but at some point *both* devices - at the same time - just quit being recognized by software. GnuRadio/GRC, Sdr.Comv2/v3, HDSdr, all of it. Neither the HRF-O nor the Nano2+, in any USB port, in any application, work.



At some point, hackrf_info went from saying no HackRF was present to throwing a dialog "The procedure entry point libusb_strerror could not be loicated in the dynamic link library libusb-1.0.dll."

(I believe that is part of the driver from Zadig, no?) Nothing shows up in the Windows Event Viewer logs when this happens, so I'm buggered for where to look next. I actually was at that point approximately the moment I discovered that the devices weren't being recognized by the software, but I do TRY to clean up my own messes, Read That Fine (if often incomprehensible) Manual, recheck my work, try to remember what mistakes I might have made, cross-check with other hardware and software, "Ask Dr. Google" etc, but I think I've got those bases well-covered five times over and I'm at wit's (and patience's) end I I just want the friggin' thing to work so I can get back to my radio hobby. I got tired of my computer hobby when this problem beat me.



Anyone got any ideas? I'd be grateful...

[Dominic Spill]

Post by Chris Meta
My name is Chris, and I come before you with a baffling problem.
My HackRF One (and my NooElec Nano2+) quit working under Windows 7. They

still work (to the extent I've learned to utilize them at this point) on 2
different Linux machines. The HackRF has the 2017.02.1 firmware on it,
which I upped it to sometime early this year.

Post by Chris Meta
These WERE working Windows. I don't know exactly when or what happened,

but at some point *both* devices - at the same time - just quit being
recognized by software. GnuRadio/GRC, Sdr.Comv2/v3, HDSdr, all of it.
Neither the HRF-O nor the Nano2+, in any USB port, in any application, work.

Post by Chris Meta
At some point, hackrf_info went from saying no HackRF was present to

throwing a dialog "The procedure entry point libusb_strerror could not be
loicated in the dynamic link library libusb-1.0.dll."

Post by Chris Meta
(I believe that is part of the driver from Zadig, no?) Nothing shows up

in the Windows Event Viewer logs when this happens, so I'm buggered for
where to look next. I actually was at that point approximately the moment I
discovered that the devices weren't being recognized by the software, but I
do TRY to clean up my own messes, Read That Fine (if often
incomprehensible) Manual, recheck my work, try to remember what mistakes I
might have made, cross-check with other hardware and software, "Ask Dr.
Google" etc, but I think I've got those bases well-covered five times over
and I'm at wit's (and patience's) end I I just want the friggin' thing to
work so I can get back to my radio hobby. I got tired of my computer hobby
when this problem beat me.

Post by Chris Meta
Anyone got any ideas? I'd be grateful...

Hi Chris,

This certainly sounds like a USB driver issue on the Windows 7 system as
it's affecting multiple pieces of hardware and both work on Linux.

Going through the things that you've already tried:
- have you removed and reinstalled the Zadig driver?
- was there a recent Windows update that could have caused this?
- is it just those two USB devices?

Thanks,
Dominic