Issue metadata
Sign in to add a comment
|
Chrome Updates do NOT report "Installation date".on Windows
Reported by
raphaelb...@gmail.com,
Oct 19
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Observe Chrome installation date. (Control Panel) 2. Install newer version. (Help > About Google Chrome) 3. repeat 1. and observe that the installation date has not changed. 4. Note that the date shows the "original install date" from possible many years ago... 5. Shrug your shoulders and resolve to fix this little niggle. What is the expected behavior? Installation date should show "Todays Date". viz. The date that the latest update was installed on THIS computer. NB. The installation date is NOT the "Chrome release date". That could be days or weeks earlier depending on the user and/or update/release process. What went wrong? Installation date remains stubbornly set as the original installation date of Google Chrome; possibly, many years ago. (My examples show "05Apr2013" even though it is now 16Oct18. My original download of Chrome was indeed 05Apr2013... Did this work before? No Chrome version: 70.0.3538.67 Channel: stable OS Version: 10.0 Flash Version: Justification: Most other software shows a revised installation date when an update is installed. That makes sense to me and everybody else in the universe. Way to fix it: Your implementation of this fix is possible because you will always have "Todays Date" available from the users computer. Go Google Installation team. You can do this... Thank you for a sweet browser. Raphael.
,
Oct 19
re: Comment 1 by ido.mon... "I think this is something you should tell Microsoft" Thank you for a fast initial response and a suggested workaround. Sadly you have rather ducked the issue here. Please allocate this problem to the installation guys and they can look at it. To summarise: Google Chrome like many software products issues updates from time to time. Chrome writes the new version number but omits writing a date in the "Installation Date". It is the responsibility of the software vendor to write such data as seems appropriate when making product updates. Me too: I love blaming Microsoft for stuff too but this time you have rather missed the point. I look forward to a more generous consideration of the DATE issue in this case. thx Raphael
,
Oct 19
,
Oct 22
Thanks for filing the issue! Unable to reproduce the issue on reported chrome version 70.0.3538.67 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Checked the chrome installed date in control panel. Observed today's date. @Reporter: Could you please let us know if this is seen on other machines too. Any further inputs from your end may be helpful.
,
Oct 22
re: Comment 4 by vamshi.kommuri Thanks for the test. From your test description I cannot tell whether you had a previous version installed BEFORE you did the update. I cannot tell whether you did a Chrome update. How to do the test: You should have a previous version installed and observe the install date. Then - A DAY LATER - you should allow the update as in the original report. You will observe that the install date has not moved to "today". This is the bug. I hope that helps. What other machines: I have observed this effect on Win 8.1 and also Win 10 machines. I suspect the problem is in the Chrome Update stuff. Thx Raphael
,
Oct 22
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 22
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ido.mon...@gmail.com
, Oct 19