发表于 2013-11-9 15:30:22
How To recreate a Win 8.1 KMS host VM|
I provide activation data for VirtualBox, VMWare, Hyper-V and QEmu for use in Windows 7 Professional. See the attached zip file. This can be used to
recreate, completely offline, a working and activated KMS Host capable of activating up to Windows 8.1. It does NOT activate Windows Server versions
or Office. The activation data for each VM type consists of these items:
* *.C7483456-A289-439d-8115-601632D005A0 (two files)
I also provide four scripts in the form of *.cmd files to ease the process of restoring the activation data.
1) Create a VM using default settings for Windows 7 x86 (32-bit). DO NOT CONNECT THE VM TO THE INTERNET! You will need to adjust your VM to match
the IDs below exactly. The procedure is different for each VM type. (I don't provide instructions for this here; it's extensively discussed
Machine UUID: 52c53716-8c91-4936-bd6a-a1606b2fb1c0
HardDisk UUID: 5802f3cf-5e3e-490a-9c23-3500e2807a64
MAC Address: 0800272E4F02
UUID Bios: 56 4d 05 03 45 32 9c 3d-51 8e c7 9a 25 7a af 60
Baseboard Serial: 9253-0101-5575-5535-6237-3815-88
BIOS GUID: 2EFCD925-A555-469B-B736-A38404BFA66D
BIOS Serial: 9253-0101-5575-5535-6237-3815-88
MAC Address: 00:15:5D:73:84:00QEmu example command line:
qemu-system-x86_64.exe -vga cirrus -serial none -parallel none -display sdl -smbios type=1,manufacturer=Intel,version=1.01234,uuid=564d81c6-cd3a-
d8e4-db29-756df139acb9 -uuid 564d81c6-cd3a-d8e4-db29-756df139acb9 -m 512 -localtime -hda win7.img -name "Windows 7 Professional KMS" -M pc -L . -net
nic,macaddr=00:11:22:33:44:03,vlan=0 -net tap,vlan=0,ifname=tap1 -rtc base=localtime,clock=host -nodefconfig -no-user-config -no-hpet -no-fd-bootchk
-no-quitAssumes you have a hard disk image named win7.img in same folder as qemu, and a TAP adapter installed on the host named tap1. You will have
to adjust the command line to suit your own environment.
(The QEmu activation data is directly taken out of KMSmicro v5.0, hence the command line is almost identical to what KMSmicro v5.0 uses.)
2) Install Windows 7 Professional x86. When prompted for a product key, either skip it if possible, or use a default key for Win 7 Pro.
3) Install the KB2885698 update [http://www.microsoft.com/en-us/downl....aspx?id=40549] for Windows 7 x86 to add support for Windows 8.1 clients to
the KMS host component. Reboot once after this is installed!
4) Copy one of the folders from the supplied activation data (corresponding to your VM type) into the VM, using your favourite method to get files
into the VM. Place it wherever you want, for example in a folder named Activation on the Desktop.
4) Boot the VM to Recovery Console: mash F8 while the computer is booting, and select "Repair Your Computer". Follow the prompts about keyboard
layout and log in with a user. In the menu you are greeted with, select the "Command Prompt" option.
5) Change to drive D: (this is where normally the regular Windows 7 installation is mounted). Change to the folder where you placed the activation
data, for example: cd \Users\UserName\Desktop\Activation
6) There are four scripts supplied. Execute all of these in turn:
install_token.cmd (you will be asked 2 confirmations, answer Y)
register_wpa.cmdThere should be no error messages. (See the Appendix about what these scripts do)
7) Reboot normally.
You are done and should now have an activated KMS host. Check activation state with "slmgr /dlv". Charge the KMS host with your favourite charger
solution if desired. Don't forget to allow the KMS service through the firewall.
The supplied scripts
install_mistery.cmd: Copies the "mistery" files (*.C7483456-A289-439d-8115-601632D005A0) to their place.
attrib -h \Windows\System32\*.C7483456-A289-439d-8115-601632D005A0
copy *.C7483456-A289-439d-8115-601632D005A0 \Windows\System32install_token.cmd: Copies the tokens.dat file to its place.
del \Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\*.* /s
copy tokens.dat \Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatformregister_digitalid.cmd: Loads the
SOFTWARE hive of the Windows 7 install and merges the three entries in the CurrentVersion key.
reg load HKLM\MountPoint \Windows\System32\config\SOFTWARE
reg import CurrentVersion.reg
reg unload HKLM\MountPointregister_wpa.cmd: Loads the SYSTEM hive of the Windows 7 install and overwrites the entire WPA key.
reg load HKLM\MountPoint \Windows\System32\config\SYSTEM
reg delete HKLM\MountPoint\WPA /f
reg import WPA.reg
reg unload HKLM\MountPointAdditional notes
The reason why the Office 2010/2013 KMS Hosts are inactive in the resulting VMs is that after transferring activation data from KMSmicro to a
different VM, all three KMS Host components are initially inactive (Windows, Office 2010, Office 2013). I was able to reactivate the Windows 8.1 KMS
Host, but could not find a way for the Office KMS Hosts. Rather than having unactivated components in grace period, I chose to remove the Office KMS
Host product keys.
This doesn't apply to the QEmu activation data, which is the original copy out of the KMSmicro VM, and therefore contains all three activated KMS
Host components. If you use the QEmu activation data in a QEmu VM on Windows 7 Professional, you will have a KMS Host capable of activating up to
Windows 8.1 and Office 2010/2013.
This does mean that at this time it's not possible to create an arbitrary VM that provides a KMS Host up to Win 8.1 as well as Office 2010/2013. I
don't think this is a big problem, as there are other ways to activate Office 2010 and 2013 already, even in Windows 8.1. For example, it is
possible to run two different VMs, one for Win 8.1, and one for Office 2010/2013 activation. They could even run simultaneously and listen on two
If you already have a VM up and running with a Windows 8/Office 2010/Office 2013 KMS host (perhaps from last year), you may be able to reuse it,
and convert it to a Windows 8.1 KMS host. WARNING: This disables the Office 2010/2013 KMS hosts! Note that I haven't tested this, but this is what I
* Adjust the UUID etc. of the VM to match those of the supplied activation data.
* Follow the procedure in Part IV from step 3.
Comments, requests for clarification and in-depth technical questions are welcome. Errors in the document are very possible, please point it out if
you find one.
Attachment: activation data for various VM types
Download link: http://www1.datafilehost.com/d/699cee29
The download only contains very brief instructions, this is intentional.