Skip to main content
Question

Failed to create activation request - after changing password

  • May 11, 2023
  • 11 replies
  • 858 views

Forum|alt.badge.img+7

Hello everyone,
Earlier today I was helping a colleague at work who couldn't login on a M1 Mac. After Googling a bit I started in recovery mode, opened the Terminal and typed resetpassword. After changing the password and reboot it wanted to activate - after a while we got "Failed to create activation request".

I Googled some more and now I have removed the Mac from my colleagues Apple ID but we still get the same error. Does anyone know what's best to do next? Is it possible to save the data in any way?

11 replies

sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • May 11, 2023

@jonros Does your corporate network perform any SSL inspection on traffic going through your firewall? If so that may be interfering with communication between that Mac and Apple's activation servers. This is the document that lists all of Apple severs that need to be exempted from SSL inspection: https://support.apple.com/en-us/HT210060


Forum|alt.badge.img+7
  • Author
  • Contributor
  • May 11, 2023

@jonros Does your corporate network perform any SSL inspection on traffic going through your firewall? If so that may be interfering with communication between that Mac and Apple's activation servers. This is the document that lists all of Apple severs that need to be exempted from SSL inspection: https://support.apple.com/en-us/HT210060


@sdagley I checked with Mac colleagues who works with network and firewall and they told me everything should be ok. I even connected to my private phone as Wi-Fi but it didn't help.


sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • May 11, 2023

@sdagley I checked with Mac colleagues who works with network and firewall and they told me everything should be ok. I even connected to my private phone as Wi-Fi but it didn't help.


@jonros Might be time to consult AppleCare on that Mac but you might try doing a DFU restore on it first: https://mrmacintosh.com/restore-macos-firmware-on-an-apple-silicon-mac-boot-to-dfu-mode/


Forum|alt.badge.img+7
  • Author
  • Contributor
  • May 11, 2023

@jonros Might be time to consult AppleCare on that Mac but you might try doing a DFU restore on it first: https://mrmacintosh.com/restore-macos-firmware-on-an-apple-silicon-mac-boot-to-dfu-mode/


@sdagley Doesn't that erase all the data?


Forum|alt.badge.img
  • New Contributor
  • May 11, 2023

@sdagley Doesn't that erase all the data?


A DFU restore would erase all data. It would put it back to the shipping out of the box OS.


Forum|alt.badge.img+7
  • Author
  • Contributor
  • May 11, 2023

A DFU restore would erase all data. It would put it back to the shipping out of the box OS.


Something we really want to avoid in this case if possible. Just have to contact Apple support then. Years of work is on the drive.


sdagley
Forum|alt.badge.img+25
  • Jamf Heroes
  • May 11, 2023

Something we really want to avoid in this case if possible. Just have to contact Apple support then. Years of work is on the drive.


@jonros Have you tried booting that Mac into Target Disk Mode: https://support.apple.com/guide/mac-help/transfer-files-mac-computers-target-disk-mode-mchlp1443/mac

That you've reset the password might prevent that from working, and if you have FileVault enabled the odds of being able to recover anything from that drive are low.


Forum|alt.badge.img+11
  • Contributor
  • January 16, 2024

Just had a user with this problem.

The bad part is that the machine is not able to reach target disk mode or any mode to export the data (with our without FV).

In my case this was caused by a bug in Sonoma 14.1.2 on MacBooks when the battery is drained out.

 


Forum|alt.badge.img+11
  • Contributor
  • January 16, 2024

What I suspected, Apple Enterprise Support just confirmed that the issue was caused by Sonoma 14.1.2 on a MacBook when the battery is drained (user does not connect it to power before it gets to 5% or less).

The date and time on the computer changes to 11 months back from today and the recovery is not able to proceed any further.

 

Notify your MacBook users to not upgrade to 14.1.2 and upgrade directly to 14.2.1.

 

Cesar Pineda


Forum|alt.badge.img
  • New Contributor
  • February 19, 2024

Something we really want to avoid in this case if possible. Just have to contact Apple support then. Years of work is on the drive.


Did u ever find a solution to this? I am having the same issue. Many important files I need.


Forum|alt.badge.img+7
  • Author
  • Contributor
  • February 21, 2024

Did u ever find a solution to this? I am having the same issue. Many important files I need.


Only thing was to erase the hard drive and reinstall macOS and loose all the data. Visited Apple Store and they couldn't solve it any other way either. :(