Did KB5005033 break my Surface Book hibernation by power button?

Question

"Wait until you see the message “Slide to shut down your PC”."

Has Microsoft changed how this works recently (August 2021)? I have the original Surface Book, and had never seen this screen. Mine was set to hibernate on a power button press, and it always just did.

Suddenly this week it shows this screen for a few seconds after a power button press, and then just crashes - no crash dump, nothing in the logs, just gone. Takes several long presses of the power button to recover, and the log just says "The previous system shutdown at xxx on xxx was unexpected." Sometimes it adds "The WinFsp.Launcher service terminated unexpectedly" when a reboot attempt fails.

If I set the power button to "Sleep" or "Do Nothing", it always shuts down on a button press, and doesn't crash. If I hibernate from the Win->Power->Hibernate menu item it hibernates properly.

Last update: August 10, 2021—KB5005033
Hmmm...
It includes:
Power.Settings.Button.ppkg,Not versioned,31-Jul-2021,17:56,"5,727"
Power.Settings.Control.ppkg,Not versioned,31-Jul-2021,17:55,"6,916"
Power.Settings.Graphics.ppkg,Not versioned,31-Jul-2021,17:55,"5,833"
Power.Settings.Sleep.ppkg,Not versioned,31-Jul-2021,17:55,"7,254"

Maybe they did change something? And no longer support the original Surface Book?

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5005033-and-kb5005031-cumulative-updates-released/
Says:
Microsoft fixed an issue that prevents power plans and Game Mode from working as expected

They seem to have broken mine... Wish I could remember not to use the power button to hibernate...

BTW, no relevant tags seem to be allowed, and I can't post without some, so I'm taking any I can...

Answer 1

The product group for Surface hardware actively monitors questions over at
https://answers.microsoft.com/en-us/surface/forum
https://techcommunity.microsoft.com/t5/surface-devices/ct-p/SurfaceDevices

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hello,

I would suggest you to contact the Microsoft Chat support so they might have a remote session and have a look at your Power configuration .

Meanwhile you can try to restore the PC to older dates or try uninstalling the specific KB update if you suspect these updates are causing these issues.
A general troubleshoot would be to update all the drivers from the Microsoft website
https://support.microsoft.com/en-us/surface/download-drivers-and-firmware-for-surface-09bb2e09-2a4b-cb69-0951-078a7739e120

Hope this Answers all your queries , if not please do repost back .
If an Answer is helpful, please click "Accept Answer" and upvote it : )

Regards
Mukesh

Answer 3

@Limitless Technology ,

My limited vision and essential tremor make "chat" a miserable experience. I've checked my power config everywhere including RegEdit, and it is correct. I have all the current drivers.

Today I uninstalled 5005033. It apparently reinstalled 5004237 from July in the process, but Update History sees that with its old July time, only Uninstall sees it today ???

Has successfully done the configured action for the power button twice now, hibernation seems to be back!

(But it worked a few times when I first used the Win menu instead of the button, and when that began failing 100% it worked a few times from the TouchMe app, before that collapsed, so I'm not celebrating yet...)

So I guess I have to keep updates paused until MS solves this? How will I know if they do?

BTW, I received no notification about the replies here. Is "Following" supposed to provide some? Where?

Answer 4

So I guess I have to keep updates paused until MS solves this? How will I know if they do?

These groups may be your best resource to find out.
https://answers.microsoft.com/en-us/surface/forum
https://techcommunity.microsoft.com/t5/surface-devices/ct-p/SurfaceDevices

BTW, I received no notification about the replies here. Is "Following" supposed to provide some? Where?

Email alerts have been broken and erratic for the last week or so, they're working on it.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 5

Run Surface Diagnostic Toolkit