In this process, you need to generalize the Windows installing by using the command sysprep /generalize /shutdown /oobe and remove any data specific to your PC for privacy purposes. However, Sysprep can’t execute this process if it fails to validate the system and returns the “Sysprep was not able to validate your Windows installation” error message. This issue can happen because of various reasons, which we have mentioned in this article along with their solutions.
Causes for Sysprep Was Not Able to Validate Your Windows Installation
Fixes for Sysprep Was Not Able to Validate Your Windows Installation
First, make sure to disconnect the internet to avoid any automatic processes, such as updates while generalizing your Windows installation.
Running Sysprep on an upgraded Windows OS.Device Encryption or BitLocker enabled.Unprovisioning UWP apps for a user.Presence of an active scenario such as pending system updates.Corrupt Spopk.dll file.
Then, apply the possible solutions we have provided below to troubleshoot your issue.
Check Log File
The Sysprep error message also shows where you can review the error log message. So, the first thing you should do is check the log file to narrow down the exact reason for the issue.
You can open Run (Win + R) and enter notepad %windir%\system32\Sysprep\panther\setupact.log to open this file using the notepad.
After looking through the log, move on to the corresponding solutions depending on the nature of your error.
Disable Upgrade Registry Key and Entry
Sysprep won’t be able to validate your Windows installation if you try running the processs after upgrading your system. The log should show the following or a similar error message in such a scenario: As the message says, Microsoft doesn’t support running Sysprep on an upgraded Windows system and instead recommends users to clean install Windows first. However, you can avoid this issue by changing some registry values. Here’s how you can do so: This process fools the Windows OS into believing that you have a custom install version of Windows instead of an upgraded one.
Disable BitLocker
You can’t run Sysprep when your system is encrypted. If you try to do so, the error log usually shows the error message below: You may also get other messages, but they will contain the word BitLocker. To resolve the issue, you need to disable the process. Here’s how you can do so:
Disable TPM and PTT
Sometimes your system thinks BitLocker is enabled even when it’s actually off. So, you’ll still get the above error. It happens because sometimes the BDE goes into a waiting state when TPM is detected. There are two ways to resolve the issue. You can either enable BitLocker and then turn it off again. Or you can go to your BIOS and disable TPM (Trusted Platform Module), which is the device your system uses for encryption. You can usually find the option under Advanced, Security, or Trusted Computing in the BIOS or UEFI. You may also need to disable PTT (Intel Platform Trust Technology) in some devices.
Reinstall or Remove UWP App Packages
If you unprovisioned any Universal Windows Platform (UWP) app that is installed on one of your user accounts, the source files for the app won’t be present on your user profile. In such cases, Sysprep can’t validate the installation and you’ll usually find the following error message in the log file: You need to remove the apps from the user or remove all users with unprovisioned apps to resolve such issues. First, try re-registering the default Windows apps in case there’s some other issue with the app. To do so: Run Sysprep again and check if you still encounter the issue. If you do, you need to remove the UWP apps and their provisioning. You also need to manually remove the apps if the error log shows something like: Here are the necessary steps:
Complete Pending Updates and Then Pause Updates
Your can’t enable the Sysprep audit mode if there’s an active scenario such as updates. Such processes use your reserved storage, which locks your Windows OS. In this case, the log file shows an error message similar to: To resolve the issue, you need to install all pending cumulative updates and then pause your updates. You don’t need to install the optional updates. Make sure to install the necessary updates and restart your PC to complete all pending operations. Then, pause your updates using the instructions below: Disconnect your internet and try running Sysprep again.
Replace Spopk.dll File
Spopk.dll is a type of OPK Sysprep Plugin file that helps in Sysprep’s Windows installation validation. Sometimes this DLL file can become corrupt causing issues while running Sysprep. In such cases, the log shows an error message similar to, First, remove provisioning for the store apps, then install cumulative updates or pause updates and retry running Sysprep. If you still encounter the issue, you need to replace the Spopk.dll file. Here’s how you can do so:
