![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My computer, a Plex media server with 21TB of data, was also hit with this flaw. My motherboard, a Gigabyte 770TA UD3, has two SATA controllers on board. One a SATA II for SATA drives 4, 5 and 6, and a SATA III (Marvell 91XX) for drives 1 & 2. The Marvell one required a system driver to load prior to windows boot for the SATA boot drive (C:) to work. After many system restores to get an operable computer, I discovered that the Marvell controller was not in the system folder anymore but marked as an unknown device with no driver in device manager. After a long search, I found there is no driver for this anymore, particularly for Windows 10. Probably because the motherboard is so old. A Windows 10 driver is available, from ASUS but only in China/S.E. Asia. LInk to it on windows forum: Link to post on forum for driver
(hxxps://windowsforum.com/resources/marvell-91xx-sata-controller-6gb-driver-for-windows-10.40/)
Installed the driver , device moved back to system device and computer boots normally after update. Maybe this old device (Marvell controller) while no longer supported by Microsoft/Vendor in the "new devices only" west was considered by Windows to be unsupportable during the update and removed by Windows (arbitrarily & unilaterally, they do it all the time, don't deny it MS) leaving thousands if not millions of older computers unable to boot because their boot drives were render inoperative by the update roll up from MS. This is why, if you fight through to the option to system restore & go back to an earlier time, your computer works and then after the update it doesn't. MS is removing a critical system/device driver it doesn't know what to do with and for which it has no Windows 10 driver, killing many older (especially AMD) computers that relied on it. ASUS, based in S.E. Asia, has hundreds of older boards in it's inventory and millions of customers in China running older hardware, they custom made a window 10 driver for these older system rather than face the wrath of millions of angry customers, MS apparent doesn't care about these older less advanced users. They had this unsupported device arbitrarily removed, crippling their computers. Load the win 10 driver from ASUS as instructed in the post and your machine has a Win 10 driver for the Marvell 91XX controller and the update leaves it alone and your computer reboots normally after the update. There are a lot of people in the world not running cutting edge Windows 10 compliant systems. You can't forget about them when you update your OS. Hopes my hours of looking can save some one else the trouble. Hope it helps people with this problem, it certainly did for me.
