Bryan Klinkel Posted July 31 Share Posted July 31 Our environment is Horizon 2212 on Windows 10 22H2 and everything was working great until folks that WFH had their Horizon clients auto update to Horizon client 2406. Now sessions are crashing. Submitted a ticket but wanted thoughts from the community. 1 Quote Link to comment Share on other sites More sharing options...
Employee Doug Arcidino Posted July 31 Employee Share Posted July 31 Are you able to describe the situation a little bit more? What exactly is crashing? Quote Link to comment Share on other sites More sharing options...
Bryan Klinkel Posted August 1 Author Share Posted August 1 The client opens fine but when you try to connect to a server, the client crashes/disappears while leaving the icon in the tray. Now, there are times where you are able to connect to that server but once you disconnect from the session and later try to reconnect to that server, the client reverts back to the crash behavior. Quote Link to comment Share on other sites More sharing options...
PAB Posted August 12 Share Posted August 12 Had this exact same problem using Horizon Client 2406. Rolling back to 2312.1 resolved the issue. Quote Link to comment Share on other sites More sharing options...
Mr_SCB Posted August 12 Share Posted August 12 Out of interest, which OS are the WFH users running on their local machines? (W10, W11, MacOS, Other?) I use Server 2022 on my local device at home (makes life easier compared to a desktop OS) and have been running the 2406 Client since it was launched without issue. Quote RegardsMr_SCB Link to comment Share on other sites More sharing options...
virtualblog Posted August 19 Share Posted August 19 Noticed some tickets about the new Horizon client 2406. People having issues with connecting and authenticate. With the old client everything was working great. Not all clients have the same issue. At my personal device the 2406 client is working like a charm. I'm also interested in the OS of the WFH Users. At this moment we have a IT call in combination with a personal device "Windows 10 Home edition 22H2, build 19045.4780" Quote Link to comment Share on other sites More sharing options...
Bryan Klinkel Posted August 23 Author Share Posted August 23 For the WFH users OS, since its their personal PCs, we usually don't have that info unless necessary. We were doing the same thing as others here, just revert back to an older version of the client. This has been happening on my own PC at home and I have W10 22H2 plus I use MS Win Sec/Defender. Odd thing is that if I turn off the Win Sec Control Flow Guard for vmware-view.exe, the 2406 client works like a champ. If I enable CFG again, the client goes back to disappearing. Quote Link to comment Share on other sites More sharing options...
Tanner Posted September 4 Share Posted September 4 (edited) We have the same issue. Since the update to the client anyone on 2406 client cannot connect to our environment. Any update or anyone find a resolution to this? Edited September 4 by Tanner Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted September 4 Share Posted September 4 Not really helpfull I guess.. be we are not seeing any major issues with using the 2406 client in our environment. Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Diego Posted September 10 Share Posted September 10 On 4/9/2024 at 20:52, Robin Harmsen said: Supongo que no es muy útil, pero no vemos ningún problema importante al utilizar el cliente 2406 en nuestro entorno. yo tengo el mismo problema en mi Chromebook vmware horizont client en esa versión funciona pero no abre las maquinas virtuales me hecha en el momento. en la versión anterior si funciona bien. Quote Link to comment Share on other sites More sharing options...
Diego Posted September 10 Share Posted September 10 On 9/4/2024 at 8:52 PM, Robin Harmsen said: Supongo que no es muy útil, pero no vemos ningún problema importante al utilizar el cliente 2406 en nuestro entorno. yo tengo un problema en chrome os flex, en mis maquinas el vmware horizont client versión 2406 no funciona ya que el programa entra pero al ejecutar la maquina virtual se cierra inesperado. en el log no logro comprender el porque de ese suceso cuando la versión anterior funciona perfectamente. hasta ahora mis trabajadores siguen trabajando con la versión anterior Quote Link to comment Share on other sites More sharing options...
Schmad7 Posted Tuesday at 02:09 PM Share Posted Tuesday at 02:09 PM We had the same issue. After we collecting debug logs on the client while initiating the remote connection, they believe they've found a bug in version 2406 and they'll be releasing a fix. No ETA at the moment but I'll try to update when I have one. Quote Link to comment Share on other sites More sharing options...
Diego Posted yesterday at 03:32 PM Share Posted yesterday at 03:32 PM Gracias espero respuesta Quote Link to comment Share on other sites More sharing options...
Employee Victor León Posted yesterday at 04:35 PM Employee Share Posted yesterday at 04:35 PM Hello, There will be a dump file in the client log bundle. You can use WinDbg to review the file. Is the faulting module: C:\Windows\SYSTEM32\ntdll.dll ? We are working on a fix with above module coming with 2406.1 Quote Link to comment Share on other sites More sharing options...
Schmad7 Posted 4 hours ago Share Posted 4 hours ago Just heard from support that they'll be releasing version 2406.1 in late October and that should fix the issue supposedly. Quote Link to comment Share on other sites More sharing options...
Bryan Klinkel Posted 3 hours ago Author Share Posted 3 hours ago 20 hours ago, Victor León said: Hello, There will be a dump file in the client log bundle. You can use WinDbg to review the file. Is the faulting module: C:\Windows\SYSTEM32\ntdll.dll ? We are working on a fix with above module coming with 2406.1 There aren't any dump files in the log bundle which is also odd. Hopefully the fix will resolve the issue. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.