Fix Windows 11 INACCESSIBLE_BOOT_DEVICE After Intel RST VMD Driver Load on NVMe Systems

ByPriya Nair

The short answer: your SSD is there, it’s just hidden behind a controller Windows doesn’t know about yet

If you’re installing Windows 11 on an Intel 11th Gen or newer laptop and the NVMe drive doesn’t appear, Intel VMD is almost certainly why. VMD — Volume Management Device — is a controller layer Intel introduced for managing PCIe-attached storage, primarily for RAID and Optane setups. Windows 11’s installer ships without VMD drivers, so it can’t see any drives sitting behind that controller.

Loading the Intel RST driver during setup clears that first hurdle. But there’s a second one: if the driver doesn’t get properly integrated into the Windows boot image, the installed OS panics on first restart with INACCESSIBLE_BOOT_DEVICE (stop code 0x7B). That’s the two-stage problem the Dell Inspiron 16 Plus 7630 — and a lot of other 12th and 13th Gen machines — runs into.

Why it happens

Intel VMD acts as a remapping layer between the PCIe bus and the NVMe device. When VMD is active, the SSD doesn’t appear as a standard NVMe drive; it surfaces through the VMD controller instead. The installer’s load-driver step teaches the current session about that controller. It does not guarantee the driver ends up in the right place for early-boot use once Windows is actually installed.

Windows needs the RST VMD driver initialized before the filesystem layer even starts. If it’s absent or loaded too late in the boot sequence, the kernel can’t find its own boot volume and throws the 0x7B stop code. This is a sequencing problem, not a damaged installation — the files are all there.

Fix 1: Offline DISM injection from WinRE (recover without reinstalling)

You don’t need to wipe and start over. Boot from your Windows 11 USB, choose “Repair your computer,” then navigate to Troubleshoot → Advanced options → Command Prompt.

Inside WinRE, identify which drive letter got assigned to your Windows partition. In the recovery environment it’s often D: rather than C:. Run diskpart followed by list vol to check. Then inject the driver offline:

dism /image:D:\ /add-driver /driver:E:\vmddrivers\ /recurse

Replace D:\ with your Windows partition letter and E:\vmddrivers\ with the folder containing the Intel RST VMD driver’s .inf file. The /recurse flag tells DISM to search subfolders automatically. Reboot when it finishes. The boot image now has the driver in place before Windows tries to hand off to the storage stack.

Get the driver package from Dell’s support page for your specific model rather than pulling it straight from Intel — Dell’s builds are validated against the VMD controller configuration on these machines, and the generic Intel package can behave differently.

Fix 2: Disable Intel VMD in BIOS before installing

Cleanest option if you haven’t installed yet, or are willing to start fresh. With VMD disabled, Windows treats the NVMe drive as a plain PCIe device — no driver loading needed during setup, no boot sequencing problem.

On most Intel systems the toggle lives under Advanced → PCIe/Storage Configuration → VMD Setup Menu → Enable VMD Controller. Set it to Disabled and save.

The catch on the Dell Inspiron 16 7630: some BIOS revisions on this machine hide that menu entirely. The VMD toggle simply isn’t there, even after a BIOS update. Community reports suggest it appeared on some motherboard revisions and disappeared after warranty replacements — it looks like a firmware inconsistency rather than an intended omission. If you can’t find the option, move on to the DISM method above.

If you do find and disable VMD, there’s no real downside for a standard single-drive setup. The Inspiron 7630 doesn’t ship with RAID or Intel Optane, which are the only reasons you’d want VMD active to begin with.

Fix 3: Slipstream the driver into your installation media

This prevents the problem before it starts. On a working machine, mount the install.wim from your Windows USB and inject the driver file before running setup:

dism /mount-image /imagefile:D:\sources\install.wim /index:1 /mountdir:C:\mount
dism /image:C:\mount /add-driver /driver:C:\vmddrivers\ /recurse
dism /unmount-image /mountdir:C:\mount /commit

With the driver already baked into the image, the installed OS picks it up from the start. No interactive load-driver step, no post-install injection. This tends to produce the cleanest result on VMD systems and is worth the extra ten minutes of prep if you’re doing multiple installs or expect to reinstall later.

Why the interactive load-driver step during setup sometimes isn’t enough

Clicking “Load driver” in Windows Setup injects the RST VMD driver into the installer’s in-memory environment for that session. The installer can now see the SSD. But whether those driver files also land in the correct boot-critical driver store location in the installed OS depends on driver package structure, installer version, and a few other variables that aren’t fully in your control.

It works for some people and fails for others on identical hardware. That inconsistency is exactly why slipstreaming the media or doing a post-install DISM injection are safer methods on VMD systems — both are deterministic. The interactive step is a session hack; the other two are permanent.

Dell Inspiron 16 Plus 7630: a few model-specific notes

Dell publishes a support article covering Intel 11th through 14th Gen “no drives found” scenarios that links to a validated RST VMD driver package for affected Inspiron models. That’s the right starting point for sourcing the driver — don’t just grab whatever shows up first on a search.

Secure Boot doesn’t need to stay disabled permanently. Turn it off during the installation or DISM injection process if the system requires it, then re-enable it once Windows is running cleanly.

One more thing: Windows Update will sometimes push a newer (or different) Intel RST driver after the first boot. In a small number of cases that update has caused a second boot failure. If your system comes up successfully after using the DISM method, it’s worth checking Device Manager and pinning the VMD controller driver version before running updates, at least until you’ve confirmed the new driver version doesn’t cause issues on your specific machine.

Sources


Similar Posts