Roll Back NVIDIA Driver: 13 Steps, 35 Min [2026]

October 26, 2026

24 min read

NVIDIA shipped GeForce Game Ready Driver 621.01 WHQL, and soon after owners were posting about video playback that freezes after the install. A WindowsForum write-up from October 24 lays out the workaround most of them landed on: roll back to 617.42, the RTX Spark launch driver NVIDIA released earlier. This rollback NVIDIA driver tutorial walks through that move on Windows 11 in 13 steps, with three methods, a PowerShell project, and a long troubleshooting list.

One caveat up front. The freeze is a user-reported problem, and the rollback is a user-reported fix. Several hardware sites say NVIDIA acknowledged the bug, but the driver’s own release page does not list it as a known issue, and nothing official recommends 617.42 for this symptom. Treat the rollback as a sensible troubleshooting step, not an official remedy. If you only want the normal upgrade path instead, our guide to updating graphics card drivers covers it.

By the end you will have a verified copy of 617.42 on disk, a restore point, an exported copy of 621.01 so you can move forward again without re-downloading, a block that stops Windows Update and the NVIDIA App from undoing your work, and a script that repeats the whole routine on any machine. Budget about 35 minutes for a first run.

Google · Preferred Sources

Don't miss new tech stories on Google

Add Tech Insider once in the Google app and our stories appear in your news suggestions.

Add Now

What Is Going Wrong With NVIDIA Driver 621.01

Driver 621.01 is a WHQL-certified Game Ready release for 64-bit Windows 10 and Windows 11. NVIDIA’s download page lists it at roughly 1.04 GB and offers the NVIDIA App as an optional install alongside the display driver. The release was built around two launches: Phantom Blade Zero, which arrives October 28, and Call of Duty: Modern Warfare 4, whose full release followed on October 23. It also added support for Microsoft’s Advanced Shader Delivery in Modern Warfare 4, which uses cloud-precompiled shaders to cut compile stutter.

The complaints started within days. Users describe video playback that locks up in browsers and media players, and some report black screens. Hardware Busters ran a report saying NVIDIA confirmed a bug that freezes video playback and blanks screens, and Igor’s Lab wrote that NVIDIA is investigating the video freezes. According to the WindowsForum article, NVIDIA asked affected users to send watchdog dumps in the 621.01 feedback thread on its forums.

The pattern to look for is narrow. Freezes during video playback, starting right after the 621.01 install, with nvlddmkm Event 153 entries in the Windows System log. If your crashes happen only inside one game, or began before October 21, you are probably chasing a different problem. NVIDIA’s own release notes for earlier drivers show how common version-specific regressions are. Its notes list an Assassin’s Creed Shadows crash after an update to an earlier driver.

Windows itself is not the suspect. Windows 11 version 26H2, also called the Windows 11 2026 Update, reached general availability and full phased rollout for eligible 25H2 and 24H2 devices by October 21, 2026. The evidence so far points at the driver, not the operating system, and the sources do not tie the freeze to 26H2.

Should You Roll Back? A Quick Decision Check

Rolling back costs you something. A newer driver carries game fixes and optimizations, and a downgrade throws those away. So the first job is deciding whether the trade is worth it for your PC. Work through the two lists below before you touch anything.

Signs the Driver Is the Cause

The freezes began after you installed 621.01 on or after October 21, and the machine was stable on the previous driver.
They show up during video playback in more than one app, for example a browser tab and a local media player.
Event Viewer shows nvlddmkm Event 153 entries that line up with the freezes.
Temperatures, RAM and storage tests came back clean, and nothing else changed that week.

Reasons to Stay on 621.01

You play Phantom Blade Zero on launch day and want the Game Ready tuning NVIDIA built for it.
You depend on a fix that only 621.01 carries, such as the Wuthering Waves crash fix with NVIDIA Freestyle filters and DLSS Frame Generation.
You never watch video on the affected GPU, so the reported bug does not touch your workflow.
Your freezes started before October 21, which makes 621.01 an unlikely culprit.

If the first list describes you, go ahead. If the second list describes you better, try a cheaper stopgap first: switch off hardware acceleration in the browser or media player that freezes, and see whether playback stabilizes. That is my own suggestion, not a documented fix, so judge it by results. It sidesteps the GPU video path without giving up the new driver. If it works, you can wait for NVIDIA’s next release.

Prerequisites: What You Need Before You Start

The tutorial assumes a desktop or laptop with a GeForce RTX card that both drivers support. NVIDIA’s pages list 617.42 as supporting the RTX 50 series, including the RTX 5090, 5080, 5070 Ti, 5070, 5060 Ti, 5060 and 5050. The 621.01 page lists RTX 20-series cards and up, plus the RTX 50 family. Older Maxwell, Pascal, Turing and Ampere cards still receive Game Ready driver upgrades according to the 621.01 page.

Operating system: Windows 11 version 26H2 or 25H2, 64-bit. Microsoft recommends staying on 25H2 or 26H2 for continued monthly updates.
Current driver: GeForce Game Ready Driver 621.01 WHQL installed, which you will confirm in Step 2.
Target driver: GeForce Game Ready Driver 617.42 WHQL, downloaded from NVIDIA’s driver site in Step 4.
Shell: Windows PowerShell or PowerShell 7.
Permissions: a local administrator account and the ability to reboot.
Disk space: a few gigabytes free for the installer, the extracted files, and an exported copy of the current driver.
Time: about 35 minutes, plus extra for a 30-minute playback test.

The table below pins down every version in play on October 26, 2026, so you do not mix up branches. Drivers cost nothing. NVIDIA distributes them as free downloads, and Device Manager ships inside Windows.

Component	Version	Date	Role in this tutorial
GeForce Game Ready Driver	621.01 WHQL	Oct. 21, 2026	Newest release, the one you are leaving
GeForce Game Ready Driver	617.42 WHQL	Listed Oct. 6, re-released Oct. 16 for RTX Spark	Rollback target
GeForce Game Ready Driver	Not listed	Earlier release	Too far back, NVIDIA’s notes list a game crash
Windows 11	26H2 (2026 Update)	Generally available by Oct. 21, 2026	Operating system under test
NVIDIA App	Current release	Ongoing	Can offer 621.01 again after you roll back
Device Manager	Built into Windows	Ongoing	Hosts the Roll Back Driver button

What a Rollback Costs You

Every driver bundles fixes and game tuning, so going backward removes some of both. NVIDIA’s announcement of 621.01 headlined Game Ready support for Phantom Blade Zero, Modern Warfare 4 with Advanced Shader Delivery, and the Cyberpunk 2077 DLSS 4.5 update. The 617.42 announcement from October 6 covered a different slate: Modern Warfare 4 with DLSS 4.5, Dragon’s Dogma 2: Dark Arisen, Microsoft Flight Simulator 2024 Sim Update 7, Star Wars: Galactic Racer and Valor Mortis. Back2Gaming’s release summary covers the 621.01 side of that ledger.

Item	Arrived in	What a rollback to 617.42 does
Advanced Shader Delivery for Modern Warfare 4	621.01	Removes it, 617.42 was announced with DLSS 4.5 only
Game Ready tuning for Phantom Blade Zero (launches Oct. 28)	621.01	Launch runs without that driver tuning
Game Ready support for the Cyberpunk 2077 DLSS 4.5 update (Oct. 22)	621.01	Removes it
Fix for Wuthering Waves crashes with Freestyle filters and DLSS Frame Generation	621.01	The crash can come back
Fixes for Star Citizen and Surviving Mars problems	621.01	The problems can come back
Game Ready support for Flight Simulator 2024 Sim Update 7 and Star Wars: Galactic Racer	617.42	Stays in place

NVIDIA’s release notes list the Wuthering Waves, Star Citizen and Surviving Mars fixes under 621.01. Whether any of them matter to you depends on what you play. A competitive shooter player who watches no video on that PC might keep 621.01. A creator who edits and reviews footage all day probably wants 617.42 until NVIDIA ships a corrected build. After the rollback, re-check your per-game profiles and our Nvidia Control Panel settings for gaming walkthrough, because some tuned values can reset when the driver package changes.

Steps 1 to 3: Confirm the Symptom, Record Versions, Protect the PC

Step 1: Confirm the Event 153 pattern. Open Windows Terminal as administrator and query the System log for nvlddmkm events from the last three days. A handful of entries clustered around your freezes is the signature. Zero entries means the driver may not be your problem, and you should stop here before changing anything.

Get-WinEvent -FilterHashtable @{
    LogName      = 'System'
    ProviderName = 'nvlddmkm'
    Id           = 153
    StartTime    = (Get-Date).AddDays(-3)
} -ErrorAction SilentlyContinue |
    Select-Object TimeCreated, Id |
    Sort-Object TimeCreated

Sample output from a machine that hit the bug (illustrative, your timestamps will differ):

TimeCreated            Id
-----------            --
10/24/2026 9:12:41 PM 153
10/24/2026 9:48:03 PM 153
10/25/2026 7:30:19 PM 153

Step 2: Record the driver you have now. Note the exact driver version Windows shows for your NVIDIA card before you change anything. The nvidia-smi tool ships with the driver and prints the version directly. Run it so you have a written baseline.

nvidia-smi --query-gpu=name,driver_version --format=csv,noheader

Get-CimInstance Win32_PnPSignedDriver -Filter "DeviceClass='DISPLAY' AND Manufacturer LIKE '%NVIDIA%'" |
    Select-Object DeviceName, DriverVersion, DriverDate, InfName

NVIDIA GeForce RTX 5080, 621.01

DeviceName               DriverVersion DriverDate           InfName
----------               ------------- ----------           -------
NVIDIA GeForce RTX 5080  32.0.16.2101  10/21/2026 12:00 AM  oem42.inf

Write down the InfName. Windows copies third-party drivers into its driver store under names like oem42.inf, and you need that handle in Step 3 and again in the pnputil method. If the short version printed by nvidia-smi is not 621.01, you are already on something else and this tutorial’s premise does not apply.

Step 3: Create a restore point and export the current driver. The restore point is your parachute for a bad install. The export is a convenience. It saves the 621.01 package from the driver store, so you can return to it later without downloading 1 GB again. Windows limits restore point creation to one per 24 hours by default, so a failure here usually means you already made one today.

Enable-ComputerRestore -Drive "C:\"
Checkpoint-Computer -Description "Before NVIDIA rollback" -RestorePointType MODIFY_SETTINGS

New-Item -ItemType Directory -Force -Path C:\DriverArchive\pre-rollback | Out-Null
pnputil /enum-drivers > C:\DriverArchive\pre-rollback\enum-drivers.txt
pnputil /export-driver oem42.inf C:\DriverArchive\pre-rollback\621.01

Replace oem42.inf with the name from Step 2. The export folder will hold the INF, the catalog file and the driver binaries. Keep it. If 617.42 turns out worse on your hardware, you can reinstall from that folder through Device Manager’s Update Driver, Browse my computer option.

Steps 4 and 5: Download and Verify 617.42

Step 4: Download the installer from NVIDIA. Go to NVIDIA’s official driver download page, choose GeForce, your product series and product, Windows 11 as the operating system, and Game Ready Driver as the download type. The default result is the newest driver, which is 621.01. To get the older one, open the list of previous drivers (NVIDIA labels this area Beta and Older Drivers) and pick 617.42 WHQL. Get it from NVIDIA directly. Do not take a driver from a mirror site, a forum attachment or a bundle on a file host.

NVIDIA’s own October 16 announcement described 617.42 in its RTX Spark form this way: “Download and install the launch-day RTX Spark 617.42 WHQL Game Ready Driver from the NVIDIA app or our website.” On a regular GeForce desktop you want the GeForce build for your card family, not an RTX Spark laptop package. Save the file to C:\DriverArchive\617.42 so it survives the cleanup you may do later. The file name usually follows the pattern of version, desktop, win10-win11-64bit, international, dch, whql.exe, though yours may differ slightly. If your GPU is older and you are unsure it is covered, the driver page’s supported products list settles it.

Our guide on how to update GPU drivers covers the NVIDIA search form if you have never used it. The only difference here is that you intentionally pick the older entry.

Step 5: Verify the signature and record a hash. NVIDIA signs its installers with an Authenticode certificate. Checking it takes seconds and catches a corrupted or tampered download. The SHA256 hash is for your records. NVIDIA does not publish one next to each driver, so the hash helps you detect later corruption of your own archive and lets the script in the project section log what it installed.

$f = Get-ChildItem C:\DriverArchive\617.42\*.exe | Select-Object -First 1 -ExpandProperty FullName

Get-AuthenticodeSignature $f |
    Format-List Status, @{n='Signer';e={$_.SignerCertificate.Subject}}

Get-FileHash $f -Algorithm SHA256 | Tee-Object -FilePath "$f.sha256.txt"

Status : Valid
Signer : CN=NVIDIA Corporation, O=NVIDIA Corporation, L=Santa Clara, S=California, C=US

Algorithm  Hash                                                              Path
---------  ----                                                              ----
SHA256     3F9A...C1D2 (64 hex characters)                                   C:\DriverArchive\617.42\...

The output above is illustrative. Status must read Valid and the signer must name NVIDIA. Anything else, delete the file and download again. The sample hash above is a placeholder. Your real value will be 64 hexadecimal characters.

Steps 6 and 7: Rollback NVIDIA Driver With Device Manager

Windows keeps the previous driver package when it installs a new one, as long as nothing has pruned it. Device Manager can swap back to that package in about a minute, with no download. It is the fastest route and the one to try first. It works only when Windows still holds the older package, and the sources do not promise that the package it restores will be 617.42 specifically. You verify that in Step 7.

Step 6: Use Roll Back Driver. Close your browser, media players and any game launchers first. Then follow this path.

Right-click the Start button and open Device Manager.
Expand Display adapters.
Right-click your NVIDIA GPU and choose Properties.
Open the Driver tab and check the Driver Version and Driver Date fields. They should show the 621.01 build from October 21, 2026.
Click Roll Back Driver. If the button is gray, skip to the clean install method in Steps 8 and 9.
Pick a reason from the list when Windows asks, then confirm with Yes.
Let the screen flicker, then restart Windows when prompted.

Microsoft’s own guidance describes the same workflow. Open the device properties, use the Driver tab, select Roll Back Driver when it is available, restart, and test. If the button is unavailable, Microsoft’s fallback is Update Driver with a search for drivers, or a driver from the manufacturer’s support page. For this scenario the manufacturer page is NVIDIA’s, which is why Step 4 came first.

Step 7: Verify the version that came back. Do not assume the rollback landed on 617.42. Windows restores whichever package it kept, and on a PC that went through several updates that might be a different build. Run the Step 2 commands again.

nvidia-smi --query-gpu=name,driver_version --format=csv,noheader

NVIDIA GeForce RTX 5080, 617.42

If you see 617.42, jump ahead to Step 10. If you see anything else, or the number did not change, move on to the clean install method, which gives you control over the exact version. The NVIDIA Control Panel (System Information) and the NVIDIA App also show the installed version, but nvidia-smi is the quickest cross-check.

Which Rollback NVIDIA Driver Method Fits Your PC

Device Manager is not the only road. Four others exist, and each fits a different situation. Pick by what is broken, not by what sounds most thorough. A deeper method adds time and risk without adding benefit when the simple one already works.

Method	Needs the 617.42 download	Works when Roll Back is gray	Risk level	Best for
Device Manager Roll Back Driver	No	No	Low	A fresh 621.01 install with the old package still stored
Installer with clean installation ticked	Yes	Yes	Low	Most people, and the best default
pnputil remove, then install	Yes	Yes	Medium	Stubborn leftovers of 621.01 in the driver store
DDU in Safe Mode, then install	Yes	Yes	Medium	Black screens, repeated failed installs, mixed driver versions
System Restore point	No	Yes	Medium	An install that left Windows unstable

System Restore deserves a warning. It rewinds system files, drivers and registry settings to a snapshot, which can undo more than you want, including other recent updates. Treat it as a recovery tool, not a routine rollback method. For a routine move from 621.01 to 617.42, the clean install route is the one I would pick for most PCs, and the next section covers it.

Steps 8 and 9: Install 617.42 Yourself, Cleanly

Step 8: Run the 617.42 installer with a clean installation. This method needs no help from Windows’ stored packages. It also resets driver-level settings, which sometimes matters when a bad driver left odd values behind. Save any custom Control Panel profiles first if you want to restore them.

Close every app that uses the GPU, including browsers, Discord, overlays, capture tools and RGB software.
Run the 617.42 installer you saved in C:\DriverArchive\617.42. Accept the default extraction folder and let it unpack.
On the first options screen choose NVIDIA Graphics Driver only. Skip the NVIDIA App for now. It can wait until after you block automatic updates in Step 10.
Choose Custom (Advanced) and tick Perform a clean installation.
Click through the installer. The display will blank for a few seconds more than once, which is normal.
Restart when the installer finishes, even if it does not insist.

Prefer automation? NVIDIA’s installer accepts community-documented switches for silent installs, and the project section below uses them. Test them on your own machine before trusting them on others. Run without the silent switch first if anything looks off, because the visible installer shows error text that silent mode hides.

Step 9: Know the two escalation paths. You may not need either, but it pays to read them now, not at midnight with a black screen. The first is the pnputil path. It deletes the old display driver package from the Windows driver store, then installs 617.42 on a clean slate.

# Disconnect from the network first so Windows Update cannot fetch a replacement driver
pnputil /delete-driver oem42.inf /uninstall /force
Restart-Computer

After the reboot Windows falls back to the Microsoft Basic Display Adapter. Run the 617.42 installer from there, then reconnect to the network. Using the wrong oem number removes the wrong package, so recheck the InfName from Step 2 before you press Enter. The second escalation path is Display Driver Uninstaller in Safe Mode, which scrubs drivers, leftovers and registry entries more aggressively than pnputil does. Our DDU tutorial for cleaning GPU drivers covers its settings in detail. Use it when the first two methods keep failing or when you suspect leftovers from an earlier driver family.

Run Step 7 again after any of these methods. The goal is the same each time: nvidia-smi prints 617.42, and Device Manager’s Driver tab agrees.

Steps 10 and 11: Stop Windows Update and the NVIDIA App From Undoing It

This is where most rollbacks quietly fail. The WindowsForum write-up warns, citing EJS Computers, that the NVIDIA App and Windows Update may offer 621.01 again, and that rolling back and then clicking Update an hour later puts you right back where you started. The same article advises skipping 621.01 until a newer driver lists a fix for the freeze. Two doors need closing.

Step 10: Keep Windows Update out of the driver business. Windows can deliver graphics drivers through quality updates. A Group Policy setting named Do not include drivers with Windows Updates stops that, and the same policy exists as a registry value on Home editions. The commands below set it. This is a machine-wide switch. It affects every driver, not only NVIDIA’s, so note the date you set it and plan to undo it.

$key = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate'
New-Item -Path $key -Force | Out-Null
Set-ItemProperty -Path $key -Name ExcludeWUDriversInQualityUpdate -Type DWord -Value 1

# To undo it later:
# Remove-ItemProperty -Path $key -Name ExcludeWUDriversInQualityUpdate

Also open Settings, then Windows Update, then Advanced options, then Optional updates. If a driver update for your NVIDIA card sits in that list, leave it unticked. The policy blocks automatic delivery, but a manual click can still install what you see there.

Step 11: Tame the NVIDIA App. If you installed the app, open its Drivers area. When it lists 621.01 as available, ignore it. Look through the app’s settings for automatic driver download or notification options and turn them off. The exact labels change between app versions, so read each switch before you flip it. If you skipped the app in Step 8, nothing needs doing here, and you can use NVIDIA’s website for driver downloads until a newer release proves itself.

You can also use plain old discipline as a block. Put a note on your calendar for the day a new Game Ready driver appears, and read the release notes and early user reports before you install anything. A short wait costs nothing, and a bad driver costs an evening. That habit also fits the broader pattern NVIDIA owners have learned from earlier regressions such as the one tied to 616.56.

Steps 12 and 13: Test the Fix and Archive Your Drivers

Step 12: Reproduce the original failure. A rollback only counts if the problem goes away under the same conditions that triggered it. Play the same videos in the same apps that froze before. If you run more than one monitor, test with the same layout, because multi-monitor setups are one of the details worth reporting to others. Let it run for at least 30 minutes. Then count new Event 153 entries since the reboot.

$boot = (Get-CimInstance Win32_OperatingSystem).LastBootUpTime
$hits = @(Get-WinEvent -FilterHashtable @{
    LogName='System'; ProviderName='nvlddmkm'; Id=153; StartTime=$boot
} -ErrorAction SilentlyContinue)
"Event 153 since boot ($boot): $($hits.Count)"

Event 153 since boot (10/26/2026 6:02:11 PM): 0

Zero after a long playback session is the result you want. After a successful rollback, the first launch of each game rebuilds shader caches, so a little stutter on first run is normal. Our guide to the NVIDIA shader cache size explains how to inspect or clear that cache if a title misbehaves after the driver swap.

Step 13: Archive and document. Create a folder layout you will understand in six months. Keep each installer beside its hash file, plus a short text note with the date, the GPU, and the reason you rolled back.

C:\DriverArchive\
    617.42\
        <installer>.exe
        <installer>.exe.sha256.txt
    pre-rollback\
        621.01\                 (exported driver package)
        enum-drivers.txt
    NOTES.txt                    (date, GPU, symptom, result)

That archive pays off twice. It lets you move forward to 621.01 or any later build deliberately, and it protects you if NVIDIA ever pulls a download link. Intel did something similar in April 2026 when it removed Arc driver packages older than 32.0.101.6987 from its Download Center, so keeping your own copy of a known-good driver is a habit worth building for any GPU vendor.

Full Working Project: A Rollback Script You Can Reuse

The steps above take 35 minutes by hand. The two scripts below compress the repeatable parts into a few seconds of typing. The first, Rollback-NvidiaDriver.ps1, checks the installer’s signature, creates a restore point, exports the current driver, counts recent Event 153 entries, runs the installer, optionally applies the Windows Update policy, and writes a log plus a JSON summary. The second verifies the result after you reboot. Save both in C:\DriverArchive\tools.

#Requires -RunAsAdministrator
[CmdletBinding()]
param(
    [Parameter(Mandatory)][ValidateScript({ Test-Path $_ -PathType Leaf })][string]$Installer,
    [string]$TargetVersion = '617.42',
    [switch]$CleanInstall,
    [switch]$BlockWindowsUpdateDrivers,
    [string]$ArchiveRoot = 'C:\DriverArchive'
)

$ErrorActionPreference = 'Stop'
$stamp  = Get-Date -Format 'yyyyMMdd-HHmmss'
$runDir = Join-Path $ArchiveRoot "run-$stamp"
New-Item -ItemType Directory -Force -Path $runDir | Out-Null
$logFile = Join-Path $runDir 'rollback.log'

function Write-Log([string]$Message) {
    $line = '{0} {1}' -f (Get-Date -Format 's'), $Message
    $line | Tee-Object -FilePath $logFile -Append | Write-Host
}

function ConvertTo-NvidiaVersion([string]$WindowsVersion) {
    $p = $WindowsVersion.Split('.')
    $digits = $p[2].Substring($p[2].Length - 1) + $p[3]
    $digits.Insert($digits.Length - 2, '.')
}

$gpu = Get-CimInstance Win32_PnPSignedDriver -Filter "DeviceClass='DISPLAY' AND Manufacturer LIKE '%NVIDIA%'" |
    Select-Object -First 1
if (-not $gpu) { throw 'No NVIDIA display adapter found.' }

$before = ConvertTo-NvidiaVersion $gpu.DriverVersion
Write-Log "GPU: $($gpu.DeviceName) | driver before: $before ($($gpu.DriverVersion)) | INF: $($gpu.InfName)"
if ($before -eq $TargetVersion) { Write-Log 'Already on the target version. Nothing to do.'; return }

$sig = Get-AuthenticodeSignature -FilePath $Installer
if ($sig.Status -ne 'Valid' -or $sig.SignerCertificate.Subject -notmatch 'NVIDIA') {
    throw "Installer signature check failed: $($sig.Status)"
}
$hash = (Get-FileHash -Path $Installer -Algorithm SHA256).Hash
Write-Log "Installer SHA256: $hash"

try {
    Enable-ComputerRestore -Drive "$env:SystemDrive\"
    Checkpoint-Computer -Description "Before NVIDIA rollback to $TargetVersion" -RestorePointType MODIFY_SETTINGS
    Write-Log 'Restore point created.'
} catch {
    Write-Log "Restore point skipped: $($_.Exception.Message)"
}

$exportDir = Join-Path $runDir "exported-$before"
New-Item -ItemType Directory -Force -Path $exportDir | Out-Null
pnputil /export-driver $gpu.InfName $exportDir | Out-Null
Write-Log "Exported current driver package to $exportDir"

$events = @(Get-WinEvent -FilterHashtable @{
    LogName='System'; ProviderName='nvlddmkm'; Id=153; StartTime=(Get-Date).AddDays(-3)
} -ErrorAction SilentlyContinue)
Write-Log "nvlddmkm Event 153 in the last 3 days: $($events.Count)"

$argList = @('-s', '-noreboot', '-noeula')
if ($CleanInstall) { $argList += '-clean' }
Write-Log "Running installer with: $($argList -join ' ')"
$proc = Start-Process -FilePath $Installer -ArgumentList $argList -Wait -PassThru
Write-Log "Installer exit code: $($proc.ExitCode)"

if ($BlockWindowsUpdateDrivers) {
    $key = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate'
    New-Item -Path $key -Force | Out-Null
    Set-ItemProperty -Path $key -Name ExcludeWUDriversInQualityUpdate -Type DWord -Value 1
    Write-Log 'Windows Update driver delivery blocked by policy.'
}

[pscustomobject]@{
    Gpu            = $gpu.DeviceName
    VersionBefore  = $before
    TargetVersion  = $TargetVersion
    InstallerHash  = $hash
    InstallerExit  = $proc.ExitCode
    Event153Before = $events.Count
    WuDriversBlock = [bool]$BlockWindowsUpdateDrivers
    RunDir         = $runDir
} | ConvertTo-Json | Set-Content -Path (Join-Path $runDir 'summary.json')

Write-Log 'Done. Reboot, then run Verify-NvidiaRollback.ps1.'

Run it from an elevated prompt. Windows PowerShell may block unsigned scripts under its default policy, so the example passes a one-time bypass for this single process only.

powershell.exe -ExecutionPolicy Bypass -File C:\DriverArchive\tools\Rollback-NvidiaDriver.ps1 `
    -Installer "C:\DriverArchive\617.42\617.42-desktop-win10-win11-64bit-international-dch-whql.exe" `
    -CleanInstall -BlockWindowsUpdateDrivers

2026-10-26T18:20:04 GPU: NVIDIA GeForce RTX 5080 | driver before: 621.01 (32.0.16.2101) | INF: oem42.inf
2026-10-26T18:20:05 Installer SHA256: 3F9A...C1D2
2026-10-26T18:20:09 Restore point created.
2026-10-26T18:20:31 Exported current driver package to C:\DriverArchive\run-20261026-182004\exported-621.01
2026-10-26T18:20:32 nvlddmkm Event 153 in the last 3 days: 3
2026-10-26T18:20:32 Running installer with: -s -noreboot -noeula -clean
2026-10-26T18:24:47 Installer exit code: 0
2026-10-26T18:24:47 Windows Update driver delivery blocked by policy.
2026-10-26T18:24:47 Done. Reboot, then run Verify-NvidiaRollback.ps1.

The log above is illustrative, and your timings and paths will differ. After the reboot, run the verification script. It checks the version, prints nvidia-smi output, and counts new Event 153 entries inside the window you choose.

param(
    [string]$ExpectedVersion = '617.42',
    [int]$Hours = 1
)

function ConvertTo-NvidiaVersion([string]$WindowsVersion) {
    $p = $WindowsVersion.Split('.')
    $digits = $p[2].Substring($p[2].Length - 1) + $p[3]
    $digits.Insert($digits.Length - 2, '.')
}

$gpu = Get-CimInstance Win32_PnPSignedDriver -Filter "DeviceClass='DISPLAY' AND Manufacturer LIKE '%NVIDIA%'" |
    Select-Object -First 1
$now = ConvertTo-NvidiaVersion $gpu.DriverVersion
$smi = (& nvidia-smi --query-gpu=name,driver_version --format=csv,noheader) -join '; '

$hits = @(Get-WinEvent -FilterHashtable @{
    LogName='System'; ProviderName='nvlddmkm'; Id=153; StartTime=(Get-Date).AddHours(-$Hours)
} -ErrorAction SilentlyContinue)

"Installed (Windows): $now"
"nvidia-smi:          $smi"
"Event 153, last ${Hours}h: $($hits.Count)"
if ($now -eq $ExpectedVersion) { 'RESULT: version OK' } else { "RESULT: expected $ExpectedVersion, found $now" }

With those two files you can roll back a second PC in the time it takes the installer to run. Keep the scripts next to the drivers they were tested with. When a newer driver arrives, the same Rollback script moves you to it, because the target version is a parameter, not a constant.

Common Pitfalls When You Roll Back an NVIDIA Driver

These six mistakes account for most failed or short-lived rollbacks. Each one is easy to avoid once you know it exists.

Letting the driver come back by itself. Windows Update and the NVIDIA App can both offer 621.01 again. Do Steps 10 and 11 right after the rollback, not next week. Rolling back and then clicking Update an hour later puts you right back where you started.
Trusting the Roll Back button blindly. The button restores whichever package Windows retained. It may not be 617.42. Always confirm the version with nvidia-smi, as in Step 7.
Going back too far. A downgrade across several branches can break game support and reintroduce bugs NVIDIA already fixed. Stay with 617.42, the driver released just before 621.01, unless you have a specific reason to go older.
Grabbing the wrong package. NVIDIA publishes GeForce Game Ready drivers and RTX Spark-branded builds for the new laptop platform, and 617.42 itself carries the RTX Spark name. Match the package to your card and your product line, and pick the one listed for Windows 11.
Skipping the restore point. Most rollbacks go fine, which is exactly why people skip the safety net. The one time a black screen follows the reboot, a restore point turns a lost evening into five minutes.
Forgetting to undo the Windows Update block. The policy in Step 10 stops driver delivery for every device, including network and audio chips. Set a reminder to remove it once you are on a fixed driver, or you will wonder months later why Windows never updates anything.

Troubleshooting: 11 Problems and Fixes

Work through these in order if something goes sideways. Each item names the symptom first, then the likely cause and the fix.

Roll Back Driver is grayed out. Windows has no earlier package on file. This happens after a clean install, after DDU, or after the driver store was pruned. Skip Device Manager and use the clean install in Steps 8 and 9.
The installer says the graphics driver cannot find compatible hardware. You grabbed a package for the wrong product line or card family. Recheck the series and product on NVIDIA’s download form, and confirm your card appears on the driver’s supported products list. RTX Spark laptop builds do not belong on a desktop GeForce card.
The installer reports the driver is not compatible with this version of Windows. You picked a 32-bit or non-DCH package, or the wrong operating system in the form. The 617.42 and 621.01 pages both list 64-bit Windows 10 and Windows 11.
Black screen after the reboot. Hold the power button to force a shutdown three times so Windows enters recovery. Then choose Troubleshoot, Advanced options, Startup Settings, Restart, and pick Safe Mode. From there, run the DDU method from the earlier section, or use System Restore with the point you made in Step 3.
nvidia-smi still shows 621.01. The rollback did not complete, or the PC has not rebooted. Restart, then run the Step 2 queries. If nothing changed, a second display adapter, such as integrated graphics, may be the one Device Manager showed you. Check that you opened the NVIDIA adapter’s properties.
Windows Update installs 621.01 again. The policy value did not apply, or an Optional updates entry got clicked. Confirm the registry value from Step 10 exists and equals 1, then run gpupdate /force and reboot.
The NVIDIA App prompts for 621.01 on every launch. That is expected until a newer release replaces it. Dismiss the prompt, avoid the one-click update button, and check its settings for notification options.
Checkpoint-Computer fails with a frequency error. Windows allows one restore point per 24 hours by default. Use the one you already have, or temporarily set the SystemRestorePointCreationFrequency registry value under the System Restore key to 0, create the point, and delete the value afterward.
The silent installer returns a non-zero exit code. Rerun it without the -s switch so the dialog shows the real error. Also close security tools and overlays, which sometimes lock files the installer needs. A reboot-pending state can also trip it, so restart and try again.
Video still freezes after the rollback. Event 153 counts of zero with continuing freezes mean 621.01 was not the only culprit. Test the browser and player with hardware acceleration off, update the display cable or try another port, check temperatures, and try a different monitor layout. If Event 153 entries continue on 617.42, the driver is not your root cause, and rolling back further will not help.
Games look worse or lose features. DLSS 4.5 titles or recent launches may depend on 621.01 tuning, as the earlier table shows. Reapply per-game settings, and consider moving back to 621.01 once NVIDIA lists a fix for the freeze.

One habit prevents a dozen of these. Before any driver change, note the date, the old version, and the symptom. A two-line log turns a vague memory of what happened into evidence you can paste into a forum thread or a support ticket.

Advanced Tips for Driver Version Control

Once the basic rollback works, a few habits make future driver swings painless. None of these are required. They save time when you manage several PCs or when the next regression arrives.

Stage a Known-Good Driver in the Driver Store

Windows can hold multiple versions of the same driver in its store. Adding the exported 617.42 package without installing it keeps a local copy ready for Device Manager’s Roll Back or Update Driver flow. Use pnputil with the add switch and point it at the INF in your archive folder. It stages the package without changing the active driver. Verify with pnputil /enum-drivers afterward, and remove old staged packages with /delete-driver when you are done to keep the store tidy.

pnputil /add-driver "C:\DriverArchive\617.42\extracted\Display.Driver\nv_dispi.inf"
pnputil /enum-drivers | Select-String -Pattern "nvidia" -Context 1,5

The INF file name varies by package, so locate the right one after extracting the installer to a folder with 7-Zip or the installer’s own extraction step. Use the INF that sits next to the display driver binaries, not an audio or USB-C helper INF.

Report Your Result to Help Others

NVIDIA asked affected users for watchdog dumps in its 621.01 feedback thread, according to WindowsForum, and that article invites readers to share their GPU, monitor count, and whether 617.42 fixed the freeze. Those three details are the useful ones. A report that names the card, the number of displays, and the before-and-after result gives engineers and other readers something to work with. Attach your Event 153 counts from the script logs.

Two more ideas round out the toolbox. First, if you rely on driver-level features such as Smooth Motion, retest them after every rollback, since a feature’s behavior can shift between builds. Our Nvidia Smooth Motion setup guide shows what to check. Second, build a scheduled reminder, one that fires when you intend to revisit the question. A rollback should be a temporary measure with an end date, not a permanent decision. Watch NVIDIA’s release notes for a build that lists a fix, test it on one PC first, and then go forward again with the same script. Browse more PC walkthroughs in our hardware section for related maintenance guides.

FAQ: Rolling Back NVIDIA Drivers on Windows 11

Is it safe to roll back an NVIDIA driver?

Yes, when you use a signed driver from NVIDIA and make a restore point first. 617.42 is an official WHQL release, and the process only swaps display driver files. The real risks are a temporary black screen if the install fails and the loss of newer game optimizations, both of which the steps above cover.

Does NVIDIA officially recommend rolling back from 621.01 to 617.42?

Not in the release materials we reviewed. NVIDIA’s driver page for 621.01 does not list a video-freeze defect or recommend 617.42. Some outlets report that NVIDIA acknowledged the bug, and users say the rollback fixes it. Both are secondary reports, so treat the rollback as a workaround and watch NVIDIA’s pages for an official statement or a newer build.

How do I rollback NVIDIA driver 621.01 when the Roll Back Driver button is gray?

Download 617.42 from NVIDIA, run the installer, choose Custom (Advanced), and tick Perform a clean installation. The gray button only means Windows has no stored earlier package. The installer does not care, and it gives you the exact version you want.

Will a rollback delete my games, saves or settings?

No. Games and saves live outside the driver. A clean installation can reset driver-level settings such as Control Panel profiles, and shader caches rebuild on the first launch of each game. Note your custom profiles before you start if you want to restore them.

How long should I stay on 617.42?

Until NVIDIA ships a driver whose release notes address the freeze, and early user reports confirm it. Then test the new build on one machine before you update the rest. If you rely on Phantom Blade Zero or the Cyberpunk 2077 DLSS 4.5 update, weigh that need against the freeze risk, since 621.01 carries Game Ready support for both.

Will Windows Update or the NVIDIA App reinstall 621.01?

They can. Reports warn that both may offer the driver again. The registry policy in Step 10 blocks Windows Update from delivering drivers, and you can leave the NVIDIA App’s driver prompt alone or skip installing the app until a fixed release appears.

Do these steps work for AMD or Intel graphics?

The Device Manager method works for any display adapter that kept an earlier driver package. The download pages, version formats, installer switches and cleanup tools differ by vendor, so adapt the version checks before you reuse the scripts. AMD, for instance, documents its own cleanup utility for downgrades in its Adrenalin release notes.

Marcus Chen

Gaming & Consumer Tech Editor

Marcus Chen is a senior editor at Tech Insider, where he leads coverage of the US online gaming market, including sweepstakes and social casinos, alongside consumer technology. He evaluates operators on their published terms, licensing and RNG certifications, stated redemption policies, and corroborating independent reporting, and writes plainly about what the evidence supports. Tech Insider does not run first-party money tests and does not gamble with reader funds. Marcus has reported on the technology and online-gaming industries for more than a decade.

View all articles