Windows 10: Windows 10 - Sysprep - Unable to use new account after sysprep

Hi everyone, I am an imaging/sysprep noob and would like some advice.

I have been trying to create an image for a network that will use multiple accounts. I edit the Admin profile in audit mode and add everything I'll need and create the image through WinPE. After I push the image out using GSS I am unable to to use a different account, I can only use the admin account I mentioned earlier on the login screen, there is no option for ''Other User''.

Do any of you have an idea why this might be and a fix? Thank you for your time.

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

Failed to sysprep and capture Windows 10 Fall Creators 1709

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh

 

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?