Snagit (Windows): Self-repair on first run

Note: In most cases, self-repair should not occur in Snagit version 13. If you are experiencing the self-repair in version 13, please contact our support team.

Problem

After deploying Snagit to a user base, when a user runs Snagit for the first time (or, maybe every time) Snagit attempts to repair itself.  



Solution

Snagit 13 and later

In most cases, self-repair should not be occurring in Snagit 13 and later. If you are experiencing self-repair in version 13 or later (other than the scenario explained below), please contact our support team.

Bug in Windows 10 with Snagit 13.x and later

There is a known issue where self repair can be triggered after installing the Window 10 Creators Update.  See here for details. 

Bug in Snagit 13.0.0 -> 13.1.0

There is a bug in Snagit 13.0.0 -> 13.1.0 that will trigger the self repair. This specific bug is fixed in Snagit 13.1.1 and later. This can occur if shortcut is created on the Desktop when creating the transform (MST) file for deployment. The current workaround is to select to not create a Desktop shortcut when creating the transform file.

Snagit 12 and earlier

The most common cause for this behavior is when Snagit is being deployed under a SYSTEM account (or an administrator account through whichever deployment solution is being used). Therefore the registry keys that are placed in the registry under HKEY_CURRENT_USER for Snagit are being created for the account that the software was deployed with, rather than the logged in user account.  So, when a normal user logs in and attempts to launch Snagit, Snagit will trigger an auto-repair for the missing resources.

Another possible cause for this behavior is if the HKEY_CURRENT_USER hive is deleted every time a user logs out of a machine. If a user logs into a machine, and the necessary resources under HKEY_CURRENT_USER\Software\TechSmith\SnagIt\12\ do not exist, the auto-repair will be triggered. 

If the source is no longer accessible to the user (the source being the MSI that was used to deploy Snagit), then a prompt similar to the one below may be presented. 

What can I do to prevent this?

  1. Deploy Snagit through the logged in user accounts rather than through a SYSTEM account.  If users are locked, it is possible to enable some features via group policy to avail running MSI's. 
  2. Make the source installer available so that the auto-repair completes successfully. That is, make sure the logged in users are able to access the original MSI used to deploy Snagit. This can be done by creating a SOURCELIST (property name) in the Windows Installer.
  3. Use Windows Active Setup. It is possible to add these keys to HKEY_LOCAL_MACHINE into the transform file and let Windows generate the missing keys for any user who logs in. 
  4. Write a script to run on every user when they login.  Insert the HKEY_CURRENT_USER\Software\TechSmith\SnagIt\12\ registry keys using the script.  
Was this article helpful?
0 out of 2 found this helpful