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.
Yeah I cant repair the license cause office isnt installed coz i cant install it coz it asks for a product key, then says ive already used a trial product key on this computer.
In that case download Office 2010 Pro Plus. The latest version is broken on Channel Change so download Volume. Last I remember TS said a magnet link is up for it. Install that and it won't need a key.
Sorry i dont really understand. I should be downloading a different version of pro plus which doesn't need a key to install? Where do i get it from? sorry im a n00b at this sort of thing.
Click the second link in my signature, it should be there. you want the volume edition and it is a bittorrent download.
Not sure why but the key checker is crash happy. Has to do with the fact that I'm trying to run the DLL from temp, as I used to just do that in case office wasn't installed. I'm using a basis of C# code from MasterDisaster but it seems to crash a lot, and we added Thread.Sleeps to reduce the problems but it still seems to fail. I'm tempted to just cut XP support for key checking and use the windows built in PidgenX.dll as this problem is really annoying. I get a BEX error, usually after a second check and not the first.
What I'm going to do is use the PIDGENX on the system which will work on vista+. I will fall back to using Office 2010's if on XP. If you use XP and don't have 2010 installed the toolkit is basically useless anyway. This will make key check faster for 99% of people since I won't need those sleeps and it won't crash every other time.