Forum Discussion
1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's
1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's
This will be the very first question I will ask in the AMA. I hope you have a better answer than "we are working on it" ready for the thousands of us with this issue and waiting for a fix since September.
https://social.technet.microsoft.com/Forums/en-US/08485ba0-f69f-483b-861e-238f161dabee/problem-with-upgrade-to-creators-update-on-nvme-disk?forum=win10itprosetup
- This is a known issue. The fix for this will be included in the cumulative update that will be released today at 10am via http://catalog.update.microsoft.com (manually downloaded). It will also be included in the next Patch Tuesday cumulative update. (Ref OS #14207031, 11D)
222 Replies
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 512gbThat method also worked for me. My system is very similar to yours except I have have 64 GB of ram and the 1TB ssd. So I did get the 1709 finally installed. But now I seem to have other driver problems with my internal USB hub device and also my "Windows Update" now says "Some settings are managed by your organization" and this prevents me from checking for updates or seeing my updte history. I wonder if you had any similar problems afer your successful upgrade to 1709?
Last weekend I successfully finished the update of my system (MSI X99 + SSD 850) to 1709. It took me 6 hours. Most time was spent waiting for the system. No clean installation.
I was tired to wait for a solution by MSI and/or Microsoft.
My approach was to make a intermediate step via a "normal" disk.
Short description:
1. Image Backup of system disk
2. change SSD to "normal" disk
3. recover image to "normal" disk
4. Because of new hardware set product key again. Otherwise after the update procedure ended with error message like "can't get product key"
4. start update to 1709
5. clean system disk (delete upgrade folder etc.)
6. make image backup of "normal" disk
7. recover image to ssd
8. O gott! BSOD 0x00000bb!
9. select option "start safe mode" from BSOD. system starts in safe mode
10. restart system
11. everthing works fine
Regards
Michael
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.
Hardware:
ASUSTeK X299 MARK 2
Sambsung SSD 960 EVO 1TBWhat 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.
Edit:
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
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.
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.
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!
- A temporary workaround is reboot untill you get the blue screen, press F8 for startup settings.
Then select (7 Disable Driver Signature Enforcement.
This boots the PC. Sometimes it boots after the first reset, sometimes it comes up with the BSOD.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.
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 ;-)
Microsoft released yesterday a new Update called KB4054517.
https://support.microsoft.com/en-us/help/4054517
Will try this update, hope it will fix the 0xc00000bb error for nVME drives.
Erkan Isik wrote:
Microsoft released yesterday a new Update called KB4054517.
https://support.microsoft.com/en-us/help/4054517
Will try this update, hope it will fix the 0xc00000bb error for nVME drives.
Please let us know if this works. Thanks.
Nope KB4054517 (12.12.2017) also didn't work. Got still the Error 0xc00000bb.
I did try it with the normal Win Updater and with the Upgrade Assistent, both got the error.
It really feels like a joke that Microsoft and the Manufacturers didnt patch it already. 1709 was released end of October. Now we have mid December and it's still not fixed...
The 1004 BIOS Update DID NOT fix the problem for me. I just wasted an hour attempting the upgrade using the Windows 10 Update Assistant and it failed with the same BSOD.
ASUS Prime X299-Deluxe
Samsung 960 Pro NVME M.2 SSD
Hi Steven,
I'll put in some more detail about how I got my system to update in the hope its of some help to anyone.
After updating bios to 1004 I made some adjustments to bios PCH Storage Configuration and Boot -> CSM before upgrading to FCU1709.
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
I updated from USB using a fresh copy built with the Media Creation Tool (FCU 1709).
I started the update from windows.
Update went through smoothly. After the update I had to reinstall my antivirus and a few drivers but nothing drastic. Ive read about other experiencing that from the 1709 update but it wasnt a drama to fix. I only noticed something off with a few drivers when stressing my machine with an intensive game after the update.
Seems spot on now. Hope this info helps.
Thanks Tim for sharing your fix. That gives me one more fix procedure to try. I was surprised to see that I did not have the latest BIOS even though I am running the Asus EZ tool that is supposed to check daily for bios updates. I did find the 1004 that you mentioned plus an even newer 1102 version from Jan 17, 2008. So I am manually updating the bios and will follow your procedure to see if that works for my setup.
I to have been having this issue with an X99-A MSI board built by Origin with:
MSI Godlike Gaming Carbon
w/ Samsung 960 Evo NVMe and a Samsung 850 SSD
The update appeared to have issues and recently seemed to try to auto update itself hosing my install to be stuck on a blank boot screen, no amount of repairing startup fixed it so I went back to a recovery USB from Origin.
I seem to agree with the group here that the common denominator seems to be the 960 NVMe but that could just be that its a common NVMe drive.
Considering its already hosed my install and I've gone back to a blank 1703 install I may try some of the workarounds to get to 1709. What's frustrating to me right now is that the Windows Update is stuck wanting to install 1709 so bad that because its failed on restart theres no way I can see to force it to redownload updates or check for new ones. I've gone so far as delete the download files expecting it to check and attempt redownload. Nope, still thinks its there and still thinks it wants me to restart thinking it will install.
I attempted to use the Microsoft tool again to download the update on Wednesday and it didn't seem to pull any new updates as it ended in the same error on install.
Another odd thing is that for the first time I've had my overclocking profile fail twice after shutting down the PC and on the next boot up the next day it fails, I reload the config and it's fine. All hardware checks out. Just odd. No issues until this 1709 stuff started.
- The suggestion I received from many employed by MS was to simply format and re-install Windows. This isn't an option, I run a highly customized system with many apps. A full reinstall would be a tremendous effort, the in place update really needs to work.
I have a brand new system with Asus prime x299 motherboard along with 64 gb ram and i9-7900x cpu and 1TB samsung M.2 ssd. It is now Feb 4 2018. I have installed and reinstalled my brand new windows 10 pro multiple times from the $200 usb stick. I also have dvd and even dowloaded the latest from internet. Everything works great until the update service starts forcing the 1709 defective update on me. Then the problems and harm begins. I have tried every so-called fix on the internet. The update process always leads to BSOD with 0xc00000bb. I am a software engineer with over 30 years experience. Nothing works. Not the trouleshooter, nor any of the other many fixes offered by MS support fotums. Not even the brand new ISO download with 1709. So there is apparently still no solution for this problem after many months. I see that I am not alone. There is no excuse for this. This motherboard is popular and one of the newest out there. The 1709 update was not adequately tested and is defective and is causing harm to many people like me who have wasted many many hours trying to get it to work. Who is responsible and accountable for this blunder at microsoft? We will never know. For now I can only disable the windows update service and pray that someday someone at Microsoft will fix this terrible and embarrassng defective product. This is no different than going to car dealer and buying a new car and then the car won even start. The dealer is happy to take all your money and apologizes for the defective product and promises to get it fixed someday. Meanwhile you have nothing for your money and dealer has no incentive to fix their defect because they already have all your money. Somewhere there might be a smart lawyer or consumer organization who will get dealer attention by class action lawsuit representing all the injured customers. Maybe then the product will get fixed or recalled and the customers will get their money back.
- This is a known issue. The fix for this will be included in the cumulative update that will be released today at 10am via http://catalog.update.microsoft.com (manually downloaded). It will also be included in the next Patch Tuesday cumulative update. (Ref OS #14207031, 11D)
I've been watching the Windows Update Catalog website all day, as of this writing (4:43PM) I don't see it. I'm using the search term "windows 10 cumulative update" and the most recent results are dated as Nov 29th, but they show as being for Build 1709. I would assume by what you suggested we would be seeing a Cumulative Update dated for today, Nov 30th with Build 1703 in the description.
Thank You very much for addressing my question. I am happy that this was resolved and am excited to finally be able to try FCU.
Here are links to just a few of the dicussions regarding this issue. This is widespread and a solution is required.
https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFggtMAA&url=https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F08485ba0-f69f-483b-861e-238f161dabee%2Fproblem-with-upgrade-to-creators-update-on-nvme-disk%3Fforum%3Dwin10itprosetup&usg=AOvVaw2zXfJgTM6FJaq_nGgja4Rf
https://www.google.ca/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uact=8&ved=0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFghBMAI&url=https%3A%2F%2Frog.asus.com%2Fforum%2Fshowthread.php%3F96864-Beware-of-Fall-Creators-Update-with-a-ASUS-x299-MOB-amp-Samsung-NVMe-SSD&usg=AOvVaw1uS12FMzgE7edDudsQmrnR
https://www.reddit.com/r/Windows10TechSupport/comments/7729kq/windows_10_update_1709_fails_to_install_0xc00000bb/
https://www.cnet.com/news/windows-10-fall-creators-update-hits-install-snag-for-some/
