Snagit (Windows): SnagPriv.exe does not start

Problem

When starting Snagit, you may receive a message indicating that SnagPriv.exe cannot start.

snagIt_error.png

Solution

Single End User (personal computer)

If you are running into this problem on your personal computer, this can likely be resolved by setting SnagPriv.exe to Run as Administrator.

  1. Navigate to the Snagit installation directory.  By default, the installation directory is (where "#" is the version of Snagit you have installed):

    Snagit 2018

    C:\Program Files\TechSmith\Snagit ##

    Snagit 13 and earlier

    32-bit Windows: C:\Program Files\TechSmith\Snagit #
    64-bit Windows: C:\Program Files (x86)\TechSmith\Snagit #
  2. Locate SnagPriv.exe in this directory, right click on it, and choose Properties.
  3. On the Compatibility tab, check the box to "Run this program as an administrator" and click Apply.

IT Department / Administrator

If there are multiple users within your organization running into this problem, we have seen multiple causes.  Running SnagPriv.exe as an administrator as mentioned above is not likely an option in these environments, so we suggest considering the following suggestions with your IT and security teams.  

Cause 1: Third party conflicts

We have seen some third party security policies and software cause this error. If possible attempt to disable security software to rule out a potential conflict. We have seen the following programs cause this problem.

  • Entrust software

If you do identify another third party program that is causing this conflict that is not mentioned above, please submit a support ticket with us so we can update our documentation.

Cause 2: Unable to check CRL

This issue can be caused by an invalid value of a specific registry key that Microsoft relies on to check for valid certificates.  The registry key in question is below. This setting can also be found in the Control Panel > Internet Options > Advanced tab.

This may be a setting that you wish to clear with your internal security team to verify that it it acceptable within your environment.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing

The 'State' key needs to be set to 0x00023c00 per this MS KB article in order to check for the publisher's certificate revocation list.  If this registry key is set to anything other than 0x00023c00 it can cause the error message of 'SnagPrive.exe is unable to start'.

We have found multiple things such as .NET upgrades, Windows Updates, Group Policy updates, and others can accidentally modify the value of this key which in turn causes the error message in Snagit.

Cause 3: Unable to verify digital signature

If the computer is unable to verify the digital signature of the executable, then it will fail to launch. To check if the signature is able to verify, follow these steps.

  1. Navigate to the Snagit installation directory.  By default, the installation directory is (where "#" is the version of Snagit you have installed):

    Snagit 2018

    C:\Program Files\TechSmith\Snagit ##

    Snagit 13 and earlier

    32-bit Windows: C:\Program Files\TechSmith\Snagit #
    64-bit Windows: C:\Program Files (x86)\TechSmith\Snagit #
  2. Locate SnagPriv.exe in this directory, right click on it, and choose Properties.
  3. Select the Digital Signatures tab. Select the signature from the list and choose Details.

    signaturecheck.png

This details window should show the status of the verification of the digital signature.

Success Example:

checkok.png

Failure Example:

checkfail.png

If the signature is not able to be verified, there may be something blocking that verification on the local computer or within the environment.

Suggestions

Do not attempt these suggestions without first consulting with your internal IT and security teams.

  1. Make sure the DigiCert Root CA's are installed and trusted within your environment.
  2. Make sure that the entire certificate chain is installed and trusted on the machine. This can be found in the Digital Signature Details window, by selecting View Certificate > Certification Path.
  3. Make sure the following update is installed on the system: https://technet.microsoft.com/en-us/library/security/3033929.aspx 
  4. Contact local security team to investigate if there is a local policy that is preventing the signature from being verified.
  5. Reinstall the root certificates.
  6. Contact TechSmith Support to try a different build of Snagit.
  7. Contact Microsoft Support.
Was this article helpful?
9 out of 22 found this helpful