inaccessible boot device after installing Windows Insider build


paulpchou

Active member
Local time
1:27 PM
Posts
54
OS
Windows 11
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.
 
Windows Build/Version
Windows 11 Insider build 23612

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    Asus
    CPU
    Intel core i5-11-1135G7
    Motherboard
    AsusTek Computer, Inc.
    Memory
    16GB LPPDR4x
    Graphics Card(s)
    Intel iRIS xe
In this video guide, i'm going to talk about the Windows stop code - Inaccessible Boot Device error and the solutions for it.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
Just curious on how to fix access denied in one of the commands in the video.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    Asus
    CPU
    Intel core i5-11-1135G7
    Motherboard
    AsusTek Computer, Inc.
    Memory
    16GB LPPDR4x
    Graphics Card(s)
    Intel iRIS xe
For insider builds please use the insiders feedback hub:





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


 
Last edited:

My Computer

System One

  • OS
    Windows 10
    Computer type
    Laptop
    Manufacturer/Model
    HP
    CPU
    Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
    Motherboard
    Product : 190A Version : KBC Version 94.56
    Memory
    16 GB Total: Manufacturer : Samsung MemoryType : DDR3 FormFactor : SODIMM Capacity : 8GB Speed : 1600
    Graphics Card(s)
    NVIDIA Quadro K3100M; Intel(R) HD Graphics 4600
    Sound Card
    IDT High Definition Audio CODEC; PNP Device ID HDAUDIO\FUNC_01&VEN_111D&DEV_76E0
    Hard Drives
    Model Hitachi HTS727575A9E364
    Antivirus
    Microsoft Defender
    Other Info
    Mobile Workstation
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
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
Will any one of them work?
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?
 

My Computer

System One

  • OS
    Windows 11, Windows 10, Linux Fedora Cinnamon
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.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    Asus
    CPU
    Intel core i5-11-1135G7
    Motherboard
    AsusTek Computer, Inc.
    Memory
    16GB LPPDR4x
    Graphics Card(s)
    Intel iRIS xe
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.
 

My Computer

System One

  • OS
    Windows 11, Windows 10, Linux Fedora Cinnamon
Just curious on how to fix access denied in one of the commands in the video.
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.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP Pavilion
    CPU
    AMD Ryzen 7 5700G
    Motherboard
    Erica6
    Memory
    Micron Technology DDR4-3200 16GB
    Graphics Card(s)
    NVIDIA GeForce RTX 3060
    Sound Card
    Realtek ALC671
    Monitor(s) Displays
    Samsung SyncMaster U28E590
    Screen Resolution
    3840 x 2160
    Hard Drives
    SAMSUNG MZVLQ1T0HALB-000H1
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.
 

My Computer

System One

  • OS
    Windows 11, Windows 10, Linux Fedora Cinnamon

Latest Support Threads

Back
Top Bottom