SOLVED: Sysprep was not able to validate your Windows installation, when run on Windows 11.

When you try and run Sysprep before imaging Windows 10 or Windows 11 you may see the error 

Sysprep was not able to validate your Windows installation.


You are told to check the log


Checking the log shows an error similar to this



SYSPRP Package Microsoft.OneDriveSync_21196.921.7.0_neutral__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

SYSPRP Failed to remove apps for the current user: 0x80073cf2.

SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.


 While you're here -
Why not check out our Windows Server Documentation and Audit Tool?


This is because Windows store apps - more information can be found here
https://docs.microsoft.com/en-US/troubleshoot/windows-client/deployment/sysprep-fails-remove-or-update-store-apps

The code in the Microsoft article isn't very clear, instead this script should help.

You can add additional packages if SysPrep fails with another package.

Clear-Host
$packages = @('*Microsoft.BingNews*','*Microsoft.OneDriveSync*', '*Copilot*', '*Microsoft.Ink.Handwriting*')
foreach ($package in $packages)
{    
    Write-Host "Removing: $($package)";
    Get-AppxPackage -AllUsers $package | Remove-AppxPackage -AllUsers;
    Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like $package} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
}




You may also see this issue
2025-10-09 16:19:42, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll; dwRet = 0x80310039[gle=0x00000001]

Running the following command shows that Bitlocker is enabled on the system (C:) drive and the drive is encrypted.
Get-BitLockerVolume -MountPoint "C:"

You need to decrypt the system drive before running Sysprep - this can be done with the following command.
Disable-BitLocker -MountPoint "C:"


 While you're here -
Why not check out our Windows Server Documentation and Audit Tool?

Comments

Post a Comment

Popular posts from this blog

SOLVED: Exchange Online Management PowerShell Connect-ExchangeOnline bug "A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles"

Image
While you're here why not check out our  Exchange audit and documentation tool ? If you're using the Exchange Online Management PowerShell cmdlets you may notice that the following error: A window handle must be configured. See https://aka.ms/msal-net-wam#parent-window-handles This error appears in version 3.7.0 (and persists in version 3.7.1) when the following change was made. Integrated WAM (Web Account Manager) in Authentication flows to enhance security. You notice that this error occurs in PowerShell ISE but not in a PowerShell, the issue also appears in any Windows based applications - for example a WinForms application that tries to execute Connect-ExchangeOnline PowerShell ISE A .NET console application does work correctly. .NET console application While you're here why not check out our  Exchange audit and documentation tool ? The error occurs because Microsoft has made the (correct) decision that when an interactive login prompt it must have a parent window so t...
Read more

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

get-windowsfeature : The given key was not present in the dictionary

Image
When you run the get-windowsfeature cmdlet in PowerShell on Windows Server 2012 you may see the following error get-windowsfeature : The given key was not present in the dictionary. At line:1 char:1 + get-windowsfeature + ~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (:) [Get-WindowsFeature], KeyNotFoundException     + FullyQualifiedErrorId : System.Collections.Generic.KeyNotFoundException,Microsoft.Windows.ServerManager.Commands    .GetWindowsFeatureCommand This seems to occur if there is a problem in the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager\ServicingStorage\ServerComponentCache As this is just a cache registry key you can try renaming the key to ServerComponentCache.old and then re-running the PowerShell command or refreshing the view in server manager. This recreates the key and rebuilds the server feature information. - While yo...
Read more