Anyone have a problem with 32bit office on 64 bit windows getting activated? 32bit office on 32 bit windows its ok, 64 bit office on 64bit windows its ok. Made changes in the code: Code: cscript "%ProgramFiles(x86)%\Microsoft Office\office14\ospp.vbs" /inpkey: cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /sethst:127.0.0.1 cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" /act cscript "%ProgramFiles(x86)%\Microsoft Office\Office14\ospp.vbs" also its 30 day grace period in the command prompt, not 180 days.
Yes, i did also try Office 2010 V2.05. Works ok with 64 bit office on 64 bit windows, says its activated. But 32 bit office on 64 bit windows still says it needs activating did change the bat to "%ProgramFiles(x86)%, but still no luck.
Next thing you wanna do is download VAMT 2.0 and try to manually activate it with the keygen.exe open on the side. And then activate it the normal KMS way using the VAMT 2.0 tool it should work like a charm as it has had a good success rate... Unlike some other stuff I can assure you this will work ...
Frankly i dont know, but i do know that the KMS Activator will work with the VL versions. (Which IMO is still the most elegant way because the activation is 100% authentic.)
@ Phazor: Hi there! Nice to see that you want to create a nice KMS Activator!! <3 What I would like to see in it (no must, but would be damn nice): -nice gui to choose the options from -a pop up after activation what say wheater it was succesful or failed -maybe some kind of activation status in the activator gui (see DAZ's Windows Loader --> untouched activ, activated, etc.) -showing the serial if possible? That would be awesome! Best Regards, kokosmann BTW: REP+
Well, all of what youve proposed is already implemented in KMS Activator 5.0, so 6.0 will of course have it as well. (FYI, 5.0 already supports Vista/Win7/Servers and 6.0 will have that plus Office capabilities.) You can make other proposals though...im not starting before the weekend...
Wow thank you Phazor. I am almost ashamed of asking but where can I find your KMS Activator 5.0? I just used the search but didn't find anything. Sorry, but is that activator already released? Where is the thread? Sorry for that again. Best Regards, kokosmann
Hey guys, not to flame it but I would be careful if you used the Mini KMS activator from wzor! I ran a special tool by ESET called SysInspector(Free tool) and it told me that the KMService is rated pretty risky! The thing that really bothered me about it though, if it is supposed to be an emulated KMS then why is it connecting to some place on the internet? Those connections are also rated pretty risky! This is just a heads up because the keygen in Tuvi's method is not appearing that risky, same thing for Phazor's activator.
Well I suppose there was a reason why I didn't post the Mini-KMS thing on the Office 2010 Repository as I don't know what the heck it does and personally I trust Tuvi more than I do some Russian (silly Russians) I haven't even heard of. I'm inclined toward Tuvi's way cause I've seen the source code and everythign...
If one goes by this, what advice would you to give under the following situation: 1. somehow TUVI's method has not worked for me. 2. made a system image before office 2010 3. installed office 2010 volume 64 bit and activated with mini-kms If I go back to system image (without office), reinstall office 2010, hope for Tuvi to work. If it does not work, and I do not use mini-kms, thus remaining unlicensed, what is the activation period/grace and what happens after that (product goes from unlicenced to activated with serial key). Will I get only popups or something else. I can deal with 30 days trial anyway hoping for a more robust activator before then/robust way to work with retail edition. If nothing comes till then, go back to system image (minus office 2010) and install office 2010 again. How does this sound.
That ain't lookin soo good man... that kinda sux too... I would try doing a complete uninstall down to the registry entries and then doing a disk clean up afterward... cause it looks to me like some of the registration from the uninstalls you have been doing have been left behind ergo not being able to do jack diddly with activating via KMS...