Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For "some reason" Google Chrome no longer is able to connect to any website, eventually failing with:

Error 7 (net::ERR_TIMED_OUT): The operation timed out.

Other browsers (Firefox, IE10) on the same host are unaffected. According to chrome://chrome/history/, my last successful page get was on 6th November.

Re-running the installer doesn't bring anything up.


Wierdly, Chrome does work if I am running Fiddler (and only if I am), even though it is configured to not use a proxy.

share|improve this question

closed as too localized by random Nov 13 '12 at 22:29

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you checked your DNS and/or proxy settings? – ChrisF Nov 12 '12 at 21:44
@ChrisF Other browsers are fine, so I'd trust DNS. There is no proxy configured – Rowland Shaw Nov 12 '12 at 21:46
up vote 0 down vote accepted

Turns out there was a rogue Chrome process, and rebooting (and not just sleeping) resolved the issue.

share|improve this answer
What do you mean by rogue? – Synetech Nov 13 '12 at 22:20
One that showed in task manager, couldn't be killed via task manager, but had no visible windows. – Rowland Shaw Nov 14 '12 at 8:48
It was probably from a plugin, but “couldn’t be killed via Task Manager”‽ You mean End Process didn’t work? If so, then it was probably from something that hooks into the kernel (which a browser shouldn’t be doing), most like the GPU plugin. – Synetech Nov 14 '12 at 16:06
Looks like there was also an issue with Office 2013 causing Windows Installer to have a sulk (which was blocking the reinstall) – Rowland Shaw Nov 26 '12 at 12:30

Not the answer you're looking for? Browse other questions tagged .