CVAD 2402CU2 - ICA Session Logoff Hangs at "Signing out" Due to Stuck Session Printer Deletion in Wfshell.exe

book

Article ID: CTX697062

calendar_today

Updated On:

Description

Symptoms

  • Users were unable to log off Citrix ICA sessions.
  • The session remained stuck at the "Signing out" screen indefinitely.
  • The issue occurred only in ICA sessions.
  • Local console logoff and RDP logoff worked normally.
  • The affected sessions required administrative intervention to terminate.

CDF traces showed that session printer deletion was initiated during logoff but never completed. Process dump analysis found:

  • Winlogon.exe was waiting for wfshell.exe to exit before completing logoff.
  • wfshell.exe was stuck processing session printer deletion and could not exit normally.

As a result, the logoff sequence was blocked and the ICA session remained in the logging off state.

Cause

A redirected printer could not be deleted successfully during user logoff.
wfshell.exe remained blocked while performing printer cleanup, preventing Winlogon.exe from completing the logoff process.

Resolution

The customer disabled Citrix printer mapping policies.

After printer redirection was disabled:

  • ICA session logoff completed successfully.
  • wfshell.exe exited normally.
  • The logoff hang was no longer observed.

Recommend to further investigate the affected printers, including their connectivity and availability, to identify the underlying printer-related issue.

Issue/Introduction

Users experienced abnormal logoff behavior in Citrix ICA sessions where the session remained indefinitely at the "Signing out" screen and could not complete the logoff process. The issue was reproducible only in ICA sessions. Logoff operations through local console sessions and Microsoft RDP sessions completed successfully.

Analysis of CDF traces and process dumps collected during the hang showed that Winlogon.exe was waiting for wfshell.exe to exit, while wfshell.exe was blocked during session printer deletion operations.

Disabling printer mapping policies immediately resolved the issue, confirming that the printer redirection process was the root cause. Further investigation of the redirected printers and their connectivity was recommended.