Restart and retest first
Complete the update process with a full restart, then reproduce the issue in a scene you know well. Compare FPS, frame time and system load with your previous baseline if you have one. Avoid applying multiple tweaks before you know what changed.
Check for background activity
After a major update, Windows or applications may perform indexing, component cleanup, store updates or cloud synchronization. Open Task Manager during the slowdown and sort by CPU, disk and memory use. If a background task is active, give it time to finish and compare again later.
- Confirm no additional Windows update is pending.
- Check whether graphics and chipset drivers changed.
- Review power mode on laptops and desktops.
- Close nonessential launchers and overlays for a controlled test.
Verify the graphics driver
Windows Update can sometimes deliver a different driver version than the one previously installed. Check the installed version and compare game stability. If the timing strongly points to a driver change, test a known-stable version rather than changing unrelated settings.
Check power and display settings
Verify the monitor is still running at the intended refresh rate and that the system power mode did not change. On laptops, compare plugged-in behavior with the manufacturer's normal performance profile.
Re-check game settings and caches
Some games rebuild shaders after operating-system or driver changes. The first sessions can therefore stutter more than normal. If the issue improves as the same areas are revisited, shader compilation may be part of the explanation.
Avoid disabling Windows security as a performance fix
Security features should not be switched off simply because performance changed after an update. If a specific process consumes unusual resources, diagnose that process. Broadly disabling protections adds risk without proving the source of the slowdown.
When rollback is worth testing
If the slowdown is repeatable, started immediately after a specific update, persists after background maintenance completes and affects several workloads, reviewing the update history can help. Use rollback only as a controlled diagnostic option when supported, and keep system security and backup implications in mind.