Forum Discussion
Win7 to Win10 1803/1809 in-place upgrade Task Sequence breaks with no apparent error code
ITOpsReborn 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.
gafoorgk 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/
ITOpsReborn 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. :-)
gafoorgk 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.
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!
