Windows 10: The Virtual Desktop is not Sysprep generalized

​

When deploying a Windows image over Hyper-V or creating a new VDI, you might have encountered an error that says The virtual desktop is not Sysprep generalized. This can be slightly confusing for someone who doesn’t know what Sysprep is and how they can resolve this issue. Following is the exact error message we see. […]

This article The Virtual Desktop is not Sysprep generalized first appeared on TheWindowsClub.com.

read more...

 

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.

 

Making Windows Image Without Sysprep Generalize tools, is Wrong?

Dear Microsoft team

I have a question about Windows Image, if i took Windows Image Without Sysprep (Generalize) tools, I installed all apps and Restated machine and took image with Acronis , and Restored this image in others machines, is this steps Wrong ?

Should I make Sysprep (Generalize) ??

Best Regards,

Hany Barbis

 

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

MiracastView cause sysprep error in Windows 10 Version 1709 - Windows Client

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?