Bitlocker pre-boot (PIN) super slow to load after 24H2 update

Update: Bitlocker delay worse now as 22635.4660 BETA BUILD. 5+ min delay before it appears.

Hey guys, I've been VERY disappointed with Microsoft's lack of response or care about this issue. They just sent me an email regarding a bug report I sent them for OneDrive 4 MONTHS AGO. So, were right on track to receive a patch for this bug sometime in March.

.

Today, I rebooted for the Insider Beta build 22635.4660 on my DESKTOP PC AMD Ryzen 7 3700 with Aorus motherboard. It DID NOT previously have this problem. It's been on beta builds for a while with other issues, but not this one. After reboot, it now freezes at the BIOS screen, and sits there for 5 GOD DAMN MINUTES BEFORE DISPLAY BITLOCKER PIN SCREEN. Come on! Seriously! You don't fix the issue, and instead you make it significantly worse. I'm not even joking, at least 5 minutes if not longer. I thought my SSD had gone out, or that my operating system was hosed. I was dreading having to reinstall Windows 11 again for the third time in the last 3 months.

.

Windows 11 stability has gone significantly downhill. I can't even describe how absolutely disappointed I am in Microsoft's deployment of updates and code development. Everything is just horrible. Memory leaks and every application, somehow my 48 gigs of RAM gets eaten up all after a week of not rebooting. Whereas several years ago I used to have more tabs open, more Chrome windows open, have everything open, and never chew through 16 GB ram. Now I have 48 GB of RAM and I'm chewing through that within a week. I used to not have to reboot for a month at a time. I just don't have time for all that ****.

.

Windows stability in the past used to be great. I in-place upgraded from 7 to 8 to 10 and through every version of 10. 24GB of RAM. Never chewed through it like this. Never had issues with Bitlocker. This is just absolutely ridiculous. Who the hell runs this show now?

.

I also performed full RAM and SSD tests. Passed with flying colors. It's not my hardware.

.

So for anyone holding hope that this issue will be fixed anytime soon. It won't be. The latest update caused more problems, on a PC that was not having the Bitlocker delay issue. If you think your OS is hosed because Windows 11 isn't booting now after updates, it's not hosed. Let it sit there for 5 to 10 min and it will eventually boot.

.

Also, out of curiosity, while it was sitting on the BIOS logo doing nothing, I typed my password and waited to see if it showed in the text field when Bitlocker came up 5 min later. It does! Whatever info that's worth.

Same problem. As soon as I updated from 23H2 to 24H2 today, the time from power-on to the BitLocker prompt fully appearing and being responsive behaves just as the original posted indicates (except much slower - much more then 1/2 second between prompts). Once that slowness is past and Windows has started up, my first impression is that the system performs properly, but time will tell.

Until now (and I've used BitLocker pretty much since it was released almost twenty years ago) I've never seen this behavior.

Lenovo ThinkPad T16 Gen 2.

Winver shows 26100.2033

Hello

Thank you for posting in Microsoft Community forum.

What is the internal version number of your operating system?

By querying the known issues of Windows 11 24H2 update history, no similar problems were found.

Windows 11, version 24H2 update history - Microsoft Support

It is recommended that you temporarily disable updates and then report this issue to Microsoft through the Feedback Center.

Send feedback to Microsoft with the Feedback Hub app - Microsoft Support

Known Issue Rollback (KIR): Microsoft has acknowledged issues with recent Windows 11 updates causing boot problems and has issued Known Issue Rollbacks (KIR) to address these. The KIR is typically deployed automatically, but for managed systems, IT administrators may need to deploy a special Group Policy.

www.tomshardware.com

www.thurrott.com

Best Regards,

Wesley Li

Same issue. I know Bitlocker is now enabled by default, but why that would result in this behavior, on a computer where Bitlocker was already enabled, is quite puzzling.

@Wesley Thanks for moving my post. I've updated it with my OS version number. I have also left feedback on the feedback hub.

@Williams_J Glad I'm not the only one with the problem. If you manage to find a solution or if it suddenly fixes itself, do say! Thanks!