VMware Horizon Community
Donwurzel
Enthusiast
Enthusiast

Thinapp Not Installed on Clients Windows 10 20H2

Dear Community, 

I updated the Golden Image from Windows 10 1909 to 20H2 and now the Thinapp won't installed on the Client:
If I copy the Thinapps (5.2.9) local to the machine it works without problems. The Windows 10 1909 Clients are not affected, their the Thinapps works.

In Vmware View Horizon Admin Console following Error is shown up:

OpenPackageError details. HRESULOT hr = 0x80010105 ErrorInfo object is NULL, There was no error object to return

In the Client Workstation Windows 10 20H2 following Errors are shown in the VDM Log of the Client:
2021-04-09T09:11:41.449+02:00 DEBUG (1570-1134) <pool-3-thread-4> [AbstractTopicPublishingManager] (DesktopControlPublishingManager-agent) Message published.
2021-04-09T09:11:44.164+02:00 DEBUG (1570-1158) <SwiftMQ-SessionPool-5> [msgid] Validating message with ID: 'null'.
2021-04-09T09:11:44.164+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [wsnm_desktop] DesktopManager got a InstallApps message
2021-04-09T09:11:44.164+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinApp Install applications called for 1 applications
2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] Application ID: app1
2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinAppMgmt: Application Details: APP_CN = "8c5c43e5-f12c-4843-a942-e2907e0ab39d"
OPERATION = "INSTALL"
INSTALL_FLAGS = "0"
APPLICATION_PATH = "\\xxxxxl\xxxxx$\Igel6iH20\bin\igel6i.msi"
INSTALL_TYPE = "FULL"
APP_DISPLAYNAME = "Igel6i"

2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinAppMgmt: Opening application Igel6i package at path: \\xxxxx\xxxxxx\Igel6iH20\bin\igel6i.msi
2021-04-09T09:11:44.214+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinApp: OpenPackage
2021-04-09T09:11:44.239+02:00 ERROR (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] OpenPackage failed, path =  \\xxxxx\xxxxxx\\Igel6iH20\bin\igel6i.msi. Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return.
2021-04-09T09:11:44.354+02:00 DEBUG (0B84-1E64) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinAppMgmt: Success, returning Application Response: APPLICATION_COUNT = "1"
app1 =
APP_CN = "8c5c43e5-f12c-4843-a942-e2907e0ab39d"
OPERATION = "INSTALL"
RESULT = "FAILED"
SkippedErrorContext = "OpenPackage"
SkippedErrorCode = "-2147417851"
SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."

Has somebody the same error?

thx for your helpt

Best Regards 

 

 

Reply
0 Kudos
6 Replies
Donwurzel
Enthusiast
Enthusiast

What I found out is  that I have a Horizon Agent 7.11 installed in the Clients and that Version ist not compatible with Windows 10 20H2 - I will update and reply if the error is solved after the upgrade...

Here the Product Matrix
https://kb.vmware.com/s/article/2149393

 

Reply
0 Kudos
Donwurzel
Enthusiast
Enthusiast

Updated - Horizon Agent to 7.13 / DEM to 2103 but the error still exist, No Thinapp Creation with the new Windows 20H2.

021-04-19T14:44:12.367+02:00 ERROR (0AA8-09A8) <MessageFrameWorkDispatch> [ws_thinappmgmt] OpenPackage failed, path = xxxxxx\igel6i.msi. Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return.
2021-04-19T14:44:12.482+02:00 DEBUG (0AA8-09A8) <MessageFrameWorkDispatch> [ws_thinappmgmt] ThinAppMgmt: Success, returning Application Response: APPLICATION_COUNT = "2"
app1 =
APP_CN = "d3daf633-0aaa-458d-8c04-84003972c78b"
OPERATION = "INSTALL"
RESULT = "FAILED"
SkippedErrorContext = "OpenPackage"
SkippedErrorCode = "-2147417851"
SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."
app2 =
APP_CN = "298e567c-6efe-4a92-a03f-fca18cb1cee6"
OPERATION = "INSTALL"
RESULT = "FAILED"
SkippedErrorContext = "OpenPackage"
SkippedErrorCode = "-2147417851"
SkippedError = "Error details. HRESULT hr = 0x80010105. ErrorInfo object is NULL, There was no error object to return."

The Same Image with 1909 works, but a clone with 20H2 gets that error....

Thx for your Help !

Best Regards Wurzel

 

 

Reply
0 Kudos
DCasota
Expert
Expert

Does the Windows 20H2 image exclude the Msft KB4592438? It has been mentioned in 5.2.9 Release Notes.

Reply
0 Kudos
Donwurzel
Enthusiast
Enthusiast

Yes, the KB4592438 s not installed on the Golden Image - I think otherwise the Thinapps would 'nt work if i start them. (I can manually copy the Thinapp to the Image or start it over UNC Path, both work)

The only Problem I have is that the Thinapp isn't copied to the image.
I think I will change the behavior and start the Thinapps over UNC Paths with Shortcuts to them, or copy them to the Golden Image manually....

Best Regards Wurzel

 

Reply
0 Kudos
DCasota
Expert
Expert

 

Since W10 there always were additional SMB v1-3 impacts concerning access from newer patches and/or releases. Smb/cifs file server And W10 client should support at least one smb version+dialect (SMB v1 <-> SMB v1, SMB v2 <-> SMB v2, SMB v3 <-> SMB v3). This is relevant for Thinapp' unc path connections method, too.

 As the smb/cifs file server hasn't changed, and assuming it is more desirable to have a 1909 & 20H2 working set, you could do a few workarounds to check. I've started a listing which may help.

1) Allow SMBv1 interoperability (see thread)
W10 clients:
Get-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"
Disable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol"
Reboot
Enable-WindowsOptionalFeature -Online -FeatureName "SMB1Protocol" -All

:: Autostart on user login. U = Driveletter for the server share
net use U: “\\server\share” /persistent:no
reg.exe ADD HKCU\Network\U /v ProviderFlags /t dword /d 1 /f

Windows server: KB5000856

2) Allow SMBv2 Insecure Guest Authentification
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters AllowInsecureGuestAuth dword 1

3) SMBleed "SMBv3" related patch
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters DisableCompression dword 1

SMB dialect key features mapping between server and client is signifant. Some 'Microsoft SMB'-only descriptions are:

SMB 3.0 with encryption is supported by Microsoft Windows 8, Server 2012 and above.
For Linux, Samba 4.0 and above supports SMB 3.0 (see https://wiki.samba.org/index.php/LinuxCIFSKernel). 

That said, the SMB (3.x) compliancy for storage solutions never was a client golden image property only.

Reply
0 Kudos
DCasota
Expert
Expert

Spoiler
You might identify which SMB version *should* and *are allowed* be used between server and client. On W10 client you can run get-smbclientconfiguration and compare EnableInsecureGuestLogons, EnableSecuritySignature, RequireSecuritySignature with the settings required from the specific file share server. Hope this helps. Daniel

 

Reply
0 Kudos