Fix “Sysprep was not able to validate” Error on Windows 11/10

fix Sysprep was not able to validate

SysPrep is a useful feature that allows the cloning of the current Windows OS to multiple PCs. Many users have complained about receiving an error message, “Sysprep was not able to validate your Windows Installation”. After this error message it closes and does not create any copy of the current Windows OS. In this fixing guide, we are going to resolve this issue on your Windows 11 and Windows 10 PCs.

fix Sysprep was not able to validate
Sysprep error message

What is Sysprep?

Sysprep is a Microsoft System Preparation tool used to duplicate, test, and deliver new software tools for the Windows operating system based on an established installation. It is used to clone an existing Windows installation across multiple PCs. Cloning Microsoft Windows without first running Sysprep would be problematic because Windows 10, Windows Server, and other versions of Microsoft Windows include Security Identifiers(SIDs) that must be unique from one computer to the next. Sysprep generalizes windows by removing the security identifiers and other computer-specific information.

How to fix Sysprep’s Windows validation error?

Sysprep was not able to validate your Windows installation error can be fixed by following these below-mentioned fixes:

Fix 1: Check the Log File

When Sysprep displays the error prompt, it also displays, “Review the log file at %WINDIR%\Systme32\Panther\setupact.log for details”. What we need to do here is check the log file to narrow down the exact reason for the issue. You can do this as follows:

Step 1: Press Windows + R on the keyboard to open the Run dialog box and then paste the following and hit Enter or click on OK.

notepad %windir%\system32\Sysprep\panther\setupact.log

run the notepad log
Run dialog box

Step 2: The log file will be opened in Notepad. After looking through the log, move on to the corresponding solutions depending on the nature of the error.

Fix 2: Turn BitLocker Off

After going through the log file if you find any of the following two errors, then you must turn off the BitLocker to run the Sysprep.

  1. Error(0x80310039) SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep.
  2. Error(0x0f0082) SYSPRP ActionPlatform: Launch Module Failure occurred while executing ‘ValidateBitLockerState’ from C:\Windows\System32\BdeSysprep.dll.

Bitlocker provides security over the system drive, mainly the C drive. You can check for the BitLocker and disable it as follows:

Step 1: Search Command Prompt in the search bar of the Start Menu and hit Run as administrator.

run cmd as administrator
run cmd as administrator

Step 2: In the Command Prompt window execute the following command.

manage-bde -status

This will display all the drives with the BitLocker status.

manage bde status
Bitlocker status

Step 3: If the BitLocker is turned on for any of the drives you can decrypt by executing the following command:

Disable-Bitlocker -MountPoint 'C'

Here Replace the ‘C’ with the drive letter for which the Bitlocker is active.

dicrypting the drive
Decrypting the drive

This will disable the BitLocker for the concerned drive.

Fix 3: Remove any UWP Apps

If in the error log file you receive the following error message:

SYSPRP Package App Name_1.2.3.500_x64__8we4y23f8b4ws was installed for a user, but not provisioned for all users. This package will not function properly in the Sysprep image.

This means that you have downloaded a Universal Windows Platform (UWP) app that is installed on one of your user accounts, its source file will not be present on your user profile. In this scenario, Sysprep can’t validate the installation and will return the error log.

Here, two fixes are possible:

  1. You can remove the problematic app.
  2. Remove all users with unprovisioned apps.

But the first thing we need to do is to re-register the default Windows apps in case there is some other issue with the app.

Re-registering default UWP apps.

Step 1: Open the Run dialog box by pressing Windows + R on the keyboard and type PowerShell and then press Ctrl + Shift + Enter to open Administrator PowerShell.

run poershell
Run Dialog box
Administrator PowerShell
Administrator PowerShell

Step 2: Enter the command:

Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode-Register "$($_.InstallLocation)\AppXManifest.xml"}

PowerShell command to install default apps
Command to install default UWP apps

Doing the above fix will install all the UWP Apps in the system and hence may solve the problem happening with any other UWP Apps.

Step 4: Run Sysprep again. If it runs then the problem is solved. But if it shows the following error message in the error log:

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

then we need to do any of the two things:

  1. Remove the UWP Apps which are displayed in the error log.
  2. Remove all the Unprovosioned users.

Remove the UWP Apps

SYSPRP Package App Name_1.2.3.500_x64__8we4y23f8b4ws was installed for a user, but not provisioned for all users. This package will not function properly in the Sysprep image.

In the above error message App Name is the name of the app which is causing the problem and so we will remove it. Follow the steps to do the same:

Step 1: Open the Run dialog box by pressing Windows + R on the keyboard and type PowerShell and then press Ctrl + Shift + Enter to open Administrator PowerShell.

run poershell
Run dialog box

Step 2: When the PowerShell opens execute the commands in the given order:

Remove-AppxPackage -Package\packagename

Remove-AppxProvisionedPackage -Online -PackageName packagename

Note: Here, replace the packagename with the actual name of the package. For example – In the image below Microsoft.WindowsAlarms_11.2206.27.0_x64__8wekyb38bbwe is the name of the app which will come in place of packagename

powershell remove appx package
App Package Name

Step 3: Repeat these steps for all the apps that are mentioned in the Sysprep error message log.

Remove all the unprovisioned users

In your OS if there are any local accounts, then you need to remove them for Sysprep to work. You can do this as follows:

Step 1: Press Windows + R on the keyboard which will open the Run dialog box. Type netplwiz and hit Enter.

run dialog box

Step 2: In the User Accounts window that appears, come under the Users tab, select an account and click on Remove. Finally, click on OK.

remove users
Remove Local Account

This will remove all the local accounts. Run Sysprep again and see if the problem persists.

Fix 4: Change Registry Values

Sysprep will not work if you have upgraded your windows to a newer version, you will face the following error:

Error[0x0f0036] spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

This is because Sysprep will only work on custom (clean) install versions of Windows. We can bypass this if we have already upgraded the windows by modifying the registry setting as follows:

Step 1: First of all open the Run dialog box by pressing Windows + R on the keyboard, type regedit and hit Enter.

regedit run dialogue box
regedit run dialogue box

Step 2: Registry Editor windows open up. Here, navigate to the following:


You can also directly paste the above path into the address bar of the Registry Editor.

Step 3: Right-click on the Upgrade registry value and click on Delete to remove it.

upgrade key delet
Upgrade registry delete

Step 4: In the Confirm Window click on Yes.

registy delete
Confirm delete

Note: Please make sure to create a backup of your system. Since this method overwrites the functions that are helpful for the operating system to work correctly.

Step 5: Now, navigate to the following path in the Registry Editor:


Step 6: Double-click on the CleanUpState registry value and change its value data to 7 and make sure to set its base as Hexadecimal. Then click on OK.


Step 7: Close the Registry Editor and run Sysprep.

Fix 5: Complete active scenarios

If you have any active scenarios like ongoing windows updates then Sysprep will not work in Audit mode because these active scenarios will take up your reserved storage space and lock the Windows OS.

The Sysprep will show you below mentioned error message in the error log when such a scenario occurs:

SYSPRP Sysprep_Clean_Validate_Opk: Audit mode cannot be turned on if reserved storage is in use. An update or servicing operation may be using reserved storage.; hr = 0x800F0975.

You may solve this issue as follows:

Step 1: Close any ongoing installation from Settings.

Step 2: If windows are installing updates then let them install. After it gets installed then pause the windows updates for the time being.

Step 3: Search for Windows Updates Settings in the Start menu and hit Open.

windows update settings

Step 4: From More options in the left pane select the duration of Pause from the drop-down menu and close it.

windows update install
Windows update pause

Step 6: Now the Sysprep again and see if the problem persists.

Fix 6: Replace the Spopk.dll File

If the Spopk.dll file causes a problem then you will see the below-mentioned error message in the error log:

SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing ‘Sysprep_Clean_Validate_Opk’ from C:\Windows\System32\spopk.dll ;dwRet = 0x975.

Spopk.dll is an OPK Sysprep Plugin file that helps in Sysprep’s Windows installation validation. This might get corrupted sometimes and cause trouble while running Sysprep. Below are the steps to replace this file with a healthy one:

Step 1: Download the spopk.dll file from the internet or copy it from another computer.

Step 2: Press Windows + R to open a Run dialog box and type cmd . Press Ctrl + Shift + Enter to open Command Prompt with the administrative rights.

run window cmd
Run dialog box-cmd command

Step 3: Enter the following command to take ownership and change permissions for spopk.dll :

  • takedown /f %WinDir%\System32\spopk.dll
  • icacls %WinDir%\System32\sopok.dll /Grant Administrators:f
aministrator right inthe command prompt
Taking ownership

Step 4: Again press Windows + R to open the Run dialog box and type %windir%\Systme32 to open System32 folder.

Step 5: Here replace the spopk.dll file with the newly downloaded one.

spopk.dll file
System 32 folder

Step 6: Confirm the prompt.

Bottom Line

So this is it. I hope this tutorial was able to solve your problem. Here we have listed all workarounds to solve your Sysprep validation problem. We are always happy to solve your problem. If you still face any other problems then please let us know. Thank you for being with us!!

Also Read:

Rate this post
Posted by
Ekansh Sudha

Hello there, I am Ekansh Sudha, basically a technology freak. Lover of innovation, advancement & change. I like how technology shapes our live & make good use of them to make our life, even more, better...(^_^)....

Leave a Reply

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