AutoKMS effectively runs daily, keeping activated. If you needed to manually activate, just rerun EZ-Activator.
Yep, pretty much can tell funny things are happening, as that memory process injection code eventually has to execute and can be analyzed. I'm not getting any detects until it runs, though that could change. A lot of AV now have "trust" based scanning, as in AutoKMS is a virus because a few stupid people say it is and the companies say it is. You saw how cheaply Fortinet operates.
@Bosh I made a new way to switch the toolkit. I start it in a smaller window (basically remove tab control and move everything else up). Then the user presses a little Office or Windows button. This adds the tabcontrol and puts everything else back down. You can press either button and it changes the tab control, title and icon on the fly. This means just one window. I find Selector is annoying when I'm debugging builds, as I forget to close it and a rebuild fails as a result.
Yeah, at no point did I ever plan to make it have 2. I change things on the Form and it redraws to change. I change the window title, icon, and tabs, and it remains the same exe and process.
Yeah, I felt the blank space looked weird, but I'd like to make it expand in an animation if possible. Also, notice how Microsoft Toolkit uses the office icon. It would be nice to have a different icon, one that relates to microsoft but not the windows or office icon.
You can set a delay for automatic draw the form, using int variables, creating a simple animation ...
Just noticed something to change in AutoRearm. I do a lowest grace check, with default variable = 30. I then search all licenses, but condition of License Status code = 2. (0 is unlicensed/no key, 1 is activated). I should make it >= 2 instead of == 2, because Notifications Mode = 5 and there are weird grace states in between. Theoretically the user is unlikely to get there but I'll change it anyway. This is probably the only change I've made to it. According to AV, my AutoRearm is barely used/known, but it has a lot more safety checks I'd like to see in IORRT. The checking of the days prevents overwriting activation. If a user installs a rearm tool, mine will not nuke office if activated, so if a user forgets and MAK activates, they won't lose it. Still, the one thing I'm stuck with is if the user has multiple office. Given a rearm effects all of them, if one needs activated I rearm, as otherwise one app would stay activated and one not (better to rearm than let the one app die). Still if the user activated before installing that activation it will uninstall and reactivate. This issue is a non concern given MAK activations are few and far between, and most users install one app. Just another reminder that if you rely on a leaked key for activation, you should use OTK/MTK/ATM to back that up ASAP. I got a MAK from school that had a short enough window to activate and backup on my new laptop before it ran out of uses (note it is not leaked and is empty so don't ask for it and I wouldn't leak it anyway).
Hey thanks for that info Cody If you wanna help do checks that is fine but the only thing I've experienced with IORRT was when someone installed another app after IORRT had already been installed...lol That killed it but they just can uninstall and reinstall I think I forget if they have to KMS activate again to fix? Regarding the MAK keys I think the whole MAK leak for 2010 is over so I'm not too worried
Yeah there's only so many things to check. I figure that I detect if IORRT is already installed, and hope they wouldn't do anything like install it over the top. I was referring more to the way that I have this day check, but it was messed up. I believe you just restore daily and don't worry about that. I haven't seen any new keys but I'm glad as they only complicate things, with people assuming Office can be preactivated because somebody ripped someone else's torrent and put a new key in, claiming it "Works forever" to get mass DL+Rep but the users find out there is an issue and ask later how to preactivate office.
I did clean install win7, then office then used your tool to activate it and KIS2012 didn't complain about AutoKMS like last time, go figure