I stopped force-shutting down my PC after Windows 11's August update fixed this one thing

Published Aug 24, 2026, 8:00 PM EDT Maker, meme-r, and unabashed geek, Joe has been writing about technology since starting his career in 2018 at KnowTechie. He's covered everything from Apple to apps and crowdfunding and loves getting to the bottom of complicated topics. In that time, he's also written for SlashGear and numerous corporate clients before finding his home at XDA in the spring of 2023. He was the kid who took apart every toy to see how it worked, even if it didn't exactly go back together afterward. That's given him a solid background for explaining how complex systems work together, and he promises he's gotten better at the putting things back together stage since then. I confess I don’t turn off my main PC that often, but the times I have over the last year have felt like a struggle. It’s set to shut down when I press the power button because I don’t use hibernate or sleep on my desktop. But I’ve pressed the button and wondered whether my PSU or front-panel connector was failing, since the fans kept spinning even as my peripherals and screen went dead. The only thing that got it back was a ten-second press of the power button for a hard reset, and that’s not my intended behavior. Here’s the thing. The PC wasn’t hanging, my hardware was fine, and it was doing what it was supposed to. It just wasn’t doing what I told it to, because Windows 11 has multiple layers of your power settings, and until this month’s update, your PC only ever changed one of those copies. I’m the first to complain when Microsoft breaks something, but this is a rare win, and it deserves celebration. Custom power plans and Fast Startup often cause shutdown issues, and a holdover setting from earlier versions of Windows was breaking shutdown. Windows has been keeping two sets of power settings And only one of them was paying attention The modern Settings app is hiding the legacy power scheme system, which still controls your PC’s behavior. It doesn’t save one set of preferences; your PC keeps a full copy of every power setting for each plan, and it could have Balanced, High, Ultimate, and whatever power plan your PC vendor decided to add. You might even have specific Ryzen power plans depending on when you last updated your chipset drivers. My PC has four, including the normally hidden Ultimate Performance power plan, because I enabled it for screenshots and forgot it existed. Each plan has its own display timeouts, sleep timers, lid actions, power button actions, and settings for PCIe and USB behavior, among others. And the Settings app only changes things for the currently enabled plan. It won’t touch the others, and depending on your PC configuration, it sometimes changes on its own. Updating your GPU driver could cause it, so could OEM tuning utilities like the “performance mode” in MSI Center, Armoury Crate, or Lenovo Vantage. And anything that is scripted with powercfg /setactive does it silently, and you’ll not know until you try to power down your PC. This is what turned a button tap into a ten-second hold Force shutdowns cost more than ten seconds Those utilities changing your power plan turn a simple button press into a ten-second ordeal where you wonder if your hardware is failing. I set my PC to turn off when I press the button, and I expect it to happen without fail. Anything else makes me question reality, when I should be questioning the second layer of Windows settings. And modern standby doesn’t always work on desktop PCs, with a sleep state that won’t wake looking suspiciously like a hardware power problem. You know the symptoms: fans on, display off, unresponsive keyboard. The only way to recover is a long-press of the power button, and it shouldn’t be like this. Laptop users get a similar issue because closing the lid has its own list of power states to choose from. I want mine to wake instantly when I open the lid, but OEM software packages like to change things once I unplug from the wall, and the only way to stop it is to uninstall the sometimes-useful software that handles updates and other tweaks. The punchline is that a hard result comes with consequences. Windows didn’t have time to flush its write caches or close file handles so you could end up with garbled data. And the dirty shutdown flag gets set, which triggers chkdsk and sometimes the Startup Repair routine when you start your PC again. And resets add a Kernel-Power event 41 to the Event Viewer logs, which look like a failing PSU unless you notice the power plan is set incorrectly. What the August 2026 update actually changed And how to check your own PC instead of trusting it Microsoft is rolling out the behavior change slowly, through the new Controlled Feature Rollout mechanism. That means having KB5121003 installed doesn’t mean your PC has the fix. It just means it has the method for the fix, and your power button behaving correctly is not far behind. You can check your build with winver, and you want 26100.9168 or 26200.9168 at a minimum, but you’ll also want to test the behavior because the version number doesn’t mean anything until it’s active. To check for yourself: Open Control Panel and go to Hardware and Sound, then Power Options and Choose what the power buttons do Set the power button action (or lid action if you're using a laptop) to what you actually want Double-check the listed power plans on the Power Options page For each plan, go in and make sure that the settings for power button action have survived the save The other way is to open up a terminal and type in powercfg /list and Windows will show you every power plan installed on your PC, with an asterisk next to the currently enabled one. Mine showed four options, including an Ultimate Performance plan I've never enabled on my Ryzen PC. You can also use powercfg /query to see every value in the active scheme, and powercfg /requests to see which process is stopping your PC from going to sleep. And if you don't have the August update yet, you can use powercfg /setacvalueindex and its /setdcvalueindex twin to set the button behavior ahead of the update. Your PC was just doing what it was supposed to be doing, even if it felt wrong The thing that really sticks out for me here isn’t the behavior. Computers crash, software gets bugs, and things get fixed. That’s just part of using technology, and I can forgive that. But for months my PC has been ignoring a default that I set, and deciding to use another set of rules that live in a part of the settings that aren’t visible. Whether this was an oversight or part of the gradual swap from the old Windows settings menus to the new ones I don’t know, and we probably won’t ever know. But at least it’s been fixed.