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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-04-30T22:29:57+00:00

    Hello,

    Thanks for the article, but the download link inside the article is not working. Looks like the wushowhide.diagcab tool is not longer avaliable.

    Regards.

    Sorry, was not aware. You can get it from MajorGeeks:

    https://www.majorgeeks.com/files/details/wushowhide.html

    Regards,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-30T20:23:04+00:00

    I totally understand the risk here when using the insider build. I am a software engineer myself for 20 years. I know how it is. I have never used Feedback Hub before because I cannot boot into the system when it's broken, I am not sure if it needs to collect any data from the system while it's in the broken state. 

    You are correct, the more data they can get, better for a resolve. Not much one can do if you cannot get into system when broken. As long as they are aware, it helps. This would be ideal for a dual-boot scenario where one could retrieve the logs from the faulty drive or partition. Not a fan of dual-boot myself.

    Regards,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-04-30T20:15:25+00:00

    Hello,

    Thanks for the article, but the download link inside the article is not working. Looks like the wushowhide.diagcab tool is not longer avaliable.

    Regards.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-04-30T19:57:55+00:00

    I totally understand the risk here when using the insider build. I am a software engineer myself for 20 years. I know how it is. I have never used Feedback Hub before because I cannot boot into the system when it's broken, I am not sure if it needs to collect any data from the system while it's in the broken state.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-04-30T18:27:25+00:00

    So, now that I am back to build 21359.1. The AMD SCSI Adaptor driver is not even there. I have Standard NVM Express Controller driver and Standard SATA AHCI Controller. Maybe the update erroneously install the wrong driver that's causing our problem? 

    Hi Andy,

    Could very well be. To be expected with Dev builds, at this point, all one can do is file a FBH report and let the MS engineers resolve. With the millions of hardware configurations out there, truly is quite the task they face, not like apples.

    Regards,

    Was this answer helpful?

    0 comments