Sorry, but besides the "Extra context menu item" (which I think it does nothing) there are none Office programs
Maybe it has to do with a previous installed version of office? I had office 2007 installed in this netbook (official license), before I installed 2010. So far I tried pretty much everything i could. Will try to reinstall later once again.
Guess who built the first ISO using V2.1. Things are getting much closer if you ignore the RAM Keygen.
Running it form RAM without ever writing it to disk, Phazor does it somehow. This makes it so AV can't delete the keygen.
Hey all. Just wanted to say a big thanks first for the work on this. I have run into quite a roadblock on one of my computers with it though. Functioning great on others. Enviro: Win 7 64bit, Office Proplus VL x64, avast with exception, comodo wall with autokms added to trusted files. Breakdown: Installed 2 weeks ago. Everything went smooth, autokms was running. Every day autokms reset to 180. A couple of times i did allow osppsvc.exe with firewall, was worried about that, but imagine its routing locally? Then 3 days ago I noticed I was at 176 days. Attempted manual activate, failed, with no error log beyond <failed to activate>. Was talking on phone and like an idiot hit rearm. That set me to a 30 day grace period. Strange. Tried another activate and then rebooted and viola, 0 days grace and apps are in notifications mode. All attempts: uninstall and reinstall license, key etc fail. This is with av and firewall disabled though I added exceptions and was functioning before. So I uninstalled, used uninstall script from toolkit to clean up after, reboot, reinstall attempt ez activator, all attempts fail, 0 days grace, no rearms! No matter i do, whatever angle or process, I am in notifications and have no rearms and no grace! Have now uninstalled and reinstalled 5 times, both as x86 and x64... Is there anything I could look for to try to determine what is happening? I tried running kmsemulator as admin while I fire an office app (yes I read almost this whole thread) and absolutely nothing happens, it stays blank. Another symptom, after an activation attempt, kmsemulator seems to get locked, i right click on it and dont get a menu, and I cant delete it, says I need permission. When this is occurring the toolkit always barks "failed to start kmsemulator". It will sit there locked until reboot. Logfile on first attempt and then when emulator gets locked: Code: ------------------------------------ AutoKMS Ran At 1/29/2011 9:12:13 AM. Successfully Checked Installed KMS Products. Professional Plus KMS Installed. Successfully Set KMS Host To 127.0.0.1 Started KMSEmulator.exe Attempting To Activate Professional Plus. Failed To Activate 10 Times. Stopped KMSEmulator. ------------------------------------ AutoKMS Ran At 1/29/2011 9:20:31 AM. Successfully Checked Installed KMS Products. Professional Plus KMS Installed. Successfully Set KMS Host To 127.0.0.1 Failed To Copy Or Start KMSEmulator.exe Attempting To Activate Professional Plus. Failed To Activate 10 Times. Stopped KMSEmulator. Sorry bout the long post, but since you are devving thought you might be interested in how I manged to break your good work. Thanks again, as i say, working great on other machine with exactly the same enviro, av/wall.
Likely things are stuck. Too bad you use x64 like me as Phazor has a 32 bit KMS tool that succeeds in the rare cases mine won't. I've found that the License Repair + EZ-Activator works 95%+ of the time IF AV is totally resolved (and this included Windows Defender and Windows Firewall as Windows Firewall once blocked someone). For the 5% it doesn't people have either in a last resort did a total OS reinstall which is a bit extreme, or used Phazor's tool and his KMS magic activate it. It doesn't work on x64, but if you used it to successfully activate where everything seems to fail with any other KMS tool, then you could keep using AutoKMS as is to keep it at 180 days. I hope he can get x64 worked out.
He said notifications + 0 rearms + EZ-Activator not helping, so unless he gets EZ-Activator_KMS working (and that would mean he could keep using the already installed AutoKMS), AutoRearm won't help.
Thanks for the response, I suspected it would would be a drastic move. Before i do an os reinstall, I'll try to debug the windows protections, did have the native disabled firewall up watching inbound/outbound during firing, no event there. In regards to notifications mode, I have 30 days with the nasty red bar/prompts, right? Also, i did not purge office registry entries, should i do some regedit scrubbing? Thanks again guys. Off to work now but will experiment this eve.
I missed that ...lol Then he should uninstall with toolkit, reboot, reinstall and do EZ again and it will work?
Did all of that! 5 times over, on both an x86 and x64 office fresh install. Something is sticking around, no idea what.
Basically it's a problem that us KMS guys in 2010 have been working on but basically office always reinstalls in same status regardless of reinstall. OS reinstall is only way to clear what we haven't been able to detect
I remember that I needed to delete the whole "Office folder" in the registry, and also delete all traces from office in the "application data" and "Common files" folders in order to completely wipe out Office, but again, I'm not sure that it will work 100% of the time. There's still a lot to find out about Office installations
One of the things that make it hard is there are so many office related reg keys created (not even connected to licensing directly) that would be impossible to find and delete all of them. The only time I was able to break office and reinstall without it retaining notifications was to install Office 2010 in a XP SP3 clean VM using Total Uninstall to monitor Office 2010 up to the point I purposely broke it by running license repair right after install, then immediately uninstall using Total Uninstall (without ever using Office 2010 which may have added more stuff), and the log was so massive that just looking at the reg log (files are much easier to clean than registry) was enough to crush anyone's hope of this. Also keeping in mind this was just Pro Plus x86 which x64 and different SKU's would have different/more reg crap. PS: I also went through the massive reg log destroying anything and everything that jumped out as conceivably at fault but leaving the rest alone and it wasn't enough.