12-13-2017 11:50 AM
We are continuing to work on it. A few points:
12-13-2017 11:53 AM - edited 12-13-2017 11:54 AM
Thanks for the update Michael.
Is there any indication as to why the 1004 update did not resolve it for everyone?
Did MS work together with ASUS on this update?
Is there something those of us whom 1004 did not resolve the issue could try?
Are there other factors which could interfere? Installed Memory size, video card, etc?
In my case, another member with the same motherboard, m.2 drive and using the ms nvme driver was able to perform the upgrade. I replicated that configuration and mine was not successful.
12-13-2017 11:54 AM
12-13-2017 11:58 AM
The basic problem: Memory fragmentation during system initialization forces IO buffers into high memory. So yes, the hardware in the system has a definite impact on that fragmentation (each device reserves an address range).
While we have provided details about the issue to ASUS, we are not aware of what they changed in the 1004 firmware.
12-13-2017 01:00 PM
I tried upgrading to 1709 after the ASUS BIOS upgrade to 1004 and still a no go. I still get error 0XC00000bb.
12-13-2017 04:47 PM
Hello! My name is Michele, from Italy. I've a Samsung 960 Pro on MSI X99A Workstation (beta bios v. 1.15), and even my system suffers of this issue. Error 0xc00000bb, if I update via Windows Update or Windows Update Assistant; error 0xc1900101 - 0x20017 if I try to update via Media Creation Tool. My PC is a custom built Xeon based workstation, and I use it for my work, so I can't have a clean install...
I have tried to open a ticket with MSI. MSI tried to install the update on a system like the one I have, and they said "no problems here!" and closed the ticket. The official bios release is locked at 1.0 (2016). They sent me a beta bios (1.15) but I still have the issue.
Now Windows Update did another download... I hope to have my troubles fixed, but I don't think so. I'll wait for the next release...
12-14-2017 07:20 PM
So when i used windows upgrade assistant it basically messed up my pc and turned from the initial error code 0xc00000bb to error code 0x80242006.
Any idea how to fix this?
I've looked online and tried a few things and none seemed to have worked.
Obviously once this has been fixed i'd still have the error code 0xc00000bb waiting for me but at least I've ticked off one in the process.
Also I know Asus is probably the most popular brand of motherboards but have you guys been in contact with MSI? or even gigabyte about the problem? Neither have a fix and it seems no one even talks about brands other than Asus.
12-15-2017 10:14 AM
I have the save issue during Update from 1607->1709 several times. My configuration
Board: MSI X99A XPoWER GAMING TITATIUM
BIOS: Latested (MS-7A21)
System Disk: SAMSUNG MZVPW128HEGM (SSD SM961-NVMe 128GB M.S PCIe)
I would strongly appreciate if Microsoft stop updating my system to 1709 until the issue was fixed!
Security updates are welcome. This must be possible. In this case waiting for the fix is tolerable.
12-18-2017 04:06 AM
Just the same board and ssd I have and I also meet this issue during updating from 1703 to 1709, this is annoying
12-18-2017 10:21 AM
12-19-2017 06:42 AM
No way for my system. When BSOD occurs, every button (F1 for the recovery, F8 for boot options...) results in nothing. I'm able only to enter the UEFI or to "load another OS" with F9.
So I tried to disable the driver signature in Command Prompt, with
bcdedit /set testsigning off
I did reboot the pc, then I tried to update. And I received the same error: BSOD with 0xc00000bb.
12-20-2017 08:54 AM
Do not waste your time. It's not our fault and I personally do not miss the creator update. Switch of the Windows Update service and wait for the bug fix. Shame on Microsoft that they forgot to consider these "technical state of the art configurations" and finally not be able to provide a solution in acceptable time frame. Furthermore although they collect so much informations from every installation they do not stop updating those systems! Obviously they collect the wrong information ;)
12-22-2017 09:16 AM - edited 12-22-2017 09:17 AM
For what it's worth.
MSI X99A XPOWER GAMING TITANIUM LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.1 Extended ATX Motherboards - Intel
Intel 750 Series AIC 1.2TB PCI-Express 3.0 x4 MLC Internal Solid State Drive (SSD) SSDPEDMW012T4X1
Getting 0xc00000bb error after reboot. Have to go back through UEFI boot menu and reselect above drive in order to boot back in to windows.
12-26-2017 04:06 PM - edited 12-26-2017 04:19 PM
I have the same issue I have the MSI X99A Gaming Pro Carbon (MS-7A20) Mother Board with a Intel i7-5820K CPU 3.30GHz and a Samsung SSD 960 Pro M.2 1TB and I cannot update to the latest build of windows 10 this is a major failing from microsoft.
12-27-2017 06:40 AM
Same issue here with MSI X99S Gaming 7 (MS-7885) Motherboard and Samsung SSD 960 PRO
Windows 10 tried 22 times to install the update and failed. The update routine is totaly dumb and does not recognize that the update does not work on my system, instead it ended me being in an update loop forever. To make matters worse I was not always allowed to stop the update process. Seriously Microsoft if you force me to an update make sure it works! We are in 2017 and not 1997... never heard of user experience?
Here the nice list of update fails:
01-02-2018 02:17 AM
I've a MSI X99A Godlike Gaming Carbon and Samsung SSD 960 Evo nVME combination and suffering the same failure during 1703->1709 update so your bug is not just confined to X299 and/or ASUS. Maybe your MS engineers could inform MSI to get them to provide a BIOS fix for my board (if needed) as I very much doubt they would listen to me.
Here's hoping you get a suitable solution to all our bugs when installing 1709 before you remove support for 1703.
01-03-2018 10:20 AM
The Update from 1703 to 1709 dont work!
Motherboard MSI MS-7885 Bios H.C0
01-05-2018 12:22 PM
Still same problems here since Sept. 2017 no update possible.
WIN 10 64 Bit
MSI X99A Raider ( MS-7885) BIOs P.50
Samsung SSD NVMe 960 Treiberversion 10.0.10586.0
please MS can you help!!!
01-10-2018 12:54 PM
no one can help??? no idea? nothing. this sucks. every day my pc is still in a updateloop.
i waste so much time for this and ms is not able to fix it.
01-10-2018 01:22 PM - edited 01-10-2018 01:24 PM
The Microsoft guy said there would be a fix end of January.
I still doubt that with all the updates their currently doing regarding meltdown and spectre.
I have waited since October for a fix and just cba anymore and went for a fresh install today.
Currently running v1709 on my:
Motherboard: X299 MSI GAMING M7 ACK
SSD: Samsung 960 Pro.
Only because I use this drive for OS only I could afford to do a fresh install without fear of deleting anything important and starting again.
It's just the v1703 updating to v1709 that bricks the pc basically.
Doing a fresh install then search for updates gives you the v1709 without ever being on v1703 so it works and if their isn't a fix by the end of this month then just go ahead and do this.
01-11-2018 05:15 AM
01-17-2018 01:46 PM
Same problem for me. MSI X99a gaming pro carbon. Samsung evo 960 m2.
This is going on for months.
What really annoys me is that the update prompts become more and more obnoxious. Please Microsoft stop trying to force an update on me that is broken!
01-20-2018 07:28 AM
What is the status of this fix? Been Pausing updates for months on Win 10 pro because of this...
01-20-2018 08:42 AM
Well... no good news, till now. 0xc00000bb is still a big black hole...
Some times ago, I tried to contact MSI. They excluded that the issue is "mobo or bios" related, and suggested me to format and do a clean install. Oh, well... and my work? My customised production software? I use the workstation as work station...
Samsung released the 5.2 version of Magician software, but not new driver or new firmware (I have the buggy 3b6qcxp7... :( ).
I updated the Intel Rapid Storage Engine to the last version. 0xc00000bb and update failed. And it is able to see only 4 disks of the 7 installed on my system.
Microsoft said that the fix will come in late January, but now the world fights versus Meltdown, Spektre and the other CPU vulnerabilities... I don't think that they are working on a problem that affects a little number of machines... I hope I'm wrong, but...
01-20-2018 08:50 AM - edited 01-20-2018 08:51 AM
It is clear now that Microsoft is never going to fix this issue. If you keep getting the error when trying to reboot you have two choices : Either clean install or stay on 1703. I think it is very unlikely Microsoft will ever bother to issue a fix for the issue.
01-20-2018 09:48 AM
As mentioned before, there were two different issues being worked on. The first one, which affected only certain Intel NVMe devices, is already fixed in the latest cumulative update. Next week's cumulative update is expected to address the second problem, which occurs with x299 chipsets, mostly from ASUS.
I'm still checking to confirm that these will be published as dynamic updates so that they are automatically installed as you are upgrading to Windows 10 1709. (Until that happens, you'll still have the problem unless you manually inject the update yourself, which is not a simple task.)
01-20-2018 09:50 AM
Thanks for the update, Michael. It's nice to know that this problem hasn't been ignored!
01-20-2018 10:34 AM
"Next week's cumulative update is expected to address the second problem, which occurs with x299 chipsets, mostly from ASUS."
Thank you for replying Michael and letting us know, the above is what I have been waiting for!
01-20-2018 10:57 AM
We have heard from various Microsoft reps for weeks and weeks and weeks that the fix is coming. Yet it never comes. I will believe it when I see it.
01-20-2018 11:04 AM
01-20-2018 01:30 PM
I have an ASUS X299-A Prime MOB and a Samsung 960 Pro NVMe SSD. I have been waiting since October for a fix to upgrade to 1709. Nothing yet.
01-22-2018 07:26 AM
i´m still hanging on windows 10 version 10586, it´s not possible to use update 1703 and 1709, since oktober i´m still in a updateloop. how can i make my updates??
Win 10 pro 64bit
MSI X99 Board
32 Gb RAM
NVMe SSD 960 as bootmedium
the main problem is, i use my pc for work, and every day pc downloads the latest updates.
but it failed everytime. because of missing os driver for the ssd. (0xc00000bb),
so restart and windows get back to the old 10586 windows.
but everyday this updates starts from beginning, i cannot stop it. and it kill´s my datatransfer volume for nothing. how can i stop it??? and is it sure that the problem is fixed and of january??
or, how can i stop the windows from updating? only for the time MS need´s for fixing the problem.
i read in many forums, that many people with samsung ssd nvm has the same problem,
not only a few.
i write to samsung many emails, but the only thing they told me, that it is not a problem from samsung, it was a problem from ms, they have to fix it. for my opinion they have to make i big red sticker on there ssd medims: DONT USE IT AS BOOTMEDIUM WITH WIN10.
so what can i do?? someone any help, or tips for me??
i will not going to back win 7.
plesase MS help, let your user not standing in the rain like samsung!
01-25-2018 06:43 AM
i have the same problem, MS phone and chat support cant help. If you try to contact the german MS support... let it be. horrible...
my hardware: msi x99a gaming 7, intel 6850k, nvidia gtx 1080, m2 ssd samsung, 32gb DDR4-2400 ram.
Bluescreen with 0xc00000bb or if windows can start, note appears "update 1709 failed"... can do nothing to fix this issue, no workarround helps, new windows installation doenst help too.
So Microsoft, when we can expect the fix?
01-25-2018 08:41 AM - edited 01-25-2018 08:56 AM
Hi all. I have had the same issue with the BSOD. I wanted to just let anyone who might have the same hardware I have know what I did to get this update working.
ASUSTeK X299 MARK 2
Sambsung SSD 960 EVO 1TB
What I did:
I read on here about updating the motherboard so I updated my ASUS BIOS version to 1102 (most recent) just last night. I then used the 1709 update assistant one more time and it worked flawlessly.
Another thing to note that I did that may or may not have made a difference was:
I deleted anything in the C:\Windows\SoftwareDistribution\Download folder
Deleted the few folders off the C: drive the failed installations added
Renamed the windows update database files (.edb and .jfm files) located in C:\Windows\SoftwareDistribution\DataStore
Renamed the Windows Update Log folder located in C:\Windows\SoftwareDistribution\DataStore as well.
Renamed the SLS folder in C:\Windows\SoftwareDistribution
Renamed the ReportingEvents.log in C:\Windows\SoftwareDistribution
01-25-2018 10:52 AM
BIOS version 1102 seems to have solved the upgrade to 1709 problems for people with ASUS X299 MOB's. If you have an ASUS MOB upgrade the BIOS to 1102 and you should be able to upgrade.
01-26-2018 03:54 AM - edited 01-26-2018 03:55 AM
I have the same problem 1703->1709 and Samsung SSD 960 with MSI X99 Gaming 7, latest BIOS is HF from 2016. BSOD 0xc00000bb with "normal" Update procedure , with manual Update via Update Assistant and also with an downloadet bootable Update DVD, makes no difference at all in any way you are trying
It would be very kind, if anybody find a solution, please let us know here, so that we share a solution, so that we not have to search in 10 different places in the net :)
01-26-2018 10:36 PM
FYI I updated to 1102 as Scott G mentioned and was FINALLY able to install 1709. If you have a ASUS X299 mobo, update the BIOS to 1102, it worked for me as well.
01-28-2018 01:38 PM - edited 01-28-2018 01:38 PM
Hope you're doing well. Currently we have almost end of January. Do you have any information about the patch for the 0XC00000bb FCU Update Error on X99 Mainboards with Intel NVMe SSD?
01-29-2018 02:37 AM - edited 01-29-2018 02:40 AM
After 10 hours attempts I find the way to resolve this problem. This is what I did:
1) Update BIOS to 1102 from asus.com and reset BIOS to default settings(Disabled XMPP and reset my overclock)
2) Make USB flash with MediaCreationTool
3) Make this action from Tim Gall poste:
For PCH Storage Cofiguration I set:
SATA Controllers to disabled (the topmost option). I enabled it again once the upgrade was complete.
For Boot ->CSM I set it to enabled
Boot Devices Control set to UEFI only
Boot Network and Boot Storage Devices set to ignore
Boot from PCIE expansion devices to UEFI first"
4) I open BIOS menu after all system's restarts before update continue. Update was loading, then restart, I click DEL to open menu, quit without change, update continue install.
I don't sure that 3) and 4) is important, but I did and now I have 1709 windows 10 build.
And my config is Motherboard Asus x299 Prime Deluxe+Samsung 960 PRO 512gb
01-30-2018 03:48 AM
01-30-2018 04:30 AM - edited 01-30-2018 04:31 AM
for my understanding. Is it an issue for Microsoft or for the Motherboard Dealer? Don't get me wrong but I do not see any activities on MSI side. I do not see any intensive discussions concerning MS update with MSI x99 on MSI boards.
01-30-2018 08:25 AM
01-30-2018 04:14 PM
So... today Samsung released a new firmware for 960 Pro (4B6QCXP7).
Obviously, on my MSI X99A Workstation, no way to install the FCU. Same error, again and again. I can write a film or a tv serie about this... and MSI doesn't have a new bios/beta bios for my mobo. Thank you...
01-30-2018 11:16 PM
i use samsung magican, but for me, there is no new firmware for the samsung NVMe 960 SSD.
is still the same old one 3B7QCXE7. how do you get the new one??
and today is the last day of january, and MS told all the time, end of january you get a patch.
i think we never get help from MS, MSI or Samsung.
what a story....
01-31-2018 04:48 AM - edited 01-31-2018 11:08 AM
I have also the same problem since the Creators Update (some years already) which was never solved.
As most of you, I have a MSI X99A Raider mobo with an i7 6800K. (960EVO)
I hope it will be soon fixed, because the FCU is trying to update twice per day with the corresponding bsod after updating.
01-31-2018 05:22 AM
same for me, everyday 2 or 3 times, downloading the hole updates. but installation failed.
the problem is, that i can not stop the download. or the update process. so i loose everyday many GB datatranfer for nothing,
and it kill´s my monthly volume.
why they don´t answer??
MSI: no Answer
MS: no Answer, or response, or help
Samsung: ask MS or MSI
01-31-2018 11:10 AM
02-01-2018 10:30 AM
Exactly same problem for me with MSI "X99A"
Its like madness that he forces the user to upgrade to a version every other day and then crashes with blue screen 0xc00000bb and then downgrades to make it work again.
This might even mess up the SSD lifetime...
by Rod Falanga on May 17, 2020
by ferricoxide on May 09, 2020
by Heather Poulsen on May 04, 2020
by KazukiOta on April 17, 2020
by John Wilcox on April 15, 2020