How to Repair “The Timestamp Signature and/or Certificate could not be Verified or is Malformed” Error in Windows PC

  • Several users recently reported encountering this problem when trying to install the.Net framework or similar applications on their Windows.
  • Not having these updates on your system can lead to a problem with Dotnet Framework timestamp signatures.

(Case No. EGF-242-16878) No support for NTFS Storage Spaces in Windows 8 and higher. BSOD occurs on reboot.

The “Timestamp Signature” error has been encountered by numerous Windows users recently when installing applications such as the .Net framework etc.

In my first attempt to install KIS 2013, I was told that the Digital Signature of installation files was missing from the CD that I purchased last year. The Learn more link led me to download the 2014 version, only to get the same message again.

Several possible causes may contribute to this error. Below is a list of possible causes.

Why does this error occur?

  • Outdated Windows: The Dotnet framework is constantly being updated by Microsoft to fix runtime/application development bugs, and to keep up with the times, your computer’s Windows must be fully patched to the latest version. Not having these updates on your system can lead to a problem with Dotnet Framework timestamp signatures.
  • Outdated Dotnet Framework installer: If you are trying to use an outdated Dotnet Framework installer (which may already be present in your system boot folders), that installer may not be compatible with your system operating system and may cause this Dotnet problem.
  • Unsigned system driver: To improve the security of Windows and the Dotnet Framework for running applications, all drivers on your system must be digitally signed. If any of the drivers on your system are not digitally signed, the Dotnet Framework installer may cause a timestamp signature error.
  • Outdated root certificates on your system: If your system is unable to automatically update its root certificates due to a faulty certificate manager on your system, the Dotnet Framework installer may fail to authenticate many important system resources and thus indicate a timestamp problem.

How do I get rid of this error?

Windows Cannot Verify The Digital Signature For This File

Older Windows systems do not have SHA-2 digital signatures, causing the problem.

In the details of the COMODO signature, I see the following message: The timestamp signature and/or certificate cannot be verified or are malformed. Despite running as administrator, using the troubleshoot compatibility tool, deleting toolbars, closing all non-essential processes, and going to the task manager, nothing seems to work. The GetSystemInfo report is below. Please take the CD out of the computer, and ignore it.

Download the standalone installer

  1. Go to the Microsoft download site for the .NET Framework.
  2. .Net Framework 4.8 is currently available for download from the link above.
  3. You can find more downloads by scrolling down.
  4. Choosing Offline Installer from the download type will download the offline installer by clicking Runtime on the right.
  5. Right-click on the installer and select Run as administrator.
  6. Installing the program successfully fixes the error.

Performing a Windows update

  1. Run can be opened by pressing Windows + R.
  2. The Windows Update window can be accessed by typing ms-settings:windowsupdate.
  3. Once you have clicked Check for updates, you will find an update window.
  4. All updates (optional or not) should be downloaded and installed.
  5. The problem may be resolved if you reboot your computer.

Check the timestamp of the certificate

  1. Choosing Properties from the right-click menu will reveal the installation file’s properties.
  2. You can find the Digital Signatures tab by clicking on it.
  3. Click on Details for the signer you want to view.
  4. To view the certificate, click Subscriber Information on the Digital Signature Details window.
  5. The validity date should be checked from the valid to date.
  6. Installer versions for expired certificates can be downloaded.

Using the latest version of the .NET Framework installer

  1. .NET Framework can be downloaded from the Microsoft website using your browser.
  2. The .NET Framework version you should select is 4.8 (currently).
  3. You can download .NET Framework 4.8 Runtime by clicking the link below.
  4. Double-click on the installer once it has been downloaded.
  5. When installing, check for errors such as “Timestamp” and “Certificate Verification”.

Disable code signing for the driver package

  1. When you press Windows and R at the same time, Run will open.
  2. For group policy editing, type gpedit.MSC.
  3. The User Configuration entry can be expanded in the Group Policy Editor.
  4. Select Administrative Templates – System – Driver Installation from the menu.
  5. On the right side, click Code Signing for Driver Packages if you selected Driver Installation.
  6. Click on Enabled in the pop-up window.
  7. Choose Ignore when Windows detects that a driver file does not have a digital signature.
  8. Your changes will be saved when you click Apply.
  9. The system should be rebooted.
  10. If the faulty driver installs successfully after the reboot, you are good to go.

Frequently Asked Questions

If you tried to join a meeting and got the error message "The timestamp signature and/or certificate cannot be verified or is incorrect", it means that Windows cannot update its internal certificate.

  1. Check the timestamp of the certificate.
  2. Download the latest version of the installer.
  3. Unlock the driver.
  4. Disable code signing for the driver package.
  5. Disable the application of the driver's signature.

  • Outdated Windows.
  • Unsigned system driver.
  • Outdated Dotnet Framework installer.
  • Outdated root certificates on your system.

The software may cause User Access Control (UAC) errors when installed in protected locations such as “Program Files” or “Program Files (x86)” in Windows Vista, Windows 7, and Windows 8.1. We recommend reinstalling the software if the error persists. CrossCore Embedded Studio can be installed in C:/Analog Devices/CrossCore Embedded Studio by default.

Website | + posts

Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog,, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.