UPGRADE SEQUENCE 1709 WINDOWS 10

[kcumbie8]

I'M wondering if anyone has had success in using  the Upgrade task sequence   in in SCCM CB 1710 to upgrade  From  Windows 10 1607 to  Windows 10 1709   I haven't been able to do Successful Upgrade test  when   it rolls back.. On side note i haven't been able to successfully update my home computers without doing a wipe and load from 1703 to 1709 using the Creators tool   Anyone know of any issues . With 1709 upgrade

 

 

 

 

[Jorgen Nilsson]

Hi,

there have been som issues with 802.1x and ue-v when going from 1607-1709 but nothing major.

Regards,

JÖrgen

[anyweb]

the upgrades from 1703 to 1709 for me (in testing) have gone without a hitch, however... after the upgrade is done and after one or two reboots we've witnessed a white spinning circle of dots which never completes, it just stays there, we've seen this on Surface Pro 4 and HP X360 g2 and as of yet have not identified the cause, once we figure it out i'll post an update here.

[kcumbie8]

I'll  Run another upgrade test again and gather SMTS  logs etc.  from my upgrade  test  this weekend and post here as well.

I Enclosed the SMSTS.log from  the upgrade sequence . I believe this might be a issue with windows update agent looks like the error is 0xC1900204.  though i tried to run though the steps to fix to correct that  error and got the same results . 

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/receiving-error-0xc1900204-when-attempting-to/1b419f97-d5f1-4826-bf45-8c552291dbc6

Still fiddling around with it . 

 

smsts.log 

Edited December 4, 2017 by kcumbie8
correct spelling

[mhd]

@anyweb, don't know if you're still having the spinning circle issue, but if so, this might resolve it:

http://www.thesccm.com/fix-windows-10-in-place-upgrade-task-sequence-infinity-restart-loop/

Having my own struggle w/ 1709 in-place upgrade so appreciate hearing any issues others have worked through. 

[anyweb]

interesting and thanks for sharing but we found out the issue, it's related to DMA as described in these links, so a GPP will solve it for now

https://blogs.technet.microsoft.com/secguide/2018/01/18/issue-with-bitlockerdma-setting-in-windows-10-fall-creators-update-v1709/

https://support.microsoft.com/en-gb/help/4057300/devices-not-working-before-log-on-a-computer-running-windows-10-1709