There's so many tools using the Tap adapter now, people would likely be changing the settings on the connection it makes, and possibly installing more than one. As a multi-user tool it's just better to have it uninstall afterwards, but you're not married to those settings. You can extract the exe and point all of the different things to the cmd script and remove the line that calls the devcon remove tap0901 part
Yes, I understand. For general use it's better to keep it "self-contained", for others (like me), there's enough options to follow you guys' wonderful examples, and "cook" something for ourselves. Having the $oem$ folder to pre-activate 8.1 is a wonderful starting point!! Thanks man, I really, really (yes, REALLY) appreciate it!!!
I use the network adapter WIFI to get internet access. I can use Ethernet Network Adapter Cable for task to realize the tap adapter?
Sorry if this is a stupid question but doesn't KMS_VL_ALL 6.0.3 create/delete daily scripts for re-activation? If it does not, do I need to re-run the KMS_VL_ALL 6.0.3 script daily? Also, does it re-enable the Firewall after it activates?
No, you have to use/run the script. - No, you need to run it once. It does not disable firewall in the first place, it just adds exception rule then remove it
I'm not entirely sure how well the time-scheduled tasks run. It could be that running it weekly or monthly would be a really good way to do that. I think the problem might be that if your system is not idle it will not run or something. I'm pretty sure there was a reason that many of us started using onstart, onlogon, and daily. The daily one is really just for people who leave their computer on for a REALLY long time. Monthly seems perfectly reasonable to me. You're more than welcome to try it. Just don't be freaked out if it requires you to actually idle for 5 minutes or something when it's supposed to occur.
In the case of pre-9600 builds, there is no need to remove the TAP device and kill TunMirror. Thank you for your tool.
It doesn't remove the tap device. It skips the part where it does "set /a ktap=0" so the call "if %ktap% equ 0 (%xOS%\devcon.exe remove tap0901 >nul 2>&1)" doesn't do anything since ktap is previously set to 1. The killing tunmirror is unnecessary, but harmless
Your script (statements 13 to 15) : if %winbuild% LSS 9600 (set kmsip=127.0.0.2&goto osttap) set /a ktap=1 The correct coding should be : set /a ktap=1 if %winbuild% LSS 9600 (set kmsip=127.0.0.2&goto osttap) Right?
The initial release of KMS_VL_ALL by abbodi1406 worked wonders for me and I love the simplicity, best KMS solution so far. But with 6.0.3 and 6.0.2 I haven't been able to activate again, just keeps failing and can't connect to the local KMS server. I believe it has something to do with KMSpico being run at one point in between and hasn't worked since. I remember reading others saying that KMSpico leaves something behind in the registry or something that prevents other KMS activators from working. Does anybody recall what the fix for this was? Thank you!
Thank you so much. That is exactly the registry fix that I had seen previously and was looking for. These threads have become so polluted and messy since these KMS emulators started making progress lately and it's been more difficult to find the good information. I appreciate you finding that info for me, it fixed my problem. Also, yes, since the script failed it did leave the Tap adapter behind so I ran the remove script and that took care of it. Now with the registry fix the initial script runs perfectly and removes tap after properly. Thanks again.
How can I run this in a VM where all my computers can point to the VM server and get activated? Thank you
Anyone care to tell this complete noob how to use this? I've dlownloaded KMS_VL_ALL_6.0.3.zip. Do I need to extract this on my Windows 8.1 machine and then run KMS_VL_ALL.cmd as admin or what steps are needed to activate my license? Thanks in advance!