Touch id in Ventura

Just came to say, having same issue here now where fingerprint login or unlock is no longer working. MacBook Pro 16" 2021 (M1) Ventura 13.2. Also when unlocking its very slow and I have a window pop up saying 'you must authenticate to unlock screen' with OK button greyed out and only option is to 'switch user' click my username, and enter password. All very laggy and slow. But once in all seems fine. This is annoying and hopefully gets sorted soon. I've tried the suggestions in the thread to no effect :(

Update: after some erratic and unpredictable behavior, the malfunction of TouchID has stabilized as follows:

1. For logging in after sleep, TouchID consistently is available and works.
2. For use within a User for software, TouchID consistently works (I logged in to this Forum with TouchID)
3. For switching from one User profile to another on my machine, Touch ID is not work, nor does the login screen say that "Your password is required". TouchID just doesn't work, and I must type my password every time. (This was not the case in Monterrey).

From a Cold Boot Up - stop and read the fine print below the slit for the Computer password.

To Verify the Ownership of this computer, it Is Required to Manually type in the Password

Same here, I upgraded my mac to Ventura yesterday and suddenly, the TouchID is not working. I have spoken to the Apple Support guy via Chat, still can't resolve it. This is definitely a bug. Apple please get a hotfix asap!!

Touch ID stopped working after OSX upgrade to Ventura 13.1 (Macbook Air 2020, Intel i7). I deleted and recorded fingers touch again, still did not work.

I see no one can solve it here. Perhaps Apple's developers can solve it?

I'm on 13.2 since upgrading yesterday (Mac Air M1), and Touch ID no longer works for User logins, though it still works fine inside a User for Apps, Apple ID login, etc. I have gone to Touch ID & Password and made sure it was on, but it still doesn't work.

That is correct: from a cold boot or logout of a User, I get a notice requiring the password, and provide it.

After that, I do NOT get a message requiring a password, but the TouchID does not work.

Thanks!

Interesting and sorry your machine is problematic.

To compare, using 2 M1 Computers all running Ventura 13.2 and am typing this reply on yesterday delivery of the M2 MBA with Ventura 13.0 ( yes 13.0 ) for the moment.

The Touch ID on all 3 machines works as designed and Intended

Go Figure

Thanks for the update. I'm also on 13.2.1, but continue to have TouchID working except for switching between User profiles. Since I switch a lot, it's an annoyance, but not intolerable. Hope Apple figures it out, or can at least issue instructions for what settings might be affecting this.

Thank you the input

Using a M1 MBA and also a M2 MBA both on Ventura 13.2.1 with the Builtin Keyboard and can not reproduce this issue

As for the Authors' Original question, which to Who by earlier posting was directed to - it is presently unknown just which computer is under question and to where or not the OEM Touch Enable Keyboard is or is not used .

As for potions of the Population affect with this issue - not doubt the ASC Forums would in swamped with this type of question.

At least, I am not seeing too many of such questions which does not mean they do not exist but not seeing them

Same here. I just bought a MacBook Air M1 two months ago, it came with OS Ventura. The fingerprint sensor and touch ID worked just fine for about 1.5 months but then it somehow becomes not sensitive (if I put my finger on it, as if theres nothing for it to scan). I clean it up several times but the touchpad still doesnt show much improvement on scanning fingerprints, this is saddening

There is an undocumented AFAIK maximum of Five Fingerprints that can be registered at one given time.

I've had 1 and then 2 and then deleted the old one, so back to 1. Still does not work.

I have noticed the exact same problem. After updating to macOS Ventura, I am unable to unlock the screen with fingerprint anymore.

I guess it is a bug in the OS.

I am on 13.1 as well, but it doesn't work. Thanks for the info.