can i run it as admin and still have it worked when logged in as standard user? or should i login into standard user account before using?
In v2.2, I also am unable to set the Office installer path. Clicking on the button doesn't do anything. Win7 Pro x86.
dear cody, i've downloaded the V2.2, but my antvirus (Kaspersky internet security 2011) is detecting as virus " HEUR:TORJAN.WIN32.GENRIC". but earlier versions are not detected by AV. i just freshly nuke my PC with Windows 7 because ealier my system's registry comletely damaged with OSPP tool. it is preventing to install Office 2010. till now i didn't install Office 2010. i want to integrate Service pack1 with Office 2010 Installer package. is 2.2 is safe or i should go with 2.1.6? chandu
Cody doesn't include viruses ...lol AV always target toolkit and emulator, etc... Create exceptions or turn off AV do your thing then try again
Go to KIS -> Settings -> Application Control -> Applications. Then from the program list, find the Toolkit, right-click and Move to Trusted KIS - and any other security tool for that matter - can't have a way of knowning what's malicious and what's not. So, it correctly picks programs such as Activators (since they attempt to make system modifications)...
I am having the same problem as these guys! Could a link be posted to 2.1.6 so I could see if it works? I am on Win7 Ultimate SP1 x64 if it matters. Thanks!
Broke now on me. I'll have to look into sometime. Changing to .NET 4 must have broken it, as that code hasn't changed for a long time.
OK simple fix for browsing fail. Turns out for some strange reason those buttons lost thier association with their click action. That means clicking them does nothing. Two clicks in VS2010 and it works again. To help 2.2.1 come out quicker, please upload the pkeyconfig.xrm-ms from Multipoint 2010, just DL it and get. My connection is too weak to get the 3GB download.
CODYQX4, what is update KB2413186 ... something about validation stuff. Will it work with your tool ???
File validation, nothing to do with activation, rather a security feature. Also no updates mess with the toolkit, which is likely update safe since nothing I do can really be beat by an update, as opposed to a file crack or exploit.
Ok, also your 2.2 update shows as virus with avira. I never got this with other releases from you (to test).
The RAM stuff is to blame, nothing I can do but I 'd rather it be the way it is now than the way it used to be. Now people know AV is a problem from the beginning instead of getting the surprise when they install AutoKMS and it fails every time.
Help please? Hi, I'm new here. I installed the Office 2010 Home version first, with a trial product key. Then I downloaded this file, but it said the license was corrupt. I chose repair, but it said it couldn't retrieve a product key for that version of Office. So I used the remove office utility in the program I downloaded, then downloaded Pro plus. Tried to install it with the trial product key given before using the program to activate it, but the office installer said that I couldn't use that product key because i had already install a trial version of office on my computer, even though I'd removed it. I tried 2 different product keys, the same result. Can anyone help me with what to do? much appreciated.
Thing is I have removed keys for retail stuff, may re-add the 3 main just for this, but you could run repair again via toolkit and then install license for Pro Plus then run EZ-Activator.
@Bosh I know it's a long way off but I thought of a nice idea to still support office 2010 when the next version is out. Basically store our resources files externally, and if the users want old support they DL the 2010 file. This is to keep Office 201X toolkit smaller, as it is the biggest MDL app as far as I know in terms of MB (all those slics and patches). I don't want people to DL a 100+MB app (or upload it, my connection sucks), just so I can support 2010 + 201X, and it would be a shame to kill 2010 support when 99% of the code is likely to transfer over. We'll try to migrate to this eventually, but won't bother for awhile since who knows what the next office will throw at us. @Everyone else, would this sound nice to you so one tool can keep old support without forcing other people to DL a large app for legacy support? I'd basically pre bundle a 201X office resource file and you just download the 2010 one if you want 2010 support and it will detect it, and use the right one based on office version detection.