Hi, I’m about to update my production machine (with Cubase 13 and 14 on it) to Windows 24H2 (from 23H2).
24H2 had a ton of problems in the field so I’m waiting for the upcoming Patch Tuesday to get the first round of bug fixes for it before running the update to mitigate any risk of downtime.
Has anybody on here had any issues with 24H2, or was it smooth sailing?
smooth sailing here.
remembr your power settings and things like USB suspend will be changed with a big update so remember to check and reset your power settings afterwards.
C14 running like a champ here on 24H2 with 9950x-RME UFX III
M
Thanks for your reply and the tip, that’s great news!
I have been waiting a few weeks mainly to decide if I should risk the 24H2 update. I am on a 8th gen i7 with 16Gb of memory with all non-essential services disabled (including Windows Search indexer). Also to eliminate spiking in general caused by services acessing the internet, I use a VPN service with network blocking on. The system had some overall stability issues in Cubase over many past years. So yesterday I hit the update button. It took the system about 1.5 hours to complete the update with a horrible wait on 97% progress, but finally it came through. My first impression is that Cubase ASIO performance is more stable, much lower spiking and about 7% better then it has been before the update. Overall system usage when finished booting (without any application running) is at 3% to 4%.
just updated and tested and for me also is more stable and better performance (Realtime - 2-3% less, ASIO Guard - about 1% less, Peak - is about the same).
Make sure after the update to reject all of Microsoft new “feature” (AI and like).
Just got the install - all working fine on latest Cubase 14 Pro
24H2 is running fine on our three production machines now, but there was a brief moment of panic when the RME HDSPe drivers became unavailable after the update (it happened on all three machines).
The drivers were visible in Device Manager but couldn’t be seen by Cubase, Nuendo, Pro Tools or Windows, for that matter.
Solution was to uninstall the drivers using the ‘try to completely remove drivers’ option.
After that, power off the machines (restart wouldn’t work). Then, after boot up, reinstall the drivers and everything should be OK from there.
The update didn’t reset any of our power settings but it did re-enable the USB controller settings for allowing the devices to be turned off in Device Manager, so check that after the update is complete.
Thanks everybody for chiming in!
Turns out, after advertising itself as being ready for my machine, when I kicked off the 24H2 update, it said that “my device wasn’t ready for it”.
So I guess their preflight checks flagged some driver or something else that is causing known problems, and now I’ll just have to wait until a new rev of 24H2 comes out that will actually install…