[hacksonx]

"{ Version 57.0.2987.98 (64-bit)

   Updates are disabled by your administrator

"}

Guess I will only be able to comment on these when I get home. The full screen screenshot feature is going to be a welcomed addition. I will especially have to teach it to the BA's since they always want to take screenshots to show to business when design is finished but test is still acting up.

[james-skemp]

This has been showing up on my work machine since our IT group started installing Chrome on all machines.

If you do a search for that and 'Chrome' you'll find sites that tell you how to work around the issue.

Chrome has long supported the ability to workaround non-admins the ability to install Chrome (local user directory I believe) so no surprise there's a workaround for this as well.

Personally, I found that the registry key wasn't matching what those say, but Chrome still has that message but will update. Your mileage may vary.

[symlinkk]

What good reason would a sysadmin have to disable web browser updates?

[steven777400]

It's possible that a new version could have a breaking policy change. For example, all our intranet apps are served over HTTP. At some point, that's going to become untenable due to the changes for browser security requirements.

In general, there's no momentum to make a change that the agency doesn't "have" to make, and when the browser finally refuses to transmit forms over HTTP then we want to know about it before the change is deployed to all the users.

[james-skemp]

In the days of IE it was common because certain tools would only support certain versions of IE. Intranets and specialized web portals (like ticket systems) for example.

[hacksonx]

My sentiments exactly, especially since we as developers aren't in one team with system admin so they do not seem to understand our struggle.