Win 7 no usb found with matching PID/VID

windows
#21

cool, great to hear (perhaps not for you frowning ) , but means we don't have a general issue smile

if your having issues with a few devices, yeahs its possibly time for a change...

one thing you could try, is using a different usb hub, as they are 'not all equal',
I'd recommend a USB 2.0 powered MTT hub, I use a this one Pluggable MTT Hub, the important thing is it support MTT, which unfortunately is not often stated. (this one uses the Terminus FE1.1SB chipset which has MTT)

It may or may not solve the problem, as we don't know what the issue with the hub is... but its a useful hub to have around anyway when dealing with multiple USB 1.x devices (I got it due to my Virus, and have been very happy with it)

(Just to be clear to others, we have no reported issues with using hubs etc, this issue sounds it could be a 'one-off', but we will monitor)

Anyway, really glad to hear, that you are up and running with Axoloti, and can start exploring its depths ... enjoy saxophone

#22

Apparently Windows Update does not provide the driver on XP, Vista and Windows 7.
Use winusbcompat.zip, which I added here: https://github.com/axoloti/axoloti/releases
Extract, and point windows to the extracted location when it asks for a driver after plugging in.

Windows 8 and later do not need it.

Common installation problems
#23

Hi
I have the same problem but nothing to do...

I have Windows 7 32 bits

Axoliti program is intalled to C:\Program Files\Axoloti
Runtime is installed to C:\Program Files\axoloti_runtime\platform_win

Axoliti program start but message is "No available USB device found with matching PID/VID
search path : objects
finished loading objects"

When I plug my board (I tried on powered USB hub and directly PC desktop each time, and all USB devices unpluged) , red and green LED flashed but Windows doesn't see it. Zadig doesn't see it too.
After I tried to plug in DFU mode, with S1, no LED lightning, Windows doesn't see it. Zadig doesn't see it too...
There is another way to update firmware ? (I have STK500 v1 and Pocket AVR Programmer from Spakfun)

#24

Could you try a different USB cable?
Does the green LED stay on and the red LED stay off after blinking?
There is no AVR on Axoloti, STK500 or pocket AVR won't do anything.

#25

Wow !!!
I tried with another USB cable, I bougth it at the same time of the first one and now, Axoliti Core works !!!
I don't know why because the first one works with my smartphone, I try it again with Axoliti Core, it doesn't work ???

Update is good too with Axoliti app

Thanks to you for your very quick reply wink

#26

You'd be surprised how many times there are faulty cables...
One thing, (actually I will add this to FAQ), its VERY common that microUSB cables you have knocking around the house, are charging cables only... this is because, these are often supplied with phones etc. that don't need data, but need power.
(first time I plugged in Axoloti I had exactly this problem, as Id unknowingly used a cable I used for my PI2 for power)

#27

With bad USB cable, after red and green blinking, green LED doesn't stay on, with good cable, green LED stay on.
Thanks again

#28

Hi,

I had the same problems (and the same OS configuration) here, and I used the USB cables received with my two Axoloti Core boards.
I'll try to substitute the cables, but...

#29

The issue with @1_over_f_noise's setup was caused by an old driver on a USB 3.0 Host Controller by Renesas (those are quite rare), and resolved by upgrading the host controller driver. The symptoms: everything looking fine in device manager, but no detection of the presence of a board at all in the Axoloti software.
Thanks @1_over_f_noise for nailing the cause!

#30

I can't get it working on win7 here, in device manager the Axoloti is showing up under "Sound video and game controllers" when I launch the editor I get the Firmware ID showing and in the text box I get:

USB device found
not accesseable : driver not installed
USB device found
not accesseable : driver not installed
No available USB device found with matching PID/VID

I opened Zadig and it is showing up there as "Axoloti Bulk Interface (Interface2)" and driver is shown as "WinUSB (v6.1.7600.16385)"

I have tried another USB port (both on my laptop, no hubs) I have tried removing in device manager and re-installing. I have also tried 3 different USB cables.

I noticed once when re-installing the driver after removing it that the Axoloti appeared under "Universal Serial Bus Devices" as "Axoloti" and was not in the "Sound video and game controllers" anymore. I have since re-installed again and it is back there now.

Any ideas? This is doing my head in, wasted 2 evenings that should have been spent making noises instead on swearing at my laptop :smile:

Thanks

#31

Tried again then did the exact procedure in the second post of this thread and it now works :relaxed:

Big issue to install the soft and the drivers
#32

I have the same problem on a Lenovo w520 Axoloti-core runs fine in linux 64 bits.
However, in Windows 7 64bits with same cables and setup it doesn't connect.

So I updated the usb 3.0 host controller but nothing changed.
Axoloti 1.0.10-0gf8e51d-dirty message: No available USB device found with matching PID/VID

Solved, after renesas USB3.0 Host driver update, the Zadig WinUSB one click solution in comment #2 and a reboot.
Axoloti boards now working in Linux Elementary Freya 64bits and Windows 7 64bits

#33

i am experiencing the very same issues as at the start of the topic, but i can't seem to install the driver (without WCID) :frowning:

os: newly installed win 7 pro x64 (installed all updates upto today)

it always detects it as a device with WCID, and axoloti can't find the device (No available USB device found with matching PID/VID)

any suggestion what i could do? (i tried every driver provided by Zadig)

even device in DFU mode is recognized by windows, but not by axoloti... :frowning:

EDIT: problem solved, the problem had to do with usb ports. i've put it in another port and it suddenly worked :smiley:

#34

For future reference
Windows drivers (winusbcompat.zip) required for versions prior to windows 8 can be found here.
https://github.com/axoloti/axoloti/releases/tag/1.0.6

#35

I just got a new board today, Dec 6. I got the same error, so I tried this fix. The board is now alive and there are strange sounds filling the room.

#36

USB port mon sees this:
File:
Driver key name: {36fc9e60-c465-11cf-8056-444553540000}\0110
Device instance ID: USB\VID_16C0&PID_0442\002800293435511733353932
Device hardware ID: USB\VID_16C0&PID_0442&REV_0200
Device service: usbccgp
Device friendly name:
Device location: Port_#0005.Hub_#0001
Device physical object name: \Device\00000134
Device descriptor
USB: 0x0200
Device class: 0xEF
Device subclass: 0x02
Device protocol: 0x01
Max packet size: 0x40 (64)
Vendor: 0x16C0 (Van Ooijen Technische Informatica)
Product ID: 0x0442
Device ID: 0x0200
Manufacturer: 0x01 (Axoloti)
Product: 0x05 (Axoloti Core)
Serial number: 0x03 (002800293435511733353932)
Number of configurations: 1
Connection status: Device connected
Current config value: 0x01
Device bus speed: Full (USB 1.1, 12 Mbit/s)
Device address: 0x11
Open pipes: 4
but the axoloti exe still complains:
USB device found
not accesseable : driver not installed
USB device found
not accesseable : driver not installed
Please Help!

#37

Had a "no usb found-problem" with WIN10, tuns out that G-DATA (antivirus) blocked the device.
Happy i can patch again. : ) : ) : )

#38

I got this error as well when I first tried to connect the board and run the app. turned out that I was using a damaged cable.

#39

wow just had to do this.

Been using axoloti without issue on this windows machine (8.1) for ages - swapping around 3 of them and lately a bit more often since the whole OLED extravaganza. All axos are on same firmware, 2 are identical board revisions.

Plug in one this morning - no cpu PID/VID message. Plug in other, axo editor connects no issue. Checked wiring and everything with the hardware mods - nothing helped. Bit the bullet and went the Zadig route - Axo Bulk Device shows WinUSB driver 6.3XXX . Replaced it with 6.1, the nonworking board works again. The other one too. Funky