Turkey (Turkish)
Germany (German)
Worldwide (English)
Intel officially documents loading an F6 Intel RST/VMD driver through the Windows Setup Load Driver step on affected systems.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
If Windows 11 Setup cannot see SSD/NVMe, diagnose firmware detection, Intel VMD/RST, F6 driver, Load Driver and controller mode safely.
Intel officially documents loading an F6 Intel RST/VMD driver through the Windows Setup Load Driver step on affected systems.
If BIOS/UEFI does not see the SSD at all, the F6 driver is not the first problem; physical/firmware detection must be fixed first.
If the SSD model is absent from firmware storage/NVMe information, do not start by hunting Windows Setup drivers. Check M.2 seating, lane sharing, slot compatibility and whether the SSD is detected elsewhere.
If BIOS sees the SSD but Setup and Diskpart do not, a storage-controller driver is a strong suspect. On Intel VMD/RST systems the inbox Windows driver may not expose the controller.
VMD can manage NVMe devices behind an Intel storage-controller layer. Without the matching controller driver, Setup may not list the physical NVMe as a standard device. That does not mean the SSD is bad.
Intel documents the general F6 method. On laptops and branded desktops, prefer the OEM RST/VMD package for the exact model when available because firmware/controller configuration can be vendor-specific.
After extracting the package to USB, choose Windows Setup → Load driver → Browse and select the folder containing the `.inf` files. Intel documents this F6 'have disk' workflow.
Use Shift+F10, then `diskpart` → `list disk` to check storage visibility independently of the Setup GUI. If the disk appears after loading the driver, the issue was controller recognition rather than partitioning.
diskpart
list disk
exitSome systems permit a fresh VMD-off/AHCI installation on a blank disk. But changing controller mode on an existing Windows installation can break boot-critical driver matching and cause INACCESSIBLE_BOOT_DEVICE 0x7B.
If VMD/RST manages a RAID volume, disabling it can also change array visibility. Do not change controller mode on production RAID without vendor guidance and backup.
Unallocated space is normal on a new blank SSD and Setup can create required partitions. But if a previously used disk suddenly appears entirely unallocated, do not click New or run `clean` before investigating partition metadata and data recovery.
| State | Correct direction |
|---|---|
| BIOS also cannot see it | SSD/slot/firmware detection |
| BIOS sees it, Setup/Diskpart does not | VMD/RST/F6 storage driver |
| Appears after loading driver | Controller driver confirmed |
| Disk visible but old data/partitions missing | Partition/data-recovery assessment |
Do not use destructive boot, BitLocker, firmware, partition or storage commands without backups and a rollback plan. Never copy example drive letters without verification.
No. If firmware sees it, a missing VMD/RST controller driver is a common possibility.
Not blindly if an existing Windows or RAID setup is present. For a blank-disk install, follow OEM guidance.
For boot, storage, RDP or update problems on a Windows VPS or physical server, send the exact error code, Windows version and console screenshot to technical support.