SOLVED OS Windows 10 1709 Inplace Upgrade

[Mahmoud87]

Hi guys

I am trying to do an In-Place upgrade from Windows 7 x64 Enterprise to Windows 10 x64 Enterprise build 1709.
I am not using the servicing plan yet, and still using TS. I have first imported the install.wim to SCCM, then created an Operating System Upgrade Package, distributed the content and showing green under the content status.

I have created a new task sequence to "Upgrade an operating system from upgrade Package", followed the wizard selected the right index for my Enterprise version.

Deployed this TS to a device collection, I have added 2 computers one running Windows 10 x64 build 1607, and the other running Windows 7 x64 Enterprise.

The Windows 10 upgraded fine without any issues, but the Windows 7 doesn't want to upgrade and got few errors. I have tested to other computers and the same thing happened the Windows 10 upgrade to the latest build 1709 and the Windows 7 computers still failing. Below some logs from the Windows 7.

Couldn't upload the smsts.log but here is the important part.

Failed to run the action: Upgrade Operating System. 
Unspecified error (Error: 80004005; Source: Windows)    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Set authenticator in transport    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Clear local default environment    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Let the parent group (Upgrade the Operating System) decides whether to continue execution    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
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)    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Failed to run the last action: Upgrade Operating System. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Set authenticator in transport    TSManager    1/11/2017 5:14:05 PM    3788 (0x0ECC)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
****************************************************************************    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Task sequence execution failed with error code 80004005    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Cleaning Up.    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Removing Authenticator    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Clean up post directory 'C:\WINDOWS\SMSTSPostUpgrade' on reboot    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Cleaning up task sequence folder    TSManager    1/11/2017 5:29:18 PM    3788 (0x0ECC)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
SetNamedSecurityInfo() failed.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
SetObjectOwner() failed. 0x80070005.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
==========[ TsProgressUI started in process 4800 ]==========    TsProgressUI    1/11/2017 5:29:19 PM    3820 (0x0EEC)
Command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister    TsProgressUI    1/11/2017 5:29:19 PM    3820 (0x0EEC)
Unregistering COM classes    TsProgressUI    1/11/2017 5:29:19 PM    3820 (0x0EEC)
Unregistering class objects    TsProgressUI    1/11/2017 5:29:19 PM    3820 (0x0EEC)
Shutdown complete.    TsProgressUI    1/11/2017 5:29:19 PM    3820 (0x0EEC)
Process completed with exit code 0    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Successfully unregistered TS Progress UI.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Trying to restore client to the state it can be managed    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
CCMExec service startup type is set to enabled    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Modifying CCMExec Service to auto start.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
CCMExec Service started    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Waiting for CcmExec service to be fully operational    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
CcmExec service is up and fully operational    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Current Assigned Management Point is SCCM.xxx.xxxx with Version 8540 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ClientLocation    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Successfully connected to MP SCCM.xxx.local:80    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Cleaning up any active TS requests in WMI.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Deleting CCM_TSExecutionRequest instance: CCM_TSExecutionRequest.RequestID="58e64714-0a9d-403f-b370-ab4c1e3edb74".    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Removed 1 instance of CCM_TSExecutionRequest for tasksequence.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Cleaning up any maintenance task requests in WMI.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{58E64714-0A9D-403F-B370-AB4C1E3EDB74}".    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{1D4A3355-981A-4B04-BBFA-C60272AF266A}".    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Removed 2 instances of SMS_MaintenanceTaskRequests for tasksequence.    TSManager    1/11/2017 5:29:19 PM    3788 (0x0ECC)
Start to cleanup TS policy    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
End Task Sequence policy cleanup    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
End program:     TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
Error executing Task Sequence Manager service. Code 0x80004005    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
Sending error status message    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)
Set authenticator in transport    TSManager    1/11/2017 5:29:26 PM    3788 (0x0ECC)

Hopefully someone can point me in the right direction.

 

[Prajwal Desai]

I see error 0xC1900208 which translates to Compatibility issues found (hard block). I think you must run a compatibility scan using the command - SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly on win 7 machine.

 

[Mahmoud87]

I see error 0xC1900208 which translates to Compatibility issues found (hard block). I think you must run a compatibility scan using the command - SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly on win 7 machine.

Hi Prajwal, I am so sorry guys, I meant to get back to the thread and mark it as solved got so busy at work and with this project. I figured it out the following day and you're right it was compatibility issues with SCEP. I have marked "ignore any dismissible Errors". All working perfect now.