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.

Dual boot,same apple id wont remain authenticated on both sides

Hi there! Im running a dual boot on my MB pro M4. Running it off 2 volumes on the same ssd, call it OS 1 and OS 2 (os 2 was installed fresh and then loades with time machine backup of OS1),both on Golden Gate. Both are signed in with the same Apple ID.


Issue: every time i switch between them i get hit with a notification that there is an issue with icloud and i need to reauthentificate so every time i sign in on one side i need to sign in again going back on the other side. Its important to sign in with the same id (continuity,handoff,notifications)


Consulted AI and this is what it said,idk of true i find it weird that i cant be logged in both OS like i would be with two user accounts:

When you sign into an Apple ID, Apple creates a cryptographically bound session token that ties your Apple ID accountto your specific Mac's hardware security enclave (Secure Enclave / TPM).

When you install macOS twice on the same physical MacBook:

  1. Both OS installations share the exact same physical hardware identifiers (ECID, Logic Board Serial Number, Secure Enclave keys).
  2. When you boot OS A and sign in, Apple's authentication servers register a fresh hardware-bound session token for that Mac's hardware ID.
  3. When you switch to OS B and sign in, Apple's servers issue a new session token for that same hardware ID, which invalidates/revokes the previous session token generated for OS A.
  4. When you boot back into OS A, its locally saved token is now rejected by Apple's servers as revoked, triggering the prompt: "Re-enter your Apple ID password to keep using iCloud."

It is an intentional, server-side security measure enforced by Apple's authentication servers to prevent token cloning/hijacking across hardware—not a local macOS Keychain corruption bug.

1 reply

To whomever else has this issue i found the fix. The issue was migrating a time machine backup to the second os so if you do this you need a fresh install and user,after that you can log in with your main user and its going to work fine. Avoid doing it with time machine/migration assistant