sodcalculator

10 Tech How-To

How to Check a Digital Signature in Windows 10

Guide 10-58001 · Updated · Step by step

Checking a digital signature on a Windows 10 program file tells you whether the file is genuinely from the publisher it claims to be from and whether it has been altered since signing. This helps you avoid running tampered or malicious software. You only need the file itself and a few minutes—no extra tools are required.

What You’ll Need

  • The executable (.exe), installer, or other signed file you want to verify
  • Windows 10 (any edition) with File Explorer available
  • An internet connection if you want to check the certificate against a certification authority (optional but recommended)

Step-by-Step

  1. Locate the file in File Explorer. Navigate to the folder where the program is saved—this could be your Downloads folder, a USB drive, or a network share.
  2. Right-click the file and select Properties from the context menu. If you don’t see Properties, make sure you’re clicking the file itself, not a shortcut.
  3. Go to the Digital Signatures tab in the Properties window. This tab lists all signatures attached to the file. If you don’t see this tab, the file is not digitally signed.
  4. Select the signature you want to check from the list. Most files have only one signature. Click it once to highlight it.
  5. Click the Details button below the signature list. A new window opens showing signature information, including the signer’s name, the certificate’s issue date, and the signing time.
  6. Check the “View Certificate” button to inspect the actual certificate. This opens the Certificate dialog where you can see who issued the certificate, the validity period, and the intended purpose.
  7. Verify the certificate’s validity. In the Certificate dialog, look at the “Certificate status” field. It should say “This certificate is OK.” If it says anything else, such as “expired” or “not trusted,” treat the file with caution.
  8. Click OK to close the Certificate dialog, then OK again to close the Details window. Return to the Properties window.
  9. Check the “Signature” line in the main Properties window (on the Digital Signatures tab). It should say “This digital signature is OK.” If it says “The digital signature is not valid,” the file may have been tampered with or the certificate is problematic.
  10. Optionally, verify the publisher. Right-click the file, choose Properties, then look at the “Details” tab. The “Copyright” and “Product name” fields often list the company. Cross-reference this with the signer name from the signature.

Common Mistakes

  • Checking a shortcut instead of the actual file. Shortcuts (.lnk files) don’t carry digital signatures. Always right-click the .exe or .msi file itself.
  • Ignoring the certificate’s expiration date. A file signed with an expired certificate can still be valid if it was signed during the validity period, but Windows may flag it. Check the signing time against the certificate’s validity window.
  • Assuming a valid signature means the software is safe. A valid signature only proves the file hasn’t been modified since signing and that the signer’s identity is verified. It doesn’t guarantee the software is free of malware—some malicious programs are signed with stolen certificates.
  • Overlooking the “More Details” link. In the Details window, there’s a “More Details” link that shows the certificate’s full chain. Clicking it can reveal if the certificate is chained to a trusted root.
  • Not checking the “View Certificate” status. Sometimes the signature line says OK, but the certificate itself has issues. Always open the certificate to confirm its status.

Tips

  • Use the “Details” tab to see the file’s version info. A legitimate program usually has a product name, version, and company name that match the signature.
  • Check the signer’s name carefully. Look for typos or slight variations (e.g., “Micosoft” instead of “Microsoft”). Attackers often create certificates with names that look similar to real companies.
  • If the file is from the internet, Windows often shows a “Security Warning” when you run it. This warning includes the publisher name. Compare that with the signature.
  • For important files, you can also use the command-line tool signtool (part of the Windows SDK) to verify signatures, but the Properties method is enough for most users.
  • Keep Windows updated. Microsoft regularly updates the trusted root certificate list, which helps ensure that valid certificates are recognized.

Troubleshooting

I don’t see the Digital Signatures tab. This means the file is not digitally signed. Some installers from small developers are unsigned. You’ll have to rely on other trust signals, like the download source and antivirus scans.

The signature says “not valid” but the file works fine. This can happen if the certificate has expired, was revoked, or the file was modified after signing. If you downloaded the file recently, try downloading it again from the official source. If the problem persists, avoid running the file.

“Windows cannot verify the publisher of this software” appears when running. This is similar to an invalid signature. It often means the certificate is not chained to a trusted root or the signature is broken. Check the certificate details as described above.

The certificate is valid but the signer is unknown to you. Look up the publisher’s website or contact their support to confirm they distribute this file. Even a valid certificate doesn’t mean the publisher is reputable.

I accidentally clicked “Run” on an unsigned file. If you’re concerned, run a full antivirus scan immediately. Also, check the file’s hash against the official one if the publisher provides it.

Frequently Asked Questions

Q: What does a digital signature actually prove?
A: It proves two things: the identity of the signer (the publisher) and that the file’s content hasn’t changed since it was signed. It does not prove the software is bug-free or safe.

Q: Can I check the signature of a .dll or .msi file?
A: Yes, the same method works for any file that supports digital signatures—.exe, .dll, .msi, .cab, and even some .ps1 scripts. Right-click and look for the Digital Signatures tab.

Q: Why does Windows sometimes say “The digital signature is OK” but the certificate is expired?
A: This happens when the file was signed during the certificate’s valid period, but the certificate has since expired. Windows may still consider the signature valid because the signing timestamp proves it was done when the certificate was valid.

Q: Is a signed file always safe to run?
A: No. A valid signature only means the file hasn’t been tampered with after signing. Malware can be signed with stolen or fraudulently obtained certificates. Always consider the source and run antivirus scans.

Q: Can I remove a digital signature from a file?
A: Yes, but it’s not recommended. Tools like signtool can remove signatures, but doing so will make the file appear unsigned and may trigger security warnings. It also destroys the integrity guarantee.

Q: What if the file has multiple signatures?
A: Windows lists all of them. You can check each one individually. A file is considered valid if at least one signature is valid and trusted.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →