Did you just download a file that has a digital signature from Microsoft Windows Software Compatibility Publisher and wonder if the file is safe? If so, please read on.
You'll probably notice Microsoft Windows Software Compatibility Publisher when running 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 Software Compatibility Publisher certificate with the following procedure:
Here is a screenshot of a file that has been signed by Microsoft Windows Software Compatibility Publisher:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This means that the file has been published by Microsoft Windows Software Compatibility Publisher and that no one has tampered with the file.
If you click the View Certificate button shown in the screengrab above, you can examine 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 Software Compatibility Publisher, such as the street name, city and country.
Microsoft Windows Third Party Component CA 2013 has issued the Microsoft Windows Software Compatibility 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 Software Compatibility Publisher files I have gathered, thanks to the FreeFixer users.At the moment there's no scan result available for any of the Microsoft Windows Software Compatibility Publisher files, but they have been queued for scanning. Please reload this page in 5-10 minutes to check if the scan result is available.
Detection Ratio | File Name |
---|---|
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | 77e727.rbf |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | VCRUNTIME140.dll |
Queued for scan.. | vcruntime140_1.dll |
Queued for scan.. | vcruntime140_1.dll |
Queued for scan.. | vccorlib140.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Queued for scan.. | vcomp140.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | scdetour.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | MSVCP140.dll |
Queued for scan.. | VCRUNTIME140_1.dll |
Not available | mfc140u.dll |
Not available | mfc140u.dll |
Not available | mfc140u.dll |
Not available | mfc140u.dll |
Not available | mfc140u.dll |
The analysis has been done on certificates with the following serial numbers: