I renamed it into {not-keygen}.{not-exe} instead. I didn't investigate the issue in details, but I think that Microsoft expects a more enterprisey file name for

I renamed it into {not-keygen}.{not-exe} instead. I didn't investigate the issue in details, but I think that Microsoft expects a more enterprisey file name for a legitimate keygen. I should have called it something along the lines of CredentialManager.exe instead :) But I wonder whether it did auto-submit these files to Microsoft together with my private keys. I'm glad that the private keys were in config files outside of the executables, and this probably saved them from being compromised.