Apple wireless keyboard stopped working after latest Mavericks update

Hello Guest5,

We've got an article that can help get your Keyboard paired to your Mac.

Troubleshooting wireless mouse and keyboard issues

http://support.apple.com/kb/TS3048

Cheers,

Allen

I have this same thing happening with my system (Mid-2007 iMac 24"). I've found that if I press a key on the keyboard and wait 10-20 seconds the keyboard usually reconnects. It's not ideal, but I don't have to restart anymore to get back to work.

Hi there, I have the exact same issue with a Macbook Air (mid-2011). Unfortunately Apple's troubleshooting instructions do not address the issue at all. Waiting for 20 secs also does not always help. I don't have the same issues with my Apple wireless mouse or my Belkin Wireless Numeric Keypad. It looks like the Mavericks update introduced a bug in the Apple wireless keyboard pairing process.

The only solution I found is to log in with the Macbook Air's own keyboard and to pair the Apple wireless keyboard manually by turning it off and then on and Connecting the keyboard manually under the Bluetooth options. Really quite unpractical and bothersome.

Hope this issue will be addressed by Apple shortly. Releasing such buggy upgrades clearly falls short of my expectations.

Yeah, I've now been having the problem consistently, and the only thing I can do to remedy it is to restart. Ignore my comment above, because I can no longer seem to fix it by just waiting.

Just a thought: my wireless keyboard is not the most recent. It dates back to 2009 (model no. A1314). Is your keyboard also an older one or perhaps the same model no.? If so, the bug could be associated with older Apple wireless keyboards (or with that model no. in particular).

It wouldn't be the first time that Apple somehow forgets to test new software releases with older hardware. Call that planned obsolescence if you will :-(

Incorrect. This is a bug introduced by the update. The keyboard keeps trying to connect. It burns out batteries in a couple of weeks. The iMac or whatever cannot see the keybord, and doesn't send the login combination number. A little research makes clear this is abug. Stop sending people to the troubleshooting file, because it won't help until the bug is fixed. Until then, dont use a wirelss keyboard. Let hope it is fixed in the next patch.

Correct. It is a bug and you cannot use wireless keyboard until it is fixed.

i have the same problem the fn key get active when i press any key delleting all characters to the right of the cursor

Mac mini 2009 8GB Ram with Bluetooth keyboard same year. Installed Mavericks 10.9 up to date (11th Dec 2013)

Sorted clearing the PRAM. cmd+opt+r+p while rebooting.

When you hear the booting sound twice, release.

Has anybody found a solution to this yet?

I have the same problem with my Apple Bluetooth keyboard on a 2010 iMac i5.

Keyboard suddenly disconnects. On restart it finds the keyboard then keeps losing the connection.

Have done the PRAM reset/new batteries/Re-paring etc. with no success.

I am experiencing the same problem with Mavericks upgrade. It worked for sometime. After i deleted the bluetooth devices, it no more working for me. And i can't pair it again 😟

Just updated to Mavericks on my Mac Mini 2,26Ghz Intel Core 2 Duo and at the same time the Apple wireless keyboard A1255 stopped working without any light in the LED at all. Have cheked and replaced batteries. Both Mac and keyboard have been running fine for years. A Sandberg mini bluetooth keyboard 630-40 is working.

Since changing my laptop to a more recent rMBP 13" (brand new and thus with a clean Mavericks installation), the issue seems to have (almost) disappeared.

Might it be due to leftovers from previous versions of MacOS? Did some of you attempt a fresh install of Mavericks? Could this address the issue?

I have the same Problem with Bluetooth, i have a mighty mouse after installing mavericks, i have a problem with it.

I can use the mouse for some minutes and then it works not "smoove", it feels like a bad connection.

Have anybody a workaround for me?