AppSyncExpireMessage=This application has been unable to contact its update server for %expire_days% day(s), so it is unavailable for use. Check your network connection to ensure uninterrupted service. AppSyncWarningMessage=This application will become unavailable for use in %remaining_days% day(s) if it cannot contact its update server. MSIArpProductIcon=%ProgramFilesDir%\Google\Chrome\Application\chrome.exe MSIInstallDirectory=Google Chrome (VMware ThinApp) Enable MSIFilename if you want to generate a Windows Installer package. For documentation and to obtain a complete list of options available visit: Lines that begin with a semicolon contain only comments and do not have any effect This file can be used to configure build and runtime options for packages I don't find the option to attach a file so I'll copy -paste the package.ini content here: With the isolation being MERGED, it does create it in the user profile.įor the Flash bit that does not work, did you follow that KB.? Google Chrome checks if this folder exists for this user, and if not, re-creates it. Then create a new "Default" folder, with MERGED isolation.Īfter the package is rebuilt, it should work fine. This is normal, because "Explorer.exe" does not and cannot run in the virtual environment.Īnother workaround than putting the file manually on the native environment, would be to rename the "%Local Appdata%\Google\Chrome\User Data\Default" to "%Local Appdata%\Google\Chrome\User Data\Default.old". If you use ProcMon to troubleshoot the behaviour, and look for "Google Profile.ico", you will see that the process "Explorer.exe" returns "PATH_NOT_FOUND". That file exists in the package, and if you copy the "Google Profile.ico" from the capture folder to this location on the native environment, it works!Īs you probably notice, I did bold the word "Windows". Click "Change Icon" and notice the error message : Windows can't find the file %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default\Google Profile.ico Right click "Google Chrome" and select "Properties" Google Chrome 34 and 35 are still showing the same behaviour.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |