macOS Tahoe 26.1 and 26.2 are enabling an unknown screentime passcode automatically at setup.

AHappyBeeing wrote:

macOS Tahoe 26.1 and 26.2 are enabling an unknown screentime passcode automatically at setup.

If I try the "forgot" passcode option, I am asked for appleid and password, enter password correctly, and still receive the "# Failed Passcode Attempts" error. Attempted to use the "Forgot Password" option, changed the AppleID password, immediately used the new password and again received the "# Failed Passcode Attempts" error.

I have tried different devices to reset the passcode, but the issue follows devices.

I updated to 26.2 across all devices,

I created a new admin account on the Mac and it again automatically enabled an unknown screen time passcode.

Has anyone else seen this issue and/or found a solution?

Currently, my only work around to a screen time lockout is to create a "Standard User" account on the Mac and not associate it with an AppleID, but that is certainly not ideal.

See if there is anything here—

Set, change, or remove a Screen Time passcode on Mac

Turn off Screen Time on your Mac - Apple Support

Set up Family Sharing on Mac - Apple Support

further—

Call Customer Support (800) MY–APPLE (800–692–7753)

or on line https://getsupport.apple.com/

Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple Support - Apple Support

AHappyBeeing wrote:

None of those options are helpful. I have contacted Apple Support. It is apparently a known problem, but that doesn’t help me with the solution.

If Apple told you it is a known issue, but have no solution, then it appears you will need to wait until Apple provides a solution. IIRC, I believe I saw another post about this issue some time ago on this forum. I don't recall any solution, but you may want to search the Apple Discussion Forum to see for sure....it may have been a couple weeks to a month ago.

Or perhaps erase the computer (Erase All Contents & Settings) & restore from a backup made before this issue began. Theoretically if the system is already on macOS 26.2 and you restore from an older backup, then you should be able to bypass the problem for now.