Citrix XenApp 1903 with Windows 2019 Server App server Error 1480 when launching applications but Desktop launches

[Tom Swift]

New build using Citrix XenApp 1903 on Windows 2019 application server.  Able to launch published desktop but getting error 1480 in Application logs when trying to launch standard applications like Notepad or Calculator.

 

Error Log:

Failed to launch application Notepad with command line "C:\Windows\System32\notepad.exe" on client 'Joes Computer' for domain/user 'mycorp\administrator' in session '4'. Ensure the application is installed and that the user has permission to launch it.

 

Screen shot from event log attached.

[Tom Swift]

ANSWER:

 

REGEDIT:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"AppSetup"="CtxHide.exe,UsrLogon.cmd,cmstart.exe"

 

The setting for AppSetup when broken only has UsrLogon.cmd and needs to have CtxHide.exe before UsrLogon.cmd and cmstart.exe after UsrLogon.cmd

 

Launching applications worked immediately after adding these settings.

 

On a different system that works but is ruing 7.15 LTSR and Windows 2012 R2 instead of 1903 on Windows 2019 the setting for AppSetup was "UsrLogon.cmd,cmstart.exe"

 

 

 

 

[Ganesh Raju]

What was the Working Directory path of  published Notepad application? It should be C:\windows\system32.

[JOANNE KEKES]

Thank you for posting this fix!  I had the same issue with Virtual Apps 1912 on Windows Server 2016 and this fixed it.

[noel spirit]

On 5/13/2019 at 8:05 PM, Tom Swift said:

ANSWER:

 

REGEDIT:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"AppSetup"="CtxHide.exe,UsrLogon.cmd,cmstart.exe"

 

The setting for AppSetup when broken only has UsrLogon.cmd and needs to have CtxHide.exe before UsrLogon.cmd and cmstart.exe after UsrLogon.cmd

 

Launching applications worked immediately after adding these settings.

 

On a different system that works but is ruing 7.15 LTSR and Windows 2012 R2 instead of 1903 on Windows 2019 the setting for AppSetup was "UsrLogon.cmd,cmstart.exe"

 

 

 

 

 

 

This fixed worked for us, thank you so much for sharing.