[Snagit] snagpriv.exe cannot be started

  • 3
  • Problem
  • Updated 6 months ago
When starting Snagit 13 we get the error that SnagPriv.exe cannot be started.

I tired the solutions explained in this post: https://support.techsmith.de/hc/de/articles/211853218-Snagit-Beim-Start-kommt-pl%C3%B6tzlich-die-Mel...

But the registry key was correct and starting SnagPriv.exe as administrator resulted in the same error.

Does anyone know this problem and has another solution?

Thank you.
Photo of support

support

  • 1 Post
  • 0 Reply Likes

Posted 2 years ago

  • 3
Photo of kevin.schumacher

kevin.schumacher

  • 1 Post
  • 0 Reply Likes
Don't know the solution, however i am having the same issue all the sudden.
Photo of Johnny Fish

Johnny Fish

  • 1 Post
  • 0 Reply Likes
For me I can set the run as administrator and it works, but I can't apply this fix because I cannot grant users admin privileges in order to run the app. Version 12 was previously installed. Removal of 12 and reinstalling 13 doesn't fix the issue either. I have over a dozen users with this problem.
(Edited)
Photo of mike

mike

  • 1 Post
  • 0 Reply Likes
I have the same problem, in Windows 10 for the past week or two.
Photo of Leon Wood

Leon Wood

  • 1 Post
  • 0 Reply Likes
I apply admin privilege  but...  It doesn't fix the issue in Windows 10....  
(Edited)
Photo of keith.kratochvil

keith.kratochvil

  • 1 Post
  • 0 Reply Likes
I had the same issue and found it was actually a problem with certificates missing from the machine. Our network has no connection to the Internet. I had to download the certificate and have it transferred over. In our case, it was the DigiCert SHA2 Timestamp Responder. It basically made Windows not trust the program, so then it would not run. I had to open the properties of SnagPriv.exe, go to Digital Signatures tab, then Details. The issue was with the cert in the Countersinatures section. You may be having a similar issue (or not).
Photo of Jamison Ye

Jamison Ye

  • 1 Post
  • 0 Reply Likes
Does anyone have fix for it?  We have a close network also. 
(Edited)