[Klaus M]

Hi everyone,
I’d like to share an issue that may affect anyone using MIDI devices on Windows 11, especially MobileSheets, USB‑MIDI keyboards, or other MIDI‑dependent apps.

After installing the Windows 11 Preview Update KB5074105 (January 2026), all my MIDI connections in MobileSheets suddenly stopped working.
Windows still detected my keyboard in Device Manager, but the UWP/WinRT MIDI interface was broken, so MobileSheets could no longer access any MIDI devices.

Symptoms:

• MobileSheets shows no MIDI devices
  
• Keyboard is visible in Windows but not in apps
  
• MIDI routing layer appears corrupted
  

Fix: 
I uninstalled KB5074105, and immediately all MIDI connections started working again.
Note: 
The update will still appear in the Update History — that’s normal.
What matters is that it no longer appears under Installed Updates.

Posting this in case others run into the same issue. Preview updates can be unstable, and in this case KB5074105 clearly caused a MIDI subsystem failure.

Best regards,
Klaus

[Telstar]

Ive just updated my Backup computer with  KB5074105 and no problems with MIDI or anything else so far, but after your experience I will hold off on updating my main Computer for a while - thanks :-)

[Tony Lawton]

Hi everyone,
I’d like to share an issue that may affect anyone using MIDI devices on Windows 11, especially MobileSheets, USB‑MIDI keyboards, or other MIDI‑dependent apps.

After installing the Windows 11 Preview Update KB5074105 (January 2026), all my MIDI connections in MobileSheets suddenly stopped working.
Windows still detected my keyboard in Device Manager, but the UWP/WinRT MIDI interface was broken, so MobileSheets could no longer access any MIDI devices.

Symptoms:

• MobileSheets shows no MIDI devices
  
• Keyboard is visible in Windows but not in apps
  
• MIDI routing layer appears corrupted
  

Fix: 
I uninstalled KB5074105, and immediately all MIDI connections started working again.
Note: 
The update will still appear in the Update History — that’s normal.
What matters is that it no longer appears under Installed Updates.

Posting this in case others run into the same issue. Preview updates can be unstable, and in this case KB5074105 clearly caused a MIDI subsystem failure.

Best regards,
Klaus

Hi Klaus
Just wondering whether you sorted your problem. I have the same issue.

Regards
Tony

[PhotoDoc05]

Hi everyone,
I’d like to share an issue that may affect anyone using MIDI devices on Windows 11, especially MobileSheets, USB‑MIDI keyboards, or other MIDI‑dependent apps.

After installing the Windows 11 Preview Update KB5074105 (January 2026), all my MIDI connections in MobileSheets suddenly stopped working.
Windows still detected my keyboard in Device Manager, but the UWP/WinRT MIDI interface was broken, so MobileSheets could no longer access any MIDI devices.

Symptoms:

• MobileSheets shows no MIDI devices
  
• Keyboard is visible in Windows but not in apps
  
• MIDI routing layer appears corrupted
  

Fix: 
I uninstalled KB5074105, and immediately all MIDI connections started working again.
Note: 
The update will still appear in the Update History — that’s normal.
What matters is that it no longer appears under Installed Updates.

Posting this in case others run into the same issue. Preview updates can be unstable, and in this case KB5074105 clearly caused a MIDI subsystem failure.

Best regards,
Klaus

Hi Klaus
Just wondering whether you sorted your problem. I have the same issue.

Regards
Tony

Same issue here with the Update.  No communication with Mobile Sheets via MIDI.  Uninstalled the Update, but STILL no communication.   So, went to MIDI Settings, and toggled to Generic Device, then back again to Genos / PSR ---- and it worked again.    I'm not going to install the Update at this point, but I would suggest if someone has a problem after the Update, try toggling the MIDI setting in Mobile Sheets to see if it resets properly, and let us know if it worked.  Otherwise, uninstall the Update, and you may still have to toggle the MIDI setting.  
Regards and Good Luck,  Jerry

[Klaus M]

Hi, all,
still no communication from Genos2 to MobileSheets (MS) by hitting a song registration on my G2-display. 
I have an ACER Aspire 5 notebook for MS and based on my Co-Pilot AI App I used, it was stated as ACER renumerates each time a linked USB-device and MS needs tu use a fixed ID.
... btw, I discussed this item with Mike Zuber by mail, he is informed, but a fix for it is not available at this moment.
W11 internal MIDI rules saves the last device ID number as hidden. That hidden "Ghost" entry within the W11 device-Manager (is not active) is used by MS if the keyboard is linked to the notebook via USB. Therefore, Genos2 has no communication via MIDI to MobileSheets. If you mark a song in MS, the sheets are opended, but not by hitting a registration on the G2 display
I tried feeled "thousands" of possible ways to solve the problem. 
At the end I am so confused and frustated and it is a pity about no success till now. Many days, many many hours.
There were ideas for example to use a USB 2.0 hub adapter (with an own controller on board, important!), but after many trials no success at all. I tried different other ways and the Co-Pilot Ai helped to find a structured way, but at the end, no rfesult.
I would be grateful for any helpful other ideas.

Toggling MobileSheets MIDI Device to "Generic" didn't help.

[Telstar]

This maybe worth a try - Some people with the same problem have reported this below gets the MIDI ports showing again, I assume if it works for you it would have to be done after every reboot/power on until Microsoft issues a bug fix.

e
Open Windows Terminal as an Administrator (“run as administrator”)
Type net stop midisrv
After that completes, type net start midisrv
Start up the app you want to use with MIDI

[iezyboy]

I have the same problem. Uninstalling the update was not possible on my PC, because Microsoft already set it to permanent. 

I fixed it by setting the "windows midi service"  from "Manual triggered" to "automatic delayed" in the services screen in windows. This automatically starts the service after a reboot which resolved the issue for me. 

The procedure is as follows:

1. Click on start
   
2. type: "service". The startscreen should find services
   
3. Click on services to open the services screen
   
4. Scroll to "windows MIDI" service 
   
5. Double click on it to open the service properties
   
6. Click on the dropdown which shows somethin like "Manual ..."
   
7. Set it to "Automatic (Delayed Start)" and click the ok button
   
8. Start the service if it is not already started. You can do this by richt clicking on the service and click start
   

[jamesduprey@hotmail.com]

I have the same problem. Uninstalling the update was not possible on my PC, because Microsoft already set it to permanent. 

I fixed it by setting the "windows midi service"  from "Manual triggered" to "automatic delayed" in the services screen in windows. This automatically starts the service after a reboot which resolved the issue for me. 

The procedure is as follows:

1. Click on start
   
2. type: "service". The startscreen should find services
   
3. Click on services to open the services screen
   
4. Scroll to "windows MIDI" service 
   
5. Double click on it to open the service properties
   
6. Click on the dropdown which shows somethin like "Manual ..."
   
7. Set it to "Automatic (Delayed Start)" and click the ok button
   
8. Start the service if it is not already started. You can do this by richt clicking on the service and click start
   

I had the same issue, and your suggestion of restarting the WindowsMIDI service fixed it. Thanks so much.

In summary, I did each of the following. I am not certain what was the cause of the issue or the fix.
  1. Uninstalled the Windows Preview Update KB5074105 (January 2026)
  2. Went to MIDI Settings in Mobile Sheets, and reselected Genos / PSR Models
  3. Reinstalled the Yamaha USB-Midi driver 3.1.4 for 64-bit Win 11
  4. Restarted the WindowsMIDI service, as stated above.

Thanks, again.

[Rey_a]

I have the same problem. Uninstalling the update was not possible on my PC, because Microsoft already set it to permanent. 

I fixed it by setting the "windows midi service"  from "Manual triggered" to "automatic delayed" in the services screen in windows. This automatically starts the service after a reboot which resolved the issue for me. 

The procedure is as follows:

1. Click on start
   
2. type: "service". The startscreen should find services
   
3. Click on services to open the services screen
   
4. Scroll to "windows MIDI" service 
   
5. Double click on it to open the service properties
   
6. Click on the dropdown which shows somethin like "Manual ..."
   
7. Set it to "Automatic (Delayed Start)" and click the ok button
   
8. Start the service if it is not already started. You can do this by richt clicking on the service and click start
   

Run into the same problem today, after a security update a couple of days ago. (not a preview though, and not the KB n°'s mentioned above)
Your procedure/solution solved it for me as well!
Never would have found that myself.

Thanks !
Rudy