Attempting to create a reference OS image, but an error message occurs “Sysprep was not able to validate your Windows installation.” How to fix it?
“Sysprep Was Not Able to Validate Your Windows Installation” error may appear when you perform the Sysprep /generalize /oobe /shutdown command while building a reference Windows 10 image as below.
As you know, the Sysprep software is used to create a reference Windows image and depersonalize it, and remove all unique identifiers (SID, GUID) from the system, which is required for it to be deployed correctly on the corporate network.
We will suggest a method for remedying your problem on this topic in this article.
What Causes “The Sysprep Was Not Able To Validate Your Windows Installation” Error?
Sysprep Windows is a program that prepares an image for the deployment of an operating system. This utility must run if you wish to produce a reference OS image.
However, you may occasionally encounter an error message that says Sysprep was unable to validate.
Since introducing Windows apps (Metro or Modern applications) in Windows 8, this issue has occurred. It isn’t a brand-new error message, after all. This message was generated by Sysprep in prior Windows editions for a variety of reasons.
The most common reason is that Sysprep runs on a Windows system that had been upgraded. It’s best to keep things as simple as possible when creating a reference image. Always begin with a fresh installation and change only what is a must.
Another possibility is that the Windows installation was not activated. Outstanding reboots can cause Sysprep to fail sometimes. Before you perform Sysprep, you want to ensure that validating windows 7 is completely stable.
The most likely cause of the error notice in Windows 10 failed to validate product key is because Sysprep ran into issues with the new Windows apps. These programs are still unfamiliar with how to validate windows 7, so proceed with caution when using them in your reference image.
How To Fix “Sysprep Was Not Able to Validate Your Windows Installation” Error?
Ways of solving this occurring error examine the Sysprep utility log file setupact.log in any text editor (for example, Notepad) in the C:\Windows\System32\Sysprep\Panther directory.
Begin by looking over the contents of the setupact.log file from the bottom to the top for any issues. You’ll need to take distinct steps to solve the mistake depending on what it is. The probable Sysprep errors will discuss below.
Turn Off BitLocker
Error SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039)
Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing ‘ValidateBitLockerState’ from C:\Windows\System32\BdeSysprep.dll
If you notice your file exhibits any of the two problems after reviewing the log file, try disabling BitLocker.
Run the following command from the command prompt as administrator:
The following information should return:
Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: [OSDisk]
Conversion Status: Encryption in Progress
This error is common on Windows 10 tablets and laptops that use InstantGo encryption (based on BitLocker.) To address this problem, run the command below PowerShell command to disable encryption for the system volume:
SYSPRP Failed to Remove Apps for the Current User
If you get the following problems, it means you could have downloaded a program of Universal Windows Platform or deleted an application wrongly. As a result, examine the setupact.log for such errors:
Error SYSPRP Package SomeAppName_188.8.131.520_x64__8we4y23f8b4ws was installed for a user, but not provisioned for all users. This package will not function properly in the Sysprep image.
Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.
This cue suggests you either manually installed Modern/Universal Apps from the Windows Store or uninstalled a specific program wrongly.
Attempt to uninstall this software bundle with the following PowerShell commands:
You want to stop the Internet connection on your reference Windows 10 PC and stop automatic updates in audit mode before producing the image to guarantee that the Microsoft Store does not update the apps from there.
Remove all local user profiles, leaving only the local administrator profile.
Sysprep Will Not Work On Upgraded OS
When you try to execute Sysprep in the setupact.log after upgrading the operating system in your image to Windows 10 from a prior version (Windows 8.1 or Windows 7 SP1), the error below should appear:
Error [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.
Using Sysprep on a Windows image upgraded from a previous Windows version is not recommended by Microsoft. It is advisable to use an image with a fresh Windows 10 installation. There is, however, a means to get around this requirement:
- Open the Registry Editor regedit.exe and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\Setup;
- Find and delete the parameter called Upgrade;
Go to HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus and change the parameter of the CleanupState key to 7.
As a result, Sysprep will presume that this copy of Windows is being installed in clean mode. The last step is to reboot your PC and run Sysprep once more.
I hope that this post on how to fix Sysprep was unable to validate your Windows installation using a simple method. You can do so by reading and following our instructions. That’s all!
Maybe you are interested in