inaccessible boot device after installing Windows Insider build

I received an error message inaccessible boot device after installing Windows Insider build. These are some steps I found online. Will any one of them work?

1. change Default Operating System to Run at Startup in Command Prompt type bcdedit /default {identifier} or bcdedit /set {default} device partition=C:
2. enable AHCI Mode in BIOS
3. disable VMD controller Or are there other better fixes? Startup repair does not work. I can boot Windows after two straight green screen error. By the way, when I reinstalled Windows this week and updated the previous Dev channel build, it didn't have the issue. It is when I tried to installed the latest Dev channel build, the issue happened. It happened after restarting and Windows is working on the update. Scan for disk error didn't fix the issue.

In this video guide, i'm going to talk about the Windows stop code - Inaccessible Boot Device error and the solutions for it.

Just curious on how to fix access denied in one of the commands in the video.

For insider builds please use the insiders feedback hub:





Please test the drive using Sea Tools bootable: (Long Generic test)

Hi there

@paulpchou

It's highly unlikely to be a hardware error.

To fix (this invariably works)

1) boot windows install device
2) select Repair system
3) choose Command mode
4) diskpart
5) list disk
6) select disk xx (your Windows install)
7) list vol
8) select vol xxx (the volume of your windows install -- it will be the one with the size of your windows install)
9) assign letter=y (use any unassigned letter) for this example assume G. If already assigned then skip this step.
10) select vol qqq (should be the efi partition - typically size=100mb)
11) assign letter=S
12) exit

Now re-install the boot loader

a) cd g:\windows\system32
b) g:
c) bcdboot.exe g:\windows /s S: /f UEFI

bootloader should return message boot file successfully copied

reboot PC -- should all be fixed.

Q.E,D

Cheers

jimbo

paulpchou said:

Will any one of them work?

Click to expand...

Booting in ACHI mode is quite an esoteric solution which often doesn't apply; have you checked your disk controller settings in the BIOS?

Since the system was working without any issues before updating to the latest Dev build, and assuming that your disk is healthy, then I should imagine that the latest Dev build has introduced some service configuration change. That can lead to Stop 0x7Bs like you're experiencing.

Are you able to boot into Safe Mode at all?

I haven't tried it yet. I am outside. Will try it. I can boot to Windows. I got the green screen error only twice.

If the crashes are only intermittent then there shouldn't be a service configuration issue, I would check the health of the disk as suggested by the others and take into consideration that you are running a Dev build, so there is a possibility that there is a bug with the build itself.

paulpchou said:

Just curious on how to fix access denied in one of the commands in the video.

Click to expand...

When using Command Prompt to fix boot-related issues, it is common to face the “bootrec /fixboot Access is denied” error. There are many possible reasons for this problem to occur on your computer. In this video, i will help you troubleshoot this error.

I doubt there is anything wrong with the boot loader or the boot manager considering the OP has claimed to be able to boot into Windows successfully. This seems like a bug with the Dev build or a disk which is starting to fail, I'm leaning towards more of an issue with build itself.

I was encountering 'inaccessible boot device' after the first reboot when installing Windows 11 on a BIOS-configured RAID 1 array. It turns out that the RAID drivers I loaded at the start of the installation process were not copied over to the Windows drive. Here's how I used DISM after the first reboot to install the drivers and continue the installation:

1. **Boot into WinRE:** Use your Windows 11 installation media and select 'Repair your computer' to access the Command Prompt.
2. **Identify/Assign Windows Drive:**
* Type `diskpart`, then `list volume`.
* Find the volume corresponding to your Windows installation. If it lacks a drive letter:
* Select it using `select volume #` (replace # with the volume number).
* Assign a drive letter using `assign letter=D`.
* Type `exit` to leave diskpart.
3. **Inject RAID Drivers:** Use the DISM command:
* `DISM /Image:\ /Add-Driver /Driver:E:\Drivers /Recurse`
* Replace `D:\` with your Windows drive and `E:\Drivers` with the path to the RAID driver folder.
* If the drivers are unsigned, add `/ForceUnsigned` to the end of the command.
* If you have a single .inf file, use `DISM /Image:\ /Add-Driver /Driver:E:\Drivers\yourdriver.inf`
4. **Reboot:** Close the Command Prompt and restart. Your installation should proceed as normal.