Sysprep Was Unable to Validate

KB ID 0001535


While building a new Windows 10 machine to be used as a template, I ran Sysprep to generalise the installation, and got this;

Sysprep was not able to Validate

Sysprep was not able to validate your Windows Installation.
Review the log file at
%WINDIR%\System32\Sysprep\Panther\setupact.log for
details. After resolving the issue, use Sysprep to validate yout
Installation again.


What I did was Google the error, instead of looking at the log file, and read a post that said this can happen if the reference machine has not been activated, and went down a blind alley because THATS NOT TRUE of course you can generalise a newly deployed ‘non-activated’ reference machine.

When I finally read the error log, I found the following;

Package Microsoft.LanguageExperiencePacken-GB_17763.6.14.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
Failed to remove apps for the current user: 0x80073cf2
Exit code of RemoveAllApps thread was 0x3cf2.

This problem is being caused by an app, (Windows has suffered with this since Windows 8!) I’ve highlighted the app name above, yours may have a different name, but the fix is the same. We need to remove that app, and stop Windows connecting to the internet to install more app shenanigans!

Disconnect the reference machine from the internet by disconnecting its NIC, (below I’m using a VMware VM).

Disconnect Network

Run a PowerShell window, (as Administrator) and execute the following command, (obviously use the name of your offending app rather than mine if it’s different!).

Get-AppxPackage –Name *LanguageExperience* | Remove-AppxPackage

Remove App Package

Then you should be able to run Sysprep successfully. 

Sysprep Working

DON’T FORGET to reconnect the NIC if you are creating a template, once the machine has shut down.

Related Articles, References, Credits, or External Links


Author: PeteLong

Share This Post On


  1. You are a lifesaver!!!
    Thank you!!

    I had the exact same en-GB LanguageExperience pack app!
    The other weird thing is that I have the Windows Store completely disabled with reg entries, but that thing still managed to sneak in somehow!

    One thing to note – the app was in a profile that I was deleting before running sysprep, but it still caused the error.
    I had to log into that specific profile to remove it. And then go back to my local Admin to do the sysprep.

    Post a Reply
  2. Worked perfectly. Thanks so much.

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *