Hi guys
i was having a few(lots) of teething problems with migrating from windows 10 to win 11 , now there is an update that i keep ignoring , because i finally got a working system, however i don’t think its a good thing to ignore updates for ever , due to the volatile world of computing ,.. bug glitches and so on..
has anyone got any reasons to not install this on my studio machine ?
thanks in advance
T
Do it.
But don’t install the preview updates and wait for the patch tuesday.
1 Like
25H2 been fine on my windows system with cubase pro 15.x / wavelab 13 pro
as always, backup should be common sense
2 Likes
has it any stuff beneficial to us ?
like midi driver stuff and or any diverse effects with audio etc ?
I’m with it and everything is fine with Cubase 15 pro Wavelab 13 Pro Spectralayers 12 pro.
1 Like
perfect …sold..
thanks guys 
Just wait for the patch tuesday and ignore all the preview updates.
BTW see advanced / optional updates if there’s any coming for your computer brand like System or firmware. Install them.
1 Like
I’ve been on 25H2 since I built this machine, but obviously that was a clean installation. No unsolvable problems to report, once I’d removed all the unwanted dross.
1 Like
Which update, specifically? If it’s the January 2026 Preview update, you may want to wait if you are using any virtual MIDI ports.
Among other things, that includes the bits for a phased rollout of the new MIDI stack. If the feature is enabled on your PC, and if you use loopMIDI or other virtual MIDI ports, there’s a timing issue in there that requires you to jump through a couple hoops for them to work.
Info here:
Pete
Microsoft
Just FYI, up to a few days ago, on W11 Pro 25H2 26200.7840, I was being offered the update with new MIDI stack (KB5074105) under “Windows Update > Advanced options > Optional updates”, which I chose to not install (waited for Patch Tuesday!)
Then two security updates appeared 10-Feb, which I installed:
- 2026-02 .NET 80.24 Security Update for x64 Client (KBS077863)
- 2026-02 Security Update 0<85077181) (26200.7840)
After that (and several reboots), the update with the new MIDI stack (KB5074105) was no longer offered at all.
Currently, the only update currently being offered on my system is 2026-01 .NET Framework Preview Update (KB5074828), and it’s optional. I’m just curious as to why it appears to have been pulled from this month’s batch.
Told him to avoid previews and wait for patch tuesday.
I have no idea. The MIDI update hasn’t been pulled, but I haven’t checked to see if anything else in that KB caused it to be pulled. Eventually the preview updates get pulled into the main cumulative updates, but I don’t see any indication of that here.
Edit: just verified the above, and the KB is still rolling out. Not sure why you’re no longer being offered the update.
Pete
Microsoft
1 Like
Thanks, I’ll wait until it shows up here in a main cumulative update and let you know!
KB5074105 is an optional preview update, not a mandatory security update, it will be included in the next mandatory update as soon as it will be 100% tested like all the preview updates.
”Currently, the only update currently being offered on my system is 2026-01 .NET Framework Preview Update (KB5074828), and it’s optional. I’m just curious as to why it appears to have been pulled from this month’s batch.”
Same here. Just wait.
If you click “check for updates” we consider you what we call a “seeker” and you will be shown preview/optional updates. It sounded like that wasn’t happening here, which is strange.
Pete
Microsoft
I understand how it works. The point of my FYI was only to report that the preview appeared, then disappeared.
Given that this may be one of the biggest changes to occur in Windows MIDI since, well, ever, it would be nice to have some control over the process. I know, disconnect the internet …