Craig_00's Posts

Yes, we are also seeing intermittent freezing on a bunch of versions. We have seen in for sure on 2106 and 2111.1 Strangely it seems to only affect a few people, so we have a range of client versions in play at the moment. Some people on 2111.1 and have no issues, others got intermittent disconnects and we had to roll them back to 2106 or 2103. Some folks started getting another issue, so we went back further to 2012. The other issue is a strange display error where the top toolbar of whatever application is on the left monitor goes blank. It's still possible to click functions on the toolbar (if you guess where the mouse is), but the top 1 inch or so of the left monitor never refreshes. Either disconnecting and reconnecting the session, or setting the client to a single display and back to multiple will fix it temporarily. We've not taken out a ticket with VMware yet - kind of lost patience with them because we really don't have spare time and equipment for testing poor software releases.

You can get the older versions from VMWare's site This is the Windows version: https://customerconnect.vmware.com/en/downloads/details?downloadGroup=CART22FQ2_WIN_2106&productId=1027&rPId=83268 The version number is in the dropdown box near the top. 2106 is not affected. In VMWare's infinite wisdom, they have decided not to publicly release the fix yet. 

Hi YunYiQun Issue appears to be resolved for me with the Windows sandbox version provided. Initial testing with two client PCs appears good. I will leave the sessions open all day to verify, and try a couple of other machines early next week. Craig.

I got given an 'engineering build' early last week that was meant to collect more logs. It instantly crashed as soon as I pressed any key in the remote session. I submitted the logs, then got given a different build, also for log collection. I submitted those logs on Friday. Nothing since.  I ended up customising our Horizon landing page so the Client download link no longer points to vmware's website for the latest version. This has helped a bit, as I can direct new hires or staff getting new computers to a working version. Unfortunately, I still can't stop my staff from periodically updating to the latest build through the client itself.

When we first hit the issue, it turned out our horizon support contract had lapsed for a couple of weeks, or I would have opened a ticket straight away. We are dead in the water with all client PCs that install the 2111 version. Does not matter what OS version or build is on the client PC, and we have a mixture of Server 2016 and Win 10 Enterprise remote systems. We don't have the option of PCoIP, and a couple of our key applications don't perform well over RDP, so we are only using BLAST. Any remote session is totally unusable until we roll the client version back to 2106. We don't get one or two key repeats, we get thousands, and no matter how long the session is open for, the repeats never stop. As others have said, disabling typematic does fix the issue, but makes the system unusable in other ways because key repeats are not possible at all. Our staff are all working from home, so we can't prevent them upgrading. We've repeatedly sent out messages not to do so. We're getting a couple of support incidents a day to fix the issue on a home PC.

Still an issue for us. Despite telling people not to upgrade, we are having to uninstall 2111 and reinstall 2106 almost daily on staff personal computers. This is having a serious impact on staff productivity and on our support team. I have a support request open with VMWare. #22301149002  

Hi YunYiQun I tried the sandbox version on a machine that had never previously had the vmware client installed. It functions fine. No issue with the keyboard repeat. At this time, I am not able to test the sandbox version on a machine that was affected by the issue - they were all staff personal machines, so I don't have the ability to remotely install software. When the issue occurred, staff had logged into their account on a Server 2016 remote desktop. Immediately after logging in, they tried to open any application / web browser. As soon as they type any key, many dozens of characters appear. Pressing a key once, then pressing backspace once would delete all of the keys. I will keep the sandbox version handy in case I get further reports, but for now we've advised staff not to upgrade client versions.

Not going to try that fix. Your own documentation states: This configuration prevents intended key repeat. Cannot input character repeatedly on desktop pool by holding down a key. https://kb.vmware.com/s/article/59631    

We have now had four employees working remotely 'upgrade' to the 2111 client on their personal computers report this issue. In all four cases, downgrading to 2106 has fixed the problem. At this time, we are unaware of anyone successfully using this version with our Horizon platform. We have issued a company-wide bulletin to postpone any further upgrades until this is reported fixed. All Windows 10. Mixture of editions (Home, Pro, Enterprise) all affected. Mixture of release versions. All US English keyboards with no special input hardware. Our UAG and Connection server and agents are Horizon 7.