Microsoft is quietly adding a compatibility check to Windows Update so Windows 10 users can see — right in Settings > Windows Update — whether their machine meets the minimum requirements to upgrade to Windows 11, and the change has implications that go beyond a simple convenience notification.
Background
The system requirements for Windows 11 have been a recurring source of confusion since the OS was announced: TPM 2.0, Secure Boot, and a tight list of supported CPU families created a large pool of machines that were functionally capable but officially “ineligible.” Microsoft’s initial diagnostic, the PC Health Check tool, was pulled shortly after launch because its messaging was unhelpful; Microsoft revised and reissued the tool with clearer guidance, and it remains the canonical way to inspect device-level causes (for example, "Secure Boot disabled" or "TPM missing/disabled"). At the same time, Microsoft has used Windows Update as a distribution and messaging channel to encourage upgrades: phased rollouts, targeted banners, and service updates that can present users with upgrade offers are now part of the update landscape. Those server-side changes — and a quietly distributed Windows Update component change identified by observers — lay the groundwork for the new in-Settings compatibility check.
Overview: what changed in Windows Update
- What you’ll see: For Windows Insiders in the Release Preview channel (Windows 10 version 21H2 at the time of the rollout), Windows Update will now evaluate compatibility and display a short message if the device passes the check: “Great news — your PC meets the minimum system requirements for Windows 11. Specific timing for when it will be offered can vary as we get it ready for you.” The text also includes a caution that some Windows 10 features aren’t available in Windows 11 and links to additional guidance.
- Who got it first: Microsoft rolled this capability out to the Release Preview channel as part of a phased Insider testing approach. Observers expected the same behavior to show up broadly for eligible Windows 10 devices once the telemetry and rollout were validated.
- Why it matters: The change moves a compatibility check from a separate app (PC Health Check) into the same UI most users already visit for updates. That reduces friction for casual users and makes eligibility visible at a glance — which also converts a compatibility check into an upgrade prompt inside a trusted system control panel. Tech reporting called it helpful for users but noted it doubles as a high-visibility nudge in Microsoft’s broader upgrade campaign.
Technical context: Windows 11 requirements and the tools that check them
The requirements in brief
- TPM 2.0 (Trusted Platform Module) and UEFI Secure Boot are baseline security prerequisites.
- Supported CPUs are limited to relatively recent Intel, AMD, and Qualcomm families (Microsoft has periodically updated the supported CPU lists and made narrow additions after testing).
- Minimum RAM and storage thresholds (4 GB RAM / 64 GB storage) and modern graphics/DirectX support are part of the checklist.
Diagnostic tools and Microsoft guidance
- PC Health Check: the official Microsoft tool that reports compatibility status and, in recent builds, explains why a device fails (for example, informing users if Secure Boot is disabled or TPM is not present/enabled). Microsoft’s support documentation explains how to verify TPM and enable it in firmware, and walks through the PC Health Check experience.
- Windows Update check: the new in-Settings check supplements the Health Check experience by bringing a one-line compatibility result to the Windows Update UI. For users who prefer not to run separate apps, this provides a lightweight answer directly where upgrade decisions are taken.
How the new Windows Update compatibility check works (what to expect)
- Windows Update performs its normal check for available feature and quality updates.
- For devices in the targeted rollout cohorts (initially Release Preview Insiders on 21H2), an additional compatibility probe runs that evaluates CPU, TPM, Secure Boot, RAM, storage, and other platform markers.
- If the device passes, Windows Update shows the “Great news — your PC meets the minimum system requirements for Windows 11” message, and — depending on Microsoft’s staged rollout policy — may later present an option to “Download and install” Windows 11 when the offer is ready for that device. If the device fails, Windows Update is expected to show a message indicating the device is not eligible and link to support articles.
Notes on timing and staging:
- This is a phased rollout. Not everyone will see the messaging at the same time even if their hardware passes the same checks.
- Microsoft uses telemetry and compatibility hold logic to throttle or block feature updates for devices with known driver or hardware issues. The presence of a compatibility message does not override other rollout safeguards.
What this means for Windows 10 users (practical impact)
- Lower friction for checking eligibility: Casual users no longer need to find and install the PC Health Check app to get a first-pass answer. Windows Update brings the check to the familiar settings area.
- Higher visibility for Microsoft’s upgrade push: Because Settings → Windows Update is where users expect actionable prompts, embedding compatibility messaging there increases the chance a user will opt-in to an upgrade when the offer arrives. Many outlets note this acts as a visible nudge in Microsoft’s broader migration plan.
- Fewer support surprises — when it works properly: If the in-Settings check makes the failure reason available (or if it links to PC Health Check) then users have clearer, actionable next steps: enable Secure Boot, enable TPM in firmware, update BIOS, or accept that the CPU is unsupported. Microsoft updated PC Health Check precisely to provide these actionable details.
- But expect variability: Vendors and drivers still matter. Firmware updates from OEMs (BIOS/UEFI) can change eligibility; Microsoft notes it may take time for Windows Update to refresh eligibility after hardware changes — reports suggested waiting up to 24 hours in some cases for eligibility to propagate. That delay has been called out in support guidance and coverage. If you recently installed a TPM module or updated firmware, allow time and/or run PC Health Check for an immediate result.
Step-by-step: how to check if your Windows 10 PC is eligible (recommended sequence)
- Back up your data first — full image or at least critical files to OneDrive/external storage.
- Open Settings → Update & Security → Windows Update and click Check for updates. If Microsoft has enabled the compatibility probe for your device cohort you will see either the “Great news — your PC meets…” message or a message that your PC does not meet requirements.
- If you need granular detail about why a device fails, download and run the PC Health Check app (or open Settings → Update & Security → Windows Security → Device security → Security processor details) to see whether TPM 2.0 is present and enabled and whether Secure Boot is active. Microsoft’s support pages explain how to check and enable TPM from firmware/UEFI.
- Update firmware and drivers from your PC or motherboard vendor, then re-run the checks. Don’t assume a BIOS update will automatically flip eligibility in Windows Update — Microsoft’s backend may need time to refresh telemetry.
- If you decide to proceed and the Windows Update offer appears, follow the standard upgrade prompts; keep drivers updated and keep the machine connected to reliable power and network during the process.
Strengths of Microsoft’s approach
- Lower technical friction: Moving the basic compatibility check into Windows Update reduces the number of steps for mainstream users and provides a more discoverable upgrade pathway.
- Actionable guidance: The revised PC Health Check and the Windows Update message together can steer users toward concrete fixes (enable TPM/Secure Boot, install a firmware update) instead of leaving them with a vague “unsupported” label.
- Safer phased rollout: By keeping upgrade offers gated by telemetry, Microsoft can reduce the risk of broad regressions (drivers, OEM-specific issues) when enabling large feature upgrades. The compatibility message does not guarantee immediate availability — that safeguard remains.
Risks, limitations, and things to watch
- Messaging vs. intent: It’s difficult to verify Microsoft’s intent beyond immediate product management goals. Some coverage frames the change as an advertising or migration nudge — that’s a reasonable interpretation, but it is not a provable statement of corporate intent. Treat “advertising tool” language as analysis, not fact.
- False reassurance or false negatives: A short message saying “your PC meets the minimum system requirements” is helpful, but it’s not a guarantee of a flawless upgrade. Driver interactions, third-party security software, and obscure hardware incompatibilities still cause failed installs after the initial compatibility pass. Likewise, a device that fails the check may actually be remedied by a firmware update or enabling a toggled feature in UEFI — which requires user initiative and vendor support.
- Phased rollout confusion: Even if Windows Update reports eligibility, the timing of the actual offer varies. Devices can be eligible but held back by staged deployment logic for weeks or months. This staged model reduces mass-failure risk but creates user frustration and support questions.
- Policy and support consequences for unofficial installs: Microsoft’s public guidance remains firm: installing Windows 11 on hardware that does not meet minimum system requirements is unsupported. Unsupported installs may be left off future update streams and are not recommended for production machines. That policy affects users who try manual or registry-based bypasses to force an installation.
- Privacy and telemetry concerns: The compatibility check uses telemetry and device signals. While Microsoft’s rollout design relies on server-side decisions, some users will object to the notion of eligibility being decided and presented via cloud-backed logic rather than purely local checks. The company’s updates to Windows Update components have already generated debate about how assertively it nudges devices toward newer builds.
Recommendations for users and IT pros
- For consumers:
- Back up first. Always. Upgrades can fail and leave systems in awkward states.
- Use Windows Update to get the high-level compatibility result, then open PC Health Check for the detailed explanation if something fails.
- If your device is borderline eligible, check your OEM support site for BIOS/UEFI updates; enabling TPM and Secure Boot often fixes false negatives.
- For IT admins:
- Don’t rush broad rollouts based on a Windows Update compatibility message alone. Pilot in a controlled environment; validate critical line-of-business apps and device drivers before approving mass upgrades. Microsoft’s rollout uses blocks for driver/compatibility telemetry for a reason.
- If you need to delay the Windows Update offer, rely on update management tools (WSUS, Intune, Configuration Manager) and standard patch testing windows. Remember that Microsoft’s server-side staging might bypass simple UI toggles for individual machines.
What’s verifiable — and what remains uncertain
- Verifiable:
- Microsoft has updated the PC Health Check tool and published guidance on TPM and Secure Boot; the Windows Insider Blog describes the company’s approach to minimum system requirements.
- BetaNews, Windows Latest, TechRadar, and other outlets observed the new compatibility message in Windows Update for Release Preview Insiders and reproduced the exact wording of the message.
- Microsoft’s broader update strategy includes phased rollouts and compatibility holds; independent reporting and observed behavior in the field confirm that devices are offered upgrades on a staged basis rather than globally at once.
- Not fully verifiable (flagged with caution):
- Whether Microsoft’s primary motive for embedding the check in Windows Update is marketing, user convenience, or device security cannot be proven definitively from public statements alone. Treat commentary that frames the change primarily as a marketing tactic as informed analysis, not a documented corporate policy.
- The exact timing of an upgrade offer after eligibility is detected can vary with Microsoft’s backend policies; predicting the wait time for a specific device is not reliably possible without telemetry access to Microsoft’s rollout servers. Users should assume variability and rely on the documented phased rollout model.
Final assessment
Embedding a Windows 11 compatibility check inside Windows Update is a pragmatic move: it reduces friction for ordinary users, surfaces eligibility in a place where upgrade decisions are made, and pairs easily with the revised PC Health Check for actionable remediation steps. For Microsoft, the change also amplifies the visibility of upgrade offers and helps accelerate adoption on eligible devices as Windows 10 support winds down. Yet the technical and policy complexities that have defined the Windows 11 transition remain: firmware and driver state, OEM support windows, staged rollouts, and the difference between
eligible and
recommended mean that the presence (or absence) of a short message in Windows Update should be treated as the start of a decision process — not its end. Users should back up, verify the detailed Health Check findings, and, where applicable, test upgrades in a controlled fashion. Microsoft’s change simplifies one piece of the upgrade puzzle, but it does not erase the broader responsibilities that come with major OS migrations: plan, test, back up, and, when in doubt, wait until you have vendor-supplied BIOS/drivers and a clear rollback path.
Source: BetaNews
Windows Update is letting Windows 10 users know if they can upgrade to Windows 11