I can confirm that i didnt delete install AutoKms i just removed the PIDS from the file,all is well,great app guys. This was for Windows 7 pos embedded
Hi CODYQX4 first thanks for amazing tools i just update to 2.2.3 and have several question : 1. on setting it seems AutoKMS always set windows7 activation by default, shouldn't it better disabled? i mean before using office, most people will already active their windows using retail product, winloader etc. shouldn't having it enable might cause conflict ? or it need to be enabled ? 2. cmiiw from what i see, 2.2.3 always schedule to run re-activation on startup if i want to change it, it seems i need to use AutoKMS custom task, right ? how i can set activation schedule to once a month or other setting ? EzActivator just working without problem, but it just me seeing that reactivation once a month is better than every startup thanks again
That setting means nothing unless you have a KMS key installed for windows. Older versions didn't check it but did try to activate anything if you did check it.
I am running Win7, with a quad core proc, 4gb ram This programme 'ToolKit' locks up on me every time I try running it, be it normally or as Admin, it just locks up and I get nowhere fast
What do you mean lock up? Does it run and freeze? What functions we're you using? Any more info would be helpful
As soon as I try to use EZ Activator it just freezes and locks up, I also tried activating office on the activator tab, same thing, freeze and lock. I cant close it without using Task Manager
What version of office? I know some (the crap trials) add lots of licenses and OSPPSVC runs at 99% cpu (not my fault) when it goes through. Try again and tell me if OSPPSVC is raping the CPU at high percentage. If so you may want to uninstall all office and use Pro Plus VL if not already. Note if in your case OSPPSVC is the culprit, it will eventually work, just take an absurd amount of time to do so.
Im using 2010 Pro Plus. Toolkit runs fine and is 'stable' untill I try any of the functions, it freezes and locks within 2 secs, it using no cpu at all and Ive left in open for over 2 hours, still froze and locked untill I use task manager to clear it
Does it disable the buttons and start the progress bar? Also could you run a license repair and see if that works? I'm not sure what could cause it to lock up like that as it's never happened before.
it doesnt affect my PC at all, toolkit is the only none working prog once I try anything with it, I can access everything on my pc when toolkit is locked. License repair also freezes and locks
This is a screen cap of the frozen Toolking doing license repair, the freeze happened in about 3 secs
Are you certain its really frozen? Its supposed to run MSI at that point (or checking license info, hard to tell), and this takes awhile to do. Is the progress bar stuck in place? Do you get msiexec running processes during the repair. Also, you do have AV stuff off right? Most of the time that causes issues but never freezes, just asking as that usually is at fault for most issues that aren't quickly detected coding bugs.
Its defo frozen, theprogress bar freezes and thats what alerted me. I disabled my AV prog and even run toolkit as admin, same result
Problems in Win XP hi.. , I've tried to use this application to activate Office 2010 in Windows XP, but I can't . I got the following message: "unable to find a version of runtime to run this application" . I have NET.framework 4.0 installed, can anybody help me please?? ... thanks in advanced
Can people please start testing the Microsoft Toolkit? Don't let the alpha tag scare you, its 99% unchanged in office part. V2.2.3 OTK has 142916 downloads , just from my link. MTK R3 has 270 .
Where did you get the .NET 4? Try reinstalling it to be sure. I hope I haven't made it need .NET 4 Full (Extended) as MS is really pushing the client thing. Still doubt that is the case since I'd expect more of this if that was the case. Pretty much stumped on the freeze. Can't think of anything that would cause it. Maybe try an older version and see if that works?
Basically short of bugfixes, OTK is basically feature locked/complete, and I watch both threads. Stuck on further development until I get the feedback I asked for on that thread. Most of the stuff I want tested is the windows part, since the office part is nothing new there.
Yea that is good idea to go to one thread Maybe name change to Office/W7 KMS something for title Also get rid of alpha should be beta since your very close I'm sure People will test beta more probably Give redirect link to new thread In fact I'd get rid of beta altogether and just give new build number for new toolkit