SnagIt 2018, I can no longer detach surface book screen

  • 20
  • Problem
  • Updated 1 year ago
  • Acknowledged
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Inactive threads; archiving to prevent necroposing

Since upgrading from 13.1 to 2018, I can no longer detach my surface book screen.
I presume that it is something to do with a file path pointing at the SD card (which is in the keyboard part and not the screen) but I cannot find it anywhere in the preferences.
Photo of justin.lawless

justin.lawless

  • 3 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 20
Photo of jeffh

jeffh

  • 2 Posts
  • 1 Reply Like
I am in the same boat.  Surface Book 2 and I can't detach without going into the Task Manager and killing SnagIt.  I will be uninstalling the product until it is fixed.
(Edited)
Photo of Rick Stone

Rick Stone

  • 5652 Posts
  • 2692 Reply Likes
Hi there

I'm a curious type. Unfortunately I don't own or have access to a Surface, so I have no way of knowing how SnagIt interacts. But just watching from the sidelines, it does make me wonder about this particular thread. 

I'm not saying there isn't an issue to be addressed with SnagIt, but honestly, how big of a deal is this from a realistic standpoint? I mean, it seems to me to be akin to using USB flash drives. Yeah, I know that the "proper" process is to take the step of right-clicking my flash drive and commanding Windows to Eject it. But in some cases it simply won't do that and I end up doing what I call "popping" the drive by just disconnecting. And most of the time I'm fine and nothing is messed up as a result.

It seems to me that there would be no harm in simply detaching something like a keyboard regardless of the messages involved. Or is there?

Are there some ramifications that those of us that don't use Surface machines are unaware of? Because if not, it simply seems that this is more of a nuisance message that is happening.

I'm just happy I'm not a cat. Appreciate any feedback.

Cheers... Rick :)
Photo of Ward Mahowald

Ward Mahowald

  • 6 Posts
  • 5 Reply Likes
It's not just a warning, the Surface Book actually won't let you detach until all messages are resolved.  BTW, this issue is not limited to Snag-It.  Any program that uses the GPU in the Surface Book Base also causes the same thing (Photoshop, Illustrator, etc).  You just have to close and completely exit all offending programs before you can detach.  Snag-It might be a little unique because most users let it run in the background all the time, therefore you see the warning every time you try to detach.  Hope that helps.
Photo of jeffh

jeffh

  • 2 Posts
  • 1 Reply Like
If it was as simple as just pulling without ejecting I wouldn't mind.  I will be honest, I haven't ever officially ejected a USB via the eject media option.  I just grab and go.  As you stated, yYou can pull a USB drive without ejecting it, however, the Surface Book is attached to the keyboard by a "lock" and the lock won't release until the SnagIt is killed completely. 

Think of it this way - you have a laptop on a docking station.  You hit the release button on the dock but the system says no you have to close outlook to be able to detach your laptop from the docking station.  Its a total pain in the bootay. 

I am sure that, as others have said, it is related to snagit locking itself to the dGPU that is in the keyboard.  Then when you go to detach, because the system sees there is an app that is actively using the dGPU then it says no you can't.  There are ways to pin apps to graphics cards (Use the Intel adapter for X app and the Nvidia adapter for Y app). Yet there isn't a way to do this with SnagIt. 

Hopefully this explains the frustrations of those of us with SB and SB2 devices. 
Photo of Rick Stone

Rick Stone

  • 5652 Posts
  • 2692 Reply Likes
Thanks for the replies, folks. Most appreciated. I had no idea there was some physical locking device involved!
Photo of Mike Baturin

Mike Baturin

  • 2 Posts
  • 0 Reply Likes
Any update to this issue?  Just purchased Snagit 2018 and now I cannot detach without quitting snagit. This is actually causing me grief as I detach often to take my Surface Book 2 to meetings.  Having to constantly close snagit is a major PITA.
Photo of notasaint

notasaint

  • 5 Posts
  • 2 Reply Likes
To the best of my knowledge the main issue has not been resolved by TechSmith yet. However, I would like to point out to everyone on this thread that closing just the Editor should allow you to disconnect while still having the main Snagit application open and available for use. At least that is working for me...
Photo of Mike Baturin

Mike Baturin

  • 2 Posts
  • 0 Reply Likes
Thanks for that info - still a pain to have to remember that extra step.
Photo of Patrick Loftus

Patrick Loftus

  • 4 Posts
  • 1 Reply Like
I can confirm that closing the editor works for me as well.  Still a pain and really disturbing that this issue has been unresolved for several months.  Has anyone found a reasonable replacement for snagit?

This conversation is no longer open for comments or replies.