You have no Tap adapters leftover from previous attempts? Maybe run Remove_Tap-Adapter.cmd and retry.
Forwarding port 1688 does not need to be permanent. And the whole world does not know if or when your have forwarded port 1688. Port forwarding is an option that can be active for just a few minutes.
May I suggest you a "cosmetic" fix ? Spoiler @echo off set port=1688 set kmsip=10.3.0.3 set AI=43200 set RI=43200 set epid=RandomKMSPID set /a ktap=1 set /a ktun=0 :gotAdmin pushd "%~dp0" :Compare the build and install tap and tunmirror if 9600 or greater for /f "tokens=6 delims=[]. " %%G in ('ver') do set winbuild=%%G if %winbuild% LSS 9600 (set kmsip=127.0.0.2&goto osttap) reg.exe query "hklm\software\microsoft\Windows NT\currentversion" /v buildlabex | find /i "amd64" >nul 2>&1 if %errorlevel% equ 0 set xOS=x64 if /i "%PROCESSOR_ARCHITECTURE%"=="x86" if not defined PROCESSOR_ARCHITEW6432 set xOS=x86 route print | find /i "TAP-Windows Adapter V9" >nul 2>&1 IF NOT ERRORLEVEL 1 goto :act IF ERRORLEVEL 1 goto :tap :tap certutil.exe -addstore -f "TrustedPublisher" tap0901.cer >nul 2>&1 %xOS%\devcon.exe install %xOS%\OemWin2k.inf tap0901 >nul 2>&1 if %errorlevel% neq 0 (exit) set /a ktap=0 :act for /f "tokens=1 delims=. " %%i in ('route print ^| find /i "TAP-Windows Adapter V9"') do (netsh interface ip set address %%i static 10.3.0.1 255.255.255.0) >nul 2>&1 start /b /high TunMirror.exe >nul 2>&1 set /a ktun=1 osttap Set KMSSERVERPATH="%~dp0KMS Server.exe" netsh advfirewall firewall add rule name="KMSServer" dir=in program=%KMSSERVERPATH% localport=%port% protocol=TCP action=allow remoteip=localsubnet >nul 2>&1 netsh advfirewall firewall add rule name="KMSServer" dir=out program=%KMSSERVERPATH% localport=%port% protocol=TCP action=allow remoteip=localsubnet >nul 2>&1 start /b /high "" "KMS Server.exe" %port% %epid% %AI% %RI% KillProcessOnPort >nul 2>&1 timeout /t 3 /nobreak >nul 2>&1 call :SPP call :OSPP taskkill /t /f /IM "KMS Server.exe" >nul 2>&1 if %ktun% equ 1 (taskkill /t /f /IM tunmirror.exe >nul 2>&1) if %ktap% equ 0 (%xOS%\devcon.exe remove tap0901 >nul 2>&1) And of course the same fix for your $oem$ folder.
I don't have that much error handling in that script. I paired up the tunmirror and tap install because you don't need either of them win builds <9600 So it makes sense to me to use just the one variable. It might be a decent idea for abbodi1406 though as he actually handles the errors and shuts down when each one is individually failing.
Does it matter what KMS cd-key is used? The reason I ask is because I've just came into a legit and working Windows 8.1 KMS key. Would it be possible for me to run something like KMS_VL_ALL_6.0.3 but locally (not connect to a outside KMS server) and use this key instead? Or does it really matter and just stick with KMS_VL_ALL and not worry about this key I have?
It's not error handling he suggests you add a mark for tunmirror just like tap, so if you are on win8, 7 it does not kill tunmirror (because it's not started in the first place)
1. No, because vista uses different Software Licensing Service and Mechanism. the keys maybe are added for compatibility or something in the very first KMS_VL_ALL script. 2. because tunmirror.exe is a .net4 program. Nevertheless, i already added win8 & win7 support without needing for tap & tunmirror to the next KMS_VL_ALL release. 3. It will generates epid matching OS lcid (not 1033 everytime).
I'll admit I'm not sure how all this licensing stuff works. Just know that key I have is legit and works as it came from the current company I'm working for. I unfortunately do not have a MAK key. Just wasn't sure if it was worth it to configure, somehow, MKS_VL_ALL to use this key instead of trying to connect to some remote KMS server online somewhere. Thanks!
But why would you want KMS_VL_ALL to use a custom key (legit, that too) and connect to some other server? Besides, if you have KMS_VL_ALL, it's offline, you can activate without an internet connection too
Hi guys, I'm sure this question has been asked before on this thread, but I really don't want to search through 207 pages. Does The kms pico linked in the op activate win 8.1 pro for 180 days now without needing constant access to a server?