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.
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. :-)
ITOpsRebornYup, 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.
