It also affects Windows 10 installations as well. It is different as it may not be causing BSOD but will cause a non boot situation. Mine is an SM50 as well so it may effect a lot more drives then originally thought but for me it might be the original cause of changing all of the drive letters in my system, at least in the pre windows environment. After the update I started getting a purple screen of death complaining of an Nvidia file. A reboot would give me access for less then a minute and quickly no boot at all. I was stuck in the repair cycle with little clue on what was even wrong. I went into bios as it was the only thing available at the time and saw that it had changed the boot order to the WD drive, which in my case was the H drive for backup, one of six installed drives. I changed it to boot to the Win 7 drive, it was really Win 10, I just never changed the name. At least I access to the full repair loop where I uninstalled the three updates not knowing which was the cause and one would not complete and kept reinstalling later whenever I did get to Windows, but that is a while off at this point. Ok, so I was later able to go back to a restore point before the updates, thinking I was good then I did a SFC /scannow and it would not complete with an error. Then I tried the DISM restore health and it also would give an error of corrupted component store. Then I tried running chkdsk and after about four hours it completed but started looping the repair cycle again with no access to windows.
At this point I knew I had bigger problems, one of them was that chkdsk C: was not running on the C: drive at all. I found this out after getting access to password protected repair functions, who really remembers a password after 20 years when I have always bypassed using it. If I am not mistaken, the install originated with a clean Win 2000 install and every thing else has been an upgrade since then. After finally getting access to the command prompt in the repair loop, I found that all drive letters were changed in the console, every one, and that was what borqed he original no boot issue. Using diskpart after remembering that command, I found that the hidden boot partition was assigned a letter instead of being part of a single drive. From there I was able to reassign every letter to the drives that they should have been, and dropping the assigned letter on the Windows boot partition. I was luck that every drive was a single partition and that I knew the letter assignment of each by the drive name or I would have had to reinstall, something I have always refused to do. There were way more steps that I took that had no effect and have skipped some for length of the post. I have still not fixed the corrupt component store so I can't run the SFC or DISM commands to find and replace corrupt install files but that is my next goal.
While it might be the easiest thing to reinstall, I think that may be what they want. If you trust Bill, you haven't been paying attention.
