- Jan 15, 2018
- 6
- 2
I've been troubleshooting a choppy video problem the cropped up when I moved my test system into the remote location I was monitoring.
I tried everything (iframes, buffer, network diagnostics, CBR vs VBR, D2D, windows defender etc)
What I finally discovered was that the remote viewing software I was using (TeamViewer) was issuing a lock session command on exit (locking the screen). Despite optimizing all of the power settings, it seems that Windows 10 has some power settings that get kicked in on session lock.
I turned off the lock session feature and all is good.
I have a case open with Microsoft on this, but any other insights as to how to fix this without NOT locking the session would be appreciated!
I tried everything (iframes, buffer, network diagnostics, CBR vs VBR, D2D, windows defender etc)
What I finally discovered was that the remote viewing software I was using (TeamViewer) was issuing a lock session command on exit (locking the screen). Despite optimizing all of the power settings, it seems that Windows 10 has some power settings that get kicked in on session lock.
I turned off the lock session feature and all is good.
I have a case open with Microsoft on this, but any other insights as to how to fix this without NOT locking the session would be appreciated!