Running Sysprep errors out and points to setupact file

sadi · 31 Jan 2017

Hello,

I am trying to create a Windows 10 image using an unattend file and sysprep. When I run the command below:

sysprep.exe /oobe /generalize /unattend:c:\windows\system32\sysprep\unattend.xml

After which I get an error message prompting me that sysprep was unable to validate my Windows installation and to look at a log file located in the sysprep\panther folder.

There are a few error lines I am unfamiliar with, any ideas on what I may need to fix? Attached are both the log file and the unattend answer file I created.

Kari · 31 Jan 2017

Hi Sadi. welcome to Ten Forums.

Which version (or build) and edition of Windows 10 you are trying to sysprep? Are you running sysprep after a clean install in Audit Mode, or later on an existing Windows 10 installation?

Kari

cereberus · 31 Jan 2017

Sysprep does not like uwp apps that a user downloads (default ones preinstalled are ok).

In this case it is candycrushsodasaga that is the issue (look at text in log file). So basically uninstall it before sysprepping.

Unfortunately, it then tends to bomb out with similar error in next package and you have to delete that and so on.

I would uninstall all uwp apps that you can upfront to avoid repetition.

sadi · 31 Jan 2017

Kari said:

Hi Sadi. welcome to Ten Forums.

Which version (or build) and edition of Windows 10 you are trying to sysprep? Are you running sysprep after a clean install in Audit Mode, or later on an existing Windows 10 installation?

Kari

Hi Kari,

This is Windows 10 Pro, version 10.0.10586 Build 10586. I installed Windows 10 clean from the installation disk that came with the machine, we bulk order HP 840 with Windows 7 pre-installed but they come Windows 10 ready with a license. I am pretty sure that sysprep was run in Audit mode as I was unable to open certain applications such as Edge (despite me not using the keyboard shortcut during the setup screen to boot into Audit mode).

sadi · 31 Jan 2017

cereberus said:

Sysprep does not like uwp apps that a user downloads (default ones preinstalled are ok).

In this case it is candycrushsodasaga that is the issue (look at text in log file). So basically uninstall it before sysprepping.

Unfortunately, it then tends to bomb out with similar error in next package and you have to delete that and so on.

I would uninstall all uwp apps that you can upfront to avoid repetition.

I did a clean install so I was surprised to see candycrush on there, I made sure the application was not on the device before running sysprep and tried to find the file you saw in the logs, but there was no trace of it, so I am not sure where that file is being referenced. I tried to go through the other error lines as well but I do not really understand what they are pointing to as an issue since they seem to just lead to the generalize.xml file found in C:/Windows/System32/Sysprep/ActionFiles

cereberus · 31 Jan 2017

You may have to use powershell commands to remove stuff - see tutorials section.

Kari · 31 Jan 2017

sadi said:

This is Windows 10 Pro, version 10.0.10586 Build 10586. I installed Windows 10 clean from the installation disk that came with the machine, we bulk order HP 840 with Windows 7 pre-installed but they come Windows 10 ready with a license. I am pretty sure that sysprep was run in Audit mode as I was unable to open certain applications such as Edge (despite me not using the keyboard shortcut during the setup screen to boot into Audit mode).

OK, I think that explains it.

To start with, you of course know that Windows 10 version 1511 (build 10586) is already over 18 months old and honestly, you shouldn't use (and there really are no good reasons to use) it anymore to make your deployment image. The current branch and version is 1607 (build 14393) from August 2nd 2016. That's the version you should use.

Next, if you did not specifically boot to Audit Mode with CTRL + SHIFT + F3 from OOBE regional settings dialog, you most definitely were not in Audit Mode. Instead you have installed Windows normally and then used built-in admin account in normal mode to customize and Sysprep. This explains why Edge and other UWP apps did not work; they are disabled when using built-in admin account both in normal and Audit Mode, Settings app being only exception.

That being said, if you insist doing this using v. 1511, it had several issues with Sysprep. One was that you had to install it on a technician machine without network connection: on technician machine, unplug Ethernet cable, turn PC on and install until OOBE regional settings dialog, boot to Audit Mode and only then plug Ethernet cable back in and connect to Internet.

This prevents Windows provisioning UWP apps too early and allows you to run Sysprep.

sadi said:

I did a clean install so I was surprised to see candycrush on there, I made sure the application was not on the device before running sysprep and tried to find the file you saw in the logs, but there was no trace of it, so I am not sure where that file is being referenced.

In v.1511 Candy Crush Saga was not preinstalled per se but it was one of those recommendations Windows showed after first boot to desktop. As it was not properly installed it was also hard to get rid of.

It is preventing you to run Sysprep because of the reasons told above: You have installed Windows normally and sysprepped in normal mode (or entered Audit Mode later on when OOBE was already completed), not as it should be done with v.1511 installing Windows without network connection until in Audit Mode, connecting network, customizing and sysprepping.

Kari

sadi · 31 Jan 2017

Kari said:

OK, I think that explains it.

To start with, you of course know that Windows 10 version 1511 (build 10586) is already over 18 months old and honestly, you shouldn't use (and there really are no good reasons to use) it anymore to make your deployment image. The current branch and version is 1607 (build 14393) from August 2nd 2016. That's the version you should use.

Next, if you did not specifically boot to Audit Mode with CTRL + SHIFT + F3 from OOBE regional settings dialog, you most definitely were not in Audit Mode. Instead you have installed Windows normally and then used built-in admin account in normal mode to customize and Sysprep. This explains why Edge and other UWP apps did not work; they are disabled when using built-in admin account both in normal and Audit Mode, Settings app being only exception.

That being said, if you insist doing this using v. 1511, it had several issues with Sysprep. One was that you had to install it on a technician machine without network connection: on technician machine, unplug Ethernet cable, turn PC on and install until OOBE regional settings dialog, boot to Audit Mode and only then plug Ethernet cable back in and connect to Internet.

This prevents Windows provisioning UWP apps too early and allows you to run Sysprep.

In v.1511 Candy Crush Saga was not preinstalled per se but it was one of those recommendations Windows showed after first boot to desktop. As it was not properly installed it was also hard to get rid of.

It is preventing you to run Sysprep because of the reasons told above: You have installed Windows normally and sysprepped in normal mode (or entered Audit Mode later on when*OOBE was completed), not as it should be done with v.1511 installing Windows without network connection until in Audit Mode, connecting network, customizing and sysprepping.

Kari

Ah, I see, I will create a bootable usb with the latest build then and try it again. Is it best to create and sysprep the image through Audit mode? I did watch your videos where you created an image on a VM using it, but this was my first time working on Windows 10 and imaging in general so I was trying to find the simplest way to do it using whatever media came with the device. Either way, I will update when I get a chance to try this tomorrow and hopefully will have better results.

Thanks!

Kari · 31 Jan 2017

sadi said:

Ah, I see, I will create a bootable usb with the latest build then and try it again. Is it best to create and sysprep the image through Audit mode? I did watch your videos where you created an image on a VM using it, but this was my first time working on Windows 10 and imaging in general so I was trying to find the simplest way to do it using whatever media came with the device. Either way, I will update when I get a chance to try this tomorrow and hopefully will have better results.

Thanks!

I try to avoid using words "correct procedure"; every time I do so some other geek feels it important to split hairs and posts something like "I've always done it like this, not like as you tell"

So, I am not telling the correct way to do this, I am just telling how I am doing image creation having always managed it without any issues. I'll list work flow in about right chronological order:

Be sure your technician machine has no Internet connection
Install Windows 10 normally until after last reboot the Regional Settings dialog is shown, press CTRL + SHIFT + F3 to reboot to Audit Mode
In Audit Mode desktop, connect machine to network and Internet
Install your software & additional features (for instance language packs), restart if an installer requires it; as long as you do not specifically tell Windows to exit Audit Mode, Windows returns to Audit Mode after restart
Customize Windows as you wish
Run Sysprep with /generalize and /oobe switches & your custom answer file (/generalize switch only required if default profile customizations have been done, it also requires COPYPROFILE component in answer file to be set TRUE)
Capture image
Deploy

Kari