Roll back a display driver
Rolling back a display driver returns Windows to an earlier installed package when a recent change introduced a problem. It is most useful when the timing is clear and the previous package supported the same GPU and computer. Rollback cannot fix a cable, monitor input, application bug, failing hardware, or an unrelated dock driver, so confirm that the display stack changed before reaching for it.
Record the current and previous versions, the exact symptom, connected displays, Windows release, and laptop model. Keep work saved and make sure recovery access exists. Use Device Manager's supported rollback option when available or follow the computer maker's recovery guidance. Do not download an old package from an unknown site or disable security safeguards to recreate a previous state.
In this guide
Key Takeaways
- 1
A rollback is evidence-driven and usually less disruptive than deep cleanup.
- 2
Check that the issue began after the driver change and affects the display path.
- 3
Use Device Manager or OEM recovery guidance for the exact computer.
- 4
Validate the earlier package and preserve its version for future support.
Confirm that the driver caused a regression
Compare the timing of the update with the first failure. Look for a new warning in Device Manager, changed display behavior, lost brightness or switching controls, artifacts, or an application that worked with the previous package. Also test a simple desktop task and check monitor power, input, cable, and dock state. A coincidental network or hardware change should not trigger a driver rollback.
Record the package provider and version shown in Device Manager, plus the application or display affected. If only one application fails, inspect its renderer and profile before changing the whole adapter. If every display is affected immediately after an update, rollback evidence is stronger, but keep a recovery plan in case the prior package is no longer usable.
- Write down the before and after behavior and the package versions.
- Check physical display connections and application-specific settings.
- Choose rollback only when the driver change matches the observed regression.
Use the supported rollback path
Device Manager may offer a driver rollback action for the display adapter. Read the reason prompt, select the option that describes the regression, and let Windows complete the transition. If that control is unavailable, the computer maker may provide a supported recovery package or restore procedure. Use the model-specific path rather than copying an old installer from a third party.
Do not remove integrated and discrete adapters together, change BIOS settings, or install firmware as a substitute for rollback. Keep monitors connected as directed and avoid interrupting a restart. If rollback cannot proceed because the screen is unavailable, use the supported Windows recovery environment or alternate display route prepared in advance.
- Open the affected adapter's supported driver properties and review rollback availability.
- Follow the OEM recovery route when Windows does not retain a usable previous package.
- Keep security protections enabled and record the resulting version.
Validate the earlier version
After rollback, check the adapter status and confirm the expected earlier version. Test native display behavior, resolution, scaling, brightness, sleep and wake, internal and external outputs, and the application that exposed the regression. If the earlier package restores the display but loses a needed feature, note that tradeoff rather than applying random settings.
Tell the computer or GPU maker what changed, including both package versions and the affected workflow. Keep automatic update decisions in mind if Windows later offers the newer package again, and read official release notes before accepting it. If rollback does not help, restore the current supported package or investigate another layer instead of repeating it.
- Verify the earlier adapter version and required display controls.
- Reproduce the original task and compare its behavior with the pre-update state.
- Preserve the evidence and seek official guidance if the regression remains.
Common Questions
Why is the Roll Back Driver button unavailable?
Windows may not retain a previous package, the adapter may use a different installation path, or policy may limit the action. Check the computer maker's supported recovery guidance instead of sourcing an unknown old installer.
Should I roll back whenever a game has a problem?
No. First compare other applications, display connections, game settings, and the actual driver change. Roll back when evidence ties a broad display regression to the new package and the earlier package is supported.