Anyone else install VDA 2402 and start experiencin...
# citrix-vad
m
Anyone else install VDA 2402 and start experiencing blank start menu's and broken taskbar pins? I've been running 2311 since it was released and since upgrading to 2402, I've been seeing start menu's and taskbars getting blown up.
👀 2
d
We don't publish desktops, so we don't see the start menu and taskbars, but I will say that I am not surprised by this based on our experience with 2402 so far with issues with black screens and other screen artifacts since upgrading to 2402. There are so many other features in 2402 that I need, we are still pushing ahead with the rollout as the screen issues are minimal in comparison. We have a ticket with Citrix to try and work through the issues.
m
I too was psyched for 2402. The timing of it was perfect for a desktop refresh project. I have too many irons in the fire right now and I'm afraid it's back to 2311 for me until 2402 CU1 is released. Whatever is causing the issue, it persists in the profile after going back to 2311. I'm having users report to me their Start Menu and Taskbar is messed up. On the other hand, it is plausible May updates have something to do with it. I'm running Server 2022.
d
That sucks. Hopefully 2402 CU1 will resolve the issues. We run 2016 and 2019 servers. Looking to start moving 2022 soon.
r
@Matt Sliva are you using any profile management solution? Did you open a support case? @Dennis Parker can you DM me some more details on the graphics issues you are facing? ( P.S: I'm working for Citrix HDX Engineering)
m
@Rody Kossen We are using Citrix UPM. No containers. I have not opened a support case yet. I want to get a handle on what's causing it. We run MCS and the last change included VDA 2402, WEM 2404, and May 2024 updates. I am trying to narrow down what's causing it.
👍 1
r
A few things you might want to look at as well: 1. Does it only happen to existing 2311 created profiles or also new ones 2. Create a CDF trace for a new profile ( initial login) and secondary login Can you share a few screenshots of the issue? ( DM is fine ) I would definitely recommend opening a case as well.
d
DM sent to @Rody Kossen as requested.
k
No issues here (at least none reported), we went from 2311 to 2402 w/ UPM Containers, Server 2022 w/ May 2024 updates, WEM 2404 as well. And we have another catalog using FSLogix 2210 HF4 same move from 2311 to 2402 VDA and WEM 2404/Server 2022. Our next jump will be to Windows 11 Multi-Session hopefully soon using the same UPM Containers (works so far in our testing).
👍 1
d
Found an apparent fix for my black screen issues which may or may not be related to anything you are seeing. We had some seamless flags set previously to workaround some black box issues in 2203 that also ended up creating some higher than normal CPU usage in WinLogon.exe on 2402. We were seeing 1-2% constant CPU usage on the 2402 systems in the TWI3.dll within the WinLogon.exe process. This led me to look at our seamless flags again and I removed two entries we had put in for other issues. Removing the two entries resolved both the WinLogon.exe CPU usage and the black boxes on the 2402 VDAs. The two flags: Disable Active Accessibility Hook: 0x4 Disable Shell Hook Agent 0x2000 Those were set on 2203 and now are not set on 2402.