Symantec Corp 10.2 . Even with exclusions, when I reboot it kills the the task execution and deletes any files
So, that only explains that the software you're using is not doing what you're telling it to do. You have two options: 1 - Totally disable the antivirus while activating 2 - Use another antivirus that in fact does what the user wants. If you go for #2 I would suggest the Avira Antivir Free
Thanks Bosh. I can activate with it disabled but when I turn it on, even then its fine. Its just when I reboot and the autokms task schedule runs, then it activates autokms and quarantines all the files. The problem is not that the exclusions doesnt work but that upon reboot as soon as the autokms executes then it goes banana's. Everything was OK until I updated on Monday. Must be a new type of tamper protection or something. I'll play around and see if there's a waork around but if anyone else gets it resolved, I hope they post here. All in all great work guys. Its just this AV irritation.... oh and the "it" I refer to above is the AV(Symantec Corp 10.2)
First of all I would thank to thank CODYQX4 and all the other developers for a great tool. I believe you when you say that there is not a trojan. I run free Avira with Comodo Firewall. The interesting thing is that Avira always challenges the AUTOKMS.EXE but I can say allow, Avira still challenges again sometimes, but the reactivation to 180 days works on boot up. The thing that reassures me is that Comodo has never said that AUTOKMS.EXE is trying to contact the Internet. On a friend's system with Norton Internet Security 2010 it will not allow AUTOKMS at all. Way round is to disable everything for 15 minutes and then it works fine. I have told him not to worry about reactivating every day and just run the routine with Norton off every few months. I am not an expert like a lot of people on this board, but I really appreciate all the hard work you do for the community. As you have pointed out before to the doubters they can always lash out several hundred pounds and buy the product.
I just tried the EZ Activator with one of the retail copies found in Fask's thread and it worked! for now anyway, hopefully it stays. But thanks for this liitle peice of software, I want to buy Office but simply can't afford it right now. I will in the future though.
When Avira catches something or warns you it will give pop up to remove or see details choose see details then right click what ever is flagged then choose always ignore. I did that few times and no more warnings
I guess the main problem is not really relating to any connection that it has made ...... but rather related to the internal structure of the exe file itself ...... sometimes a exe / dll file can be packed (or compressed) by tools known as PE packer ..... they are usually used to reduct the size of the exe / dll file .... and could be used for anti-offline-debugging too ...... usually those packed exe are harmless if they have been tested well in sandbox ..... but just because some of the people who also packed their trojan (for anti-debugging) to stop anti-virus program to detect them ........ so what anti-virus program does now is to stop every program that packed with harmful PE packer (for example, something that intended to stop AV program to detect it / reverse it but not reducing the size) .... if you do not know anything about a exe / dll file (for example, what it does) which has been packed by a PE packer, I recommend you not to run it since it can do harmful things in your computer ..... but in this case ...... since you know what actually it did on your computer and it has been well tested before ...... I think it is safe to run / use it
Keygen is packed but there is a unpacked version. I tested both with VT, and the unpacked gets one less detection, but by an AV I've never heard of and nobody uses. All the popular AV didn't care if it was unpacked or not. I gues it acts suspicious, opens a port and listens while generating KMS activation codes. Sounds like a backdoor to an AV that doesn't know better.
Ah then properly because of the listen state of the connection ...... but usually AV should not block any unknown connection ...... (actually I am thinking that MS is working with those AV to stop any things that are related to product key / KMS activation ...... since I have found that even produkey is blocked by several AV products)
I see you added some things, but I am not sure if it all what it means. One thing I've wanted to add is Activation # (For MAKs)/Genuine status (don't think pidgenx.dll can do that though, but VAMT does it somehow) Down the line I may add it but probably not in this upcoming BETA. Right now I'm sticking to the bugs, and I could add this later. I am curious about some of it, as you have stuff output that no other PDIX checker has. What is BINK ID? You mention it being used to keygen? I may discuss with Bosh, as we don't totally understand how our own implementation of the key checker works, whereas you seem to have dug into pidgenx.dll to find all this info.
Hi, thanks alot for your effort. I would just like to know if this autokms would conflict with Daz's or Hazar's softmod for Windows 7. Thanks!
That seems interesting, but what could we obtain of all of that?? And don't get me wrong, I'm asking because I don't know a thing about that, didn't understand what can we do with all that info. So, if you could explain me it would be very helpful, here or through a PM, it doesn't matter. Thanks in advance
Thanks unknownzd But, with all that info from the pidgenx.dll and the pkeyconfig.xrm-ms what would be the goal? I mean, I don't know if the idea is to be able to just correctly validate keys, or to find a way to bypass the activation, or anything else.
To find the related the public key and hence brute forcing a private key (people has brute forced out the XP private key just in 10 hours using P3, actually that was the way of how XP keygen created) .... and hence finding a OEMBypass key which has never been found before (but well I won't make program into public or here ..... instead I will give out a OEMBypass key once I have found it)