Disk Utility wont Start Since 10.11.6

Question

Level 1

54 points

Disk Utility wont Start Since 10.11.6

I recently updated from 10.11.3 to 10.11.6

Now disk utility won't start anymore. When clicking on the icon it jumps a few minutes but won't open at all. The icon stays there and when restarting my MacBook it says "disk utility prevented the system from restarting and I have to close it".

what I already tried:

create a new user

secure system start

smd reset

starting the disk utility from Yosemite

Strange thing: when I inserted a defect memory card it says the card can't be read, I can ignore or mount it. When mounting the disk utility started.

my System is a MacBook Pro, mid 2012, 1 tb ssd, osx 10.11.6

MacBook Pro (13-inch Mid 2012), OS X Mountain Lion (10.8.5)

Posted on Aug 3, 2016 4:29 AM

Reply

Answer 1

tim_135

Community Specialist

Aug 3, 2016 4:46 PM in response to djtwok

Hello djtwok,

Thanks for bringing up your question here in the Apple Support Communities. I'm happy to help you check our disk utility. Thanks for letting me know what you have already tried also. That should help me with some steps, and save you time.

The first thing you want to do is to make a backup. Use this help article from Apple to ensure all your data is safe: Use Time Machine to back up or restore your Mac.

Once your data is safe, please try booting your Mac into safe mode and seeing if you can load disk utility. Try safe mode if the Mac is not successfully started. Once you boot into safe mode, if the issue is not happening, please check the section titled "If the problem does not occur in safe mode".

If you still experience the issues, and you also experienced them in the new user, please reinstall your operating system. This help article will assist you: How to reinstall OS X.

Thanks again and have a great rest of your day.

Reply

Answer 2

Aug 19, 2016 7:30 AM in response to djtwok

This issue is also discussed and resolved here:

Disk utility does not load disks...

zapping PRAM solved it for some. Booting into Safe Mode solved it for me. You shouldn't need to do anything more complicated than that.

Reply