Ran into the same issue after having a succesful 1607 task sequence for months. It does kinda have a OOBE feeling to it and I have tweaked a couple of settings such as SkipMachineOOBE but not getting anywhere! I have a feeling that there is either a patch or something like that in my build or a bug with the ADK? Does anyone else have some suggestions? It seems work fine with our Win10圆4 1703 Domain Task Sequence but not our Win10圆4 1703 Workgroup Task Sequence (it stays at Just a sec forever). Hey guys this issue has been driving me crazy the last week or so.