On Windows 11 25H2, Spark 40 / MINI / GO / NEO firmware updates may stall or fail. Your Spark hardware and its current firmware are working normally - the issue is in how Windows 25H2 handles USB MIDI.
This guide walks through a workaround: switch Windows to Legacy MIDI mode, update the firmware, then switch back.
Before You Start
Is your computer on Windows 11 25H2?
- Press Win + R (hold the Windows key and press R).
- Type
winverand press Enter. - A small dialog appears. Look at the Version field.
If it shows Version 25H2 (OS Build 26100 or higher), this guide applies to you. If you're on 24H2 or earlier, firmware updates should work normally - no workaround needed.
Step 1: Download Microsoft's MIDI Tools
- Open https://github.com/microsoft/MIDI/releases in your browser.
- In the Assets section of the top release, click the file ending in
_Tools_x64.exe(e.g.Windows_MIDI_Services_Tools_x64.exe).
Step 2: Install the Tool
- Find the
.exein your Downloads folder. - Right-click → Run as administrator, click Yes on the permission prompt.
- Accept the license, click Next → Install → Finish.
Step 3: Open "MIDI Troubleshooting and Repair"
- Click the Windows Start button.
- Type
MIDI Troubleshooting, then click the MIDI Troubleshooting and Repair app.
Step 4: Switch to Legacy MIDI Mode
- Click API mode on the left side of the app.
- Select Legacy MIDI.
- Click Yes when the app offers to restart Windows.
Step 5: Update Your Spark Firmware
After Windows restarts in Legacy MIDI mode, run the firmware updater for your product as usual:
- Spark 40 - Firmware Update Guide
- Spark MINI - Firmware Update Guide
- Spark GO - Firmware Update Guide
- Spark NEO - Firmware Update Guide
Step 6: Switch Back to the Default Mode (Recommended)
Once the firmware update is successful, switch Windows back to the default Windows MIDI Services mode:
- Open MIDI Troubleshooting and Repair again.
- Click API mode → select Windows MIDI Services.
- Restart Windows.
FAQ
If This Workaround Doesn't Work
If switching to Legacy MIDI mode still doesn't allow the firmware update to complete, here are two alternatives:
Option 1: Stay on Your Current Firmware
Your Spark ships with a recent firmware version. Recent firmware updates contain minor bug fixes and improvements only - no critical functionality is missing on earlier versions. If you don't have an urgent need to update, staying on your current firmware is a valid choice. The Spark app will continue to connect and work with your Spark normally.
Option 2: Use a Different Computer
The Spark firmware updater still works normally on:
- Windows 10
- Windows 11 version 24H2 or earlier
- macOS 10.13 or later
Running the updater on any of those systems will let you update your Spark today.
Background: What Changed in Windows 11 25H2
The Spark firmware updater communicates with your amp over USB MIDI. During an update it detects the connected Spark, switches it into bootloader (update) mode, then transfers the new firmware file.
Windows 11 version 25H2 introduced a redesigned MIDI subsystem that changes how third-party audio tools - including firmware updaters - communicate with USB MIDI devices. The result for the Spark firmware updater:
- The updater becomes unresponsive after device detection
- Spark is not recognized in bootloader mode
- The update stalls or fails partway through
Two behaviors in particular affect firmware updaters that use USB MIDI:
-
MIDI device enumeration is more sensitive to timing. The new subsystem responds differently when an application repeatedly checks the list of connected MIDI devices in rapid succession. Firmware updaters that poll the device list tightly can hit timing conditions that cause the update to stall.
-
Connection handling when the device reboots. When your Spark reboots into firmware update mode, the active MIDI connection is lost. The previous MIDI subsystem automatically reconnected on every message send, which masked this disconnect. The new multi-client architecture does not do this by design (removing the per-message reconnect is intentional for performance and multi-client support), so a firmware updater that does not explicitly re-open the connection after the reboot cannot complete the transfer.
Switching to Legacy MIDI mode routes MIDI through the previous subsystem for the duration of the firmware update, which does not have these behaviors. Switching back to the default Windows MIDI Services mode after the update restores the newer architecture's features for everyday use.