

if the program or the computer crashes and you try to run Disk Utility 13 again, the backed up /usr/libexec/diskmanagementd-sierra gets overwritten with the current (now ElCapitan) version, which is probably what happened in my case. But closing the application reverts any changes made and everything should be back to don't think it is very safe as implemented right now, since there doesn't seem to be any version checking. I guess under Sierra you can't access encrypted HDDs while this Disk Utility is running because of the modified diskmanagementd. It still needs a small modification to /usr/libexec but it shouldn't be affecting Sierra at all. I was/am working on a different version that will be working different way if successful. If you want to see the script browse the contents and check the macOS folder. Note that you can't operate both at the same time. This is done to allow both Disk Utilities to co-exist and work. Thats the only modification to system files. When the program exits, the script deletes diskmanagentd (the El Capitan version) and renames diskmanagementd-sierra to diskmanagementd. The script renames diskmanagementd to diskmanagementd-sierra, copies the El Capitan diskmanagementd to /usr/libexec and executes Disk Utility. After you enter the password at the osascript prompt, a script gets executed. The only system file modified(temporarily) is /usr/libexec/diskmanagementd. I panicked, so I booted to ElCapitan (thankfully I kept a backup) and decrypted them there. Please proceed with caution, I would like some feedback from people on errors or bugs that might come you explain how the magic is done ? Are there any systems files replaced ? I think this could be responsible for my encrypted HDs being unable to unlock in Sierra after installing/running the patched DiskUtility. Partitioning a hard drive, erasing hard drive, restoring to hard drive Creating an image, restoring an image, converting an imageĢ. Tested on a fresh install of macOS Sierra, on an actual MacBook Pro (separate machine from the one it was modified on)ġ. Upon launching you will need to provide password to run the scripts that make things spin. your favorite version of Disk Utility now works on macOS Sierra. This is normal behavior!ĭebug menu is available to list all partitions and mount EFI.įor the nostalgic or the crazy ones. Note: When you launch this version two icons will appear on the dock. To enable this options execute in Terminal: sudo spctl -master-disable To run it you need to Allow apps from Anywhere under System Preferences -> Security & Privacy.
