New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 712142 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Google Chrome Auto Update Off don't work on Windows 7 Machine

Reported by contacts...@gmail.com, Apr 17 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Make the Registery changes suggested in many articles, it works on most windows OS except windows 7
2. 
3. 

What is the expected behavior?
After making the registry changes google chrome auto update should be disabled.

What went wrong?
Google Chrome got Updated even after making registry  changes with and without ADM template

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 6.1
Flash Version: 

Please provide proper steps to disable google chrome auto update for all OS and particularly for windows 7.

Also can google chrome auto update disabled using registry directly or we need ADM template always
 
it would be good if i can get steps to turn off google chrome update only by registry tweaks and not using UI interface.

Please provide information 
Cc: susanjuniab@chromium.org
Labels: Needs-Milestone Needs-Feedback
contactsalot@ Thanks for the issue.

Tried this issue on Windows 7 using the latest Canary 63.0.3233.0 and latest Stable 61.0.3163.100.
Could you please provide us the Registry Path where the changes have to be made and please explain what changes have to be made to test this issue.

Request you to provide us the screen cast for better understanding of the issue.

Thanks..
Components: Internals>Installer
Status: WontFix (was: Unconfirmed)
As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end.

Thanks!

Sign in to add a comment