A few words from Ratiborus about KMSmicro Yesterday, when I asked Ratiborus whether KMSmciro was an activator or not he answered this: "Activator is not the correct definition. Usually "activator" refers to various hacking programs that have something to hack into the files reworked or replaced. A KMSmicro does everything as scheduled by M$. Everything is done by the rules. This is exactly the same as the CCM server and those who are in firms and companies. The only difference is that I reduced in size the operating system. I personally activated KMSmicro server M$. Moreover. The key that is set in KMSmicro isn't legal. I did not buy it, just somebody gave it to me. So this is not an activator. This is the CCM server."
After installing the Russian KMS server 5.0 the KMSmicro.exe did not work for me. I put all the files in the same directory and started the qemu-emulator manually with a cmd-file (as administrator). When the KMS-server is running its starts with a Russian timezone. You need to change the timezone to the one of your PC. After changing the timezone the KMS shuts down. Restart with the cmd-file. See code below. Don't forget the last character (point). start qemu-system-x86_64.exe -net nic,vlan=0 -net user,vlan=0 -redir tcp:1688::1688 -m 512 -hda kmsmicro.rom -rtc base=localtime,clock=host -name KMS_127.0.0.1 -M pc -L .
No I did not install TAP. I removed several files (one by one) with trial and error. The following files are essential and needed to start the KMS server manually. bios.bin fmod.dll intl.dll kmsmicro.rom kvmvapic.bin libgcc_s_dw2-1.dll libglib-2.0-0.dll libgthread-2.0-0.dll libpng12.dll libpng14-14.dll libssp-0.dll mgwz.dll mingwm10.dll pxe-e1000.rom qemu.exe SDL.dll vgabios-cirrus.bin zlib1.dll
I'm going to ask heldigard about this, he is a nice guy, hopefully he will shed some extra light on this.
Can anyone tell me how to create a shortcut to start the Qemu machine without using KMSMicro.exe to start it? I have it running on my LAN and want to be able to simply run the VM at startup. Any assistance is appreciated.
What's the difference KMSPico vs KMSmicro? Anyway, I just installed Win 8.1 Pro N VL whilst supposedly this was 17/10 version with rollup included, but as soon as tried to update, it found and installed the 230MB update... Ain't this strange? I just pressed the latest KMSPico portable and it activated win in no time. I didn't see anything, no UI no anything. Do I have to do something extra? I mean, to delete any leftovers or something? Meanwhile the N version was nice in theory, considerably cleaner Windows, but eventually I installed only the x64 media package because I don't want to have Win without Dxva and EVR. At least I left out the x86 package. My player ( MPC HC ) is x64 version and Firefox works normal with html5 mp4 + dxva.
since you are activated nicely, don't worry about further steps. You are done atm. Concerning the 10/17 version I doubt that it was such because the updates won't come in a second time
Can you please elaborate a little more? What do you mean? The 17/10 version doesn't include the rollup? Yeah, I don't worry about the KMS. I know after 6 months again. The fact I didn't see UI on KMSPico portable is normal, right?
the startline to have it run on lan is Code: 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 256 -hda Bios\KMSmicro.rom -name "KMSmicro Console IP-127.0.0.2:1688" -M pc -L Bios -net nic,macaddr=00:11:22:33:44:03,vlan=0 -net user,vlan=0 -redir tcp:1688::1688 -rtc base=utc,clock=host -nodefconfig -no-user-config -no-hpet -no-fd-bootchk -no-quit you might have to adjust timezone in vm to utc kms server name = local ip of host computer (or it's name) you can activate all computers on your lan except the one which is running qemu
newest 10/17 MSDN VL versions like the the one you mentioned have these updates included. If you loaded an earlier version without these updates, they come automatically when you are online. Nothing dramatic. All is fine after that but you did not get the 10/17 version as your download, that easy
Thank you very much! The one running the VM is a win7 machine anyway so that doesnt matter, thanks again!
Success: View attachment 24979 As you can see, I managed to graft the tokens and the product key (partial 2PFVV) into a fresh Win 7 Pro VM in VirtualBox, and managed to activate it online and charge the KMS host. However, as I mentioned before, it's a technically very challenging process. For now I can tell you that it involves more than just copying tokens.dat from the SoftwareProtectionPlatform folder. The main difficulty is that we do not know what the product key is. tokens.dat alone, without knowing the product key, is not enough to transfer. Therefore, the entire set of activation data needs to be transferred, which is made up of several more parts. I may appear to be secretive at the moment, but that is not my intention. I plan to write instructions and release reusable activation files for at least VirtualBox and VMWare, and perhaps Hyper-V. There are two main reasons why I am not ready to release any information yet: 1) In order to create the activation files for all those virtualization products, I do have to be able to activate online. For now, this CSVLK isn't blocked yet, and I am able to do so. However, if everyone and their grandma starts playing around with it, it will very quickly become blocked. I would like to finish everything up before that happens. 2) The process is complex. I don't want to release half-baked instructions. I am also trying to judge the level at which I should aim the instructions. I think not everyone will be able to set up their own clean KMS VM. Please be patient with me.