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...
Dude I have done massive torrents and also had keygen failure for a few which led me to start my "alternative to KMS/Keygen" thread KMS works good as does silent task for my win 7/2010 but still sometimes I cannot help some dudes when they have probs even with clean installs so I get what cody is saying
Yes, localhost.dll is present. If I login with a local administrator account I get the DLL error. The full error is "You are attempting to open a file of type 'application extension' (.dll). These files are used by the operating system and by various progams. Editing or modifying them could damage your system. If you still want to open the file, click open with. Otherwise click cancel. " If I click on Open with I then get "windows can't open this file: localhost.dll". If I login to the computer with domain admin credentials I do not get the error.
Aha. So it is a permissions issue then? Do you think it would help to equip the launcher with a manifest that sets the 'RequireAdministrator' flag? In that case it would have to be launched with admin privs, otherwise it wouldnt launch at all...
I got the same issue on my w7Ent. I opened an admin cmd and ran lhstlnch.exe with no problems... I suggest you to create a task scheduler entry and run this as admin. PS: Be advised, after the lhstlnch.exe is set as a system task, you can not remove the lhstlnch.exe file...
Sorry folks...little time...will be back later. Just wanted to inform everyone that i found a bug; unless i was working with a wrong copy of the script, repeating the activation request in the Office section will start the activation request for Windows instead. (Small two-letter mistake, still mucho annoying.) Fixed version with a couple of extra options to follow soon. Please quit using and delete 1.0 if you can confirm the above, and please also refrain from distributing it elsewhere. (For obvious reasons.) Later guys...
Well, lets just say it is there when Windows asks for activation. Thats its only job, there isnt anything beyond that. Now for something odd. Originally i had no problem with Office activation at all. In fact it worked so darn well that i never had to repeat an activation request, which is also why i didnt catch the goto bug much sooner. Then something odd happened. By mistake i rearmed Windows, but i didnt reboot. Instead i just sent another activation request and thought thats that. From that moment forward i was unable to activate Office no matter what i tried. And trying i did, you can believe that. Deleted various Office subkeys in the registry. Result: Office doesnt care or tries to heal itself, activation still impossible. Deleted the entire Office 14 key in the registry. Result: Office tries to heal itself, activation still impossible. Deleted the entire Office 14 folder. Result: Office tries to heal itself, activation still impossible. Deleted tokens.dat and the cache folder. Result: Office creates a fresh set, activation still impossible. And so on, and so forth...you get the idea. The status quo is that Office seems to be totally and entirely shot. And right now i have no idea what else to try...
@ Phazor, don't know if it will help but have you tried using Windows Installer Cleanup utility (MSICUU2.exe)
Thanks urie, but i didnt uninstall/reinstall Office. What im trying to find is a fix so it accepts the KMS Host again, you know, like you rearm or -rilc Windows to restore the default lics. The odd thing is that Office seems to have the option to reinstall the lics too, its just not documented. I have checked a couple of its DLLs, and the functions to uninstall and reinstall the lics are definitely there. The problem is that i didnt yet figure out how to trigger it. However, it seems to be working similar to the Office rearm command, which is passed on from one file to the next to the next, etc. There seem to be at least 3 'hops' involved, but i would have to investigate this further to be totally sure. It would probably be easier to just delete something though. (Some file or regkey.)
Cody suggested to me to use his toolkit to delete licence then let it repair maybe even couple times then it's fine. Am I missing something...lol
Where do Windows and Office store what KMS Hosts they have had contact with? For instance, the last one Windows used can be seen under 'Registered KMS machine name' and 'KMS machine extended PID' when you do a slmgr -dlv. Where is this stuff being stored?
Right, he said he somehow 'destroyed' something...is it something i already tried (see my post) or something else? I had Office heal itself like a dozen times and still nothing...
BTW, heres a new 'trick' i stumbled upon: If you dont like 127.0.0.1, or localhost, you can also use the machines own name as Host Machine Name. Since using the machines own name is technically the same as using 127.0.0.1 or localhost it doesnt even have to be added to the hosts file. All other names can be used by adding them to the hosts file. (127.0.0.1 MYPREFERREDNAME)
Good news; after wrestling with this crap for frickin days i have finally found the solution to my super-persistent 8007000D problem with Office. The solution was not to delete any files or reg-entries, but simply to rearm Windows first. Order of actions: 1) Uninstall Windows PKey, rearm Windows, reboot 2) Uninstall Office PKey, rearm Office 3) Install Windows GVLK, activate Windows 4) Install Office GVLK, activate Office This worked right away. This means UniKMS 1.1 now has all necessary means onboard to fix a persistent 8007000D for both Windows and Office. As per SubZero5's suggestion i have also switched to a schedule-based Host Installer to get the permissions issues out of the way. localhost.dll will be launched by lhstlnch.exe 30 seconds after a user logs in. This allows the rest of the system enough time to load everything else. A couple of planned tweaks are still open, but a release should follow very soon now. Keep checking the thread for news...
Well, i dont think an installation could be any more screwed up than mine was. And i can repeat the fix at will, (i have a copy of the VM with the screwed up setup), it works everytime if done in the proper order. Anyhow, what was it you were doing? You said you 'destroyed' something...what and how?