New issue
Advanced search Search tips

Issue 594063 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Extensions corrupting - Virtual Desktop Enviroment

Reported by c.schw...@ofid.org, Mar 11 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. In a freshly created Domain Profile open Chrome
2. Install a Extension (in this example we use AdBlock Plus, most common in our company)
3. LogOff and LogOn again
4. Chrome Extension is corrupted (view Attached File for better understanding)

What is the expected behavior?

What went wrong?
Things we tried out as of now:

) Changed the user data dir and cache location via gpo to different places (now it is not set, default location - AppData/Local which is synced via Persona)
) updated to newest version of chrome - and on a test pool to different versions (64 and 32 bit)
) we checked the folder access rights

WebStore page: AdBlock Plus

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: stable
OS Version: 6.1 (Windows 7 64bit)
Flash Version: 21.0.0.182

We are using Persona Managment from VMware so sync user data and settings, VMware vSphere and Horizon for our Enviroment, Floating non-persitent Pool
 
ExtensionsProblem.png
77.5 KB View Download

Comment 1 by c.schw...@ofid.org, May 23 2016

push
We observed the same issue, and resolved it by moving the profile to a network drive. You will have to workaround other issues since both scenarios sre not officially supported. See also the discussion with pkasting at https://www.reddit.com/r/chrome/comments/52y42q/announcing_chrome_53/
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 16 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment