Windows 10: Old user still there in OOBE after sysprep and deleting it

I want to sysprep a computer before giving it as a gift. I want this since I want it to keep all the drivers already installed and everything. However, when I sysprep it using Administrator account and delette the "User" account, when I boot to OOBE, it doesn't ask me to create a new user and it's still showing me the "User" I had previously. If I go through the process, I get to the login screen and I cannot login using "User" since the account has been deleted (I was kind of locked the since there was no account at this point but I manage to fix this). Also, at the first screen of OOBE, if I do Shift-F10 and input net user in the command prompt, I do not see "User" so the user has really been deleted. Do you have any idea what's happening? How can I get the computer to sysprep and asking me for a new username at OOBE? I'm on latest version of Windows 10 on this computer. Thank you very much in advance!

:)

 

Windows 10 OOBE loop after sysprep

I ran into boot loop after sysprep Windows 10.

I've prepared a custom machine to deploy with WDS.

Sysprep has been run with /oobe/generalize options.

When I restart, windows 10 get into a reboot loop, and every time ask for system oobe wizard.

I found these on setuperr log file:

[msoobe.exe] Failed to set password and password hint with hr=0xD000006C

[msoobe.exe] Failed to create the default account with hr=0xD000006C

[msoobe.exe] TASK: End failed running task PrepareUserOOBE with hr=0xD000006C.

[msoobe.exe] Failed user OOBE prep task with hr=0xD000006C

[msoobe.exe] Failed to run OOBE Host with hr=0x80004005

[msoobe.exe] OOBE failed with hr=0x80004005

[windeploy.exe] Command [%windir%\system32\oobe\oobeldr.exe /system /quiet] failed with exit code [0x80004005]

[windeploy.exe] OnError commands failed. hr = 0x80070002

 

Windows 10 Update breaks Sysprep?

I am attempting to image a Dell E7470 with Sysprep to upload to my WDS server.

When I run Sysprep /oobe / shutdown, it completes. However, without Generalize, I won't be able to upload it or deploy it.

When I run Sysprep /oobe /generalize / shutdown, it reports that a fatal error has occurred. The setupact.log lists that the Miracastview app cannot be removed.

I have attempted the Remove-appxpackage commands, but it states that it has been provisioned for the user but not all users. It says to attempt removal with Add / Remove Windows features, but it is not listed there.

I have tried the steps in

https://support.microsoft.com/en-us...w-cause-sysprep-error-windows-10-version-1709

but none of this has worked either.

I guess the answer is to not run any Windows updates before Sysprep and avoid 1709? It appears to be bad news.

Anybody else encounter this? Any other solutions available?