I personally went with this (manual) approach:ġ. There's many janky looking apps out there that try to do this. Then additionally, if you want to have PrintScreen, Ins and NumLock keys you'll need to remap some of the Apple keyboard's F keys. One needs to enable support for legacy USB devices in UEFI/BIOS to make it recognize Apple keyboard during POST.

So again, no need to download & install any Apple drivers. And if I just plug in that Apple keyboard into a USB-3 port, it works right out of the box. I tried it on a brand new installation of Windows 10. The thing I learned is that there's absolutely no need to even touch Apple Bootcamp installer to make the external Apple keyboard work on a Windows 10 device. Volume Shadow Copy was failing with these two error messages:įirst. I'm posting these error codes so that someone else can find this post through a Google search. Note to self: NEVER EVER install Apple software on a Windows device!

Then, at least I'm at square one, having my backups working again! See these two:Īnd then while trying to remove it I discovered another nasty surprise. I was able to discover it with the Autoruns tool. (The unresolved question that only Apple probably knows, is why do I need a file system driver for the keyboard? But that's beside the point.) Evidently the Bootcamp installer installs their HFS file system driver. Until I eventually found out the root cause. I noticed that my backups stopped working and the Volume Shadow Copy was giving out an initialization error. I did and it took me two days to restore my computer back to normal. Guys, whoever reads this DO NOT install Apple Bootcamp. When I boot up that PC with just the Apple keyboard plugged in via USB, the post gives me this and stops the boot: My main goal with using that key mapping app was to map keys I circled in red above, namely:Īnd there's another issue, which is probably even bigger than the one above. When I loaded it up, the app showed as such:īut if you look at the Apple keyboard, it looks like this - as you see the entire extended part of the keyboard is missing from the app! Maybe I'm just not understanding how it works. I then followed this tutorial on configuring it with the Keyboard Layout Creator 1.4 app. I didn't have the issue like others experienced with mixed up and # keys, etc. So after a reboot (that had it's own issues, but I'll get to it later) the Apple keyboard was recognized and worked for 95% of keys. (And apart from that silly thing renaming my drive C into 'bootcamp' it didn't seem to have done much.) I followed this tutorial on how to install the Bootcamp driver. I was able to play with your suggested setup this weekend.

Can i use apple keyboard on pc