Error “This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package” Installation success or error status: 1620.


Attempting to install an .msp file (in my case Citrix XenApp 6.5 RollUp7) it fails to install with the following error message.

Error Message

msp error

Troubleshooting Steps

  1. Run the msp with the verbose logging switch for example:

.\XA650W2K8R2X64R07.msp /L*v C:\Temp\RollUp7.log

2. Have a look in the C:\Temp\RollUp7.log file and you’re looking for the highlighted in red below “C:\Windows\Installer\d5c63.msi

Log File:

=== Verbose logging started: 30/05/2018 8:17:04 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\windows\System32\msiexec.exe ===
MSI (c) (EC:F0) [08:17:04:901]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:F0) [08:17:04:901]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (EC:10) [08:17:04:917]: Resetting cached policy values
MSI (c) (EC:10) [08:17:04:917]: Machine policy value 'Debug' is 0
MSI (c) (EC:10) [08:17:04:917]: ******* RunEngine:
 ******* Product: {1471A89F-8CAB-4C46-89AB-942432D1DD3D}
 ******* Action: 
 ******* CommandLine: **********
MSI (c) (EC:10) [08:17:04:917]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (EC:10) [08:17:05:057]: Cloaking enabled.
MSI (c) (EC:10) [08:17:05:057]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (EC:10) [08:17:05:151]: End dialog not enabled
MSI (c) (EC:10) [08:17:05:151]: Original package ==> C:\windows\Installer\d5c63.msi
MSI (c) (EC:10) [08:17:05:151]: Package we're running from ==> C:\windows\Installer\d5c63.msi
MSI (c) (EC:10) [08:17:05:166]: Note: 1: 2276 2: 3: 75 
DEBUG: Error 2276: Database: . Codepage 75 not supported by the system.
1: 2276 2: 3: 75 
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
MSI (c) (EC:10) [08:17:05:213]: Note: 1: 1708 
MSI (c) (EC:10) [08:17:05:213]: Product: -- Installation failed.

MSI (c) (EC:10) [08:17:05:213]: Windows Installer installed the product. Product Name: . Product Version: . Product Language: . Manufacturer: . Installation success or error status: 1620.

MSI (c) (EC:10) [08:17:05:213]: MainEngineThread is returning 1620
=== Verbose logging stopped: 30/05/2018 8:17:05 ===


3.  Browse to C:\Windows\Installer\ folder (hidden protected OS folder) and rename the .msi to .old mentioned in the log file.

4. Re-run the .msp install

5. This time it will prompt for the original msi files, in my case it was the mps.msi


6. Browse to the original msi file where it may be and now the .msp file will install normally.

“Please wait for User Profile Services” – Logon delay


  • Windows Server 2008 R2
  • Citrix XenApp 6.5 RU5


During users logon to XenApp published applications and published desktops there can be a lengthy delay on “Please wait for the User Profile Services”, it can hang on this for up to 30 secs.


In the Group Policy Management browse to:

  • Computer Configuration
    • Administrative Templates
      • System
        • User Profiles

Modify the policy setting “Set maximum wait time for the network if a user has a roaming user profile or remote home directory” to “Enabled” and set the value Wait for network for maximum (seconds) to 0.

User session stuck on XenApp server


  • Windows Server 2008 R2
  • Citrix XenApp 6.5


User’s session is stuck on XenApp server, logging off from AppCenter doesn’t remove them.


1.Log onto the RDS server and launch Remote Desktop Services Manager or connect via another server.

2.Get the Session ID of the hung session from the Session tab:

  • Session: Disconnected
  • User: <Blank>
  • ID: <number>
  • State: Disconnected
  • ClientName: <Blank>
  • LogOnTime: Unknown

3.Click on Processes tab

4.Click on ID column to sort the processes by ID

5.Find the hung ID number

6.There is normally 3 processes visible

  • LogonUI.exe
  • Winlogon.exe
  • Csrss.exe

7.Right-click on winlogon.exe and End Process, once you end this process the other 2 will disappear.

8.DO NOT end process on csrss.exe, this will crash and reboot the RDS server

9.Now the user has cleared from the RDS server and from AppCenter.

Windows cannot connect to the printer – error 0x00000006


  • Windows Server 2008 R2 SP1
  • Citrix XenApp 6.5 RU5


Attempting to add a network printer the following error is displayed

  • “Connect to Printer. Windows cannot connect to the printer. No printers were found”
  • Operation failed with error 0x00000006


Microsoft’s resolution for this issue is to install KB2778831, however there are instance of this hotfix being applied and the issue still occurring.

Manual Fix:

  1. Open Registry Editor
  2. Browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers
  3. Back up then delete the Client Side Rendering Print Providers key
  4. Restart the Printer Spooler service
  5. Printers should now add successfully

Slow Logon’s when using Folder Redirection

Environment Windows Server 2008 R2 Citrix XenApp 6.5 RU5

Issue Slow logon speeds into XenApp Published desktop/applications, hangs for a period of time on ‘Applying Folder Redirection Settings’

Resolution On the XenApp Servers, apply the following registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer FolderRedirectionWait (REG_DWORD) = 0

Further details –

Service ‘Director Windows Management Instrumentation Provider’ failed to start.


  • Citrix XenApp 6.5 RU2-5
  • Microsoft Windows Server 2008 R2 SP1


Installing ‘Director Windows Management Instrumentation Provider’ (DirectorWMIProvider_x64.msi) onto Citrix XenApp 6.5, the component installs but then fails starting the service.


  • Recommend Fix:

Ensure the latest Microsoft Root Certificate has been applied – then install DirectorWMIProvider_x64.msi (ideal fix), the service will now start during install.

  • Alternate Workaround:

Enable “Turn off Automatic Root Certificate Update” in GPO under Computer Settings / Administrative Templates / System / Internet Communication Management, then install DirectorWMIProvider_x64.msi (this fix isn’t ideal but works, you might experience issues browsing to https sites of the latest Root Cert Update hasn’t been applied. Recommend to install KB970067 also, this hotfix resolves issues with high CPU for Wmiprvse.exe on Terminal Servers running Windows Server 2008.

Local Printer not printing in Citrix XenApp session


Windows Server 2008 R2 SP1

Citrix XenApp 6.5

Local HP Printer

Configured Policies:

– Auto-create client printers: (Auto-create the client’s default printer only)

– Automatic installation of in-box printer drivers (Disabled)

– Universal driver preference (EMF;XPS;PCL5c;PCL4;PS)


User has a local printer and logs into a Citrix desktop\application. The policy is configured to map through user’s local default printer. The printer maps through and appears in the users session. User prints to the local printer, print job spools, disappears and nothing prints out.



Reconfigured the ‘Universal driver preference’ driver order from