Screen lock & fingerprint unlock are very slow in macOS 14.6

Hi, I'm using MBP M1 Pro. After upgrading to macOS Sonoma 14.6, I'm experiencing slowness in following scenarios:


-Locking the screen: either by pressing the power button shortly, or by going to Apple icon and selecting "Lock Screen" - the screen turns into the wallpaper almost immediately, but the date, time and account icon do not come up, sometimes for even 20 seconds. Until they do, touching fingerprint scanner, or typing the password, does not unlock the MacBook.


-Unlocking the screen: Once the date, time, and account name are visible on the screen, I'm able to unlock my MBP either by typing the password or using the fingerprint scanner, but the fingerprint unlock option can take up to 10 seconds (with the loading "circling dots" animation at the bottom of the screen) to unlock it.


I have tried booting in Safe Mode, but my experience with locking & unlocking was similar there.

MacBook Pro 14″, macOS 14.6

Posted on Aug 1, 2024 2:54 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 15, 2024 10:15 PM

Afternoon all,


We've been experiencing the same issue on Intune managed devices running macOS 14.6.1.


I was able to verify that going back to 14.5 resolved the issue. After the device upgraded to 14.6.1 again the issue re-appeared.


I reported it to Microsoft and they asked me to try removing the MDM profiles and see if that resolved it.


Again, I can confirm that unassigning all of the configuration profiles, scripts and apps resolved the issue. The primary Intune management profiles remained since the device is still linked but this is good.


However, I was determined to find the specific cause. The previous comment about the issue not being present when a different user logged in led me to check the configuration profiles that are deployed via the user channel vs. device.


After re-applying all of the configuration profiles and scripts one at a time I was able to track the cause to a single profile in Intune that uses a Custom Configuration profile to set the local device password policy. It uses the com.apple.mobiledevice.passwordpolicy payload type.


Removing this policy by itself resolved the issue after a restart and re-applying it made the issue return.


I can't guarantee it will resolve the issue for all of you since your setup may be vastly different, but it's worth checking. Failing this, removing your user deployed profiles may help you narrow the cause.


The user related profiles can be identified by going to System Settings > Privacy & Security > Profiles.


At the top there should be a section named User (Managed).


I've passed this info and the configuration profile XML file onto Microsoft for review.


Thanks and good luck!

46 replies

Aug 1, 2024 4:08 AM in response to Owl-53

PRP_53 wrote:

How many times has the computer been Restated since the Monday July 29, 2024 Sonoma 14.6 update was released ?

At least 5 times.

Or >>

Restart in Safe Mode. This will perform a Disk Repair, clear cache files and only load Apple Software, extensions and fonts.

The boot up will be slow and can take some time - Normal.

Safe Mode will also eliminate Third Party Software, extensions and drivers from loading.

It will only load the Minimum amount of Core Apple Processes to allow the the computer to function at a reduced Level of Performance 

Does the issue present in this mode ?

Yes, as I wrote earlier, I have tried booting in Safe Mode and experienced the same slowness.

Aug 1, 2024 8:00 AM in response to Creyden

Thank your the Report


Configuration profiles found - This computer may have configuration profiles installed.


Speak your IT Department about this and any other computer Issues





Configuration Profiles:


  com.apple.ManagedClient.preferences



com.google.Chrome


    GloballyScopeHTTPAuthCacheEnabled


    UrlKeyedAnonymizedDataCollectionEnabled


    ImportSearchEngine


    PromptForDownloadLocation


    CloudPrintProxyEnabled


    AlternateErrorPagesEnabled


    AudioSandboxEnabled


    RemoteAccessHostRequireCurtain


    SpellCheckServiceEnabled


    PasswordManagerEnabled


    RemoteAccessHostFirewallTraversal


    SyncTypesListDisabled[0]


    DisableSafeBrowsingProceedAnyway


    PaymentMethodQueryEnabled


    SafeBrowsingProtectionLevel


    RemoteAccessHostAllowRelayedConnection


    ExtensionInstallForcelist[0]


    SyncDisabled


    DownloadRestrictions


    RemoteAccessHostAllowClientPairing


    AllowCrossOriginAuthPrompt


    CommandLineFlagSecurityWarningsEnabled


    AuthSchemes


    ComponentUpdatesEnabled


    ImportHomepage


    ImportSavedPasswords


    MetricsReportingEnabled


    UserFeedbackAllowed


    DefaultInsecureContentSetting


    EnableOnlineRevocationChecks


    SitePerProcess


    DiskCacheSize


    ImportAutofillFormData




  com.apple.notificationsettings


    NotificationSettings[0]/ShowInLockScreen


    NotificationSettings[0]/NotificationsEnabled


    NotificationSettings[0]/BadgesEnabled


    NotificationSettings[0]/ShowInNotificationCenter


    NotificationSettings[0]/CriticalAlertEnabled


    NotificationSettings[0]/SoundsEnabled


    NotificationSettings[0]/BundleIdentifier


    NotificationSettings[0]/AlertType

com.google.Keystone


    updatePolicies/global/UpdateDefault


  com.apple.SoftwareUpdate


    AllowPreReleaseInstallation

Aug 2, 2024 4:12 AM in response to Creyden

Agree or Disagree as one may wish it


Mobile Digital Management Services has Total Control of both the Computer as well as what can or can not be installed on these computers.


That is why the computer Serial Number is registered into the MDM Data Base


Even if one were permitted or allowed to Totally Reformat the computer and then reinstall the OS Fresh.


At any moment in time, the MDM Service can, again, Install their Service onto the computer


Thusly and again taking Total Control of the computer


It is only when the Serial Number has been Removed, by the MDM Administrator, does the user have control of the machine


Aug 2, 2024 4:15 AM in response to michal_s

michal_s wrote:

I would say the real issue is not due to having your MBP managed by MDM profile, but bug in macOS 14.6 ... so many people from different companies started having the same issue right after the upgrade ...

Respectfully


It is the Responsibility of the MDM and Company IT Department to work hand in hand to Test their Control Software ( MDM Services ) Before allowing any updates to be allowed to be installed



Aug 2, 2024 4:36 AM in response to Creyden

Creyden wrote:

All I'm saying is that the issue has been caused by the upgrade and not by some changes introduced by the MDM.

Whose fault it is and who should provide a solution to this issue is a different discussion.

If you can provide hard and imperial evidence to support this notion


By all means, provide this evidence to Apple as a Bug Report


Be aware, Apple may or may not get back to you


They, would probable require a Totally Clean Installation of macOS Sonoma 14.6 without any MDM or Profiles installed on your machine before even considering to look at your supplied data.


Then, they too would have to Test your exact steps on their equipment, to Reliable and Consistently produce this issue


Then and only then, they may consider looking into this matter


 Product Feedback - and make it known to Apple using the Bug Report


Have taken up enough of your valuable time


Good luck with this issue

Aug 9, 2024 11:05 AM in response to Creyden

This is happening to various companies across different MDM platforms. This is NOT the fault of the MDM but rather a change that Apple needs to address. I just want to know that this issue has been made aware to the correct team so that we can apply security updates to our company machines and know that this issue will be addressed.

Aug 9, 2024 7:07 AM in response to Creyden

The only counter argument to the Touch ID not functioning I can present


1 M3 Machine with a Button Touch ID and 1 M2 Desktop with the Apple Touch ID Keyboard


Both machines ran Sonoma 14.5 and upgraded to 14.6 to 14.6.1


Both machines are not part of any MDM Services for anyone


Touch ID one both machines worked in 14.5 to 14.6 and now 14.6.1


The only reasonable conclusion I can reach, is the MDM Service


As MDM Service are normally a Third Party Service


That falls clearly Out-Side the Domain of Apple.


Contact a third-party vendor - Apple Support


" Contact a third-party vendor

The best source of help for a product not made by Apple (a third-party product) is the company or person who made it—its vendor or developer. "

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Screen lock & fingerprint unlock are very slow in macOS 14.6

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