Short followup: What (if any) are the diverse effects of using Applocker to block vmlm_helper.exe on RDS hosts?
I have the same problem in View desktop (Windows 10 desktop). This file is from "VMware Logon Monitor", is included in View Agent 7.1 or higher
I have installed horizon view 7.2.
I still do not know why it happens.
More info of "VMware Logon Monitor" here: VMware Logon Monitor
Did you install the vRealize Operations for Horizon Desktop Agent? It is part of the agent install. I believe that includes the logon monitor so metrics can be uploaded to vrealize. Try uninstalling it.
I tried all suggested solutions in this thread with no success. The service will start even if I disable it. vRealize Operations for Horizon Desktop Agent is not installed and when I block the vmlm_helper.exe with UEM the session gets disconnected before I even see the Desktop. Any other ideas how to disable (or at least hide) it? Since it seems to be adding quite a bit of a delay at logon and doesn't look very nice from an end user's perspective in my opinion. We are currently using view 7.2 (linked clones) / Appvolumes 2.12.1 / UEM 9.2 / Windows 10 1607. Any further help would be appreciated since I'm starting to pull my hair out over this issue.
How do you have your RDS servers configured? Linked or Instant clones vs Manually added VM's?
If Linked or Instant clones I would suggest disabling the service on the Master image and recompose/reschedule so that the RDS machines get the update.
I've done this for my Master image that builds the Instant Clone RDS VM's and the service stays disabled and not running.
Actually, we have individual linked clone VMs based on a master image rather than RDS Servers. This was the only thread I could find that was somehow related to my issue but it's possible that there are differences between RDS and individual VMs during the View Agent install (it detects it's not being run on a RDS Server and you have to choose an individual desktop setting). I have disabled the vmware logon monitor service (vmlm.exe) in the master image. The service also shows as disabled on the linked clones, however, the vmlm_helper.exe still runs on startup in a cmd with a black background before the Desktop appears.
Took a look at this. The vmlm_helper.exe is in the userinit registry setting:
"Userinit"="C:\\Windows\\system32\\userinit.exe,\"C:\\Program Files\\VMware\\VMware View\\Agent\\bin\\vmlm_helper.exe\",\"C:\\Program Files\\VMware\\VMware View\\Agent\\bin\\wssm.exe\","
I removed the vmlm_helper.exe from the key as follows. The comma needs to be at the end of the line.
"Userinit"="C:\\Windows\\system32\\userinit.exe,\"C:\\Program Files\\VMware\\VMware View\\Agent\\bin\\wssm.exe\","
We see the exact same issue on our W10 desktop after upgrading to 7.2.
Anyone upgraded to 7.3.x to see if that fixed the issue? And did removing this from the userinit do the trick techguy? Also, what could the implications be from remving this from the userinit? What does it do then?
We upgraded to 7.3.1 and the issue is still there. We removed the key and what happens is that the cmd of vmlm_helper.exe does not appear and the screen stays black for a bit less than before. The vmlm starts anyway.
Its been working since I implemented it 3 months ago. I push the setting through group policy. By removing it you won't get the logon statistics in vrealize/view helpdesk portal.
This has been a pain for me as well. Has anyone found a solution besides hacking the registry? I only have minimal agent options installed. No vRealize for instance. It takes about 3-4 min for me to log into the desktop. Running agent 7.1.0
I've managed to fix the issue without removing vmlm_helper.exe from userinit registry key.
The issue was related with our antivirus software called Cylance Protect and it was to do with "Compatibility Mode".
- Using the Registry Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\Cylance\Desktop.
- Right-click Desktop, click Permissions, then take ownership and grant yourself Full Control.
- Right-click Desktop, then select New > Binary Value.
- For the name, type CompatibilityMode.
- Open the registry setting and change the value to 01.
- Click OK, then close Registry Editor.
- Restart VM.
You can deploy that using a GPO without changing the permissions.
I hope that helps.
After I had the same issue, I found the solution for my environement. Some service not start correctly, and some service are VMLM's dependancy. In my case ClipSVC couln't start correctly. After solved the service starting issue, I have no more this kind of behavior and no more vmlm_help.exe black box.
We are facing the same issue with VMWare Horizon Agent 7.7. Any help/update with this issue? Thanks in advance.