Create media for automated unattended install of Windows 10  

This problem seems to be even worse than initially reported.

Suppose I created an admin user in my answer file called WinUser. After sysprep is run and the reference system is rebooted, or you image the sysprped system and install Windows from that image, if you logon as WinUser (or whatever name you use), you can successfully create new user accounts that work fine.

As noted earlier, if you enable the "Administrator" account and create new user accounts while logged on as administrator, those accounts will have problems. But it gets worse. Once you enable the Administrator account and logon to the administrator account even once, from then on even accounts that you create while logged on as WinUser will be bad. Even if you you disable Administrator again, the problems will continue.

So the bottom line is that as soon as you re-enable the Administrator account and logon to it, you are dead in the water and can no longer create usable accounts.

Hey @hsehestedt and a really big thanks for all your effort. Sorry for the late answer but I had some urgent matters at work. I will try the advices that you have mentioned in the previous posts. Most probably my problem lied in enabling the Administrator account because that was the default way that I worked in the past. In my first attempts in generating the custom ISO image I did not enabled the local Administrator account through the unattend.xml file but only afterwards in the Windows Settings. As mentioned, I will do as well some testing and post my conclusions here for the community to be aware. But if the default behavior is as described above then I see it as a quite big problem. Thanks again guys for all your effort!

@Booghie, I agree with you. As it stands now, once you enable Administrator and logon even once, you will never be able to create another user account that is not defective.

BTW, I just tried this with a "regular" unattended install where sysprep is not involved and thankfully that installation was not affected by this issue.

So, I now have a question for you: Do you want to go ahead and file a report with Microsoft on this issue or should I go ahead and see if I can figure out a way to file this with them?

Hey @hsehestedt. From my side is no problem if you file the report to Microsoft. As mentioned before I will conduct some tests and post the results here but if we can inform them about this behavior and avoid such problems in the future would be awesome. Cheers!

- - - Updated - - -

Hey guys,

after some testing I can confirm the behavior described by @hsehestedt. What I have done is to crete a new unattend.xml file without the default Win10 Adminstrator account enabled. Instead, I have created a new account registered in the Administrators group and another account registered in the Users group. Then I sysprep my custom system and deployed it to another machine. The install process went without problems and both created account had none of the problems mentioned in the posts above. I've created another local user (Test1) and when I logged in everything went fine. After that I logged in with the created user admin account and enabled the default Administrator account. After logging in the default Administrator account, where everything went ok, I've created a new local user (Test2). And from this point, as you can expect, everything goes bad. The user Test 2 presents all the problems initially described in my post. As @hsehestedt mentioned, even after deactivating the local Administrator account every user account created afterwards will develop the same problems. So, without further comments, I think is safe to advice, for the moment, to not enable the default Administrator account when performing an Win10 unattended install (during or after the install). Any further problems related to this matter I will post here if its the case. For the time being I would like to thank you for the support and lets hope that this problem will be fixed in the future.

@Booghie, thanks so much for the confirmation. In the meantime, I've filed a report via Windows feedback but I don't know how much attention tat gets. I'd like to see if I can find another avenue to Windows support without having to pay for a support incident

Dear friend @Kari

I hope you be well and safe, take care yourself and try to do your immunity be higher, maybe you can do what I do, I do Autohemotherapy it improves the immunity system and helps to combat all kind of problems.

Be well and safe.

Kind Regards,
@JeepWillys58

Kari said:

Thanks, but this time the problem was prolonged balance issues, together with nausea and vertigo, all caused by Ménière's disease.

This has caused me for instance suddenly losing balance and getting hot beverage on my shirt, then panicking that and falling down. Burning skin and hurting bones.

My dear friend @Kari,

I sincerely hope my friend that you will be well and recover, regardless of what problem is affecting you at the moment, that you will be able to get through it and do even better and stronger.

Kind Regards,
@JeepWillys58