After recent windows 11 updates i cant start cubase 15 or studio one 7. Also.. my computer doesnt go into sleep mode. i read its probably a windows update issue.. damn what is microsoft doing again

 

Try to perform in the elevated command prompt:

1. SFC /scannow
2. DISM /Online /Cleanup-Image /RestoreHealth

Restart the machine.

 

Bought a new laptop recently, and it came with win 11. It took me weeks to disable all the shit that could interfere with my set up, solve problems related to file explorer black screen and finally make my small set of plugins (less than 60) work without issues. After I got all working fine, I now keep disabling the windows update for the longest time and totally avoid getting online on this machine.

Microsoft is a very shitty and shadowy company to say the least (one simply has no complete control over the system that is installed in their machine).

If one can choose, I would advice to avoid this 11 shit as long as you can.
If for any reason you are in win 11 like me, avoid updates for the longest possible if your set up is working fine.

 

Last edited: Apr 19, 2026 at 12:55 AM

as has already been said;
- completely disable windows updating and pretty much all other autonomous updating crap that is running (i.e. browsers, ms a/v/firewall, etc, etc)
- oct/nov 25 updates for both win10/11 removed capability of winOS to be activated using local KMS. The KB5068861 update should be removed along with the oct counterpart. If a host was hit with this update it will disable any KMS activation that was running and make reactivating winOS via KMS impossible. I dont use MAS anymore either because it came unglued on its own due to use of one of those update blockers that do not work. There was communication at some point due to the blocker being ineffective and a connection was made to an update server and voila! I use a proper local KMS server script (not MAS) that NEVER fails as long as updates are not allowed.

You can be online and not be liable for screwing up your shit with ms updates - it requires complete removal of the update infra-junk on the host machine. Once completed you're completely safe and locked down even when online.

If you do not do this you will find settings that you made and reverse engineering that was done to keep you safe from telemetry and updating garbage will be reset to microsoft default == ON.

 

Last edited: Apr 19, 2026 at 1:54 AM

For starters, never use the ‘Home’ version of any Windows 10/11! And never ever log in using a Microsoft account!

Using the ‘Pro’ version makes it much easier to use a local account. And settings like postponing updates and disabling telemetry can be much better controlled by using Local Group Policy Editor (gpedit.msc). You can even freeze the version of windows 10/11 you use and it will not update anymore until you allow it again. And virtually any setting and behaviour can simply be controlled without using shady and dubious third party tools like local KMS activation. You can buy an OEM activation key for Windows 11 Pro for about $10-20. So why would you want to fumble around with that? Once activated you can start blocking anything you want and still keep legitimately activated.
But again "Never ever log in with a Microsoft account"!

And @Kate Middleton, do you really want your pc to be able to go into ‘Sleep Mode’ when you're using it for DAW work?

That is literally one of the first things I disable along with ‘Hibernation’. Fair options for office work maybe, but I really get horrified at the thought of having this active on my DAW system!

 

"IF APPLICABLE"

Turn off your interface. Load Studio One (or Cubase) with the native WindowsAudio device driver. Once the DAW loads (and hopefully it does) turn on your interface and switch the audio device in your DAW to your interface. Close the DAW and reopen. It should be fine from then on. I just went through this and a similar strategy was what solved it. In my case Studio Pro was hanging on Scanning Presets.

Focusrite interface is what I was using btw, if that's of any relevance here...