How to Fix FileVault APFS Encryption Stuck at Estimating Time on Mac mini M2: Senior Engineer macOS Guide
⚡ Quick 60-Second Verdict: What This Issue Means
Your Mac mini M2’s FileVault encryption has stalled during the APFS volume conversion phase—typically because the background encryption daemon (`diskmanagementd`) is waiting on a filesystem snapshot, disk I/O contention, or a power-management interrupt. The fix is almost always non-destructive: verify disk integrity, clear blocking snapshots, and force the encryption thread to resume via Terminal in Recovery Mode.
- NEVER force-shutdown (hold power button) while “Estimating Time” is displayed. The APFS conversion writes new metadata structures; a hard power cut corrupts the volume superblock, requiring full erase/restore.
- Do NOT run third-party “disk repair” tools (CleanMyMac, Drive Genius, etc.) on an encrypting volume. They snapshot the filesystem, which blocks the encryption thread permanently.
- Do NOT disable FileVault via System Settings while stuck. The “Turn Off” button queues a decryption that will also hang, doubling the metadata rewrite workload.
- Keep the Mac mini M2 on UPS or stable wall power throughout. Unlike MacBooks, M2 Mac mini has no internal battery—any power flicker during APFS crypto operations = unrecoverable volume corruption.
1. Immediate Safe Actions (Non-Destructive User Triage)
Three straightforward, non-destructive initial triage steps tailored specifically to FileVault APFS Encryption Stuck at Estimating Time on Mac mini M2:
Verify Disk Health & Clear Blocking Snapshots
Open Terminal (Applications → Utilities) and run each command below. This checks APFS container integrity and removes any local Time Machine snapshots that silently block encryption conversion.
# 1. List APFS containers and identify the System volume
diskutil apfs list
# 2. Verify the container (read-only, safe)
diskutil verifyVolume /
# 3. List local snapshots (these block encryption if present)
tmutil listlocalsnapshots /
# 4. Delete ALL local snapshots (safe—only removes local cache, not backups)
tmutil deletelocalsnapshots /
Wait 60 seconds after the last command, then check System Settings → Privacy & Security → FileVault. If “Estimating Time” changes to a progress bar with minutes, the block is cleared. Proceed to Step 02 if still stuck.
Force Encryption Daemon Restart via launchctl
The `diskmanagementd` daemon manages APFS encryption threads. On Apple Silicon, it can enter a wait state that survives sleep/wake. Restart it cleanly:
# Unload and reload the disk management daemon (requires admin)
sudo launchctl kickstart -k system/com.apple.diskmanagementd
# Verify it's running
pgrep -x diskmanagementd
Return to FileVault preference pane. The status should update within 30 seconds. If it shows “Encryption paused: Connect power adapter” despite being on wall power, proceed to Step 03.
Reset SMC Equivalent (Power Management Controller) on Mac mini M2
Apple Silicon Macs don’t have a traditional SMC reset, but the power controller state can be cleared with a specific power-cycle sequence. This clears the “AC power not detected” flag that falsely pauses encryption:
- Shut down completely via Apple Menu → Shut Down. Wait for power LED to turn off.
- Unplug the power cord from the Mac mini (not the wall). Wait 30 full seconds.
- Plug power cord back in. Wait 5 seconds.
- Press and release the power button normally to boot.
After login, open FileVault pane. Encryption should resume with a live time estimate.

2. Software False Alarm Recovery & Reset Protocol
Mac mini M2 Hardware Reset Sequence
If Steps 01–03 fail, the encryption thread is likely blocked by a kernel-level I/O wait. The only reliable clear is a full NVRAM + power-controller reset via Apple Silicon Recovery Mode entry sequence. This does not erase data—it only resets volatile firmware registers and forces `apfsd` to re-evaluate the conversion state on next boot.
- Shut down via Apple Menu → Shut Down. Wait for LED off.
- Press and hold the power button (do not release).
- After ~8 seconds, “Loading startup options” appears. Continue holding.
- After ~15 seconds total, the screen goes black and the Mac mini powers off completely. Release the button.
- Wait 10 seconds. Press power button once to boot normally.
This sequence (unique to M1/M2/M3 Mac mini) clears the Secure Enclave power-state cache and forces a fresh APFS mount with encryption resume. Check FileVault pane after login—conversion should proceed.
3. Advanced Diagnostics & Component Triage
Hardware Telemetry & Sensor Verification
If encryption still stalls, verify the NVMe controller and thermal state aren’t throttling I/O. Mac mini M2’s unified memory architecture means SSD thermal throttling directly stalls `apfsd` crypto threads.
- Open Console.app (Applications → Utilities). In the search bar, type:
subsystem:com.apple.diskmanagement. Look forAPFS encryptionorconversionerrors in the last 30 minutes. - Run thermal check via Terminal:
# Check SSD thermal state (Apple Silicon powermetrics requires sudo) sudo powermetrics --samplers smc -n 1 -i 1000 | grep -i "ssd\|nvme\|thermal" - If “SSD Thermal Throttle” = YES or temperature > 85°C: ensure bottom vents are unobstructed, ambient temp < 30°C. Let idle 15 min, retry FileVault.
- Run Apple Diagnostics: Shut down → Hold Power button → Release at “Loading startup options” → Press ⌘+D. Note any
NDD(NVMe) orPPT(power) reference codes.

4. Diagnostic & Operating Parameter Matrix
| Diagnostic Indicator / Check | Expected Normal State | Fault Alert Threshold | Verified Resolution Target |
|---|---|---|---|
| FileVault Status Text | “Encryption paused: Connect power adapter” OR live progress bar with time estimate | “Estimating Time Remaining…” persisting > 10 minutes on wall power | Progress bar appears with decreasing minute count after Step 01–03 |
| Local Snapshots (tmutil) | Zero snapshots listed for “/” volume | ≥ 1 snapshot present (blocks APFS conversion exclusive lock) | tmutil listlocalsnapshots / returns empty |
| diskmanagementd Process | Running (PID visible via pgrep), CPU 0.5–2% during conversion | Not running, or stuck at 0% CPU for > 5 min | sudo launchctl kickstart restarts it; pgrep returns PID |
| SSD Thermal State (powermetrics) | SSD Temp 35–65°C, Throttle = NO | Temp > 80°C OR Throttle = YES | Temp < 70°C sustained, Throttle = NO after vent clearance |
| APFS Container Verify (diskutil) | “The volume appears to be OK” / exit code 0 | “Invalid key structure” / “Checkpoint mismatch” / exit code 8 | verifyVolume returns OK; repairVolume not needed |
| Apple Diagnostics Result | “No issues found” (ADP000) | NDD001–NDD003 (NVMe), PPT001–PPT003 (Power), VFD001 (VFD) | ADP000 after thermal stabilization; else escalate to hardware service |
5. Frequently Asked Questions (FAQ)
“Estimating Time” has been stuck for 3 hours. Is my data safe?
Yes. While “Estimating Time” displays, FileVault has not yet begun rewriting your data blocks. The volume is still mounted read-write in plaintext. Your files are fully accessible and unmodified. The stall is purely a metadata/daemon coordination issue. Do not force-shutdown—follow Steps 01–04 in order.
Can I just turn FileVault off and back on to “reset” it?
Absolutely not. Clicking “Turn Off FileVault” while stuck queues a full-volume decryption operation that uses the same blocked `diskmanagementd` thread. You’ll end up with two stuck operations (encrypt + decrypt) and a volume that cannot be repaired without erase. Only use the daemon restart (Step 02) and power-cycle (Step 04) methods documented here.
Why does my Mac mini M2 show “Connect power adapter” when it’s a desktop plugged into the wall?
This is a known Apple Silicon firmware bug (present since M1, persists in M2/macOS Sequoia 15.x). The power controller incorrectly reports “battery not connected” to the encryption daemon, which pauses as a safety measure. The 30-second power-cord unplug (Step 03) or full NVRAM reset (Step 04) clears this false flag. It is not a hardware defect.
What if none of these steps work and encryption remains stuck?
If all 5 steps complete and FileVault still shows “Estimating Time” after 30 minutes, the APFS container likely has a checkpoint inconsistency requiring Recovery Mode repair:
- Boot to Recovery (hold power button → Options → Continue).
- Open Terminal from Utilities menu.
- Run:
diskutil apfs list→ note the APFS Container UUID (e.g.,disk3). - Run:
diskutil repairVolume disk3(replace with your container identifier). - Reboot normally. FileVault will resume conversion automatically.
This repairs the APFS superblock without data loss. If repairVolume fails, you have a hardware NVMe issue—contact Apple Support with the Diagnostic reference code from Step 05.
Share your OS version, device model, and exact error code in our independent peer Q&A rooms.
Comments