WINDOWS 10 RESET REARM COUNT INSTALL
WINDOWS 10 RESET REARM COUNT DRIVERS

Remark: for the current purposes “rearm” means reset the activation period of the OS.įor versions of Vista and above, to rearm a computer you run the command: So if you by any chance happen to stumble across this blog in the proper moment you can save at least half of your time with the following information.

WINDOWS 10 RESET REARM COUNT INSTALL

And bingo, finally rearm in Save Mode, restart, logon, install the Hyper-V drivers, find your mouse in the corner and full with joy return to the usual Windows world, causing you the rest of the wasted time. You lavish another half an hour googling / binging to find out what the commands were. Good ol’ times, forgot, forgot, rapidly accustomed to the Vista / Win7 world. Fine, but regrettably there is no such command under XP.

The installation breaks somewhere in the middle and you iterate the procedure just to be sure that it was not your fault and to round up the next 30 minutes J You finally come to the brilliant idea to rearm in Safe Mode. This takes another half an hour J OK, we don’t give up, do we? Just restart in Safe Mode and try to install Hyper-V Integration Services. This takes you about half an hour J But what if you want to change the key – let’s say you are moving from an OEM machine and want to insert a retail license key? If you try to change the key from the telephone activation windows, don’t be surprised if no new activation token is being created.

WINDOWS 10 RESET REARM COUNT DRIVERS

You are the clever guy who doesn’t give up and try to agree, but since the drivers for Hyper-V are still not installed you are using the keyboard and attempt to activate over the phone. If you disagree you are logged off momentarily. Then on the console you are welcomed with a pop-up screen to activate. But what if you are trying Windows XP? You are moving the machine, configuring it through Hyper-V manager and starting. And that is the MS activation: if you are moving a Server OS, like Server 2003 (R2) and above you will land with a 3-days grace period to activate, which is enough time to install Hyper-V Integration Services and using the mouse, activate, or even change the key comfortably. Well, there are some caveats, especially when you are moving Client OS and not Server OS. Should work right out of the spot, right? I mean, using Sysinternal’s disk2vhd is a straight-forward process and moving to a Microsoft homogenous environment – meaning, moving to Hyper-V – should be a piece of cake. The background was trivial: P2V migration. Recently I experienced a 3 hours LOB delay because of Microsoft’s infamous activation policy.

Windows 10 reset rearm count