Me too here, V9 will be my 4th download on this KMSMicro series Maybe they can compress it into just 10 Mb
At this rate, when I wake up tomorrow it will be 25MB unzipped (but I need to fly to San Diego for a conference. My fun is over soon, at least until the 14th lol)
If it can sync Time offline or Activate without sync time... It will be a complete offline Activation solution....
Thank god I didn't invest time and effort in a GUI to make the process simple (a push of a button) Til this settles down to a size like the KMS for windows 7 and Office 2010, we shall SEE IT GET SMALLER AND SMALLER. Then the GUI applications will follow
mount/attach KMSmicro.vhd goto :\kmshost\configuration.cmd & open with notepad delete the top lines: "%programfiles%\NetTime\NetTime.exe" "%systemdrive%\kmshost\NETTIME\NETTIME.exe" /hide save & eject/unmount the vhd now the machine/script will run without internet needed and you can sync time offline manually through option Z choose & set your right timezone... then set time manually correctly
Just delete de space in the btih: hash for example: Code: 03B33594D4928DE92024E857621A90 C3A1F30D0B to 03B33594D4928DE92024E857621A90C3A1F30D0B and it will work
No this will make the KMSmicro time to be like your real machine time Regardless of the difference in timezones but the correct time sync require to either KMSmicro+RealPC to be the same in timezone&time, or the correct time when the timezones differ example: KMSmicro time 03:00 , timezone US standard | RealPC time 03:00 , timezone US Standard or KMSmicro time 03:00 , timezone US standard | RealPC time 08:00 , timezone GMT
Create differencing/undo image for v8+ since V8, KMSmicro has been upgraded from Connectix VHD format to QEMU qcow2 format as you boot up KMSmicro, the image will be written and altered. A good thing to have is to have the main image read only, and have all writes to a differencing image, and by removing or reseting that image, you get an undo feature. What we can do now is access the cow (copy-on-write) feature of the qcow2 (QEMU copy-on-write v2) image. Get a copy of the full qemu, we actually only need qemu-img.exe (which was not included in the KMSmicro package) I am using a copy from here: homepage3.nifty.com/takeda-toshiya/ copy qemu-img.exe into Bios folder (same folder as openqemupc.rom) Create a new cmd script file in the same folder as the other cmd script files. Insert the following as content: Code: REM Create or recreate differencing image for copy-on-write for qcow2 image @ECHO OFF pushd "%~dp0" cd qemu\bios qemu-img.exe create -f qcow2 -b openqemupc.rom openqemupc-diff.rom echo. echo New diff image created. echo. pause popd exit edit your KMSmicro scripts and alter the lines from Code: -hda Bios\openqemupc.rom ^ to Code: -hda Bios\openqemupc-diff.rom ^ Running this cmd script will create (or recreate, removing the old) differencing image file (based on the current image, in what ever state it may be) where all writes will be made, making the original read only. A recommended course of procedure would be: re-extract a fresh copy of the original image (openqemupc.rom) boot it up normally apply any changes (time-zone, etc) shut it down copy qemu-img.exe, create script. Run the script. edit remaining scripts to use the diff image.
Just tried v9 on a Win 8 Pro x64 and it worked perfectly, but why (a couple of days ago on another PC) when I entered the free M$ WMC key to upgrade a non activated Win 8 Pro x64 did it say permanent activation whereas the v9 MicroKMS activation method is only for 180 days?
WMC key is RETAIL key, so it's permanent of course, but it's unsafe since it's personal key This KMSMicro will be the best solution since you need no internet connection to active your windows and 180 days is EXTENDABLE.
I can't seem to get this to run on one of my pcs. I have been able to get it to run on all my other pcs but not this one. I am using V9 and when I run the 1-0kms command a command windows flashes for a second but the server never boots up. In the task manager it shows it as running. This is the pc that I installed VMware workstation on to activate using the original kms activation method.
from task manager stop all vmware services and try again or look in qemu folder for sderr.txt file and read what the error
I already tried by stopping all the VMware services, maybe I missed one. Here is the text from the sderr file qemu-system-x86_64.exe: -net user,hostfwd=tcp:0.0.0.0:1688-:1688,hostfwd=udp:127.0.0.1:123-:123: could not set up host forwarding rule 'tcp:0.0.0.0:1688-:1688' qemu-system-x86_64.exe: -net user,hostfwd=tcp:0.0.0.0:1688-:1688,hostfwd=udp:127.0.0.1:123-:123: Device 'user' could not be initialized