This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I have built a Windows 10 Enterprise v1809 and 21H2 image from the ground up following Microsoft best practice but have hit a wall. Installed Windows using autounattend.xml file, customized the image with the auto logged in administrator account and ran sysprep. The problem is, after deploying the image there are two administrator profiles in the users dir, Administrator (which is empty) and Administrator.computername (populated with the typical Documents, Downloads, Desktop etc directory's). Trying to understand what is causing this. Can provide unattend and autounattend files for review. Wondering if anyone has experienced this issue recently? Any and all input on this issue would be appreciated.
Thanks,
Mary