User profile for user: a_cramp
a_cramp Author
User level: Level 1
4 points

macOS 27 Lock screen password authentication fails on MacBook Pro M3

Issue report: macOS 27 Lockscreen password authentication is broken in certain circumstances

Enterprise-managed MacBook Pro 14" M3 with a Lock Screen message policy set


I refer to two different screens here which perform similar functions:

  • Lockscreen - The screen presented after the Mac has entered Sleep mode or is Locked (⌃⌘Q). This screen is responsible for resuming a previously-active login session after authenticating.
  • FileVault Unlock Screen - The screen presented after the Mac has been powered off, restarted, or the user has Logged Out (⇧⌘Q). This screen is responsible for creating a new login session after restarting or signing out.


When my Mac on macOS 27.0 Golden Gate (build 26A428) is at the Lockscreen, password authentication does not resume the existing user session. The user session remains locked, and the unlock prompt remains on-screen. The login prompt does disappear after entering the correct password; but is immediately re-spawned; whereas if I enter an incorrect password, the password field "jiggles" and the text remains, highlighted in the same prompt. I can still unlock fine with TouchID.


I believe having a lock screen message set is relevant, as in a screen recording I took of the login process, there is a split second where the old macOS 26.x Tahoe password entry field is visible with the lock screen message; while the new macOS 27.x Golden Gate password entry field does not display the configured lock screen message.


For anyone using a MacBook Neo, Mac Studio, iMac, or Mac Mini without access to an Apple Magic Keyboard or with TouchID, this particular issue would result in their computer being basically unusable, as a full system reboot would be required if it ever goes to sleep.


Contrast, with the FileVault Unlock Screen, such as after a reboot, I can sign-in just fine with my regular password (but TouchID is not available as the secure enclave is locked).



MacBook Pro (M3, 2023)

Posted on Sep 21, 2026 6:02 PM

Reply
Question marked as Top-ranking reply
User profile for user: Owl-53
Owl-53
User level: Level 10
119,637 points

Posted on Sep 22, 2026 1:51 AM

On macOS 27.0 (build 26A428), on a managed 14-inch MacBook Pro with an M3 processor and an enterprise Lock Screen message configured, entering the correct account password at the Lock Screen does not unlock the existing session. 


The password prompt briefly disappears and then reappears. An incorrect password is rejected normally, while Touch ID successfully unlocks the session. The same account password successfully authenticates at the FileVault/startup screen after a restart.


The Lock Screen message may be relevant because the macOS 26.x password interface briefly appears with the configured message before the macOS 27.x interface appears without it. 


This does not establish that the message is causing the failure. 


IT should first determine whether the organization is deploying the standard macOS Lock Screen message or a PolicyBanner, since these are different mechanisms. (Apple Support)


A useful first test would be to temporarily remove the Lock Screen message configuration and reset  password unlocking. 


If the behaviour changes, that would provide evidence of a relationship between the configuration and the problem. If it does not, the message is less likely to be involved.


IT should also review the Platform SSO Lock Screen authentication policy, including whether the policy requires Touch ID, permits password authentication, or uses web-based authentication.


 macOS 27 allows these authentication settings to be configured separately for FileVault, the Lock Screen, and the login window. (Apple Support)


If permitted by the organization, testing with a temporary local account that does not receive the same enterprise configuration would provide another useful comparison. If password unlocking works with that account but not the managed account, the results could indicate an account-specific or configuration-specific difference. 


If both accounts show the same behaviour, the problem would not appear to be limited to the managed account.


If the problem remains reproducible, the test results, the applicable MDM and Platform SSO configuration, and diagnostic information such as a sysdiagnose should be provided to the organization's IT administrator or Apple Support for further investigation. 


Apple notes that macOS 27 supports remote log collection on supervised devices when required as part of an AppleCare case, which may also be relevant to an enterprise escalation. (Apple Support)


Apple documentation: What's new for enterprise in macOS Golden Gate 27 · WWDC26 identity integration updates · How to set up policy banners in macOS

View in context
3 replies
Question marked as Top-ranking reply
User profile for user: Owl-53
Owl-53
User level: Level 10
119,637 points

Sep 22, 2026 1:51 AM in response to a_cramp

On macOS 27.0 (build 26A428), on a managed 14-inch MacBook Pro with an M3 processor and an enterprise Lock Screen message configured, entering the correct account password at the Lock Screen does not unlock the existing session. 


The password prompt briefly disappears and then reappears. An incorrect password is rejected normally, while Touch ID successfully unlocks the session. The same account password successfully authenticates at the FileVault/startup screen after a restart.


The Lock Screen message may be relevant because the macOS 26.x password interface briefly appears with the configured message before the macOS 27.x interface appears without it. 


This does not establish that the message is causing the failure. 


IT should first determine whether the organization is deploying the standard macOS Lock Screen message or a PolicyBanner, since these are different mechanisms. (Apple Support)


A useful first test would be to temporarily remove the Lock Screen message configuration and reset  password unlocking. 


If the behaviour changes, that would provide evidence of a relationship between the configuration and the problem. If it does not, the message is less likely to be involved.


IT should also review the Platform SSO Lock Screen authentication policy, including whether the policy requires Touch ID, permits password authentication, or uses web-based authentication.


 macOS 27 allows these authentication settings to be configured separately for FileVault, the Lock Screen, and the login window. (Apple Support)


If permitted by the organization, testing with a temporary local account that does not receive the same enterprise configuration would provide another useful comparison. If password unlocking works with that account but not the managed account, the results could indicate an account-specific or configuration-specific difference. 


If both accounts show the same behaviour, the problem would not appear to be limited to the managed account.


If the problem remains reproducible, the test results, the applicable MDM and Platform SSO configuration, and diagnostic information such as a sysdiagnose should be provided to the organization's IT administrator or Apple Support for further investigation. 


Apple notes that macOS 27 supports remote log collection on supervised devices when required as part of an AppleCare case, which may also be relevant to an enterprise escalation. (Apple Support)


Apple documentation: What's new for enterprise in macOS Golden Gate 27 · WWDC26 identity integration updates · How to set up policy banners in macOS

Reply
User profile for user: WheelieNick
WheelieNick
User level: Level 9
69,384 points

Sep 22, 2026 1:38 AM in response to a_cramp

Hi there


Please try this

  1. Open System Settings -> Lock Screen.
  2. Turn off "Show message when locked" or clear the text field completely.
  3. Test the password lock screen again. Removing the legacy string container usually prevents the UI process from crashing.


You also want to report this behavior to Apple. Apple is not actively participating on this user to user support forums, so use this link Product Feedback - Apple


Reply
User profile for user: Jason_KS
Jason_KS
User level: Level 1
8 points

Oct 6, 2026 11:34 AM in response to a_cramp

I am encountering a comparable problem. At the FileVault screen, I can sign in without trouble, but later locks function only with Touch ID. Logins without Touch ID reach the desktop, yet my keybag stays locked.


A manual 


security unlock-keychain


is needed to restore proper passkey operation afterward.


The issue began in 27.0.0 and continues through 27.0.1.

Reply

macOS 27 Lock screen password authentication fails on MacBook Pro M3

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up