Windows 10: Failure in Sysprep building install image

I am the manager of a group refurbishing computers for children and needy adults. We were doing Windows 7 until it was stopped. I am trying to build an image in Windows 10 which maintains the look and feel of the Win 7 machine. I have not made any change to anything in the Start Menu (that seems to be a guarantee of failure) and if I am violating any other rules I am missing it.

I build the image (start from Build 1607) and everything seem to be good until I do sysprep (does not seem to matter whether I use Audit mode or OOBE). The sysprep fails every time, the first warning message is always the same (dwRet = 0x2). When we finally get to the Error messages I am getting a message about Twitter not being provisioned for all users, however I have not selected Twitter in any action I have taken.

The only thing I am doing which gives me pause is that I have used a Windows 10 license s that I can do some desktop personalization which is not possible without activation. Could this be causing all my problems?

:)

 

Importing Win10 into MDT 2013

I was unable to import it using the install that was available for free download. However, I got it working with the download that I got directly from the volume licensing center.

Still having issues capturing an image with it though. Getting a failure after running Litetouch, just before the sysprep phase. I read somewhere that MDT 2013 update 1 preview isn't working with later builds of the tech preview, or the final build. Assuming
we have to wait for another MDT update.

 

Windows 10 Creators update SYSPREP

Hi! I'm building an image on Windows 10 Education Creators update 1703. And I'm having troubles with sysprep. The sysprep will run. But after a reboot it takes forever for the computer to start. It is stuck at "it's taking a bit longer than usual but it
should be ready soon". Any suggestions? Clean 1703 install with the latest windows updates. No other software is installed.

Thanks!

 

Hi Ehkaplan, welcome to Ten Forums.

First, sysprep fails far more often when done on a physical machine than when done on a virtual machine, Also sysprepping an existing Windows installation in normal mode fails more often than sysprepping a fresh, clean install of Windows in Audit Mode.

This tutorial will show you how to setup and use Hyper-V virtual machine as a technician machine to prepare a Windows 10 deployment image: Windows 10 Image - Customize in Audit Mode with Sysprep - Windows 10 Forums

A video from said tutorial:

[youtube]p9oMAGGFjCA[/youtube]

Second, Windows 10 on technician machine which is only installed for preparing a deployment image does not have to be activated in order to do the personalisations. You have some nice and easy workarounds for this.

An example: to set your personalised theme, colours, screensaver and such, use an activated Windows 10. Customise the theme and other visual aspects, apply it, right click and select Save theme for sharing:





Now simply copy the saved theme file to your unactivated Windows 10 technician machine and apply it (double click applies a theme file).

Screenshot below showing unactivated Windows, Settings app telling I would need to activate before being able to personalise, which I have worked around by bringing a theme file with background, colours, screensaver and so on from another Windows 10 machine:




All file explorer settings can be personalised also in an unactivated Windows 10.