Windows 12 does not have an announced release date, and Microsoft has not confirmed that a product by that name even exists. Based on Microsoft’s three-year cadence, its silicon partnership decisions, and the public build record, a plausible window is the second half of 2027, though nothing in the official record commits Microsoft to that date or that name.
The question is reasonable, because Microsoft spent 2024 and 2025 shipping AI features under the Windows 11 brand. That pattern tells you more about release timing than any leaked roadmap. The version number matters less than the servicing model underneath it.
The servicing model that decides release timing
Microsoft does not ship a new major version when features are ready, and it does not wait for a single big bang. Windows releases sit on a servicing foundation with a yearly rhythm. Feature updates for Windows 11 arrive in the fall, Microsoft’s Enablement Package model went mainstream with Windows 10 version 1909 in 2019, and the company has shipped annual client feature updates on that cadence since. Each fall release is a package that flips features already present in the code, which shortens installation to minutes and shrinks the support surface Microsoft must test.
A new major version is a different kind of event, because it resets the support end date. That reset is the reason the version number exists as a marketing and support artifact. Changing it is an economic decision, not a technical one. Windows 11 was announced in June 2021 and reached general availability in October, roughly four months from announcement to shelf. That is the shortest announcement-to-release gap in recent Windows history. Microsoft can therefore appear to be quiet and still ship within a year.
The historical cadence, quantified
Windows release intervals are the best available baseline, and the numbers are consistent enough to be useful.
Major Windows client releases and their gaps
| Release | General availability | Gap from prior major release |
|---|---|---|
| Windows 7 | October 2009 | 2 years, 9 months (from Vista, Jan 2007) |
| Windows 8 | October 2012 | 3 years |
| Windows 10 | July 2015 | 2 years, 9 months |
| Windows 11 | October 2021 | 6 years, 3 months (skipped a numbered release) |
| Windows 11 24H2 | October 2024 | 3 years (latest annual feature update shown for reference) |
The median gap across those releases is roughly three years, and every full-number release since 2009 landed in the July-to-October band. Two facts follow. First, Microsoft prefers fall launches. Second, the company did not skip Windows 9 to reach a three-year interval; it skipped to align numbering with its internal kernel version family.
That history supplies the 2027 estimate, but it is weak evidence on its own. A cadence is a description, not a commitment. Microsoft has broken it before and will again.
Why the Windows 11 support clock matters
A release date usually becomes visible through the support calendar, not the press cycle. Windows 11 Home and Pro editions on version 23H2 exit servicing on November 11, 2025. Versions 24H2 and 25H2 follow on their own schedules, and Microsoft’s modern lifecycle policy gives 24 months of updates to Home and Pro editions of each annual feature update. Enterprise and Education editions receive 36 months.
The practical implication is that Microsoft can keep Windows 11 alive for years without a successor. A named Windows 12 is therefore a choice about platform identity, not a requirement for security updates. It becomes likelier when three conditions coincide: a hardware capability Microsoft can gate on, a support date that makes a reset attractive, and an AI or security feature that cannot ship as a toggle.
What Microsoft has actually said
Microsoft’s public statements contain no Windows 12 announcement. The company has instead described Windows 11 as the home for its Copilot work. Copilot became generally available inside Windows 11 in late 2023, and later builds moved AI features into the taskbar and Settings. Windows 11 24H2 in 2024 and 25H2 in 2025 both arrived as annual updates rather than new product names.
The one genuinely hard gate Microsoft has disclosed is hardware. Windows 11 requires TPM 2.0 and a supported CPU list, and Microsoft has stated that it will not relax those requirements. Any successor is likely to raise a floor rather than lower it, most plausibly a stronger local AI accelerator requirement. Microsoft has not published such a requirement. Treat any specific NPU or memory threshold circulating online as unconfirmed.
Silicon partnerships and the NPU floor
The mechanism worth understanding is how Microsoft uses OEM silicon cycles as release triggers. Qualcomm’s Snapdragon X Elite laptop platform shipped in mid-2024 and became the first hardware to meet the Copilot+ PC baseline. That baseline was defined as 40 or more trillion operations per second (TOPS) on a dedicated neural processing unit. It shipped on Windows 11.
That is the counterintuitive detail: the Copilot+ PC baseline, 40 TOPS, did not wait for a new Windows version. Microsoft bolted it onto Windows 11 through servicing. A feature this large arriving without a version bump tells you that the company does not see a new version number as a prerequisite for platform-level hardware features.
If a Windows 12 arrives, it will likely be tied to a silicon generation that offers a capability the older OS cannot expose cleanly, such as a shared memory architecture or a mandatory NPU tier. The release would then be timed to OEM launch cycles rather than to a marketing calendar.
Builds, leaks, and what they prove
Public Windows builds carry a kernel version family, and that family has advanced while the marketing name stayed at 11. Insiders on the Dev and Canary channels have received builds labeled with the 26xxx series, and build numbers in the 27xxx range are the current upper edge of leaked mentions. That progression is normal servicing work. It does not prove a Windows 12 build exists.
The professional caveat: build numbers, OEM driver listings, and references in Microsoft’s own error messages have preceded every recent Windows release. They have also appeared for releases that were canceled. Windows 10X is the clearest case. It generated extensive internal builds and shipping hardware plans, then was folded into Windows 11. A leak is a signal about engineering activity, not a product decision.
Red flags to watch for in coverage: A single anonymous source with a build number and no date corroboration. A “release date” tied to an OEM marketing event, which changes with inventory. Claims that Microsoft will drop TPM 2.0 or the CPU list, which Microsoft has contradicted. Screenshots of Settings pages with a version string, which are trivial to fabricate. Confirmation of a name without a servicing plan, since the name is the cheapest thing to change.
The misconception: a new number is not a new engine
The most common error is treating a version bump as a rewrite. Windows 11 is architecturally a continuation of Windows 10, which is why upgrade paths and driver models survived. The same continuity is likely for any successor. A new version resets support dates, changes hardware floors, and gives marketing a story. It does not replace the kernel.
A second misconception is that AI features arrive with the new version. Copilot shipped on Windows 11, and Copilot+ features rolled out as updates. The version number is a packaging decision made after the engineering is done.
Practical steps, with dates and thresholds
You do not need to guess to be ready. Use the support calendar and the hardware floor as your signals. These steps work whether or not Windows 12 ever ships.
Track your edition’s end-of-servicing date. Windows 11 23H2 Home and Pro end on November 11, 2025, and 24H2 runs 24 months from its release for those editions. Move to the current feature update before that date rather than after. Confirm TPM 2.0 and Secure Boot are enabled now. Run the PC Health Check app; it reports TPM status and CPU compatibility in plain language. Budget for a 40 TOPS NPU only if you want local AI workloads. The ceiling is a Copilot+ baseline, not a Windows 12 requirement, because no such requirement exists. Watch two official sources only: the Windows release health page and the Windows IT Pro Blog. Both publish servicing dates before any consumer press does. If your machine is five or more years old, plan hardware replacement around the 24H2 servicing end rather than around a product name. Ignore “release date” lists from aggregators. None of them carry a Microsoft commitment, and the honest answer is that no date exists.
What can and cannot be concluded
The conclusion is narrower than most coverage suggests. Microsoft has confirmed no Windows 12. The historical cadence supports late 2027 as a plausible window. The servicing model supports indefinite continuation of Windows 11 under new annual updates. The hardware record shows Microsoft will gate on silicon only when servicing cannot deliver the capability.
Two limitations deserve emphasis. First, cadence evidence is retrospective and has been broken before, so a 2027 estimate carries low confidence. Second, the version name itself is a marketing variable. A release that behaves like Windows 12 could ship as Windows 11 27H2 without breaking anything. The name matters for support clocks and hardware floors; it matters little for the code underneath.
This article is general educational information about software release timing, not a purchasing, investment, or support recommendation. It does not promise any release date or outcome and is not a substitute for guidance from a qualified IT professional who can assess your specific systems.