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 No comments

102 answers

Sort by: Newest
  1. Anonymous
    2021-09-06T16:56:07+00:00

    this same driver is affecting me pls how do i roll it back

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-07-26T21:33:01+00:00

    Just to confirm that removing raid driver fixed the problem!

    I have Asus Crosshair VIII Hero WI-FI with two nvme (XPG GAMMIX S50 is bootable) and several ssd drives from which two are used as sata raid.

    First I removed both AMD-RAID Bottom Devices, second one gave me option to delete driver files which I did.

    Then I rebooted into bios and switched sata mode from raid into ahci and then rebooted into windows which caused my raid drive to disappear. Started win11 preview update and finally I didnt get bsod after first autorestart.

    After several autorestarts and win11 update finished I went into bios, switched back sata mode to raid and manually installed raid drivers in win11, restarted again and everything worked perfectly!

    Thank you!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-05-15T10:16:45+00:00

    Same problem here though I'm running at Intel platform.

    What I found helpful is turing on/off PCI Express Native Power Management option in BIOS each time after restarting for installing Insider build. It doesn't matter either on or off all I need to do is turning it. Hope that helps.

    CPU: Intel Core i9 9900K

    MB: ASUS Maximus XI Extreme

    Storage: Intel Optane 900p 480G (system), Samsung 970 Pro+970 Evo Plus+860 Evo

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-05-13T22:20:32+00:00

    Something else that might be possible is use a setupact.log to see if the errant driver is mentioned and what device it is tied to..

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-05-13T15:55:28+00:00

    This is specific to the AMD driver mentioned earlier in this thread. It was incorrectly installed on some devices it wasn't intended for. 

    I know..  I was having unexplained drivers put on my system and it was because of hidden devices..  Something is triggering the system to want to install those drivers..  I understand the Intel situation because it happened to me. 

    I know nothing about AMD systems.. but if they may have something related to some type of eSATA controller in the Bios, it may be relevant.  The fact it shows as a specific controller driver does not necessarily mean that exact controller is involved..

    Was this answer helpful?

    0 comments No comments