As you see, the C004F074 is the same error with domain connect as localhost with no active KMSEmulator. It means that clients are getting no response at all from your DNS enabled PC. Do try the firewall though, from my experience you can let Windows Firewall block KMSEmulator and it function locally, it can be a whole other world for across a network. I'd try all security software and router, be certain the port is open, and god only knows if the issue is on the client, server, or something going wrong across the network beyond your control. Some ISPs I hear block ports, you'd have to check this as I cannot, but it shows the cases. All is right with the AutoKMS service though. If its running locally it is running right. The issue exists elsewhere, unless KMSEmulator won't work over the internet, which I doubt.
Dear guys, I have this common error "Failed to inject memory" when I click to activate the EZ-Activator. For the information, I am using Office Toolkit 2010 2.2.3 and can't seem to find any working solution on this thread. Actions taken so far : 1) Disable all anti-virus protection 2) Installed microsoft framworks 4.0 Please someone can you advise me on the next steps or counter this error. Millions thanks in advance Natee
@natee19 In Settings, in the EZ-Activator tab, untick the options: - Change KMS PID on failure - Change CMID on failure Save the settings, try again.
OTK v2.2.3 With Retail License on Failure of Advanced Tokens Manager v3.0 Best greetings for the day! Once, I had destroyed Microsoft Office 2010 Retail Box after exasperated by the abrupt closing problem with Excel 2010, Word 2010 etc., but out of curiosity I downloaded from the Office Backup yesterday, and have installed today with OTK v2.2.3. Whatever I have noticed with OTK activation, those screen prints is being enclosed herewith. I don't know which one is the cause of this bug whether OTK or Office. I'm sure, if it's concerning to OTK, then it will be addressed in comming release. Thanks & Regards Enclosed: MSOxlsx.png (Excel 2010), MSOdocx.png (Word 2010)
This bug is caused by a screwup in the registry, the picture on the right is good. You can reinstall licenses for Pro Plus, (You mentioned retail, if you are using retail install retail license, if you converted to VL install VL.). This bug is harmless though. It can occur if your registry is screwed up and you back it up screwed up, but reinstall license (not Repair/Delete!, will readd the registry entries).
Thanks for ensured me about the bug is harmless. One more thing I have noticed that KIS 2012 treats OTK as a trojan and sends to lab, if installed before KIS. Meantime, if OTK installed after KIS then it's not. Why don't you build KMS virus free?
Because the KMS part is not made by me, ZWT made it, and only they can change it. We're stuck using their KMS Keygen for activation, and their tool gets flagged despite being safe.
Thanks to all my friends to give faith to be harmless. But if it's true and does not recur unexpected closing problem of Office 2010 (Retail), then it's best one than other ways of activation.
i tried capturing packets from/to 1688 using wireshark, so i used filter "port 1688" but i can't capture anything! no matter if i use 127.0.0.1 / 10.0.0.7 or global address and no matter if the autokms service is on or off. something is obviously not working right with wireshark because the computer does get requests and answer them. (i do see other activities in wireshark)
Hello all. Thanks for your wonderful program!! Anyway, Im having a problem with my AV. To be precise, Microsoft Security Essentials (MSE). Sometimes when I reboot It detects a process as a virus (Win32/Keygen) but It doesn´t tell me the path of this process. It just tells me the PID. I added AutoKMS.exe to my AV exclusions but the problem persists. How can I fix this?. What elsse do I have to add to my exclusions? With erlier versions of EZ-Activator I didn´t have this problem. I used to add %Windir%/Keygen.exe and %Windir%/AutoKMS/AutoKMS.exe and everything worked fine. Now it seems that the Keygen.exe is being detected but it is not where it used to be. Where is it now and how is it called? Thanks.
Try adding vbc.exe to exclusions. It's in %WINDIR%\Microsoft.NET\Framework\v2.0... whatever the version. It may be scanning that and stopping it, as my NIS can do that.
It is estrange. Why do I have to add vbc.exe to exclusions if Im using Microsoft´s antivirus. Why with erlier versions of the toolkit this wasnt neccesary? Anyway, I´ll try what you said. Its difficult to test it because it happens sometimes. Not on every reboot.
Because I run KMSEmulator inside that file now so I don't have to write to disk. This prevents AV from deleting things, but a AV that scans vbc.exe memory may terminate it. You effectively have to change KMSEmulator.exe exclusion to vbc.exe exclusion. Doing it like this also meant a consistent spot to exclude.