The last January security patches for Windows 11 They've given more than one company and system administrator a scare. One specific update caused certain computers running Microsoft's operating system to crash. they could not be turned off or enter hibernationrestarting over and over again without displaying clear error messages.
Following complaints on forums and support channels, the company acknowledged the problem and has published out-of-band emergency updates This will restore normal shutdown procedures and, incidentally, correct other issues related to remote connections and cloud services. Meanwhile, many users have been forced to resort to console commands to shut down their PCs with some degree of control.
A bug in the January update that prevented Windows 11 from shutting down
The origin of the problem lies in the January security update identified as KB5073455Published last Tuesday, the 13th, as part of the traditional Patch Tuesday, this patch, intended to strengthen security and correct previous errors, ended up introducing a serious bug: when attempting to shut down or hibernate the computer, the system restarted automatically instead of completing the shutdown.
This behavior has been observed in teams with Windows 11 version 23H2, especially in the Enterprise and IoT editions, that is, environments more typical of companies and organizations than of home users, and in some related compilations such as Windows 11 26H1Microsoft has clarified that the KB5073455 update It was not distributed generally to all editionsThis limits the scope, but does not lessen the seriousness of the ruling for those who suffer it.
According to the company's support documentation, the bug is related to the function of System Guard Secure Launch or Secure BootA virtualization-based security layer protects the boot process from firmware threats. When this feature was combined with the January patch, some systems were simply unable to complete the shutdown process or enter hibernation.
In practice, the affected computers have become trapped in a frustrating loop: the user clicks power off or hibernate, the session ends, and instead of disconnecting, The machine restarts as if a restart had been requestedNo error code or warning appears on the screen, which has complicated the diagnosis at first.
Affected computers and Windows versions
Microsoft itself has detailed that the shutdown failure is limited to Windows 11 version 23H2 when Secure Launch or equivalent advanced security mechanisms are active. This is, in most cases, corporate PCs, professional workstations, or managed IoT devices, where this type of protection is usually enabled by default.
In Spain and the rest of Europe, this scenario mainly affects organizations that use Windows 11 Enterprise on their networks, as well as to cloud infrastructures and virtualized workstations. On home computers, where these hardened secure boot features are not always active, the impact has been significantly less.
Besides the shutdown debacle, the January patching round caused problems on other fronts. The following issues have been detected: Connection and authentication errors in remote desktop applicationsincluding Azure Virtual Desktop and Windows 365, in different versions of the system, among them Windows 11 24H2 and 25H2as well as Windows 10 22H2 under extended support programs and Windows Server 2025.
In these configurations, after installing the security patches, Some remote sessions stopped requesting credentials correctly. or they failed to establish a connection. For many companies that rely on daily remote access to servers, cloud PCs, or virtual desktops, the problem has resulted in service outages and work delays.
Temporary solution: Shut down the PC using commands
Before the final fix was ready, Microsoft published a temporary solution to be able to turn off the equipment without getting stuck in the reboot loop. The recommendation was to use the Command Prompt (CMD) and run a specific command.
The suggested procedure is simple: open the console (by searching for "cmd" in the start menu or search bar), and type the instruction shutdown /s /t 0Pressing Enter will shut down the computer immediately, without going through the usual menus or forcing a restart. However, it's important to save all open documents and work files beforehand. to avoid data loss or corrupted files.
Some users have opted for more drastic measures, such as Turn off the equipment by directly cutting the power supply. or by forcing a shutdown with the PC's physical power button. While this may seem like a quick fix, it's not the recommended method: interrupting the power supply without a proper shutdown can corrupt the file system or cause other operating system errors.
In the specific case of hibernation problems, There is no equivalent shortcut that restores it while the bug is activeThe only way to restore this behavior is to install the corrective update that Microsoft has made available to administrators.
Emergency updates: KB5077797 and KB5077744
Faced with a growing number of complaints and internal reports, Microsoft has launched out-of-band (OOB) updatesThat is, patches that do not wait for the next Patch Tuesday cycle, to mitigate the most serious flaws introduced in January.
For systems affected by the shutdown issue in Windows 11 23H2, the company has released the update KB5077797This package fixes both the bug that prevented Turn off or hibernate the computer when Secure Boot was enabled as part of the errors related to remote connections to cloud services.
In parallel, for Windows 11 24H2 and 25H2The update has been released KB5077744focused on resolving the failure of Remote Desktop connections to Microsoft 365 Cloud PC, Azure Virtual Desktop, and Windows 365In Windows 10, a specific update identified as KB5077796 addresses similar authentication errors in remote connections.
For now, Microsoft indicates that these are emergency updates. They don't always appear immediately through Windows UpdateIn many cases, administrators and advanced users must resort to Microsoft Update Catalog to download the packages corresponding to your version and install them manually on each computer or using centralized management tools.
How to install the fixes on your PC or corporate network
For those managing multiple jobs in offices or data centers, the process begins with identify exactly which version of Windows is installed on each machine and whether it has features like System Guard Secure Launch enabled. This allows you to determine which patch is appropriate: KB5077797 for Windows 11 23H2 with the shutdown failure, KB5077744 for Remote Desktop issues in 24H2 and 25H2, and KB5077796 for specific Windows 10 environments.
Once the correct package has been located in the Microsoft Update Catalog, the file can be download and install manually on each affected computer, or distribute it using software deployment tools if it's a corporate network. After installation, Microsoft recommends restarting the device to ensure that all changes are applied correctly.
After restarting, it's a good idea to perform some basic checks: verify that the equipment It shuts down and enters hibernation from the usual menu. without unexpected restarts, and that Remote Desktop connections prompt for credentials again and are established normally.
For any further questions, the company keeps its official support pages with a list of known issues and the status of each fix. Reviewing these technical notes is especially useful for administrators managing environments with hundreds or thousands of computers distributed across multiple locations.
Other issues stemming from Patch Tuesday in January
The error that prevented the computer from shutting down hasn't been the only headache caused by the latest updates. According to various expert reports, including media outlets such as Windows Latest or BleepingComputerSeveral minor but annoying bugs that affect the daily use of the system remain unresolved.
These problems include black screens that appear for seconds or minutes before showing the cursor, the desktop background being reset to black without apparent explanation and anomalous file behavior desktop.ini in File ExplorerThese are errors that do not prevent the use of the PC, but they are inconvenient and cause frustration.
Incidents have also been reported in Outlook Classic configured with POP accountsIn these cases, the application may freeze and continue running in the background, preventing a normal session closure or a clean system shutdown. Force-closing the program is possible, but it should be done carefully to avoid damaging the email database.
Microsoft acknowledges some of these problems and assures that He is working on additional patches.But for now, it hasn't set an exact date for its arrival on Windows Update, nor has it detailed all the fixes in a single cumulative update.
Overall, what happened with the Windows 11 error that prevented the computer from being shut down This reopens the debate about the quality of updates and prior testing in real-world environments, especially at a time when Microsoft is introducing numerous new features and artificial intelligence capabilities to its operating system. For most end users, the impact has been limited, but in Europe and Spain, many companies have been forced to react quickly, reviewing their patch deployment policies and relying on temporary solutions until out-of-band fixes arrive from the Microsoft Update Catalog.
