Screen lock & fingerprint unlock are very slow in macOS 14.6

after installing 14.6.1 problem fixed

how come 14.6.1 fixed it without any changes in our MDM

Not for me

json-hp wrote:

how come 14.6.1 fixed it without any changes in our MDM

How exactly has the user determined that the MDM Service has not been updated or changed should be the question

not for me either, problem still exists after 14.6.1 update. sorry for the duplicate

problem still exists after 14.6.1 update, both at lock and unlock with fingerprint.

Confirmed I still am having the same issue on a MacBook Pro M1 and a MacBook Pro M2 with 14.6.1.

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 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.

I have a MacBook M1 with JAMF / Crowdstrike running 14.6.1 that is VERY slow in unlocking (but almost instantaneous in screen-locking), and a MacBook M2 running 14.6.1 at home (without Managed services) which is instantaneous in both lock and unlock operations.

I would suggest that everybody get their IT/Management tool team to submit tickets to the managed software companies to get them to test properly with 14.6.1. This is obviously some new functionality by Apple that is impacting the 3rd party tools, and the changes will have to be made there (instead of MacOS)

👍

I can provide hard imperial evidence it's not specifically to do with MDM profiles... we removed enrollment from one of our systems, and the problem persisted. Even after Active Directory configurations and Kerberos SSO configurations were pulled.

We cannot simply defer to the "well just nuke it" solution and expect that to solve our problems. People have jobs. People are devoted to the projects they're working on, and when a macOS update comes along, the answer cannot simply be "just give them a new computer / just erase their computer and start over". That is not knowing your user, and that is not a viable option. You've not taken the time to troubleshoot or show ownership of the problem.

So to add something of value to this thread...

1. I know that removing Directory services configurations does not make the problem go away for a user's account
2. I know that removing MDM profiles (fully unenrolling a mac) does not make the problem go away for a user's account.
3. I know that we can sign into another local account on the system, and that account seems to be fine with locking / unlocking.
4. I know that clearing ~/Library/Caches didn't help my particular user.
5. I know that the problem persists for my user on macOS 14.6 and 14.6.1.

So I'm going to theorize that there's some kind of preference or cache sitting somewhere holding onto stale data and it's causing the authentication process to stall.

It seems this issue is not unique and appears to be related to macOS 14.6 rather than the MDM profile itself. Many users have reported similar problems after the update. A possible workaround could involve removing and reapplying the MDM profile, which has worked for some, although the issue might reoccur after a restart.

If the problem persists, another potential fix that some users have reported is updating to macOS 14.6.1, which seems to have resolved the issue for them without altering MDM settings. Additionally, monitoring processes like `opendirectoryd` during the delay might provide more insight, as it seems to spike in CPU usage during these moments.

Hi all,

we experience the same issue. Login takes quite some time until processed.

Not on all machines, but some.

The only common thing is the OS though, so macOS 14.6 or 14.6.1.

I manage macOS devices in Intune, Jamf (on-prem and cloud) and VMware. On all three MDM some machines show the same behavior after the update to 14.6.x... So to me it seems that it is not a MDM issue. Since these three different vendors probably do not make the exact same updates on the exact same time. And, to my knowledge, all MDM use Apples API/APNS to work their MDM magic anyways. So not much they can do without Apple altogether.

To take updates into our own hands is another fun thing with macOS. Apple does not allow postponing updates for longer than 90 days. So no big help there. (There are ways to block updates altogether, of course. But that would probably be worse than just living with these few users and devices that experience this issue currently).

So pretty sure we have to wait for a fix from Apple here

Present the finds to your MDM Service, your IT Department and to Apple as a Bug Report

This ship has sailed a long time ago.