Current update causes blue screen and bootloops

Another Windows update is causing problems. Similar to the past, some devices are experiencing blue and green screens after installing the latest update. Some devices boot BitLocker recovery. Microsoft is still looking for the cause.

BSOD and BitLocker boot after Windows update

Many users are eagerly awaiting the release of Windows 11 24H2. However, KB5043145 was initially released at the beginning of the week optional update for Windows 11 22H2 and 23H2. If you haven’t updated yet, you should probably wait. Some users report new problems after installation.

After installing KB5043145, blue and green screens sometimes occur. In addition to the occurrence of a BSOD or GSOD, some computers boot into BitLocker recovery after repeated unsuccessful restart attempts using the automatic Windows repair tool.

Microsoft is asking users for help

Microsoft has already confirmed the existence of the problem. This is what happens with clients with Windows 11 23H2 and 22H2. Servers are not affected. According to a post (via Neowin) are currently investigating the issue and will share new information as it becomes available. Affected users are asked for help in order to find a solution as quickly as possible.

If you experienced this issue, please use the Feedback Hub to create a report and provide further details. This information will help us speed up our investigation. You can find out how to use Feedback Hub at Send feedback to Microsoft using the Feedback Hub app.

Already similar problems

Back in June, Microsoft had to withdraw a Windows 11 update at short notice after it led to one serious error had come. Even after installing KB5039302, some devices were stuck in a reboot loop. As part of the updates for patch day in July there was also Problems with BitLocker. Similar to the current bug, devices also booted into the BitLocker recovery screen. Without the corresponding BitLocker key, users were locked out of their computers.

The current optional update KB5043145 now seems to combine these two problems. Apparently Microsoft has not yet been able to find and eliminate the underlying cause. To avoid the existing risk of a BSOD or a bootloop, it is recommended to wait before installing the latest version of Windows 11 22H2 and 23H2.

See also: