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

Cannot start Firefox 4.0 using Stardock 2.0

  • 4 replies
  • 2 have this problem
  • 6 views
  • Last reply by Tremola

more options

Error when loading Firefox 4.0 using Stardock 2.0:

Could not initialize the application's security component. The most likely cause is problems with files in your 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 session, you might see incorrect application behaviour when accessing security features.

Error when loading Firefox 4.0 using Stardock 2.0: Could not initialize the application's security component. The most likely cause is problems with files in your 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 session, you might see incorrect application behaviour when accessing security features.

All Replies (4)

more options

See this link: Windowsblinds

more options

The solution for Windowblinds has probably nothing to do with the problem I have, hence is not solve my problem.

more options

Stardock is the name of the company. Their most popular product is Windowsblinds. There isn't a product called Stardock 2.0 as far as I can tell on http://www.stardock.com/products/

But try the troubleshooting steps in this document instead: http://kb.mozillazine.org/Could_not_initialize_the_browser_security_component

more options

You are absolutely correct: it should state Objectdock 2.0 and not Stardock 2.0.

Thanks for the link you attached. I had seen that document myself, checked all of the proposed solution. They either do not apply or just don't work! As I stated, at the folder level, it indicates that one or more files inside the folder is/are Read Only when in fact none of the files has such a restriction.

The document you refer to refers to a file "cert8.db". That specific file is has no read restrictions!

However thanks Xircal for your efforts.

Does anyone else have any suggestions?????