Microsoft Acknowledges Windows 11 KB5083769 Problems: BitLocker Alerts on Some PCs and Installation Reboot Issues

The recent Windows 11 update, KB5083769, while not extensive, has brought to light some critical issues for certain users, including the unexpected appearance of a BitLocker recovery screen. Microsoft has acknowledged these issues and is in the process of implementing a fix.

According to reports from Windows Latest, the installation of the April 2026 Update necessitates multiple reboots on some systems. This peculiar behavior is likely linked to the simultaneous release of a. NET Framework update, which many users experienced during this period.

Typically, updates proceed without significant interruptions. However, following the installation of KB5083769, one user found themselves on the black “Working on updates” screen, anxiously watching the installation percentage tick up to 50% before the initial reboot. But rather unexpectedly, their PC rebooted an additional three times before finally reaching the lock screen. This peculiar pattern has been echoed by other users across multiple devices.

While Windows updates usually require just a single reboot, the observed multiple reboots could suggest a possible bug or may be directly tied to the recently released. NET Framework update that coincided with Patch Tuesday on April 14.

Microsoft is actively investigating these reports but has not yet confirmed whether a bug is responsible for the repeated reboots. It’s worth noting that there exists a different issue affecting Windows Server instances to reboot multiple times; however, this does not correlate with the experiences of standard consumer PCs.

Additionally, several users have encountered installation failures for Windows 11 KB5083769 due to persistent error codes, including but not limited to 0x800736b3, 0x800f0991, 0x800f081f, 0x800719e4, 0x800f0823, and 0x80071a2d. One user reported difficulties installing the update on a Lenovo Yoga Slim 7x.

Impact of the Windows 11 KB5083769 Update on BitLocker

One particularly concerning issue has been the unintentional triggering of a BitLocker recovery screen following Windows updates. Though rare, there have been multiple incidences over the last six months of users encountering this issue, notably after the October 2025 update and now again with KB5083769 (April 2026 Update).

In a recently updated support document, Microsoft confirmed that the appearance of the BitLocker recovery screen is mainly affecting devices with a specific configuration. These affected systems typically have BitLocker enabled on the primary drive coupled with a Group Policy configuration that includes the “TPM platform validation profile for native UEFI firmware configurations, ”in addition to reporting a “Not Possible” status under Secure Boot State PCR7.

Microsoft has urged enterprises to review their BitLocker group policies to ensure proper configuration before applying this update, as potential conflicts could lead to recovery alerts.

Fortunately, a server-side fix has been introduced by Microsoft, which aims to smooth out the installation process for the April 2026 Update.

Source & Images