Discussion in 'Windows 8' started by CODYQX4, Dec 17, 2013.
what does bypass local host mean/do?
Just a quick question without knowing the slightest bit about how kms works and on 8.1.
Couldn't one just have their KMS server on their own machine, pointing it at a remote IP whether it be internet or intranet, add a HOST file entry where that remote IP is diverted back to their own machine and it work that way?
Personally, my favorite is the TAP
I have the same worry, i know that many AV are more sensible to dll injection, bot for now with eset 7 i had not problems.
I voted for dll injection, i tried it with your tool on 4 machines with no problems, all activated, both 8.1 and office
Is there no way to block the serial port profile then use kms? I voted for dll injection, it always worked for me until i used the skype bypass anyhow
Would it be difficult to implement all 3 into MTK for people to choose / alternative methods if one fails ?
Personally I don't mind so long as it gets the job done - Voted TAP because it has always worked for me so far
lol ... you took the word out of my mouth upon having a choice
edit: @Cody take your time guys and everything gets perfect
cody already implemented all 3 into MTK, he is just taking a poll to see which should be the default method
you can choose the method in settings
DLL injection is my favorite, since my OpenVPN likes to have TAP adapter for its own only. )
Since I have disabled AV four years ago, I got not only faster PC, but rescue from those fake alerts too.
BTW: @BigMuscle did his Aero add-on based on DLL injection without single AV popup.
It's good to see that you want to know what your user base likes, and tailor MTK accordingly. However, I have a doubt (feel free to bash me if it's a stupid question).
A vast majority of the users of MTK are people who barely know what the three methods mean. So just asking what they prefer, without giving them a quick and short intro to all three methods, might not be such a good idea. Of course, I assume this survey pertains to people who actually look into MTK beyond the minimum two screens, but that automatically renders this moot since they can definitely change the activation method to whichever they want. And someone too impatient to open the configuration screen is probably no pro. Just sayin'.
In other words, the noobs don't know what they're doing, the pros don't care what's default (I think), as long as something works. I'm no noob, but I'm no pro either. I have a vague idea of how TAP and WinDivert work, which I gleaned from the internet and prowling all over this forum. And as for the DLL injection thingy, I didn't have the foggiest idea what it was about until after Tito told me. And now I have a clearer (but NOT complete) understanding of it.
Maybe, just maybe, this survey would be more effective if you pointed out the pros and cons of each method and then allowed people to choose between them... but that's just my opinion. Also, I'm a big fan of your work.
A tip of my hat to you, good sir.
As pun said
A little more info on how each one works I understand using the tap connection but not sure on the DLL injection i presume it replaces the DLL that stops KMS activation through local host
WinDivert Client I need more info on thanks
I will vote when I know a little more
I prefer dll injection. I don't like the tap adapter always flashing unidentified network at me.
AFAIK, WinDivert works the same as TAP except that it doesn't install an adapter.
And as for the DLL injection, it effectively removes the localhost check in memory so that Windows/Office can be activated by an emulated KMS server running on the same PC. (Source: Tito)
While that is a good start, it isn't enough for non-noob non-programmers like us So yeah, a little more clarity would be real nice
Having considered that and having tested them all, in an ideal world I'd go for starting MTK with DLL Injection as the default. However if there is concern that future AV methods may not like it, then maybe WinDivert as the default startup may be sensible.