When deploying Windows 10 1709 Feature Update using SCCM, you may encounter errors when running the installation in Software Center. These errors are sent by the Windows setup itself, they are not related to SCCM. In this post, we’ll show you how to troubleshoot these error and how to resolve the error 0xC1900208 – 1047526904. This post assumes that you’ve done the preparation steps to deploy features upgrades with SCCM.

Windows 10 1709 Troubleshooting

Here are some basic troubleshooting tips that you need to understand before proceeding. This blog post is not about troubleshooting any errors, we’ll focus on the frequent 0xC1900208 error but we think that you need basic understanding before proceeding. If you’re already familiar with this process, skip to the next section.

When launching a Windows 10 feature update from SCCM :

  • Upgrade files (ESD and WindowsUpdateBox.exe) are downloaded in SCCM cache (C:\Windows\ccmcache)
  • Relevant content is also stored in C:\WINDOWS\SoftwareDistribution\Download
  • ESD file is unpacked in the C:\$WINDOWS.~BT folder (hidden)
  • Windows setup is launched from that last location
  • Relevant Log files are located in C:\$WINDOWS.~BT\Sources\Panther
  • To read log file in the Panther directory, ensure to start CMtrace using Administrative privileges

Theses 3 location will get referred in this post. Here’s the relevant Microsoft documentation that will help you troubleshoot any Windows installation errors:

Resolution for Error 0xC1900208 – 1047526904

So let’s get back to our main topic which is resolving Error 0xC19002081047526904. This post has been made on Windows 10 computers using build 1607 and 1703.

  • When running the Windows 10 feature update from the Software Center you receive the error 0xC1900208 :

SCCM Windows 10 Feature Update Error 0xC1900208

  • When retrying a second time the error 0x80240020 is returned. Don’t use this error for troubleshooting, use the first one.

SCCM Windows 10 Feature Update Error 0xC1900208

  • Same error is shown in C:\Windows\CCM\Logs\WUAHandler.log

SCCM Windows 10 Feature Update Error 0xC1900208

Error 0xC1900208 - 1047526904

Following Microsoft documentation our error is due to  :  This could indicate that an incompatible app installed on your PC is blocking the upgrade process from completing. Check to make sure that any incompatible apps are uninstalled and then try upgrading again.

The first easy troubleshooting step you can do at this point is to launch setup.exe from the C:\$WINDOWS.~BT directory.

  • After going through the first screens, the setup will warn you about those incompatible apps. Here are 2 examples we encountered.

SCCM Windows 10 Feature Update Error 0xC1900208 SCCM Windows 10 Feature Update Error 0xC1900208

  • If you don’t want to run the setup.exe, you can refer to the C:\$WINDOWS.~BT\Sources\Panther\CompatData[date-time].xml. You’ll have a couple of Compatdata.xml files, usually, the most recent one will contain the information you need. In this example, Mcafee is the faulty application and give setup the instruction to stop

SCCM Windows 10 Feature Update Error 0xC1900208

  • Our next action was to check the Mcafee website to check if Windows 10 1709 is supported. Unfortunately, it’s not yet supported at the time of this writing. The only option we had was to completely uninstall the Mcafee suite from the computer
  • Once uninstalled, a couple of steps must be performed to restart the upgrade process. If you simply hit Retry in Software Center, it won’t work.
    • Empty the SCCM Cache
    • Delete the content of C:\WINDOWS\SoftwareDistribution\Download folder
    • Delete the C:\$WINDOWS.~BT folder (hidden)
    • Initiate a Software Update Deployment Evaluation Cycle and Software Update Scan Cycle
  • Wait a couple of minute for the scan to complete and retry the deployment
  • The deployment will now work, no more 0xC1900208 errors! You can follow the process in the C:\$WINDOWS.~BT\Sources\Panther\Setupact.log file

SCCM Windows 10 Feature Update Error 0xC1900208

You’ve now mastered the 0xC1900208 error and can continue your Windows 1709 migration !

Comments (18)


08.01.2019 AT 10:47 AM
THANK YOU ! Windows 10 display an error but doesn't give any solution ! Without your article I will still be stuck and looking for a solution. C:\$WINDOWS.~BT\Sources\Panther\CompatData[date-time].xml have been the solution for me, 4 files with this name was there and one was showing the program blocking the migration from windows 7 to windows 10. After I just uninstalled this program and I have been able to make the update, It was magic ! I hope Microsoft is going to promote your page because it was really useful... Regards

Brian Walz

07.25.2019 AT 10:07 AM
When I went to run the setup.exe in the C:\$WINDOWS.~BT directory, all the other folders disappeared. If they do, you can go into %windir%\Panther\NewOS\Panther\ and the "CompatData" XML file will be there for viewing.


02.22.2019 AT 12:02 PM
Excelente, solucionó mi problema.


05.22.2018 AT 07:06 AM
Check out https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures... Helped me figure out I screwed up my SetupConfig.ini file. =)

chander mani

04.02.2018 AT 10:01 AM
in my case upgrade is working fine but in sccm report, it is showing as Failed to install update(s). Which log I need to check. any link or document...

Kelly Jackson

03.23.2018 AT 10:18 AM
Hey Guys, Firstly, Id like to say thank you for writing up this great documentation. I believe this is my issue for sure. So I followed the steps and it seems that after I deleted the CCM Cache, the C:\$WINDOWS.~BT folder, and the SoftwareDistribution\Download folder I ran the actions in Configuration Manager and now I cannot get the update to show back up in Software center. Any Ideas on what could cause this or what is preventing it from coming back? Im running 1607 trying to feature update to 1709.


08.14.2018 AT 08:12 AM
I am having the exact same issue. I cannot get the update TS to show up in the Software Center again. Have you found the fix?


03.01.2018 AT 02:21 PM
Great info, not even Microsft knows this. I had spend hrs with them and they were not able to read their own logs.


03.01.2018 AT 07:17 AM
Great Article!!! you send me in the right direction and saved me hours of work.


02.22.2018 AT 05:43 AM
great article

James Leroux

01.16.2018 AT 11:02 AM
Just a snip of what you can do to deal with these compatibility error messages. # Set Defaults $TITLE = "OS Upgrade Compatibility Check" $REBOOTTITLEEN = "Upgrade Compatibility Check Failed. Compatibility error found: " $REBOOTTITLEFR = "La vérification de compatibilité de mise à niveau a échoué. Erreur de compatibilité trouvée: " $MESSAGE = "--No Issues Found--" $MESSAGEFR = "--Aucun problème n'a été trouvé--" $RETURNCODE = "0" #Establish TSENV Write-host "--Establish TSENV" $TSENV = New-Object -COMObject Microsoft.SMS.TSEnvironment #Process _SMSTSOSUpgradeActionReturnCode, set $returncode IF ($OSUpgradeActionReturnCode -eq "3247440400") { $TITLE = "OS UPGRADE COMPATIBILITY CHECK PASSED" $MESSAGE = "--No Compatibility Issues Found but OSUpgrade Still Exited with failure, engage support--" $MESSAGEFR = "--Pas de problèmes de compatibilité détectés mais OSUpgrade Still Exited with failure, engagez support--" WRITE-HOST "$MESSAGE" $RETURNCODE = "1" } IF ($OSUpgradeActionReturnCode -eq "3247440392") { $TITLE = "COMPATIBILITY CHECK FAILURE" $MESSAGE = "--Compatibility issues found (hard block,software)--" WRITE-HOST "$MESSAGE" $MESSAGE = "--Detected Software: " $MESSAGEFR = "--Logiciel détecté: " $RETURNCODE = "1" $SCANRESULTSPATH = $ENV:SYSTEMDRIVE + '\$WINDOWS.~BT\SOURCES\PANTHER' $SCANRESULTSFILE = Get-ChildItem $SCANRESULTSPATH\compat*.xml |select-string -pattern "Programs"|group path|select name $SCANRESULTSFILECOUNT = $SCANRESULTSFILE.NAME | MEASURE-OBJECT IF ($SCANRESULTSFILE.NAME -like "*Compatdata*" -and $SCANRESULTSFILECOUNT.COUNT -eq "1") { [xml]$SCANRESULTS = get-content $SCANRESULTSFILE.NAME $FORMATEDRESULTS = $SCANRESULTS.compatreport.programs.program.name |FORMAT-TABLE|OUT-STRING #$MESSAGE = $MESSAGE +"`r`n" + $FORMATEDRESULTS $MESSAGE = "$MESSAGE`r`n$FORMATEDRESULTS" $MESSAGEFR = "$MESSAGEFR`r`n$FORMATEDRESULTS" #$MESSAGE = "$MESSAGE`r`n$($FORMATEDRESULTS.something)" write-host $message } ELSE { $MESSAGE = $MESSAGE + "`r`n" + "Unable to process correct COMPATDATA XML please contact support" $MESSAGEFR = $MESSAGEFR + "`r`n" + "Impossible de traiter correctement le format XML COMPATDATA, veuillez contacter le support" write-host $MESSAGE } } IF ($OSUpgradeActionReturnCode -eq "3247440388") { $TITLE = "COMPATIBILITY CHECK FAILURE" $MESSAGE = "--Wrong SKU or architecture (Language)--" $MESSAGEFR = "--Mauvais SKU ou l'architecture (Langue) --" WRITE-HOST "$MESSAGE" $RETURNCODE = "1" } IF ($OSUpgradeActionReturnCode -eq "3247440384") { $TITLE = "COMPATIBILITY CHECK FAILURE" $MESSAGE = "--Does not meet system requirements for Windows 10--" $MESSAGEFR = "--Ne répond pas aux exigences système pour Windows 10--" WRITE-HOST "$MESSAGE" $RETURNCODE = "1" } IF ($OSUpgradeActionReturnCode -eq "3247440398") { $TITLE = "COMPATIBILITY CHECK FAILURE" $MESSAGE = "--Insufficient free disk space--" $MESSAGEFR = "--Inspace disque libre insuffisant--" WRITE-HOST "$MESSAGE" $RETURNCODE = "1" }


12.31.2017 AT 04:28 PM
I use a simple powershell script to parse that XML and dump out the specific incompatible programs into a message or log... I ended up using a TS to deploy the upgrade instead, and worked in some logic to read the setup return code and parse the xml if needed......


12.20.2017 AT 10:01 AM
Sorry about that wrong blog I put on


12.20.2017 AT 09:59 AM
Hello guys Do you have any documentation on a side by side migration from start to finish for 2012R2 to Current Branch?


11.17.2017 AT 12:37 PM
I have similar error for Microsoft End Point Protection as incompatible app for Windows 10 in place upgrade. Had to uninstall Microsoft End Point Protection from Control Panel and then retried in place upgrade from Windows 7 Entp and Windows 8 Entp to v1709 Windows 10 Entp. The process went without any issue and in place upgrade was successful. All apps worked and the user data was intact. So, If anybody is trying for in place upgrade from Windows 7 or Windows 8 to v1709 Windows 10 Entp check for incompatible apps. Ram


11.16.2017 AT 07:47 AM
Awesome article! much appricated.