The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Screen Blanking not working after Windows 10 2004
Microsoft has pushed out Windows 10 2004 to my workstations in our office and now screen blanking no longer works.
My employee's are working remotely and rely on screen blanking for privacy. My co...
Thanks for your patience everyone.
We've released an update that fixes the screen blanking failure for hosts running Windows v2004 and higher. Please upgrade affected PCs to LogMeIn host software 4.1.0.14344 in order to activate the new screen blanking method.
JCSS The latest Windows updates from Microsoft have blocked the ability for LogMeIn to blank the screen, based on some security issues they viewed as vulnerable. While you can still roll back this update (#2004) to resolve the issue, we are currently working on a new way to blank Windows machines with this OS version moving forward. I'm sorry I don't have a current ETA to share, and will update as soon as I hear more.
I think the fact that AshC is remaining silent on this thread speaks volumes, LogMeIn obviously don't want this issue being highlighted and are hoping they will have a fix before people that haven't noticed it so far start questioning them and moving provider. Luckily we managed to roll back the Window 10 2004 update on 2 PCs in our office that only updated recently and blanking is working but because my update was over 10 days ago rolling back the update is not an option. We have had to turn off Windows update on the 2 PCs for now while we await an answer from LogMeIn (not ideal at all) which I don't expect to happen given how this has been handled thus far. The plan now is to move the PCs that we need blanked for confidentiality purposes away from LogMeIn and over to VPN/RDP set up as we have been left with no choice. It's a pity LogMeIn haven't seen fit to handle this with some degree of customer care because up until this happened I couldn't fault the service.
Just confirmed this doesn't work in Windows 10 20H2 either.
So we are now 2 windows 10 versions deep with this not working. 1909 was the last one.
