spider remote Spider V Remote not detecting Spider V on Windows 11 25H2 – SOLUTION FOUND!

[sysdroid98]

I was having the exact same problem described in this thread with my Line 6 Spider V30 MkII.

After a Windows 11 update, Spider V Remote stopped detecting the amplifier and showed:

"No Device Connection"

The USB connection itself was working correctly: the Spider V was still recognized as an audio interface and worked normally with the ASIO drivers. I also tried:

• Different USB cables

• Different USB ports

• Reinstalling the Line 6 drivers

• Reinstalling Spider V Remote

• Older versions of Spider V Remote

• Running as administrator

• Compatibility mode

• Factory resetting the amplifier

Nothing worked.

My system is:

• Windows 11 25H2

• OS Build 26200.9168

• Feature Experience Pack 1000.26100.344.0

• Line 6 Spider V30 MkII

The solution

The problem appears to be related to the new Windows MIDI Services stack introduced in recent versions of Windows 11.

Microsoft provides a compatibility option called Legacy MIDI API Mode, which allows older MIDI applications/devices to use the previous Windows MIDI stack.

 

I enabled it by adding the following registry value:

1. Open Registry Editor (regedit.exe)

2. Go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

3. Create a new DWORD (32-bit) Value named:

UseLegacyMidi

4. Set its value to:

1

5. Restart Windows.

After rebooting, I opened Spider V Remote, connected my Spider V30 MkII, and it immediately detected the amplifier and worked normally again.

So if your Spider V Remote suddenly stopped detecting your amplifier after a Windows 11 update, especially on Windows 11 25H2, I strongly recommend trying this before replacing cables, reinstalling drivers, or resetting the amplifier.

Important

This does not appear to be a problem with the USB audio functionality itself. In my case, ASIO/audio continued working normally while Spider V Remote could not communicate with the amplifier.

I have not seen an official Line 6 statement confirming this specific compatibility issue, but the timing and symptoms strongly point to the changes in Windows MIDI Services.

If this fixes the problem for you as well, please report your Windows version/build and Spider model in this thread. Hopefully we can establish whether this affects Spider V users broadly and give Line 6/Microsoft enough information to address it.

Edit: To undo the workaround, you can change UseLegacyMidi back to 0 or remove the registry value and restart Windows.

[sysdroid98]

If you need more information about, please visit the microsoft github Knowles base

 

https://microsoft.github.io/MIDI/kb/how-to-change-api-mode/