Windows 10: VMware horizon client 5.4.0

Hii,


Can we install VMware horizon client software particularly in windows 10 home version ??

:)

 

VMware Horizon Client generating hundreds of gigabytes of logs in VDM folder

I work for a very large financial institution and use VMware Horizon Client daily for work, both on a personal laptop (which runs Fedora) and home desktop. This issue is occurring on the desktop; the details of the desktop are below:

• Windows 10 Version 1803 (OS Build 17134.345)
  
• VMware Horizon Client 4.8.1 build 8980186
  
• Horizon Client, along with all other software on the Windows OS on the desktop, is installed on a 500GB Samsung SSD (C). I have an external Seagate 8TB desktop HDD, E, that I have backed up the VDM\logs folder to, but have deleted the logs from C. There is another installed SSD in the desktop which has Fedora installed but I do not use it for Horizon Client or anything related to work, and the disk is not visible to Windows.
  

Horizon Client is the only VMware product I have knowingly installed. I have been using this version of the client since I first installed it in July. In the past week massive log files have been generated on a daily basis in C:\Users\username\AppData\Local\VMware\VDM\logs. The largest, created this afternoon when I first opened the client and updated very frequently, is ~177 GB.

Here are my central questions:

1. Why are the logs suddenly so incredibly large? Usually they are under 100 KB.
   
2. Can I configure log generation in Horizon Client? So far I haven't found a way to do this; the Horizon Client settings are essentially useless.
   

Does anyone have any helpful info, or has anyone else encountered this issue? VMware support has been incredibly difficult to reach and utterly useless because I am using free Horizon Client. I can not open an enterprise support case with VMware on behalf of my organization. There are no questions covering this topic that I have been able to find on Windows forums, VMware community forums, Reddit, or anywhere on Stack Exchange.

EDIT: Using gc filename.txt | Measure-Object -Line I have discovered that the file is >1.2 billion lines long. As a sidenote, this is probably not the most efficient way to have discovered the line count of the file because the PowerShell command ran for well over an hour.

This message:

2018-10-31 15:42:44.934+-6:00 WARN (2A14) [WinCDK] UdpProxyLogger : udpProxyLib: FECHostPollLoop: recv on wakeup pipe returned -1, error 0x00002746

Seems to have been recorded many millions of times. All that differs between the lines is, as far as I can tell, the timestamp. I believe the error is caused by my VPN (I use iVPN) conflicting with Horizon Client, because this log inflation has not happened when I use the client with my VPN off. I still have no idea what exactly is causing it, why the error popped up only recently, or how to fix it other than turning the VPN off.

For the sake of pure curiosity I might spin up some S3 compute and generate a breakdown of how many unique messages there are in the file and how many duplicates there are of non-unique messages.

 

Keyboard input stops working in Windows 10 when running VMware Horizon Client

I just upgraded to Windows 10 and then installed VMware Horizon Client for Windows to support my office. When I use VMware (version 4.4) nothing keyed from the keyboard seems to work. I did not have VMware installed beforehand, so I cannot say this is
a Windows 10 issue, but VMware documentation states that the problem might be software blocking keystroke logging. Does Windows 10 have this feature and can it be turned off?

***Post moved by the moderator to the appropriate forum category.***

 

Keyboard input stops working in Windows 10 when running VMware Horizon Client

Hi Michael,

We did a quick search about VMware Horizon Client and there might be an updated version other than what you are currently using. The version 7.1 was the latest release and that might just make a difference. However, if you want to use that version, try to
run the software in compatibility mode. If the issue persists, reinstall the driver for your keyboard.

Please advise as necessary.