Windows 10: defaultuser0 profile created windows 10 1703 after sysprep

anyone get defaultuser0 profile created and windows license not activated after ran sysprep in task sequence?
1. create VM and work on built-in administrator and ensure only standard built-in administrator, disabled DefaultAccount and disabled guest account is there by command net user before sysprep in windows 10 1703 enterprise.
2. below link is my answer unattend.xml file used in task sequence
https://www.dropbox.com/s/luvbgyl1v1...ttend.xml?dl=0

3. after task sequence finished, login to domain account and saw disabled account named defaultuser0 and its profile created and windows license not activated.
anyone has similar issue or i did something wrong? because i also did the same for build 1607 and does not encounter the same issue. any help is appreciated.

:)

 

"defaultuser0" created on clean install of Anniversary Update

i also has the defaultuser0 in c:\users\. i am using the windows 10 1703 iso from VLSC and create golden image in VM and the golden image does not have defaultuser0 profile before i sysprep

after sysprep, and deploy in TS and login, i see defaultuser0 in c:\users\

 

"defaultuser0" created on clean install of Anniversary Update

I'm not sure if this is entirely the same situation, but it seems to me that the defaultuser0 isn't "mistakenly added". I'm rather under the impression that it was "mistakenly not deleted" when finishing the setup of an unattended install (in my case), because
I just did a clean install of Windows 10 pro 1703 with WDS/MDT, and during final MDT phases this "defaultuser0" profile is visible on this PC.

The MDT failed because of an error on my part (I'm playing around with running MDT phases under another user profile than the default local administrator), so the setup wasn't finished, but the user is still there.

UPDATE: The user seems to be removed after setup op 1703, before MDT applies Windows updates.