![drivedx uninstall update drivedx uninstall update](https://www.saashub.com/images/app/context_images/16/4741c4f417c2/passmark-diskcheckup-alternatives-medium.png)
![drivedx uninstall update drivedx uninstall update](https://cdn.techjourney.net/2020/06/uninstall-broken-updates-1024x421.png)
I don't see anything in the DriveDx report although the short self-diagnostic never finished which is unusual. I forgot to suggest to run Disk Utility First Aid on the drive and to run "Repair Permissions" as well (I think the "Repair Permissions" may still be available in macOS 10.11, but if not then run it from Yosemite). By erasing the whole drive (possibly re-partitioning it) you eliminate the file system issues unless it is caused by a hardware issue.
#DRIVEDX UNINSTALL UPDATE INSTALL#
However, if there is a problem with the file system it may be interfering with the 10.11 install process. If Snow Leopard and Yosemite are booting and working fine, then it should be possible to install macOS 10.11 as well without erasing the drive. Now quit Disk Utility and select "Reinstall macOS".
![drivedx uninstall update drivedx uninstall update](https://static.binaryfruit.com/images/drivedx/DriveDxIcon-shadow-128x128@2x.png)
Back in the Partition tab of Disk Utility make sure "MacOS Extended (Journaled)" is selected for the file system and click "Apply". Then use the "Advanced" button to make sure that "GUID Parition" is selected and click "Apply" and/or "OK". Within the "Partition" tab of Disk Utility select "1 Partition" from the drop down list. In Disk Utility select the physical drive on the left pane. How did you acquire and create your macOS installer?ĭid you first erase or partition the whole physical drive before attempting to install macOS? IIRC macOS 10.11 and earlier requires you to use the "Partition" tab in Disk Utility in order to erase the whole physical drive. It will also provide me with the make & model of the drive used. Post the DriveDx report here as it may contain some clues even if the report summary says everything is "ok". I'm not completely sure, but I think these files should have been copied to the laptop's drive by the installer, but the installer doesn't see these files on the laptop's drive. It looks like the installer could not find some files it was expecting to use.