# Google Chrome Portable Help

## a new way to get online

Google Chrome Portable automatically downloads and installs Google's innovative Chrome browser and converts it into a portable form. Google Chrome is built for speed, security, and simplicity, so it will run well even on your aunt's ancient PC. Learn more about Google Chrome Portable...

- Support PortableApps.com's Hosting and Development

Go to the Google Chrome Portable Homepage >>

Get more portable apps at PortableApps.com

## Google Chrome Portable-Specific Issues

Installer and launcher licensed under GPLv2. More License Info.

### Known Issues

- The built-in update feature in Google Chrome will not function.
- Google Chrome Portable and local Chrome may not work simultaneously unless they are both the same exact version. This cannot be fixed with the current way Google Chrome's update system works.
- Google Chrome does not appear to run properly under some unofficial minimalistic Windows distributions. Only official RTM builds of Windows from Microsoft are supported.
- Currently, Java plugins will not integrate with Java Portable, but will only be able to use a locally installed Java. A future release of Java Portable or the PortableApps.com Platform may add the ability for Java Portable to work in Google Chrome Portable.
- When opting in to Portable Passwords (see GooglechromePortable.ini), a malicious individual will be able to determine the length of your passwords.

### Using an arbitrary version of Chrome, Chromium, or Iron

There are a few ways you can set up Google Chrome Portable to use a different version of Chrome or variants. First you must install Google Chrome Portable. Then you can remove the existing version of Chrome from App\Chrome-bin and replace it.

If your final program executable name is not App\Chrome-bin\chrome.exe you can use a GoogleChromePortable.ini file to have the launcher launch a different file. See the file in Other\Source for more info, you can use it as a template in the same directory as the launcher.

The following methods have been known to work for installing an arbitrary Chrome:

1. Copy a local Chrome installation

   Press Win+R to open the Run dialog. On XP and below type:

       %USERPROFILE%\Local Settings\Application Data\Google\Chrome\Application

   On Vista and above you type:

       %USERPROFILE%\AppData\Local\Google\Chrome\Application

   And click OK. This is the Google Chrome application directory. There are two ways to copy the files:

   1. Open the directory corresponding with the version number you want to copy, and then the Installer directory inside that. If you extract the Chrome.7z file you find therein into your App folder it will create a Chrome-bin directory and populate it with the proper files.

      OR

   2. Copy the entire directory you are in. You will want to exclude the following files:
      - old_chrome.exe
      - Any version number directory other than the newest (chrome.exe will only work with the newest).
      - The Installer directory inside the version number directory.

      All the files and directories go into App\Chrome-bin.

2. Download an arbitrary version installer

   This url will download any Chrome version you want, provided it's still on the server (old versions seem to be removed periodically):

       http://dl.google.com/chrome/install/<X>.<Y>/chrome_installer.exe

   Replace <X> and <Y> with the third and fourth numbers from the version. Example: 3.0.197.11 has a download url of http://dl.google.com/chrome/install/197.11/chrome_installer.exe

   Do not run this installer as it will silently update your local Chrome! Instead unpack it with an archiver program (7-zip works) and you will end up with a single .7z file. Extract this file into App and it will create the Chrome-bin file and populate it with the proper files.

### Installing plugins

If you wish to have portable plugins, be aware that many plugins are linked to locally installed programs and will not function correctly in a portable environment. When testing plugins be sure to test them on a system that does not have the plugin installed locally.

Note that if a system has plugins installed locally for Firefox or Chrome, your portable Google Chrome should find and use them automatically.

Since verison 5.0 Chrome includes a built-in Flash player so no Flash plugin is needed.

Starting with 6.0 (currently only in the Dev channel) Chrome will have a PDF plugin capable of rendering PDF files. No PDF plugin will be needed externally.

To install a plugin, first you need to find the location of a locally installed plugin. Run a local Firefox or Chrome and navigate to about:plugins. In Chrome, click "Details" on the right.

You should now see each plugin's details including the file path.

If you open the folder up and copy any relevant looking files to Google Chrome Portable\App\Chrome-bin\plugins (you'll have to create the plugins folder) it should work if the plugin supports being used this way.

You can open about:plugins in Google Chrome Portable to verify which plugins are being loaded and used. Again be sure to test the plugin on a computer without that plugin installed locally!

### Removing unneeded components

NOTE: This section is out of date. Be sure to keep backups in case your removals break something you want. Test thoroughly.

Chrome ships with a few features that can be safely removed:

To remove languages, open the App\Chrome-bin\<version number>\Locales directory, and remove any language file you do not need. en-US.dll is US English and may be the only one you want.

To remove DOM Inspector, remove the App\Chrome-bin\<version number>\Resources\Inspector directory. DOM Inspector will still be available within Chrome as an option but will not function (the popup window will have an error message).

To remove packaged Web Apps (GMail, Calendar, Docs) remove the appropriate directories from App\Chrome-bin\<version number>\Resources. Probably not worth it since they're mostly just a few icons.

In addition if you installed a custom Chrome version by hand keep in mind that the App\Chrome-bin\<version number>\Installer directory is not needed and should be removed. Normal Chrome only seems to keep it around for uninstallation purposes.

You can also experiment with removing App\Chrome-bin\<version number>\gears.dll to remove Google Gears support but I don't know if that will work or not. :) Same with gcswf32.dll and pdf.dll for the internal flash and PDF plugins.

wow_helper.exe is used for 64-bit support for the sandbox and if you don't intend to run on 64-bit you don't need it. It is not installed on 32-bit machines by the Chrome installer. There are also nacl64.* files which are probably 64-bit Native Client plugin stuff.

### Enabling Chrome's First Run dialog

You can trigger the first run dialog in Google Chrome to import bookmarks from the local machine by deleting App\Chrome-bin\First Run and then running Google Chrome Portable. Note that it works even if you have a profile, but I don't know if it'll preserve or wipe out your bookmarks when it imports, so be careful!

### Compressing with UPX

Though PAF has allowed the installer for Google Chrome Portable to be simplified, a downside is that UPX cannot be used to automatically compress the downloaded Chrome files. You can compress some of them by hand if you wish.

Do not compress the following files:

- avcodec*.dll - Random crashes with <video>/<audio>. UPX detects errors when you try to decompress.
- chrome.exe - Tabs no longer show content.
- chrome.dll - Not supported by UPX.
- wow_helper.exe, nacl64.dll, nacl64.exe - 64-bit binaries not supported by UPX.
- Locale DLLs - Chrome starts up with no text, pops up a blank dialog, and crashes.

The following files CAN be compressed without breaking Chrome:

- avformat*.dll
- avutil*.dll
- chrome_launcher.exe
- d3dcompiler*.dll
- d3dx9*.dll
- gcswf32.dll
- gears.dll
- icudt*.dll
- libegl.dll
- libglesv2.dll
- npchrome_frame.dll (Compacts in Chrome 6, not in Chrome 7)
- pdf.dll

New versions of Chrome may add more binaries, be sure to test Chrome thoroughly if you compress any of them.

### Copying a local profile

Press Win+R to open the Run dialog. On XP and below type:

    %USERPROFILE%\Local Settings\Application Data\Google\Chrome\User Data

On Vista and above you type:

    %LOCALAPPDATA%\Google\Chrome\User Data

This is your profile dir and should be copied to Data\profile. If you did it right you will end up with a Default directory and a Local State file in Data\profile. You may also have a few more files and folders depending on your profile settings.

You should exempt Default\Cache and Default\Media Cache from the copy. You may also want to trim your profile down a bit regularly, in particular the History Index files can get large. You should use the in-Chrome options for purging old data, or if you know how, vaccuum the SQLLite databases in your profile. Note that removing the Thumbnails file may seem like a good idea but then your icons on your bookmarks will be gone.

You can further reduce the profile size by disabling malware and phishing protection in Chrome and then removing the Safe Browsing files from the profile.

In the end it may be prudent to simply export your bookmarks from Chrome and then re-import them in a fresh profile to keep file sizes down.

### Cleaning up in case of a launcher crash

If the GoogleChromePortable process does not exit normally, it will leave some bits and pieces that need to be cleaned up, as most portable launchers will:

1. HKEY_CURRENT_USER\Software\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}\pv will be set to the Portable Chrome version. If the local Chrome is a different version this value will need to be adjusted to match. If there is no local Chrome the entire key should be deleted.
2. HKEY_CURRENT_USER\Software\Google\Update\Clients\{4ea16ac7-fd5a-47c3-875b-dbf4a2008c20}\pv will be set to the Portable Chrome version. If the local Chrome CANARY is a different version this value will need to be adjusted to match. If there is no local Chrome CANARY the entire key should be deleted.
3. HKEY_CURRENT_USER\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96} should be deleted if Chrome is not installed locally.
4. HKEY_CURRENT_USER\Software\Google\Update\ClientState\{4ea16ac7-fd5a-47c3-875b-dbf4a2008c20} should be deleted if Chrome CANARY is not installed locally.
5. HKEY_CURRENT_USER\Software\Google\Rlz should be deleted.
6. If there is no local Chrome HKEY_CLASSES_ROOT\Applications\chrome.exe, HKEY_CLASSES_ROOT\.htm\OpenWithList\chrome.exe, and HKEY_CLASSES_ROOT\.html\OpenWithList\chrome.exe should all be deleted. Otherwise HKEY_CLASSES_ROOT\Applications\chrome.exe\shell\open\command should be set to the location of the local chrome using the following templates.

   For XP:

       "C:\Documents and Settings\<Username>\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" -- "%1"

   Vista and 7:

       "C:\Users\<Username>\AppData\Local\Google\Chrome\Application\chrome.exe" -- "%1"

   Chrome overwrites this value with it's own location when run portably so the launcher will restore it on close.

7. Make sure there is no Data\settings\GoogleChromePortableShuttingDown and delete it if it exists.
8. %TEMP%\GoogleChromePortable\profile should be copied back to Data\profile to avoid losing any profile data changed last session, if copying the profile locally was on. %TEMP%\GoogleChromePortable\profile\Default\Cache should be excluded if it exists.
9. %TEMP%\GoogleChromePortable\rlz.reg should be merged into the registry if it exists.
10. %TEMP%\GoogleChromePortable should be deleted.

### Command line options

Google Chrome has some experimental features which require command line parameters to activate. Some others are for diagnostic purposes. You can enable these by copying GoogleChromePortable\Other\Source\GoogleChromePortable.ini to GoogleChromePortable\ and adding the parameters to the AdditionalParameters field. For example:

    [GoogleChromePortable]
    AdditionalParameters=--disable-extensions --enable-webgl

This disables extension support in Chrome and enables experimental WebGL support.