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

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

|

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

The other hot fix is KB5003401

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Do you happen to have BitLocker enabled?

Never mind the BitLocker question. Have you updated any drivers recently?

-Eddie

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

No bitlocker. No driver update since last restart. Only thing is the windows update. 

Tried many suggestions from the web, nothing helps. 

Basically, when booting into command prompt and running diakpart, it lists no drive at all. I know the drive is good as it passes the detail bios check and I can even mount and backup files from Linux. The drive is only a few months old.

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I'm looking to see if you are running Advanced Micro Devices, Inc. - SCSIAdapter - 9.3.0.221 in particular. Can you boot into Recovery Mode?

-Eddie

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I don't have any SCSI adapter. Only NVME (windows 10) and a SATA drive (which is not windows).

It first gives me BSOD with 0xc0000001 inaccessible boot device error.

Then I can have the option to boot into safe mode but it never does. It goes into recovery mode. In there, I tried every options there to recover and all of the just failed to do anything because like I mention, if I go into command prompt, it's at X:\ which is not my normal C:\, it looks like a small recovery image.

From there running "diskpart" and "list disk" shows nothing. That's why it cannot repair anything or rollback any patch.  

I booted into linux, I can see all 3 partitions on the NVME drives and can ntfsclone the whole partition with 465GB of data no problem. 

So, all the data and partitions are there but somehow windows won't boot or recognize them. 

Like I said, I can mount the drive in linux and get to any file you want for any diagnostics and log. I backup my files in there but it sucks if I have to re-setup/install everything. So, any help would be appreciated. 

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

We've received a couple of similar reports. For others, they were able to recover by rolling back to a previous restore point, then not installing newer drivers. The one I mentioned previously was one potential culprit. Are you familiar with bcdedit?

-Eddie

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I can definitely figure it out if you can give me some pointers. Just mentioning bcdedit already gives me some thing to read about. Thanks. 

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I made some progress following the step in the last reply of this page: https://social.technet.microsoft.com/Forums/en-US/b228ae18-a637-4887-992f-e3e128e33d74/how-to-fix-inaccessiblebootdevice-windows-10-pro?forum=win10itprogeneral

The key is to use Windows 10 Installation CD/USB recovery instead of the one from the installed drive. The update messed up that recovery as well so it is not seeing the drive at all.

I still get the same error (inaccessable boot device) but at least now I can see my drive c: (osdevice) from the recovery command prompt. 

One odd thing now is that wmic no longer shows the above 2 hotfix is applied. 

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Good news. I tried the "Startup Repair" a couple times and after a few reboot by itself, I got windows to boot again!

2 people found this reply helpful

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

yup, the os is back to the previous build version:

Edition Windows 10 Pro

Version Dev

Installed on ‎4/‎20/‎2021

OS build 21359.1

Experience Windows 10 Feature Experience Pack 321.7601.0.3

Was this reply helpful?

Yes
No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated September 10, 2021 Views 8,053 Applies to: