The new MIDI stack is not just a new driver, it’s a complete rewrite of everything under the covers.
This issue is similar to the Resolume one, though. In that one, I had to change from the older MIDI 1 driver to our newer MIDI 2+1 driver USBMidi2-ACX. Once I did that, and ensured the names were what the Resolume files were looking for, it all worked.
This was last night, so I don’t have an understanding of the actual cause yet. It was clear that all required messages were going out and with the right values. I considered it might be a speed issue, but I don’t have a simple way to throttle just yet (I’d need to throw in a delay and then run that private build)
The full instructions for the Resolume Arena / APC mini mk2 workaround are on the Discord server under #workarounds-and-instructions . You can try those with the x-touch here as well.
Thanks Pete. I’ll give it a try and report back. If that doesn’t work, I think my best bet is to report the issue on the Discord page and continue there where it’s easier to swap screenshots etc.
According to Microsoft, the following were missing: KB5082417, KB5083769, and KB890830.
And bam! → the errors were back.
then I uninstalled the two KB508XXXXX updates, and now everything is working again after uninstalling KB5083769. I’ve postponed updates again for four weeks.
It’s possible that it’s still listed as installed in the update history even though I uninstalled KB5079473 . This history is strange → sorry for the misinterpretation.
I’ve had exactly the same confusion about which updates affected it and which didn’t - it’s really much more difficult to pin it down than it seems! Thanks for updating - it’s a great help. I think everyone’s script is broken with full updates at the moment. I’ll keep trying to find a solution with Pete’s help.
Out of interest, which version of Windows 11 are you currently at? (type ‘winver’ in the search bar to find out)
I am one happy bunny. I have a fully updated Windows 11 PC, with Bjoluc’s script running my X-Touch and extender perfectly! All buttons working, all scribble strips displaying correctly, All clearing, with faders back to zero when quitting the project.
Of course, I can’t take any credit - It’s all down to Pete:
It works for Bjoluc’s script and the X-touch too! Thanks a million, @Psychlist1972 !
Pete’s listed full instructions on his Discord page, but here’s what I did:
Open Device Manager, and expand the node ‘Sound, video and game controllers’
Right-click on ‘X-Touch’ and select ‘Update Driver’
Click on ‘Browse my computer for drivers’
Click on ‘Let me pick from a list of available drivers on my computer’
Select ‘USBMidi2-ACX’ and click ‘Next’
Repeat for the Extender, ‘X-Touch-Ext’ if you have one.
Close and restart your PC
Notes:
If you can’t see USBMidi2-ACX, you’ll have to update your PC first.
Switch your X-Touch and any extenders off and on in case they are still locked up before launching Cubase.
There remains one minor issue, but I think it’s the fault of Cubase, not Windows. I’ll detail it in a separate post.
So here’s the new issue I’ve found since switching to the new MIDI 2+1 driver USBMidi2-ACX. It doesn’t affect operation so far, but it is curious.
When you close a project and open a different one (I’m using Cubase 15), The faders first jump to the positions they had in the previous project, then jump again to the correct positions for the new project. Weird. It only happens if you open a different project without completely quitting Cubase first. It seems like some cache data somewhere is not getting cleared.
I’d be interested to hear if anyone else has this minor issue?
Fantastic ! Ihad exactly the same issue, i followed the instructions you have given, and … Everything works perfectly. My windows is updated, and my Xtouch is updated and fonctional. Thanks a lot guys.
One really annoying thing for Windows 11 users if you use the updated driver fix above to solve this issue. Every time it updates, Windows 11 automatically reverts to the old drivers and the issue returns! You then have to manually update the drivers again as I’ve described above.
I’m attempting to get around this problem by going into System>Advanced system settings>Hardware>Device Installation Settings and selecting ‘No’ to ‘Do you want to automatically download manufacturer’s apps for your devices?’.
We’ll see if it works, but it’s a real hack. The old driver it reverts to is a Windows driver, not a manufacturer’s app, and normally I would want Windows to automatically download them.
If anyone knows a way to prevent Windows form rolling back just the driver for the X-Touch (and nothing else), I’d love to hear it. In the meantime, I’ll let you know if this works for the next update.
Note: I’ve heard that MS is going to fix this issue in 26H2, but so far, that’s just an aspiration.
I assume you have the devices connected during the update, and have not been moving them between ports on, say, a USB hub.
If you right-click the device itself in device manager, and choose properties, do you see any “failed to migrate …” type of messages in the events?
The settings should carry over. I get a new OS install every week, and the settings, including the selected driver, have been sticky. This may be related to comments from others about device ids changing under certain circumstances.
Edit: I see you also posted on the Discord server. Thanks. We can continue the discussion there.
Having had a rethink, I’ve decided against preventing automatic downloads of all manufacturer’s apps for my devices. It’s too all-encompassing! I just want to prevent specific drivers from reverting: the X-Touch and X-Touch extender ones.
This can be carried out via Group Policy for Pro users and through the Registry for Home users. There’s a good description of how to achieve this here:
Hi doctorlaz, hi everyone,
After the latest Windows 11 update, I had to reinstall the drivers again :-((. During the process, one of the two refused to install the ‘USBMidi2-ACX’ driver (throwing an error saying the driver couldn’t start and marking it with an exclamation point). However, after restarting everything, it did end up loading the driver after all.
To: Pete
Microsoft
Is this going to happen again with every update, or will it be fixed in the next one? What is the current status?
We asked the USB plug & play team if there’s any way to keep drivers. They said this should only happen on an OS upgrade, not an update, but reports like this are showing otherwise.
Do you recall which update it was? Maybe you see a KB number in your update history?
BTW, I only stumbled on this out of luck. I don’t go searching for my name, so if you need me to see something, please @ mention me. Or even better, mention me on the MIDI Discord (which is also the only forum I check from my phone). Thanks.
Hi Pete @Psychlist1972, unfortunately the USB plug & play team are mistaken. The drivers are getting reset on every monthly update. For June in my case, the updates applied were KB5094126 and KB5097148, both listed as ‘Security Updates’.
The driver rollback doesn’t only apply to the X-touch either. It also occurred on my Nektar CS12 and Softube Console 1 mk III controllers. Hope this helps.
All the best, Paul
ps. I’m responding on this forum rather than the discord one because that thread has stalled awaiting the USB PnP team’s response. Perhaps you could update that one?
Hi Pete, here are the requested files—thanks for asking:
Security update (KB5094126) (26200.8655)
.NET Framework security update (KB5087051)
Both updated on June 17, 2026.
P.S.: Regarding the fact that I didn’t address you with an “@” tag—it wasn’t really crucial to me exactly when you read this. It works fine either way, though having to switch drivers afterwards is a bit of a hassle.
If you have a moment, before you have other updates installed, can you share with me a zip of the setupapi log files?
C:\windows\inf\setupapi.\*
I’ll share that with the pnp team. This behavior is unexpected. Maybe we did something incorrectly with this in MIDI, or perhaps there’s something else going on.