Server 2012 Essentials Set Up Windows Wizard Runs after log in

I have a virtual instance of Windows Server 2012 Essentials that, after logging in, starts the Set Up Wizard.  If I use task manager to force end the wizard, I'm taken to a the default dark blue screen background and I'm unable to do anything with the machine, no CLI, no GUI.  I see no icons or anything.

I'm using to monitor the server's status, it see that the server is rebooting and that it's running - so I'm confident that most of the rest of the server is still there, but I can't figure out what is evoking the set up wizard to run as I'm taken straight into it.  

Going into Safe Mode I tried to look at the startup stuff, I see that "startup items are not enabled on this system" and in Task Manager, where you usually find startup stuff in Windows 8 - there's no such feater in TaskManager on Server 2012.

Any thoughts on what might be evoking this and how to stop it?
Azra LyndseyNerdAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Is there a reason you aren't completing the wizard? Essentials is a specialty product and has specific technical and licensing restrictions and requirements. The wizard makes the necessary configuration changes so the technical requirements are met. It should not be closed or skipped. If you don't want essentials configured, you should not install essentials, but should instead opt for standard or datacenter.
Azra LyndseyNerdAuthor Commented:
I ran the wizard a few weeks ago when I first started working with this instance.  So I don't think I should have to run it again (do I?), it just started this behavior today.

I tried to run through the wizard but it only gives me two options to proceed forward: Either do a migration from another server, or put down a fresh install of Windows.

Cliff GaliherCommented:
That is not a choice when an installed essentials OS boots, even if the wizard was never run. That *is* a choice in the initial installation wizard launched from media. Check to make sure a bootable USB, DVD, or (or virtual equivalent id this is a VM) isn't in the server that is superseding the hard drive in boot order.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Azra LyndseyNerdAuthor Commented:
Like I said, this comes up only after I've logged in to the computer.  It starts loading stuff, then this opens.  I can get into safemode, and I see all the stuff I've done on the box - and this doesn't load.

I did check to make sure that there are no ISO, DVD drives, or USB sticks connected to the VM.  It's naked.

Anything else you can think of?
Cliff GaliherCommented:
The wizard is not copied during install. It is part of the boot.wim, or put another way, part of the WinPE environment on installation media. The files that are laid down during an OS installation are in the install.wim, and that wizard is not included in the install.wim at all. So it shouldn't even be on your hard drive, and there is no way to get it to launch even with creative startup manipulation.

What you describe about closing the wizard and not having anything in the background, not even explorer, does sound like PE through and through.  

If you are *certain* that there is no install media on the server, someone may have mangled a recovery partition. Since you can get into safe mode, I'd launch bcdedit from there and make sure the normal mode boot option is booting from the proper partition and is configured properly. If that somehow got pointed to a rogue partition, that could (oddly, but possibly) account for the problem. This includes ensuring the system isn't PXE booting another boot.wim and similar. If you use anything like WDS or similar technologies for OS deployment, someone could have uploaded a bad boot.wim and has the system booting oddly that way as well.

But essentially my "ideas" remain the same. That wizard is not running from your normal install. It simply wouldn't be present to be run. SOMETHING is grabbing you during the boot process. Either a bad BCD entry (which safe mode would not have a problem with) or some other variant on that theme.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Azra LyndseyNerdAuthor Commented:
We ever could get the server to come back to life, so something went whack, I ended up deleting the virtual install and creating a new one.

Thanks for your help!
Azra LyndseyNerdAuthor Commented:
Good info on what might be going on here, sadly, I didn't have a chance to work this all the way out before I had to move on.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.