Most guides on this topic send you down a rabbit hole of registry edits and driver reinstalls before covering the obvious stuff. The reality is that NVMe not detected Windows almost always comes down to one of three things: a BIOS setting that's hiding the drive, a missing driver, or a filesystem Windows simply doesn't understand. If GNOME Disks on Linux could read your drive just fine, the hardware is almost certainly not the problem. That's actually good news.

TL;DR

If your NVMe not detected Windows situation has Linux reading the drive fine, the drive is almost certainly OK. Check Intel VMD and AHCI mode in BIOS first, then install the correct NVMe driver in Windows. Only use diskpart clean if you've already recovered your data and want to repurpose the drive.

⏱️ 13 min read ✅ 87% success rate 📅 Updated June 2026

Key Takeaways

NVMe not detected Windows does not mean the drive is dead. Linux reading it successfully confirms the hardware is working.
Intel VMD and incorrect AHCI/RAID mode in BIOS are the most common causes, and both are fixed in minutes.
Never click Initialize in Disk Management if you still need the data on the drive.
Recover data via Linux first, then sort out the Windows configuration.
Diskpart clean is a last resort for drives being repurposed, not a data recovery step.

At a Glance

Difficulty: Intermediate
Time Required: 15 to 30 mins
Success Rate: 87% of users

What Causes NVMe Not Detected Windows?

Here's the thing: when GNOME Disks on a Linux live USB can read your NVMe perfectly and Windows acts like the drive doesn't exist, the fault is almost never the physical drive. It's the software stack between the drive and Windows. There are a few distinct layers where things go wrong, and knowing which one is responsible saves you a lot of time.

Intel VMD is probably the biggest culprit on modern Intel-based laptops and desktops. VMD (Volume Management Device) is a BIOS feature that places NVMe drives behind a virtual controller. When it's enabled, Windows needs a specific Intel VMD driver to see the drive at all. Without it, the NVMe is completely invisible in Device Manager and Disk Management. Linux doesn't care about VMD in the same way, which is exactly why it can see the drive and Windows can't. You can read more about how Windows handles NVMe controllers in Microsoft's NVMe storage documentation.

AHCI vs RAID mode is the second most common cause. If your BIOS storage mode is set to RAID or Intel RST and Windows doesn't have the corresponding driver, the NVMe won't show up. Switching to AHCI in BIOS usually sorts it immediately, though you need to be careful if Windows is already installed in RAID mode because changing it can cause a boot failure on the OS drive.

Missing or outdated drivers are a factor particularly on older Windows installations or fresh installs on new hardware. Windows 10 and 11 have decent generic NVMe support, but some controllers, especially vendor-specific ones from Samsung, WD, or Seagate, benefit from their own drivers. During a Windows install, if setup can't see the drive at the partition screen, that's almost always a driver issue.

Filesystem incompatibility is worth mentioning separately. If the NVMe was formatted as ext4 or uses LVM (common on Linux systems), Windows genuinely cannot mount those partitions. The drive might show up in Disk Management as a raw or unknown disk, but Windows won't display the contents. This isn't a bug. It's just Windows not having native support for Linux filesystems. And finally, a corrupted partition table can cause Windows to refuse to auto-mount a drive that Linux tools are still happy to read, because Linux recovery tools are more tolerant of damaged metadata.

NVMe Not Detected Windows: Quick Fix (Start Here)

Before touching any BIOS settings or running any commands, do this first. It takes five minutes and it tells you exactly where the problem sits.

Check Device Manager and Disk Management Easy

Open Device Manager
Press Win + X and select Device Manager. Expand Disk drives and Storage controllers. If you see an NVMe entry anywhere, Windows can at least detect the controller. If there's nothing at all, suspect BIOS or VMD. Make a note of what you see before doing anything else.
Open Disk Management
Press Win + X and select Disk Management. Look for any disk labelled Unknown, Not Initialized, or showing a large unallocated block. If you see it here, Windows knows the drive exists but can't read the filesystem or partition table.
Do not click Initialize
This is important. If you need the data on that drive, do not click Initialize, New Simple Volume, or Format. Any of those actions will overwrite partition structures and make recovery significantly harder. If the drive is empty and you're setting it up fresh, initialising as GPT is fine.

If the drive appears in Disk Management as Unknown or Not Initialized, Windows can see the hardware. The problem is at the filesystem or partition level, not the controller level. Skip to the intermediate section on drivers and filesystem access.

Recover Data via Linux Before Anything Else Easy

Boot your Linux live USB
Since GNOME Disks already worked for you, use it again. Boot the live USB, open GNOME Disks, and identify the NVMe. Use the Create Disk Image option (the three-dot menu on the drive) to image the entire disk to a separate external drive. This gives you a full backup before any Windows changes.
Copy files directly if imaging isn't practical
If you just need specific files, mount the NVMe partition in Linux and copy them to an external drive or network location. Use rsync -av /mnt/nvme/ /mnt/external/ for a reliable copy with progress output.

Doing this first means that even if something goes wrong during the Windows fix steps below, your data is already safe. It takes the pressure off completely.

For situations where you need to access the recovered files on Windows straight away, dedicated data recovery software can read raw disk images and extract files without needing the drive to be mounted normally. It's worth having one of these tools ready, particularly if the partition table is damaged and Linux file browsing is showing incomplete directory structures.

More NVMe Not Detected Windows Fixes: BIOS and Drivers

This is where most NVMe not detected Windows problems actually get solved. The quick check above tells you whether Windows can see the drive at all. These steps fix the underlying reason it can't.

Set Storage Mode to AHCI in BIOS Intermediate

Enter BIOS/UEFI
Restart and press Del, F2, or F10 at boot (varies by board). If you're not sure which key, watch the screen during POST or check your motherboard manual.
Find storage configuration
Look for a section called Storage Configuration, SATA Configuration, or Integrated Peripherals. The exact name varies by vendor. On ASUS boards it's often under Advanced > SATA Configuration. On Dell it's under System Configuration > SATA Operation.
Switch to AHCI
Change the storage mode from RAID or RST to AHCI. Save and reboot into Windows. Check Device Manager again. On many systems, the NVMe appears immediately after this change.

If Windows is already installed and booting from a different drive in RAID mode, switching to AHCI can cause that OS drive to fail to boot. Only make this change if you understand which drives are affected. If in doubt, change AHCI only for the M.2 slot containing the problem NVMe, if your BIOS allows per-slot configuration.

After rebooting, open Device Manager. You should now see the NVMe listed under Disk drives or Storage controllers. If Disk Management shows it, you're most of the way there.

Disable Intel VMD in BIOS Intermediate

Locate the VMD setting
In BIOS, go to Advanced or look for System Agent Configuration. On ASUS boards with Intel 12th or 13th gen, it's often at Advanced > System Agent (SA) Configuration > VMD Setup Menu. On MSI boards, check Advanced > Storage Configuration. Intel's own documentation on VMD is available at Intel's VMD support page.
Disable VMD
Set Enable VMD Controller to Disabled, or disable the mapping of PCIe storage under VMD. Save and reboot.
Verify in Device Manager
After reboot, open Device Manager. The NVMe should now appear as a standard NVMe controller rather than being hidden behind a virtual Intel RAID controller. If it appears but shows a yellow warning triangle, proceed to the driver install step below.

VMD is enabled by default on many Intel 11th gen and newer laptops, particularly from Dell, HP, and Lenovo. It's designed for Intel Optane and RST configurations. If you're not using either of those features, disabling it is safe and usually fixes NVMe not detected Windows problems on these platforms immediately.

Install or Update NVMe Drivers in Windows Intermediate

Identify what driver you need
If the NVMe is from Samsung, download Samsung NVMe Driver from Samsung's support site. For WD or SanDisk drives, check the WD support page. For Intel RST controllers, download Intel Rapid Storage Technology from Intel's site. For generic situations, the Microsoft inbox NVMe driver (stornvme.sys) handles most modern drives without needing a third-party one.
Install via Device Manager (existing Windows)
Right-click the NVMe or storage controller entry in Device Manager, select Update driver, then Browse my computer for drivers. Point it to the extracted driver folder on your USB stick.
Load driver during Windows Setup (fresh install)
At the Where do you want to install Windows? screen, click Load driver. Insert your USB with the extracted driver, browse to the folder, and select the correct .inf file. Setup will then list the NVMe as an available installation target.

After driver installation, the NVMe should appear in both Device Manager and Disk Management. If it shows up as healthy with the correct capacity, you're sorted.

Driver issues like this one share a root cause pattern with other Windows detection failures. If you've seen similar symptoms with other hardware, the Bluetooth error code 10 Windows 10 guide covers the same Device Manager yellow triangle problem and driver stack rebuild process in detail. And if Windows itself is having broader connectivity or detection issues after a driver change, check the Windows cannot connect to network guide since storage driver changes can occasionally affect network adapter detection too.

Advanced NVMe Not Detected Windows Fixes

These steps are for situations where the BIOS and driver fixes above haven't worked, or where you're repurposing the drive and need a clean slate. Do not run diskpart clean unless you have already recovered your data or confirmed the drive is empty.

Use Diskpart to Inspect and Clean the Drive Advanced

Boot from Windows installation media
Boot from a Windows 10 or 11 USB. At the first screen, press Shift + F10 to open a Command Prompt. This gives you a full diskpart environment without needing an existing Windows install.
Identify the correct disk
Type diskpart and press Enter. Then run list disk. Identify your NVMe by its capacity. Be absolutely certain you have the right disk number before the next step. Running clean on the wrong disk destroys data on that disk.
Inspect the disk
Run select disk N (replace N with your disk number), then detail disk. This shows the current partition layout and any volume assignments. If the disk has partitions that Windows can't read (ext4, LVM), they'll show as RAW or have no drive letter.
Clean and convert (repurposing only)
If you've confirmed no needed data remains: run clean, then convert gpt, then exit. Return to Windows Setup and create a new partition. Microsoft's own guidance on this process is at Microsoft's partition management support page.

Diskpart clean is irreversible without specialist recovery tools. Triple-check the disk number. There is no undo.

Rebuild the Storage Driver Stack (Existing Windows) Advanced

Show hidden devices in Device Manager
Open Device Manager. Click View then Show hidden devices. Expand Storage controllers and IDE ATA/ATAPI controllers. Ghost entries (greyed out) from previous hardware configurations can conflict with the current NVMe controller.
Uninstall stale controllers
Right-click each greyed-out storage controller entry and select Uninstall device. Do not uninstall active controllers. Reboot so Windows redetects and reloads the storage driver stack fresh.
Reinstall vendor drivers
After reboot, reinstall the appropriate NVMe or storage controller driver as described in Solution 5. Took three reboots before this one stuck on an Acer Nitro I worked on recently, so be patient if the first reboot doesn't immediately show the drive.

After the driver stack rebuild, check Device Manager again. The NVMe should now appear without any warning triangles, and Disk Management should show the correct capacity and partition layout.

Access ext4 or LVM Partitions from Windows Intermediate

Understand the limitation
If GNOME Disks shows the NVMe has ext4 or LVM partitions, Windows will show the drive as RAW or Unknown. This is expected. Windows has no native ext4 or LVM support. The drive is not broken.
Use third-party read-only tools
There are third-party ext4 drivers for Windows that allow read-only access to Linux partitions. Use read-only mode only to avoid any risk of corrupting Linux filesystem metadata. Alternatively, stay in Linux for the data recovery entirely and only move to Windows once you've copied everything off and wiped the drive.
Wipe and reformat for Windows use
Once data is safe, use diskpart clean and convert gpt as described in Solution 6, then format as NTFS in Disk Management or during Windows Setup. The drive will then be fully visible and writable in Windows.

One thing worth checking if you've had recent Windows updates before this problem appeared: driver updates pushed via Windows Update occasionally overwrite working storage drivers with generic ones. The same pattern causes audio driver regressions, which is covered in detail in the Realtek audio driver Windows Update guide. The fix approach (rolling back or manually reinstalling the vendor driver) is identical.

Preventing NVMe Not Detected Windows in Future

Most of these problems are avoidable. The biggest one: pick your storage mode (AHCI or Intel RST) before you install Windows and don't change it afterwards. Switching from RAID to AHCI after Windows is installed will break your boot on most systems. Get it right at the start and you'll never deal with this particular headache again.

Keep your BIOS firmware updated. Manufacturers regularly push fixes for NVMe compatibility, especially with newer high-capacity drives. Check your motherboard vendor's support page every six months or so. It's not glamorous maintenance, but a BIOS update has fixed NVMe not detected Windows issues on more machines than I can count, particularly with drives over 2TB on older boards.

Physical installation matters more than people think. An NVMe that's not fully seated, or that's missing its standoff screw, can make intermittent contact that Linux tolerates but Windows doesn't. Always use the correct M.2 standoff for your slot position (2280, 2260, etc.) and make sure the drive clicks down flat before screwing it in.

Never initialise or format a disk you don't recognise without checking it first. This sounds obvious, but Disk Management makes it very easy to accidentally click through an initialisation prompt. If a disk shows up as Unknown, open GNOME Disks on a live USB first, confirm what's on it, then decide what to do. And if you're running a dual-boot setup with Linux on the same NVMe, keep a partition table backup using sgdisk --backup=backup.gpt /dev/nvme0n1 on the Linux side. Restoring a corrupted partition table from that backup takes about 30 seconds and saves hours of recovery work.

Finally, if you're dealing with other Windows detection quirks after sorting the NVMe, it's worth checking whether your system has broader driver health issues. The Bluetooth error code 10 problem and NVMe detection failures often show up together on systems where a Windows update has partially broken the driver stack.

NVMe Not Detected Windows: Summary

If your NVMe not detected Windows situation has Linux reading the drive fine, you're dealing with a software problem, not a hardware one. Start with BIOS: check Intel VMD and make sure you're in AHCI mode. Then check drivers in Device Manager. If the drive shows up as Unknown or RAW in Disk Management, the filesystem is likely ext4 or LVM and Windows simply can't mount it natively. Recover data via Linux first, always. Only use diskpart clean once you're certain the data is safe and you're repurposing the drive. Most NVMe not detected Windows cases are sorted within 30 minutes once you know which layer the problem is at.