· The rearm count is reset to 5
http://www.vdnieuwenhof.eu/2014/03/reset-windows-rearm-count/
http://bobbitco.com/2015/09/22/how-to-reset-the-sysprep-rearm-counter-on-windows-2008-r2/
winpe3_amd64.ISO under local host.
Enter the key after reboot.
slmgr.vbs /ipk 9C6JF-G8DJP-2M247-V979W-62F6G
· Verify these settings Regedit:
https://www.itninja.com/question/windows-7-rearm-count-0
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\
CleanupState:2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\
GeneralizationState:7
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm :1
· Run sysprep
sysprep.exe /generalize /oobe /reboot
· Delete the key
https://www.wintips.org/sysprep-fatal-error-0x0f0085-could-not-load-msesysprep-dll-fix/
· Sysprep_Generalize_MiStreamProv: RegDeleteValue for target uri failed with erro
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\StreamProvider] “LastFullPayloadTime”=dword:00000000
· Verify: check SID different.
Whoami /user
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
https://support.huawei.com/enterprise/zh/knowledge/EKB1000097038
问题描述在进行Windows系统封装时，由于 sysprep的剩余次数超过操作系统限制而引发报错。
告警信息
系统封装失败。
处理过程
MSDN官方的说明中可以看出在做Sysprep的过程中3次的重置限制是可以跳过的，在超出3次后sysprep过程中会跳出系统发生严重错误的对话框，导致sysprep的过程终止。
解决方法如下：
运行regedit进入注册表编辑器更改以下两项键值：
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\ CurrentVersion\SoftwareProtectionPlatform\SkipRearm键值更改为1
HKEY_LOCAL_MACHINE\System\Setup\Status\SysprepStatus\右方的 GeneralizationState键值更改为7
然后再进行Sysprep即可。
根因
Windows 7/2008/2012操作系统重置激活开始时间的次数最多支持执行3-5次，使用模制作板优化工具制作完整复制模板时会对模板虚拟机执行sysprep，而执行sysprep过程中默认会重置激活开始时间，如果执行sysprep时系统剩余的可重置次数超过系统的限制次数，则模板制作就会失败。
建议与总结
请各位在封装windows镜像时, 在操作系统进行Sysprep前最好运行slmgr /dlv 查看该系统还能进行sysprep的剩余次数以免操作系统超出sysprep的次数而引发报错导致做无功。
在cmd命令窗口中执行如下命令，请看下图：
END
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
https://www.repairwin.com/how-to-sysprep-windows-more-than-three-3-times-rearm/
https://system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times/
It can happen, the need of re-syspreping an already syspreped machine, why ? maybe you lost your Image master. so.. you running the setup process, adding the changes you want, relocating the XML answerfile, running the sysprep with /generalize switch.. the process is running for few seconds and then the sysprep window is disappeared. well.. open the sysprep log file under \sysprep\Panther … there you will find setup error log, if the logfile contains this line :
Date Time, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn’t update the recorded state, dwRet = 31
then Microsoft say… “Hey dude, bummer…, re-create the whole image“.
well… it’s not so true… this error indicates that you syspreped the machine more then 3 times, you cant do that… if the windows system was already activated by pre OEM activation you cant even re-arm the machine.. so you have 2 problems, one – can’t sysprep anymore and probably you can’t re-arm your machine (it wont let you sysprep if you cant re-arm..).
so, first check if you can re-arm by runing the slmgr.vbs /dlv and check the re-arm counter, if it set to zero.. you need to do the following : http://support.microsoft.com/kb/929828 (set the <SkipRearm>1</SkipRearm> like in the example, note: this option will make the product key window to appear in the setup process).
you can also try running : slmgr.vbs –rearm, to rearm Windows.
after that, let’s come back to the sysprep process.. for syspreping already syspreped machine we have to change few keys in the registry :
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\
CleanupState:2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\GeneralizationState:7
After done with the registry, do the following :
Start -> Run : msdtc -uninstall (wait few seconds)
Start -> Run : msdtc -install (wait few seconds)
Restart the machine
Check the registry for the right registry keys values
sysprep with the new XML answerfile.
and.. Walla !
Have fun.
