Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X
We are experiencing a new issue where the Print Screen button used to trigger Techsmith SnagIt does not work when Creo is the active application. It used to work flawlessly, but recently stopped working.
My best guess is a change introduced by Windows Updates, Optional Windows Updates or Manufacturer Updates in Windows 10.
We use two primary suppliers for laptops and the problem appears to be isolated to Lenovo P series laptops running Windows 10. Lenovo has its own driver update tool keeping the laptop hardware and graphics drivers up-to-date which could add to the confusion.
Our current work-around is to click on another application to trigger SnagIt, but this drops any active UI in Creo. Simple screen shots are easy, but training screen shots are now a bit harder since the active UI elements are closed when another application is selected to use the Print Screen button to trigger SnagIt.
Solved! Go to Solution.
we found it! weird permissions issue between creo and snagit. to get it working again, we exited snagit and restarted using Run as Administrator. that gave snagit the higher permissions it needed to activate the PrtScr button in Creo. if you track down the shortcut that starts the application, you can turn on the Run as Administrator option in the compatibility tab so you never have to worry about it again 😁
I use snagit 2022.1.2 and Creo 6.0.6.0. I am not having any issues. HP z4 desktop. We stay updated on updates (at least based on corporate roll out)
Have you tested using a different trigger keystroke? Other than that, I got nothin'
Creo 7.09
Windows 11 Pro
Snagit 2022
Lenovo P16 Gen 2 Laptop
No issue with Snagit capture (printscreen) with Creo active
we found it! weird permissions issue between creo and snagit. to get it working again, we exited snagit and restarted using Run as Administrator. that gave snagit the higher permissions it needed to activate the PrtScr button in Creo. if you track down the shortcut that starts the application, you can turn on the Run as Administrator option in the compatibility tab so you never have to worry about it again 😁