Macbook Pro lockout issueSolved

Participant
Discussion
3 days ago Jan 20, 2026

Hi, one of our devices (MacBook Pro) got remotely locked, and now the device shows “Try again in 25177311 minutes” when attempting to enter the PIN.

The Mac likely ran out of battery after the lock command was sent. Has anyone encountered this or found a workaround?

Replies (6)

Marked SolutionPending Review
Participant
3 days ago Jan 20, 2026
Marked SolutionPending Review

Yes, I have seen this before. It’s usually related to the system clock getting reset. If the Mac loses power after a remote lock and there were multiple incorrect PIN attempts, macOS can miscalculate the lockout timer.

Marked SolutionPending Review
Participant
2 days ago Jan 21, 2026
Marked SolutionPending Review

+1 to what @merlynn said.

We had a similar case where the device battery drained completely. Once powered back on, the clock was way off, which caused the retry timer to show a huge number like this.

Marked SolutionPending Review
Participant
2 days ago Jan 21, 2026
Marked SolutionPending Review

Good to know this isn’t an isolated issue. Were you able to fix it without wiping the device?

Marked SolutionPending Review
Participant
1 day ago Jan 22, 2026
Marked SolutionPending Review

Yes. In our case, connecting the Mac to a wired Ethernet connection and rebooting helped. Once it had internet over Ethernet, the system clock synced properly and the PIN prompt became usable again. Wi-Fi alone didn’t work for us while it was locked.

Marked SolutionPending Review
Participant
19 hours ago Jan 22, 2026
Marked SolutionPending Review

If Ethernet doesn’t fix it, the next option is DFU mode. A DFU revive can repair the firmware and usually keeps user data intact. Only go for a full restore if revive fails. Apple has official docs on this, and it worked for us on an M1 MacBook.

Marked SolutionPending Review
Participant
12 hours ago Jan 23, 2026
Marked SolutionPending Review

Appreciate everyone’s input. We will try Ethernet first, then DFU revive if needed, and escalate to Apple if it’s still stuck.

Save