Win7 to Win10 1803/1809 in-place upgrade Task Sequence breaks with no apparent error code

%3CLINGO-SUB%20id%3D%22lingo-sub-708858%22%20slang%3D%22en-US%22%3EWin7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-708858%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%E2%80%99re%20migrating%20from%20Win7SP1%20to%20Win10%20Ent.%201803%2F1809%20in%20our%20corporate%20environment.%20Strange%20thing%20noticed%20is%20migration%20TS%20always%20breaks%20on%20Latitude%20E7470%20after%20%E2%80%98Upgrade%20Operating%20System%E2%80%99%20task.%20Other%20models%20(E7440%2C%20E7450%2C%20E6440%2C%20O7010%2C%20O9020%2C%20T7910%2C%20etc.)%20don't%20have%20such%20issue%20at%20large.%20Almost%2050%20nos.%20of%20E7470%20is%20tried%20and%20all%20of%20them%20got%20the%20same%20issue.%20Currently%20migration%20on%20this%20particular%20model%20is%20on%20hold.%20Didn%E2%80%99t%20see%20anyone%20mentioning%20the%20same%20issue%20anywhere.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETS%20screenshot%20as%20well%20as%20last%20few%20lines%20from%20smsts.log%20is%20copied%20below.%20As%20you%20can%20see%20there%20is%20no%20error%20reported%20by%20the%20task.%20But%20a%20reboot%20is%20initiated%20somehow%2C%20which%20breaks%20Task%20Sequence%20and%20then%20it%20doesn%E2%80%99t%20go%20further.%20In%20general%2C%20what%20are%20the%20reasons%20why%20such%20error%20occur%3F!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EProcess%20completed%20with%20exit%20code%200%20TSManager%2019%2F06%2F2019%2018%3A55%3A23%207816%20(0x1E88)%0A!--------------------------------------------------------------------------------------------!%20TSManager%2019%2F06%2F2019%2018%3A55%3A23%207816%20(0x1E88)%0ASuccessfully%20completed%20the%20action%20(Upgrade%20Operating%20System)%20with%20the%20exit%20win32%20code%200%20TSManager%2019%2F06%2F2019%2018%3A55%3A23%207816%20(0x1E88)%0ANot%20in%20SSL%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20global%20environment%20variable%20_SMSTSLastActionRetCode%3D0%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20global%20environment%20variable%20_SMSTSLastActionName%3DUpgrade%20Operating%20System%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20global%20environment%20variable%20_SMSTSLastActionSucceeded%3Dtrue%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AClear%20local%20default%20environment%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AThe%20action%20(Upgrade%20Operating%20System)%20requested%20a%20retry%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ACreated%20volatile%20registry%20entry%20for%20pending%20reboot%20initiated%20by%20this%20task%20sequence%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AExecuting%20command%20line%3A%20%22bcdedit.exe%22%20with%20options%20(0%2C%200)%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AProcess%20completed%20with%20exit%20code%200%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ATSUEFIDrive%3A%20%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AUpdated%20security%20on%20object%20C%3A%5C_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AUpdated%20security%20on%20object%20D%3A%5C_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AUpdated%20security%20on%20object%20C%3A%5C_SMSTaskSequence.%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20global%20environment%20variable%20_SMSTSNextInstructionPointer%3D64%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20TS%20execution%20environment%20variable%20_SMSTSNextInstructionPointer%3D64%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20global%20environment%20variable%20_SMSTSInstructionStackString%3D27%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASet%20a%20TS%20execution%20environment%20variable%20_SMSTSInstructionStackString%3D27%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0ASave%20the%20current%20environment%20block%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0AExpand%20a%20string%3A%20%25_SMSTSMDataPath%25%5CLogs%20TSManager%2019%2F06%2F2019%2018%3A55%3A24%207816%20(0x1E88)%0A_SMSTSReturnToGINA%20variable%20set%20to%3A%20%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ASMSTSUninstallCCMClient%20variable%20set%20to%20false%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0A_SMSTSCaptureMedia%20variable%20set%20to%20false%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0AThe%20action%20(Upgrade%20Operating%20System)%20initiated%20a%20reboot%20request%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ANot%20in%20SSL%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0A****************************************************************************%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0AExecution%20engine%20result%20code%3A%20Reboot%20(2)%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ATask%20Sequence%20Manager%20ServiceMain%20finished%20execution.%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ATask%20Sequence%20Manager%20execution%20terminated%20as%20system%20shutdown%20is%20in%20progress.%20Code%200x00000000%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ARegQueryValueExW%20is%20unsuccessful%20for%20Software%5CMicrosoft%5CSMS%5CTask%20Sequence%2C%20SMSTSEndProgram%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0AGetTsRegValue()%20is%20unsuccessful.%200x80070002.%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0AEnd%20program%3A%20%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0AStopping%20Task%20Sequence%20Manager%20service%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%207816%20(0x1E88)%0ARegQueryValueExW%20is%20unsuccessful%20for%20Software%5CMicrosoft%5CSMS%5CTask%20Sequence%2C%20SMSTSEndProgram%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%204588%20(0x11EC)%0AGetTsRegValue()%20is%20unsuccessful.%200x80070002.%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%204588%20(0x11EC)%0AEnd%20program%3A%20%20TSManager%2019%2F06%2F2019%2018%3A55%3A54%204588%20(0x11EC)%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F119808i0C6B7B8A9F41692D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-708858%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOperating%20System%20Deployment%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736318%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736318%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F243513%22%20target%3D%22_blank%22%3E%40Abdul%20Gafoor%3C%2FA%3E%26nbsp%3Bmost%20likely%20a%20staged%20driver%20is%20killing%20it.%26nbsp%3B%20You%20may%20want%20to%20image%20one%20with%20Windows%2010%2C%20and%20build%20the%20driver%20package%20old%20school.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fitopsreborn.com%2F2016%2F08%2Fsccm-driver-package-best-practice%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fitopsreborn.com%2F2016%2F08%2Fsccm-driver-package-best-practice%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736400%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736400%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F370060%22%20target%3D%22_blank%22%3E%40Ascent_TK%3C%2FA%3EYup%2C%20I%20thought%20of%20that.%20One%20of%20the%20driver%20is%20forcing%20this%20unplanned%20restart.%20I'll%20give%20this%20old%20school%20method%20a%20try%20and%20let%20you%20know%20the%20result.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-741417%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-741417%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F370060%22%20target%3D%22_blank%22%3E%40Ascent_TK%3C%2FA%3E%26nbsp%3BOld%20school%20method%20didn't%20help%20either.%20All%20trials%20seems%20to%20have%20been%20exhausted%20to%20find%20the%20root%20cause.%20Following%20are%20already%20tried%3B%3C%2FP%3E%3CUL%3E%3CLI%3EUsed%20latest%20OSD%20enterprise%20driver%20package%20from%20Dell%3C%2FLI%3E%3CLI%3EUsed%20the%20method%20you%20suggested%20to%20create%20driver%20package%3C%2FLI%3E%3CLI%3EDid%20update%20software%20%26amp%3B%20drivers%20to%20latest%20prior%20to%20in-place%20upgrade%20together%20with%20both%20of%20above%20points%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIt%20must%20be%20one%20of%20the%20drivers.%20Only%20solution%20left%20is%20to%20create%20a%20post%20upgrade%20task%20sequence%20for%20this%20particular%20model.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748638%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748638%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F243513%22%20target%3D%22_blank%22%3E%40Abdul%20Gafoor%3C%2FA%3E%26nbsp%3BHave%20a%20look%20at%20the%20following%20site.%26nbsp%3B%20In%20my%20experience%20the%20SMSTS.log%20file%20doesn't%20tell%20you%20much%20about%20the%20upgrade%20process.%26nbsp%3B%20Post%20logs%20if%20you%20can.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.ghacks.net%2F2018%2F02%2F06%2Fwindows-10-upgrade-log-files-list%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.ghacks.net%2F2018%2F02%2F06%2Fwindows-10-upgrade-log-files-list%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754692%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754692%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F370060%22%20target%3D%22_blank%22%3E%40Ascent_TK%3C%2FA%3E%26nbsp%3BThanks.%20I%20already%20stumbled%20on%20this%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDecided%20going%20through%20logs%20and%20finding%20out%20root%20cause%20is%20going%20to%20take%20more%20effort%20and%20time%20than%20building%20a%20post%20upgrade%20task%20sequence.%20So%2C%20created%20a%20Task%20Sequence%20only%20for%20model%20E7470%20with%20all%20tasks%2C%20which%20wouldn't%20run%20through%20original%20Task%20Sequence.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%2C%20sure%20I'm%20going%20to%20find%20out%20the%20root%20cause%20once%20project%20is%20finished%20before%20set%20date.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1444076%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1444076%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F243513%22%20target%3D%22_blank%22%3E%40Abdul%20Gafoor%3C%2FA%3E%26nbsp%3BI%20was%20wondering%20if%20you%20ever%20found%20the%20root%20cause%20to%20this%20issue.%26nbsp%3B%20I%20am%20working%20on%20an%20in%20place%20upgrade%20to%201909%20of%20Win10%20machines%20that%20have%20either%201709%2C%201803%2C%20or%201809%20installed.%26nbsp%3B%20So%20far%20I%20haven't%20seen%20many%20issues%20but%20came%20across%20one%20that%20appears%20to%20be%20the%20same%20as%20to%20what%20you%20have..%26nbsp%3B%20Just%20like%20what%20you%20saw%2C%20the%20smsts%20log%20shows%20everything%20was%20fine%20and%20states%20the%26nbsp%3BUpgrade%20Operating%20System%20step%20completed%20successfully%20but%20then%20I%20see%26nbsp%3B%22The%20action%20(Upgrade%20Operating%20System)%20requested%20a%20retry%22%20in%20the%20prior%20to%20the%20reboot.%26nbsp%3B%20The%20log%20shows%20the%20reboot%20was%20called%20but%20did%20not%20happen.%26nbsp%3B%20The%20machines%20have%20been%20rebooted%20manually%20many%20times%20since%20and%20the%20software%20center%20shows%20the%20upgrade%20TS%20is%20still%20%22installing%22%20but%20nothing%20is%20happening.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20found%20a%20cause%20for%20this%20and%20also%20what%20did%20you%20do%20for%20any%20machines%20that%20were%20stuck%20in%20this%20state%3F%26nbsp%3B%20I%20thought%20of%20excluding%20these%20machines%20from%20the%20update%20deployment%20to%20try%20and%20have%20the%20TS%20fail%20and%20disappear%20from%20the%20software%20center%2C%20then%20add%20them%20back%20to%20the%20deployment%20and%20try%20running%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452261%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452261%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F690621%22%20target%3D%22_blank%22%3E%40norcMike%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20machines%20that%20I've%20had%20the%20TS%20hang%20like%20that%2C%20I've%20got%20a%20script%20for%20clearing%20things%20out%20and%20resetting%20them.%26nbsp%3B%20I've%20put%20a%20portion%20of%20it%20on%20github%2C%20which%20should%20be%20enough%20to%20do%20what%20you're%20hoping%20to%20clear%20out%20the%20%22installing%22%20TS.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fgwblok%2Fgarytown%2Fblob%2Fmaster%2FResetTSlite.ps1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fgwblok%2Fgarytown%2Fblob%2Fmaster%2FResetTSlite.ps1%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ETypically%20I've%20seen%20this%20behavior%20when%3A%3CBR%20%2F%3EMachine%20is%20rebooted%20PRIOR%20to%20the%20first%20reboot%20created%20by%20the%20Setup%20Engine%20(End%20User%2C%20or%20other%20process%20that%20reboots%20the%20process%20while%20the%20TS%20has%20kicked%20off%20and%20the%20Setup%20Engine%20is%20in%20Phase%201.)%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you're%20using%20the%20latest%201809%20media%20and%20CM%201910%2C%20most%20of%20the%20times%20I've%20seen%20this%20have%20been%20resolved.%26nbsp%3B%20More%20details%20HERE%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.recastsoftware.com%2Fblog%2Fwindows-10-rollback-setuprollback-cmd-and-configmgr%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.recastsoftware.com%2Fblog%2Fwindows-10-rollback-setuprollback-cmd-and-configmgr%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EGood%20luck%20with%20your%20upgrades!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1452269%22%20slang%3D%22en-US%22%3ERe%3A%20Win7%20to%20Win10%201803%2F1809%20in-place%20upgrade%20Task%20Sequence%20breaks%20with%20no%20apparent%20error%20code%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1452269%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350114%22%20target%3D%22_blank%22%3E%40gwblok%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20this.%26nbsp%3B%20I%20will%20check%20this%20out%20and%20see%20what%20I%20get.%26nbsp%3B%20Incidentally%20I%20am%20using%20the%20latest%201909%20ISO%20and%20running%20SCCM%201906.%20Do%20you%20know%20or%20heard%20if%20the%20rollback%20feature%20has%20issues%20in%201909%3F%26nbsp%3B%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

We’re migrating from Win7SP1 to Win10 Ent. 1803/1809 in our corporate environment. Strange thing noticed is migration TS always breaks on Latitude E7470 after ‘Upgrade Operating System’ task. Other models (E7440, E7450, E6440, O7010, O9020, T7910, etc.) don't have such issue at large. Almost 50 nos. of E7470 is tried and all of them got the same issue. Currently migration on this particular model is on hold. Didn’t see anyone mentioning the same issue anywhere.

 

TS screenshot as well as last few lines from smsts.log is copied below. As you can see there is no error reported by the task. But a reboot is initiated somehow, which breaks Task Sequence and then it doesn’t go further. In general, what are the reasons why such error occur?!

 

Process completed with exit code 0	TSManager	19/06/2019 18:55:23	7816 (0x1E88)
!--------------------------------------------------------------------------------------------!	TSManager	19/06/2019 18:55:23	7816 (0x1E88)
Successfully completed the action (Upgrade Operating System) with the exit win32 code 0	TSManager	19/06/2019 18:55:23	7816 (0x1E88)
Not in SSL	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a global environment variable _SMSTSLastActionRetCode=0	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a global environment variable _SMSTSLastActionName=Upgrade Operating System	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a global environment variable _SMSTSLastActionSucceeded=true	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Clear local default environment	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
The action (Upgrade Operating System) requested a retry	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Created volatile registry entry for pending reboot initiated by this task sequence	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Executing command line: "bcdedit.exe" with options (0, 0)	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Process completed with exit code 0	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
TSUEFIDrive: 	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Updated security on object C:\_SMSTaskSequence.	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a global environment variable _SMSTSNextInstructionPointer=64	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a TS execution environment variable _SMSTSNextInstructionPointer=64	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a global environment variable _SMSTSInstructionStackString=27	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Set a TS execution environment variable _SMSTSInstructionStackString=27	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Save the current environment block	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
Expand a string: %_SMSTSMDataPath%\Logs	TSManager	19/06/2019 18:55:24	7816 (0x1E88)
_SMSTSReturnToGINA variable set to: 	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
SMSTSUninstallCCMClient variable set to false	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
_SMSTSCaptureMedia variable set to false	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
The action (Upgrade Operating System) initiated a reboot request	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
Not in SSL	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
****************************************************************************	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
Execution engine result code: Reboot (2)	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
Task Sequence Manager ServiceMain finished execution.	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
Task Sequence Manager execution terminated as system shutdown is in progress. Code 0x00000000	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
GetTsRegValue() is unsuccessful. 0x80070002.	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
End program: 	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
Stopping Task Sequence Manager service	TSManager	19/06/2019 18:55:54	7816 (0x1E88)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram	TSManager	19/06/2019 18:55:54	4588 (0x11EC)
GetTsRegValue() is unsuccessful. 0x80070002.	TSManager	19/06/2019 18:55:54	4588 (0x11EC)
End program: 	TSManager	19/06/2019 18:55:54	4588 (0x11EC)


Capture.PNG

8 Replies
Highlighted

@Abdul Gafoor most likely a staged driver is killing it.  You may want to image one with Windows 10, and build the driver package old school. 

 

http://itopsreborn.com/2016/08/sccm-driver-package-best-practice/

Highlighted

@Ascent_TKYup, I thought of that. One of the driver is forcing this unplanned restart. I'll give this old school method a try and let you know the result.

 

Thanks.

Highlighted

@Ascent_TK Old school method didn't help either. All trials seems to have been exhausted to find the root cause. Following are already tried;

  • Used latest OSD enterprise driver package from Dell
  • Used the method you suggested to create driver package
  • Did update software & drivers to latest prior to in-place upgrade together with both of above points

It must be one of the drivers. Only solution left is to create a post upgrade task sequence for this particular model.

Highlighted

@Abdul Gafoor Have a look at the following site.  In my experience the SMSTS.log file doesn't tell you much about the upgrade process.  Post logs if you can.  

 

https://www.ghacks.net/2018/02/06/windows-10-upgrade-log-files-list/

Highlighted

@Ascent_TK Thanks. I already stumbled on this site.

 

Decided going through logs and finding out root cause is going to take more effort and time than building a post upgrade task sequence. So, created a Task Sequence only for model E7470 with all tasks, which wouldn't run through original Task Sequence.

 

But, sure I'm going to find out the root cause once project is finished before set date. :)

Highlighted

@Abdul Gafoor I was wondering if you ever found the root cause to this issue.  I am working on an in place upgrade to 1909 of Win10 machines that have either 1709, 1803, or 1809 installed.  So far I haven't seen many issues but came across one that appears to be the same as to what you have..  Just like what you saw, the smsts log shows everything was fine and states the Upgrade Operating System step completed successfully but then I see "The action (Upgrade Operating System) requested a retry" in the prior to the reboot.  The log shows the reboot was called but did not happen.  The machines have been rebooted manually many times since and the software center shows the upgrade TS is still "installing" but nothing is happening. 

 

Have you found a cause for this and also what did you do for any machines that were stuck in this state?  I thought of excluding these machines from the update deployment to try and have the TS fail and disappear from the software center, then add them back to the deployment and try running it.

Highlighted

@norcMike 

On machines that I've had the TS hang like that, I've got a script for clearing things out and resetting them.  I've put a portion of it on github, which should be enough to do what you're hoping to clear out the "installing" TS.

https://github.com/gwblok/garytown/blob/master/ResetTSlite.ps1


Typically I've seen this behavior when:
Machine is rebooted PRIOR to the first reboot created by the Setup Engine (End User, or other process that reboots the process while the TS has kicked off and the Setup Engine is in Phase 1.)

If you're using the latest 1809 media and CM 1910, most of the times I've seen this have been resolved.  More details HERE: https://www.recastsoftware.com/blog/windows-10-rollback-setuprollback-cmd-and-configmgr

Good luck with your upgrades!

Highlighted

@gwblok 

Thanks for this.  I will check this out and see what I get.  Incidentally I am using the latest 1909 ISO and running SCCM 1906. Do you know or heard if the rollback feature has issues in 1909?  Thanks.