Windows 10 installing Fall Creators Update (Samsung NVME SSD)

windows-10-upgradewindows-10-v1709

I've just clean installed Win 10 1703 (new PC build)

Yesterday I wanted to update to 1709 (Fall Creators Update)
After starting the update, it prompted a restart. After that, Windows would boot to an error screen saying

"0xc00000bbA required device isn't connected or can't be accessed"

I've found similar issues on the internet saying that that's just how it is with Samsung NVMe drives and Windows 10. I guess I need to install Windows anew to get the Fall Creators Update.
What boggles my mind is that I can barely find any threads relating to this issue. I mean, the 960 NVMe SSDs from Samsung are quite popular, why are there only a few old threads on the net? Made me think this might not be such a common issue.

One other thing I've found out is that if I restart using Shift-Click and then select "Startup Repair" it'd reboot and result in the same error I get when trying to update.

What I've tried so far:

  • Update using Windows Update (Now it doesn't show the update anymore…)
  • Update using the Update Utility from Microsoft's website
  • Update using the Media Creation Utility

  • Also played a lot with UEFI settings (Secure Boot, CSM, Fast Boot, etc. nothing seems to work though)

All 3 methods result in the same error.
I think it might be because Windows can't properly boot into recovery (That's also why Startup Repair doesn't seem to work either)

My question now is: Did something go wrong during the Windows install and might a fresh install fix my problems?
Is this behavior expected from an NVMe drive by Samsung?

My specs:

  • i7 7820X
  • Asus X299 Prime Deluxe
  • 32GB G.Skill TridentZ
  • Samsung 960 Evo NVMe (M.2)

I have installed most Asus drivers as well as Samsung's NVMe driver

Best Answer

Success/solution!
I have the same system (more or less, same x299 MB and 960 Pro NVME drive).
I got this to work, finally, after building custom boot media, trying some things reported, like disabling SMART, and more.
Nothing worked, and I was unwilling to trash my install and do a clean one, at least not yet...

What did the deal for me was moving the drive into a "fake RAID" mode, by enabling it under IRST. I'm almost positive this abstracts (i.e. doesn't use) the NVME bus, and then update to 16299.19 (with patch) went off without a hitch, finally!

Afterwards, I "flipped" it back to AHCI, so it could run through NVME and re-installed the Samsung NVME driver.
Under IRST I was getting about 50% performance (50% of the Samsung driver, which gives me about a 40% boost over the Inbox NVME driver), so basically about half-speed of NVME.
I'm set though, and hopefully this will help others that are stuck on the Fall Creators build, with a Samsung NVME drive...
Good thing to "keep in the back of your mind" too, whenever a major update needs to boot minimally, this might still be necessary (depending on NVME Windows integration AND BIOS updates).

Related Question