Sysprep HyperV Windows 2008 R2 server - error on startup

I made a sysprep image a Windows 2008 R2 server running on a HyperV host. I selecteed the options 'Enter System Out-of-Box Experience (OOBE), Generlize option is checked, and shutdown options is set to Shutdown.

When I go to boot up the Virtual machine that was sysprep, I get an error during the Windows boot process 'Windows could not fnish configuration the system. To attemp to resume configuration, restart the computer'. A restart does not fix the issue.

How do I get a sysprep to work when having the generlize option? I tired an export from the hyperV manager as well as a clone from VMM but the same error occurs.
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.


Kindly check the line

you need to remove any network before running sysprep.
gregurlAuthor Commented:
I remove the network and performed another sysprep and the error still occurred on startup..
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

gregurlAuthor Commented:
I have not changed the SID. I thought that is what the 'Generalize' option for the sysprep is supposed to do when making the sysprep image. I have done the newsid application in the past but I have read some applications like Sharepoint errors can occur with using newsid,.
Could you provide us more info on configuration of VM in Hyper V
gregurlAuthor Commented:
After some search, it seems the Daemon tools used to mount a CD /DVD could cause an issue. I uninstalled the software but the error still occurs.

I looked in the registry and the \HKLM\System\CurrentControlSet\services\sptd\cfg has some issue getting permissions to view the registry kety to delete or change permissions. I try to take ownership of the key under the adminstrators account to delete the key before a sysprep, but I cannot take control of this key.
gregurlAuthor Commented:
The final solution was to create a new image and not install the Daemon tools that caused the registry key permissions issues after sysprep.

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
gregurlAuthor Commented:
The removal of the Daemon tools fix the isssue with teh sysprep install.
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

From novice to tech pro — start learning today.