Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
This thread was archived. Please ask a new question if you need help.
Solved Archived

Internet Keyword Search not working

Firefox
cor-el replied
Lisebell
Lisebell

I recently updated Firefox to 8.0.1, and since then I have been having problems with searching from the location bar. When I try to use firefox's 'Internet Keyword Search', it comes up with the message "File not found: Firefox can't find the file at jar:file:///C:/Program Files/Mozilla Firefox/omni.jar!/chrome/en-GB/locale/browser-region/region.properties[insert searched item here]" etc. When I change the keyword.url settings in the about:config from chrome to google, this works until I restart firefox. When I restart, the about:config settings have all changed back to chrome. Help!

I recently updated Firefox to 8.0.1, and since then I have been having problems with searching from the location bar. When I try to use firefox's 'Internet Keyword Search', it comes up with the message "File not found: Firefox can't find the file at jar:file:///C:/Program Files/Mozilla Firefox/omni.jar!/chrome/en-GB/locale/browser-region/region.properties[insert searched item here]" etc. When I change the keyword.url settings in the about:config from chrome to google, this works until I restart firefox. When I restart, the about:config settings have all changed back to chrome. Help!

All Replies (3)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator

Chosen Solution

See:

Start Firefox in Use Troubleshoot Mode in Firefox to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

Lisebell
Lisebell Question owner

Thanks cor-el,

Disabling all my extensions did nothing for the issue, however after I manually deleted the prefs.js files etc, it seems to have fixed the problem :)