These instructions are for AutoKMS_VL_ALL 1) Extract win8 dvd or iso to a folder on your hard drive lets say d:\win81-dvd 2) Extract AutoKMS_VL_ALL-6.0.3-oem-v2.7z to d:\win81-dvd\sources 3) open d:\win81-dvd\sources\$oem$\$$\setup\scripts\setupcomplete.cmd in notepad. 4) find REG ADD line and change it to this : REG ADD "HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths" /v %AUTOKMS% /D 0 /T REG_DWORD /F 5) save modified setupcomplete.cmd 6) author a new iso or bootable usb using your favorite tools.
Well, I only wrote about KMSpico from the very beginning, in fact if I have to use AUTO_KMS (which makes more sense to me BTW) istead of KMSpico then I don't need anything else but this line: REG ADD "HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths" /v %AUTOKMS% /D 0 /T REG_DWORD /F in SetupComplete.cmd and no other files in $OEM$/$$/.... ( no RunOnce, no clean.cmd and of course no KMSpico_setup.exe) Did I get this right? (I work "inside" the iso with Ultraiso and the ISO has been bootable since I got it directly from MS)
You need murphy's AutoKMS_VL_ALL-6.0.3-oem-v2.7z file which need to be extracted to sources folder. Just follow the steps I mentioned above.
Yes, I got it already, I just asked if SetupComplete.cmd should have other lines than the one you wrote and if other files should be present in same dir All this is done Should this be the only line? And, last Q: Any other files in same dir as SetupComplete.cmd ?
Please, can somebody tell me, VPN Tap Driver, where I can find this driver? I didn't uninstall this driver when I installing W8.1 Pro.
KMSpico will do the work for you. Get it her (http)://forums.mydigitallife.net/threads/49108-KMSpico-Official-Thread
Yes it does have other lines however it is already there you just need to change the REG ADD line. after you extract the archive I mentioned above this will be your final folder structure : sources\$oem$\$$\setup\scripts\setupcomplete.cmd sources\$oem$\$$\AutoKMS_VL_ALL\AutoKMS_VL_ALL.exe sources\$oem$\$$\AutoKMS_VL_ALL\Check-Activation-Status.cmd sources\$oem$\$$\AutoKMS_VL_ALL\Create-Daily-Activate-Task.cmd sources\$oem$\$$\AutoKMS_VL_ALL\Uninstall-Daily-Activate-Task.cmd You do not need any other files besides those I listed above and no additional modifications are necessary to setupcomplete.cmd besides the REG ADD line. You really shouldnt worry about what goes where, the archive already contains the correct folder structure. You just need to extract it to sources folder and the required files and folders will be extracted. The only thing you need to do after extraction is changing the REG ADD line in setupcomplete.cmd and it is only required for making sure that windows defender does not flag AutoKMS as virus other than that it does not affect activation at all.
Hi, I tested this by adding it to my AIO windows iso and it woked great, Windows 8.1 is automatically activated and the task(s) is in place.. but I have a question, why the Activation interval and Renewal interval are set to 43200 and not to the defaults (120/10080)? if this is set to run daily and on boot why not leave it to the defaults... what is the advantage?...just wondering.. thanks! edit: fyi- I also installed Office 2013 and it activated just fine.
Random: Spoiler Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\KMSServerService\Parameters] "KMSPort"="1688" "KMSPID"="RandomKMSPID" "VLActivationInterval"=dword:00000078 "VLRenewalInterval"=dword:00002760 "KillProcessOnPort"=dword:00000001 Specific: Spoiler Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\KMSServerService\Parameters] "KMSPort"="1688" "VLActivationInterval"=dword:00000078 "VLRenewalInterval"=dword:00002760 "KillProcessOnPort"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\KMSServerService\Parameters\KMSPID] "55c92734-d682-4d71-983e-d6ec3f16059f"="55041-00206-152-589866-03-1033-9200.0000-3002013" "59a52881-a989-479d-af46-f275c6370663"="55041-00096-199-972952-03-1033-9200.0000-3002013" "0ff1ce15-a989-479d-af46-f275c6370663"="05426-00206-234-182757-03-1033-9200.0000-3002013"
You could probably insert the code to specify the service priority and re-compile it, but I'm not aware of any way to launch a service and modify it's priority after the fact. Even if you did tune the tunmirror to run more efficiently by taking up more cpu cycles, would you really want that running all the time? I think that tunmirror may just be the first working method of getting around the localhost block. We could probably come up with some different coding that actually works more efficiently. There's gotta be more ways out there to fool the activation that wouldn't fail out with the system is slow or busy.