Share via

Desktop will not start! freezes with the Below error code! From Prompt, Desktop drives appear to be missing.

Dick Baribeau 20 Reputation points
2026-05-15T22:33:54.77+00:00

ERROR CODE iNACCESSIB;E BOOT DEVICE (oX7B}

diskpart list volume shows "no volume"

Help!

Windows for home | Windows 11 | Performance and system failures

2 answers

Sort by: Most helpful
  1. Ivan B 110.7K Reputation points Independent Advisor
    2026-05-15T23:14:03.71+00:00

    Hi,

    In this case, do the following: access the BIOS and see if the SSD or HDD is being recognized without error.

    Did you make any changes to the BIOS or update it?

    If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

    Thanks

    Was this answer helpful?


  2. Q&A Assist
    2026-05-15T22:34:23.0433333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error INACCESSIBLE_BOOT_DEVICE (0x7B) together with diskpart list volume showing no volumes indicates Windows has lost access to the boot disk entirely. This is usually a storage/boot‑device problem rather than just a file‑system error.

    Work through these steps in order; stop if a step shows the disk is not detected at all (that usually means hardware/OEM repair is required).

    1. Boot into Windows Recovery Environment (WinRE)
      1. Power off the PC.
      2. Power it on and interrupt boot 2–3 times (hold power to force off during the spinning dots) until Automatic Repair appears, or
      3. Boot from Windows 10/11 installation media (USB/DVD). On the Install Windows screen select Next > Repair your computer.
      4. Choose Troubleshoot > Advanced options > Command Prompt.
    2. Check if the disk is detected at all
      1. In Command Prompt, run:
              diskpart
              list disk
        
      2. If no disks are listed, or the system disk is missing, this is a hardware/firmware/controller issue:
        • Power off, check physical connections (SATA/NVMe) if this is a desktop.
        • If a laptop or OEM system, contact the manufacturer or a repair shop; the drive or controller may have failed.
      3. If the OS disk appears in list disk but list volume shows no volumes, there may be severe partition/file‑system corruption or a controller/BIOS mode mismatch.
    3. Check BIOS/UEFI storage settings
      1. Reboot and enter firmware setup (commonly ESC, DEL, or F2; see PC documentation).
      2. Confirm:
        • The system drive is detected in BIOS/UEFI.
        • Any recent changes to storage mode (e.g., AHCI ↔ RAID/IDE/Legacy) are reverted to what they were when Windows was installed.
      3. Save and reboot back into WinRE Command Prompt and re‑run diskpart list disk / list volume.
    4. If the disk and volumes appear, repair file system and system files If after fixing BIOS/UEFI the OS volume shows up again in list volume:
      1. Note the drive letter of the Windows volume (for example, D: in WinRE).
      2. Run Check Disk:
              chkdsk /f /r D:
        
      3. After it completes, run System File Checker against the offline Windows:
              sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows
        
      4. Exit and restart to see if Windows boots.
    5. If Windows still will not boot but disk/volumes are present
      1. Boot again into WinRE.
      2. Use Troubleshoot > Advanced options > System Restore and choose a restore point from before the problem started.
      3. If that fails, consider backing up data from WinRE (using another USB disk) and performing a clean install using the Media Creation Tool image.
    6. If disk is present but volumes never appear
      • This usually indicates serious partition table or boot‑partition corruption, or failing hardware.
      • At this point, data recovery tools or professional recovery/repair are recommended before attempting a clean install, as further writes can reduce chances of recovery.

    If at any stage the OS disk is not visible in diskpart list disk, or BIOS/UEFI does not see the drive, treat it as a hardware failure and involve the OEM or a repair technician.


    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.