Chrome Stable Channel Update

@chrcol No issues here with that link. Do you have some program filtering http/https on your machine?

 

its resolved, the cause was the experimental TLS 1.3 setting.

is already fixed in testing builds.

 

Chrome 55.0.2883.75 released!
Link: https://googlechromereleases.blogspot.ca/2016/12/stable-channel-update-for-desktop.html

 

Chrome 55.0.2883.75

Offline Installers
Consumer version
x64
redirector.gvt1.com/edgedl/release2/vllsgbu5dpgyjmk8asiyozmqf97zwlfqwz8lbdozvfzsmg4kf3a7d164wd47jiyapyh7r349khowbfgxdiwr3aluxcb30eap62m/55.0.2883.75_chrome_installer.exe
x86
redirector.gvt1.com/edgedl/release2/bo26ez30rcitgyuswe830vv04ejpvc3spzwynlc7unklxoctxbstgy0otycv79glemtj6mlpt681o1f8dja9ajvo6eed98on0ff/55.0.2883.75_chrome_installer.exe

Enterprise version (msi installers)
x64
dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
x86
dl.google.com/dl/chrome/install/googlechromestandaloneenterprise.msi

Differences between Consumer and Enterprise versions

Spoiler

1. Enterprise lands in Program Files (x86) even though x64 is used, while Consumer in AppData.
2. In a multi-user scenario, msi installs Chrome for all users by default.

Here are a couple other features you should be aware of:
1. If a user already had the Consumer version installed and you push out the Enterprise edition to their machine, the next time they launch the Consumer edition it will detect that the Enterprise edition is installed. After displaying an explanatory message to the user, the Consumer edition uninstalls itself, the user's Chrome shortcuts are updated and the Enterprise edition is launched.
2. The user's personal settings from the Consumer edition will be picked up by the Enterprise edition, as long as the version number of the Enterprise edition is greater or equal to the Consumer edition.

Therefore, I recommend to install Enterprise on a clean fresh system.
Also I recommend Enterprise version for those who are using programs like AppGuard or ReHIPS which block running programs from AppData folder.

FAQs (Enterprise version)
https://www.chromium.org/administrators/frequently-asked-questions

Policy List for Enterprise version: https://www.chromium.org/administrators/policy-list-3

 

Version 55.0.2883.75 m (64-bit)

Google Chrome is up to date.

 

55 is running fine for me on two 7x64 computers. Thanks for the heads up, folks.

 

Chrome 55 now prefers HTML over Flash:

To revert this behaviour, the flag chrome://flags/#prefer-html-over-flash can be disabled.
If it's not disabled, and you still want to use Flash on demand, there can be some issues:

 

Thank you for this.

 

There's no option to change the top chrome to non-material anymore

 

Is just me or the previous version of chrome when upgrade to this last version is no more resident after install, i mean for example OldChromeRemover didn't found the old version, and after checking the folder, no old version appears

Rules.

 

I noticed it too
There are always two versions in the directory, but with installing Chrome v55 i see only 55.0.2883.75, v54 "disappeared".

 

I've read some development talk recently that they have been planning on implementing some sort of delta patching or similar. I don't recall the exact terminology. But I'm wondering if that is the reason behind not having the old version of Chrome left behind here. Just a thought, anyway. I'll have to look into the bug reports further.

 

@mood
@WildByDesign

Thanks for your tips.

Rules.

 

The stable channel has been updated to 55.0.2883.87 for Windows and Mac. This will roll out over the coming days/weeks (Linux update will be next week).
https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop_9.html

 

Chrome 55.0.2883.87

Offline Installers
Consumer version
x64
redirector.gvt1.com/edgedl/release2/ita7hv5uktmxmkscmig7s9ehraz1im1do4ucck991uyfo3bqkdc55mn1vmrebmzqwrxt5ib6x8ohjojd56hwomb4593vqb9sfl1/55.0.2883.87_chrome_installer.exe
x86
redirector.gvt1.com/edgedl/release2/q7lq1jxh9nj7yg25wz7wzwdrac1ksyd9ys0puhi0l4dwmoww5f1xo61y4kl9pkwj4wdgbxpajbh0av7j7ec2q7nptu8uy11j2zo/55.0.2883.87_chrome_installer.exe

Enterprise version (msi installers)
x64
dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi
x86
dl.google.com/dl/chrome/install/googlechromestandaloneenterprise.msi

Differences between Consumer and Enterprise versions

Spoiler

1. Enterprise lands in Program Files (x86) even though x64 is used, while Consumer in AppData.
2. In a multi-user scenario, msi installs Chrome for all users by default.

Here are a couple other features you should be aware of:
1. If a user already had the Consumer version installed and you push out the Enterprise edition to their machine, the next time they launch the Consumer edition it will detect that the Enterprise edition is installed. After displaying an explanatory message to the user, the Consumer edition uninstalls itself, the user's Chrome shortcuts are updated and the Enterprise edition is launched.
2. The user's personal settings from the Consumer edition will be picked up by the Enterprise edition, as long as the version number of the Enterprise edition is greater or equal to the Consumer edition.

Therefore, I recommend to install Enterprise on a clean fresh system.
Also I recommend Enterprise version for those who are using programs like AppGuard or ReHIPS which block running programs from AppData folder.

FAQs (Enterprise version)
https://www.chromium.org/administrators/frequently-asked-questions

Policy List for Enterprise version: https://www.chromium.org/administrators/policy-list-3

 

Version 55.0.2883.87 m (64-bit)

Google Chrome is up to date.

 

Roll-out plan for HTML5 by Default
Link: https://blog.chromium.org/2016/12/roll-out-plan-for-html5-by-default.html

 

So I'm currently using henrypp's nosync Chromium, does anyone if AppContainer "Default" on this version is further elevated than "Untrusted"? Should I set it to "Enable" instead?

 

Not so much a update question, but has there been a work around for adding additional command line switches to chrome's "target" box. I thought it was a windows issues allowing only 260 characters, which I thought was fixed, but upon testing I can only add so many characters before it simply will not add any further

 

It's a limitation, 260 Characters is the maximum.
This is fixed, as you already noted. But first you have to enable it. On Windows 10 you have to set a registry key (see below):

 

Thanks for the info, mood. Someone mentioned a registry value before, but I also heard it was supposed to be standard. Either way, thank you!

 

Privacy (less Google) & Security (with Control Flow Guard compiled): best use henrypp (@hnerypp ?) stable Chrome nosync (with codecs)

Privacy flags
#disable-hyperlink-auditing
#reduced-referrer-granularity

Security flags
#enable-permissions-blacklist
#extension-content-verification (Enforce strict . . )
#mark-non-secure-as (Display a verbose . . .)
#enable-appcontainer on Windows 8 and higher
#enable-ppapi-win32k-lockdown on Windows 10 and higher

For hardcore Wilders members, some additional options are availabe

Privacy switch (could impact website functionality)
--disable-reading-from-canvas (blocks canvas fingerprinting attempts, although some say no-fingerprint is also a fingerprint)
--no-referrers (this overrules reduce referrer flag and completely stops passing referrer information)

Security flags (could impact website functionality)
#disallow-doc-written-script-loads (a fairly safe next level flag, since it is bad practice to deliver scripts this way)
#enable-top-document-isolation (Top document process is separated from its subframes when possible, but the subframes are all housed in a single renderer process in stead of separate processes as with third-party iframes in #enable-site-per-process)
#enable-site-per-process (support for rendering cross-site iframes in separate processes. In this mode, documents will share a renderer process only if they are from the same web, OOPIF was scheduled for Q3/Q4 2016, but is delayed due to , see note below).

Note: OOPIF increases number of processes and memory usage. Possibly new faster and memory saving Javascript interpreter ignition (#enable-ignition) is implemented first to compensate for performance effects of this security and stability improvement

When I enable-top-document-isolation and use startpage as default search engine I get a funny (positive) side effect that a blank tab is displayed with new tab.

 

So I navigated to: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem and enabled the "Enable Win32 Long Path" as well as entered the registry at

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FileSystem

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

and made sure LongPathsEnabled was set to 1, but the 260 characters are still limited within the "target" box under chrome properties. I also looked at a winaero article and they claimed that there was a group policy entry that enabled long paths but I don't have it as well as some others that have commented on the article.

http://winaero.com/blog/how-to-enable-ntfs-long-paths-in-windows-10/

Not sure what I am doing wrong but anyone else experiencing this?