Issue
Sometimes when trying to update or reinstall through ChromeUpdater, it goes (Not Responding)
But without any log files, how do we know what's going on?
I rarely have need for Process Monitor has been invaluable for diagnosing ChormeUpdater issues particuarly in production environments outside the Bestbar-Unipod-Bitberry internet network. There are a few articles in Process Monitor.
Causes and Solutions
Cannot access file path
One cause of ChromeUpdater going Not Responding is it cannot access the source path
Typically this one is noticed immediately as it doesn't even get a single box int he Installed column ticked
You can find the source path File > Config
Trying to access the path \\bb-iis\chromedata\Shared_Apps\ Windows Explorer prompts for credentials
And having found this, checking in Windows Credential Manager, we find they are not there either
Entering the details in Windows Explorer
Make sure Remember my credentials is checked. It seems this is important and it's with this it writes to Windows Credentials.
Then can get to the files
And after some time, ChromeUpdater seems to get access to the credentials and away it goes
Cannot access file path though Windows Explorer can
One cause of ChromeUpdater going Not Responding is it cannot access the source path even though Windows Explorer can
Typically this one is noticed immediately as it doesn't even get a single box int he Installed column ticked
You can find the source path
Trying to access the path \\bb-iis\chromedata\Shared_Apps\ Windows Explorer it works
But checking in Windows Credential Manager, we find they are not there
It's like Windows Explorer is able to cache credentials for it's own purpose, perhaps for some session or till reboot, but they haven't made it to Windows Credentials.
I think happens if you don't check Remember my credentials
Anyway, in Windows Credential Manager, you can add credentials manually
Entering the details in Windows Explorer
And after some time, ChromeUpdater seems to get access to the credentials and away it goes
A file missing
One cause of ChromeUpdater going Not Responding is a file that it is trying to fetch is simply missing
Typically this one is noticed during the update as as some of the boxes in the Installed column are ticked then it just stalls
Fire up Process Monitor. See Open Process Monitor.
Set the filter to capture events for ChromeUpdater. See Filter for a process name.
We can see it's looping on file \\bb-iis\chromedata\Shared_Apps\arview22513234.ocx
Sure enough, the file isn't present
Put the file in place
And after some time, ChromeUpdater seems to get access to the file and away it goes
Comments (0 comments)