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

If you have encountered the “Timestamp Signature” error when installing applications such as .Net Framework etc., you are not alone. Several users recently reported encountering this problem when trying to install the .Net framework or similar applications on their Windows.

We investigated this problem and found that this error may have several causes. Let’s go through the possible causes of this problem below.

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?

Download the standalone installer

  1. Go to the Microsoft download site for the .NET Framework.
  2. Click the link to get the latest version (currently .Net Framework 4.8).
  3. Scroll down to More Downloads.
  4. In the Offline Installer download type, click Runtime at the right end to download the offline installer.
  5. Right-click on the installer and select Run as administrator.
  6. When the installation is complete, this indicates that the error has been fixed.

Performing a Windows update

  1. Press Windows + R to open Run.
  2. Type ms-settings:windowsupdate to open Windows Update.
  3. Then click Check for updates.
  4. Download and install all available updates (including optional updates).
  5. Reboot your system and see if the problem is resolved.

Check the timestamp of the certificate

  1. Right-click the installation file and select Properties.
  2. Click the Digital Signatures tab.
  3. Select the signer and click the Details button.
  4. In the Digital Signature Details window, click View Certificate in the Subscriber Information section.
  5. Check the Valid from Valid to date.
  6. If the certificate has expired, you can download the latest installer version.

Using the latest version of the .NET Framework installer

  1. Use your browser to open the download page on the Microsoft website for the .NET Framework.
  2. Select the latest recommended version of the .NET Framework (currently 4.8).
  3. Click the Download .NET Framework 4.8 Runtime button.
  4. When the download is complete, double-click to run the installer.
  5. Make sure that the “Timestamp” or “Certificate Verification” error does not occur during the installation.

Disable code signing for the driver package

  1. Open Run while holding down the Windows and R keys.
  2. Type gpedit.MSC to open the Group Policy Editor.
  3. In the Group Policy Editor window, expand the User Configuration entry.
  4. Then navigate to the following folders: Administrative Templates -> System -> Driver Installation.
  5. If you selected Driver Installation, double-click Code Signing for Driver Packages on the right side.
  6. In the window that appears, select the Enabled option.
  7. Open the drop-down menu under When Windows detects a driver file without a digital signature: and select Ignore.
  8. Click Apply to save your changes.
  9. Reboot the system.
  10. After the reboot, check to see if you can install the faulty driver without any problems.

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.