Kaspersky Anti-Virus 2013 & Malwarebytes Anti-Malware are detecting this and removing it. I read that you say you changed the signature of the sfx, maybe another route should be taken in order to stop this annoyance although I doubt you will so I am going to delete this from my storage.
Thing is i've taken a break from software development i'm to busy with other stuff at the moment. v1.3.4 is using the original rar sfx module fixing it and realeasing a new version would be a waste of time. Maybe decompressing and protect it with a vm protector would work?. Solution 1: Create your own private build and dont share a sample with the av vendors. Solution 2: Easy yeah delete it.
When checking it with virustotal i´m only seeing false-positives due to behavior heuristics. When checking older AutoKMS there are ways more of those entries (best so far 27/47 ). Except of my system drive, the rest will only be protected/scanned by my explicit order, PERIOD. No way i let my AV patronize me . The only moment i agree with the AV Vendors is, we know both that the flagged files on my machine are bad for MS, but of some benefit for the user . For suspicious files they invented VMs....
VM's would be perfect if could use the real Hardware instead of vitualiced Hardware which just gives bogus results compare with real machines! And that exactly why I keep away from VM's, use extra HDD's for to install such "Testing-OS's" etc. and boot using the BIOS Boot Manager!
I had extracted the files, all looks well. Enjoy your other work, either way, I have other routes to take for checking keys.
That was a sidenote, not the message. Not an essential part of my post . One aspect beside running different OSs side by side, was the security aspect, see i.e. 'Sandboxie' .
Great apps woot, let say I just use your tool to validate my windows key & the result is valid, will it be able to pass microsoft validation process in their website?