VMware Horizon Community
TomH201110141
Enthusiast
Enthusiast
Jump to solution

App Volumes 4.9 - Google Chrome not starting

After packaging the latest version of Google Chrome (version 111.0.5563.147) with App Volumes 4.9 I can not start Google Chrome in a Horizon Desktop (Windows 10 22H2, Horizon 2212 - 8.8).

Attached you see the error message:

TomH201110141_0-1680005228631.png

 

It's like Chrome can not be read because you can not read the security informations:

TomH201110141_1-1680005365308.png

 

 

 

0 Kudos
1 Solution

Accepted Solutions
Tolino
Contributor
Contributor
Jump to solution

Hi,

Did you perhaps upgrade FSLogix at the same time? We experienced exactly the same problem with Chrome and Jabber, after upgrading the environment yesterday, and found that the issue for us were related to FSLogix 2210 Hotfix 1. After reverting FSLogix to version 2.9.8361.52326, both applications started working again.

 

View solution in original post

4 Replies
Tolino
Contributor
Contributor
Jump to solution

Hi,

Did you perhaps upgrade FSLogix at the same time? We experienced exactly the same problem with Chrome and Jabber, after upgrading the environment yesterday, and found that the issue for us were related to FSLogix 2210 Hotfix 1. After reverting FSLogix to version 2.9.8361.52326, both applications started working again.

 

TomH201110141
Enthusiast
Enthusiast
Jump to solution

Hi @Tolino 

yes you a right. I found the answer yesterday in the Microsoft community (https://techcommunity.microsoft.com/t5/fslogix/fslogix-2210-hotfix-1-2-9-8440-42104-unable-to-launch...)

Not only Chrome is affected. Like you said Jabber and for me Acrobat Reader is affected too.

I hope it get's fixed as soon as possible. The quality of FSLogix is currently horrible, so many really disturbing and seriuos bugs.

0 Kudos
TomH201110141
Enthusiast
Enthusiast
Jump to solution

A fix is available, see the origin post at MS Tech community:

You need to modify your golden image:

reg add "HKLM\SYSTEM\CurrentControlSet\services\svdriver\Instances\App Volumes Instance" /v Altitude /d "132000" /f

https://techcommunity.microsoft.com/t5/fslogix/fslogix-2210-hotfix-1-2-9-8440-42104-unable-to-launch...

rgb99
Enthusiast
Enthusiast
Jump to solution

I ran into the same exact issue. The registry value change resolved the problem. Interesting that it's been over three months since the problem and workaround, yet there's no new FSLogix release.

0 Kudos