We have many customers reporting that the CtxHdxWebSocketService (CitrixHDX HTML5 Video Redirection) service has stopped and you are unable to start it. Has anyone else seen this today? All affected customers use PVS services, but nothing has changed.

🙈 Strange issue… Thanks!

We’ve got that today on around 15 VDA’s.

Sophos has a similar issue 🙄: https://community.sophos.com/intercept-x-endpoint/f/discussions/145511/enpoint---threat-detection---ssl-inspection-active---invalid-date

Look to have the same here on S2019 running 1912CU7

Different service but... Does the issue also affect the Teams redirection? Got a customer who reports that since today, Teams says "Citrix HDX not connected"

That service does affect Teams redirection

Yeah it affects ms teams optimization as it shows as not optimized

wtf who brings the crate of beer for this..............................

Teams is not optimized anymore, well that’s normal if the corresponding service is stopped 🤨 We have some trouble this morning with customers…

Set-Date -Date (Get-Date).AddDays(1) Start-Service CtxHdxWebSocketService Set-Date -Date (Get-Date).AddDays(-1) 🙂

I presume the issue automatically goes away tomorrow 01/03/2024

When you realize the 29.2 bug is the new y2k bug! 🤦🏻‍♂️

We had that laugh earlier.

prepare for switch to daylight saving time next month 😄

Already got the daylight saving change pencilled in 😂

a twitter user just reported when running the above workaround defender starts a full scan (bc he thinks he hadnt scanned for a day..) just fyi

Hi, FYI, we are aware of this issue and looking into it. https://support.citrix.com/article/CTX617043/citrix-hdx-service-fails-on-29th-february

for defender users: add this before: Get-ScheduledTask -TaskName "Windows Defender Scheduled Scan" | Disable-ScheduledTask and this after: Get-ScheduledTask -TaskName "Windows Defender Scheduled Scan" | Enable-ScheduledTask

Just FYI the bug also uses UTC not the local machine time, as many of my customers VDAs had the service crashing out when they booted/rebooted this morning on 1 March AEDT (UTC+11). Weirdly it is letting us just start the service with no more crashing even though in UTC it's still the 29th?