Windows 10 auto-update Aug. 10 AM breaks Chrome entirely
Reported by
gordon.k...@gmail.com,
Aug 10 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586 Example URL: Steps to reproduce the problem: Chrome worked fine on my Dell Windows 10 machine. Microsoft did some auto-update overnight. From that point on, Edge and Safari can access websites but Chrome cannot. I tried to reinstall Chrome, and did, but it still cannot display any web site. It just hangs. What is the expected behavior? If I type in a URL, the web page should display What went wrong? See: steps to reproduce the problem Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? Yes August 10 Does this work in other browsers? Yes Chrome version: 46.0.2486.0 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 Please email me at Gordon.kass@gmail.com with information and hopefully a solution.
,
Aug 11 2016
Do you have a link to the right version for me to download and install?
,
Aug 11 2016
,
Aug 11 2016
Why do you state I am running version M46? (How would you know what version is on my machine?) It appears to me by checking versions that I am running M54-52.0.2743.116. I did a download of that from Google after the problem developed (uninstalled old version, installed new version). But the problem persisted.
,
Aug 12 2016
I think the idea that you're running M46 comes from Edge pretending to be an old version of Chrome. It sounds like renderers aren't starting for some reason. Would you take a look at chrome://crashes and see if any are listed? wfh: could this be related to the renderer crashes you're looking into? Anything you'd like to ask the reporter about?
,
Aug 12 2016
Today (Thursday), Chrome worked fine. Without me doing anything different. I am not sure how that could be. But it works.
,
Aug 12 2016
FWIW I saw a similar report to this on reddit yesterday - updating to the anniversary edition of Windows fixed it for them.
,
Aug 20 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 25 2016
As per comment #7 closing this issue, Please raise a new issue if you come across the similar one on latest chrome version. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by brajkumar@chromium.org
, Aug 11 2016Labels: Needs-Feedback