After a Windows update your NVMe SSD can feel like a different drive overnight. Boot takes noticeably longer and hangs on the spinning dots, games stutter while loading textures or take forever to get to the main menu, and file transfers or installs crawl. Task Manager shows 100% Active Time on the drive with low throughput, and apps freeze for a second or two when you open them.
This is not something to ignore even if the PC still boots. A slow NVMe after an update usually means Windows changed a driver, power setting, or security feature that is throttling the drive or running heavy background work like re-encryption. Most causes are reversible in minutes without reinstalling anything, but if BitLocker is re-encrypting or the drive is overheating due to a power plan change you should fix it promptly to avoid unnecessary wear. Work through the fixes below in order from quickest to most involved.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Power management and write-cache policy reset | Check Settings > System > Power and Device Manager > Disk drive > Policies. Write caching is unchecked or PCI Express Link State is set to Maximum power savings. | Easy (2 minutes) |
| Microsoft NVMe driver replaced manufacturer driver | Open Device Manager > Storage controllers. Controller shows Standard NVM Express Controller after the update instead of Samsung, WD, or Intel driver. | Easy (5 minutes) |
| BitLocker / Device Encryption re-encrypting in background | Go to Control Panel > System and Security > BitLocker Drive Encryption or Settings > Privacy & security > Device encryption. Status shows Encryption in progress with a percentage. | Easy – wait to finish |
| Virtualization-based Security and Memory Integrity re-enabled | Open Windows Security > Device security > Core isolation details. Memory integrity is On. System Information shows Virtualization-based security as Running. | Moderate (restart required) |
| Outdated chipset driver or firmware and TRIM not running | Check Device Manager > Storage controllers driver date and run Optimize Drives. Last retrim or last optimized date is weeks ago or status is Needs optimization. | Moderate (10-15 minutes) |
| Corrupted update files and storage stack | Run Settings > Windows Update > Update history. Latest cumulative update shows Failed or Requires restart. SFC / DISM reports corruption. | Moderate (15-30 minutes) |
Fix 1: Reset Windows Power and Write-Cache Policy for Your NVMe Drive
What causes it
Feature updates often reset your power plan to Balanced and re-enable PCI Express Link State Power Management. That setting aggressively downclocks the PCIe link to save power, which starves an NVMe drive that expects a full PCIe 3.0 or 4.0 link. Updates also clear the write-caching policy that lets Windows buffer writes in cache before flushing to the drive.
How to check
Press Windows + R, type powercfg.cpl and press Enter. Note your active plan. Click Change plan settings > Change advanced power settings. Expand PCI Express > Link State Power Management and see if it is set to Maximum power savings. Then press Windows + X > Device Manager > expand Disk drives > right-click your NVMe drive > Properties > Policies tab. See if Enable write caching on the device is unchecked.
What to do
In the Advanced Power Settings dialog, set PCI Express > Link State Power Management to Off for both On battery and Plugged in if you are on a desktop. For laptops, set it to Moderate power savings while on battery and Off while plugged in. Click Apply. Next, in Control Panel > Power Options, select High performance or if you are on Windows 11, go to Settings > System > Power & battery > Power mode and set it to Best performance while you test. In Device Manager > Disk drives > your NVMe > Properties > Policies, check Enable write caching on the device. Leave Turn off Windows write-cache buffer flushing unchecked unless you have a battery backup or UPS. Click OK and restart.
How to undo it
Reopen powercfg.cpl > Change advanced power settings and set Link State Power Management back to Maximum power savings or Moderate power savings. In the same Policies tab, uncheck Enable write caching on the device to return to the safer default.
Fix 2: Restore the Correct NVMe Controller Driver
What causes it
Windows Update frequently replaces the manufacturer NVMe storage controller driver with the generic Standard NVM Express Controller (stornvme.sys). The generic driver works but can disable vendor-specific power and queue handling, which reduces performance on many Samsung, Western Digital, SK Hynix, and Intel drives. As of early 2026, this replacement still happens after major cumulative updates even if you installed the vendor driver manually.
How to check
Press Windows + X > Device Manager > expand Storage controllers. Right-click the NVMe Controller entry > Properties > Driver tab. Check Driver Provider and Driver Date. If Provider is Microsoft and Date is recent, Windows switched the driver. Also check Event Viewer > Windows Logs > System for Source: stornvme events right after the update time.
What to do
In Device Manager > Storage controllers, right-click the controller > Update driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer. If your manufacturer driver is listed, select it and click Next. If not, download the chipset and NVMe driver from your motherboard or laptop support page or the SSD vendor’s support page, then use Browse my computer for drivers > Browse and point to the folder with the .inf file. Install, then restart when prompted. Do not use Driver rollback if the previous driver was also Microsoft’s generic driver.
How to undo it
Return to Device Manager > Storage controllers > Properties > Driver tab > Roll Back Driver if available, or click Update driver > Search automatically for drivers to let Windows reinstall the Microsoft Standard NVM Express Controller. Restart after changing.
Fix 3: Wait For or Pause BitLocker Re-Encryption
What causes it
Major updates sometimes suspend and then resume BitLocker or Device Encryption for your system drive. While the drive is encrypting or decrypting in the background, every read and write is handled with extra processing and the drive stays highly active, which makes everything feel slow even though Task Manager may not show a clear culprit.
How to check
Press Windows + R, type manage-bde -status and press Enter in an elevated Command Prompt or type Control Panel > System and Security > BitLocker Drive Encryption. Look for Conversion Status and Percentage Encrypted, or Encryption in progress. If you use Device Encryption, go to Settings > Privacy & security > Device encryption and check if it says Encryption in progress.
What to do
If encryption is in progress, plug in your laptop and let it finish without putting the PC to sleep. Avoid running large file copies or games until it completes. You can check progress again with manage-bde -status in Command Prompt (Admin). If you need the system usable immediately and you fully understand the security trade-off, open Command Prompt (Admin) and run manage-bde -pause C: to pause, then manage-bde -resume C: later when you can let it finish overnight. Do not turn off BitLocker unless you intend to permanently decrypt.
How to undo it
If you paused it, run manage-bde -resume C: in an elevated Command Prompt to continue. If you suspended protection with manage-bde -protectors -disable C:, re-enable it with manage-bde -protectors -enable C:. No restart is needed for pause or resume.
Fix 4: Turn Off Memory Integrity and Other VBS Features If They Were Re-Enabled
What causes it
Windows updates can re-enable Virtualization-based Security features such as Memory integrity (HVCI) and Windows Defender Application Guard, even if you previously disabled them for performance. These features add virtualization checks to every I/O path and are known to reduce storage throughput on some gaming PCs, especially on older CPUs.
How to check
Go to Windows Security > Device security > Core isolation details. Check if Memory integrity is On. Then press Windows + R, type msinfo32 and press Enter. Scroll to the bottom of System Summary and read Virtualization-based security and Kernel DMA Protection. If Virtualization-based security shows Running and you did not turn it on, an update enabled it. Also check Settings > Privacy & security > Windows Security > Device security for any yellow warnings about Core isolation.
What to do
In Core isolation details, toggle Memory integrity to Off and restart when prompted. If you also see Local Security Authority protection causing issues, leave it On unless Microsoft Defender specifically warns that it is off. For systems where VBS was enabled by the update via Group Policy, press Windows + R, type gpedit.msc, go to Computer Configuration > Administrative Templates > System > Device Guard > Turn On Virtualization Based Security and set it to Disabled, then restart. On Windows Home, use Settings > Privacy & security > Device security > Core isolation instead of gpedit.msc.
How to undo it
Reopen Windows Security > Device security > Core isolation details and toggle Memory integrity back to On, then restart. If you changed the Group Policy setting, set Turn On Virtualization Based Security back to Not Configured and restart.
Fix 5: Update Chipset Drivers, NVMe Firmware, and Re-Enable TRIM
What causes it
An outdated chipset driver or old NVMe firmware may be incompatible with changes in the Windows storage stack. After an update, Windows may not send TRIM commands efficiently if the Optimize Drives schedule was disabled or if the drive firmware needs an update to handle new power states. Without regular TRIM, free blocks are not cleared and sustained writes get slower over time.
How to check
Press Windows + X > Device Manager > Storage controllers and System devices. Check driver dates for your AMD or Intel chipset. Then press Windows + S, type Defragment and Optimize Drives and open it. Select your NVMe drive (listed as Solid state drive) and look at Last run and Current status. If TRIM never ran after the update or Optimization is disabled, note it. Press Windows + X > Device Manager > Disk drives > your NVMe > Properties > Details tab > Property: Hardware Ids and Firmware Revision to see current firmware.
What to do
Install the latest chipset driver package from your motherboard or laptop manufacturer’s support page, not from a generic driver utility. Restart. Check the SSD vendor’s toolbox (Samsung Magician, WD Dashboard, Crucial Storage Executive, Intel Memory and Storage Tool) and install offered firmware updates while on AC power and without interrupting the update. Then return to Defragment and Optimize Drives, select the NVMe, click Change settings and check Run on a schedule with Weekly frequency, then click Optimize to run Retrim now. Keep at least 15-20 percent free space on the NVMe drive for best performance.
How to undo it
Firmware cannot be downgraded safely on most drives, so only update if the vendor lists the update as stable. For drivers, go to Device Manager > Storage controllers or System devices > Properties > Driver tab > Roll Back Driver to return to the previous chipset driver. In Optimize Drives, click Change settings and set the schedule back to its previous state or to Off if you prefer manual optimization.
Fix 6: Repair Windows System Files and Storage Configuration
What causes it
A cumulative update can leave corrupted system files or a bad filter driver configuration. Damaged servicing files or a stuck Windows Update cache can keep storage-related services in a retry loop that holds the disk active. Corruption also prevents proper installation of the NVMe driver and power settings you just fixed.
How to check
Press Windows + X > Terminal (Admin) or Command Prompt (Admin). Run sfc /scannow and wait for the result. If it reports integrity violations or cannot repair, run DISM /Online /Cleanup-Image /ScanHealth. Also check Settings > Windows Update > Update history for Failed to install messages. View the System event log at C:\Windows\Logs\CBS\CBS.log for repeated errors if you want more detail, or simply note if sfc finds problems.
What to do
In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth and wait for it to complete without closing the window. Then run sfc /scannow again and restart. If the drive is still slow, reset the Windows storage filter cache: press Windows + R, type regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}. Export that key first (File > Export) as a backup. Check the UpperFilters and LowerFilters values; if a third-party tool left entries there after the update and you no longer use that tool, remove only those specific entries after confirming with the vendor’s documentation. Also run Windows + R, type services.msc, ensure Windows Search and SysMain are Running and set to Automatic, then restart.
How to undo it
If you edited the registry, double-click the .reg backup you exported to restore the original UpperFilters and LowerFilters values. In services.msc, set Windows Search or SysMain back to their previous startup type if you changed them. No other undo is needed for SFC or DISM as they only repair system files.
Fix 7: Roll Back the Update or Repair Install Windows While Keeping Files
What causes it
Sometimes the cumulative update itself contains a regression in the storage stack that no setting fixes. If the slowdown started immediately after a specific KB update and all other hardware checks out, the update’s own drivers or filter changes are the cause.
How to check
Go to Settings > Windows Update > Update history. Note the KB number for the most recent Quality Update that aligns with when slow performance began. Click Uninstall updates at the bottom of that page to open Control Panel > Installed Updates. Check the Installed On date for the KB in question. Also open Settings > System > Recovery and see if Go back or Uninstall latest update is available.
What to do
If you are within the uninstall window (typically 10 days for feature updates, longer for quality updates), go to Control Panel > Programs > Programs and Features > View installed updates or Settings > Windows Update > Update history > Uninstall updates, select the latest KB and click Uninstall, then restart. Test your drive after reboot. If you cannot uninstall or performance is still poor, do an in-place repair: go to Settings > Windows Update > Advanced options > Recovery or download the Windows Media Creation Tool, choose Upgrade this PC now > Keep personal files and apps. This reinstalls Windows without removing your data and refreshes the storage stack. Afterward, re-check power settings and drivers from Fixes 1 and 2.
How to undo it
If you uninstalled an update and want it back, go to Settings > Windows Update > Check for updates to reinstall the latest KB. If you performed the repair install, you can revert within 10 days via Settings > System > Recovery > Go back if the option appears, otherwise keep the refreshed install as it preserves your files and improves stability.
If Nothing Works
If performance is still slow after all fixes, check physical causes that Windows cannot fix. Open Task Manager > Performance > SSD and watch temperature under load; if it repeatedly hits the thermal throttle range shown by your vendor tool (often above 70 degrees Celsius), improve airflow, reseat the drive, and ensure the motherboard heatsink or thermal pad is correctly installed. Run vendor diagnostics: Samsung Magician > Drive Health, WD Dashboard > Tools > S.M.A.R.T., or Crucial Storage Executive > S.M.A.R.T. If health is below 90 percent or Reallocated Sector Count or Media Errors are non-zero, back up immediately.
Test the drive in another M.2 slot if available to rule out a PCIe lane issue introduced by a BIOS update that installed alongside Windows Update. Update your system BIOS from the motherboard vendor with precise model matching, since BIOS updates often bundle NVMe compatibility fixes. If the drive consistently fails vendor diagnostics or shows slow behavior in another PC or slot, replace it under warranty and restore from your backup. For any workflow with valuable data, always back up to a second physical drive before flashing firmware or BIOS.
FAQ
Should I disable SysMain or Windows Search to make my NVMe faster?
Leave both services on Automatic. Updates may reset them, but disabling SysMain (formerly Superfetch) and Windows Search does not speed up modern NVMe drives and can make search and caching worse. If either service is stuck in a high read loop after an update, restart the service in services.msc and run Fix 6 to repair files rather than disabling it permanently.
Does resetting my BIOS help after a Windows update slowdown?
Do not load BIOS defaults blindly. Instead, enter BIOS by pressing Del or F2 during boot and verify that PCIe configuration is set to Auto or Gen4/Gen5 matching your drive, and that ASPM power saving is not set to forced L1. Only update or reset BIOS if your motherboard release notes list NVMe or PCIe stability fixes for your exact board revision.
Will turning on write caching risk data loss?
Write caching improves performance by buffering writes, and on desktops with a UPS it is safe to leave on. If you disable Turn off Windows write-cache buffer flushing, a power loss could lose buffered data, so keep that box unchecked unless you are on a laptop with a healthy battery or a desktop with battery backup. You can find these options in Device Manager > Disk drives > your NVMe > Properties > Policies.
How long should I wait after an update before trying fixes?
Give the PC 30 to 60 minutes on AC power after a major update to finish indexing, .NET optimization, and BitLocker encryption shown in Control Panel > BitLocker Drive Encryption. If the drive is still slow after a full restart and those background tasks show Completed, work through Fixes 1 through 3 first, as they resolve most post-update slowdowns without touching system files.
