Shulou(Shulou.com)06/02 Report--

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

Https://blogs.technet.microsoft.com/brandonlinton/2018/05/03/sysprep-fails-if-installing-windows-management-framework-5-1/

[HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows\ StreamProvider] "LastFullPayloadTime" = dword:00000000

Verify: check SID different.

Whoami / user

-

Https://support.huawei.com/enterprise/zh/knowledge/EKB1000097038

The problem describes that during the encapsulation of the Windows system, an error is caused because the remaining number of times of sysprep exceeds the operating system limit.

Alarm information

System encapsulation failed.

Treatment process

In the official instructions of MSDN, you can see that the reset limit of 3 times in the process of Sysprep can be skipped. After exceeding 3 times, the sysprep process will jump out of the dialog box where a serious error occurred in the system, resulting in the termination of the sysprep process.

The solution is as follows:

Run regedit to enter the registry editor to change the following two key values:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ SoftwareProtectionPlatform\ SkipRearm key value changed to 1

The GeneralizationState key on the right of HKEY_LOCAL_MACHINE\ System\ Setup\ Status\ SysprepStatus\ is changed to 7.

Then Sysprep can be done.

Root cause

The maximum number of times that the operating system resets the activation start time of Windows 72008Compact 2012 can be performed 3-5 times. Sysprep will be performed on the template virtual machine when making a full copy template using the molded board optimization tool, and the activation start time will be reset by default during the execution of sysprep. If the number of resets left by the system exceeds the limit number of times the system can perform sysprep, the template will fail.

Suggestion and summary

When encapsulating the windows image, it is best to run slmgr / dlv before the operating system Sysprep to check the remaining number of times the system can perform sysprep lest the operating system causes an error and causes reactive power caused by the number of times the operating system exceeds sysprep.

Execute the following command in the cmd command window, see the following figure:

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 1 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.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.