I know this post is old, but it cannot be a "hardware" issue. I just did a windows 10 update and now my screens will not go "blank". Is there an update to this issue?
Solved! Go to Solution.
@cta We just released a new version of LMI Pro. Can you please confirm which endpoint you are running on the Host PC?
@cta Thanks, can you also confirm the Host software build?
Here's a reference article you may utilize to stay current: https://support.logmeininc.com/central/help/whats-new-in-central
@cta There is no extra charge for screen blanking functionality.
If you have a PC that is up to date with the latest software version referenced in that 'What's New' article, then you may click the 'Contact Support' option at the bottom in order to start a new case for investigation. Support agents will need event and LMI log files from the affected machine most likely.
LMI has been updated to 22.214.171.12444 yesterday, I reinstalled Logmein but since this update the blanking feature just does not work anymore on W10.
I saw "LogMeIn Virtual Display Adapter" appear and disappear 2s later when I try to activate this blanking feature.
021-03-22 14:46:19.098 - Info - LogMeIn - AUTORITE NT\Système - 18280 - 0x00003EA0 - BlankScreen/VDD - Start blanking
2021-03-22 14:46:19.098 - Info - LogMeIn - BlankScreen/VDD - InitAdapter
2021-03-22 14:46:19.099 - Info - LogMeIn - BlankScreen/VDD - Device VDD1 created
2021-03-22 14:46:21.111 - Error - LogMeIn - BlankScreen/VDD - Device open error: 0x00000002
2021-03-22 14:46:21.111 - Error - LogMeIn - BlankScreen/VDD - Failed to init virtual adapter with unique id: VDD1
What can we do ?
@GregLMI Thank you for those details.
Are you able to click my Community name and send over the full log file from the date after you updated the endpoint?
Hi. This update seems to have triggered an issue where I have double cursor while using Autodesk programs (Autocad and Revit). This wasn't an issue before this update was automatically installed, so something in the update broke it. Impossible to work like this.
Do you have a solution for this?
The two cursors are different sizes and track each other with a delay in the remote computer, making it impossible to work.