Hi Pete, I’ve done all of the power options (and then some, using Power Settings Explorer) and the results were still the same. I’ve had C States and EIST disabled in the Bios (Gigabyte Z590 Aorus Pro AX, 64GB Ram) but I’m still having issues. It’s way worse when I Monitor a channel, as the VST Meter will jump from 50% to peaking and distorting. Meanwhile, Cubase in the Windows Task Manager is at 6.2%. Thanks for the suggestions!
Other than the power / c-state change, I’m not aware of anything else in 24h2 that changed that could impact this. (That doesn’t mean there couldn’t be something, just that I am out of ideas there.)
I mean, it could be things that would impact you across versions, like if you are using a sample instrument and haven’t excluded the sample folder from Defender real-time scans, or if your project folder is being managed by OneDrive.
Do you see anything else in the task manager taking up CPU cycles?
Pete
Microsoft
Interesting, but I would not block h2 because it seriously prevents some very cruel backdoors and protection it also stops to my knowledge the automatic screen recording of windows copilot which was forbitten by the EU back in December. So not installing is also not good in my humble opinion. Interestingly I made a post yesterday that the issues seem to be not because of windows 11 but because of 13 and 14 … Cubase 12 pro has non of the issues with windows 11