Does Windows 11 26H2 work with a GTX 10-series graphics card?

What you need

• A card that is compatible with DirectX 12 or later and has a WDDM 2.0 driver. Every GTX 10-series card clears this, so the GPU is not what decides whether your PC is eligible.
• The PC must already be running Windows 11 version 24H2 or 25H2. 26H2 arrives as an enablement package, not a clean install, and there is no direct path to it from Windows 10 or from 23H2.
• KB5124010 (released 22 September 2026) or a later cumulative update must be installed first — it is the stated prerequisite for the enablement package.
• The rest of the Windows 11 baseline still applies: UEFI with Secure Boot, TPM 2.0, a compatible 64-bit dual-core processor, 4 GB of memory and 64 GB of storage. On a PC old enough to have a GTX 10-series card, the processor is the requirement most likely to block the upgrade — not the graphics card.

Supported on

• Windows 11, version 26H2 (OS build 26300), generally available since 29 September 2026
• NVIDIA GeForce 582.78 and later Release 580 security drivers, which support Windows 11 and Windows 10 64-bit
• All Pascal desktop cards NVIDIA lists: GT 1010, GT 1030, GTX 1050, GTX 1050 Ti, GTX 1060, GTX 1070, GTX 1070 Ti, GTX 1080, GTX 1080 Ti, TITAN X and TITAN Xp

Limitations

• No Game Ready drivers. The current Game Ready branch is 617.42, and its supported-product tables contain no GTX 10-series card. New game launches will not come with driver-side optimisation or day-one fixes for your GPU.
• Security fixes only, and only until October 2028. NVIDIA's plan gives Maxwell, Pascal and Volta cards critical-security driver updates from October 2025 through October 2028, roughly quarterly — 582.78 of 30 September 2026 is one of those.
• A GPU bug you hit will not be fixed. Bug fixes are explicitly part of what NVIDIA now reserves for Turing and newer. If a game renders incorrectly on your card, the honest expectation is that it stays that way.
• Your OS and your GPU run out of updates at nearly the same time. 26H2 Home and Pro stop getting updates on 10 October 2028, and NVIDIA's security drivers for Pascal stop in October 2028. Choosing 26H2 does not extend the life of the machine past that point.
• Two rendering bugs are already on the list and will stay there. NVIDIA's 582.78 notes list exactly two open issues: distorted Counter-Strike 2 text when the in-game resolution is below native [5278913], and light flickering in Like a Dragon: Infinite Wealth on some configurations [5432356]. Neither will get a fix on this branch.
• Features that are gated on newer driver branches are out of reach, since your card cannot install a branch newer than Release 580.

How to set it up

1. Confirm which architecture your card actually is, because the model names mislead. Press Windows+R, run dxdiag, and read the Display tab. A GTX 10-series number (1050 through 1080 Ti, or a GT 1010/1030) is Pascal and is affected. A GTX 16-series number is not — the GTX 1630, 1650, 1660 and their Ti/SUPER variants are Turing, and 617.42 still supports them.

   dxdiag

2. Check which driver branch you are on. In the NVIDIA app or NVIDIA Control Panel, open System Information and read the driver version. A 58x.xx version is the Release 580 security branch, which is correct and current for a Pascal card. If you are on something older, 582.78 or later is the one to install.
3. Do not keep checking for a newer Game Ready driver. NVIDIA's download page will not offer your card anything above the Release 580 branch, and a tool reporting "you are up to date" on a 58x.xx driver is telling you the truth, not failing.
4. Before taking 26H2, install the latest cumulative update so the KB5124010 prerequisite is satisfied, then let Windows Update offer the enablement package. The switch completes with a single restart.
5. If 26H2 is not offered yet, that is usually the staged rollout rather than a block on your hardware. Microsoft expands it over months, and turning on "Get the latest updates as soon as they're available" opts you into the earlier phase.

Known problems

• Applications and games that use Windows' built-in AC-3 (Dolby Digital) decoder can crash on 26H2. Microsoft has this marked Confirmed with no fix shipped yet. It is an OS bug, unrelated to your GPU, and hits 24H2 and 25H2 the same way. · how to fix it
• Some USB Audio Class 1.0 devices fail with Code 10 or produce no sound. On 26H2 this is still open — the out-of-band fix that helped 24H2 and 25H2 does not resolve it here. · how to fix it
• Reports circulating that 26H2 replaces NVIDIA and AMD drivers with generic Microsoft ones and causes VIDEO_TDR_FAILURE crashes are not confirmed by anyone. No such issue appears on Microsoft's 26H2 known-issues page, and neither NVIDIA's 617.42 nor 582.78 release notes mention it. Treat it as unverified.

Alternatives

• Stay on Windows 11 25H2: Supported for Home and Pro until 12 October 2027, a year longer than 24H2. If you would rather not move while 26H2 is new, this is the low-risk place to sit — and it changes nothing about your driver situation either way.
• Move to a Turing or newer card: The cheapest cards that restore Game Ready driver support are the GTX 1650 and GTX 1660 family, which are Turing despite the GTX name. Anything RTX 20-series or above also qualifies.
• Do nothing about the GPU: If you play older or less demanding games, a Pascal card on a security-patched driver is a reasonable place to be until October 2028. The driver freeze costs you optimisation for new releases, not the games already working today.