In case anyone else experience this issue, we seem to have a solution. Something corrupted the default user profile during the Feature Update from Build 1607 to Build 1703.
The following PowerShell commands took care of the issue:
Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache -Force -Recurse Remove-Item -Path C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache -Force -Recurse
This solves the issues for any new profiles, but profiles created after the Feature Update will need to be deleted.
This can be marked as solved now.
this only happens with Windows 10 1703 when you use “copyprofile” in unattend.xml, if so and if you want to stick with copyprofile (like me) you have to delete the mentioned folders but you miss a file that has also been deleted, let me have a look for it…
Found it back, look at this thread, what you found was mentioned before (read the complete thread!):
rd /S /Q "C:\Users\Default\AppData\LocalLow" rd /S /Q "C:\users\Default\AppData\Local\Microsoft\Windows\WebCache" rd /S /Q "C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache" del /F "C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat"
I trigger that delete lines with setupcomplete.cmd
Microsoft changed the copyprofile behaviour, you need to know how to handle it if you still use it.