Windows 11 23H2 Not getting shutdown

Loganathan R 166

Windows 11 23H2 after Jan 2026 update it is not getting shutdown and as per MS Known issue update, we have installed the OOB patch KB5077797 still the same. We have tried via command line and UI still system is not getting shutdown.

konrad lis 10 Reputation points

2026-01-20T07:42:38.7333333+00:00

I have the same bahavior on laptops in company. OOB installed and change nothing.
Richard Long 391 Reputation points

2026-01-20T18:50:43.3833333+00:00

I have the same issue even after installed the OOB patch. Also made the registry change to disable Secure Launch. No change in behavior.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Matt G 25 Reputation points

2026-01-22T15:34:27.4533333+00:00

We are experiencing the same issue. KB5077797 and the suggested workarounds do not resolve the issue in our environment. Our comptuers still can't be shut down or hibernated, only rebooted.
Paulo Juliani 1 Reputation point

2026-01-23T14:29:13.19+00:00

The only workaround that worked for me with KB5077797 already installed was change in BIOS the Secure Boot Mode from Deployed to Audit
Carl Medley 0 Reputation points

2026-01-26T17:25:18.5766667+00:00

Regarding Saturday's Emergency patch KB5078132 (https://support.microsoft.com/en-us/topic/january-24-2026-kb5078132-os-build-22631-6495-out-of-band-ae8525fd-a0a8-4b9b-bba9-c647ea5dc8dd) we STILL have the same issue with not being able to shut down.

12 answers

Metz, Tobias (TMG/TC TK O1) 20 Reputation points

2026-01-22T14:14:36.4766667+00:00

only deinstall of KB5077797 AND KB5073455 solved the Problem on my HP Laptop
Please sign in to rate this answer.

4 people found this answer helpful.
Carl J. Radcliff Jr 0 Reputation points

2026-01-23T14:24:33.0833333+00:00

Removing both patches fixed ours as well. Shutdown process seems to be slower overall though even post removal.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Liam Samuel 36 Reputation points

2026-01-29T05:32:01.0833333+00:00

According to Microsoft, the behavior is hardware dependent. As a result, Microsoft is currently working closely with OEM partners to prioritize testing and validation of a fix across the affected hardware configurations before any release is made available.
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Robert Kennington 10 Reputation points

2026-01-23T17:35:29.68+00:00

I have nothing to add except to say that I and at least 3 other users are also having this issue even after installing KB5077797. I tested disabling Secure Boot in BIOS just to see if it would fix the problem. I then had to track down my Bitlocker key in order to finish booting my machine, so obviously not a solution within my organization even if we were willing to disable Secure Boot for all users. It did, however, allow me to shut down, but after re-enabling Secure Boot (requiring me to type my Bitlocker key again) the problem returned.

I wonder if Microsoft will release another OOB patch or make us wait until February (or later) regular patches?
Please sign in to rate this answer.

2 people found this answer helpful.
Carl Medley 0 Reputation points

2026-02-02T11:54:21.4+00:00

I have us still on 23H2, and my org leadership is asking why not push 24/25H2 to help resolve the power issues. But then everything I read about 24/25H2 says to avoid it like the plague (Bitlocker/boot issues for one). So to me, upgrading isn't the answer either...

Stanimir Lazarov 10 Reputation points

2026-02-04T18:56:10.6533333+00:00

From Group Policy go to Computer Configuration->System->Device Guard and DISABLE/Not Configure this: Turn On Virtualization Based Security. Restart the computer. Run msinfo32.exe and check if Configuration-based security services Running/Configure are with empty values. You should not have as a values Secure Launch and Credential Gurads. Try to shutdown the computer.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Harry Phan 17,360 Reputation points Independent Advisor

2026-01-20T09:15:24.23+00:00

Hello Loganathan R

The shutdown failure you are seeing on Windows 11 23H2 after the January 2026 cumulative update is a known regression tied to the Secure Launch feature in combination with the update stack. Even though KB5077797 was released as an out‑of‑band fix, Microsoft has confirmed that the patch does not fully resolve the issue on systems where Secure Launch is enabled in firmware. That explains why your machines still refuse to shut down even after applying the patch and attempting shutdown through both GUI and shutdown.exe.

At this point the only reliable workaround is to disable Secure Launch at the UEFI/BIOS level or through the registry under HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SecureLaunch by setting the value to 0. After making this change, restart the system and shutdown should function normally again. Be aware that disabling Secure Launch reduces boot‑time protection, so this should be considered a temporary measure until Microsoft issues a corrected cumulative update. If you are in an enterprise environment, you should also check whether other components such as Hyper‑V or Credential Guard are dependent on Secure Launch before disabling it.

Since 23H2 is already in extended servicing, Microsoft is expected to release a follow‑up patch to fully address the shutdown regression. Until then, the workaround above is the only supported method to restore shutdown functionality.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Harry.
Please sign in to rate this answer.

2 people found this answer helpful.
Teemu 5 Reputation points

2026-01-22T05:31:39.1633333+00:00

This did not work with Lenovo T16 Gen 3 atleast.

Matt G 25 Reputation points

2026-01-22T15:38:24.96+00:00

This does not work on Dell Precision 5690

Rick Rigbye 5 Reputation points

2026-01-23T08:00:09.8+00:00

only Uninstall of KB5077797 AND KB5073455 solved the Problem
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Loganathan R 166 Reputation points

2026-01-20T12:08:25.9766667+00:00

Created the DWORD SecureChannel and set to 0 and tried still the result is same.
Please sign in to rate this answer.

1 person found this answer helpful.
Harry Phan 17,360 Reputation points Independent Advisor

2026-01-21T04:24:56.9166667+00:00

The registry value you modified is not the correct one for controlling Secure Launch, which is why you are not seeing any change. The DWORD you created under SecureChannel has no effect on shutdown behavior. The relevant key is located at HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SecureLaunch. Within that path, the Enabled value must be set to 0. If the value does not exist, create a DWORD named Enabled and set it accordingly. After making this change, perform a full reboot rather than a simple restart, since the firmware handoff is involved. Only then test shutdown again.

Loganathan R 166 Reputation points

2026-01-21T05:53:01.2766667+00:00

Tried created the key and created the DWORD still same

rai was here 5 Reputation points

2026-01-22T09:34:11.8366667+00:00

same for our company

the securelaunch regkey doesnt work, also switching of securelaunch via gpo

also the recommended shutdown /s /t 0 doesnt work

for me it seems, that securelaunch has nothing to do with the problem of not shutting down.

PINKI KUMARI SINGH 5 Reputation points

2026-01-22T13:20:49.6666667+00:00

Any further update on this? Its not working installing OOB update(KB5077797),disabling secure launch or with shutdown /s /t 0.

Stanimir Lazarov 10 Reputation points

2026-02-04T19:00:33.9666667+00:00

From Group Policy go to Computer Configuration->System->Device Guard and DISABLE/Not Configure this: Turn On Virtualization Based Security. Restart the computer. Run msinfo32.exe and check if Configuration-based security services Running/Configure are with empty values. You should not have as a values Secure Launch and Credential Gurads. Try to shutdown the computer.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows 11 23H2 Not getting shutdown

12 answers

Your answer