The test rig and what it took to get Windows 7 running
Both operating systems ran on identical hardware:
- Radeon RX 6950 XT
- Ryzen 7 9800X3D
- 64 GB of DDR5-6000 CL30
- Seagate FireCuda 530 NVMe SSD
- ASUS ROG STRIX B850-F Gaming WiFi motherboard
Windows 7 was Ultimate 64-bit SP1 (build 7601). Windows 11 was 25H2 (build 26200.9278). Both were clean installs, with the SSD filled to roughly 50–60%.
Installing Windows 7 on this hardware took real work:
- Storage and USB drivers: Windows 7 has no native NVMe or USB 3.0 support. The drivers have to be slipstreamed into the installation ISO. Microsoft later shipped NVMe patches, but the installer still won't see an NVMe drive unless the right driver is injected.
- Chipset drivers: There are no official Windows 7 chipset drivers for AM5.
- GPU choice: The RX 6950 XT is an RDNA 2 card, and RDNA 2 still has Windows 7 driver support. That is why it was chosen.
- Firmware settings: The board still offers CSM and legacy boot. Boards that have dropped them can make Windows 7 hard to install or even prevent it booting. The testers disabled Secure Boot, enabled CSM and set Boot Device Control to Legacy OPROM Only. This cost them Resizable BAR on Windows 7.
- Windows 11 settings: The testers disabled VBS and HVCI.
Both systems used a package labelled AMD Adrenalin 22.6.1. The two packages contain different internal driver versions. The Windows 11 driver is based on a more advanced codebase, even though both were released in June 2022. That difference matters when reading the results.
DirectX 11 results: it depends on the bottleneck
The DirectX 11 games are the fairer comparison, because both systems run them natively. The article's text gives no frame-rate numbers, only qualitative findings from the charts, so I am not quoting figures.
| Game | Reported outcome |
|---|---|
| Metro 2033 Redux | Windows 11 had the higher average FPS. Windows 7 had much stronger 1% lows when CPU-bound dips occurred. |
| Batman: Arkham Origins | Windows 7 led at 1080p in average FPS and 1% lows, and kept a small lead at 4K. |
| Batman: Arkham Knight | Windows 7 led at CPU-limited 1080p. Windows 11 led at 1440p and 4K. |
| Batman: Arkham City | GPU-bound at every resolution, so Windows 11 led throughout. |
| The Witcher 3 | Windows 7 had better 1% lows at 1080p. Windows 11 took a slight lead at 1440p and 4K. |
| Control | Windows 11 won everywhere. The game was tested in DX11 on both systems, since its ray tracing needs DX12. |
| Hitman: Absolution | GPU-limited even at 1080p. The article gives no explicit winner. |
| Hitman 2 | GPU-limited throughout, with a Windows 11 sweep. |
The pattern is clear. Windows 7 wins where the CPU limits the frame rate, mainly at 1080p and in 1% lows. Windows 11 wins once the GPU is the limit. The authors attribute this to Windows 7's lower CPU overhead and fewer background processes, and to Windows 11's more advanced graphics driver codebase. This is their interpretation, not a proven cause.
DirectX 9 results: a lopsided fight
Windows 7 won both DX9 titles clearly:
- Batman: Arkham Asylum: Windows 7 had significant advantages, especially at 1080p and 1440p. The lead narrowed at 4K, but Windows 7 was still smoother overall.
- Borderlands 2: Windows 7 had a massive lead at lower resolutions. At 4K the two were virtually identical.
This comparison is tilted by design. Windows 7 runs DX9 natively, while Windows 11 uses the D3D9On12 mapping layer. The authors chose that out-of-the-box path deliberately. They suggest a different translation layer such as DXVK might narrow the gap, but they did not test it. These results measure the translation path as much as they measure the operating systems.
Is it the security features?
Not in this test. VBS and HVCI were off on Windows 11, so they can't explain the CPU-limited deficit. For context, Tom's Hardware's earlier Windows 11 testing found that the impact of VBS/HVCI varied by title, with some games barely affected and others hit harder. The authors point instead to telemetry and other background services. They also found that installing AMD chipset drivers and enabling Resizable BAR did not meaningfully close the CPU-limited gap. They did not isolate which services were responsible.
Caveats
- This is one platform, one GPU generation and ten mostly older games. Every title is a DX9 or DX11 game from 2019 or earlier.
- The two GPU drivers are not identical internally.
- Windows 7 had no official AM5 chipset drivers, so its configuration is not a typical supported one.
- I found no independent reproduction of these results.
- The article mentions Microsoft's "K2" plan to improve Windows 11 performance and reliability. It gives no details or evidence of results, so treat it as a future promise.
Don't take this as a reason to go back
Microsoft's own FAQ says support for Windows 7 ended on January 14, 2020. It also says that after the end of support, Microsoft no longer publishes security updates for the product. Updates after that date applied only to devices covered by Extended Security Updates. A Windows 7 gaming install is an isolated experiment or an offline retro-games machine, not a daily driver for browsing, email or banking. One third-party roundup also notes that Steam no longer supports Windows 7. That is a commentary site's claim, so check it before relying on it.
What this means for Windows 11 gamers
The most useful finding is that a fast CPU doesn't guarantee smooth frame pacing. On this rig, Windows 11 left some CPU-side performance on the table, which shows up in 1% lows more than in averages. If you run older DX9 games on Windows 11, you can try a different translation layer such as DXVK, which the testers suggest might help. If you are CPU-bound, trimming background services may help.
If Microsoft's K2 efforts reduce Windows 11's overhead, this kind of test would be a good way to measure it. For now, Windows 7 wins on lean CPU behavior, and Windows 11 wins on modern GPU drivers and the ability to run current games.