If I could get rid of that suspect capture things might work but where to look? Other actions seemed to work normally so attempted a fix before the full uninstall/reinstall. I suspected that mutant snag was the cause.

When I launched the Editor there was still an error but restoring my unsaved captures seemed to work. I was able to launch the Editor, run the backup routine and save the file before OK’ing. It didn’t actually terminate until you clicked “OK” on the error dialog. However it was then I noticed behind the error dialog the Editor was still running. Unfortunately I discovered the backup function is done from the Editor, not the Snagit capture component, which presented a problem. A general web search didn’t point to any obvious solution so decided to backup my unsaved captures, remove and reinstall Snagit. Since I use Windows 7 64 I didn’t even try those fixes. I had a look at the TechSmith Support site but the only mention of this sort of error related to some old XP/Vista runtime library updates.

I hoped it was just some corrupt memory, temp file or whatever but no joy, the runtime error persisted.Ī repair install, and another reboot, didn’t help so this was getting serious. As the Editor launched I got a C++ Runtime error (below) and launching it directly gave the same result.īy now the CAD publish was over so I restarted the whole machine. Snagit capture was still running so I tried another screenshot. After a lengthy wait I had to End Task my way out. Then Snagit Editor got very slow and appeared not to respond. It appeared the callout “tail” flew off to infinity (recreated right). While adding a callout I clicked, maybe outside the editor, during a pause. The computer was occasionally a bit slow as the publishing consumed chunks of processor time. I had CAD application publishing (digital print to DWF file) and was editing some captures while it was working. I can’t imagine working without Snagit but faced that horror last night.

Snagit 12 how to fix