{“lastseen”:”2026-06-23T15:36:51″,”description”:”* * *\\n\\n#### Key Takeaways\\n\\n * Windows 11 24H2 reaches the end of servicing on October 13, 2026, making timely enterprise upgrades critical.\\n * Enterprises often face version drift, with multiple Windows 11 builds across endpoints requiring different upgrade paths.\\n * Upgrade approaches vary based on system state and may include enablement packages, ISO-based feature updates, or direct Windows 10 upgrades.\\n * For supported Windows 11 systems, enablement packages provide the fastest, lowest-impact upgrade method.\\n * Centralized orchestration with TruRisk Eliminate helps standardize upgrades and reduce version drift at scale.\\n\\n\\n\\n* * *\\n\\nIn enterprise Windows environments, endpoints often run multiple build versions due to variations in update cadence, system readiness, and upgrade methodologies. As a result, different upgrade approaches may be required, including enablement packages, feature updates, or direct OS transitions. This makes maintaining version consistency a persistent operational challenge.\\n\\nThis challenge becomes more critical as systems approach the end of their service life. According to Microsoft\u2019s official lifecycle policy, **Windows 11 version 24H2 (Home and Pro) will reach the end of servicing on October 13, 2026**. This makes it essential to plan upgrades well in advance, particularly in environments where endpoints are distributed across multiple OS baselines.\\n\\nTo address this challenge, Qualys TruRisk Eliminate provides comprehensive coverage across all upgrade scenarios, enabling consistent and controlled execution across your entire environment.\\n\\n## Before You Start: Assess Endpoint Readiness\\n\\nBefore initiating any upgrade activity, endpoints should be grouped by eligibility and current OS state:\\n\\n * Enablement-ready systems running recent Windows 11 builds\\n * Systems requiring feature updates on older Windows 11 versions\\n * Windows 10 systems requiring a direct upgrade\\n\\n\\n\\n## Upgrade Path 1: Enablement Package Preferred Approach (Recommended)\\n\\nEnablement packages are lightweight updates that activate functionality already present within the operating system. Rather than performing a full OS upgrade, they unlock new capabilities within the existing build. \\n \\n**Advantages of Enablement Packages**\\n\\n * Minimal download size \\n * Faster installation relative to full feature updates \\n * Reduced reboot requirements \\n * Lower operational impact and failure rate \\n\\n\\n\\nFor endpoints already running recent Windows 11 builds, feature updates can be deployed using enablement packages. This makes them the most efficient and low-impact upgrade path available.\\n\\n### Deploying Windows 11 Upgrades with TruRisk Eliminate\\n\\nWith Qualys TruRisk Eliminate, IT teams can create patch jobs directly from the patch catalog and deploy enablement packages at scale. This enables rapid, enterprise-wide rollout across endpoints without relying on fragmented tooling or manual intervention. \\n\\nExample: Use QQL to identify enablement packages:\\n \\n \\n patch.title:\\”Enablement\\” \\n\\nSelect the required patch from the results and create a patch job targeting the relevant asset groups.\\n\\n\\n\\n## Upgrade Path 2: Feature Update via ISO (Fallback)\\n\\nEnablement packages are the preferred method for Windows feature updates and are typically released by Microsoft for supported baselines.\\n\\nHowever, in rare cases where Microsoft does not release an enablement package for a given transition, a feature update using an ISO becomes necessary. Based on recent release patterns, this scenario is uncommon and has been observed only in limited cases, such as the transition from Windows 11 23H2 to 24H2.\\n\\n### Deploying ISO-Based Feature Updates with TruRisk Eliminate\\n\\nUse QQL to identify Microsoft feature update patches:\\n \\n \\n patch.isFeatureUpdate:true AND patch.vendor:`Microsoft`\\n\\nFrom the results, select the required ISO-based package, enable it in the catalog, and create a patch job targeting the relevant asset groups.\\n\\n\\n\\n## Upgrade Path 3: Direct Upgrade from Windows 10\\n\\nFor environments still running Windows 10, multi-step upgrades are not required. Systems can be directly upgraded to Windows 11 25H2 without intermediate transitions.\\n\\nIf endpoints need to move from Windows 10 to the latest supported build, Qualys** TruRisk Eliminate** provides the required coverage to execute this transition in a controlled manner.\\n\\n### Upgrading Windows 10 Systems with TruRisk Eliminate\\n\\nWith Qualys**TruRisk Eliminate**, ready-to-use scripts are available in the Custom Assessment and Remediation (CAR) library to directly upgrade systems from Windows 10 to the latest Windows 11 build.\\n\\nExample: Navigate to **Script Library \u2192 System Updates and Upgrades \u2192 Windows OS Upgrades**. Select the **Windows 10 to Windows 11 upgrade script** , import it in approved mode, and execute it on the required asset groups.\\n\\n\\n\\n## Operationalizing Windows Upgrade Strategy\\n\\nManaging Windows upgrades requires aligning the appropriate method with each system\u2019s state. Using enablement packages, ISO-based upgrades where needed, and direct Windows 10 transitions ensures consistent and controlled execution across the environment.\\n\\n_Planning your upgrade strategy early can keep your systems supported and aligned. By starting ahead, you ensure seamless integration across your environment. Ready to leap? _\\n\\n* * *\\n\\n**Start your free trial today to see how TruRisk Eliminate can streamline your Windows upgrades!**\\n\\nStart Your Free 30-Day Trial\\n\\n* * *\\n\\n## Frequently Asked Questions\\n\\n**When is Windows 11 24H2 end of support?** \\nOctober 13, 2026 for Home and Pro editions. Enterprises should begin planning upgrades well in advance.\\n\\n**What is Windows 11 version drift?** \\nIt occurs when endpoints run multiple different builds of Windows 11, requiring varied upgrade approaches (enablement packages, feature updates, or full OS transitions).\\n\\n**What is the recommended upgrade path for recent Windows 11 builds?** \\nEnablement packages are the preferred, low-impact method. They unlock new features with minimal download size, faster installation, and fewer reboots.\\n\\n**How can Qualys TruRisk Eliminate help with Windows 11 upgrades?** \\nIt allows you to target systems with QQL, deploy enablement packages or ISO updates via patch jobs, and run direct Windows 10 to Windows 11 upgrade scripts from the CAR library.\\n\\n**Should I upgrade Windows 10 systems directly to 24H2?** \\nYes. Direct upgrades are supported and recommended to avoid unnecessary intermediate steps.”,”published”:”2026-06-23T15:00:00″,”modified”:”2026-06-23T15:00:00″,”type”:”qualysblog”,”title”:”3 Paths to Upgrade Windows 11 before 24H2 End of Servicing (EOL)”,”source”:””,”references”:””,”id”:”QUALYSBLOG:FDC705F50F73787D6AF114F35B4AE2FD”,”bulletinFamily”:”blog”,”cwe”:null,”cvelist”:[],”sourceData”:””,”sourceHref”:””,”cvss”:{“score”:0,”severity”:”NONE”,”vector”:”NONE”,”version”:”NONE”},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:”https:\/\/blog.qualys.com\/category\/product-tech”,”category_name”:”News”,”post_link”:””,”product”:””,”version”:””,”vendor”:””,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:”2026-06-23T15:36:51″,”description”:”* * *\\n\\n#### Key Takeaways\\n\\n * Windows 11 24H2 reaches the end of servicing on October 13, 2026, making timely enterprise upgrades critical.\\n * Enterprises…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[6,8,12,13,33,120,7,11,5],"class_list":["post-65074","post","type-post","status-publish","format-standard","hentry","category-category_news","tag-cve","tag-cvss","tag-exploit","tag-news","tag-none","tag-qualysblog","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n