XenApp 6_5 for Windows Server 2008 R2,XenApp 6_0 for Windows Server 2008 R2,XenApp 5_0 for Windows Server 2008
This article contains information to troubleshoot Event ID 1116 Printer autocreation failure. Reason: AddPrinter() failed with status 0x78A.

Symptoms or Error

Client printers fail to auto-create when users log on. An event is written to the Event Log with ID 1116 from source?? MetaFrame Events. The event contains Printer auto-creation failure. Reason:?? AddPrinter() failed with status 0x78A.

  • This affects administrators and users.

  • The user is unable to add a printer manually through the client network.

  • Converting hex?? 78A?? into decimal?? 1930?? and using net?? helpmsg?? provides the cause of the issue. Refer to the following output example:
    C:\Documents and Settings\Administrator.FTLRLAB>net?? helpmsg?? 1930

Note: The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.


Complete one of the following steps to resolve the issue:

  • If the preceding policy is set to?? Enabled, change it to?? Not?? configured.


    If the policy is set to?? Not?? configured, change it to?? Disabled.

  • Run the following command from the command prompt:

    Gpupdate?? /force

Note: You must not experience this?? issue if the policy is set to?? Not?? configured. However, the policy might be behaving like it is?? Enabled. Citrix Technical Support might ask you to set the policy to Disabled. If the policy is not behaving as expected, contact Microsoft Support.
Note: Windows 2008 blocks the installation of NT 4.0 (version-2) drivers.

If this?? Solution do not resolve the issue, this policy might be set at the domain level.

Citrix recommends customers to not use kernel-mode (version-2) drivers unless absolutely necessary as they can potentially crash a server. Instead, user-mode (version-3) drivers must be used exclusively to prevent crashes and maintain server stability.

Problem Cause

A Windows Server policy named?? Disallow installation of printers using kernel-mode drivers?? causes this issue.

User-added image


Join the conversation

Citrix Discussions

Open a case

Citrix Support