No, as I was forced to make the app 32 bit and now rely on a .NET 4 function to get past registry redirection. This was needed to make the RAM Keygen execution work.
Quick question for the developer of Office 2010 Toolkit/EZ Activator (or anyone knowledgeable). It seems to me that you can either go down the windows 7 ULTIMATE route and use apps like RemoveWAT or Daz's loader to activate windows, or you can go down the windows 7 enterprise route and use your 2010 Toolkit/KMS Scheduled task activator to activate windows ENTERPRISE. My question is, whilst it is possible for windows to patch the apps like RemoveWAT as they have done in the past, wouldn't it be impossible / substantially harder to patch the Auto-KMS activator? Thus, isn't it more logical to choose the Enterprise Auto-KMS route to activate windows over the alternative ultimate route as it is highly unlikely / improbable that the auto kms activation method will ever stop working or be patched by Microsoft? Does this logic also apply to activating Office 2010 via Auto-KMS? Will the auto-kms for windows 7 / office 2010 ever stop working? Is activating windows via auto-kms more 'foolproof' and clearly a better choice than activating via loaders / removeWAT? IE: Will windows ever be able to tell it was activated using an auto-kms activator instead of a legit KMS network server? Is there a detectable / patchable difference? Sorry for repeating basically the same question so many times .
Since both Professional and Enterprise can be KMS activated, I see not reason to install any other types of loader/by-pass. With KMS, all you need to do is make sure the EXE is always running locally and you are always activated. If you do not like the local exe file running, you can always activate to one if the internet based servers. I have both Office and W7 activating to the local KMS file.
The loader is safe, but RemoveWAT is a sure fail as it is easily patched. KMS is good and MS actually gave up on Office Validation because the only hacks for activation were KMS. KMS or Loader I'd say is the best choice, but I feel KMS will be around longer. OEM activation in its current form may change before KMS, but all products out now will always work with the Loader or KMS.
| Well, in my personal opinion there's nothing better to activate Windows 7 than Daz's loader. RemoveWAT modifies Windows files and that's why it's easier to detect, Daz's loader instead does all it's work before Windows starts so it's a LOT harder to detect without affecting legit users. For enterprise you have to reactivate every 180 days, so for me it's Daz's loader once and done. Office is another story, it does not have the same retail activation method as Windows, so we're left with just Retail keys, MAK keys(which are hard to find), and KMS. Retial and MAK are runs out of activation quickly (those are mostly not shared anymore), so we're left with KMS for activating. We do not have a crystal ball to know if Microsoft will or could ever kill Daz's loader or KMS activation, but right now they are the safest bets. Hope it's clear Bosh
CODYQX4, is this activation tool definitive or will I have to run it again after 180 days? Thanks! =)
@leomenassun Under default settings the tool is schedule to run at least once every 24 hours. One condition is whenever you boot up the computer and the other is 24 hours from the time is was last booted. It will never let the PC wait til the 180th day unless you configure it that way. Hey acrsn, sorry didn't notice you post before. got problems with my refresh
I believe his daily task uses my original task re-creation concept as I did with IR5/IORRT so that daily at same time last activated does new daily task get created at that exact moment hence new daily task is re-created at same time activation is done or at boot for office So really with Trilogy's IORRT it never gets past the 179/180th day although rearm concepts work within 30 day time frame...lol
Well it still sets the 24 hour trigger when it runs, but there is now just one task instead of when we needed 2. My code allows for multiple trigger creation, unlike the exe used in batch, so I have one task with 2 triggers. But it works the same in practice. I effectively keep it from counting down assuming nothing has changed that would lead to activation failure (like AV or the user has changed office so that the PID in use no longer works, which the latter is fixed by running EZ-Activator).
Well it still sets the 24 hour trigger when it runs, but there is now just one task instead of when we needed 2. My code allows for multiple trigger creation, unlike the exe used in batch, so I have one task with 2 triggers. But it works the same in practice. I effectively keep it from counting down assuming nothing has changed that would lead to activation failure (like AV or the user has changed office so that the PID in use no longer works, which the latter is fixed by running EZ-Activator). EDIT: Connection crapped out and caused a double post.
Hmm crappy connection leads to the dark side Banned for not deleting second post So you have combined daily and startup in one task that when run uses the auto re-creation task concept at time task runs...lol Impressive... I haven't been watching your tasks as closely as I should have
everything is back to normal, had to delete it manually from C:\Windows\System32\Tasks because I didn't see AutoKMS in the list. Probably it was from the repair install
Making progress on the next tool. I have to decide on some UI stuff so I'd like to ask. Currently I'm working in the Office 2010 Toolkit UI as is, and added 2 buttons. One for windows, one for Office. Whatever is applied decides whether something like the activate button applies to office or windows. However this is inconsistent, as the License Files and Key Checker dictate that based on the comboboxes. Also some functions will never have a Windows equivalent. There will not be a windows channel changer. I'm thinking of making a selector that will spawn a window for either office or windows, so the windows one wouldn't have office only functions and I could change the UI in a way that worked best for both (it is difficult to combine them in such a way that makes sense for both. I plan to move the EZ-Activator button to the Activation tab, which would be 100% the same except for no AutoRearm on Windows, and add more information on the Main Tab. @Bosh I'll mess with it some more and see how it goes.
Yeah, 99% of the windows code is buried in OTK and not used. Basically make a UI for Office stuff and another UI for Windows, but bundled together to have one app to download. I have a launcher that can create a window, basically I make a different window for windows and luanch that instead. I am working on windows EZ-Activator now (it will handle KMS but be simpler than office given some things can't be done or are unneeded). I still need to write windows backup code, which shouldn't be too hard. PS:Notice that AutoKMS activates windows and you can install/uninstall windows keys if you select them. All Activation tab functions have working windows functions but you cannot trigger them in OTK. But they are there and have been for a while.