Did you just run into a file that has a digital signature from Microsoft Windows Kits Publisher? If that's the case, please read on.
You'll typically see Microsoft Windows Kits Publisher when double-clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can also view the Microsoft Windows Kits Publisher certificate with the following procedure:
Here is a screenshot of a file that has been signed by Microsoft Windows Kits Publisher:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This implies that the file has been published by Microsoft Windows Kits Publisher and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can see all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, and so on. You can also view the address for Microsoft Windows Kits Publisher, such as the street name, city and country.
Microsoft Code Signing PCA 2010 has issued the Microsoft Windows Kits Publisher certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screenshot above.
The following are the Microsoft Windows Kits Publisher files I have gathered, thanks to the FreeFixer users.
Detection Ratio | File Name |
---|---|
0/51 | accevent.exe |
0/55 | AccScope.exe |
0/54 | VisualUIAVerifyNative.exe |
0/57 | inspect.exe |
0/57 | AccCheckConsole.exe |
The detection percentage is based on the fact that I have collected 274 scan results for the Microsoft Windows Kits Publisher files. 0 of these scan results came up with some sort of detection. You can view the full details of the scan reports by examining the files listed above.
The analysis is based on certificates with the following serial numbers: