I had that same thing happen to one of our users at work, turns out it was caused by uninstalling Chrome.... re-installing Chrome fixed the issue... I had read other people coming to the same conclusion elsewhere, or I may have never figured that one out... I'm sure there are other causes of that error, but that's what mine was...