Inaccessible boot device after latest insider update this morning (build 21364)

Anonymous
2021-04-28T17:55:33+00:00

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

Windows Insider program | Windows Insider preview | Desktop environment and Start menu

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.

0 comments

102 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-05-13T14:27:19+00:00

    Something everyone might want to check is open the Device Manager and allow it to show hidden devices.  If a device shows as greyed out, it is not currently available.  Look for any devices you know for sure are not available to your system and uninstall those.  I am not referring to such devices and USB external drives and such.

    If you have onboard components you don't use on a system, such as special controllers, you might disable those in the Bios, if possible.  

    And keep in mind, RAID is required if you are running an Intel Optane memory configuration.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-05-13T13:45:52+00:00

    Look at your storage controllers. Do you see one that has RAID and Bottom in the title? If so, you are going to want to remove this driver completely from the system.

    -Eddie

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-05-11T00:27:30+00:00

    So for what it's worth prior to this snafu my machine was running in SATA AHCI mode. Having since encountered this error I've reformatted my machine and reconfigured SATA AHCI -> SATA RAID and enabled NVMe RAID so that in the event that Microsoft sends down RAID driver updates again it doesn't break my install /shrug.

    To make these changes, get into the BIOS (Hold Delete on boot) , go to Advanced Mode (hit F2) and then Settings > IO Ports (arrow keys and enter):

    Inside IO Ports go down to SATA Configuration:

    Inside SATA Configuration, select RAID and enable NVMe RAID:

    Then re-install Windows 🙃 I've even manually gone through and updated all the devices to the latest 9.3.1.19 driver stack, and haven't had any issues. RAIDXpert2 seems to still see all the drives just fine, and I haven't noticed any I/O issues.

    The trick to installing the CAB files is extracting them, and then for the AMD-RAID Bottom Device I had to do Update Driver -> Browse my computer... -> Let me pick ... -> Have Disk (select folder where extracted CAB happened, most likely the "Downloads" folder.) -> Click on AMD-RAID Bottom Device -> Next -> Click "Yes" accepting the warning that this driver is not recommended.

    Hopefully this helps someone fix their system or learn something new.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-05-08T08:23:43+00:00

    Same issue, restart after installing Advanced Micro Devices, Inc. - SCSIAdapter updates made boot device inaccessible.

    MB: GIGABYTE X570 AORUS ELITE

    CPU: Ryzen 7 3700X

    MEM: 32GB, 2x16 G-Skill 3600 CL18

    Boot drive: Samsung 980 PRO

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-05-08T02:53:05+00:00

    Had this same issue Gigabyte X570. Fixed after doing a boot repair.

    Wake up this morning and PC is completely BRICKED. No power whatsoever.

    Now please tell me who is responsible for this colossal f*** up?? Why would you push out a driver update and force it upon normal users? Who's smooth brain decision was this?

    I'm now left with a $4000 brick. I'm beyond furious. You guys are pathetic.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments