Apple Watches suddenly acting strange

watchOS 10.4 includes new features, improvements and bug fixes, including:

• Tap to Show Full Notification setting now allows you to double-tap to expand the notification
• Using Apple Pay with Confirm with AssistiveTouch will require a passcode for additional security and will not support double-clicking the side button
• Resolves an issue that causes some users to experience false touches on the display
• Fixes an issue that prevents contacts from syncing to Apple Watch for some users

For information on the security content of Apple software updates, please visit this website: Apple security releases - Apple Support

The fact that so many people are suddenly having this issue in the last 5 days or so leads me to believe Apple it's rolling out an update and there's a bug in it.

Very doubtful but never say never

It would have to be via wi-fi so I wonder how secure your network is.

I cannot reproduce it by opening my iphone to unlock the Watch.

Uninstall any VPN or security apps from iphone, those crooks will try anything.

Unpair and re-pair the Watch as a new watch (no backup restore) then ensure the passcode is set to erase after 10 failed attempts.

Ensure wrist detection is on.

And replace the router with one with better security Recommended settings for Wi-Fi routers and access points - Apple Support

Very unlikely, but possible: a device compromise. Unlikely, per available information, as most of us are just not worth targeting. And this would be an unusually overt hack, too. You know your own particular risks best, though. Factory reset (un-pair and re-pair) would be one option.

Unlikely, but possible: problems caused by a protective film or by a protective case, so remove any of that in use here, and then clean the display per this: How to clean your Apple Watch - Apple Support

Far more likely: the display or the digitizer or related hardware has probably failed. “Ghost touches” is another name for this sort of failure. Get the hardware looked at.

Multiple cases of this same error might mean an issue with a charger, or cable, or a power glitch. Or maybe a common environmental exposure of some sort. Odd gunk on the display. The “assistance” of somebody with physical access causing damage. Other lesser possibilities exist, such as exposure to a very strong magnetic field.

But somebody is going to need to look at these.

My brother and I both have Series 9's. I've had mine a few weeks longer. His started doing this today. I did a force restart (hold the Crown and side button for 10 seconds) and that seems to have fixed it, at least for now. Had to wait an hour due to the failed passcodes. But it seems to be back to normal.

just had this happen today. all of a sudden, the apple watch started launching apps, making calls and when took it off my wrist, it started entering the password on and on.

I restarted it by holding the side buttons down for 10 sec. now it's back on my wrist and seems like it's behaving.

I suspect something triggered this - maybe a misunderstood command (i was on a call, speaker on) that confused the **** out of it. It is not a breach because my network is secure, the phone was next to me and nothing could be downloaded onto the phone except through the AppStore and i have not downloaded anything for a while.

it is worrying I must say.

Mine just did the same thing. First started jumping from one screen to another, scrolling and acting like someone operates it remotely. Then whet I tried to restart it it called 911 twice… then locked itself for extended time because it was typing random numbers on the unlock screen. I finally did force-reset. After waiting 15 minutes of lockout, I unlocked it and it seems ok but I lost my trust to Apple Watch.

How many? You and your brother?

My brother and I each have a Series 9 Apple Watch, if that's what you're asking.

So just two plus the author makes 3.

Not so many as you suggested.

I've seen several other accounts of this outside this thread.

I have only seen reports of it happening once after an update and fixed with a forced restart.

You should always restart a watch after an update

Thank you. just doing the update. strange coincidence :)