This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
Nothing works in the recovery mode as it cannot back out the update, cannot repair.
One of the update is kb5003399 and I forgot the other one, will have to boot back to the command prompt.
In the command prompt, I can tell it's not showing my 1TB drive, it's in x:/ with very little space.
Also, wusa.exe doesn't exist in that command prompt.
Can anyone help to get my system booting again?
MB: GIGABYTE X570 AORUS ELITE WIFI AM4 AMD X570
CPU: AMD RYZEN 5 3600 6-Core 3.6 GHz
GPU: Nvidia 1070<feff><feff>
Memory: 64 GB (4 x 16 GB Crucial Ballistix 32GB Kit (2 x 16GB) DDR4-3600 )
Drive: Samsung 1TB 970 EVO NVMe M.2 Internal SSD
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Gigabyte X570 master, I experience same problem with inaccessible-boot-device after installing the driver
BIOS in SATA Configuration
Sata mode from to RAID
and
NVMe RAID Mode to Enable
Windows boot properly and re-detect all my drive under RAID-Controller, I decided to keep new drivers
Another victim of this update. Gigabyte Aorus Pro WiFi, F32 BIOS. Why was this pushed to live when it was identified in preview builds? Why was a RAID driver pushed to a system not using RAID? For a few minutes I thought my motherboard was bricked as it tried to reset itself and went completely dark after several attempts to reboot and get to F8 and force a repair. Reddit is in flames on this and deservedly so, what the hell has happened to QA at Microsoft?
Confirming. Using the Show/Hide Windows update tool I hid the AMD SCSIAdapter 9.3.0221 update and I was able to complete all current Windows Updates, including the Cumulative KB5001391 update.
It is being investigated. While I have not verified myself, there have been reports of using DISM both in this thread as well as other places on how to recover. There's a pretty good set of instructions in this thread on reddit: Driver from Microsoft via Windows Updates: Advanced Micro Devices, Inc. - SCSIAdapter - 9.3.0.221 Warning : Amd (reddit.com)
-Eddie
I can confirm AMD SCSIAdapter 9.3.0.221 is the cause the error.
It is also especially concerning because it cannot be backed out.
I have reinstalled Windows twice because I was unable to recover.
It was the only pending update on a reboot and after reboot it was a brick.
I have booted from a Windows PE environment, and tried to recover.
I am also especially annoyed because Gigabyte keeps resetting the BIOS due to a failed boot, and I have to keep resetting my options, even if its just the System Clock. Its annoying as hell.