Fix it now
The compatibility scan found something on this machine that Setup will not carry across, so it stopped before writing anything. Run the scan on its own, read the name out of the compatibility data rather than guessing, then remove or update the product it names.
D:\setup.exe /auto upgrade /noreboot /eula accept /compat scanonly /compat ignorewarning
echo %errorlevel%
dir C:\$WINDOWS.~BT\Sources\Panther\CompatData*.xml
findstr /i BlockingType C:\$WINDOWS.~BT\Sources\Panther\CompatData*.xml
- Read the exit code. 0xC1900208 means the scan found an actionable compatibility issue. 0xC1900210 means it found none, and whatever is stopping you is not a compatibility block.
- In the CompatData file, find the entries carrying
BlockingType="Hard". TheNameattribute on thatProgramelement is the product you have to deal with. - If nothing is flagged under Programs, look at the driver packages instead: an entry with
BlockMigration="True"is a driver Setup will not migrate. - Uninstall the named product with the vendor’s own removal tool rather than through Apps and Features, restart, then re-run the scan and confirm the entry has gone.
- Run the upgrade, then install a version the vendor supports on the build you have moved to.
/compat ignorewarning only passes messages Setup treats as dismissible. It does nothing to a hard block, and no supported switch overrides one.
If the scan comes back clean and the upgrade runs, you are done. If not, the next section explains what the scan is deciding and which of the blocks you have.
Why it happens
Before a feature update writes anything, Setup runs a compatibility phase: it inventories applications, drivers, devices and languages, checks each against a compatibility database and against its own rules, and decides whether the machine can be upgraded with your apps and data intact. 0xC1900208 is the published result code for that phase deciding no. Microsoft names it MOSETUP_E_COMPAT_INSTALLREQ_BLOCK and describes it as the system not passing the compat scan to install the update, or more plainly as an actionable compatibility issue such as an incompatible app.
0xC1900209 is the same finding one step later. It is MOSETUP_E_COMPAT_INSTALLREQ_CANCEL: the run ended because the compatibility result was not accepted. Interactively that is somebody choosing not to continue at the compatibility screen; in an automated run it is what Setup returns when nobody was there to choose. Neither code is a fault in Windows, and neither is fixed by retrying.
The verdict is written down before the process exits, which is what makes this one of the few upgrade failures you can diagnose in a minute. Setup writes CompatData<date-time>.xml into C:\$WINDOWS.~BT\Sources\Panther, and inside it every item that must be dealt with is marked BlockingType="Hard". Drivers are recorded separately, under DriverPackages, with BlockMigration="True" on anything that will not come across.
Endpoint security dominates the hard-block list for a structural reason. These products install filter drivers that load early and sit in the path of every file operation, and a filter driver written against one kernel and left running on another does not degrade gracefully. Setup blocks rather than gamble on producing a machine that will not boot.
An application is marked as a hard block
You have this one if The CompatData file contains a Program entry with BlockingType=”Hard”, naming an antivirus, EDR agent, encryption product, VPN client or virtualisation tool.
- Check the vendor’s support matrix for the build you are moving to before you remove anything, so you know what you will be reinstalling.
- Uninstall with the vendor’s dedicated removal utility. Ordinary uninstall routines frequently leave drivers and services behind.
- Restart, then re-run the scan-only pass and confirm the entry is gone.
Microsoft Defender takes over automatically once a third-party antivirus is removed, so the machine is not left without protection during the upgrade window.
A driver package will not migrate
You have this one if Nothing is flagged under Programs, but a DriverPackage entry carries BlockMigration=”True”.
- Identify the package in the driver store:
pnputil /enum-drivers, matching on the original name and provider rather than the oem number. - Install a version the vendor publishes for the target build if one exists.
- If none exists, remove the package:
pnputil /delete-driver oemNN.inf /uninstall.
The product was uninstalled and the block persists
You have this one if The same name comes back in the compatibility data after you removed it, or the block survives with nothing matching in Apps and Features.
- Run
fltmc filtersfrom an elevated prompt and note any filter that is not Microsoft’s. - Fetch the vendor’s clean-up tool, which is written specifically to remove what the uninstaller leaves.
- Restart, re-run the scan, and confirm the entry has cleared before starting the upgrade.
The compatibility phase timed out or was killed
You have this one if 0xC1900103 or 0xC1900109 rather than 0xC1900208.
- 0xC1900103 is MOSETUP_E_COMPAT_TIMEOUT: the compatibility issues were not resolved inside the time limit. On an interactive run that usually means the prompt sat unanswered.
- 0xC1900109 is MOSETUP_E_COMPAT_TERMINATE: the process was terminated during the actionable compatibility phase. Look for whatever ended it, which on a managed machine is often the endpoint agent itself.
- Re-run the scan from an interactive elevated session with nothing else running.
The device is under a gated compatibility block
You have this one if Nothing local looks wrong, the compatibility data is thin, and this device is never offered the build while others are.
- Run SetupDiag against the logs. Its GatedCompatBlock rule describes a temporary block with a fix pending, which is a different situation from a product you can uninstall.
- Prefer waiting, or upgrading from media once the underlying driver or application has been updated.
- Do not treat a gated block as an obstacle to route around; it is usually protecting the device from a known defect.
Full reference
Where the verdict is written
| Location | What it holds |
|---|---|
C:\$WINDOWS.~BT\Sources\Panther\CompatData<date-time>.xml |
The compatibility result from the attempt in progress, during the downlevel, OOBE or rollback stages |
C:\Windows\Panther |
Where the same logs end up once the OOBE stage has been passed |
*_APPRAISER_HumanReadable.xml |
The readable compatibility record. Search the system drive for it |
C:\Windows\Logs\SetupDiag\SetupDiagResults.xml |
SetupDiag’s own findings when Windows Setup ran it automatically |
What to search for in each file
- In the CompatData file,
BlockingType="Hard"inside the<Programs>section. TheNameattribute on theProgramelement is the product. - In the same file,
//DriverPackages/DriverPackage[@BlockMigration="True"]for drivers that will not be carried over. - In the human-readable appraiser file,
DT_ANY_FMC_BlockingApplication=True, and then theLowerCaseLongPathUnexpandedproperty, which holds the full path to the artefact that triggered the block. - Both are plain XML. Any text editor will do, and neither needs a tool downloading.
Exit codes from a scan-only run
| Code | Symbolic name | What it means |
|---|---|---|
0xC1900210 |
MOSETUP_E_COMPAT_SCANONLY | The scan ran and found no compatibility issue |
0xC1900208 |
MOSETUP_E_COMPAT_INSTALLREQ_BLOCK | The system does not pass the compat scan to install the update |
0xC1900209 |
MOSETUP_E_COMPAT_INSTALLREQ_CANCEL | Cancelled because the system does not pass the compat scan |
0xC1900103 |
MOSETUP_E_COMPAT_TIMEOUT | Compatibility issues were not resolved within the time limit |
0xC1900109 |
MOSETUP_E_COMPAT_TERMINATE | The process was terminated during the actionable compatibility phase |
SetupDiag rules that name a block
| Rule | What it reports |
|---|---|
| CompatBlockedApplicationAutoUninstall | An application that must be uninstalled, which Setup can remove itself |
| CompatBlockedApplicationManualUninstall | An application that must be removed by hand before the upgrade |
| HardblockDeviceOrDriver | An incompatible device driver |
| GatedCompatBlock | A temporary block with a fix pending |
| GenericCompatBlock | The system does not meet the hardware requirements |
| HardblockMismatchedLanguage | The host and target operating system languages do not match |
Taking an endpoint agent out cleanly
- In a managed estate, remove the device from the management group first, or the agent will be pushed back mid-upgrade.
- Uninstall with the vendor’s removal utility, not from Apps and Features.
- Restart, then confirm with
fltmc filtersthat no filter from that vendor is still loaded. Disabling real-time protection does not unload the driver. - Run the upgrade.
- Reinstall the current supported version and confirm it reports healthy in its own console before you close the job.
Where the blocker is disk encryption, decrypting a volume to clear it leaves the data unprotected until encryption is re-enabled, and on a large disk the decrypt and re-encrypt cycle runs for hours. Follow the vendor’s documented pre-upgrade procedure, which for some products is a driver update rather than a full decryption, and make sure a current backup exists before starting.
When the block is a product that has run out of road
There is a difference between an agent that needs updating and a product line the vendor no longer supports on current Windows. The first costs a maintenance window. The second will block the next feature update as well, and the one after that, so removing it to get this upgrade through simply moves the problem. Check the vendor’s support statement for the build you are moving to before deciding which of the two you have.
When a licence is the actual fix
Where the blocker is an endpoint product the vendor no longer supports on current Windows builds, removing it is only half the job: the machine needs a supported product afterwards, and staying on an unsupported one moves the same block to the next feature update. Check your existing subscription first, because if a supported version exists for the build you are moving to, upgrading the agent costs nothing. Arco supplies business antivirus and endpoint licences across the main vendors, including migrations off a product that has reached the end of its supported life, and can tell you which of them currently state support for the build you are moving to.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC1900208 |
MOSETUP_E_COMPAT_INSTALLREQ_BLOCK: the system does not pass the compat scan to install the update. Microsoft also describes it as an actionable compatibility issue such as an incompatible app | Microsoft Learn |
0xC1900209 |
MOSETUP_E_COMPAT_INSTALLREQ_CANCEL: the run was cancelled because the system does not pass the compat scan | Microsoft Learn |
0xC1900208 - 0x4000C |
Microsoft Support gives this pair as an incompatible app installed on the PC blocking the upgrade from completing | Microsoft Support |
0xC1900103 |
MOSETUP_E_COMPAT_TIMEOUT: the compatibility issues were not resolved within the required time limit | Microsoft Learn |
0xC1900109 |
MOSETUP_E_COMPAT_TERMINATE: the installation process was terminated during the actionable compatibility phase | Microsoft Learn |
Confirm the fix worked
- A scan-only run exits with 0xC1900210 rather than 0xC1900208.
- No entry in the current CompatData file carries BlockingType=”Hard”.
fltmc filtersshows no filter driver from the removed product.- The upgrade completes and
winverreports the build you intended. - The endpoint agent is reinstalled at a supported version and reports healthy in its own console.
Questions people ask about this
Can I force the upgrade past the block?
No. Setup distinguishes warnings, which /compat ignorewarning will pass, from hard blocks, which it will not, and there is no supported switch for the second kind. The block exists because the predicted outcome is a machine that does not work correctly.
Do I have to buy a new antivirus licence?
Not usually. If your current product has a supported version for the target build and the subscription is current, updating the agent is enough and costs nothing. A purchase is only genuinely needed when the product line itself is no longer supported on that build, or the licence has lapsed.
Where exactly is the list of blockers?
In CompatData<date-time>.xml under C:\$WINDOWS.~BT\Sources\Panther while the attempt is live, and in C:\Windows\Panther afterwards. Entries that must be dealt with are marked BlockingType=”Hard”, and the product name is on the same element.
Does removing the agent break our compliance position?
For the length of the upgrade the machine falls back to Microsoft Defender, which is a real antivirus rather than a gap. Document the window, keep it short, and reinstall the managed agent as soon as the upgrade finishes.
The scan names something we cannot remove. Now what?
Then the upgrade waits for the vendor, or the product is replaced. If it is a gated block rather than a product, SetupDiag will say so, and the honest answer is to wait for the fix rather than to work around a block that exists to protect the device.
