Feature upgrade stops on managed workstation

Micheal Brown 45 Reputation points
2026-10-28T17:38:07.6933333+00:00

I attempted to deploy a feature upgrade on our enterprise laptop but the process completely stopped and the system prompt states as follows: This device does not meet the minimum system requirements for this upgrade.

I have checked the standard update logs, but now multiple client devices in our fleet are failing with identical readiness blocks.

I tried inspecting the setup logs and running diagnostic checks (even though the hardware seems fully compatible with our corporate setup) but it still fails to identify the exact blocking factor.

How can I identify the specific compatibility restriction and distinguish actual hardware limitations from policy or configuration issues?

Can someone please assist?

Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments No comments

2 answers

Sort by: Most helpful
  1. Ronald Sabiiti 1,505 Reputation points Independent Advisor
    2026-10-28T18:30:32.6733333+00:00

    Hello Micheal,

    To identify the specific restriction, I recommend reviewing the following logs on one affected device:

    1. Check C:\$WINDOWS.~BT\Sources\Panther\ for CompatData*.xml and setupact.log.

    Run Microsoft's SetupDiag to analyze the upgrade logs and identify potential hardware, driver, or application compatibility issues.

    If the device appears to meet the requirements, compare its feature-update policies and deployment settings with those of a device that upgrades successfully.

    Additional references:

    Windows Setup compatibility logs

    Windows 11 system requirements

    Please share the SetupDiag results and the target Windows version. This will help us determine whether the block is caused by hardware requirements, software compatibility, or deployment configuration before making changes across the fleet.

    If this information was helpful, please click Accept Answer.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-10-28T17:38:28.4333333+00:00

    Use the Windows Setup compatibility scan logs, not only the standard Windows Update logs. A readiness block that says the device does not meet requirements can come from incompatible apps, drivers, or upgrade safeguards, and the compatibility logs are the place to identify the exact blocker.

    1. Check the Setup result code first.
      • 0xC1900208 = incompatible application or driver is blocking the upgrade.
      • 0xC1900210 = no compatibility issues were found.
    2. Open the compatibility logs in the hidden Panther locations.
      • C:\$WINDOWS.~BT\Sources\Panther\CompatData<date-time>.xml
      • C:\Windows\Panther
      • Search the OS drive for *_APPRAISER_HumanReadable.xml Use the newest timestamped file.
    3. In CompatData<date-time>.xml, search for the exact blocking type.
      • Search for BlockingType="Hard" under the <Programs> section. This identifies applications that must be removed or mitigated before the upgrade can continue.
      • Search for //DriverPackages/DriverPackage[@BlockMigration="True"]. This identifies drivers that will not migrate and must be updated or removed.
    4. In *_APPRAISER_HumanReadable.xml, identify the exact file path causing the block.
      • Search for DT_ANY_FMC_BlockingApplication=True
      • Then look nearby for LowerCaseLongPathUnexpanded That property gives the exact path to the blocking artifact, including leftover .exe or .dll files from software that may already have been uninstalled.
    5. Remediate based on what the log shows.
      • If it is an application block, uninstall the app or upgrade it to a compatible version.
      • If the log points to leftover files from an already removed app, remove the indicated file.
      • If it is a driver block, update or remove the driver.
    6. Refresh setup state before retrying with the same media.
      • Empty C:\Windows\SoftwareDistribution\Download
      • If not needed, empty C:\$WINDOWS.~BT Note: deleting cached setup files can remove diagnostic artifacts needed for later review.
    7. Re-run a compatibility-only scan to separate compatibility findings from the full upgrade workflow. Run from an elevated Command Prompt:
         setup.exe /auto upgrade /noreboot /eula accept /compat scanonly /compat ignorewarning
      
      This generates fresh compatibility results without running the full upgrade.
    8. Confirm whether the issue is cleared.
      • If the next scan returns 0xC1900210, compatibility checks passed.
      • If it still returns 0xC1900208, review the logs again for additional blockers.
    9. For fleet-wide analysis, use SetupDiag. SetupDiag parses Windows Setup logs and maps them to known rules such as CompatBlockedApplication, which helps distinguish whether the block is caused by an application, driver, or another setup rule. Example:
         SetupDiag.exe /LogsPath "C:\Temp\WindowsSetupLogs" /Output "C:\Temp\SetupDiag-Results.txt"
      
    10. If the devices are managed through Intune feature updates, also review compatibility reporting there. The Windows feature update compatibility risks report can show affected devices and classify issues such as:
    • blocking upgrade
    • blocking upgrade, update application to newest version
    • driver won't migrate to new OS
    • safeguards

    For distinguishing hardware limitations from policy or configuration issues:

    • Use Windows 11 readiness reporting in Endpoint analytics to verify whether devices meet minimum hardware requirements.
    • If devices do not meet Windows 11 minimum requirements, they will remain on their current Windows 10 version unless configured to receive the latest Windows 10 feature update instead.
    • If hardware is eligible but the compatibility logs show BlockingType="Hard", BlockMigration="True", or a SetupDiag rule such as CompatBlockedApplication, the issue is an app, driver, or configuration blocker rather than a hardware minimum requirement failure.
    • If Intune compatibility reporting shows a safeguard hold, that indicates a known compatibility protection rather than a raw hardware shortfall.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.