Joullescope not connecting to computer

[mliberty]

Great! Blue means that both Joulescopes are being enumerated by Windows.

A few more questions:

1. When you start the Joulescope UI, do they both turn green on the misbehaving computer setup?
2. Are you plugging these Joulescopes directly into the host computer? Avoid USB hubs, docks, and adapters. Unpowered USB hubs are particularly problematic for the JS110 and JS220 which only run down to 4.8 V or so. The JS320 can run down to 4 V, but it still takes most of a single USB 2 port of power.

We have had other drivers claim Joulescopes on Windows for unknown reasons. Joulescopes automatically request the built-in WinUSB driver using Microsoft OS Descriptors, but software can override this. Once overridden, Windows “remembers” it for that device. You can try out this PowerShell script to restore the default drivers:

Joulescope UI does not connect to JS220

Hi @yokoyama and welcome to the Joulescope forum! It definitely sounds like you have the same issue with libwdi incorrectly claiming the Joulescope JS220. Did you try the solution at the bottom of that forum topic? Open PowerShell, and then copy this in: Start-Process powershell -ArgumentList { foreach ($dev in Get-PnpDevice -Class 'USBDevice' -FriendlyName '*Joulescope*') { pnputil /remove-device $dev.InstanceId } pnputil /scan-devices } -Verb runAs Does this fix the problem?