Question An MS Update on Wed 14th made my 950 Pro Unbootable!?


Junior Member
Aug 17, 2019
Gigabyte GA-Z170-HD3P,
i3-6100 & i7-6700K,
DDR4 2400MHz C15 4GBx2
950 Pro 256GB
Windows 7 Pro (legit ;p)
SSD's are GPT and NVME.

Two computers; one i3 and one i7.
Built about a month apart, about a three years ago.
Now in to different homes.
On Wed the 14th both compputer's owners called with same symptoms:
They both boot to Windows Recovery Options (Select a keyboard...).
Because they 'failed' on the same day I think it must be due to a Windows Update.
Windows 7 on NVME might be a relatively uncommon combination.
Hence I'm not seeing anything about the problem.
The computer with the i7 in it is on my workbench.

If I swap SSD's with my own computer...
their computer properly boots my SSD to my OS but...
my computer boots their SSD to the same Windows Recovery Options.

Their drive doesn't show up in (their computer's) BIOS as NVME or SATA but...
the BIOS's Boot Options shows Windows Boot Manager.
BIOS's Boot Menu shows a blank entry which i think is the hardware SSD.
They both boot to the same Windows Recovery Options.

In Windows Recovery Options I get the following:
Startup Repair cannot repair this computer automatically (see pic 1)
System Restore fails (see pic 2)
System Image Recovery fails (see pic 3)
Command Prompt > DiskPart > List Disk shows no fixed (see pic 4)
Command Prompt > RegEdit only shows the temp drive X: and says there's no C:

I've been working for myself as a semi-competent tech for over a decade but I'm stumped.
Any thoughtful comments would be appreciated.
Thank you.


  • 1.jpg
    509.3 KB · Views: 5
  • 2.jpg
    501.5 KB · Views: 4
  • 3.jpg
    516.7 KB · Views: 4
  • 4.jpg
    307.3 KB · Views: 4
Last edited:


Golden Member
Dec 12, 2010
The following article may have a solution but you likely will have to determine first what the system error message is. The article says, to begin with :

If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle:

Bcdedit /set {default} recoveryenabled no
If there is little joy from these options, consider that the free windows 10 upgrade from windows 7 is likely still available. All data would have to be backed up first of course.

How to save data:
On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command prompt
type notepad and press enter
in notepad, select file>open
Use file explorer to copy any files you need to save to USB or hdd


Junior Member
Aug 17, 2019
Hi deustroop,
I appreciate your reply.
Looking into it...

OK, figured it out.
Windows did indeed push a problematic security update KB4512506.
That update knocked out my NVME driver(s?).
Windows couldn't boot conventionally so it booted into the Windows Recovery Environment.
Unfortunately Windows didn't make an NVME compatible or even capable Recovery Environment.
So the SATA(?) Recovery Environment couldn't read the rest of the drive.
So, I made 'F6' NVME driver(s?).
Installed them in the Environment.
Presto, the rest of the SSD was now visible.
Ran a standard Startup Repair.
Everything worked.
Thanks to all who considered my plight.
Last edited: