none
Win10(1809)运行Sysprep出错。是否是系统BUG? RRS feed

  • 问题

  • 首先感谢大家对这个问题的并注。这里有一个Win10(1809)的系统,将所有软件安装好以后,正运行sysprep将系统进行封装。结果无论何都报些错误。如下:

    后查看setupact.log日志文件。显示信息如下:

    2019-02-18 15:36:35, Info                  SYSPRP ========================================================
    2019-02-18 15:36:35, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2019-02-18 15:36:35, Info                  SYSPRP ========================================================
    2019-02-18 15:36:35, Info       [0x0f004d] SYSPRP The time is now 2019-02-18 15:36:35
    2019-02-18 15:36:35, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\System32\Sysprep\Panther
    2019-02-18 15:36:35, Info       [0x0f0054] SYSPRP ValidatePrivileges:User has required privileges to sysprep machine
    2019-02-18 15:36:35, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\System32\Sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2019-02-18 15:36:35, Info       [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...
    2019-02-18 15:36:47, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'cleanup' internal providers.
    2019-02-18 15:36:47, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 3
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml, and mode <null>
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2019-02-18 15:36:47, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll
    2019-02-18 15:36:47, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll without error
    2019-02-18 15:36:47, Info       [0x0f00d7] SYSPRP WinMain:Pre-validing 'generalize' internal providers.
    2019-02-18 15:36:47, Info                  SYSPRP RunExternalDlls:Running platform actions specified in action file for phase 1
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateSession: Successfully created instance with action file C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml, and mode <null>
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::Validate: Beginning action execution from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Sysprep mode in registry is <null>
    2019-02-18 15:36:47, Info                  SYSPRP SysprepSession::CreateXPathForSelection: Processor architecture in registry is AMD64
    2019-02-18 15:36:47, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll
    2019-02-18 15:36:47, Info                  SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.

    2019-02-18 15:36:48, Info                  SYSPRP All appx packages were verified to be inbox or alluser installed.

    2019-02-18 15:36:48, Info                  SYSPRP ActionPlatform::LaunchModule: Successfully executed 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll without error
    2019-02-18 15:36:48, Info                  SYSPRP ActionPlatform::LaunchModule: Executing method 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll
    2019-02-18 15:36:48, Error                 SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039)
    [gle=0x00000001]
    2019-02-18 15:36:48, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll; dwRet = 0x80310039[gle=0x00000001]
    2019-02-18 15:36:48, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x80310039
    2019-02-18 15:36:48, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x80310039
    2019-02-18 15:36:48, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x80310039
    2019-02-18 15:36:48, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80310039
    2019-02-18 15:36:50, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2019-02-18 15:36:50, Info       [0x0f004d] SYSPRP The time is now 2019-02-18 15:36:50

    我的将Bitlocker并没有激活,而且也在BIOS中关闭过TPM芯片的安装功能。相应的bitlocker drive encryption service服务禁用且关闭。所作尝试均无效。现在实在找不到用哪种方法重新封装系统了。如下bitlocker并没有开启。

    以前在搞Win10(1709、1803)时,非常容易就可以完美正常封将,为何这个1809就老是报错呢?实在有些无语啊。网上各类方法都有关注,始终无法解决。比如:王春海老师的方法,激活administrator,并删除系统内建立的帐号及配置文件。以管理员方式去行运行sysprep,还是报同样错误。

    2019年2月21日 3:17

答案

  • 这个情况我遇到过多次。

    当我们用微软的原版镜像(Pro版)干净安装后,直接进行sysprep /generalize操作,就会报错,setupact.log中显示:

    SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039)

    我们需要做的就是打开设置,更新和安全,设备加密,跳转到控制面的BitLocker界面,启用C盘的BitLocker,加密完毕后再解密,重启。运行sysprep

    试试看


    如果认为回帖者的回答有所帮助,请将之标记为答复,这样可以帮助更多的用户获取有效信息。
    2019年2月21日 6:22

全部回复

  • 这个情况我遇到过多次。

    当我们用微软的原版镜像(Pro版)干净安装后,直接进行sysprep /generalize操作,就会报错,setupact.log中显示:

    SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039)

    我们需要做的就是打开设置,更新和安全,设备加密,跳转到控制面的BitLocker界面,启用C盘的BitLocker,加密完毕后再解密,重启。运行sysprep

    试试看


    如果认为回帖者的回答有所帮助,请将之标记为答复,这样可以帮助更多的用户获取有效信息。
    2019年2月21日 6:22
  • 多亏兄弟的指点,问题已经解决了,看来还不是系统Bug。可是1709和1803怎么没有这毛病呢?同样的状态下。

    原因是拥有TPM芯片的电脑,默认开启了对系统卷的加密,只需跳转到控制面的BitLocker界面,关闭设备加密即可。重算SID后,完美解决SID重复问题。也解决的封装问题。

    非常感谢,看来自自己还需对系统加强学习。

    2019年2月22日 3:57