Windows 11: First data loss, then worse performance – update for both errors

Windows 11: First data loss, then worse performance - update for both errors


from Benjamin Grundken
Microsoft has admitted that data loss could occur in connection with Windows 11 and Windows Server 2022 using the Vector Advanced Encryption Standard (VAES). The bug was apparently fixed weeks ago, but the fix reduced performance. With the latest updates, this problem should also be over.

Microsoft has confirmed a bug on its official support website that could lead to data loss under Windows 11 and Windows Server 2022 if you encrypt your data, for example using Bitlocker. According to Microsoft, the error should only have occurred in the context of modern CPUs. Specifically, it is about processors that support the Vector Advanced Encryption Standard (VAES). Among other things, Ryzen 5000, Tiger Lake and Alder Lake S processors were affected.

According to Microsoft, it corrected the original error months ago. An update for the preview version was first rolled out on May 24th, followed by a patch as part of the security release on June 14th. However, this patch may have resulted in the speed of relevant operations slowing down or even halving. This slowdown is now also out of the world.

Also interesting: Windows 10: Microsoft will soon roll out the Windows 11 printer feature

The necessary updates came on June 23 (preview) and July 12 (security release). If you keep Windows 11 up to date automatically, you should have collected the fixes. The preview releases from June 23, 2022 are called KB5014668 for Windows 11 and KB5014665 for Windows Server 2022. The security release of July 12, 2022 is available as KB5015814 (Windows 11) and KB5015827 (Windows Server 2022).

See also  "Mythic Ocean" sends gamers to a diving station

The portal contains more information about the affected CPUs Openbenchmarking.org ready. Various processors are listed there on which Vector AES has already been tested. In all likelihood, Zen 4 and Intel’s Raptor Lake would also be affected by the bug if they had already been released.

Source: Microsoft

Reference-www.pcgameshardware.de