Deploying Windows 10 1703 from SCCm

[jfarmer]

Has anybody seen this yet when deploying 1703 from SCCM? It seems to go through the TS fine but gets to here and when I press Next, it just keeps looping...

SCCM is on 1702 and I haven't made any other changes to my TS.

[Master-VodaWagner]

Yes, I've encountered this when I attempted 1703 but went back to 1607 for now

[jfarmer]

It's something to do with Group Policy, not sure which one yet but I'm working on it.

[jfarmer]

Right, managed to sort it. I had the 'Block launching Windows Store apps with Windows Runtime API access from hosted content' enabled in Group Policy. Set it to 'Not Configured' and got it working.

[Master-VodaWagner]

bit of a bummer if the organisation wants to block the windows store....

[thegood1]

Did u check if internet is available on the machine ?

 

Also what do u meant u have not done any changes to TS ?

 

Someone said group policies applied does  in this stage group policies setup to applied or not in the task sequence day blocking store n internet etc ? 

 

[jklight]

i was getting this message too but it went away when i added the new admx files to the domain.

Edit:

Spoke too soon.  It made it to the logon screen and i entered credentials and then... same message "Why did my PC restart"

Restarted and got "just a moment" message for 15 min then restarted and... "Why did my PC restart"

i will try this: https://www.windowsmanagementexperts.com/osd-issue-with-windows-10-1703/osd-issue-with-windows-10-1703.htm next

 

Edited June 1, 2017 by jklight
correction

[Hotzenwalder]

The solution mentioned here ( https://www.windowsmanagementexperts.com/osd-issue-with-windows-10-1703/osd-issue-with-windows-10-1703.htm ) worked for me. Didn't even need the extra restart anymore

 

[jklight]

Just an update... i no longer have the problem after i updated to the latest ADK and MDT and rebuilt the task sequence.  I also added the skipmachineOOBE true and skipuserOOBE true to the unattend.xml