Appvolumes issue packaging Google Chrome 80.x and above

[Natestack]

Hi All,

This is random but for some reason google chrome 80.x and above seems to not work.

Always get an ohhh snap from chrome

79.x and below works fine ?

Note the above is when doing an app capture when installing direct on the machine without appvol works fine.

Any idea as to why this maybe ?

Appvolumes 2.x and 4.0

Windows 10 1709/1809

[DanielLenz]

Hi Natestack,

we removed the chrome.exe from the HookinjectionWhiteList registry value, that worked for us with AppVolumes 4.

Best regards,

Daniel

[Ihatehobbits]

Had the same issue.

I created a GPO based on the chrome.admx and disabled Rendering Code Integrity

[DanielLenz]

are you sure?

for us it works without setting this policy to disabled and so we don't have an impact on security.

[sjesse]

Removing the hookinjection entry works but hinders performance which is why vmware suggests the gpo which is in the release notes for 4.0, which also work for earlier versions. The code integrity feature in chrome is what is breaking, since appvolumes redirects where the files really are the code integry feature panics, and the hookinjection key is a way to try and fix that but in some cases it causes problems.

[DanielLenz]

ok, then we will do as VMware recommends

[julatoski · Accepted solution]

Hi Natestack​,

An update for the "Aw,Snap!" error due to compatibility issues with Chrome version 78 and later is available for App Volumes 4. 

See the VMware App Volumes 4 Update 1 Release Notes for details.

We are also working to bring a similar update to 2.18.

[DanielLenz]

chrome 80.x in appvolumes works like a charm for us now Good job!

[julatoski]

Thanks, DanielLenz​.  Glad it worked!

[Natestack]

Sorry know this is for Chrome but i would assume

The new version will also work for Edge Chromium ? same again 78 and above seems to have the same issue (Have not tested since 4.0.1 or 2.18.2 come out)

[Ray_handels]

Are you really trying yo put Edge Chromium in an Appstack??

I would suggest installing it in the GI, I don't think an appstack will work with an application like this but just my 2 cents though.

[Sharick]

Aw, Snap hit me again. Upgraded App Volumes from 2.18 to 4.1. On a Windows 10 1909 created two packages for two different applications. MS Office 2016, Firefox, WinSCP, Notepad ++ , Adobe Reader DC, Wireshark, etc. all working fine except the Google Chrome which was downloaded directly from google, version 85. It was working fine on the packaging machine after the installation. But when attached to a non-persistent instant clone VDI it was giving the error.

[Natestack]

Hey Mate,

that’s strange I’m on

Appvolumes 4.1

windows 10 1809

Did a new package with about 50apps installed including Chrome 85 and all working for us.

I found that Group Policy can be a pain also the editing of the shortcut we found you couldn’t make Chrome default browser.

does it work with a slightly older version of Chrome ?

[Sharick]

Yes, the Google Chrome v78 browser was working Okay in App Volumes 2.18

To set the default browser I use DEM to run this command

cd %appdata%

SetDefaultBrowser.exe chrome

Exit

And copy the file SetDefaultBrowser.exe in %appdata% using DEM Files and Folder.

[Sharick]

Symantec SEP 14 is causing issues with Google Chrome and Edge Chromium both. It's not the App Volumes 4 but the antivirus issue. We may get an update from Symantec, but also thinking to get another antivirus software.

[MuskegonCountyI]

Is there a new update for the 2.18 agent version to fix this issue?  We are having this problem in our environment and we use agent version 2.18.

Thanks for the quick reply.

[jhol5]

It is resolved in 2.18.2:

https://docs.vmware.com/en/VMware-App-Volumes/2.18.2/rn/VMware-App-Volumes-2182-Release-Notes.html#r...

Or in 4u1

https://docs.vmware.com/en/VMware-App-Volumes/4.0.1/rn/vmware-app-volumes-4u1-release-notes.html#res...