Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Surface Pro 3 does not validate Windows installation in Windows 8.1


View products that this article applies to.

Symptoms

When you run Sysprep.exe on Microsoft Surface Pro 3, you may receive the following error messages:

Sysprep was not able to validate your Windows installation. Review the log file at %windir%\system32\Sysprep\panther\setupact.log for details.  After resolving the issue use Sysprep to validate your installation again. 

Reviewing the setupact.log may show the following errors:

2014-11-03 20:57:55, Error SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039)
[gle=0x00000001]
2014-11-03 20:57:55, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll; dwRet = 0x80310039[gle=0x00000001]
2014-11-03 20:57:55, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x80310039
2014-11-03 20:57:55, Error SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x80310039
2014-11-03 20:57:55, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x80310039
2014-11-03 20:57:55, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80310039

If you run manage-bde -status command it will show the following:

Disk volumes that can be protected with
BitLocker Drive Encryption:
Volume C: [OSDisk]
[OS Volume]

Size: 118.34 GB
BitLocker Version: 2.0
Conversion Status: Encryption in Progress
Percentage Encrypted: 97.8%
Encryption Method: AES 128
Protection Status: Protection Off
Lock Status: Unlocked
Identification Field: Unknown
Key Protectors: None Found

Note This issue can occur on any system that supports connected standby.

↑ Back to the top


Cause

This issue occurs because Windows automatically starts encrypting drives by using BitLocker on Windows 8.1-based computers that support InstantGo (connected standby).

↑ Back to the top


Resolution

To resolve this issue, in Command Prompt as an administrator, run the following command:

manage-bde -off c:

Notes
  • The command may take some time to fully decrypt the drive. You can run the manage-bde -status command to monitor progress. 
  • When full decryption is complete, you can run Sysprep.exe again.
  • To prevent this issue during the initial install of Windows, set the PreventDeviceEncryption value to True in the unattend.xml file during the out-of-body experience (OOBE) phase to build the reference image. For more information, see the PreventDeviceEncryption.


↑ Back to the top


More Information

After you set the value in the unattend.xml file, the following registry subkey and registry entry is created:
Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker
Name: PreventDeviceEncryption
Type: REG_DWORD
Data: 0x00000001

↑ Back to the top


Keywords: kbexpertiseadvanced, kbsurveynew, kbtshoot, kbportal388, kb, kbportal421

↑ Back to the top

Article Info
Article ID : 3014868
Revision : 3
Created on : 7/19/2019
Published on : 7/20/2019
Exists online : False
Views : 313