"Microsoft rounded off January by adding more devices to the list of those affected by the hibernation issue it claimed had been fixed by an out-of-band update. The company acknowledged that problems remained via its Release Health Dashboard on January 30. The company noted that Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled "are also impacted by this issue.""
"The January 13 security update for Windows 11 23H2 left some PCs with Secure Launch unable to shut down or enter hibernation. Instead, the devices restarted. An emergency fix was released on January 19. However, by January 23, the company reported that it was looking into reports that "some devices are still impacted after installing the out-of-band update." Also affected were supported versions of Windows 10 (including 22H2 devices enrolled in Microsoft's Extended Security Updates program)."
The January 13 Windows security update caused some Secure Launch-capable PCs with Virtual Secure Mode (VSM) enabled to restart instead of shutting down or entering hibernation. An out-of-band emergency fix was issued on January 19, but reports indicated some devices remained affected after applying that update. Microsoft acknowledged remaining problems on its Release Health Dashboard on January 30 and stated that Secure Launch-capable PCs with VSM enabled were impacted. The issue affected Windows 11 23H2 and supported Windows 10 versions, including 22H2 devices on Extended Security Updates. Installing or skipping the January patch risks either vulnerability exposure or devices failing to hibernate.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]