oh I misunderstood then, anyway I just tried to deploy the image myself. I used dism to deploy from the setup dvd. I booted from the dvd, then just before doing anything at all I pressed shift+F10 to open the cmd prompt and from there I deployed the image on the drive, then I ejected the dvd and rebooted the system, the final configuration worked fine and.. guess what. defaultuser0 it's right there . So I don't know if it depends on the PC (the first time I noticed it I was installing it into vmware, but now I tried on a samsung notebook) or on the ISO itself (I'm using an Italian version of win10 1607 x64 downloaded directly from MS website), but I still got it XD
"defaultuser0" is created to run the user portion of OOBE, so it's not in the original image. As everything OOBE-related, creation of the account is logged in %windir%\panther\unattendgc\setupact.log. I suppose it may be possible to skip it using SkipUserOOBE, but you'd have to use unattended settings to create a user account or enable "Administrator" yourself.
Unfortunately I need OOBE to run some scripts I added in the $oem$ folder. I just cannot understand why some users doesn't have this problem, I guess I'll just have to live with it
"oobeSystem" pass would still run. Pretty sure FirstLogonCommands and setupcomplete.cmd would run as well.
Yes, my Acer laptop detected and downloaded the update, took a while for the entire process, downloading and installing.. So the 1607 is now on Windows Update also... Planning to put my Dell and Lenovo Laptops on update tonight, speed seems good on Windows Update route compare to my nightmare with ISO download from MS Tech Bench server ISO downloading links..
On my PC my Windows 10 x64 1607 14393.67 keeps failing to install a update (KB3176934) with using WU and manual install. I don't have any internet security programs installed. I'm only using Windows Defender
*ttp://download.windowsupdate.com/d/msdownload/update/software/crup/2016/08/windows10.0-kb3176934-x86_607fd89d8c53912ec6bc6d594e43a9f3e8172654.cab *ttp://download.windowsupdate.com/d/msdownload/update/software/crup/2016/08/windows10.0-kb3176934-x64_5eedcc98de283d69a008c7cfe63df0d5a7bedb8c.cab *ttp://download.windowsupdate.com/c/msdownload/update/software/crup/2016/08/windows10.0-kb3176934-x86_7a0bfab3a61d3b4823a52177f1153ce7a62927e3.msu *ttp://download.windowsupdate.com/d/msdownload/update/software/crup/2016/08/windows10.0-kb3176934-x64_5e7bc3013384454c32a4fa59c7879367b93f6e86.msu
it is because his post count does not allow him to post the link (http://) so he posted broken link hence h is replaced with "*".
Ok interesting. I took time to fully read the forum rules. I never knew a person had to have a minimum of 10 posts to put links up.
My Dell Laptop running Core i3 and Windows 10 1511 x64 is still not detecting the the 1607 via WU.. Where as My Acer Laptop detected and installed the update few days ago.. I wonder what is wrong, as I have no deferred any update from settings..