Exterminator

Community Manager
Verified
Staff member
Windows 10 Fall Creators Update Bug Blocks the Install on Some PCs

The Windows 10 Fall Creators Update is now being released in stages to users across the world, so while some people might receive it faster than others, there’s a bunch of unlucky Microsoft customers who can’t install the update because of a critical bug.

Some users are complaining that installing the Fall Creators Update fails unexpectedly, and the only common thing in all reports is a hardware mix of motherboards using Intel’s X299 chipsets and NVMe SSD drives.

Clean install solves the problems
This means that quite a large number of systems could be impacted, as the issue can affect motherboards manufactured by Asus, MSI, and Gigabyte. It’s not yet known how widespread the problem currently is, but Microsoft says it’s investigating and return with a fix shortly.

“At around 22% completion, my PC rebooted and suddenly displayed my normal boot screen with a white text saying ‘BlInitialization failed 0xc00000bb’, and I have absolutely no idea what this is. I tried resetting my SSD (Kingston 128GB) but this issue is so bad that it won't even let me do that,” one Microsoft user who turned to the Community forums to report the issue explained.

“At first my SSD was locked, then I unlocked it using commands in CMD but it all of the sudden disappeared and windows has no idea that it even exists. I tried resetting everything and all Windows tells me is "We ran into an error." or something like that and that's it.”

The only workaround available right now is to install the Windows 10 Fall Creators Update using the stand-alone ISOs, which basically means that users experiencing the bug need to start from scratch and reset their PCs. Of course, a second option is waiting for Microsoft to develop a fix and ship it to affected devices, though there’s absolutely no word on how long this is going to take.

If you haven’t been offered the Fall Creators Update just yet and you have one of the aforementioned motherboards, you better delay the manual install until more information is provided to make sure you’re not hitting the same issue.
 
P

plat1098

On a Lenovo w/NVMe, Intel IO and an immaculate pre-Fall CU system, I could not understand why the "upgrade" to Fall CU was so issue-laden: failures, duplicate downloads--ultimately it took though. A relatively decrepit machine w/SSD breezed right thru it. Noticed afterward, I had an extra recovery partition but since there were no outward problems, just let it go. Yesterday, Start menu and most taskbar items became unresponsive. So, I did a repair-install earlier today: the disk is back to the normal EFI/C/Recovery and everything works. For now. :mad:

Thanks for this info, not fun trying to figure it out.
 

shmu26

Level 83
Verified
Trusted
Content Creator
On a Lenovo w/NVMe, Intel IO and an immaculate pre-Fall CU system, I could not understand why the "upgrade" to Fall CU was so issue-laden: failures, duplicate downloads--ultimately it took though. A relatively decrepit machine w/SSD breezed right thru it. Noticed afterward, I had an extra recovery partition but since there were no outward problems, just let it go. Yesterday, Start menu and most taskbar items became unresponsive. So, I did a repair-install earlier today: the disk is back to the normal EFI/C/Recovery and everything works. For now. :mad:

Thanks for this info, not fun trying to figure it out.
Yeah, every new Windows edition adds another recovery partition. It's getting a bit annoying.
 

ElectricSheep

Level 12
Verified
On a Lenovo w/NVMe, Intel IO and an immaculate pre-Fall CU system, I could not understand why the "upgrade" to Fall CU was so issue-laden: failures, duplicate downloads--ultimately it took though. A relatively decrepit machine w/SSD breezed right thru it. Noticed afterward, I had an extra recovery partition but since there were no outward problems, just let it go. Yesterday, Start menu and most taskbar items became unresponsive. So, I did a repair-install earlier today: the disk is back to the normal EFI/C/Recovery and everything works. For now. :mad:

Thanks for this info, not fun trying to figure it out.
Not even going near that at the moment as still having problems with broken updates TWO months on! They've gotta get their act together and stop breaking stuff before everyone goes Linux or something!! :mad:
Oh and I ain't taking the Nuclear option and completely re-installing as it takes absolutely forever!:eek::p
 
  • Like
Reactions: shmu26 and frogboy