Storage devices and their controllers sit on the critical path of everything your computer does, so the software that manages them matters. Most Sata and NVMe drives work out of the box using the standard drivers that ship with Windows, which is why a fresh install can usually see your disk without any extra steps. That built-in support is stable, but it typically does not expose the full feature set of a modern SSD or a platform storage controller.
For NVMe drives in particular, some manufacturers publish their own storage driver that can improve power management and unlock vendor-specific features, while others recommend staying on the Microsoft NVMe driver for maximum compatibility. Platform storage controllers, such as those integrated with Intel and AMD chipsets, may also have vendor drivers that matter when you are running Raid or specific rapid-storage configurations. On a laptop or a prebuilt desktop, the storage controller driver is frequently bundled into the OEM's platform or chipset package, so the most dependable version comes from your computer maker rather than a generic download.
The best practice is to identify exactly what drive and controller you have, decide whether you actually need a vendor driver or can rely on the built-in one, and then obtain any driver directly from the drive maker, the chipset vendor, or your OEM. Just as important as drivers is the firmware on the drive itself and the management software that applies it; keeping drive firmware current can address rare stability or performance issues, but it should be done carefully with the manufacturer's own tool and a good backup in place.
Throughout, treat your data as the priority: back up before firmware changes, avoid third-party updater utilities, and prefer signed packages from the source. Done thoughtfully, matching the right driver and firmware to your specific storage keeps transfers fast, drives healthy, and the system dependable.
A storage driver is the software that lets Windows talk to the controller your drive is attached to, translating file reads and writes into the commands the hardware understands. For ordinary Sata drives and most NVMe SSDs, Windows uses its own built-in drivers, which is why a clean install can usually see the disk immediately. Those drivers are stable and broadly compatible, and for many people they generally do not need to be replaced.
Where a vendor driver earns its place is in the details the generic path leaves out. A drive maker's NVMe driver can refine power management and expose features specific to its SSDs, and a chipset maker's storage driver is what enables Raid arrays and rapid-storage modes on Intel and AMD platforms. On some newer systems a controller mode such as Intel VMD sits in front of the NVMe drives, and its driver has to be present for Windows to see the disks at all.
Separate from all of this is firmware, the code running on the drive itself. Firmware is not a Windows driver; it is applied through the maker's management tool and occasionally fixes a stability or performance issue. Because it rewrites the drive, it deserves the same care and backup discipline you would give any change that touches your data.
Expanded guide insight
The practical storage & nvme context
Storage troubleshooting has one priority above every driver action: protect the data. A missing drive may be a controller, letter, partition, or mode issue—not a failed disk.
Disk Management can reveal a drive missing only a letter.
Changing storage mode can prevent an existing Windows install from booting.
Many NVMe drives work with Windows’ built-in driver.
Take care: Do not initialize, format, or write to a drive with data you need until you understand its condition.
Fast checks for common storage & nvme problems
What you see
Likely area to check
Safe first move
Drive is visible in Disk Management but not Explorer
The volume has no drive letter
Assign a drive letter without formatting
Windows will not boot after a Bios change
Storage controller mode changed
Return the storage setting to its previous value
SSD is not visible during Windows setup
Controller mode or setup support is involved
Stop and identify the storage mode before changing partitions
Start with the lowest-risk check that matches what you see, then return to the detailed sections below if it does not resolve the issue.
Identify your exact device first
In Device Manager, expand Disk drives to read the exact model of each SSD or hard disk installed.
Expand Storage controllers in the same window to see whether an Intel, AMD, or standard controller is handling the drives.
Note whether a drive is NVMe or Sata; NVMe SSDs are typically M.2 sticks on the board, while Sata drives connect by a flat data cable.
For a laptop or prebuilt, the correct controller driver is chosen by the machine's model or service tag rather than by the drive brand.
For a custom desktop, the storage and Raid drivers come from the motherboard model, so note the exact board.
The drive maker's management tool reports the model, firmware level, and Smart health, which confirms exactly what you have before changing anything.
10/11 only where listed for the exact drive or controller package
Labeled MP-series M.2 NVMe drive
Scan the list first, then open the family that matches your hardware for the full reference.
Reference coverage summarizes the Windows releases discussed in this catalog; it is not certified compatibility. Confirm the exact device or PC model, hardware revision, current Windows release, and current package requirements on the publisher source before making a change.
This family name spans several Samsung consumer NVMe generations, but Samsung's NVMe Driver 3.3 does not support all of them: its official guide lists 970 PRO, 970 EVO, 970 EVO Plus, 960 PRO/EVO, and 950 PRO, and lists Windows through Windows 10. It does not list the 980 or 990 families or Windows 11. Those newer drives generally use the Windows NVMe driver; Samsung Magician supports model-specific management and firmware features separately.
How you recognize it
Exact Samsung model checked against the NVMe Driver guide
980/990 models are not listed for NVMe Driver 3.3
Magician feature support varies by model
Optional vendor NVMe driver; many setups run fine on the built-in Microsoft NVMe driver. Use Samsung's management application when a documented firmware update applies.
Reference coverage: support depends on the current model-specific SanDisk/WD utility
This entry covers WD and SanDisk SSD families that normally use Windows storage drivers. Western Digital states that Western Digital Dashboard support has ended and that SanDisk Dashboard supports SSD products; do not rely on the retired WD Dashboard. Firmware availability is model-specific, and the official firmware article directs users to the applicable dashboard or support path.
How you recognize it
Exact WD or SanDisk model and serial
Current utility confirmed on the official support article
Western Digital Dashboard is end-of-support; use the current SanDisk/WD support guidance for the exact SSD.
Reference coverage: support depends on the selected SeaTools release
Seagate BarraCuda, IronWolf, and FireCuda families include different HDD and SSD models that generally use operating-system storage drivers. Seagate documents SeaTools for diagnostics and provides a serial-number firmware lookup; its support page does not substantiate a single Toolkit package that updates firmware across all three families. Match diagnostics and firmware to the exact drive and serial number.
How you recognize it
Exact BarraCuda, IronWolf, or FireCuda model
Firmware searched by serial number on Seagate support
Use SeaTools for diagnostics and Seagate's serial-number lookup for model-specific firmware.
Kingston SSD Manager can monitor health and update firmware for SSDs on its current or legacy supported-drive lists; the family label alone does not establish support. Kingston recommends the SSD's native interface and says USB enclosures are not supported. These drives otherwise use standard Windows NVMe or Sata drivers.
How you recognize it
Exact Kingston model on the current or legacy supported-SSD list
Drive attached through its native interface
Use Kingston's SSD management utility for firmware; standard NVMe/Sata drivers are used for operation.
Reference coverage: 10/11 x64 only as listed for the selected generation package
Intel RST supports Raid, storage controllers, and VMD only on listed Intel platforms. Intel's current 20.2 download lists 12th through 15th Gen Intel Core platforms and requires a VMD-capable Bios for VMD; older generations use separate downloads. Match processor generation, controller mode, Bios capability, and Windows release, and prefer the OEM package on a prebuilt.
How you recognize it
Exact Intel generation listed by the RST package
Raid or VMD mode supported and enabled in firmware
For Intel chipset Sata/NVMe controllers and Raid. Use the computer maker's matched package on a laptop or prebuilt system.
Reference coverage: 10/11 x64 only on package-listed VMD platforms
Intel VMD is present only on supported platforms with VMD-capable Bios configuration. When storage is routed behind VMD, Windows Setup may require the matching RST preinstall driver, but this is not true of every Intel NVMe system. Use the exact OEM or Intel generation package and follow the system maker's setup instructions rather than changing controller mode casually.
How you recognize it
VMD-capable Bios and supported Intel generation
Storage controller hardware ID matched to the preinstall driver
Needed to detect NVMe drives on some newer platforms during and after Windows install; OEM systems ship a matched version.
Reference coverage: 10/11 only where listed for the exact drive or controller package
This driver supports Raid configurations on AMD chipset storage controllers, and it is what keeps an AMD-platform array visible and healthy. It is only needed when you have set up Raid rather than running single drives. On a prebuilt system, obtain the OEM-provided version so it matches your platform; on a custom build, use the motherboard maker's Raid package for your board.
How you recognize it
Used with Raid on AMD chipsets
Listed as an AMD Raid controller in Device Manager
For AMD chipset Raid configurations; on prebuilt systems obtain the OEM-provided package.
Reference coverage: 10/11 only where listed for the exact drive or controller package
This is Dell's OEM package that supplies the storage controller drivers for OptiPlex, Latitude, and XPS systems, matched to your Service Tag. It helps ensure the controller, including any Raid or VMD mode Dell configured, is driven by a version validated for your machine. Use this package on Dell systems rather than a generic chipset driver, and identify it by your Service Tag.
How you recognize it
Chosen by Dell Service Tag
Includes the controller mode Dell configured
OEM storage controller drivers matched to your Service Tag; use these on Dell systems.
Reference coverage: 10/11 only where listed for the exact drive or controller package
HP provides storage and chipset controller drivers for its EliteBook, ProBook, and Pavilion systems as an OEM package chosen by product number. This is the source most likely to work well for the controller driver on an HP machine, since it is tuned to how HP configured the storage. Enter your product number on HP's support site to get the package built for your exact model.
How you recognize it
Chosen by HP product number
Validated for HP's storage configuration
OEM storage/controller drivers by product number for HP systems.
Reference coverage: 10/11 only where listed for the exact drive or controller package
Lenovo supplies the storage controller drivers for ThinkPad, IdeaPad, and Legion systems as an OEM package matched to your machine type and model. It covers the controller and any Raid or VMD mode Lenovo set up, in a version validated for your chassis. Look up your machine type to obtain the correct package rather than relying on a generic chipset driver.
How you recognize it
Chosen by Lenovo machine type and model
Covers the controller mode Lenovo configured
OEM storage controller drivers matched to your machine type/model.
Reference coverage: 10/11 only where listed for the exact drive or controller package
For custom desktops built on ASUS motherboards, the storage and chipset drivers, including any Raid support, come from the ASUS support page for that exact board. These drive the board's Sata and NVMe controllers and enable array configurations. Download the chipset or storage package listed for your specific model, since board families can differ in the controllers they use.
How you recognize it
Used with ASUS desktop motherboards
Chosen by exact board model
For desktop boards; download the chipset/storage package listed for your exact model.
Reference coverage: 10/11 only where listed for the exact drive or controller package
Gigabyte desktop boards get their storage controller and Raid drivers from Gigabyte's support page, selected by board model. These packages cover the chipset's storage controllers and are what enable Raid arrays on the board. Match the driver to your exact model so the controller is handled correctly, especially if you plan to build or maintain an array.
How you recognize it
Used with Gigabyte desktop motherboards
Raid drivers listed per board model
Chipset and Raid drivers per board model on Gigabyte support.
Reference coverage: 10/11 only where listed for the exact drive or controller package
MSI provides storage controller and Raid drivers for its desktop motherboards, listed by board model on MSI support. They handle the Sata and NVMe controllers on the board and are required for Raid configurations. Choose the package for your exact board model so the controller driver matches your hardware and any array stays visible and healthy.
How you recognize it
Used with MSI desktop motherboards
Storage and Raid drivers listed by board model
Storage controller and Raid drivers listed by board model.
Reference coverage: 10/11 only where listed for the exact drive or controller package
ASRock desktop boards get their chipset and storage packages, including Raid support, from ASRock's support page by board model. These drive the board's storage controllers and enable array modes where used. Download the package listed for your specific ASRock board, since selecting the wrong model can leave the controller driven by a generic driver and hide a Raid array.
How you recognize it
Used with ASRock desktop motherboards
Chosen by exact board model
Chipset/storage packages per board model on ASRock support.
Reference coverage: 10/11 only where listed for the exact drive or controller package
Corsair's MP-series NVMe SSDs are M.2 drives aimed at performance desktops and gaming builds. They operate on the standard Windows NVMe driver, so there is no separate Corsair operating driver to install. Corsair's own utility is where you check the drive and apply firmware, which is the tool to use if a firmware update is recommended for your model.
How you recognize it
Labeled MP-series M.2 NVMe drive
Firmware managed in Corsair's utility
Use Corsair's utility for firmware; drives operate on the standard NVMe driver.
Device Driver Guide does not host, mirror, or alter driver files. The official-source citations below are maintained separately from this reference material and never point to third-party mirrors.
Where the correct package usually comes from
For a standalone drive, the maker's management utility is the right place for firmware and health monitoring, and any recommended NVMe driver comes from that same maker. Download the tool directly from the drive brand, such as Samsung, Western Digital, Seagate, or Kingston, and remember that many drives run best on the built-in Windows NVMe or Sata driver, so a vendor driver is optional unless the maker specifically recommends it.
For the storage controller on a laptop or prebuilt PC, go to your PC maker's support site, enter your model or service tag, and take the chipset or storage package they list. That OEM version is validated for your exact hardware, which matters most for Raid and rapid-storage setups. On a custom desktop, get the chipset and Raid drivers from the motherboard maker's page for your board.
Avoid third-party driver-updater utilities for storage; a mismatched or generic controller driver can hide a Raid array or destabilize the disk, so prefer signed packages straight from the drive maker, chipset vendor, or OEM.
Official sources and citations
These links serve two different purposes. A manufacturer support selector helps you find an exact model, but does not prove that a package or feature exists for every product in a family. Claim-specific documents explain the cited technology, requirement, lifecycle, or bounded package example. In either case, check the publisher domain, exact model and hardware revision, operating-system release, supported-products list, and package notes before making a change.
Microsoft Lifecycle: Lifecycle documentation for Windows 10 Home and Pro; separately governed editions and servicing channels can have different dates.
Western Digital: Use this publisher-maintained page to match the exact Western Digital model and operating-system release before selecting a package.
Device Driver Guide is an independent reference, not a repair or technical-support service. It does not host or mirror installers and receives no payment for these links. A named-model package example applies only to the systems and operating systems on that publisher page; it is not a recommendation to install the package across a family. Report a moved or incorrect link through the correction form.
Storage & NVMe reference tables
Built-in driver versus a vendor NVMe driver
Aspect
Built-in Microsoft driver
Vendor NVMe driver
Compatibility
Broad and stable
Tuned to the maker's own SSDs
Power management
Standard
Can be refined on supported drives
Vendor-specific features
Not exposed
May unlock model features
When to use
Most everyday drives
Only if the maker recommends it
Firmware updates
Not handled here
Applied by the maker's separate tool
What you gain and give up by relying on Windows instead of installing the drive maker's driver.
Symptom to likely cause to first safe step
Symptom
Most likely cause
First safe step
Installer sees no NVMe drive
VMD or chipset driver not loaded
Load the driver from a USB stick at setup
Drive in Bios but not Windows
Uninitialized or unallocated disk
Check Disk Management, then initialize
Slow transfer speeds
Wrong slot, heat, or a full drive
Verify the slot and free up space
Raid array disappeared
Mismatched controller driver
Reinstall the matching controller driver
Controller warning icon
Wrong or generic driver
Install the version for your exact model
Drive may be failing warning
Aging or damaged drive
Back up now and check Smart status
Storage complaints often are not driver faults, so triage before you reinstall anything.
NVMe versus Sata drives
Trait
NVMe SSD
Sata drive
Connection
M.2 slot on the board
Flat Sata data cable
Protocol
NVMe over PCI Express
Sata interface
Typical speed
Faster
Slower but broadly compatible
Vendor driver
Optional on most drives
Rarely needed
Common speed limiter
Wrong slot generation or heat
Cable, port, or an aging disk
The two interfaces differ in form, connection, and how you troubleshoot them.
When updating helps, and when it does not
For everyday drives, the built-in Windows storage driver is fine and rarely needs attention, so there is no benefit to updating it while the system is stable. The times a driver change genuinely helps are specific: the Windows installer cannot see an NVMe drive because a controller mode needs its driver, a Raid array requires a matched controller driver, or the drive maker recommends its NVMe driver for a feature you want.
Firmware is the more delicate case. Applying a drive firmware update makes sense only when the maker documents a stability or performance fix that matches a problem you are actually experiencing, not as a routine habit. Read the notes, confirm it applies to your model, and typically back up first.
When a system is running well and no installer, Raid, or documented fix applies, leaving both the driver and firmware alone is the sensible choice.
Before you install anything
Back up important data before any firmware change, since firmware writes directly to the drive and an interruption can be costly.
Identify the exact drive model and the controller in use so you install the right package rather than a generic one.
Decide whether you truly need a vendor driver or whether the built-in Windows driver already meets your needs.
For a controller driver, look up your laptop or prebuilt model, or your motherboard model on a custom desktop, so the version matches your hardware.
Keep the system on stable power and close heavy background disk activity before running a firmware tool.
For an installer that cannot see an NVMe drive, have the chipset or VMD driver ready on a USB stick to load during setup.
How to update storage & nvme drivers
1
Identify the drive and controller
In Device Manager, expand 'Disk drives' and 'Storage controllers' to see your exact model and the controller in use. This tells you whether you have an NVMe or Sata drive and whether an Intel, AMD, or OEM controller is present.
2
Decide if you need a vendor driver at all
Many drives run best on the built-in Microsoft NVMe or Sata driver. Install a vendor storage driver only when the manufacturer specifically recommends it for your drive or when you are running Raid or a special controller mode.
3
Back up before firmware changes
Driver updates are low risk, but drive firmware updates touch the device directly. Make a current backup of important data before applying any firmware so you are protected if the update is interrupted.
4
Get the driver from the right source
For a standalone drive, use the drive maker's tool. For a platform controller on a laptop or prebuilt PC, use the OEM's chipset/storage package for your exact model. For custom desktops, use the motherboard maker's chipset package.
5
Install, then reboot and verify
Run the signed installer, reboot when prompted, and confirm in Device Manager that the intended driver is active. If you updated firmware, use the manufacturer's tool to confirm the new firmware level and that the drive reports healthy.
Confirm the install actually worked
In Device Manager, confirm the intended driver is active under Storage controllers or Disk drives with no warning icon.
If you updated firmware, open the maker's tool and confirm it reports the new firmware level.
Check that the drive reports healthy Smart status in the maker's utility after any change.
Confirm the drive appears and is accessible in File Explorer and Disk Management with its data intact.
For a Raid setup, confirm the array is still present and healthy in the controller's management view.
Undoing a bad storage & nvme install
A storage driver can usually be reverted through Device Manager: select the controller, choose Roll Back Driver if it is offered, and reboot to return to the previous working driver without a download. If rollback is unavailable, uninstall the controller entry and reboot so Windows reloads its own standard driver, which may restore basic access to the disk while you find the correct package.
For a Raid or rapid-storage controller, do not initialize or format the member disks if the array vanishes after a driver change; that can destroy the data. Instead reinstall the exact controller driver that matches your platform mode, and confirm the controller mode in Uefi has not changed, since switching it can hide an existing array without touching the data.
Firmware cannot be rolled back like a driver. If a firmware update caused trouble, check whether the maker's tool offers a recovery routine for that model, restore from the backup you made beforehand if data was affected, and contact the maker's support before attempting anything that could overwrite the drive further.
A firmware update that is interrupted by power loss or a crash can corrupt data or leave the drive unusable, which is why a current backup is essential first.
Installing a generic or mismatched controller driver can hide an existing Raid array, and initializing the disks to recover it will destroy the data.
On newer platforms the Windows installer cannot see NVMe drives until the VMD or chipset storage driver is loaded during setup.
Changing the storage controller mode in Uefi can make Windows unbootable or hide an array until the mode is restored.
Third-party driver-updater tools can install the wrong storage driver and cause conflicts that look like a failing drive.
Slow transfer speeds are often a wrong slot, thermal throttling, or a nearly full drive rather than a driver fault, so a driver change may not help.
Mistakes to avoid with storage & nvme
Initializing or formatting Raid member disks to recover a vanished array, which destroys the data.
Updating SSD firmware without a backup, so an interrupted write can cost data.
Installing a generic or mismatched controller driver that hides an existing array.
Blaming the driver for slow speeds that come from a wrong slot, heat, or a full drive.
Changing the storage controller mode in Uefi and then being unable to boot.
Trusting a third-party driver-updater that installs the wrong storage driver.
Assuming every NVMe drive needs a vendor driver when the built-in one is usually fine.
Ignoring a drive-failing warning instead of backing up and checking Smart status.
Situations readers arrive with
I am installing Windows and it says there are no drives found, but my SSD is definitely fitted.
On newer Intel platforms a controller mode called VMD hides the NVMe drive until its driver is loaded. Put the Intel VMD or chipset storage driver from your PC maker on a USB stick and use Load driver at the disk selection screen. Alternatively, check whether VMD can be adjusted in Uefi per the maker's guidance.
After I changed a storage setting, my Raid array vanished and Windows only sees single disks.
Do not initialize or format the member disks, since that can destroy the data. Reinstall the exact controller driver that matches your platform mode, and confirm the storage controller mode in Uefi has not changed. Switching that mode can hide an array without touching the data.
My new NVMe SSD is much slower than I expected in benchmarks and transfers.
Speed problems are usually not a driver fault. Confirm the drive is in a slot that matches its generation, make sure it is not thermally throttling without airflow, and check that it is not nearly full. Only then look at the maker's driver recommendation or a firmware update.
Windows popped up a warning that one of my drives may be about to fail.
Back up your important data immediately, before anything else. Then run the drive maker's diagnostic and check the Smart status in their tool. Persistent reallocated sectors or read errors mean the drive should be replaced, regardless of the driver state.
I want to update my SSD firmware because I read it can fix stability issues.
Only update firmware if the maker documents a fix that matches a problem you are actually having. Make a current backup first, use only the maker's official tool, keep the system on stable power, and do not interrupt the process. If everything is stable, leaving firmware alone is the safer choice.
Symptom-by-symptom troubleshooting
NVMe drive not detected during Windows installation
On some newer platforms the installer needs the Intel VMD or the chipset storage driver loaded. Download the OEM or chipset vendor driver to a USB stick, then use 'Load driver' at the disk selection screen. Alternatively, check whether VMD can be adjusted in Uefi setup per the maker's guidance.
Drive shows in Bios but not in Windows
Open Disk Management to check whether the disk is uninitialized or unallocated. New drives may need to be initialized and formatted. If the controller changed modes, install the matching storage controller driver and reboot.
Slower than expected transfer speeds
Confirm the drive is in the correct slot and interface (for example, a Gen4 NVMe in a Gen4 slot), verify the vendor driver recommendation, and check for a drive firmware update through the manufacturer's tool. Thermal throttling and near-full drives can also reduce speed.
Raid array is missing after a driver change
Do not initialize or format the member disks. Reinstall the exact Raid/storage controller driver that matches your platform mode, and consult the manufacturer's Raid documentation. Changing the controller mode in Uefi can hide an existing array.
Firmware update tool will not run or does not see the drive
Check the manufacturer's supported-model list, operating-system requirements, and connection requirements. Some utilities require a native Sata/NVMe connection and do not support USB enclosures. Back up first; do not disable disk encryption or change controller mode unless the exact manufacturer's procedure requires it and you have secured the recovery key.
Storage controller shows a warning in Device Manager
Note the error code, then reinstall the correct controller driver from the OEM (laptop/prebuilt) or the motherboard maker (custom desktop). A mismatched or generic driver can cause conflicts; use the version listed for your exact model.
Windows warns the drive may be failing
Back up immediately. Run the manufacturer's diagnostic and check Smart status in their tool. Persistent reallocated sectors or read errors indicate the drive should be replaced regardless of driver state.
Frequently asked questions
Do I need to install a special NVMe driver?
Often no. The built-in Microsoft NVMe driver works well for most drives. Install a vendor NVMe driver only if the drive maker specifically recommends it for your model or a particular feature.
What is the difference between a storage driver and drive firmware?
A driver is Windows software that lets the operating system communicate with the controller and drive. Firmware is code that runs on the drive itself. Firmware updates can address stability or performance issues but should be applied carefully with the maker's tool and a backup in place.
Why can't the Windows installer see my NVMe SSD?
Some modern platforms use a controller mode (such as Intel VMD) that requires a driver during setup. Load the OEM or chipset vendor's storage driver at the disk selection screen, or adjust the mode in Uefi per the manufacturer's guidance.
Should I get storage drivers from Intel/AMD or from my PC maker?
On a laptop or prebuilt PC, use the OEM's chipset/storage package for your exact model, since it is validated for your hardware. On a custom desktop, use the motherboard maker's chipset package, which includes the appropriate storage driver.
Is it safe to update SSD firmware?
It can be, and it sometimes fixes real issues, but firmware touches the drive directly. Before updating, back up first, use only the manufacturer's official tool, keep the system on stable power, and do not interrupt the process.
Will updating storage drivers make my PC faster?
Usually not dramatically. Correct drivers check that stability and full feature support, and the right vendor driver or firmware can help in specific cases, but they will not turn a Sata drive into an NVMe one or overcome a nearly full or overheating drive.
Do I need a vendor driver to use Raid?
Typically yes. Raid and certain rapid-storage configurations rely on the platform's storage controller driver. Use the exact version provided by your OEM or motherboard maker to keep the array visible and healthy.
Terms used on this page
NVMe
A fast protocol for SSDs connected over PCI Express, usually as an M.2 stick on the motherboard.
Sata
The older interface for hard drives and many SSDs, connected by a flat data cable.
Raid
A configuration that combines multiple drives for redundancy or speed, requiring a matched controller driver.
Intel VMD
A controller mode that manages NVMe drives and whose driver must be loaded for Windows to detect them.
Firmware
Code running on the drive itself, updated with the maker's tool rather than as a Windows driver.
Smart
A drive's built-in health reporting that can warn of impending failure through the maker's utility.
Device Driver Guide stores a local consent preference to remember your choice. Replit Project Analytics may measure visits and selected site interactions. These local choices do not turn hosting analytics on or off. Custom events exclude form entries and other free-form content. No advertising scripts are active. Read the Cookie Policy.
