Dual cursor problem fixed but i'm able to blank my screens. on my windows 10 20H2 (OD Build 19042.1052) but i have tried other computer with the same build, cursor works fine but blank screens won't work. User tried to click or enable the blank screen, it get untick after.
Prior this this test, Logmein Virtual display driver was disabled. Not sure how to enable it. Anyone know how to enable the Logmein virtual display driver?
Can someone please confirm if the latest build resolves the double cursor and allows for blanking of screens on the host computer?
Is this build fully tested, or is it still a preview release?
I just tested it, and yes, the latest build stopped the double cursor appearing and the host computer is blank.
Its Odd, the test build works on my computer that dual cursor is fixed and blank screens works. For some reason other 3 computer i tried, dual cursor fixed but blank screen don't work. We all have windows 10 20H2 same make and model of computers.
I am hoping LogMeIn support can answer me:
I know you guys are working hard to get the latest build to fix dual cursor and blank screen issue on windows 10 20H2 or newer. We disabled all of our computer Logmein virtual display driver as a workaround to fix the dual cursor (we have to turn off the monitors power) but blank screen don't work.
If the new build is pushed out and update our current version, will the Logmein Virtual display driver get enabled back?
@aaneal Thanks for the confirmation.
@bullzeyes23 If you've already re-installed the LogMeIn beta endpoint (soon to be fully released), and screen blanking still does not work, then we may need you to create a case with Customer Support so they can send the LMI and Windows log files over to Engineering for a comparison. It's very odd that some PCs would be fine while others fail, while utilizing identical hardware.
The last two builds should not require you to disable the Logmein Virtual Display driver. Try re-enabling it to see if screen blanking works correctly.
I had disabled the LogMeIn Virtual Display Adapter prior to the new build. When I updated to that latest version, the LMI Display Adapter was still disabled and there was no way to enable it (grayed out).
I finally decided to remove the useless LogMeIn Virtual Display Adapter by clicking on "Uninstall Device" and the LMI Display Adapter completely disappeared.
I uninstalled LogMeIn Control Panel from the computer. I rebooted my computer and REinstalled LogMeIn. (Just for good measure, I rebooted my system one more time after installing).
After getting everything up and running, I remoted into that computer and clicked on "blank screen" AND IT WORKED. I hope this helps and doesn't mess anything else up for those of you who had the same issue as I did (bullzeyes23).
Thank you. I was thinking of that too. But i am wondering if there is a command line to enable the LMI virtual display instead of doing what you did. I have to uninstall the current LMI on our 95 computers and re-install with this test build if there is no way to enable the LMI virtual display.
I am hoping Logmein support can give me a way to enable it before i spend my weekend alone uninstall and re-install with the test build for 95 computers.
Over 3 months since the initial support ticket was submitted, and they're still telling everyone to uninstall the LMI virtual display adapter. I can't tell you how much lost time and revenue this problem has caused me. I've talked to tech support and was told there is no fix in the near future.