In this guide, we will show you a nifty method to fix the issue of Touch ID not working on macOS 13.3. This electronic fingerprint recognition feature from the Cupertino giant comes in handy in many use-case scenarios. Apart from the obvious task of unlocking your Mac, it could also be used to authorize purchases, app install, and authentication for Apple Pay. However, the latest update seems to have broken this functionality.
Numerous users have voiced their concern that Touch ID is not working along the expected lines on macOS 13.3. Whereas some are unable to authorize any purchases, others have said that they are unable to lock/unlock their Mac using it. Regarding the latter, earlier users could easily wake their Mac from sleep just by placing their finger on the sensor, but now that is no longer possible.
First, they have to press any other key to wake up the display and then press the touch ID sensor to unlock it [simply touching it won’t do the job]. If you are also facing any of these issues, then this guide will make you aware of a nifty workaround to rectify this bug. Follow along.
Table of Contents
Fix Touch ID not working on macOS 13.3
As of now the only workaround that is spelling out success for the users involves resetting the SMC on your Mac. So do give it a try using the below-listed steps and then check out the results.
Mac with M1/M2 chipset
Power off your Mac for 30 seconds and then turn it back on. That’s it. The SMC Reset stands complete.
Mac with Intel chipset
- Power off your Mac. Then press and hold the Control + Options + Shift keys together.
- Keep holding all three keys for 7 seconds, then press and hold the Power button as well.
Credits: Apple - Now keep holding all these four keys for another 7 seconds and then release them.
- Finally, press the Power button to turn on the Mac. The SMC reset is now complete.
Credits: AppleUpon resetting the SMC, it should fix the issue of Touch ID not working on macOS 13.3. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workarounds are your best bet.
