Forum Discussion
Win7 to Win10 1803/1809 in-place upgrade Task Sequence breaks with no apparent error code
gafoorgk 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/
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.
- ITOpsRebornJul 10, 2019Copper Contributor
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/
- gafoorgkJul 15, 2019Copper Contributor
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. :-)
- norcMikeJun 05, 2020Copper Contributor
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.