Apple Wireless Keyboard Spacebar insensitive

Hi everyone, I'm having problem with my spacebar because the sides are totally not sensitive at all. I just want to know if there should be 'nipples' attached to the sides - just like the one in the middle. This keyboard is unfortunately out of warranty and the insentivity is driving me crazy.
Based on this photo, can anyone check if this isnorm

Digging around I have just found this on Google.   If you are prepared in the final instance to replace your keyboard, this could help you find out what is wrong.
How to fix a broken spacebar on a mac - YouTube
one end of space bar not working - Apple Wireless Keyboard - iFixit

Similar Messages

  • TS3048 Apple wireless keyboard spacebar glitching out. Every time I press the spacebar it causes me to exit the dialog box  or it takes me to another another desktop window! Frustrating. any help appreciated.

    Please read title

    Hello PBnanas,
    I would be concerned too if the spacebar was not responding correctly.  I found an article that can assist with troubleshooting issues with keys not responding correctly. 
    I recommend following the steps under the section titled, "Some keys don't work as expected" in the following article to isolate and troubleshoot the issue you described:
    One or more keys on the keyboard do not respond
    http://support.apple.com/kb/ts1381
    Thank you for posting in the Apple Support Communities.
    Best,
    Sheila M.

  • My apple wireless keyboard is just over a year old, but I find that delete ( backspace ) button no longer functions, has anyone else experienced this problem, do I need to have it looked at by an apple technician ?

    My apple wireless keyboard is just over a year old, but Ifind the delete ( spacebar ) button does not function, does any one know if this is a common fault, do I need to have an apple technician to take a look at it?

    It appears to be out of date so far as the warranty is concerned.  There may have been some minor detritus slipped down the side of the key.  See if you can find a buush with stiff but fine hair.   Perhaps a toothbrush.  Then brush around the key.   It is possible to remove the key if you are very careful and that would make it easier but you have to be very careful.   You are sure there hasn't been any liquid spilt; even the smallest amount can cause a drama..

  • Space/Delete/Caps keys only work with Fn pressed. Apple wireless keyboard.

    A few weeks ago i noticed that certain keys weren't working on my keyboard.
    A row of central keys, delete, function, caps, arrow keys and the space bar. De-coupling the keyboard to attach to my iPad rendered the same results. No use of keys. I gave it a clean but zilch. So I bought a replacement apple wireless keyboard from a friend, not new but un-used.
    It worked PERFECTLY.
    BUT after the weekend, I sit at my desk to discover that while the central row of keys works fine, I have no delete key, no alt key, no down-arrow key, no spacebar, no caps...the capslock light doesn't even turn on.
    I start going crazy. Since then i've:
    I've cleaned the keyboard,
    I've deleted relevant library files,
    I've reset default keyboard function keys,
    I've performed SMC/PRAM resets.
    Nothing.
    My keyboard - now two of my keyboards (and I only have two) are unusable.
    But today I discover that in fact all the keys DO work. But ONLY if I press and hold the fn key in the bottom left hand corner. If I press the fn key the capslock button works, the light even turns on. if I press it down, I can delete things, use the alt key, I can make spaces between texts, I can use my down-arrow.
    As you can imagine, this took a while to write.
    I'm going out of my mind. PLEASE GOD SOMEONE HELP ME...

    Did you ever solve this problem? I am having the same issue. No spacebar, delete, arrows, or tab.
    Had to paste a space to write this email.
    Mavericks on late 2011 MBA

  • Wacom Tablet causes Apple wireless keyboard to stop working.

    My Wacom tablet/pen causes my Apple wireless keyboard to stop working.  While working on a photo in Photoshop using my Apple (usb) mouse to make selections the keyboard works fine.  When I use the Wacom Pen to make selections, not immediately but anywhere from five to ten minutes into it, I hear what sounds like a chirp from my computer (Mac Pro) and my keyboard stops working.  The command, option, control and direction keys still work but not the number and letter keys.  I have to connect a spare Logitech keyboard via USB in order to continue and not loose my work.  After awhile I will hear the chirp again and the Apple keyboard will start working.  This will continue to occur at irregular intervals.  Without the spare keyboard I've had to reboot my computer (loosing all the work on the photo) to get the keyboard working again, but only for it to reoccur.  Any suggestions to fix this would be appreciated.

    The Mac inherently keeps all input methods active, such that you could type alternate keys on alternate keyboards.
    If you have third party add-ons that might change the way Bluetooth works, those would be the primary suspects.
    Be sure all your Drivers are completely up-to-date, and batteries in battery-powered devices are still strong.
    Bluetooth uses the same part of the frequency spectrum (but a different modulation technique) as cheap WiFi Routers, baby monitors, and microwave ovens. if you live in a busy apartment building, there may be very high levels of interference.

  • HT201178 how do you unpair an apple wireless keyboard?

    I have an apple wireless keyboard, but I recently just purchased and apple keyboard with numeric keypad and I am wondering if I need to unpair the apple wireless keyboard from bluetooth or I dont know but, my new keyboard is wired so it should work already, correct?????

    Hello,
    I believe that when you plug in the USB keyboard, that one should control the device.
    However, why not either unpaid or turn the Bluetooth device off?
    Barry

  • How do you get the Apple Wireless Keyboard to accept function keys?

    I use the Apple Wireless Keyboard with my iPad2 and I use the VPN to connect to my work-related software which requires that I use some of the function keys as actual F1, F2, F3,...etc.  When I hit F2, the iPad2 responds with the Screen Brighter action.  How do I get the keyboard input to just be F2?  Thanks!
    Jeff Lehmer

    Thanks. But I tried that and nothing happens.  I've looked though all the System Preferences sections and can't find anything on this.

  • How do I pair my new Mac mini (mid 2011) and white Apple Wireless Keyboard (2003)?

    I just bought a new Mac mini (mid 2011) and can not set it up via my Apple Wireless Keyboard (2003). I'm disheartened but not surprised that my Bluetooth 4.0 Mac isn't backwards-compatible with my Bluetooth 1.0 keyboard. But I can't find any documentation confirming the fact that my non-paired, but tested & perfectly functioning keyboard will not work with current Macs.
    I was however, able to locate a tech support doc (http://support.apple.com/kb/HT4112) that mentions my Apple Wireless Keyboard (2003) is not compatible with iOS devices. (Which is not critical because iOS provides a non-physical keyboard. Aside, it would be lovely were Apple to add a non-physical keyboard to Mac OS X, if only so new desktop owners can continue to set up their Macs in a pinch.)

    I just bought a new mini mac (lion 2011) with a wireless keyboard.  I could not get the mac to recognise the keyboard.  Spent several hours back with the Genius team who replaced keyboard and mac but did not get anywhere.  They gave me a wired keyboard, was able to configure the mac and then it recognised the wireless keyboard.
    Seems this is a problem with the new mac/OS

  • New apple wireless keyboard & iPad 3 pairing question

    Bought a new Apple wireless keyboard this week. Had some trouble pairing with iPad 3. Took me 4-5 attempts but it finally paired successfully after 10-15 minutes. Question for all you gurus...  When the wireless keyboard arrived on Friday, I first paired it with my MacBook Pro. Could that have caused issues when I re-paired the wireless keyboard (today) with my iPad 3. And further, this will sound like a silly question, can the wireless keyboard be paired with two devices? I don't mean simultaneously. Does it screw up any settings to use the key board with separate devices/computers? Wondering -- if I keep my wireless keyboard at my office -- can I go to work with either my MBP or my iPad and simply use this one wireless keyboard? Or should each device have its own dedicated wireless keyboard? That seems redundant but I kind of love this keyboard already and would be willing to buy a second, if need be. Obviously, I don't want to spend extra money if it isn't necessary. Am I going to have to re-pair the keyboard and device each time I switch between the iPad and the MBP? Thanks all. You are always helpful and I appreciate it.

    Thanks for the quick reply Skydiver! So...I really should buy a second wireless keyboard so that I don't have to go through the hassle of re-pairing the keyboard when i switch devices, yes? Yes, I believe I've answered my own question as I now sit here with my MBP attempting to pair it to the keyboard. Oy. Taking forever. I don't mind buying a second -- for $69, it seems to be the most efficient thing to do. Now I just need to figure out a way to designate which wireless keyboard goes with which device. Time to buy a little sticker! Thanks again.

  • Apple wireless keyboard, mouse and trackpad battery management is SO MESSED UP! HELP!

    I have like 2 dozen batteries that I have swapped in the days since 10.8.4. The **** thing just drains in like 4 days. I am using apple wireless keyboard and mouse/trackpad (either at a time) with my macbook pro that is in closed lide clamshell mode less than a feet away from these devices. the batteries are draining like crazy! 3-4 days! they used to work for like weeks! i have heard in another thread that there is some bluetooth driver issue.
    i know many of you would come up with things to check for like other wireless devices, etc. but like I said i have been using this since 2011 and only now since 10.8.4 they have gone crazy!
    whats even more weird is that i dont think the batteries are really draining. its something to do with the battery management hardware/software that fails to see the power inside. when i remove the currently dead battery and put in one that was indicated having 0% charger i get a magically 50+ % sometimes event 80! a reboot and the figure is something else! since this is happening with all the three input devices i think its something to do with macbook pro.
    any fix?
    Neerav

    SOLUTION:
    Put the devices in "Manual paring mode"
    1. Turn device off.
    2. Push and hold in power button until the LED starts flashing on and off.
    3. Try the paring procedure.
    4. It should work.
    I went to the apple store and this is what they did. They got the trackpad paired no problem, but the keyboard would refuse to make connection. At first they blamed windows and didn't want to replace the keyboard because it worked fine under OSX. However I made them try one of their keyboards and it paired fine. So they ended up swapping out my keyboard for one of the newer ones and now it pairs with both windows and OSX with no problem!

  • Blue Screen of Death from Apple Wireless Keyboard in Windows 7

    Hi all,
    Situation: I have Windows 7 Professional 64 bit installed (boot camp) on my late 2008 MBP. Oftentimes, I'm plugged in to an LED Cinema display and work off of the Apple Wireless Keyboard & Magic Mouse. The Boot Camp partition / Drivers were originally installed from a Snow Leopard DVD. My Apple Software update reports that all my Apple Windows Software is up-to-date.
    Problem: Since installing Windows 7 back in May, I've experienced the Blue Screen of Death (BSOD) 5 times. Each time has resulted from a key press on my bluetooth keyboard after it had been sitting idle for some time and presumably gone into power save mode. Any key press causes an instantaneous BSOD. It only occurs when I'm running windows and I'm working off my bluetooth keyboard so it's hard to replicate and likewise hard to troubleshoot and determine if a fix has worked.
    *Error Details:* Here's some information I've extracted from the BSOD dump files.
    IRQLNOT_LESS_OREQUAL
    +The problem seems to be caused by the following file: ntoskrnl.exe+
    +Technical Information:+
    +* STOP: 0x0000000a (0xfffff80003032f00, 0x0000000000000002, 0x0000000000000008,+
    0xfffff80003032f00)
    +* ntoskrnl.exe - Address 0xfffff80002cbf600 base at 0xfffff80002c4f000 DateStamp+
    0x4b88cfeb
    Thanks for the help!
    Paul

    I'm experiencing the same problem with the BSODs while using my Apple wireless keyboard (latest model).
    I'm running Windows 7 x64 and admit that I bypassed the BootCamp software/driver installation wizard after it complained that my model didn't support installation of the x64 drivers. Its a bit of a gray area, as my system is 64-bit capable and many services and applications run in 64-bit mode without my intervention.
    Just curious if Windows 7 x86 users are experiencing these BSODs or is it a coincidence that you all are installing the drivers creatively.

  • Windows 7 Blue Screen of Death from Apple Wireless Keyboard?

    I've installed Windows 7 with Boot Camp 3.0 drivers on my Mac mini, and I suppose overall, I'm enjoying it. However, I'm getting a blue screen that seems almost random. Keyword is almost.
    I've got my Apple Wireless Keyboard and Mighty Mouse paired, and they're both working well, however, I do believe I am getting some blue screens from my wireless keyboard.
    It seems, at random intervals (usually when I haven't touched the keyboard and mouse for awhile) I get an IRQL blue screen and no information about what's exactly causing it. For example, if I'm sitting in the other room listening to music for awhile, and I come back and press the "next" media button on my keyboard, it'll crash and give me the blue screen. However, I've also tried pressing another random button (shift) to "wake" the keyboard if it had fallen asleep, which also results in a blue screen. The blue screens ONLY show up when I give input via the wireless keyboard. Or, if I leave the computer on overnight to download a file or something, the screen will sleep (which it should) then I'll press a button on the keyboard, the screen will stay asleep, and the computer will restart. Which is just a hidden blue screen I'm assuming.
    I've tried reinstalling Windows (Clean/fresh install of course), installing/uninstalling drivers, pairing and re-pairing. I've also removed unnecessary/non-Windows 7 drivers that were installed with Boot Camp.
    Outside of this blue screen, I am quite impressed with Windows 7. I just can't figure out what's going on. Is there any place I can get a description of what's causing this crash? Does anyone know what's happening or know a solution to this?
    Thanks in advance, if you need more details, please ask.

    Experiencing exactly the same symptoms, bugcheck/bluescreen only when touching the Apple wireless keyboard after a period of inactivity.
    I have an 20" iMac, just upgraded Leopard -> Snow Leopard latest minor version and updated to Boot Camp 3.1 hoping they provided a fix, but the driver at fault (keymagic.sys) doesn't look updated and the issue is still there
    Hopefully someone from Apple dev support is reading this, here's all the info I could squeeze from the crash dump:
    =============================================
    * Bugcheck Analysis *
    IRQLNOT_LESS_OREQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff80002e33440, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002e33440, address which referenced memory
    Debugging Details:
    READ_ADDRESS: fffff80002e33440
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!IoIsWdmVersionAvailable+0
    fffff800`02e33440 80f906 cmp cl,6
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: VISTADRIVERFAULT
    BUGCHECK_STR: 0xA
    PROCESS_NAME: System
    TRAP_FRAME: fffff88002f2f0c0 -- (.trap 0xfffff88002f2f0c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88002f2f100 rbx=0000000000000000 rcx=0000000000000006
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e33440 rsp=fffff88002f2f258 rbp=fffff88002f2f2b0
    r8=fffff80002a4f000 r9=0000000000000000 r10=fffffa80027f3010
    r11=fffff88002f2f208 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!IoIsWdmVersionAvailable:
    fffff800`02e33440 80f906 cmp cl,6
    Resetting default scope
    LASTCONTROLTRANSFER: from fffff80002ac0469 to fffff80002ac0f00
    FAILEDINSTRUCTIONADDRESS:
    nt!IoIsWdmVersionAvailable+0
    fffff800`02e33440 80f906 cmp cl,6
    STACK_TEXT:
    fffff880`02f2ef78 fffff800`02ac0469 : 00000000`0000000a fffff800`02e33440 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`02f2ef80 fffff800`02abf0e0 : 00000000`00000000 fffffa80`03375d90 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`02f2f0c0 fffff800`02e33440 : fffff880`04a02e5d fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 : nt!KiPageFault+0x260
    fffff880`02f2f258 fffff880`04a02e5d : fffffa80`02a3add0 fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 : nt!IoIsWdmVersionAvailable
    fffff880`02f2f260 fffffa80`02a3add0 : fffffa80`027e8b40 fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc : KeyMagic+0x2e5d
    fffff880`02f2f268 fffffa80`027e8b40 : fffffa80`02a3add0 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 : 0xfffffa80`02a3add0
    fffff880`02f2f270 fffffa80`02a3add0 : 0000057f`fd5c5228 fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 : 0xfffffa80`027e8b40
    fffff880`02f2f278 0000057f`fd5c5228 : fffff880`04a02dfc fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 : 0xfffffa80`02a3add0
    fffff880`02f2f280 fffff880`04a02dfc : fffff880`00e5a2a7 fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 : 0x57f`fd5c5228
    fffff880`02f2f288 fffff880`00e5a2a7 : fffffa80`02a3add0 00000000`00000000 fffffa80`027fd9d0 00000000`00000010 : KeyMagic+0x2dfc
    fffff880`02f2f290 fffff880`00e30c9b : fffffa80`027fd9d0 fffffa80`027fd9d0 fffffa80`027fd9e0 fffffa80`027fdc01 : Wdf01000!FxRequestBase::CompleteSubmitted+0x1f3
    fffff880`02f2f310 fffff880`00e30dc4 : 00000000`00000002 fffff880`04bbcff7 00000000`00000000 fffff880`04bbcff7 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
    fffff880`02f2f380 fffff800`02aab935 : 0d780da4`0da40dd4 fffff880`02f2f420 0d440d78`0d780da4 fffff880`04bbeb52 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
    fffff880`02f2f3b0 fffff800`02ac3516 : fffffa80`027e8f2b 00000000`00000000 fffffa80`027fdc70 fffffa80`027e8b40 : nt!IopUnloadSafeCompletion+0x55
    fffff880`02f2f3e0 fffff880`04b62323 : fffffa80`027e8b40 00000000`00000000 fffffa80`02655c10 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
    fffff880`02f2f4c0 fffff880`04ba24be : fffff880`02f2f590 fffffa80`027e8b40 00000000`00000000 fffffa80`0294f600 : bthport!BthCompleteRequestEx+0x5b
    fffff880`02f2f4f0 fffff880`04b9c8d4 : 00000000`00000000 00000000`00000001 fffffa80`02a50c40 fffff880`02f2f6e0 : bthport!L2Cap_CompleteReadIrpList+0xc2
    fffff880`02f2f540 fffff880`04b70732 : fffffa80`03349530 fffffa80`0294f5f0 fffff880`00410001 00000005`00000002 : bthport!L2CapInt_ProcessReadBip+0x430
    fffff880`02f2f6d0 fffff880`04b70078 : fffffa80`0267f230 00000000`00000000 fffffa80`029b5402 fffffa80`02670000 : bthport!HCI_ProcessAclReadBip+0x642
    fffff880`02f2f7a0 fffff880`04b988d9 : fffffa80`0267f230 fffffa80`03036702 fffffa80`026c0ab0 00000000`00000000 : bthport!HCI_ProcessAclRead+0x214
    fffff880`02f2f810 fffff880`04b66201 : 00000000`00000000 00000000`00000000 00000000`00000056 fffffa80`026c0ab0 : bthport!HCI_ProcessMpBip+0x61
    fffff880`02f2f880 fffff880`04b4d327 : fffffa80`0294f4f0 fffffa80`026c0ab0 00000000`00000000 fffff800`02ac59fa : bthport!BTHPORT_RecvMpBip+0x41
    fffff880`02f2f8d0 fffff880`04b5399f : 00000000`00000000 fffffa80`00cd3910 fffff880`04b56388 fffffa80`00cda820 : BTHUSB!BthUsb_ReadTransferComplete+0xf7
    fffff880`02f2f930 fffff880`04b53c31 : 00000000`00000003 fffff880`02f2f9f0 fffffa80`00ca2d00 fffffa80`00000012 : BTHUSB!UsbWrapWorkRoutine+0x17b
    fffff880`02f2f9b0 fffff800`02ac3516 : fffffa80`00cd3bdb 00000000`00000000 00000000`00000000 00000000`00000000 : BTHUSB!UsbWrapInterruptReadComplete+0x1dd
    fffff880`02f2fa40 fffff880`044135d9 : fffffa80`01e81050 fffffa80`00cda700 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
    fffff880`02f2fb20 fffff880`04413ab7 : fffffa80`028ef502 fffffa80`00cd3910 00000000`ffffffff fffffa80`01e81ea8 : USBPORT!USBPORTCoreiCompleteDoneTransfer+0xa15
    fffff880`02f2fc00 fffff880`0441164f : fffffa80`01e81ea8 fffffa80`01e811a0 fffffa80`01e82040 00000000`00000000 : USBPORT!USBPORTCoreiIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`02f2fc60 fffff880`04402f89 : fffffa80`01e81050 00000000`00000000 fffffa80`01e81e02 fffffa80`01e81ea8 : USBPORT!USBPORTCore_UsbIocDpcWorker+0xf3
    fffff880`02f2fca0 fffff800`02acc5dc : fffff880`02f07180 fffffa80`01e81ea8 fffffa80`01e81ec0 00000000`00000000 : USBPORT!USBPORTXdpcWorker+0x1d9
    fffff880`02f2fcd0 fffff800`02ac96fa : fffff880`02f07180 fffff880`02f11f40 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
    fffff880`02f2fd80 00000000`00000000 : fffff880`02f30000 fffff880`02f2a000 fffff880`02f2fd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    KeyMagic+2e5d
    fffff880`04a02e5d ?? ???
    SYMBOLSTACKINDEX: 4
    SYMBOL_NAME: KeyMagic+2e5d
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: KeyMagic
    IMAGE_NAME: KeyMagic.sys
    DEBUGFLR_IMAGETIMESTAMP: 49c160ec
    FAILUREBUCKETID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
    BUCKET_ID: X640xA_CODE_AV_BAD_IPKeyMagic+2e5d
    Followup: MachineOwner
    ---------

  • Boot camp side wont recognize apple wireless keyboard

    I have a base 2013 imac 21.5 inch.
    Had windows partition for a couple months now. Suddenly it doesnt reeckognize my apple wireless keyboard. Mac side reckognzes it but windows doesnt.

    After browsing some Windows fora, I went to look at the Log On tab of the Bluetooth Support Service Properties (Services page in the Computer Management utility). The hypothesis was that that service was being denied access to some resource. I ended up just fiddling, but to my amazement it fixed the problem.
    Here's the essence of my fiddling:
    + I tried stopping and restarting the service logging on as a Local System account - no luck.
    + Then I tried with my Administrator account - no luck.
    + So I wanted to restore the original account - "NT Authority\SYSTEM" - but woe unto me, I didn't know the password! (apparently no one does for this super-account.) But if you leave the password fields empty, the service starts - oof!
    And now, all of a sudden, my keyboard has started working.
    So I would suggest that in a similar situation, one should:
    + stop the Bluetooth Support Service,
    + make sure the log-on account is NT Authority\SYSTEM,
    + clear the password fields, and
    + restart the service.
    May the Force be with you.

  • Apple Wireless Keyboard on Mac Mini Core Solo CANNOT be found !

    Hi,
    My Apple Wireless Keyboard (non-aluminum)was working perfectly with my Mac Mini core Solo. I had to change the battery and after that I cannot connect to my Mac Mini.
    I tried:
    1. Update the Bluetooth software (from the downloads from Apple.com).
    2. Remove all the keyboard definitions in the System Preferences, Bluetooth.
    3. When I try to connect by selecting Keyboard in the Bluetooth Assistant, I won't get any device.
    4. When I try to connect to any device in the Bluetooth Assistent, I'll see the only Apple Wireless Keyboard I have, but then pairing failes.
    5. Only by using a USB keyboard I could enter my MacMini.
    Questions:
    a. How all of a sudden this can't work ?
    b. How to I "reset" the keyboard ?
    c. What can I do ?
    Thanks in advance.
    Rokesh

    i am having this exact same problem. Keyboard isnt seen if I select "Keyboard" in the bluetooth setup assistant, but if I select "Any Device" then after a moment "Apple Wireless Keyboard" shows up in the device list but it will refuse to pair, saying it doesnt have any configurable services.
    Any tips or help would be greatly appreciated.

  • HT3917 My apple wireless keyboard is not working after new batteries installed

    My apple wireless keyboard is not working after new batteries installed.

    Do you get a steady green light to say there is a connection.    If not, are the batteries the right way round.   Do you have a monitor to tell the batteries strength. Is there a reading.   Are the batteries good quality ones, Duracell, Energiser or Apple rechargeables.

Maybe you are looking for