Sunday, May 20, 2018

Google Chrome Portable, browse with speed, simplicity and style
It won't crash... It's really fast. —J. R. Raphael, PCWorld.com, Sep 2, 2008.
Chrome is not just the cure for slow browsing. It has a number of other key features to recommend it, including excellent HTML standards compliance, its own copy of Flash, its own PDF viewer, automatic updating, synchronization across computers, incognito viewing, and many extensions. —Martin Heller, InfoWorld.com, Feb 19, 2014.
Google Chrome is a fast, simple, and secure web browser, built for the modern web.

GoogleChromePortable_66.0.3359.181.paf
Size: 224 MB (235,196,416 bytes) Packed Size: 73.5 MB (77,123,584 bytes)
MD5: 43350A5C99F6569DE90C269DB7989318


GoogleChromePortable_66.0.3359.181_32_64_bit.paf
Size: 442 MB (464,220,160 bytes) Packed Size: 133 MB (140,001,280 bytes)
MD5: 1D9FAF05A7DA1C815D6A923EB1AF7A63


More releases... More releases...

Google Chrome Portable for Windows XP/Vista  Google Chrome for Windows XP/Vista — Legacy Release

GoogleChromePortable_49.0.2623.110_XP_Vista_32_64_bit_rev_3.paf
Size: 353 MB (370,982,912 bytes) Packed Size: 95.5 MB (100,237,312 bytes)
MD5: 5B5747BE5D43EABACCD1E1BE61860F13

Google Chrome build for NPAPI-plugins (Java, Silverlight, etc.)  Google Chrome NPAPI-friendly build — Legacy Release

GoogleChromePortable_44.0.2403.157_NPAPI_rev_1.paf
Size: 170 MB (178,368,512 bytes) Packed Size: 52.9 MB (55,476,224 bytes)
MD5: 98371C723945E3061C272D220DC2C332

Release Notes

Single Bit and Dual Bit Releases
You can use these releases interchangeably, both use the same data profile. You can upgrade to the single bit release, or later upgrade it to the dual bit release, or vice versa.
The single bit (32 bit) is for those who want to save space.
The dual bit (32/64 bit) is for users who want to use the 64 bit version of the application on Windows 64 bit. And since it also has 32 bit application binaries, it will still run on Windows 32 bit.
External Download Managers Integration
Read an example on how to integrate external download managar—for eg. FDM 5—in the help file.
Portable plugins
  • Flash Player is included, get the latest one here: Flash Player.
  • More in the help.htm...
Other NPAPI-friendly browsers

DIY/Do It Yourself: Upgrade to the Latest Release

Requirements 7-Zip, NPP/Notepad++ or other text editor, PortableApps.com Launcher Generator/PAL, PortableApps.com Installer/PAI.

  1. We'll use the 32/64 bit edition as example, you can infer from this example to upgrade the 32 bit only edition.
  2. Get the latest portable app. template, and extract the content with 7-Zip.
  3. Get the latest:
    1. Google Chrome release—both the 32/64 bit installers,
    2. Adobe Flash Player portable release,
    3. belaviyo's native client for Windows release.
  4. Put it in the same folder as the extracted template, in our example C:\0TEST.
  5. Open the 32 bit installer with 7-Zip → browse into chrome.7z\Chrome-bin folder → extract all of its contents to GoogleChromePortable _3264\App\Chrome-bin folder, Extract to App\Chrome-bin
    Do the same with the 64 bit installer but now to App\Chrome-bin64 folder.
  6. Open the Flash Player package with 7-Zip → browse into Pepper32 folder then extract pepflashplayer.dll to App\Chrome-bin\plugins folder, Extract Flash Player
    Then extract the 64 bit Flash Player in Pepper64 to App\Chrome-bin64\plugins folder.
  7. Extract the Windows native client package with 7-Zip to App\windows-native-client folder, Extract WNC
    Into App\windows-native-client
  8. Browse to GoogleChromePortable _3264\App\AppInfo and open appinfo.ini file with NPP. Replace the [Version] section with the latest version number. Make sure the PackageVersion entry is in 4 place digit, eg. 64.0.3282.140 not just 64.0.3282,
     [Version]
     PackageVersion=64.0.3282.140
     DisplayVersion=64.0.3282.140 (32/64 bit)
    
  9. Run PAL, paste the template folder address C:\0TEST\GoogleChromePortable _3264, and click Go—a new launcher will be created, Create new launcher
  10. Test the new launchers by following this guide.
  11. When all is OK, then delete the GoogleChromePortable _3264\Data folder, GoogleChromePortable.ini and run PAI, paste the package folder address C:\0TEST\GoogleChromePortable _3264, and click Go—to create the installer package. Create installer
  12. Use the installer package to upgrade your portable application. Don't forget to at least backup your Data folder before any upgrade :)
  13. If you find any changes that's not handled by the launcher, consult the PAL help file to modify the launcher yourself or ask for our paid upgrade support.

Portability Notes

  • Google Chrome writes to Windows registry and data folder while running.
  • Flash player plugin writes to Windows registry while running.
  • Windows native client to enable external download managers will write to Windows registry and data folder while running.
  • IE Tab addon—if installed—writes to Windows registry and data folder while running.
  • Make sure it exits cleanly before plugging out your thumbdrive.

About the Publisher

Make the most of the web
Motivate Google Chrome development, follow them around the Web!