Win7-64 intel computer apple wireless keyboard

I have a (1st gen?) apple wireless keyboard.
I had previously used it quite successfully in my intel e8400 Vista 32bit computer. (Kensington bluetooth dongle)
I recently built a a Win7 intel Core i7 64bit computer. (Home premium)
I tried the same (older model) bluetooth dongle and pair up the same wireless keyboard. No Go.
When I call Kensington, they swear it is just that I have an old model dongle and a new dongle will fix it up right, no problem. So......I order the dongle, wait a week and install it. No Go.
Interestingly, the Win7 computer finds the keyboard, identifies it as an apple wireless keyboard, and asks for the pairing code. I type in 1234 or 0000 (on a plugged in keybaord) and then the circle spins...and spins. Finally one of two things happens. Either the bluetooth tells me the keybaord timed out, or it says the incorrect code was entered.
A phone call and inquiry to Apple sales staff and they say that the "tech guys" say that due to "improvements" the new apple wireless keyboards will not work with anything but an apple computer.
I just find that a little hard to believe. since it is bluetooth, and the older keyboard (that has not therefore been "improved"), the switch from 32 to 64 bit shouldn't make an difference should it (radio signals is radio signals, right?)? and the Vista to Win7 switch should not matter either?
First question, Am I putting in the right pairing code?
Second question, any thought on whether this is possible or not?
Your thoughts, suggestions, etc., are appreciated in advance.

Hi Heleny,
Sorry to hear about your trouble connecting the keyboard. What version of operating system do you have? You are trying to connect it with bluetooth correct?
Thank you,
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP

Similar Messages

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.

Connect multiple 2 apple wireless keyboards to one imac computer

How to connect several apple wireless keyboards to one imac? Ive got 2 apple keyboards that I want keep and use in different rooms (have more screens connected there). I manage to connect my logitech edge keyboard and mouse in addition to the already connected apple magic mouse and apple wireless keyboard. But it does not seem as if the imac will accept another apple wireless keyboard?

Hello Steve:
I have not had a similar problem so I am fishing a bit. I think the problem is rooted in what I thought in my previous post.
Now, how to fix it?
Try this:
Go to system preferences>bluetooth. Delete any KB entries there. Trash a preference file (com.apple.bluetooth.plist). Be sure that on and discoverable are checked in the BT preference pane. Restart your computer.
Hopefully, whatever KB you have turned on will be "discovered."
Barry
.

Computer cannot discover my apple wireless keyboard.

I watched the youtube show about how to connect apple wireless keyboard to pc, and I did it step by step. But pc can't dicover the keyboard.
The keyboard is able to connect to ipad and iphone.. so it is turn on as "discoverable".
Someone help please??~~ Thanks!

Hi Heleny,
Sorry to hear about your trouble connecting the keyboard. What version of operating system do you have? You are trying to connect it with bluetooth correct?
Thank you,
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP

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 >

Apple Wireless Keyboard help needed

My wife's computer is a 24" 2.33ghz Intel Core 2 duo iMac, 2gb ram, OS 10.4.9
2 days ago her Apple Wireless keyboard stopped being recognized by the computer. When I turn it on the light blinks, but the computer never recognizes it. When I go to the bluetooth setup assistant and try to manually setup a "keyboard", it never recognizes it.
However, if I try to setup "any device", the keyboard shows up in the list, but still cannot be paired with. I am using the wireless mighty mouse, it still works perfectly fine.
I have not done any updates on this system in weeks, 10.4.9 was updated on March 17th, the keyboard did not go down until 48 hours ago. (I know, it could still be a software conflict/issue, but each day after a change it usually becomes less likely)
No other software has been added to the computer since the updates in mid-March, and as I said the keyboard is recognized if I set up any device, but not cannot be paired with. Nothing was moved, installed (hardware or software) or dropped, so I am stumped.
Have reset the PRAM, SMC, turned bluetooth off and on, changed keyboard batteries, deleted the bluetooth prefs (as per macfixit article) all to no avail.
Any ideas before bringing in for service would be welcome.

Me too, the exact same symptoms. It may help troubleshooting to know the following:
- The same occurred with a PPC G4 Mac mini running Mac OS X 10.4.8 (could even have been 10.4.7, can't remember). Problem persists after updating to 10.4.9.
- The behaviour is exactly the same on an Intel Core 2 Duo MacBook 2.0 GHz running Mac OS X 10.4.9.
- The problem started after the batteries went completely flat.
I've checked with the Bluetooth utility from Developer Tools; the keyboard is alive but reports itself as "Unknown".
I wanted to try updating the keyboard firmware using the Apple Wireless Keyboard Updater 1.1 (http://www.apple.com/support/downloads/wirelesskeyboardmousefirmwareupdate.html) in the hope that it would make the keyboard report itself correctly again. But the updater just crashes in 10.4.9 (or Tiger in general), because it uses a private framework that has apparently been removed.
I borrowed Panther installation disks from a friend to run the updater, but I can't boot even my mini with them because it shipped with Tiger.

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.

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

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.

Powering Apple Wireless Keyboard

I know this is a keyboard issue, but there's no keyboard Discussion area, and I'm using it with a MacBook Pro... thanks in advance for any help.
Using a new Apple Wireless Keyboard (the latest tiny aluminium one), it seems unclear how to use something as simple as the power button!
Apple say "The keyboard automatically powers down when you're not using it and turns on instantly as soon as you start typing. This intelligent power management means you'll get up to nine months of battery life based on average usage patterns." I get all that - sounds great! But, they go on to say "It also has an on/off switch for when you're away from your computer for a long time." But there's nothing to explain how that works. If I stop working, turn it off and walk away, there's nothing to indicate that it's turned off. When I come back to work, do I need to turn it on again or does it just power up automatically from the 'turned off' state? If so, What did the turning off actually do? Or this a 'fridge light' situation??
Point is, I see no point in the power button if the unit turns off automatically when I stop using it, and there's nothing on the device to indicate whether it's been switched off or on. And it has used the new set of batteries far too quickly for my liking (less than a week), especially considering that Apple suggest a long (up to nine months) battery life. Mind you, as is always the case, the "up to" terminology also means "down to" (zero) I guess.
Any help or advice much appreciated. Thanks.

I had the same questions after installing my keyboard. When I powered it up the first time, the power light came on and then went off. My power light seems to be off even when I'm using the keyboard to type. So that's not a valid indication of "sleep mode". However, I found to turn it off completely I pushed the power button, and the power light came back on. Then I pushed and held the power button for a few seconds. The power light went out and I saw a keyboard icon on my display with "connection lost" below it. Powered it back on by pushing the power button and was back in business immediately.
The manual is skimpy and confusing. It reads, "Note: When the Power On light is off, the keyboard is off." That's on page 3. Well it's working well right now, with the light off. If the manual is correct (it's not, but if it were) then my batteries would last a very, very long time.
Nice keyboard though, and very portable for a ModBook - if I ever get one.

Will an Apple wireless keyboard pair with an iPad2?

Is an Apple wireless keyboard designed to pair with an iPad 2? The instruction book refers to a Mac computer but never to an iPad. I keep getting the "Pairing Unsuccessful" message after I type in the 4 digit code that the iPad tells me to enter on the keyboard. The keyboard gives me the flashing light saying it's ready to pair, but doesn't make the hook-up. The keyboard is just a foot from the iPad. Any suggestions?

This might help.
Note the following:
The original Apple Wireless Keyboard, introduced in 2003, is not compatible:
Apple Wireless Keyboard (2003): Features a white case and uses four AA batteries.
In addition, many third-party Bluetooth keyboards that use the Apple keyboard layout are also compatible. Check with the keyboard manufacturer for additional information.

Budget alternative to Apple Wireless Keyboard?

Because of my current apartment set up, my computer is rarely in a position where a corded keyboard will suffice anymore. The cords are just too troublesome and even with a USB extension cable, it's not long/free enough for me. So I've turned my head towards wirless keyboards, and I have a few questions.
1. What is a good budget alternative to the Apple Wireless Keyboard (AWK from now on)that will run in OS X? By budget, I mean cheaper than the AWK, and preferably with a bluetooth adapter included (though this is a negotiable term). Those designed for Windows that still work with Mac are acceptable, as I believe that this software (http://gnufoo.org/ucontrol/ucontrol.html) should alleviate the alt/windows key problem.
2. Do I need the D-Link Bluetooth adapter to use the AWK, or are cheap alternative such as the following possible candidates?
(http://www.newegg.com/Product/Product.asp?Item=N82E16833340003)
3. While browsing, I came across a Keyboard/Trackball combination which claims to work with Macintosh. I tried to locate a review that could confirm or deny it, but was unable to. The product is this:
http://www.performance-pcs.com/catalog/index.php?mainpage=product_info&productsid=4066
Does anyone have any experience with a wireless keyboard+trackball, and would they recommend it?
I just want to know all of my options before I purchase a new keyboard.
Power Mac G3 800 mhz Mac OS X (10.4.2)

Eventually just bought the Apple Keyboard.

Apple Wireless Keyboard

I cannot get my apple wireless keyboard to work. I changed the batteries and now I can't get it to pair. When I go into set up bluetooth device I click on find keyboard and it shows nothing found. When I click other device it recognizes it but when I type in the passkey (number on the bottom of keyboard) it will not pair. Please help..

Are you using the new wireless keyboard, or the older version?
I am having similar problems with my wireless keyboard. One day it just stopped working. I took it in to the Genius Bar, and they couldn't figure out what was wrong with it either. They replaced it for me. My new one still won't work. It is strange, because my computer recognizes the keyboard, and it seems to be paired. When I type on the keyboard, it is as though the computer recognizes it as a mouse - the cursor jumps around, and if I hit the "I" key, it "clicks" as though the mouse were clicked.
Unfortunately, I am now back at school in Santa Barbara, and there are no Mac stores to visit. Furthermore, I am no longer covered by phone support (you'd think that the wireless keyboard would be covered... no such luck.) Have you had any luck with your problem?

Win7-64 intel computer apple wireless keyboard

Similar Messages

Maybe you are looking for