Windows 24H2 updating "community announcement"

I have updates blocked by GP on my PC. But I updated one item and it went to 24H2. That, together with the latest update from Slate, broke my entire setup. Luckily I had a backup and I went back to 23H2 older Slate and everything is fine. This is a community announcement. Thank you.

Maybe experimentally move to a clean install of 25H2 someday. Flawless on my systems. Always clean install.

Blocking updates completely is fine (I use Sordum windows update blocker) but If you wish to stop any upgrade to 24h2>(when enabling updates) follow this:

https://www.elevenforum.com/t/specify-target-feature-update-version-in-windows-11.3811/

Like you, my main computer stayed on 23h2 until very recently when I went to 25H2 via ISO. You don’t have to necessarily do a clean install! But if doing an upgrade you will have to do some housekeeping after and you can restore health afterwards if any issues DISM/Restorehealth.

Once all done just remove the OLD windows to save space via Disk Cleanup/System.

(support for 23H2 is ending)

25H2 runnning flawless.

1 Like

Thanks for that. I don’t care about support from Windows. If it’s working, it’s OK for me. The studio PC just does music.

1 Like

What about your setup was broken?

Lots of folks running 24h2 and 25h2 with Cubase and other apps without issue, so the update alone is not necessarily a problem.

If you have any specifics about what broke, that will help. Thanks.

Pete
Microsoft

Thanks for the interest. As I said, it was a combination of two updates. Nuendo began stalling on audio export. I had never seen this particular issue before. But it made the system unuseable. Obviously this could be due to a Windows update; or the Slate update. I prefer to stay a few updates behind with Windows. If the system is static, there’s no need to update.

I agree, just put it in as a fact, not for any reason….which of course it is not a reason to upgrade.

Note that 23h2 doesn’t get the new MIDI stack in Q1 of 2026. It’s shipping out to supported versions only (I have no way to ship to unsupported versions).

So that may be a consideration for you when the time comes.

Pete
Microsoft

2 Likes

It’s not Windows 24H2. It’s something in the Slate update. The freezedump mentions VMR. When this first happened, there were no logs created. Yestaerday after running the restored 23H2 for a while, I updated Slate out of interest (I had a fresh backup). So not a Microsoft issue; which as a shareholder, is good news.