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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-05-07T08:45:15+00:00

    Same here - This driver removes all SSDs from my system!!

    i managed to do a restore but the driver keeps installing via windows update !!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-07T09:13:26+00:00

    Deactivate drivers from Windows update: The setting is inside control panel > system > advanced system settings > hardware > device installation settings.

    Just tick disable and your done. Windows update will no longer download any drivers for your devices.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-05-07T09:23:28+00:00

    To disable drivers via Windows Update: control panel > system > advanced system settings > hardware > device installation settings. Just tick disable and your done

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-05-07T09:34:45+00:00

    I did just that - but this no long term solution - there's is a bug by pulling this driver for my system in the first place..

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-05-07T09:35:49+00:00

    PS: I'm on stable - no dev insider build !

    There must bu much more affected by this problem

    Was this answer helpful?

    0 comments