Could not initialize the applications security component

From MozillaZine Knowledge Base
Revision as of 10:24, 1 June 2012 by Alice Wyman (talk | contribs) (error message is now "application's", not "browser's" (bug 385458 - fixed in 2007!). and reordered solutions. Will also rename article.)
Jump to navigationJump to search


This article deals with the causes of the message "Could not initialize the application's security component. The most likely cause is problems with files in your Mozilla application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this application session, you might see incorrect behavior when accessing security features.". For information on other messages received when accessing secure sites, see Error loading secure sites.

Corrupted file

The file cert8.db in your profile folder may have become corrupted. Delete this file while the application (Firefox, SeaMonkey, etc) is closed. [1] To do this on Windows machines:

  1. Close the application by choosing File -> Exit.
  2. Open your profile folder in Windows Explorer.
  3. Click on the file named cert8.db.
  4. Press delete.
  5. Restart the application. cert8.db will be recreated when you do so.

Hard drive capacity

Check your hard drive's remaining capacity. To do this on Windows machines:

  1. From the Start menu, click "Computer" ("My Computer" on older Windows versions)
  2. Right click on Local Disk (C: drive)
  3. Choose Properties. A dialog will come up.
  4. Go to the General tab

If it reports less than 1MB free space, you'll need to make more room.

File permissions

Check the file permissions in your profile folder. The file named cert8.db must not be read-only. To do this on Windows machines:

  1. Open your profile folder.
  2. Right click on the file named cert8.db.
  3. Choose Properties. A dialog will come up.
  4. Go to the General tab
  5. Make sure the "Read-only" checkbox is not checked.
  6. Press OK.

Non-Latin characters in username

There seems to be a bug with non-Latin (For example Chinese or Russian) characters in your username. There's no fix yet but a workaround is to make another account with a Latin characters only username.

New profile

Create a new profile. Your current profile might be corrupted due to many reasons, such as changes in your system or lack of hard drive space at one point.