Fix Spark 40 / MINI / GO / NEO Firmware Update on Windows 25H2 (Microsoft MIDI Tool)

Applies only to Windows users who upgraded to version 25H2 (or later) from an earlier Windows version and are unable to update the firmware on Spark 40, Spark MINI, Spark GO, or Spark NEO. If your computer shipped with Windows 25H2 already installed (or was clean-installed with 25H2), this workaround may not work as expected.

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?

  1. Press Win + R (hold the Windows key and press R).
  2. Type winver and press Enter.
  3. 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

  1. Open https://github.com/microsoft/MIDI/releases in your browser.
  2. In the Assets section of the top release, click the file ending in _Tools_x64.exe (e.g. Windows_MIDI_Services_Tools_x64.exe).

GitHub releases Assets section showing Tools_x64.exe

This is an official tool from Microsoft. Pick the Arm64 version only if your PC uses an ARM processor (rare - e.g. some Surface Pro X / Copilot+ PCs). For more details, see Microsoft's How to change the MIDI API Mode.

Step 2: Install the Tool

  1. Find the .exe in your Downloads folder.
  2. Right-click → Run as administrator, click Yes on the permission prompt.
  3. Accept the license, click Next → Install → Finish.

Right-click the downloaded .exe and select Run as administrator

Running as administrator ensures the installer can set everything up properly.

Step 3: Open "MIDI Troubleshooting and Repair"

  1. Click the Windows Start button.
  2. Type MIDI Troubleshooting, then click the MIDI Troubleshooting and Repair app.

Windows Start menu with MIDI Troubleshooting typed in the search box


Step 4: Switch to Legacy MIDI Mode

  1. Click API mode on the left side of the app.
  2. Select Legacy MIDI.
  3. Click Yes when the app offers to restart Windows.

MIDI Troubleshooting and Repair - API mode page with Legacy MIDI selected

Nothing changes until you restart - you're always in control of the timing.

Step 5: Update Your Spark Firmware

After Windows restarts in Legacy MIDI mode, run the firmware updater for your product as usual:

If the update still fails in Legacy mode, contact Support with your product model, Windows version, and the exact error message.

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:

  1. Open MIDI Troubleshooting and Repair again.
  2. Click API mode → select Windows MIDI Services.
  3. Restart Windows.
The default mode supports newer features (Network MIDI, Bluetooth LE MIDI, MIDI 2.0, multi-client) that Legacy mode doesn't. Recommended for anyone using a DAW with lots of MIDI tracks.

FAQ

Q: Can I stay on Legacy MIDI?
A: Yes, if you only use Spark over USB. Switching back is recommended if you use a DAW with many MIDI tracks or newer MIDI 2.0 devices.
Q: Is Microsoft's MIDI tool safe?
A: Yes - it's an official signed app from Microsoft, hosted on their official GitHub repository. The admin prompt is required because MIDI mode is a system-wide setting.
Q: The update still fails after switching to Legacy mode. What now?
A: Open a Support ticket with your product, Windows version, and error details.

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:

  1. 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.

  2. 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.

Still need help?
Our support team can help answer questions and solve problems.
Contact Support