Hello MDL Community. I'm very sorry for my noob question(if it's too noob for you just ignore), i have read the anti-noob topic and there is no question like mine neither on Google nor on the 1st and 2nd page of MDL. Still i hope you can tell me some good arguments for and against one of the programs.
all MDL "approved" tools like the ones you mention are as reliable as the current time/day allows to say it activates your system. neither developer/coder of these tools knows what is gonna be tomorrow or the day after. So take one of the MDl tools as the ones that get you activated atm, period
Hi and thank you for the fast response. I will use KMSPico as it is not marked as like MS Toolkit though the 1st one was killed by Bitdefender immeditely after download. I will add the Respectful exclusions and make a token backup. Have a nice day.
I used Windows Loader for many years, but after Microsoft Toolkit came out I used that. My only wish is that they would allow you to do a silent activate/install of it so MTK could be ran during installs. Never used kmspico
loader is for 7 and server only left over. Newer system cannot be activated with that tool. MTK and such new developments only can do the magic as of now
Supported systems activating: Microsoft Toolkit - Windows Server 2008, Windows Vista, Windows Server 2008 R2, Windows 7, Windows Embedded 7, Windows Server 2012, Windows 8, Windows Embedded 8, Windows Server 2012 R2, Windows 8.1 and Windows Embedded 8.1. Windows Loader - Windows Server 2008, Windows Vista, Windows Server 2008 R2, Windows 7, Windows Server 2011 and Windows Server 2012. Windows Server 2012 R2 maybe soon.
Well... they will either work, or they won't. If you want to know which one is more LIKELY to work, I guess it depends on their method of installing/use. They're both based on the work that was done in the source code thread, but perhaps they implement them differently. MTK typically has better coding practices and tests everything more, but takes a bit longer to release newer versions. (Can't fix what isn't broken, amirite?) KMSpico is like a community feed-back based activator. heldigard tries almost everything. Sometimes it can be a positive change, and sometimes it can bring about new problems. heldi is like most of the rest of us that basically test something a few times and if it works for us, we upload; where CODYQX4 tends to do a lot more debugging. For methods, certain people have problems with tap adapters to bypass the localhost block in win8.1, so windivert or the secohook are better methods if that is the case. From my testing, windivert 1.1.1 seems to function flawlessly (at least on x64 OS versions) secohook seems the most promising, but it's also the least future-proof since MS could release an update to their sppsvc.exe at any time.
I find MTK great not only for activating. However, since I have a legal key, it is a equally great tool for other functions such as integrating installers/updates (office 2010, 2013). So far it has worked for me 100% based on what I wanted.
I've used MS Toolkit to activate Office on a friend's computer with no problem. Used KMSPico recently on my other desktop with no problem either. Not too sure on the advantages or disadvantages of either, but I was actually leaning towards using MS Toolkit first, but then noticed KMSPico.
microsoft toolkit is better than KMSpico because microsoft itself provides it as its name "Microsoft" Toolkit.