Windows 11 Pro 25H2
Serviced for next:
328 Days
Active
Product ID
windows-11-pro-25h2
Build Number
26200
Servicing Channel
Annual Channel
Policy Model
win11-annual-client-24m
Release Date
2025-09-30
Mainstream Support End
2027-10-12
Extended Support End
N/A (Modern Policy)
Final End of Support (EOS)
2027-10-12
Current Phase
Modern: Active Servicing
ESU Eligibility
Ineligible
Risk Level
Low
Priority
Monitor
Lifecycle Timeline & Servicing Horizon
Evaluation Date: 2026-11-18 (55.8% Elapsed)
Release: 2025-09-30
Mainstream Support: 2027-10-12
1. Lifecycle Servicing Status
Supported in mid-cycle servicing through 2027-10-12.
2. Security Servicing & Patch Eligibility
Receives full monthly Cumulative Updates (Quality Updates) and security bulletins.
3. Audit & Baseline Compliance Assessment
Fully compliant with enterprise infrastructure support standards.
Recommended Engineering Action
Maintain regular monthly patching cadence. Monitor upcoming feature updates for future validation.
Supporting Official Evidence
- Official Release Date: 2025-09-30
- Official End of Support (EOS): 2027-10-12
- Governing Policy: Windows 11 Annual Release Modern Policy (Client Pro/Home) (1.0.0)
- Microsoft Source: https://learn.microsoft.com/en-us/lifecycle/products/windows-11-home-and-pro
2.0 Vulnerability & Threat Intelligence (Sidecar Telemetry)
Decoupled sidecar threat telemetry — does not alter official Microsoft lifecycle compliance status.
Mapping Confidence: High
CISA KEV In-The-Wild
0
No active ransomware campaigns
Max CVSS Severity
--
/ 10
Severity: N/A
Max EPSS Probability
--
FIRST EPSS 30-day exploit forecast
Correlated CVEs
0
Indexed from MSRC & NVD telemetry
Sources: Microsoft MSRC · NIST NVD 2.0 · CISA KEV · FIRST EPSS
Official Microsoft Lifecycle Documentation
Verify on Microsoft Learn ↗
https://learn.microsoft.com/en-us/lifecycle/products/windows-11-home-and-pro
Is this version currently receiving monthly security patches?
▼
Receives full monthly Cumulative Updates (Quality Updates) and security bulletins.
What happens when our enterprise devices operate past official EOL?
▼
Operating past EOL means Microsoft ceases all engineering fixes and vulnerability patches. Exploit kits quickly weaponize unpatched kernel vulnerabilities, severely elevating ransomware risk.
Can running an EOL version cause our ISO 27001 or SOC 2 audit to fail?
▼
Fully compliant with enterprise infrastructure support standards. Under ISO/IEC 27001 (A.8.8 / A.12.6), SOC 2, and PCI-DSS, unsupported operating systems without active ESU or documented network micro-segmentation compensating controls are routinely flagged as high-risk audit non-conformities.