Customization Specification for Windows does not join VM to domain
search cancel

Customization Specification for Windows does not join VM to domain


Article ID: 342874


Updated On:


VMware vCenter Server VMware vSphere ESXi


Customization Specification for Windows does not join VM to domain.
Sysprep will fail 

2021-01-14 09:14:27, Error                 SYSPRP Package Microsoft.PPIProject_10.0.17134.1_neutral_neutral_Cw5n1h2txyewy was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2021-01-14 09:14:27, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2021-01-14 09:14:27, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2021-01-14 09:14:27, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2021-01-14 09:14:27, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2021-01-14 09:14:27, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2021-01-14 09:14:27, Error      [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2021-01-14 09:14:27, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2


VMware vSphere ESXi 7.0.0
VMware vSphere ESXi 6.7
VMware vCenter Server 6.7.x
VMware vCenter Server 7.0.x


This is not a VMware problem, windows OS has few package which need to be removed from the OS, the package need to be removed as, it may be older version or it may be depreciated package exists in the OS.


Before starting this procedure download the core files from

In this example used the log snip of Windows 10 Ent build 2004, the logs are located at  C:\Windows\System32\Sysprep\Panther\setuperr.log and it is complaining about number of package: one of the package has been shown here, you might need to repeat thee same procedure for all the complaint packages.
Check in the existing package list, few of the packages might be depreciated from the vendor or the package contains old version so we need to remove it.  The value of the package need to unflag from the protected list ‘0’. If the value is 1 this means it is protected and cannot be removed.

Follow below steps to update the package value to zero. The protected flag need to removed before removing the package.
Create a file with any user friendly name and append the list of the package name,  if you have list of packages name handy then add all packages name at once or else add one package at a time.

example file: removePPi.txt (use any friendly name)

You just need to match the pattern and it’s not mandatory to add the complete package name. Once it is completed open the batch file (Open AppxDBEditor.cmd) Which you have downloaded earlier.

Select the option #2 in the following page input the package which you need to exclude

Once successful, select M to modify the list while selecting the Y to confirm, wait for a moment. Once completed select D to Dump the package list.

Option D will create a file ‘AppxPackageDump.txt’

Upon opening the file the package which was complaining now it will have the value ‘0’

Now the protected flag has been removed, now using the power shell, remove the package.

1. In the powerShell run below commands 

  • Import-Module Appx
  • Import-Module Dism
  • cd ..\..\Windows\System32\
2. Remove the package from the power shell using the below command
  • Remove-AppxPackage -AllUsers -Package Microsoft.PPIProject_10.0.17134.1_neutral_neutral_Cw5n1h2txyewy -verbose

3. Once the package has been removed run the sysprep from the command line.

C: Windows\System32\Sysprep> sysprep

If the sysprep fails, then redo the same activity, identify the package which is causing the problem, update the protected flag for the package and then remove the package from the power-shell. 

If Sysprep was not successful, you need to review the setuperr.log file and repeat these same procedures multiple times for all the different  .appx packages that might show up in setuperr.log. Once you have successfully removed all the .appx UWP packages that Sysprep is complaining about, Vmware Customization Specification will work successfully in vCenter.

If you still have a problem, it is advised to contact your OS vendor.