XenApp 6_5 for Windows Server 2008 R2,XenApp 6_0 for Windows Server 2008 R2,XenDesktop 7_1,XenDesktop 7
This article contains information to troubleshoot the black screen that appears when logging on to published desktop.

Symptoms or Error

Connecting to a published??desktop on a computer that is running Windows 7 or Windows Server 2008 R2, is not successful. A black or blue screen is displayed.


Solution 1

Add or set the following registry key on the XenApp server(s) or the to resolve the issue. This key can be added on a XenApp server or a desktop VDA:

Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Logon
Name: DisableStatus
Value: 00000001

Note: This registry entry needs to be created if it does not already exist.

Solution 2

The AppInit_DLLs registry??key can either contain the short name (C:\Progra~1\..) or simply the file name which can then be discovered using the PATH variable. When 8dot3 naming is enabled the short name would be valid and when 8dot3 naming is disabled short names would be invalid.

Modify the following reg key :
Key Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
Name: AppInit_DLLs
Type: String
Value: mfaphook64.dll, instead of giving the path name.??

Now the published application/desktop session would launch successfully.

Problem Cause

  • There are several that could have caused the issue.??A??majority of them are related to drive mappings or folder redirections in logon scripts, user profiles and/or GPOs, which point to an incorrect location or experience delays mapping during the logon process.
  • This problem happens because the AppInit_Dlls reg key considers space as a delimiter. So a value C:\Program Files\.. would be invalid. In certain scenarios the 8dot3 naming convention is disabled at the OS level and this breaks the AppInit_Dlls key.??


Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.


Join the conversation

Citrix Discussions

Open a case

Citrix Support