Windows 10 Upgrade using SCCM

%3CLINGO-SUB%20id%3D%22lingo-sub-76957%22%20slang%3D%22en-US%22%3EWindows%2010%20Upgrade%20using%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76957%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%2C%3C%2FP%3E%3CP%3Ei'm%20using%20SCCM%20to%20upgrade%20windows%2010%201607%20to%201703%20and%20it%20working%20well%26nbsp%3B%3C%2FP%3E%3CP%3Ehowever%20when%20i%20want%20to%20upgrae%20from%201511%20to%201607%20or%201703%20it'%20fail%20with%20the%20following%20error%26nbsp%3B%3C%2FP%3E%3CP%3Eplease%20i%20need%20any%20help%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-76957%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOperating%20System%20Deployment%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78354%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Upgrade%20using%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78354%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Muhammad%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20smsts.log%20moves%20around%20depending%20on%20what%20stage%20of%20the%20deployment%20you%20are%20at.%26nbsp%3B%20Ronni%20Pedersen%20lists%20the%20various%20locations%20in%20his%20post%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.ronnipedersen.com%2F2014%2F08%2F12%2Fsccm-2012-r2-smsts-log-located%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.ronnipedersen.com%2F2014%2F08%2F12%2Fsccm-2012-r2-smsts-log-located%2F%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrank%20Rojas%20has%20a%20nice%20article%20on%20how%20to%20set%20the%20logging%20options%20for%20this%20logfile%20if%20you%20need%20to%20go%20deeper%20than%20the%20default%20logging%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fsystem_center_configuration_manager_operating_system_deployment_support_blog%2F2011%2F10%2F12%2Fhow-to-change-logging-options-for-smsts-log-in-system-center-configuration-manager%2F%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fsystem_center_configuration_manager_operating_system_deployment_support_blog%2F2011%2F10%2F12%2Fhow-to-change-logging-options-for-smsts-log-in-system-center-configuration-manager%2F%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78016%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Upgrade%20using%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78016%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8458%22%20target%3D%22_blank%22%3E%40Yvette%20O'Meally%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20Your%20response%26nbsp%3B%3C%2FP%3E%3CP%3E1-%20where%20i%20can%20find%20smsts.log%20%2C%20because%20i%20only%20found%20smstsv.log%20in%20SCCM%20logs%3C%2FP%3E%3CP%3E2-%20i%20use%20the%20latest%20version%201702%20with%20the%20latest%20hotfix%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77830%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20Upgrade%20using%20SCCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77830%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Muhammad%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20seems%20that%20the%20image%20you%20uploaded%20got%20stripped%20from%20your%20post.%20The%20community%20support%20folks%20were%20able%20to%20retrieve%20it%20for%20me.%26nbsp%3B%20For%20the%20benefit%20of%20other%20readers%2C%20the%20error%20message%20you%20received%20was%20%22Task%20sequence%20has%20failed%20with%20the%20error%20code%20(0x80004005).%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20a%20generic%20message.%26nbsp%3B%20To%20start%20troubleshooting%2C%20check%20the%20smsts.log%20file%20for%20applicable%20errors%20to%20see%20which%20step%20in%20the%20TS%20may%20be%20failing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20would%20be%20helpful%20to%20know%20what%20version%20of%20Configuration%20Manager%20you%20are%20using.%26nbsp%3B%20In%20case%20there%20are%20specific%20issues%20that%20may%20apply.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3E-Yvette%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Deleted
Not applicable

Hello all,

i'm using SCCM to upgrade windows 10 1607 to 1703 and it working well 

however when i want to upgrae from 1511 to 1607 or 1703 it' fail with the following error 

please i need any help 

3 Replies
Highlighted

Hello Muhammad

 

It seems that the image you uploaded got stripped from your post. The community support folks were able to retrieve it for me.  For the benefit of other readers, the error message you received was "Task sequence has failed with the error code (0x80004005)."

 

This is a generic message.  To start troubleshooting, check the smsts.log file for applicable errors to see which step in the TS may be failing.

 

It would be helpful to know what version of Configuration Manager you are using.  In case there are specific issues that may apply.

 

Thanks

-Yvette

Highlighted

Hello @Yvette O'Meally 

Thanks for Your response 

1- where i can find smsts.log , because i only found smstsv.log in SCCM logs

2- i use the latest version 1702 with the latest hotfix 

Highlighted

Hi Muhammad

 

The smsts.log moves around depending on what stage of the deployment you are at.  Ronni Pedersen lists the various locations in his post here: https://www.ronnipedersen.com/2014/08/12/sccm-2012-r2-smsts-log-located/.

 

Frank Rojas has a nice article on how to set the logging options for this logfile if you need to go deeper than the default logging - https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_...