Become The Solution Chicago Logo

Fix: Could Not Load Security & Privacy Preference Pane – Mac OS X

Fix: Could Not Load Security & Privacy Preference Pane – Mac OS X

Did you attempt to open Security & Privacy in Mac OS X System Preferences but get an error that the preference pane could not load?

 

Preferences Error

Could not load Security & Privacy preference pane.

 

Mac system preferences security privacy

 

  1. Review recently installed software. A piece of software you installed may be overriding the Security & Privacy preference pane. For example, Murus application will cause this error to occur happen.
 
  1. Did you convert your disk drive using Mac OS X Disk Utility? Some report converting a Mac OS X volume from HFS+ to CoreStorage. Revert this change and see if it fixes the preference pane.
 
  1. If you cloned a Mac OS X drive, you may have corrupt preference files. Follow these steps below.

            *Show hidden files on your Mac following this guide.

            *Open your Applications folder and delete any of the following files that begin with “.0”

 

  1. Ensure Applications -> System Preferences is not set to 32-bit mode. (Right-Click -> Get Info on System Preferences)
 
Mac os x system preferences 32-bit
 
 
  1. Ensure you are not launching multiple System Preferences apps. Open Activity Monitor (Applications -> Utilities -> Activity Monitor) go to View and select All Processes. Next, sort by name. Check for System Preferences processes. If you see more than one process, click the “i" in top left and select the Open Files and Ports tab to reveal the location. Remove the duplicate System Preferences app by opening the specified path (copy the path and from Finder Go -> Go To Folder…). You may need to quit the process first.
  1. All else, reboot your Mac and run Software Updates from the App Store to ensure you are running the latest combo updates.
 

 

Related Posts

 

Comments

Charles on Monday, 05 September 2022 07:24

I had this problem today and was prepared to follow some of the steps below or the solution proposed here (https://discussions.apple.com/thread/7503615). However, in my case this error message went away after a simple reboot. I was very happy, needless to say.

I had this problem today and was prepared to follow some of the steps below or the solution proposed here (https://discussions.apple.com/thread/7503615). However, in my case this error message went away after a simple reboot. I was very happy, needless to say.
Guest
Sunday, 02 October 2022