{"id":105584,"date":"2022-07-26T11:43:25","date_gmt":"2022-07-26T11:43:25","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=105584"},"modified":"2026-06-24T05:30:52","modified_gmt":"2026-06-24T05:30:52","slug":"fixed-the-disk-macintosh-hd-cant-be-unlocked","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fixed-the-disk-macintosh-hd-cant-be-unlocked\/","title":{"rendered":"How to Fix \u201cThe Disk Macintosh HD Can\u2019t Be Unlocked\u201d Error on Mac?"},"content":{"rendered":"

If you’re here, this is probably how it went down. You update macOS, restart, type in your password and instead of your desktop, up comes a gray box: “The disk ‘Macintosh HD’ can’t be unlocked. A problem was detected with the disk that prevents it from being unlocked.”<\/strong> You click OK. It disappears. Everything seems normal. Then you restart, and the same warning comes back.<\/p>

Before anything else, the part worth knowing is that your Mac is almost certainly fine, and so are your files. The message reads like your startup disk is failing but that is rarely what’s happening. What’s happening instead is that macOS is trying to interact with a spare volume left behind during the update – often a duplicate with a name like Macintosh HD – Data – Data. In most cases the underlying storage device is healthy, and the issue affects how macOS reaches the volume rather than the files themselves.<\/p>

You might also see this worded as “Macintosh HD – Data can’t be unlocked.”<\/strong> And there’s a rarer version where the Mac won’t boot at all, or asks for a password you don’t recognize. That points to a different issue which we’ll cover separately. Before moving on to the solution – identify exactly which version of the issue you’re dealing with.<\/p>

Why This Happens<\/h2>

The “Macintosh HD can’t be unlocked” error means macOS can’t mount or decrypt one of the volumes on your startup disk. Most of the time a macOS update is to blame – it leaves behind an extra APFS Data volume, but FileVault problems, file-system corruption, or an incomplete macOS installation can produce the same message. Here’s how the main causes compare:<\/p>

Cause<\/strong><\/td>Is it common?<\/strong><\/td>Is your data at risk?<\/strong><\/td><\/tr><\/thead>
Leftover or duplicate APFS Data volume from a macOS update<\/td>Yes. The most common cause<\/td>No. Your files stay in the real Data volume<\/td><\/tr>
Interrupted or failed macOS update (system volume damage)<\/td>Sometimes<\/td>No. The Data volume is separate, and reinstalling macOS rewrites only the system<\/td><\/tr>
FileVault problem (forgotten password or lost recovery key)<\/td>Less common<\/td>Only if both the password and the recovery key are lost<\/td><\/tr>
APFS metadata, volume group, or Preboot corruption<\/td>Rare<\/td>Usually low. First Aid or recovery software can often recover the files<\/td><\/tr><\/tbody><\/table><\/figure>

Can You Still Use Your Mac?<\/h2>

The “Macintosh HD can’t be unlocked” error shows up in two very different situations – and the correct fix depends entirely on which one you’re facing. Identify your scenario below before trying anything to determine which step to follow and which one to avoid.<\/p>

Situation 1: Your Mac Works Normally, But the Error Keeps Returning<\/h3>

You can log into and operate your Mac normally. The alert displays almost immediately upon boot-up, goes away once you click “OK” and returns again the very next time you reboot. This happens more than all other cases combined and likely indicates that an older macOS update created a leftover or duplicate volume.<\/p>

Go to Fix 1: <\/strong>Remove the Duplicate Volume<\/p>

Situation 2: Your Mac Won’t Start Up, or asks for A Password You Don’t Have<\/h3>

Your Mac can’t get past the login or startup screen, keeps looping back to it, or requests a FileVault password or recovery key you no longer have. Your data is still on the drive and remains encrypted but getting back in means working through the repair steps in Fix 2 in order, starting with the safest.<\/p>

Go to Fix 2:<\/strong> When Your Mac Won’t Boot<\/p>

Fix 1: Remove the Duplicate Volume<\/h2>

Here’s an easy explanation of the situation. A recent macOS software update created a “Data” Volume for you but it left behind another Volume (empty) called “Data”. This was forgotten by the update process. As soon as you turn on your Mac, it will try to access this extra Volume and since there are no files or data stored here; it will fail each time and show you an error message when you start your Mac. The good news is your actual files\/data have been safe all along in the first “Data” Volume. To fix the problem, you simply need to locate the empty Volume and delete it. The only part of this solution that requires some thought\/attention is ensuring you are deleting the correct Volume (the empty one).<\/p>

We’ll do this from macOS Recovery<\/a>, where nothing is running off your disk and the volumes hold still long enough to tell apart.<\/p>

1. Find the Leftover Volume<\/h3>

First boot into Recovery and open Disk Utility:<\/p>