Most of the Organizations today are running Windows 7 OS on their computers. Looking at the stability and features of Windows 10, most of them are planning to do an upgrade of Windows 7 to Windows 10. Very recently I was working on upgrading Windows 7 to Windows 10. In fact there is a post that is published to show In-place upgrade to Windows 10 Enterprise with SCCM. I had installed Configuration Manager current branch version 1602. I deployed a task sequence that would do an in-place upgrade to Windows 10. But that didn’t go well and the task sequence failed. When i checked the log file i found that my Windows 10 upgrade setup failed with exit code 0xC1900200.
Here is the error message that I got :-
Validating package for OS upgrade version
The version of source OS upgrade package ‘10.0.10240’ is supported to be used in OS upgrade.
No timeout set for Windows Upgrade Setup
Command line of Windows Setup upgrade: ‘”C:\_SMSTaskSequence\Packages\IND00006\SETUP.EXE” /ImageIndex 1 /auto Upgrade /quiet /noreboot /postoobe “C:\Windows\SMSTSPostUpgrade\SetupComplete.cmd” /postrollback “C:\Windows\SMSTSPostUpgrade\SetupRollback.cmd” /DynamicUpdate Disable’
Command line for extension .EXE is “%1” %*
Set command line: “C:\_SMSTaskSequence\Packages\IND00006\SETUP.EXE” /ImageIndex 1 /auto Upgrade /quiet /noreboot /postoobe “C:\Windows\SMSTSPostUpgrade\SetupComplete.cmd” /postrollback “C:\Windows\SMSTSPostUpgrade\SetupRollback.cmd” /DynamicUpdate Disable
Executing command line: “C:\_SMSTaskSequence\Packages\IND00006\SETUP.EXE” /ImageIndex 1 /auto Upgrade /quiet /noreboot /postoobe “C:\Windows\SMSTSPostUpgrade\SetupComplete.cmd” /postrollback “C:\Windows\SMSTSPostUpgrade\SetupRollback.cmd” /DynamicUpdate Disable
Process completed with exit code 3247440384
Windows Setup completed with exit code 3247440384
Saving exit code 0xC1900200 of Windows upgrade to Task sequence environment variable ‘_SMSTSOSUpgradeActionReturnCode’
Windows setup failed with exit code 0xC1900200. Failing task sequence step.
Enabling TSManager service
smstsmgr service startup type is set to automatic
Enabling CCMExec service
CcmExec service startup type is set to automatic
Setting the client out of provisioning mode
Exiting SetClientProvisioningMode 0x00000000
upgrade.Run(), HRESULT=80004005
Exiting with code 0x80004005
Process completed with exit code 2147500037 TSManager
!——————————————————————————————–!
Failed to run the action: Upgrade Operating System.
Unspecified error (Error: 80004005; Source: Windows)
Set authenticator in transport
Set a global environment variable _SMSTSLastActionRetCode=-2147467259
Set a global environment variable _SMSTSLastActionSucceeded=false
Clear local default environment
Let the parent group (Upgrade the Operating System) decides whether to continue execution
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Operating System. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)
Set authenticator in transport
Troubleshooting :-
If you are planning to do in-place upgrades to migrate from Windows 7, Windows 8, or Windows 8.1 to Windows 10 using SCCM task sequences then you must first try running a command that tells you whether you can do an in-place upgrade smoothly. To do this, SETUP.EXE includes a command line switch that tells it to “check for compatibility” but not actually perform the upgrade. You need to have the Windows 10 source media with you. The full command line would typically look something like this:
SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly
Windows 10 upgrade setup failed with exit code 0xC1900200
To fix Windows 10 upgrade setup failed with exit code 0xC1900200, let’s understand the error codes first. Here are the lists of the most common upgrade and installation errors and some things you can try to fix them.
| Error Code | Ways to fix it |
| 0x80073712 | A file needed by Windows Update is likely damaged or missing. |
| 0x800F0923 | A driver or other software on your PC isn’t compatible with the upgrade to Windows 10. |
| 0x80200056 | The upgrade process was interrupted because you accidentally restarted your PC or signed out of your PC. Try upgrading again and make sure your PC is plugged in and stays turned on. |
| 0x800F0922 | Your PC couldn’t connect to the Windows Update servers. If you’re using a VPN connection to connect to a work network, disconnect from the network and turn off the VPN software (if applicable) and try upgrading again. It could also mean there isn’t enough free space in the System Reserved partition. You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition. |
| 0xC1900208 – 0x4000C | 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. |
| 0xC1900200 – 0×20008 0xC1900202 – 0×20008 | This may signify that your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10. |
| 0x80070070 – 0×50011 0x80070070 – 0×50012 0x80070070 – 0×60000 | This likely indicates that your PC doesn’t have enough space available to install the upgrade. Free some space on the drive and try again. |
Resolution – If you look at the above table, the error code 0xC1900200 translates to “PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10.” This was indeed correct. When i checked the memory of that machine, it was less than the required memory that was supposed to be. After increasing the memory of the machine, I did not face this error. I hope the above table helps you in understanding the cause of any other errors.
“SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly”
It has /Quiet argument, will it really display any window or will any log be created somewhere? I got the windows stating the cause when I ran it without it.
Any idea why when i run:
“SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly”
It starts to run, but then says “An unknown command-line option [/Auto upgrade] was specified?
i am not sure why you see that message. The command is correct, can you create a new thread and post the screenshot in forums.
Hi Prajwal,
i’m new to SCCM and learning on the job.
I have been tasked to do an In-place upgrade of windows 7 to 10. I successfully setup SCCM 1710 and created an upgrade package and Task sequence. Then distributed it and deployed to a device collection. The upgrade is deployed ok.
However, the Windows 10 upgrade requires the to be initiated from Software centre on client machine.
How can i make the upgrade to initiate without initiating it in PC’s software centre.
Could below commands be the solution and if yes, how/where should i apply them?
SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly
Thanks
Morning,
I am also getting the error “Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392)” and you have mentioned in your resolution that the error code relates to the machine in question not meeting the minimum requirements and Memory was the issue.
In my case I have sufficient memory, CPU and HDD space. When I run the below command in the Operating system sources location I get an error saying that the Intel HD Graphics Card is not compatibles.
SETUP.EXE /Auto Upgrade /NoReboot /DynamicUpdate Disable /Compat ScanOnly
Surely this can be bypassed and the worst result is that it wont have a compatible graphics driver?
Can you elaborate on this? Is there a way to change the “Hard Block” to bypass?
Thanks prajwal,
I have two machines failing to run an upgrade sequence at upgrading operating system. I looked at all the logs I know of and ran the compat scan only (it passed). I’m thinking at this point the two machines are getting a bare metal. Your thoughts ?
Hey Prajwal,
My work assigned me to handle the WIndows updates and we are getting alot of failures which logs are you pulling to see these kind of failures ?