Posting to see if anyone else has encountered this strange issue.
We've recently migrated from vmware to proxmox and using it hosts our Windows 11 single-user VDA's. Very impressed with the performance so far, however we have a very annoying issue which is stopping us rolling out company wide.
When the screen saver kicks in after 15 minutes of inactivity the session locks, but keeps the content of the last opened documents on screen, everything stays visible until you move the mouse or press a key then the lock screen then appears. We use CVAD 2511, Windows 11 25h2 (fully patched), nvidia a16 vgpu, but have also stripped this back to a bare deployment from ISO with only Citrix installed (no gpo, or policy applied) and still encounter the issue.
I've tried tweaking the display type from default, none, vmware compat, virtio and tried various suggestions from across the internet which nothing seems to resolve.
Just to add normal windows lock works as expected, it's only when setting a password protected screensaver or setting the timeout with Interactive Logon: Machine Inactivity Limit
Any one encountered anything similar or have any suggestions?
Thanks
We've recently migrated from vmware to proxmox and using it hosts our Windows 11 single-user VDA's. Very impressed with the performance so far, however we have a very annoying issue which is stopping us rolling out company wide.
When the screen saver kicks in after 15 minutes of inactivity the session locks, but keeps the content of the last opened documents on screen, everything stays visible until you move the mouse or press a key then the lock screen then appears. We use CVAD 2511, Windows 11 25h2 (fully patched), nvidia a16 vgpu, but have also stripped this back to a bare deployment from ISO with only Citrix installed (no gpo, or policy applied) and still encounter the issue.
I've tried tweaking the display type from default, none, vmware compat, virtio and tried various suggestions from across the internet which nothing seems to resolve.
Just to add normal windows lock works as expected, it's only when setting a password protected screensaver or setting the timeout with Interactive Logon: Machine Inactivity Limit
Any one encountered anything similar or have any suggestions?
Thanks
Last edited: