This may sound like a dumb question, but can anyone tell me if abbodi1406's KMS_VL_ALL_6.1.1 (WinDivert Client) is only for activating VL versions of Windows 8 & Windows 8.1? I mean to ask if can also be used for other Windows versions (like Win 7, Win Vista, etc.). Also, can KMS_VL_ALL_6.1.1 (WinDivert Client) be used to activate Microsoft Office 2010 VL or Microsoft Office 2013 VL editions? Or, is it only for Windows 8/Windows 8.1? I apologize for asking this question if this has been already covered elsewhere. Thank you to anyone for some help on this.
Is there any benefits one way or the other to picking either KMS_VL_ALL_6.1.1 (WinDivert Client Bypass) versus KMS_VL_ALL_6.0.6 (TAP Adapter Bypass)? Maybe abbodi1406 can shed some light, or anyone else who knows the pros and cons of either tool? For example, is one of the above more stable than the other? Does one tool work better with certain systems versus the other? I am just wondering which tool I should use. Lastly, if I have Win 8.1 already activated via retail then if I use one of abbodi1406 scripts methods above to activate Office 2013 VL edition - will it mess with my Win 8.1 activation in any way? Thank you to anyone who can shed some insight for me on these concerns.
Glad to hear that rpo. So you used abbodi1406's script with Win 8.1 being retail activated, and it didn't touch that but only activated Microsoft Office? Which script of abbodi1406 did you use by the way - KMS_VL_ALL_6.1.1 or KMS_VL_ALL_6.0.6? Does it matter which script one uses - any pros or cons to either script? Thanks for you input.
There's nothing much to it. This script works by setting up a "dummy" KMS server, which always accepts any activation requests. Now the tricky part is to make this server accessible to the system itself without an internet connection. KMS v5 and prior allowed you to set this server's IP address as localhost (127.0.0.1) but KMS v6 caught on and barred that. So all these tools work by catching the activation requests and redirecting them to the local KMS server. Do you get it? Instead of redirecting at the source, you're doing it in transit. And there are two ways to do it: TAP and WinDivert. Here is a drastically simplified explanation. TAP is a virtual network device. It is an adapter that "taps" some other device's traffic. WinDivert is a package that is capable of capturing, sniffing, modifying, (re)injecting and redirecting packets. The difference that an end user cares about? Almost nothing. There is no need to install a TAP adapter in case of WinDivert (I think...?) Bottom line: Use whichever you want to. In the unlikely event one doesn't work, use the other, and if neither works, come back and ask abbodi's tool is brilliant; just like its creator. It smartly finds out which of your Windows and/or Office needs to be activated. Legit installs are left untouched. And no, the pros and cons across versions are not something you would notice as an end user. If it doesn't run once, you're just unlucky; try again. If it doesn't run twice, you're doing something wrong. Hope this clears up things. Cheers Also, you don't have to worry. This script is the best out there. Just try it out first instead of trying to figure out how it works. What's legit stays legit. What's not, er, becomes legit.
Pun, Thank you so much for that terrific explanation. I understand much better now, l will try one method first and if it works then I am all set. Also, thank you to abbodi1406 for creating such great scripts and sharing them with us at MDL.
<Off topic> Did anyone notice, this thread was started on 25th October and has already crossed 1 million views? There is also a thread for KMS activation of Windows 8, started in August '12, and that has about 3.5 million views. Looks like there are many takers for 8.1 after all. </Off topic>
Didn't notice.. but now that you mentioned ... KMS seems the way to go... now that bios mods have been deprecated