Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Chrome not auto updating


  • Please log in to reply

#1
diggeryo

diggeryo

    Member

  • Member
  • PipPipPip
  • 343 posts

I could really use someone's help here.  I've been searching for a while for a solution to my issue, but can't find very many resources about my specific problem.

 

My Google Chrome will not auto update on *any* of my PC's.  Some background info...

 

I use Windows 10 Home 64-bit.  Currently, my Chrome version is 51.0.2704.106 m (64-bit), as I have been manually updating.

 

I noticed this problem start several months ago.  Prior to that time, Chrome would auto update.  Not sure if any of the following have relevance to the issue, but here are some things I noticed:

  • Around the same time the issue started, I moved from 32-bit Chrome to 64-bit Chrome. 
  • I noticed that my Chrome installations reside in the "Program Files (x86)" folder. However, I could have sworn Chrome usually installed itself in Appdata.
  • I am able to manually update (by going to Help/About).  Chrome just will not auto update.
  • I have UAC turned on on all of the PC's with the issue, and when I manually update Chrome in Help/About, I am presented with a UAC dialogue box which I must click to get past before the update will occur.

When I go into Task Scheduler, it does list two items that look to be responsible for updating Chrome, and they show as being "on" and running every so often, but still no auto updating is occurring.

 

I've tried uninstalling Chrome and reinstalling, but the same issue is still occurring.

 

Any help someone could provide would be *very much* appreciated, as I have been able to find very little support elsewhere.  Most auto updating problems I've come across in my search have to do with updates being disabled by the administrator (which impact manual updates as well), but that is not happening to me.  

 

I did come across one web page that seemed to describe my problem (listed as a bug on chromium.org, but the issue was marked as "won't fix."  Here is the link, if it helps:

 

https://bugs.chromiu...l?id=606301#c20

 

Thanks.


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

The 32 bit Chrome used update plugins as seen below:

 

CHR HKLM\...\Chrome\Extension: [pilplloabdedfmialnfchjomjmpjcoej] - hxxps://clients2.google.com/service/update2/crx
CHR HKU\S-1-5-21-857764097-2768608196-515561602-1001\SOFTWARE\Google\Chrome\Extensions\...\Chrome\Extension: [pilplloabdedfmialnfchjomjmpjcoej] - hxxps://clients2.google.com/service/update2/crx
CHR HKLM-x32\...\Chrome\Extension: [kpdmjodecdegfglgaapafjleomjjlpnh] - hxxps://clients2.google.com/service/update2/crx
CHR HKLM-x32\...\Chrome\Extension: [pilplloabdedfmialnfchjomjmpjcoej] - hxxps://clients2.google.com/service/update2/crx

 

 

 
I suspect these were triggered every time Chrome ran.
 
These seem to have disappeared after updating to the 64 bit version.  That would leave only the Tasks to do the update so I suspect that's where your problem lies.
 

Search for

Task Scheduler 

and hit Enter.  This should open up Task Scheduler (after a brief delay)

 

Click on Task Scheduler Library.

 

You should have some (I have 4) GoogleUpdateTask... entries.

 

They should all say Ready  see below:

 

 gu.jpg

 
You can click on each task and then on History (short wait to populate the window) and it will show you when it last ran.  Does it say Task Completed?  When did it last run?
 

  • 0

#3
diggeryo

diggeryo

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 343 posts

Thanks for the reply.

 

On the machine I am currently looking at, I do have two items: GoogleUpdateTaskMachineCore and GoogleUpdateTaskMachineUA.

 

The history tab is listed as "disabled" in Task Scheduler, so I can't see a history of when they ran.  However, it does say "the operation completed successfully" under the "Last Run Result" column and show that they each last ran yesterday or today.

 

I have looked at these items in Task Scheduler since this issue started, and they have always listed as running successfully.

 

So it seems these tasks *are* running successfully, but for some reason, an update isn't being triggered.

 

Any other suggestions?


  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

On mine the second two appear to be the same but they call the program from a different location:

 

 
Task: C:\Windows\Tasks\GoogleUpdateTaskMachineCore.job => C:\Program Files (x86)\Google\Update\GoogleUpdate.exe
Task: C:\Windows\Tasks\GoogleUpdateTaskMachineUA.job => C:\Program Files (x86)\Google\Update\GoogleUpdate.exe
Task: C:\Windows\Tasks\GoogleUpdateTaskUserS-1-5-21-1163206598-1281092726-1077499770-1001Core.job => C:\Users\Ron\AppData\Local\Google\Update\GoogleUpdate.exe

Task: C:\Windows\Tasks\GoogleUpdateTaskUserS-1-5-21-1163206598-1281092726-1077499770-1001UA.job => C:\Users\Ron\AppData\Local\Google\Update\GoogleUpdate.exe

 

 

 

Apparently it has to talk to

https://clients2.google.com/service/update2/crx

I get a 404 error when I paste it in my browser so don't know how to test it.  Could GoogleUpdate.exe be blocked by your firewall?

 

 

There is a section in the registry:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google

 

That has an Update section under which is I assume a list of products (Clients)  that it want to update.  

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\

 

Looks like this in mine:

 

 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{430FD4D0-B729-4F61-AA34-91526481799D}]
"pv"="1.3.30.3"
"name"="Google Update"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{4DC8B4CA-1BDA-483e-B5FA-D3C12E15B62D}]
"name"="Google Chrome binaries"
"oopcrashes"=dword:00000001
"pv"="51.0.2704.106"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}]
"name"="Google Chrome"
"oopcrashes"=dword:00000001
"pv"="51.0.2704.106"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}\Commands]
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E530F96}\Commands\on-os-upgrade]
"CommandLine"="\"C:\\Program Files (x86)\\Google\\Chrome\\Application\\51.0.2704.106\\Installer\\setup.exe\" --on-os-upgrade --multi-install --chrome --system-level --verbose-logging"
"AutoRunOnOSUpgrade"=dword:00000001
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update\Clients\{FDA71E6F-AC4C-4a00-8B70-9958A68906BF}]
"name"="Google Chrome App Launcher"
"oopcrashes"=dword:00000001
"pv"="51.0.2704.106"
 
 
 
Anything in the event logs about Google Update?

  • 0

#5
diggeryo

diggeryo

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 343 posts

My two items in Task Scheduler are calling the location in "Program Files (x86)."

 

GoogleUpdate.exe specifically is not being blocked by my firewall.  However, I guess there's always a possibility that there's a general firewall rule that is blocking it.  However, now that I think of it, if this were the issue, wouldn't it also block my ability to manually update (by going to Help/About)?

 

I do have the same items in the registry as you have.  Except for the "CommandLine" part--in there I have the same thing except any place you have a double slash, I have only one slash.

 

Lastly, about the Event Logs, there is nothing that specifically says "Chrome."  However, I then decided to look at the times that the Google Task Scheduler items ran to see if I noticed anything.  I did not see anything for the last time GoogleUpdateTaskMachineUA ran.  However, I did notice an item in there at the same time as the last GoogleUpdateTaskMachineCore run.

 

It is only an information level log and the source is listed as "gupdate."  There are many of these same items in my Event Viewer, going back to even 2015, before I upgraded to 64-bit Chrome.  They say the following:

 

''*******************************

The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 
If the event originated on another computer, the display information had to be saved with the event.
 
The following information was included with the event: 
 
Service stopped
''***************************

 

I checked the location that the Googleupdate.exe file is supposedly located, and it is there.  So I don't know what to do now.  I've already tried uninstalling and reinstalling Chrome.  

 


  • 0

#6
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

How does your firewall feel about IPv6 traffic?  I was playing with netstat -a while doing a manual update check and apparently Chrome is using a lot of IPV6

 

  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:50550  den03s09-in-x0e:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:50924  den03s10-in-x0e:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:50925  den03s10-in-x0e:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:50944  den03s10-in-x0e:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:50963  den03s09-in-x01:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:51058  in-in-x66:https
ESTABLISHED
  TCP    [2601:282:c101:71f0:515e:6fbb:3eed:d660]:53021  ih-in-xbc:5228
ESTABLISHED

 

 

What is odd is I thought I had turned off IPv6.  Guess not.  
 
I'm thinking when you do a manual update you continue to use Chome.exe as the origin.  Whereas when it autoupdates the origin is googleupdate.exe which might be blocked depending on wjhat kind of firewall you have.

  • 0

#7
diggeryo

diggeryo

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 343 posts

I am using the built-in Windows 10 firewall.  I'm not sure how to see how it handles ipv6 traffic.  Any suggestions?  However, doesn't the built-in Windows firewall filter only *inbound* traffic?  Meaning the outbound update checks for Chrome wouldn't be impacted, no matter the origin?

 

Note that I am behind a router too.  It is a Buffalo router model WZR-HP-AG300H.  I am running firmware DD-WRT v24SP2-MULTI (06/03/12) std - build 19154.  In its settings page, it has the option for "IPV6 Support" set to disabled.  Would you recommend I set it to enabled instead?

 

If I do, would that have a negative impact on anything else with either my Internet connection or the security of it?

 

Also, are you aware of any way to manually check if any changes I make have corrected this problem?  Or do I just have to wait for Google to release another Chrome update and see what happens?


  • 0

#8
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

 Win 10 firewall apparently can block outfgoing traffic:  See:

 

http://www.howtogeek...ndows-firewall/

 

Wouldn't hurt to look.

 

I don't suppose it would hurt anything to enable IPv6 on the router.  Run ipconfig /all from an elevated command prompt and see if you see signs of IPv6 being used in your DNS server setting.

 

 
DNS Servers . . . . . . . . . . . : 2001:558:feed::1
                                     2001:558:feed::2
                                     75.75.75.75

                                     75.75.76.76 

 

 

 

If your ISP doesn't support it then not much will happen.  Your router also has a firewall.  See Page 56 of the user friendly part of the manual on 

http://cdn.cloudfile...erManual_EN.pdf 

Doesn't look like it would block stuff by default but worth checking I guess.

 

No clue how to tell if it is checking for an update if there is no update.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP