questions about sysprep

Sysprep is always best to do in Audit Mode. See these tutorials for a correct method to customize a Windows image, sysprep and capture it:

• Create media for automated unattended install of Windows 10
• Microsoft Deployment Toolkit - Easy and Fast Windows Deployment
• Create Windows 10 ISO image from Existing Installation

Kari

Generalizing with Sysprep fails, if app provisioning is done wrong. This causes the most errors users get when sysprepping.

The issue is not the user, nor Sysprep. The issue is that as Microsoft allowed UWP apps to run in built-in admin account in Windows 10 version 1709, and because of that, Store apps might update in the background. This causes updated apps to be provisioned, and often leads to Sysprep error.

An easy workaround is to install Windows 10 on reference machine without network connection, boot to Audit Mode, open Command prompt and run this command:

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore /v AutoDownload /t REG_DWORD /d 2 /f

This adds a key and a DWORD in registry, preventing Store apps from updating. Now connect reference machine to network, do your customizations, and when ready, last thing before sysprepping, run the following command to re-enable app updates:

reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore /v AutoDownload /f

That's it.


Having said that, now a personal, very subjective opinion:

Eileen3626 said:

You'd better use Audit Mode to have a try! Before running Sysprep in Windows 10, you should pay attention to its limitations, for instance, Sysprep may fail if you install or update Microsoft Store apps before generalizing a system image.

First, a bit background.

I am a devoted fan of Ten Forums and its sister sites, Vista Forums, Seven Forums and Eight Forums. I will have my 10th anniversary on these forums in couple of weeks.

Because the forums are so important to me and close to my heart, I would first like to thank you, and any other representative from any other software manufacturer who joins us to offer assistance for their products. Being a mere mortal member, I have no say in this, but I am sure our owner @z3r010 also appreciates it.

However, trying to mask your replies as posts from another user who managed to do something with a specific product, "forgetting" to mention that you in fact work for the manufacturer of that product, it's not cool. Like now, you "forgot" to mention that you have written that post you linked to, and the purpose of that post is to market your product.

I especially disliked this post of yours:

Eileen3626 said:

I formatted bootable SD card last week. It was very successful. Maybe you can try the utility mentioned in this tutorial.

You made the post to look as if a user (you) had got an issue fixed or something done with a specific tool, "forgetting" to mention that you yourself had written that "tutorial" to market a product of your employer. As a member here, I would like to see you to mention that in your future posts.

Respectfully,
Kari