#Apple keyboard and mouse wireless carrying case drivers
#Apple keyboard and mouse wireless carrying case driver
#Apple keyboard and mouse wireless carrying case code
#Apple keyboard and mouse wireless carrying case Pc
#Apple keyboard and mouse wireless carrying case Bluetooth

#Apple keyboard and mouse wireless carrying case Pc

To sum up: isn't it pretty curious that an awk can be connected even to a standard windows PC but not to a MBA running under win 10!? The two entries marked in red in the second screen shot above, have disappeared by now, btw.

#Apple keyboard and mouse wireless carrying case code

Not unexpectedly, this gets me the following:Īnd from now on, I am in a loop of 'ready for coupling - couple - no code - failure. Otherwise there would be no contuation possible at this point.

Since there is no code generated to be keyed in on the awk, I tried '0000' and '000000' by keying these in on the MBA's own keyboard. Upon clicking on 'couple' NO CODE is generated but rather this window shows up:

#Apple keyboard and mouse wireless carrying case drivers

Since these all are generic MS drivers as it seems to me at least, the faulty one should be the Apple KeyMagic.sys!Īnyway, upon trying to reconnect the freshly unpaired awk, this is what happens: At first, the MBA says 'there is an awk waiting to be coupled':

Upon comparison of these drivers with the drivers which become installed upon coupling the awk to a 'standard' win7/圆4 PC I note that ALL the drivers show up there too, however, the file sizes are slightly different as compared to the win 10/圆4 counterparts. Here are the comments with respect to the error message: (again I have inserted a translation of the relevant text).

#Apple keyboard and mouse wireless carrying case driver

The next picture shows that the respective (yellow marked) driver cannot be started: So I decided to further enlighten the problem a bit.

#Apple keyboard and mouse wireless carrying case Bluetooth

Much to my surprise, with a 'fresh' bootcamp driver installation the awk DOES show up both under bluetooth AND under HID, albeit in the latter case with a yellow error mark.įollowing the usual routines for reinstalling the driver etc. Now this is all in German (since I am German! :-) ) but it still should be understandable. After installing this and rebooting I got the following information from the device manager: This apparently installed some drivers but not all and so I decided to go for the official Apple release bootcamp. I followed this procedure (did NOT see the apple keyboard with the warning sign at this point, btw) and deleted all those drivers and tried to reinstall them from bootcamp 5640 hoping that the older (win7?) version would work better. The following picture suggests a way to connect the apple wireless keyboard (awk) to a stubborn machine: But hopefully I can now provide you with more details which, imho, clearly point to a driver error. I have tried that before and now once more precisely as you suggested - it did not work. I also note that a driver shows up under bluetooth drivers for that mouse - but there never was something like 'Apple Wireless Keyboard Driver'. It also could be that the bluetooth drivers are not compatible although they work fine with the wireless magic mouse and other bluetooth items. I wonder whether the keyboard driver is relevant here at all - perhaps this is the driver for the on-board-keyboard of the MBA? In any case there this just ONE keyboard driver in the device manager listed, not two, as one would expect. I also uninstalled the bluetooth drivers - no blue screen with win 10, but otherwise unsuccessful as before.

I uninstalled the keyboard drivers and put in those from earlier bootcamp versions - no change. Thereafter, I got stuck at the point where the keyboard is reported as coupled, but upon trying to actually connect it the window for keying in a code pops up (with no code generated automatically) and at that point all attempts fail (i.e. Still, the system offered me even a keycode to connect to the wireless keyboard, but did not give me enough time to key that code actually in. Right after installation of win 10 via the official bootcamp routines, I got a notification about a faulty driver. Everything runs fine now, but the wireless keyboard is not connectable at all any longer. In view of the availability of win 10/圆4, I decided to upgrade.

Recently, the system began to 'forget' about the wireless keyboard, which could be re-connected, sometimes automatically (after deleting all the drivers and reinstalling them (which, incidentally, even resulted in a windows blue screen which was recoverable from by simple rebooting)) and sometimes manually by keying in the automatically generated code number. This constellation worked fine both under MacOS (currently 10.11.5) and bootcamp win 7-64. I run a mid 2013 MBA plus cinema display plus apple wireless keyboard (model A1255).