Sorry bud, I'd edited my post as I thought I may have rushed into the AKV.exe/AKS.exe testing, was a minor bug (now fixed) and no one else had posted so I edited it out. I was also curious about what the KMS Client Emulator did in this new WinDivert method, you will see abbodi1406 answered that it was to verify the status of the server but has now been removed. You're telling me it's hard to keep up!!! I struggle too! No I can't test on x86, maybe someone can post helping you. AKS.exe/AKV.exe are new executables of the whole thing, silent and verbose options. They (which one you choose) are all that is installed when you install the scheduled task. You can also run them as a standalone exe for one off activation. And there's a Delete-Task.cmd too. @abbodi1406 - Have now also tested the scheduled task (WinDivert method - TAP is a thing of the past for me now ), very nice indeed. My preference is for some output so I obviously tested verbose, edited the task to At Logon and once again it performed flawlessly, again I tried many times while online and offline, successful activation every time. You have produced a very polished complete solution here, very well done, it's great stuff. I've now tested the WinDivert scripts, exes, and scheduled task, and exes as standalone's - every time it all worked flawlessly. For those who like a GUI there is MTK in development but for those who like a scripting solution this is an excellent bundle. Thank you again.
Tested ten times on 8.1 x86. Five times with connection. Zero failure. It goes without saying, no BSoD either. Also, Abbodi, am I correct in assuming your birthday is on 14th June '86?
Abbodi's script working perfectly fine here also (x64). Thanks for saving me from tap, this is much cleaner. Now only bake the scheduled task script into the main script and we have an unattended activator. Set and forget. Very nicely done, thanks again. Cheers.
Thank you, abbodi1406 abbodi1406 - I have just tested your "KMS_VL_ALL_6.1.1 (WinDivert)" on Win 8.1 Ent. x64 with Office 2013 x86 and it worked flawlessly and quickly both online and offline. Everything I have already used is destined for the bin. Your latest is the Ultimate. Well done, abbodi1406. You are amazing. (Stop floating around the room, please )
@abbodi1406 Just tried KMS_VL_ALL in a VM. No problem for the WinDivert version. Good job! With the TunMirror version i got this: Error.. TunMirror is not functioning. Press any key to exit... VMWare, Windows 8.1 Pro VL x64
@abbodi1406 Windows 8.1 Pro VL x64 KMS_VL_ALL in WinDivert version: OK With TunMirror version Error.. TunMirror is not functioning.
Was able to activate my VM Windows 8.1 Pro VL and Office 2013 VL Code: KMShost:danikan.no-ip.biz KMSport:9872
It doesn't crash on every x86 system, but it crashes *more often* on those systems. The crash happens when you taskkill the fakeclient program qad has reportedly found a way to fix it, but all kernel-mode sys drivers have to be digitally signed, or you have to run your computer in a special test mode So he's reporting the stuff to the guy who runs windivert I don't have an x86 native system that has the crashing problem, so I can only really test on a vm. I know, for me, core N x86 win8.1 likes to crash when taskkilling fakeclient on a vm. We'll be checking the windivert site every day in hopes of a new driver that won't crash when divertclose is called.
The WinDivert author fixed the bug and released a new package (v1.1.1, of cource including signed drivers). I confirmed there is no BSOD on x86 system.
Nice, I don't see it on the site.. but I'm guessing it will be soon AHH just showed up when I ran ctrl-f5 Nice... we'll see if we can get these integrated asap. thx for the help qad
Who is going to summarize abbodi1406's and murphys78's scripts and implementations? The two works are remarkable.
They're based off of qewpal's work on KMS_VL_ALL They're more of a proof-of-concept work than a fully fledged activator, though they can be used as one. I believe CODYQX4's 2.5.0 stable version will make all of these 100% obsolete. These kinds of scripts, while easy to create and compile, are very basic, and not very well tested. They rely heavily on the success of other programs. The main purpose of these things is to prove/debug drivers and methods so that CODYQX4 can implement them correctly. I, personally, have no intention of trying to get people to use this over MTK because it's quite inferior when you consider how well CODYQX4 tests and handles exceptions and errors. This is like a team effort to get the best activation methods going. We're like a 40s-style boxer. We'll take all comers. CODYQX4 has even begun to test using another tap adapter, so that people who have compatibility issues because of existing VPN software, will have another option (steganos etc) That's pretty much it. When CODYQX4 hits stable on 2.5, you can throw these all in the archive till the next windows version, where we have to test new ideas again.
@abbodi1406 and murphy78: great work guys on your new updates but just a little personal problem i'm facing some time ago hope you guys can help me with: Spoiler View attachment 25694 View attachment 25695 now the above pics. shows a happy activation success but, i don't have office 2013 installed , i've uninstalled it several weeks ago so what am i missing here? @abbodi1406: you might consider this update in future release: Spoiler @murphy78: you might consider this update in future release: Spoiler it's funny each of you made an essential update separately thanks for your hard works, appreciate it so much