Battery drains 10 percent overnight in sleep

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: Apple Communities (discussions.apple.com), community Q&A, Apple Support docs

When Battery drains 10 percent overnight in sleep bites you on MacBook Battery, the first instinct is to open a ticket. Most of the time you do not have to. The steps below are the ones Apple Support and Apple Business / Enterprise Support would walk you through on the call.

What battery drains 10 percent overnight in sleep actually involves on MacBook Battery

This task on MacBook Battery is one of the more searched operational topics on AWS in the last 12 months. The procedure below is the path that works in a current AWS account with default IAM and standard VPC config.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing in production.

Spot the symptom

Check Activity Monitor / Jamf inventory Logs for the calling service. Lambda, ECS, EKS, Step Functions, API Gateway, and most managed services write detailed traces to Activity Monitor / Jamf inventory Logs under predictable log group names. Use Activity Monitor / Jamf inventory Logs Insights with fields @timestamp, @message | filter @message like /ERROR/ | sort @timestamp desc | limit 50 to surface the most recent failures.

Reproduce the failure with the Terminal commands (defaults, plistbuddy, killall, sudo, system_profiler) and Apple Configurator 2 / Jamf APIs / MDM commands in --debug mode. The full SigV4 request payload it emits, plus the exact endpoint URL it resolved to, is what Apple Support and Apple Business / Enterprise Support uses to verify policy, region, or parameter issues without you having to share IAM credentials. Save the debug output to a file with ... --debug 2> debug.log and you can search it for the failed aws.request entry.

Run id -un; defaults read MobileMeAccounts; profiles list first. About one in five 'why does this not work' tickets are actually 'I am in the wrong account' or 'my session expired and the SDK is using stale credentials or ADC pointed at the wrong project'. The 5-second sanity check costs nothing and saves real time when the answer is that simple.

Solution-focused remediation path

When the failure happens in production but not in dev, do not just compare the IAM policy. Compare the Org Policy / RCP at the OU level, the permission boundary on the role, and the resource-based policy on the target. One of those is almost always different between accounts. Policy Intelligence recommendations bundles make this comparison routine.

For IAM and STS issues, the timing matters. STS sessions can take up to 60 seconds to propagate after creation. The first call right after assume-role can fail with a permission error even when the policy is correct. Add a small retry with backoff before treating the first failure as definitive.

If the issue points at IAM, do not start by adding * to a policy. Use macOS Console + Jamf Pro logs + Profile Manager check against the failed action to see the minimum scope. Adding * is the fastest way to fail your next Apple Platform Security review, and it usually does not even fix the issue because the explicit deny is often coming from a higher level (Org Policy, RCP, or permission boundary), not a missing allow.

Automate this fix so you do not do it twice

Automate the fix in Terminal with defaults, plistbuddy, and system_profiler

On macOS, the most reliable repair primitives are the built-in Terminal tools. defaults read reveals the current preference state, defaults write changes it, and killall cfprefsd forces the preferences daemon to flush so the new value actually takes effect. /usr/libexec/PlistBuddy handles structured plist edits when defaults is not enough. For hardware and inventory checks, system_profiler with the right datatype is the canonical read; for example SPHardwareDataType, SPNetworkDataType, or SPInstallHistoryDataType.

# Template - replace with your actual key path
defaults read com.apple.macbook 2>/dev/null | head
sudo killall cfprefsd
/usr/libexec/PlistBuddy -c 'Print' ~/Library/Preferences/com.apple.macbook.plist
system_profiler SPHardwareDataType -json | head -40

Automate the fix at scale with a Jamf Pro policy script

When you need to ship the fix to a whole fleet of Macs, the right primitive is a Jamf Pro policy with a script payload, scoped to a smart group of affected devices. Keep the script under 100 lines, exit with an explicit code so Jamf logs the right state, and write a one-line log entry to /var/log/jamf.log so you can grep it later. Trigger on check-in or by Self Service so users can run it on demand.

#!/bin/bash
# Jamf policy script - exits non-zero on failure so Jamf flags the device
set -euo pipefail
LOG=/var/log/jamf-macbook-fix.log
echo "$(date) starting fix on $(hostname)" >> "$LOG"
# fix logic here
defaults write com.apple.macbook HardenedSetting -bool true
killall cfprefsd
echo "$(date) fix applied successfully" >> "$LOG"
exit 0

Build a Self Service item with manual approval for risky fixes

For multi-step fixes that include a destructive action (Reset NVRAM, delete keychain, erase user data), publish the fix as a Self Service item in Jamf Pro or Kandji. The user clicks one button, the script runs, a notification confirms success. Couple it with a Jamf Pro approval workflow if your security model requires a second-person sign-off before any destructive step runs. The audit trail lives in the MDM change log with the requester and approver identity attached.

Pitfalls

The most common pitfall when fixing this on MacBook Battery is treating it as a one-off rather than as a recurring class of incident. The same misconfiguration tends to happen again after a deployment, a role rotation, or a region migration unless the fix is codified. Add a Apple Configuration Profile restriction payload, Organization Policy condition, or Apple Configuration Profile or MDM restriction payload that prevents the same misconfig from being introduced again. Documentation alone does not survive turnover.

Another common trap: confirming the fix on a single resource and assuming the fleet is healthy. Loop your check across every account, region, and IAM principal that could exhibit the same symptom. If you cannot enumerate the affected scope without a script, you do not yet understand the scope.

Full fix path

• Watch for 24 to 48 hours. Activity Monitor + macOS unified logging + Jamf inventory reports can mask issues with cached health for 6 to 12 hours, especially Cloud CDN and Cloud DNS.
• Capture the new state in a runbook so the next person on call does not have to rediscover this. Push it to Confluence or your team wiki, not into Slack.

Safety, rollback, blast radius

• Test in a non-production account if your environment has Resource Manager and Organization Policy or Cloud Resource Manager (organizations, folders, projects). The cost of one sandbox account is cheaper than one rollback meeting.
• Export the existing config before changing it. Most MacBook Battery resources support describe + export to JSON via CLI - capture that to source control before you start.
• Maintenance window discipline: if the change touches DNS, certificate rotation, or anything that emits TLS handshakes, line up a window with stakeholder notification, not a heroic mid-day swap.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• Battery drains 30 percent overnight idle background app refresh audit
• BATTERY_DRAINS_SLEEP on MacBook Battery: what causes it and how to fix
• Battery drains 50 percent after iOS 18 update first 48 hours fix
• Find which app drains battery
• Stop at 80 percent charging option Sonoma+
• Battery drains overnight on watchOS 11