Just thought I’d mention that I installed Windows 24H2 a couple of days ago.
It turned Cubase 14 Pro into an unusable, unstable dropout machine. Even with only BFD3 drums running I was getting dropouts. Also, it didn’t recognise my RME Drivers requiring a re-install.
I just recovered back to 23H2 and everything is fine again.
I thought I would post as I understand the 23H2 recovery files are deleted after 10 days, so don’t persevere if 24H2 doesn’t work on your machine
However, the Group Policy Editor is an advanced technical feature and not recommended for everyone. Because screwing this up, means you’re on your own.
Unfortunately, running an advanced DAW is still an exercise in relatively advanced computer use.
I missed oportunity to roll back to a 23H2, and I can tell that 24H2 is a worst Win version for many years for sure… Not in an audio issues for me, but I have almost 10% CPU performance decrease over 23H2
After a full day, it was still stuck at 79% installed, and it was a major hassle getting back to smooth running. I won’t touch it again until I have to.
You are right Andrew, Windows 24H2 is a pain I could have done without, but too late. Cubase has been very unstable since that update. I have problems with file management and opening files that I did not have before. I have never had to add items to exclude from Windows Defender antivirus scans, which I have had to reset a few times and which it takes forever to open and display tabs and information.
yes, I’m working all day everyday with Cubase 14 and windows 11 24H2 and it’s running perfectly.
I’ve even been doing DAW benchmark test that are pushing the machine to 100% and it’s as astable as a rock and I can see no performance difference from before the update as I have lots of data from before and after.
Windows 11 24H2 and Cubase 14-RME UFX III- are working so well here I decided NOT to make my M1 max Mac my default Studio DAW as this 9950x system is just awesome.
Well, Andy, I am caught in the trap. I got up the next morning after a very successful project the day before and it was as if a dark cloud came down and I couldn’t even edit the project for a final mix…
everything was erratic certain things didn’t work so I totally shut it off
I’m using C13 on W11-24H2 and have a few annomalies and higher-than-normal cpu% but this helped my sessions when offline (as I often am; being up-to-date with all Windows security). I turn off “Real Time Protection” and have noticed my cpu% run lower. YMMV.
But either way I’m really careful of Windows updates, regardless of what version it is. I’ll only give updating a shot if there are problems on the current version. But other than that, if it ain’t broke, I don’t fix it.
So you muscled your way into preventing Windows 11 updates for more than a year?
How difficult was that to pull off? Or were there no other Win11 updates until 24H2?
On my current Win10 system, I’ve used the Group Policy Editor to delay feature updates for a year, but to the best of my understanding that was the max delay I could get to without more extreme “hacking”.
So I learned how to 
However, the Group Policy Editor is an advanced technical feature and not recommended for everyone. Because screwing this up, means you’re on your own.
Unfortunately, running an advanced DAW is still an exercise in relatively advanced computer use.
)