Snagit (Windows): Crashing due to Highly Secure Environments, FIPS


With the introduction of the Snagit Update in Snagit 11, we have seen some issues in highly secure environments. This can manifest as a crash within Snagit, either immediately at launch or just a few minutes later. Or, there may even be a specific message indicating an incompatibility with Federal Information Processing Standards (FIPS). The issue is due to our new Auto-Updater process, which uses an encryption algorithm currently not allowed by FIPS.


Our fix for the time being is to stop Snagit from using the updater:

  1. Completely close out of Snagit so that it is not running at all. Make sure by opening your Task Manager (Ctrl + Alt + Delete) and click on the Processes tab and making sure Snagit32.exe, SnagitEditor.exe, SnagPriv.exe, and TSCUpdClt.exe are not in that list.

  2. Hold the Windows key down on your keyboard and hit the 'R' key to open the Run window.

  3. Type 'regedit' (without quotes) and hit OK to open the Registry Editor.

  4. Using the pane on the left, navigate to one of the following locations, depending on your version of Windows:

    Snagit 13

    64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TechSmith\Snagit\13
    32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\TechSmith\SnagIt\13

    Snagit 12

    64-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TechSmith\Snagit\12
    32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\TechSmith\SnagIt\12

  5. Right-click in the right pane and choose New > DWORD. Add a DWORD called “NoAutoUpdateSupport” with the value “1” in the following location (It will be one of these depending on the system), then close out of the Registry Editor.