Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

MacBook Pro M3 Pro macOS update failure (Error 1259/7723) after DFU restore

Subject: Persistent macOS Update Failure – Error 1259 / 7723 After Factory Reset and DFU Restore

Dear Apple Support Team,

I am experiencing a persistent macOS update issue on my MacBook Pro M3 Pro (Mac15,6). The problem started immediately after using the built-in Erase All Content and Settings feature.

Since then, I have been unable to install macOS updates normally.

Device Information:

  • Model: MacBook Pro (Mac15,6)
  • Chip: Apple M3 Pro
  • RAM: 18 GB
  • Current macOS: Tahoe 26.5 (Build 25F71)
  • Firmware Version: 18000.120.36
  • SIP: Enabled
  • Secure Boot: Full Security

How the problem started:

Initially, my MacBook was functioning normally. After performing a factory reset through System Settings → Erase All Content and Settings, macOS updates stopped working.

I attempted to reinstall macOS through Recovery Mode. The first reinstall succeeded, but software updates continued to fail. During subsequent attempts, even Recovery Mode failed to complete the installation.

I then connected my MacBook to another Mac (Mac mini) and performed a complete DFU Restore. The restoration succeeded, installing the latest available macOS version.

However, immediately after the DFU Restore, on a completely clean system with no third-party applications installed, macOS updates still failed with the same error.

Exact error messages:


Failed to personalize the software update.
Please try again.

MobileSoftwareUpdateErrorDomain Code=1259
failed to copy firmware identity

MobileSoftwareUpdateErrorDomain Code=2
could not obtain device identity information through SFR installer

SUMacControllerError Code=7723
PreflightPersonalizeFailed

System logs show that PreflightWakeup and PreflightPrerequisite complete successfully, but the installation fails during PreflightPersonalize.

Troubleshooting already performed:

  • Reinstalled macOS through Recovery Mode.
  • Performed a complete DFU Restore using a Mac mini.
  • Configured the MacBook as a new device without restoring backups.
  • Tested updates immediately after DFU Restore.
  • Attempted multiple macOS versions and full installers.
  • Tested different Wi-Fi networks, mobile internet, and VPN configurations.
  • Verified Apple server connectivity.
  • Checked APFS volumes, NVRAM, Secure Boot, and SIP.
  • Ran Apple Diagnostics, including Logic Board and Thunderbolt tests.

None of these steps resolved the issue. Apple Diagnostics did not detect hardware failures.

Additional findings:

System logs contain the following messages:


AppleTypeCRetimer::onTimer:
status = 0xe00002e9

Sandbox: softwareupdated deny(1)
nvram-get usbc,version,rid0

However, the USB-C controllers are detected by macOS, and the relevant NVRAM variables are readable through Terminal. I cannot confirm whether these messages are related to the update failure.

Request:

Since the problem persists even after a full DFU Restore on a clean system, I would like to request escalation to Apple's engineering team.

Please investigate why macOS cannot obtain the device firmware identity through SFR and whether this is related to firmware personalization, a software defect, or an underlying hardware issue.

My goal is to restore normal macOS update functionality without having to perform a DFU Restore every time a new update becomes available.

I can provide detailed system logs and a sysdiagnose report if needed.

Thank you for your assistance.

Best regards.

4 replies

Hi,

The combination of Error 7723 (SUMacControllerErrorPreflightPersonalizeFailed) and Error 1259 (MSU_ERR_PERSONALIZATION_FAILURE / "failed to copy firmware identity") points directly to a security personalization failure during the preflight stage of the macOS installation.

This specific combination typically happens when the installer or Apple's activation servers fail to verify and sign the local Mac's hardware identity, leaving the system in a half-restored state.


Actionable Solutions

Step 1: Force a True IPSW "Restore" via Apple Configurator


If you previously used the "Revive" option or a standard Recovery Mode update, it will preserve the orphaned secure enclaves. You must completely wipe the firmware architecture.


  1. Connect your MacBook Pro M3 Pro to a host Mac using a standard USB-C charging cable (do not use a Thunderbolt-only cable) plugged into the correct DFU port.
  2. Open Apple Configurator (or Finder's DFU interface) on the host Mac.
  3. Ensure the Mac is in DFU mode.
  4. Right-click the DFU icon and select Advanced > Restore (do not click Revive).
  5. Alternative: Manually download the exact .ipsw file for your target macOS version from a trusted source, drag-and-drop it onto the DFU icon in Apple Configurator, and select Restore.

Step 2: Clear iSCPreboot Conflict via Terminal (If Restore Fails)


If Apple Configurator still throws Error 7723/1259 during the IPSW push, you must manually destroy the broken container metadata using macOS Recovery:


  1. Boot the M3 Pro into macOS Recovery (Press and hold the Power button during startup until "Loading startup options" appears, then select Options).
  2. Open Terminal from the Utilities menu in the top menu bar.
  3. Run the following command to see your APFS structures:
  4. bash
diskutil apfs list
  1. Note your primary disk identifier (e.g., disk0 or disk3).
  2. Completely wipe the internal flash controller container using:
  3. bash
diskutil eraseDisk %any% iBridge disk0
  1. (Replace disk0 with your actual internal SSD disk identifier if different).
  2. Put the Mac back into DFU mode and run the Apple Configurator Restore once more.

Step 3: Network and Server Isolation


Because personalization relies heavily on real-time hardware signing from Apple's servers:


  • Bypass Firewalls: Ensure the host Mac is connected to a non-enterprise network (avoid strict Wi-Fi, VPNs, or corporate proxies). A clean mobile hotspot connection often resolves 1259 handshake blocks.


Update: Possible root cause identified — PS190 / HDMI controller

Hello everyone!

I wanted to share an update regarding my MacBook Pro M3 Pro (Mac15,6) and the macOS update failures.

After extensive troubleshooting, I believe I have identified the likely cause of the issue.

The problem was not resolved by a complete DFU Restore, reinstalling macOS, checking APFS containers, or trying different internet connections.

After analyzing the macOS update logs, I discovered that the update process consistently fails while attempting to retrieve firmware information from the PS190 controller (pcon0).

The relevant errors are:


PS190Instance pcon0: Querying hardware ID
IIC failed to read address 0x5e6 length 2 (0xe00002e9)
Failed to read CMDIF version

RamrodErrorDomain Code=1016
Preflight QueryInfo failed on PS190

This failure subsequently causes:


MobileSoftwareUpdateErrorDomain Code=1259
failed to copy firmware identity

SUMacControllerError Code=7723
PreflightPersonalizeFailed

I also discovered something important: the built-in HDMI port does not work.

I tested a working monitor and HDMI cable with another computer, and both worked correctly. However, when connected directly to my MacBook Pro, the external display is not detected at all.

This strongly suggests that the macOS update failures and the HDMI issue may be related to the PS190 controller or its communication interface.

Current status: Likely root cause identified, but not yet repaired or fully confirmed.

At this point, I suspect a firmware or hardware communication issue involving the PS190 controller. The next step is to have this component and its related circuitry diagnosed.

Thank you to everyone who provided suggestions and helped me troubleshoot this issue!

<< Failed to personalize the software update.

Please try again. >>


MacOS is not copy-protected in the usual sense:


Apple software downloaded from the Mac App Store, including MacOS, is not copy protected. However, it IS tagged with the Apple-ID of the purchaser when "purchased" (or equivalent — Think of MacOS as purchased on sale for $0.) A valid Apple-ID is required at some point in the process for completing installation of almost all downloads from the Mac App Store.


You cannot update, upgrade, or install new software based on already-installed software UNLESS your Mac supplies the Apple-ID used for the original software.



¿Have you entered a valid Apple-ID yet?

you need a valid Apple-ID to make progress.



Yes, I have tested this both with and without signing in to a valid Apple ID.

Unfortunately, the result is exactly the same.

I also performed a complete DFU Restore using another Mac. The restore completed successfully, but macOS updates continued to fail immediately afterward, even on a completely clean system.

The system logs consistently show:

  • MobileSoftwareUpdateErrorDomain Code 1259 — failed to copy firmware identity
  • SUMacControllerError Code 7723 — PreflightPersonalizeFailed
  • Could not obtain device identity information through SFR installer

The issue started immediately after using Erase All Content and Settings.

Do you have any suggestions for diagnosing the firmware identity or SFR personalization failure?