Windows 7 Install ... once more :/

[alt]

Hello together,

First post here, but reading since I got my Axo in February -- I really like your community

I just setup a Windows 7 64 System on my Laptop, since some driver issues with other hardware didn't really work out under Linux (I'd prefer that, but well..).

So I happily saw release 1.0.12-2, downloaded and installed as usual; no matching PID/VID. Bummer.

I read thoroughly existing threads with similar topics, but the suggested methods do not work. I can further rule out a faulty cable or faulty Axo, since both work on the linux partition of the very same machine without a hitch.

The actual problem:

Windows will recognize both Axo-Devices, but the axo-patcher still won't find the unit.

I tried:

• replacing the driver for Axo Bulk IF with Zadig (Zadigversion from Axo_Runtime and newer version from Website)
  => no change. Substituting libusb-drivers works "for windows", since it will show in the device manager under "libusb**-devices", but still PID/VID-error in axo-patcher.
• Installing the compatible drivers mentioned before (winusbcompat) for the Bulk IF
  => no change. Recognized by windows as "WinUsb 1.0", but PID/VID-error in axo-patcher.
• Booting to Flashrescue.
  That one is interesting since it works as described here up to the point where the axo-patcher will not detect any DFU-device. (Windows recognizes the ST*-device and lets me change drivers accordingly.)
• Booting with s2 held down to remove any sdcard-weirdness (I understood that this could help, but can't find the thread right now).

I tried all of the above also with release 1.0.12 to no avail.

The laptop is a Lenovo Thinkpad (e535), the chipset from AMD; I removed the Lenovodrivers and let Windows-Update get its generic driver for the USB-Host, still nothing.

To me this reeks of a weird cornercase of driverfu**ckups under win, but I am out of my wits. Any of you guys got some idea?

Thanks & Keep up the good work,
-alt

[azaxo]

It looks a little bit like a problem I had although I worked under windows 10 not under windows 7.

[SOLVED] Not accesseable : driver not installed

Together with Johannes I secured that this was not an error in the Core but an issue with the hardware or driver installation in Windows. After some extensive searching I was able to find a solution to the problem, although we could not find the cause. If you should experience the same issue: In Windows 10 move your mouse over the windows logo in the left bottom. Right click and choose Device manager. At the bottom you will find under USB Device's "Axoloti Bulk Interface". Right click and choo…

[sevo]

As @azaxo said, remove the driver. If that does not help, uninstall it. If that still does not help, scour the system for USB-serial drivers and bulk interfaces and remove all of them (or better yet, move them to quarantine). Just about every piece of flash-upgradeable hardware does install similar drivers, where some may be incompatible, and a few rogue ones claim every vaguely related device.

[alt]

Thank you for your feedback @azaxo @sevo, but in the meantime since my op I bent down and installed Win10, although I'd have loved to avoid that...I guess there is always some little sacrifice to make.

[ghostly606]

Seems like there are a few threads outlining issues with Windows 7 and device drivers which have been a help to me as I had the same issue, i.e.:

After trying numerous other fixes, my process for circumventing this is as follows (WHICH I NEED TO REPEAT EACH AND EVERY TIME I RECONNECT THE AXOLOTI OR REBOOT MY LAPTOP). I've only tried this with 1.0.12 but it may work for 1.0.12-2 (if anyone tries, please report back):

1. With the Axoloti connected go to Star Menu/Devices and Printers, select the Axoloti Core and Hardware/Properties/Drivers and then select uninstall
   
   
2. Disconnect and reconnect the Axoloti Core via USB and wait for the drivers to reinstall (it may try and install a driver for a USB Composite Device which should fail):
   
   If this happens retry (by disconnecting and reconnecting) until the Axoloti Core and Axoloti Bulk Interface drivers install successfully:
   
3. Navigate to C:\Program Files (x86)\axoloti_runtime\platform_win and run zadig_2.1.2.exe
4. Go to Options and select List All Devices then select the Axoloti Bulk Interface and replace the driver listed with the WinUSB option:
   

Once complete, restart the patcher and your Axoloti should be recognised and work as intended!

NOW DON'T DISCONNECT UNLESS YOU WANT TO REPEAT THIS WHOLE PROCESS! I've got it down to a couple of minutes every time I start up so it's not too painful.

@thetechnobear - Any chance you can add this to the installation instructions for Windows as a workaround for those experiencing this issue on Windows 7? (or add a link)

[thetechnobear]

After trying numerous other fixes, my process for circumventing this is as follows (WHICH I NEED TO REPEAT EACH AND EVERY TIME I RECONNECT THE AXOLOTI OR REBOOT MY LAPTOP).

this should not be necessary....

we have had it working on windows 7, and some users still use it, they are not jumping thru these hoops each time, afaik .

have you read thru this post....

Win 7 no usb found with matching PID/VID

Hoi. I recieved my axoloti yesterday. The software reports a problem with the driver and can not connect, DId the installation as told in the guide. Axoloti core is visible in Win 7 Device Manager, The software found no matching PID/VID., when i try to connect. (USB is connected off course and the lights on the board blink at start up) When i choose select device, it sees the axo core and the usb port, at CPU ID it reads: not available: driver not installed. Re-installing the driver did…

particularly the winusbcompat part,
as you can see from the above post, the issues is that often down to particular hardware- so unfortunately, when users have issues under windows often the solution is different for each of them - that post, and the common installation post (user guide) contains what we have found useful...

[ghostly606]

particularly the winusbcompat part

Yes, tried that. There are about 5 posts with this problem with various suggestions as to a solution, and I've tried them all. Would welcome a permanent fix mind you.

[ghostly606]

Perhaps I should elaborate a little further... the Axoloti Core appears under Devices and Printers:

But it (or the Axoloti Bulk Interface) doesn't appear as a device when I select properties or in Device Manager or zadig. Here the only options I have are USB Root Hub or USB Composite Device or something like that (sorry I am not at my home computer at the moment to check). The ONLY way I have been able to get Axoloti Core or Axoloti Bulk Interface to appear in Zadig, etc is to do the uninstall / reinstall routine I described above. And only then will the patcher recognise it.

[sevo]

Is that a fresh setup, or is there other software installed? Zadig is a tool used to reclaim generic USB ports from excessively greedy drivers - so you obviously have one of the latter on the computer, and will have to figure out which soft- or hardware it came with.

[ghostly606]

It was a fresh setup when I first endeavoured to sort this out but since I have installed drivers for the following other bits of gear. I generally only ever plug in one at a time though to change the control settings as I use the MIDI controllers with my Organelle or iPad rather than the laptop which is used as a Pd / Axoloti patcher machine:

• Korg Nanokontrol 2
• Arturia Keystep
• CME XKey
• Novation Launchpad
• USB mouse

[alt]

((monitoring this thread in case I can add something of value))

[thetechnobear]

unfortunately (!?) I don't have a windows 7 box, so hard to know what to suggest...
id say its a driver conflict but which will depend on your machine, what drivers you installed, what you machine required (for built-in devices)…

(this is why for lots it works flawlessly, and for others its a nightmare)

the fact the usb composite driver is failing to install, would be a red flag, for me, ... perhaps a red herring, or perhaps related.
I assume you have installed all the latest service packs for window 7?

other than that is normal windows driver troubleshooting, remove as many drivers as you can, only have one device plugged in, make sure you have all the latest drivers possible... check the event logs for anything that looks like an error/unusual , or even try a fresh windows install.
( I know, I hate it too... but with driver conflicts, there are not a lot of options, until you know which 2 are conflicting and why)

honestly, personally, id move to windows 10, perhaps the reinstall will clear the issue because one of the drivers causing issues has been updated.... but of course that's far from a guarantee … and potentially costly if you don't already have a windows 10 license.

[ghostly606]

I appreciate the issue with respect to all the different drivers and whatnot so many thanks for the suggestions!

I assume you have installed all the latest service packs for window 7?

Yes, I've done this.

try a fresh windows install

I would try this but not got an installation disk, bought my laptop refurbished on eBay with a fresh install already on it (apparently).

id move to windows 10

I may do this in future but not got an install disk and for now I am relatively happy following the workaround I outlined above which is 100% reliable for me.

[alt]

Still utterly annoying to repeat this procedure over and over - I'd try a reinstall as @thetechnobear recommends. Long shot: some faulty hardware regarding the laptop can be fully ruled out? (There is nothing more brainf***ing than HW that is faulty but gives the impression of being fine. Rare thing, but not impossible)

[ghostly606]

I'd try a reinstall as @thetechnobear recommends

I've no means to do a reinstall unfortunately.

[Fonoport]

Hi all,

this is my first post here.

Today I got my Axoloti board, but too bad - I am unable to set it up on My Win 7 Pro 64bit system; there seem to be a problem with Axoloti Bulk interface - ist is not recognized (or a driver for it has not been found?).

I read some suggestions about how to solve it, tried to deinstall the Axoloti and re-install it, but always the same issue.

And - sorry - I'm not going to move to Windows 10 now and I'm not going to reinstall my whole system!
Because there are reasons to keep my setup as it is and Axoloti was told to run under Windows 7 fine.

So guys would you please let me know, how to proceed? I'd appreciate it indeed!

Thanks in advance!

FP

[Fonoport]

Updated:

The problem seems now to be solved, due to rather esotheric (but really effective) suggestion by ghostly606:

Navigate to C:\Program Files (x86)\axoloti runtime\platform_win and run zadig_2.1.2.exe. Go to Options and select List All Devices then select the Axoloti Bulk Interface and replace the driver listed with the WinUSB option.

just, in my case there wasn't any driver listed on the left hand side at all.

I started the patcher now and it indicates, that Axoloti is connected.

FP