AppLE /WIRELESS /keyboard /issue

This /is /quite /possibly /the /wackiest /thing /I;'ve /ever /seen. /I /am /not /aware /of /anything /that /specifically /happened /to /my /apple /wireless /keyboard. /As /you /can /see, / /6/a /slash /or /6random /6number /appEARS / /every /time /I /press /the /space /bar. /6 /pRESSping /the /delete /key /turns /6down /the /volume. /pressing /6the /slash /key /is /the /same /as /pRESSING /THE /SPace /6bar

I'd start with a SMC reset. If that doesn't work try reseting Pram.
http://support.apple.com/kb/HT3964
Regards,
Captfred
Edit: Pram reset link:
http://support.apple.com/kb/ht1379

Similar Messages

[ISSUE] Apple Wireless Keyboard on Non-Apple hardware

I am using a laptop and would like to use the apple wirless keybaord model : A1314, the reason I am using Apples keybaords as apposed to others is that others are made of cheap plasic!
Laptop Info:
It has build in bluetooth but I also have a bluetooth usb adapter if that helps.
Its a Lenovo Thinkpad T430.
On windows 8.1.
[ISSUE]
In the settings app under bluetooth I add the divice and type in the code and press enter, It loads for a while and underneath it says driver error.
The keyboard does not work at all!
Please leave seggestions!

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.

My MacBook pro stopped connecting to my apple wireless keyboard a while ago. Since it won't connect to a second one, I suspect it's a computer issue. Software thoughts? Updates I've missed? Thanks

About a year ago, my computer and my keyboard stopped connecting. I attributed it to a failed keyboard. Didn't use it much.
Tried today with a second apple wireless keyboard, and it won't connect via blue tooth, either.
Could this be a software/firmware issue that it well known? Or the bluetooth card on my computer is dead?
Thoughts?

And, I get a message saying that the "device does not have the required services."
Thanks again.

I'm having issues with my apple wireless keyboard and bootcamp 5

I'm having issues with my apple wireless keyboard.
I just bought an Apple Wireless Keyboard for my ThinkPad E430 but the keys are not compatible.
I installed BootCamp 5 and it worked great but whenever I restart, it changes my system's time.

What do you mean by racing around in circles? Have you done any damage to your phone? Like drop it or get it wet?

Apple New Wireless keyboard issue

I purchased an apple wireless keyboard a month or so ago, and all was fine. A few days ago, I must have touched some combination of keys that now have the effect of NOT allowing me to type using the keyboard.
I changed the batteries and checked the bluetooth connection, and all seems fine. The odd part is, some of the keys (the function keys across the top) all work all the time. But NO letter keys work.
Is there a "numberlock" or somesuch key I may have inadvertently hit? Help, please?
Thanks
Mary

Hmmm...Have you gone through these steps?
http://support.apple.com/kb/TS1604
Clint Bradford

TA24778 issues with pairing an Apple wireless keyboard by bluetooth with iPad Mini

Does anyone have any tips about successfully pairing an Ipad Mini with an Apple Wireless keyboard, please? Apart from changing the batteries on the keyboard, I have had a lot of difficulty in doing it successfully.

Which Apple wireless keyboard are you using?
See this Apple doc -> iOS: Apple Wireless Keyboard compatibility
The original Apple Wireless Keyboard, introduced in 2003, is not compatible:
Apple Wireless Keyboard (2003): Features a white case and uses four AA batteries.
If you're using a compatible keyboard, does it pair with your Mac? Try turning it off and then back on and then pairing it again.

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!

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
---------

Apple Wireless Keyboard with Windows 7 on non Apple Hardware

Good Day,
I love the Apple Wireless Keyboard and it's the on I use when using my Thinkpad laptop as a desktop, meaning connected to an external Monitor and with an external keyboard and mouse. The Keyboard I use is an Apple Wireless Keyboard.
On my MBA 13 I use Windows 7 as my OS and the Apple lyouted keyboard works actually quite well with windows: The function keys perform very much like in Mac OSX with the volume, screen brightness, the fn+left or right for "home" or "end" etc.
Not I bought an Apple Wireless Keyboard to use in conjuction with my Thinkpad but all does features are missing. I guess that this has to to that on the MBA 13 the appropriate drivers where installed when the whole Bootcamp Software package was installed.
Since I obviously cant install the whole Bootcamp CD on non Apple Hardware, is there any way to just download somewhere the drivers for Apple KEyboards so the behave the same way as they would on a Mac running Windows?
Or is there any other way I could use my Apple Wireless Keyboard with non Apple Hardware the same way it behaves on my MBA 13 running Windows 7? Can somwhere lolely the Apple Keyboard drivers be downloaded?
I want to thank anyone who is kind enough to help mme with this mather in advance and please leave out comments of the kind that I it's my fault, I should have bought an Apple machine from the beginning. I have my reasons and If anyone can't handle that I kindly ask you to just ignore this post unless it's constructive and helpful contribution
Message was edited by: Apolloss

After 3 frustrating hours of trying every tip on the net, I found the answer: Try this.
"This finally fixed it for me: Device Manager - Open System Devices, you will find a Bluetooth HID Device. Double Click it, open Driver tab and click "Update Driver" Select Browse my Computer, then "Let me Pick". It should now show TWO compatible drivers with exactly the same name. One of them is the Microsoft one, one is the non-working Chinese ****. Install one of them and see if the driver properties changed to the right (Microsoft) driver. If not, try again with the other one. For me, the Microsoft driver was the first one in the list, but this may be different for you. Wow, an annoying and intense hour of trouble shooting finally over..."
Source: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/window s-update-yi-ruan-bluetooth-hid-device-driver/5bfd0c92-1771-e011-8dfc-68b599b31bf 5?page=2&tm=1304484508563
The issue is related to the Chinese version of the driver that the latest windows update applies that stops the keyboard from working.
I'm typing this on the Apple Wireless Keyboard on Windows 7 64 bit on my PC. Finallly!

Unable to pair Apple Wireless Keyboard in OS X 10.5.8

Hello everyone,
This is my first post here so if I mess it up, pls don't dog me too much...
I'm currently running OS X Tiger on a Dual PowerMac G5 2GHz with 3GB of RAM and all is well with the world. However, in an attempt to upgrade and become familar (more so) with OS X10.5 I've found that I am unable to pair with my wireless keyboard. I'm running 10.5 on a seperate drive. It sees the dongle, just won't pair with it. The Bluetooth dongle I'm using works fine in OS X 10.4.11, has for years. Any clues, is there something I'm missing?
I've read about Bluetooth issues with Leopard so I thought I would see if i could find an answer here. The keyboard is the original Apple wireless keyboard that came out a few years ago, Model M9270LL/A.
Hardware Overview:
Machine Name:    Power Mac G5
Machine Model:    PowerMac7,3
CPU Type:    PowerPC G5 (2.2)
Number Of CPUs:    2
CPU Speed:    2 GHz
L2 Cache (per CPU):    512 KB
Memory:    3 GB
Bus Speed:    1 GHz
Boot ROM Version:    5.1.8f7
Apple Bluetooth Software Version:    1.9.5f4
Hardware Settings:
PowerMac G5:
Address:    00-02-72-08-1e-0c
Manufacturer:    Broadcom
Firmware Version:    3.16389 (3.17166)
Bluetooth Power:    On
Discoverable:    Yes
HCI Version:    3 ($3)
HCI Revision:    16389 ($4005)
LMP Version:    3 ($3)
LMP Subversion:    17166 ($430e)
Device Type (Major):    Computer
Device Type (Complete):    Desktop Computer
Composite Class Of Device:    1057028 ($102104)
Device Class (Major):    1 ($1)
Device Class (Minor):    1 ($1)
Service Class:    129 ($81)
Requires Authentication:    No
Thanks for any help you folks might wish to provide me in advance.
Message was edited by: Onatopa

I don't think you're following me very well Mr Williams. I appreciate your attempt to assist and hopefully I won't come across as an **** here but, you're not helping. I will agree you, it seems to be a software issue...and it's called Leopard!
Let me explain something. I have not migrated this system, as per se, and for obvious reasons. The system has 2 HDD's. One has 10.4.11 on it and the other HDD has 10.5.8 installed. I can go from one to the other and it's the way I will continue to work until this problem has been resoved, if ever. I can NOT be productive without the Mac running, regardless of which OS. I'm attempting this because I have apps that must have Leopard, so I'm trying to make it work.
Just to be clear, I gave-up running OS X 10.3 several years ago but did not do so without kicking and screaming the entire way. Now, I'm comfortable with Tiger and I'm very glad I upgraded, as it's a much more stable OS but at this rate I'm about ready to give-up. I don't need Leopard and I don't want it, nor do I like the look and feel of it, I just wanted to try and attempt to upgrade and see if I could run some newer apps that won't run on Tiger. I will probably NEVER upgrade to an Intel Mac, even if I could afford to do so. And I will NEVER run Micro$oft Windoze on a Macintosh...period - EVER! That to me is just sacrilege...so just call me a purist, I care not. If I want to run that OS I'll do it on a PeeCee.
Back to the dicussion.
I'm typing this reply on the PowerMac running 10.4.11 using the keyboard in question and my Bluetooth dongle. And YES, the keyboard is the older, white keyboard. Did I not share the model # in the original post, Apple Keyboard model M9270LL/A ? Did you not Google that if you're not familiar with these Model numbers?
You said, "...Another thought: did you "unpair" the keyboard from the old system before trying to pair it with the new one?..." What exactly does that mean? That's makes no sense at all. "Can you "see" the keyboard in the bluetooth setup window when trying to set it up or not?" What does my original post say?? YES, I can see the keyboard in OS X 10.5.8, I just can not pair with it.
As a last resort I have installed the Apple Aluminum Keyboard Update, as per your suggestion, even though I don't have an aluminium keyboard and this 'update' installed successfully but my keyboard, although seen will still not pair with the dongle. I will NOT go buy a Al Keyboard just to test this issue. The only thing I've thought about purchasing is the Bluetooth module so that I don't need to use a dongle, but those are expensive and often hard to find. I have also removed the prefs file from /user/Library with no effect.
I almost forgot. I also have another BT dingle from Kensington and although the system sees it as does the other, it does not pair with the keyboard either. That dongle works fine on my PeeCee laptop without any problems, so both dongles are functioning correctly. Do you have any other suggestions you would like to share?
Thank you for your time.
< Edited By Host >

FN key not working on Apple Wireless Keyboard

EDIT: Found the culprit: USB Overdrive was taking over the external keyboard. After disabling USB Overdrive for the keyboard, the FN key started working again.
I have Macbook Air (Mid 2013) connected to a Cinema Display and Apple Wireless Keyboard. MBA is running the latest Yosemite (10.10).
I tried using FN + Delete on the wireless keyboard to forward delete but it didn't work, it just deleted. I tried other keyboard shortcuts that require the use of FN key, and none of them work either. But when I try these directly on the MBA's keyboard, the FN key works perfectly there, just not on the wireless keyboard.
I've removed the bluetooth keyboard and tried reconnecting, restarting computer, login out and back in. Nothing works. Anyone have any ideas?
Message was edited by: Isko Salminen

I disabled "Any Keyboard, Any Application" and "Any Other, Any Application" but I still could not use my Fn key on my Apple Wireless Keyboard. Uninstalling (removing the driver) restored Fn key functionality. In addition downgrading from 3.1 to 3.0.2 on Yosemite also solved this issue.
Did you actually try what you wrote?
I should also note that the Fn key on my rMBP's internal keyboard works with 3.1, oddly enough, but the Apple Wireless Keyboard's Fn key does not.

Apple wireless keyboard doesn't work in windows all of a sudden how to fix please?

Hi All,
Last night my apple wireless keyboard stop working in windows. It is working perfectly fine in the OS system though. I have checked control panel in Windows 7 and found out that under Device management "apple keyboard" has an issue there, I have tried to follow the steps windows suggest but it doesn't work...How can I fix this please? Thanks a lot

this problem is fixed, but if anybody has an idea what happened, I would like to know.

How to disable "special" f-key function on Apple Wireless Keyboard in Windows 7

Hi. I dual-boot my iMac using an Apple Wireless Keyboard. In Mac OS's "Keyboard" system preference pane, I've chosen to treat the F-keys as actual F-keys, and not the "special" function keys, such as volume control and screen brightness. This however does not carry over to the Windows environment.
I cannot find an option to do this on the Windows 7 side. I've tried SharpKeys (popular Windows freeware key-mapping registry editor), however the program doesn't recognize the key being pushed (unless I hold the "Fn" key, at which point, it sees it as the F# key).
To reiterate, I'd like to know how to use the F1 through F12 keys as F1-F12 in Windows 7, without having to use the "Fn" key.

Hi alexia416,
If you would like to use your Apple keyboard in Boot Camp with the standard function keys as the default, you may find the following article helpful:
Boot Camp: Use the function keys on an Apple keyboard
For other keyboard-related Boot Camp issues, this article is also useful:
Boot Camp: About keyboards and key assignment for Microsoft Windows - Apple Support
Regards,
- Brenden

Apple Wireless Keyboard on iMac 20

Good morning everybody, two months ago i have installed an apple wireless keyboard model M9270T/A (not aluminium), model with numeric pad.
It runs properly since yesterday, when it stops to run.
I have tried to reinstall, it is discovered, but it doesn't linked and the led continue to lamp. So the system tells me that this bluetooth configuration is not supported by this Os X (but until yesterday it runs properly!?!?)
I have:
1) replaced the batteries
2) followed strictly what reported on support (turn off the keyboard, follo guidelines, update the latest version of software)...
No way...does anyone can help me?
Thanks in advance

Did you manage to get around your issue without resorting to a wired keyboard? My brother has the same issue.

AppLE /WIRELESS /keyboard /issue

Similar Messages

Maybe you are looking for