Screen lock & fingerprint unlock are very slow in macOS 14.6

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)

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.

Wow! Excellent find, thank you!

I can confirm this resolved the issue for my users as well. The results were immediate!

Prior to this the only resolution was to wipe and re-configure the device after the upgrade to 14.6.1.

I'm going to deploy a script via Intune to run this for all users. Failing that they could run it manually.

Thanks again!

voostindie wrote:

This fixed it for me:

sudo dscl . deletepl /Users/$USER accountPolicyData history

Thank you.

This exact topic came up yesterday on our company's Slack messaging service. Our Macs have company installed MDM software and lots of profiles and policy data that the company keeps updating.

The fact that it just popped up for more than a few users, including me, when things were working well before, leads me to believe it is something the company did to our Macs.

But the dscl command has cleared it up for me, and at least 3 other users (so far).

Again, Thank You. 🤩

I've some additional details to add to this. Thanks to BigGee42 I was able to confirm what he found... the issue seems to be specific to the Password complexity requirement. In our case, because our company uses a peculiar ruleset, I can narrow it down specific to regex processing... And since our password policy isn't actually being applied by a config profile, this is how I can further confirm that MDM management has nothing to do with this.

Re-iterating point 3 from my past post (PRP_53's suggestion of making a dummy account) you'll find it doesn't seem to impact all accounts on the system... so I'm beginning to wonder if this is something that's being set or being corrupted with user account variables that's impacting regex processing.

Unfortunately none of the users who've brought it to my attention have also been willing to give me the time for me to get my hands on a system to find the resolution for this. When I do, I promise I'll come back here and post what I find.

sudo dscl . deletepl /Users/<accountName> accountPolicyData history

Yes this helped our situation as well, but unfortunately it does not seem like it is a fix that we can deploy on our Production environment, as this command also deletes the password history for the device, therefor users could set the same password as some of their previous passwords, which should not be allowed by the password history requirements.

Just come across this thread and this solution worked for me, I'll agree to that the InTune MDM has impacted this due to the continual policy updates as we role out and mature our management profiles :(

in the etrecheck report had the line : Apple security disabled - Apple security software is disabled. This computer is at risk of malware infection

Why did your Admin turn that off, it scans Trojans to show you downloaded!

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

👍

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.

Wow, thx a lot, finally a solution for long standing issue! It works like a charm, lock and unlock is fast as before.

This worked for me as well! Thank You

sudo dscl command worked for me too, thank you!!!