Yep, but the service does appear to start itself when one of the Office applications is first opened. So, as I've included in my notes for future reference... If installing Office 2010 under Windows XP (32-bit): After installation simply open one of the Office applications (such as Word) and then close it down again before running the activator Toolkit. This is done to start the Software Protection Platform service (service name under Task Manager: OSPPSVC.EXE) which is needed in order to run the Toolkit (alternatively, the service can be started by typing "cscript ospp.vbs /osppsvcrestart", without the quotes, into the Run box and clicking 'OK').
It's his tool and I don't quite understand how it works. Apparently activation is accidently displaying success even if it failed. I can't just rearm because those are limited. It needs to run and be on the actual PC. Anone else, the 8000700D is the keygen generating invalid data most of the time, but in cases where it fails 25 times something is wrong. A rearm is a possible solution. Some people have it where it gets stuck and doesn't work. Trying to fix this is difficult as we rely on the Keygen and can't see how it works or why I think I am going to change the way EZ-Activator does activation, to do it the way AutoKMS does it as it only activates KMS and does it one at a time so I can tell if it worked or not better
awesome thank you... i used this today to back up a retail installation and used it also to add back the tokens etc and it worked perfect. office 2010 was activated and is working perfect it passed all genuine tests as well. i did use the newest version posted which i believe is the beta one
Hi CODYQX4, Excellent job with the GUI and the toolkit worked like a charm on my Office 2010 32 bit Proplus..Just a suggestion, the toolkit window is now able to resize i.e., we can drag the edges, making it look clumsy..i think it is better to make the size of the window of the toolkit fixed like Daz loader, disabling the resizing part..
I only open autorun from cd and I then exit setup. I notice that this is created in registry. Maybe because that. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\Config\{90140000-0011-0000-0000-0000000FF1CE}] "PIDKEY"=dword:00000000 "CustomSetup"=dword:00000000 "Upgrade"=dword:00000000 "InstallType"=dword:00000000 "PreviousOfficeApps"=dword:00000000 "SourceType"=dword:00000005 "SetupVersion"=dword:129303e8 "SetupDuration"=dword:0000000f
.... lot of exeption .... i did little test, i got firewall and i blocked from lunch the CMD in program LOAD & EZ activate button and guess what i got lot of exeption put try & catch each time u use CMD /c ...
In fact we use try catch. If you get the exception in the console it's intentionally there, since it means that something unknown happen, and we want the user to have a little info about it.