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

Issue 781623 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Update check failed to start

Reported by heger...@gmail.com, Nov 5 2017

Issue description

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

Steps to reproduce the problem:
1. Have the RED Update arrow
2. Be forced to completely install Chrome
3. Fails to update even after re-installing

What is the expected behavior?
Browser to be up to date

What went wrong?
Does not update to the newest version even after reinstalling (Version checked + the red arrow still there).

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: stable
OS Version: 10.0
Flash Version:
 
92d2f5169385a55a7cea77074fc576ad.png
15.0 KB View Download
Labels: Needs-Milestone

Comment 2 by grt@chromium.org, Nov 6 2017

Labels: Needs-Feedback
That's a basic E_FAIL. Which installer are you using, the one from google.com/chrome?

Could you provide a screenshot of chrome://version?

Thanks.

Comment 3 by grt@chromium.org, Nov 6 2017

Taking another look: "error code 1" means that Chrome doesn't think it's running from a standard install location. Without being in a standard install location, it isn't sure how to ask Google Update to check for an update. The "Executable Path" field in chrome://version will be enlightening.

Comment 4 by heger...@gmail.com, Nov 6 2017

Here you go. And yes, the one from Google.

2017-11-06 14:19 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 6 2017

Cc: grt@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "grt@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
@Reporter: Attachment is seen missing from comment#4. Please paste the contents of chrome://version page here.

Thanks!

Comment 7 by heger...@gmail.com, Nov 7 2017

Google Chrome 60.0.3112.101 (Official Build) (64-bit)
Revision 1f3c0cf4b3083dfbe4da434af1726820cf384ce3-refs/branch-heads/3112@
{#723}
OS Windows
JavaScript V8 6.0.286.54
Flash 27.0.0.183 C:\Users\Hegert\AppData\Local\Google\Chrome\User
Data\PepperFlash\27.0.0.183\pepflashplayer.dll
User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
Command Line "D:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
--no-startup-window /prefetch:5 --flag-switches-begin --flag-switches-end
Executable Path D:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\Hegert\AppData\Local\Google\Chrome\User Data\Profile 1
Variations 98ee9f3e-98ee9f3e
ea8deb27-3f4a17df
241fff6c-4eda1c57
3095aa95-3f4a17df
7c1bc906-f55a7974
47e5d3db-3d47f4f4
d43bf3e5-bd7cd813
ba3f87da-45bda656
5ca89f9-3f4a17df
f3499283-7711d854
9e201a2b-6e3ce1c
5b3ed0a1-3f4a17df
68812885-4d2fac87
5e3a236d-4113a79e
b791c1b8-3f4a17df
9773d3bd-f23d1dea
2e109477-f3b42e62
99144bc3-7c4de113
9e5c75f1-b3e209da
f79cb77b-3d47f4f4
b7786474-d93a0620
27219e67-b2047178
23a898eb-e0e2610f
7aa46da5-669a04e0
64224f74-5087fa4a
56302f8c-2f882e70
de03e059-e65e20f2
f56e0452-f23d1dea
1354da85-f34af386
494d8760-91c810ef
f47ae82a-86f22ee5
3ac60855-486e2a9c
f296190c-e41722ab
4442aae2-75cb33fc
ed1d377-e1cc0f14
75f0f0a0-a5822863
e2b18481-92bb99a9
e7e71889-4ad60575
828a5926-9d7acf42
a88c475d-3d47f4f4
Compiler MSVC 2015 (PGO)

2017-11-07 15:01 GMT+02:00 sc00335… via monorail <
monorail+v2.3058424708@chromium.org>:
Project Member

Comment 8 by sheriffbot@chromium.org, Nov 7 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by grt@chromium.org, Nov 8 2017

I see that you have Chrome in D:\Program Files (x86). How did you accomplish this?

Chrome checks whether or not it is installed in the program files dir by checking the "ProgramFiles(x86)" environment variable and by calling SHGetFolderPath(CSIDL_PROGRAM_FILESX86). If you have not taken steps to be sure that these two strategies return "D:\Program Files (x86)" on your computer, then Chrome will be unable to update itself.

For reference, https://msdn.microsoft.com/library/windows/desktop/dd378457.aspx documents the "ProgramFiles(x86)" environment variable. I don't know of a documented way to change the result of SHGetFolderPath/SHGetKnownFolderPath. There's this: https://support.microsoft.com/en-us/help/933700/microsoft-does-not-support-changing-the-location-of-the-program-files which says not to even try.
I completely reinstalled Chrome meaning everything that comes with it is in
one place, so how does this still happen?

2017-11-08 14:07 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 11 by grt@chromium.org, Nov 8 2017

What do you see if you type "set ProgramFiles(x86)" into a command prompt?
:\Users\Hegert>set ProgramFiles(x86)

ProgramFiles(x86)=C:\Program Files (x86)

Comment 13 by grt@chromium.org, Nov 8 2017

How did you get Chrome installed onto your D:\ drive?
I have 2 drives, how else?

2017-11-08 15:15 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 15 by grt@chromium.org, Nov 8 2017

Out of the box, Windows puts "Program Files" and "Program Files (x86)" on C:\ and does not provide a way to change this. Somehow, you have Chrome on your D:\, so I must guess that you've taken some steps on your computer to make this happen. Can you tell me what you've done?
I have Program Files (x86) on my C as well, it also includes Google =>
Chrome. So I guess I have it in 2 places, but either way, I have completely
reinstalled Chrome, so how's that an issue?

2017-11-08 15:19 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 17 by grt@chromium.org, Nov 8 2017

If you launch Chrome and navigate to chrome://version, does it show an "Executable Path" on C:\ or D:\? If the latter, how are you launching Chrome? Perhaps you have a shortcut pointing to the wrong one.
Executable Path D:\Program Files (x86)\Google\Chrome\Application\chrome.exe

Profile Path C:\Users\Hegert\AppData\Local\Google\Chrome\User Data\Profile 1

2017-11-08 15:30 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 19 by grt@chromium.org, Nov 8 2017

How about if you explicitly launch C:\Program Files (x86)\Google\Chrome\Application\chrome.exe? Does this work? Does chrome://version show the right executable path? Does chrome://help work? If yes to all, I suggest you remove Chrome from your D drive, or at least fix your shortcuts so that they point to the one on your C drive.
So, what I tried was that I launch Chrome from my C and update it. But when
I get the Installation application and reinstall Chrome, it goes back to my
D (Since it is my default disk and C just for specific things + Win).

2017-11-08 15:38 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 21 by grt@chromium.org, Nov 8 2017

How have you made D your default disk?
Everything in my Windows as set so that things save onto my D disk as it is
bigger, that's what I meant by default. Everything automatically saves to
D.

2017-11-08 15:49 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 23 by grt@chromium.org, Nov 8 2017

There is no supported way to tell Chrome's installer to put Chrome on D:\ rather than C:\. There is no supported way to tell Windows that the "Program Files" directory is on D:\ rather than C:\. If you find that running Chrome's installer from https://www.google.com/chrome results in a Chrome install in D:\ rather than C:\, then it is because of some unsupported customization that has been done to your machine. If you don't know what that customization was, I'm not sure what I can do to help you. I would really like to be able to help you have a Chrome install that reliably updates for you, but without further information there's not much I can do.

I'll ask this again since I'm not entirely sure that I was clear before. Please try the following:
1. Launch C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
2. Navigate to chrome://help

Does this indicate that Chrome is up to date?

3. Navigate to chrome://version

Does this show that the Executable path is C:\Program Files (x86)\Google\Chrome\Application\chrome.exe?

If the answers to both of these questions is "Yes", then it seems that you have a properly functioning Chrome on your C: drive. In this case, I suggest you do what you can to remove D:\Program Files (x86)\Google\Chrome and any shortcuts pointing to it so that you use the install on your C: drive from this point forward.

I hope this helps.
So to make it clear and simple:
My Windows is installed on an SSD, that I made to be a disk C.
My HDD is disk D, which is also set to be the default Disk for saving
whatever I am downloading (Did it in the Windows 10 settings).

When I open the Google Chrome Properties on my Desktop (The one that I
installed), then it shows me C (The Windows disk) as part of the path. So,
by seeing that I would guess it is reading correctly from the C disk (Where
the Windows is), however, I still cannot update it properly.

1. By doing that, nothing has changed. The Chrome is NOT up to date =>
https://gyazo.com/8d4946901afe671351adebb4b3f83330
2. Even when I open my Chrome from C disk, the Executable Path is D.

I assume I should delete Chrome folders from both disks and reinstall
Chrome?


2017-11-08 16:01 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 25 by grt@chromium.org, Nov 9 2017

If you type "dir /a C:\" into a cmd prompt, does the directory listing show "Program Files (x86)" as <JUNCTION> or <SYMLINKD>?
It doesnt show any of that.
Just <DIR> everywhere.

2017-11-09 15:36 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 27 by grt@chromium.org, Nov 16 2017

Hi. I just tried a fresh install of Win10 on a machine with two disks. I then went into Settings -> System -> Storage and changed all of the "Save locations" to D:. I then installed Chrome from https://www.google.com/chrome/eula.html?extra=devchannel. Chrome landed in "C:\Program Files (x86)\Google\Chrome Dev".

I have to say I'm thoroughly confused as to how Chrome has ended up on your D: drive.

Assuming that the Chrome on your D: is still version 60.0.3112.101, you could try running this command from an Administrator cmd prompt to uninstall it:

"D:\Program Files (x86)\Google\Chrome\Application\60.0.3112.101\Installer\setup.exe" --uninstall --system-level --verbose-logging

Following that, I would hope that you still have Chrome in C:\Program Files (x86) and that it continues to work. If not, I would hope that installing one more time from https://www.google.com/chrome would repair it.

Comment 28 by heger...@gmail.com, Nov 16 2017

Oh, jesus, it is finally fixed with the Cmd Prmt. Thank you so much. Would
have never expected a support from Google be so helpful and do whatever it
takes to get it done.

Thank you very much!

2017-11-16 14:23 GMT+02:00 g… via monorail <
monorail+v2.304671779@chromium.org>:

Comment 29 by grt@chromium.org, Nov 16 2017

Status: WontFix (was: Unconfirmed)
I'm very glad to hear that this helped. I'm going to close this issue out as WontFix for the time being since it's a mystery as to how Chrome ended up on D:. Please re-open it if you find that Chrome stops updating again.

I'm also glad to have surprised you with a resolution. We actually do care a lot about users' experience with Chrome.

Cheers.

Sign in to add a comment