In last article It has talked about the bug of Disk Utility, which makes that instead of password hint (hint), to appear directly volume password or volumes APFS (Encrypted).
A security issue quite serious, who can expose the password encryption both to third parties and to applications that use Disk Utility. This bug only appears in the scenario where you added a new volume from Disk Utility, using “Add APFS Volumes“.
Apple has solved this problem with the recent release of the macOS High Sierra 10.13 Supplemental Update, but recommends that for data protection, you change the encryption password for the APFS partition whose password appears at password hints/hints.
How to Protect an APFS Encrypted Volume on macOS High Sierra
- Install the latest update: macOS High Sierra 10.13 Supplemental Update. App Store → Update.
- Create a backup copy of the encrypted (encrypted backup) with the data on the APFS partition affected by the Disk Utility bug.
- Open Disk Utility and Select the volume affected APFS, from the bar on the left.
- Right click and “Unmount"Then click"Erase" in order to delete volume APFS affected.
- Enter a name for the new volume in the field dedicated to the name, then il format the APFS.
- Choose the formatting option again and select APFS (Encrypted).
- Choose and enter the password for the encrypted APFS volume, enter it a second time for verification and choose a "hint" to remember the password.
- Click "Erase" and wait until the deletion and encryption process of the partition is completed.
- Click "Done" when the process is complete.
- Bring back the data made in the backup copy from point 2.
As a security measure for your data it is highly recommended that password encryption for the APFS volume must not be identical to a password you use for other accounts. For Mac users. email accounts or social networks. In general, it is recommended to use different passwords for each individual account.









1 thought on “What do we have to do if we were affected by the Disk Utility / APFS (ENCRYPT) bug on Macos High Sierra 10.13"