Touch ID Issue After Sonoma Update 14.1.1

Try doing the same in Safe Mode. Does it work there?

If it works in Safe Mode, then there is a software conflict.

Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

Shortly after posting my last comment here, I found a suggestion to reset SMC (System Management Controller) on my MBP M2 (2023). All articles says MBP M2 does not have SMC or it resets when you restart your MacBook. Not sure if that's true, the steps helped! I can add a finger print and it's working!!! We'll see for how long, but at least it's a start.

Followed these steps:

Shut Down Your MacBook Pro:

• • First, shut down your MacBook Pro completely. Go to the Apple menu and select "Shut Down".

Connect to Power:

• • Make sure your MacBook Pro is connected to power using the AC adapter.

Perform the SMC Reset:

• • Press and hold the Control (left side) + Option (left side) + Shift (right side) keys on your keyboard.
  • While holding these keys, press and hold the power button as well.
  • Keep all four keys pressed down for 10 seconds.
  • Release all keys and the power button at the same time.

Turn on Your MacBook Pro:

• • After releasing the keys, wait a few seconds.
  • Then, press the power button to turn on your MacBook Pro.

Well until somebody discovers away, that’s about all we can offer. You need to take it to an Apple Store Genius Bar or an authorized repair center to have it fixed.

I guess one more troubleshooting step you can take, is to create a new user and see if you can enable touch ID for it. Use a different finger. If you can’t create one in a new user, it is probably a hardware problem.

Had to reset my m2 pro 16 inch MBP in DFU Mode because some Jerk recommended a terminal command that bricked my device - did a clean install to 14.2.1 and now everything is working flawless again - definitely an issue with one of the recent updates

Did you do an SMC reset when you talk to Apple support?

Reset the SMC of your Mac - Apple Support

Brace yourself for worse... I had like this at the beginning, then after sometime it stopped working all together and it's been like this since November or so... I lost hope right now...

I submitted "Feedback" via "Feedback" app on my Mac. Even got a ticket number, funny thing, the ticket is open but "Recent Similar Reports: None", so I don't think they even work on the issue....

I'd ask you all to submit a ticket via Feedback App - I'm hoping that the more people reports issues with "Touch ID after Sonoma Update" (this is my subject for the ticket) via the Feedback App, it will finally get solved.

I'm on Sonoma 14.4.1 - no fix.

Is this fixed in latest version of Sonoma 14.3?

I have a similiar issue that started with 14.2.1 - MBP m2 Pro 16inch.

Touch ID only works sporadically, i even tried to set it up again which hardy succeeded because it wouldn't recognize my finger correctly.

Anyone was able to solve the issue?

The Touch ID fails to recognise my fingerprint during login attempts. Moreover, when attempting to enrol a new fingerprint, I receive the error message: "Failed. Touch ID enrolment was interrupted." I've attempted troubleshooting through both Safe Boot and creating a new user account, but these steps haven't rectified the problem. I've also followed Apple's recommended procedure for cleaning the Touch ID sensor, with no luck.

Actually, I take it back. After restart Touch ID cannot be used and a new one enrolled. However I do have a fingerprint saved now, so it's a step forward. I know it's must be a system issue. I was able to use it once. I expect to see a similar behaviour now - so from time to time it'll allow me to use it.

In common - apparently - with a lot of others, I've updated (my M1 Macair) to Sonoma 14.4.1 (wish I hadn't) and am having trouble with the touch id feature. In particular, it will allow me to unlock occasionally after which it won't play ball. If I create a new fingerprint (no problem there), same again.....works for a while then stops.

I have the same exact issue on my MacBook pro after that update, when you find a solution update us please.