Then it's a restriction within Windows Explorer and the "target box" is always restricted to 260chars. I don't have Windows10, so i can't test it myself
What about using a batch file or something similar? Then the shortcut can link to that batch file. Just a thought, anyway. I have not tried it specifically.
I guess you forgot, in the meantime, had long holidays, followed by at least two more weeks of severe hangover.
Stable channel release for 56 is expected around Jan 31st, 2017. (see: https://www.chromium.org/developers/calendar)
With stable release 56 just about a week away, we know some things already: Control Flow Guard mitigation enabled for chrome.exe and chrome_elf.dll in stable OOPIF Status - On track to launch --isolate-extensions in M56 Stable Source: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/fJxdTRpX0kc More info: http://www.chromium.org/developers/design-documents/oop-iframes
56.0.2924.76 released! Link: https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html Web dev goodies: https://www.youtube.com/watch?v=F4DfGVbvRpY
@Krusty You're welcome. Mine failed first attempt as well but was then successful once I refreshed that tab and followed through with browser restart. Good to see Control Flow Guard reach the Stable masses.
Failed here as well. I then hit F5 and the error message disappeared and asked to restart as it usually do. New version is now installed without any issue. Thanks for the heads up, WildByDesign.
Chrome 56.0.2924.76 Offline Installers Consumer version x64 redirector.gvt1.com/edgedl/release2/10oqskd63pnxnoiwr53tmula79y4ppef6bpcehthvmo59k6a3aqbn2qc7s89vnvzdp98pz8ll0ssyrudbqyi51lcnqrq6z8o1srr/56.0.2924.76_chrome_installer.exe x86 redirector.gvt1.com/edgedl/release2/jyx448uu9mdv048xstkh0y4jal15l1w4mlyz5jne0s481583zeqogcmnsz1gq1ddfvytzk8wa4yuwgsuc9vyi1t3b31sc9xhoge/56.0.2924.76_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
If i disable plugins via Group Policy and start Chrome 56, they are all enabled After starting the previous version 55 (portable) they are all disabled (as expected) One comment is also mentioning it:
Installed 56 on two 7X64 machines. Needed to refresh after receiving system level error code: 7:0X80040905 at 97% completion. Relaunch at that point finished the install. So far so good, and thank you to the members reporting here about the update!
Have there been changes made to the group policy template with this release that conflicts with previous release?
I compared the policy templates for 55 and 56 and there is no difference (except that they have removed entries for "DiabledPlugins"). If they have removed DisabledPlugins, this might be the reason that Chrome doesn't even read the existing DisabledPlugins registry-entry and is "ignoring" it. Btw.: After looking into the Forum they did this "on purpose" because they will remove chrome://plugins/ (and plugins from Chrome itself) soon: Edit: tiny correction
As of stable version 56, win32k-lockdown (https://bugs.chromium.org/p/chromium/issues/detail?id=523278) is enabled by default and no option to disable.
FYI. Google Chrome Portable 56.0.2924.76 Stable (web browser) Released for the PA Platform, courtesy of PortableApps.com.
56.0.2924.87 released! Link: https://chromereleases.googleblog.com/2017/02/stable-channel-update-for-desktop.html