Run the app, select Windows or Office and select the 'Install KMS Host' option. Reboot the system to see if the Host is properly started after login. Try the uninstall too while youre at it. Thanks.
Cool. Did it start up correctly after you rebooted or did you get any error like yngdiego? If it was properly started localhost.dll will be in the taskmanager...
Ok run it through one more time to be certain ok Where to start to finish so I can get it right including what service to look for Later
I installed this and upon reboot I receive a message : You are attempting to open a file of type "application extension" (.dll) and wants to know what I want to do with localhost.dll
Is this a Windows message or does it come from some security software? What were the options given when it asked what to do with the DLL?
The one and only. Im pretty sure i could disassemble and recreate it entirely but i: A) Think this would be a major disrespect towards ZWT, the group who brought us this ingenious little tool B) Dont have the time to do it anyway
It's a windows message. Not running any security software on this Win7 Pro 32 bit. (Not internet connected) The next screen asked me what program I wanted to use to run the dll, the usual chose a program from a list to run the file.
Well, the question is if remaking one would even solve the problem. It may well be that the flaw is not in the emulated host, but that it is simply a matter of how this host communicates with sppsvc through the loopback. Since ZWT are by no means beginners im pretty convinced that they did the best they could, and that they would have released a fix by now if it would help any.
Pretty odd. Right now i cannot reproduce this, but i will do further tests tomorrow to see if i can make such an error appear. Thanks for reporting.
So, youre saying you cannot activate Office with the KMS Host? That would be most odd indeed, because i have no problems with this at all. In fact it works just fine, and timesurfer just confirmed it. (See his screenshot.)
Now i understand. Its the same thing with Windows. Once it is 'shot' (persistent 8007000D errors) you will have to reinstall the lics (also achieved by a rearm) or it will never work. This was found out quite early in the process, so it doesnt surprise me at all that Office would react in the same way. Same volume activation system after all...