Windows 10: Account issues when using Sysprep

So I've got a set of virtual machines i'm setting up, and I want to create a "base image" I can use to clone for each one. So, I created a new VM, installed Windows 10 Pro (unactivated), downloaded the latest updates, then ran Sysprep and told it to "Generalize" and shut down. I then copied the vhdx to a safe place for cloning.

Now, when I boot the new image, it forces me to create a new account (even though there is already an account that I created prior to generalizing). Ok, fine. I create a temp account, then promptly reboot after first login to the other account i'd setup to delete the temp account.

Here's where it gets weird. The account is a Microsoft account, and where it used to say my name (which is associated with the account), now it only shows the email address. I can't seem to find a way to get it to re-acquire the Account information.

Everything else I've used seems to work otherwise, but this one glitch is mildly annoying. Is there any way to skip forced account creation after generalizing? Or alternatively, delete the account automatically when shutting down after generalizing?

:)

 

IE11 Pages not responding after Sysprep, Copyprofile=True, Windows 10 Ent 64

After running Sysprep on a Windows 10 64-bit Enterprise Build 1511 PC, Internet Explorer 11 will not load certain web sites from within a user account (admin rights) without generating a
Page Not Responding error, hanging up, and sending an error report. However if your open IE11 "Run as Administrator" the pages WILL load, therefore IE can only be opened and used in this manner. When Sysprep is run the setting to copy the Administrator Profile
to the Default user profile is turned ON (which we need) and this seems to be what is causing the issue. Everything works normally before Sysprep is run, even on standard user accounts. However this has not always been the case, so we need a solution to restore
IE11 functionality to these systems while still allowing them to be sysprepped with the correct profile settings applied.

 

Windows 10 1607 OOBE Password Hint something went wrong.

I have just installed Windows10 x64 1607 Education with all updates installed onto Hyper-V.

I cleaned up the build by removing the bloat ware and SYSPREP. No Third party Apps installed.

Now when I have turned the VM back on from the SYSPREP I am stuck on Create an account screen.

I have tried adding a new user with out a password. Something Went Wrong (Under Password Hint.)

Added Username + Password + Hint. Something Went Wrong (Under Password Hint.)

Removed the NIC from Hyper-V. No Help

Run SFC /Scannow before sysprep found no issues.

Run Chkdsk before sysprep no issue.

Still stuck at this screen.

Any ideas?

 

When sysprepping, you must tell it with a switch if next boot will be OOBE (/oobe) or Audit Mode (/audit). In your case, using /oobe switch, Windows will go through normal setup including the initial admin user creation. There's no way around it.

A suggestion: It is not a good idea to just install Windows normally going through OOBE, creating a user account (irrelevant if local or MS) and then run sysprep on normal mode. You should rather install Windows on your technician vm but instead of going through OOBE, boot to Audit Mode from the Settings dialog after the last reboot of installation.

To do this press CTRL + SHIFT + F3 when Settings dialog is shown:





Audit Mode will boot using built-in admin, no user accounts exists yet. Do your customizations, update Windows, install software, then run sysprep with /generalize and /oobe switches. Notice that if updating in Audit Mode and Windows requires a restart to apply updates, it will automatically return to Audit Mode. You can only exit to normal mode by using the /oobe switch with sysprep command.

Now you have two choices:

• Create image when machine is shut down after successful sysprep, alternatively copy the VHD to safe place. When the image is then restored to new machines, or VHD used for new virtual machines, it's a fresh new install which starts from OOBE without any existing user accounts
  -- OR --
• Restart the technician vm and go through OOBE creating your initial user, then make an image or copy the VHD.

See the tutorial: Windows 10 Image - Customize in Audit Mode with Sysprep - Windows 10 Forums. Just a few days ago I added a new video to show how well this works with version 1607, see this post.

 

When I see high-quality answers such as Kari's post, I will use a screen capture tool [if pics are embedded] to create a jpg, or, copyNpaste [if only text] into a text file -- and save such valuable advice onto my hard-drive.

 

Roland, you made me smile! Thanks *Smile

 

Thanks Kari, great information. However, I don't think you have to use a switch. If you just run Sysprep, there's a drop down to select OOBE/Audit and a checkbox for Generalize, and whether to shutdown or reboot.

The switch just avoids the GUI, AFAIK.

 

Of course you have to use switches, the Sysprep GUI just inserts those without you needing to type them.

Examples.

If these selections were chosen in Sysprep GUI...




... sysprep command would be run with these three switches (highlighted):




If these selections were chosen in Sysprep GUI...




... sysprep command would be run with this one switch (highlighted)




Because Shutdown is default behaviour, if no Shutdown option / switch is given as in above command example Windows will shut down when finished, next boot being to Audit Mode.

My point is, Sysprep GUI is only a tool to set command switches and then run the command.

In addition, using Sysprep GUI you have to name your answer file (if one is used) exactly as unattend.xml and save it to C:\Windows\System32\Sysprep folder. If it has any other name or is not saved on that specific folder, it will be ignored.

Using command line instead the answer file can be named as you wish (with .xml extension) and saved wherever you want to, its location told with /unattend switch.

Example sysprep command with freely named answer file:

 

You just said the same thing I did, but yet tried to argue about it....

 

Don't want to start an argument but this is what you said:

That statement is absolutely completely not true and invalid. Sysprep command needs switches, minimum requirement being the startup option switch either /oobe or /audit.

You have a funny way to take it when you are corrected. I repeat: your statement about Sysprep not needing switches is BS not true. To sysprep you need to use at least one switch, it's irrelevant if you enter required switch(es) using GUI or command line.

 

You are impossible to deal with.

Saying "you must use the switch" means you must specify the switch on the command line. You do NOT need to specify the switch on the command line is my only point. Running it without switches lets you choose the options from the GUI without command line switches. Why is that so hard to understand?

 

I must apologize, my previous post in this thread came out too strong, too aggressive. I have no excuse for that, and although not wanting to delete or edit the post in question I feel I have to say I am sorry for my behaviour.

I hope a short explanation is allowed.

I am a fanatic Sysprep fan. I totally love what it offers, what kind of magic I can do with it. I wrote my first Sysprep related tutorial back on our sister site the Seven Forums almost seven years ago, have been really concentrated in trying to get normal average users to find Sysprep and its possibilities.

A difficult person as I am, with even more difficult personality, I take all misconceptions or wrong interpretations of a topic this close to my heart as a personal insult. Of course I know it's wrong, but knowing it is wrong does not change how I react due faults in my personality: too impulsive, too fast, too aggressive.

The above explanation is in no way meant to be taken as "I had right to post what I did". It is simply a short explanation why I reacted so strong. I am sorry and my apology is sincere.

A very sincere

 

I appreciate the apology Kari, and I want to make sure you understand that I greatly appreciated (and continue to Appreciate) your knowledge and skill on this and other topics.

I also do not mean to come off as saying "you're wrong", and do not mean to insult you (although I seem to have a knack for unintentionally doing so). Please do not take my comments to be insults, I just like to make sure the information is as correct and complete as possible.

 

We are good as far as I'm concerned. My temper and exaggerated passion for this topic makes me behave as an idiot.