Microsoft has quietly moved from a selective rollout to an explicit “seeker” push: if your PC meets Windows 11’s eligibility rules, you can now choose to download and install
Windows 11, version 25H2 directly from Settings > Windows Update — and Microsoft is encouraging both Windows 10 and Windows 11 users to take that step.
Background / Overview
Microsoft has been navigating a difficult migration: millions of Windows 10 PCs remained un-upgraded as the platform approached its end-of-support timetable, and Microsoft’s response has oscillated between nudges, staged rollouts and more conservative deployment windows. The company now lists
Windows 11, version 25H2 (the 2025 Update) as available to eligible devices via the Windows Update “seeker” experience — a manual “Check for updates” path that surfaces the option to “Download and install Windows 11, version 25H2.” This move comes as independent industry figures and OEMs report an unexpectedly large pool of Windows 10 machines that are eligible for an upgrade but are
choosing not to move. Estimates cited in recent coverage put this cohort in the hundreds of millions; Dell, for example, referenced roughly 500 million upgrade-capable PCs that have not upgraded, a stat widely reported across the trade press. That slow uptake — combined with Windows 10’s formal end of servicing — is the context for Microsoft’s new distribution posture.
What Microsoft announced — the essentials
- The 25H2 update (Windows 11 2025 Update) is being offered to eligible Windows 10 and Windows 11 devices via the Windows Update seeker: Settings > Windows Update > Check for updates. If the device is ready, the option will appear as “Download and install Windows 11, version 25H2.”
- 25H2 is delivered as the annual feature update and, in Microsoft’s rollout model, can be staged and controlled by Microsoft with phased delivery and compatibility holds where needed. The update is positioned as a quality-and-compatibility release rather than a feature-packed “wow” milestone — Microsoft has said 25H2 adds little in the way of brand-new user features and emphasizes parity and stabilization over headline changes.
- Microsoft explicitly lists known issues and the current remediation status on its Release Health pages; it is advising that IT teams and home users follow its guidance when deciding whether to opt in immediately or wait for broader availability.
Why this matters: the migration dynamics
Windows 10 reached its official end-of-support date in October 2025. After that date Microsoft stopped issuing free security updates and routine technical support for mainstream Windows 10 editions — a hard lifecycle milestone that should, in theory, accelerate upgrades. In practice, the migration path is complicated by hardware requirements, user inertia, application compatibility testing cycles in enterprise deployments, and, for many consumers, a simple preference to “if it ain’t broke, don’t fix it.” Two practical forces push and pull users right now:
- Push: Security and support. Running Windows 10 beyond its vendor-supported lifecycle increases risk exposure; Microsoft’s messaging and the availability of 25H2 aim to lower the barrier for eligible devices to move into a supported configuration.
- Pull: Stability and compatibility. Many organizations delay feature upgrades until they validate drivers, in-house applications and hardware. In the consumer space, reports of update failures and regressions make cautious users wait for the “green” signals.
The big headline number: 500 million holdouts — what that means
Multiple reports and public earnings commentary from vendors have converged on a striking headline: around half a billion PCs that
could upgrade to Windows 11 remain on earlier releases. That figure is an aggregation and estimate — not a device-by-device census — but it explains Microsoft’s logic for lowering friction to adopt 25H2 via Windows Update. The number signals the scale of the migration problem and why Microsoft is actively nudging eligible users to opt in. Caveat: those headline figures mix eligible-but-un-upgraded devices with the much larger pool of older, ineligible machines; treat any global tally as an estimate rather than an exact census. Nonetheless, the takeaway is simple: a sizable population of PCs that can run Windows 11 has not yet moved, and Microsoft’s policy decisions reflect that reality.
Known issues, active problems and the “be careful” signals
This rollout is not risk-free. Several practical problems have been reported in community testing and in Microsoft’s own release-health notices:
- Windows Update install failures and rollback errors showing codes such as 0x80070306 have been widely reported for recent cumulative updates and feature packages; threads and Microsoft Q&A show many users encountering this failure during November–December update cycles. These failures can cause an update to fail and repeatedly attempt installation.
- A December preview cumulative (packaged as KB5070311 / SSU pairing) intended to extend dark mode coverage in File Explorer introduced a regression: when launching File Explorer in dark theme some users see a brief but intense white flash (a “flashbang” effect) before the UI finishes painting. Microsoft acknowledges this known issue and lists it in its advisory pages; the bug has been reproduced in community tests and covered in major outlets. For users who rely on dark mode (or who are visually sensitive), this is not cosmetic — it can be jarring.
- GPU/driver interactions: community reports and vendor forums have called out instability with certain GPU driver versions — Intel Arc cards and some OEM driver bundles were singled out in user reports tied to recent updates. The pattern is typical of feature update cycles: new OS builds plus vendor driver changes can create unexpected interactions on some hardware combos. Intel’s community pages and testing threads show troubleshooting and driver rollbacks as practical mitigations. Microsoft’s release-health pages and staged compatibility holds remain the authoritative place to track any widespread driver-related blocks.
Microsoft’s official posture is measured: list the known issues, deploy compatibility holds where telemetry indicates a larger problem, and roll fixes via Windows Update or Known Issue Rollback (KIR) mechanisms. For affected devices Microsoft says it is working on resolutions, but precise timelines are not always available.
Technical verification — what you should check before upgrading
- Verify your device meets Windows 11 minimum system requirements: a compatible 64-bit processor (on Microsoft’s approved CPU list), 4 GB RAM, 64 GB storage, UEFI with Secure Boot capability, and TPM 2.0. Use the PC Health Check tool or Settings to confirm eligibility before you attempt an in-place upgrade. These are non-negotiable for Microsoft’s supported upgrade path.
- Back up: create a full image or at minimum back up user data and configuration (OneDrive, external backup). Major upgrades are usually reliable but the practical step remains: if anything goes wrong, you want a tested recovery path.
- Review drivers and OEM guidance: ensure your graphics, storage and chipset drivers are up to date from vendor sites (Dell, HP, Lenovo, Intel, AMD, NVIDIA) and confirm that the OEM has validated Windows 11 25H2 for your SKU if you’re running production or critical hardware. Where OEM drivers are missing or untested, hold the upgrade until validation is complete.
- Enterprise change control: place 25H2 in a pilot ring, use Windows Update for Business or WSUS to stage deployment, and validate business-critical applications (line-of-business software, security agents, thin-client clients and imaging workflows). Use feature-update deferrals and phased deployments to limit exposure.
- Check Windows Update: after you’ve validated readiness, open Settings > Windows Update and select Check for updates. If eligible and staged to your device, you’ll see the Download and install Windows 11, version 25H2 option. This is Microsoft’s designated seeker path for users who want to opt in.
Troubleshooting common problems (practical steps)
Below are consolidated, actionable steps for the
most common issues reported during 25H2 and recent cumulative updates. These are practical triage steps — follow them only if you’re comfortable with system administration tasks.
- If Windows Update fails with error 0x80070306:
- Run Windows Update Troubleshooter (Settings > Troubleshoot).
- Stop update services, rename SoftwareDistribution and catroot2 folders, restart services (classic Windows Update reset).
- Run DISM /RestoreHealth and SFC /scannow to repair image and system files.
- Try the manual install: download the specific KB or .msu from the Microsoft Update Catalog and install offline. If offline install succeeds, monitor Update History and reboot as required.
- If Explorer flashes white in dark mode after a preview update:
- Uninstall the optional preview update (if installed) via Settings > Update history > Uninstall updates. If you rely on dark mode for accessibility, don’t install preview packages; wait for Microsoft to ship the fix in a cumulative. Microsoft has acknowledged this regression and is working on a resolution.
- If GPU/driver issues appear (e.g., Intel Arc instability or black/blue screens):
- Roll back to a previous driver version via Device Manager, or perform a clean driver uninstall with DDU (Display Driver Uninstaller) and then re-install a vendor-recommended driver.
- Check Intel, AMD, or NVIDIA support pages and OEM advisories for formally supported driver versions for 25H2.
- If the issue is widespread, expect Microsoft or the OEM to apply a compatibility hold while vendor fixes propagate.
- If you need to pause or delay the update:
- Use Pause updates in Windows Update, or configure Windows Update for Business policies and rings for managed deployments. Never pause updates indefinitely in a production environment without an alternative plan for critical security fixes.
For IT teams: recommended deployment plan
- Inventory and prioritize: identify devices capable of 25H2 and catalogue high‑risk or special‑purpose systems (medical devices, point-of-sale terminals, regulated systems).
- Pilot ring (1–5%): test in a tightly controlled group covering major hardware permutations (Intel/AMD, discrete GPUs, storage controllers, laptops vs desktops).
- Broad pilot (10–25%): expand to representative business units and verify application compatibility and driver behavior.
- Phased rollout: enable Windows Update for Business rings, stage feature updates, and monitor telemetry. Use rollback and restore procedures to reduce blast radius.
- Communication and training: prepare support desk scripts for known issues (0x80070306, File Explorer white flash), and provide end-user guidance on backups and how to report problems.
This staged approach prevents mass outages and gives time for vendor patches and Microsoft fixes to land.
Risks, trade-offs and what Microsoft is betting on
- Strengths: making 25H2 available via Windows Update lowers friction for the many devices already eligible; it makes the upgrade self-service and simplifies the path for home users and small businesses that lack central IT. Microsoft’s use of staged rollouts and compatibility holds is a pragmatic way to reduce widescale breakage.
- Risks: shipping a widely-available seeker while some compatibility problems exist exposes users to update failures and driver regressions. The File Explorer dark-mode regression and reported GPU issues are examples of why conservative pilots are still the right approach for any organization. Community reports and Microsoft’s own advisory pages show the empirical evidence of this trade-off.
- The security clock: Windows 10’s end-of-support means the long-term risk of not upgrading is real. Extended Security Updates exist as a bridge for organizations that cannot upgrade immediately, but ESU is a short-term mitigation with operational and cost implications. Microsoft’s push is therefore both security-driven and practical: reduce the unsupported install base.
Final recommendations — practical, prioritized guidance
- Home users with non-critical systems: Consider waiting a few weeks unless you need a specific 25H2 fix. If you're an enthusiast or you want the new build now, confirm a backup exists and upgrade via the Windows Update seeker path. If you rely on dark mode or have an Intel Arc GPU, consider holding off until the immediate preview regressions and driver issues are resolved.
- Power users and enthusiasts: If you install preview cumulative updates, do so on non-critical devices. Know how to uninstall preview packages and keep driver installers handy for rollbacks.
- IT admins: Use pilot rings, validate images and drivers, engage OEM support early, and treat 25H2 as a feature update that must go through organizational testing before broad deployment. Monitor Microsoft’s Release Health and KIR advisories and be ready to apply compatibility holds as telemetry dictates.
- Everyone: verify your device eligibility (PC Health Check), back up your data, and keep firmware/drivers updated from OEMs. If your device is ineligible, look at supported alternatives or ESU paths if you cannot afford an immediate hardware refresh.
Conclusion
Microsoft’s choice to make
Windows 11, version 25H2 broadly
available to eligible Windows 10 and Windows 11 devices via the Windows Update seeker is a pragmatic attempt to close a migration gap measured in hundreds of millions of devices. It reduces friction for users who are ready to move while preserving staged controls for Microsoft to manage risk. The reality today is mixed: a supported and straightforward upgrade path exists, but practical problems — update failures, a dark-mode regression, and GPU/driver friction on some hardware — mean that the prudent path differs by user and organization.
For casual users who value convenience and want to stay supported, the seeker path is the easiest route; for enterprises, power users and anyone running critical workloads, the safer option remains a measured pilot and staged rollout. In short: the new Microsoft push makes upgrading easier — but it does not eliminate the need for testing, backups and cautious deployment planning.
Source: Forbes
Microsoft Confirms New Upgrade Decision For All Windows Users