Problems with Blanking of the Host Screen During Remote Control (Windows 10)

I thought I should let the community know about this. I submitted the bug report in January and as of yet, it is not resolved.

In the power options of Widnows, there is a power option to turn off the monitor after x minutes of inactivity. (Turn off the display: x minutes)

If I am inactive in the session for a longer period than the remote screen power-down time of the monitor(s), then start using the remotte session again, the screen(s) "turn(s) on".

The point is that currently people may be processing payroll remotely or dealing with other confidential data and if they are inactive in the session for a time , then come back to the session, their work may be observed by others and remote LogMeIn users are not aware of this.

To simulate this:
On the hose computer, set the "Turn off the display" setting in the host power options to 2 minutes.
Log into the computer remotely.
Minimize the session or otherwise don't touch it so that the keyboard and mouse in the session are not used for 3 minutes.

Now use the session. The monitor will turn on and your work could be observed by anyone passing by. This is a potiential security issue, so I thought I'd better let the community know. This seems to be a Windows 10 only issue.

Find more posts tagged with

Comments

GlennD

Hi,

Today's release includes a fix for screen blanking, please let us know if you continue to expereince issues after updating.

EF1

CONVENIENCE

NECESSITY

mispelled for emphasis

EF1

We have not. We use multiple monitors, and if we turn them off, when operating remote, it operates as if there is only one monitor, drastically cutting efficiency. So, we have to leave them on. SCREEN BLANKING WHEN OPERATING REMOTE, IS NOT A CONVIENIENCE, BUT A NECCESSITY.

pmcleod

We are having this same issue and it is critical with our HR/Payroll users to have the screen blanked out while working remotely. Has anyone found any other solutions other than physically turning off the monitor and/or locking their office?

CoffeeOpSupport

I was disturbed to figure this out as well. But my problem is even worse. The blanking option only works for single monitor workstations. It does not work for any of my 2 monitor workstations. It will say in the remote session that the monitors have been blanked, but they haven't at all. We tested this with a laptop connecting to a desktop through local wifi, cellular, and across an outside vpn. Didn't matter if power settings were set to never turn off the monitors, if you have a dual monitor setup with Win10, logmein can't blank the screens at all. This needs to be resolved sooner than later, otherwise I'll be moving away from LogMeIn and finding a solution that works correctly. We have PCI-DSS compliances we must follow and we went with LogMeIn because it provided that layer of compliance, but now it doesn't.

pki730

I'm experiencing the same problem well over a year since the original post. Perhaps the logmein people do not bother looking at the problems we are experiencing when posted in these forums? I can't believe that more people are not having the same problem. I'm running Windows 10 on my home computer and logging in using my iPad and the screen is not blanking despite the fact that I installed the add on that supposedly blanks the screen when I was prompted to do so, and when I log in on my iPad it states that the screen in blanked but I'm staring right at the computer and it is not blanked!

sheepdogx

I am running into this very issue also. We recently updated our systems to Windows 10.

After speaking to Tier I and Tier II support, their answer is that it is not something their dev team can fix. The explanation I received is that Windows 10 is overwriting the third-party setting (third party being LogMeIn client).

Moving forward, I believe the only workaround is to disable the screen timeout function in Win10, unless LogMeIn is somehow able to fix this.

Just for clarification to other readers, the screen timeout is a separate setting from screensaver timer. From my testing, the screensaver setting was not overwriting the "blank screen" setting. The only time I ran into the issue of the blank screen failing on the remote host was when the screen timeout setting was set and the time elapsed. When I returned to my session, the "Blank Screen" setting was still highlighted like it is enabled, but it actually was not. You can see everything on the remote system's screen.

mlgillen

Update: Once again I was rememded that my work was being viewed by others. 5 months and no solution or fix.

Quick Links

Join the conversation!

If you found this discussion useful, why not register/sign-in? It only takes a minute to share your feedback, ask a question, or vote for a new feature!