Holy cows you saved me. I don't really care about the fn keys anymore I just love the Apple Aluminium WIRED keyboard the old one with the numeric keypad. In Windows 11 I can't find a working BootCamp anymore, and if you run some AppleKeyboardInstaller you find on github, it removes function keys by default. Thankfully you found the REGISTRY key for the "OSX Fn Behaviour" which as the name implies lets you restore the Function keys by default without having to press fn. This matches the checkbox that showed on the BootCamp panel.
Thank you for the video. I was not able to get it to work following your exact instructions, but you leaded me to the solution. Here's what I did and my config. Using Apple Magic Keyboard A1644 on Windows 10 Using Brigadier I downloaded the model MacBookPro16,3 (the latest with Intel CPU) Open a command prompt with admin cd BootCamp/Drivers/Apple run BootCamp.msi and install the drivers Keyboard now works with no additional steps needed. FN key and all! WOOOO!
I installed Magic Utilities first and maybe there is a hidden driver that is preventing your method from working? It is the same program that you had in your installed apps, except the "Windows Package Driver - Apple Inc. Apple Keyboard (date & version)" is not there for me. I have uninstalled Magic Utilities itself and then installed the drivers via Brigadier but no luck :(
@@stanleychen3298 I've downloaded the 7zip. Turns out the newer version of 7zip fails to open it. Downgrading to 2019 version helps! Thank you for the video
Pro tip: just use 2nd source link in this video's description, then download and install drivers themselves (1.5MB) instead of full package (1.5GB). This worked for my Japanese A1314! Then you can just go to the "modifying registry" chapter of the video (or the same page above that you just opened) to change Fn key behaviour. upd: I decided to roll back to basic windows driver, because with apple driver even though I have function key working, I have 「英数」, 「かな」 and 「delete」keys working only with「fn」key pressed if I flip registry value :( Hope this info help somebody!
Hi, im trying this for my Magic Keyboard 2 (A1644) it seems the keyboard driver is different than the magic keyboard one howether when i type in a newer macbook model so i get the updated driver it isnt an exe file i can lauch for the driver but a bunch of .sys .cat and .inf files. Any suggestions to help?
I had a similar situation when using the latest version of 7zip (which I had manually installed). Using the one from the video (22.01) got me the same files as in the video.
Can you help with this error? ERROR: Traceback (most recent call last): File "brigadier", line 379, in <module> File "brigadier", line 313, in main File "brigadier", line 84, in sevenzipExtract File "subprocess.py", line 172, in call File "subprocess.py", line 394, in __init__ File "subprocess.py", line 644, in _execute_child WindowsError: [Error 2] The system cannot find the file specified [10560] Failed to execute script brigadier C:\Users\User\Downloads\brigadier-0.2.6> Thanks a lot if you can.
@@stanleychen3298 I have the same problem and I installed 7-zip before excecuting Brigadier. What can you suggest to do? Mb it's because I have a2450 model?
@@ternoviikust8480 I had 7-Zip already installed for years. Brigadier is trying to use it on this path: "C:\Program Files\7-Zip\7z.exe", so move its installation there (since you probably have it elsewhere, I had it on the D: drive) and you will be fine.
So for those whose function keys only worked as F1-F12 but not also as media keys no matter if they held the Fn key or not, I'll tell you what worked for me. For context, the model of my keyboard is the third generation (A1314) and I'm running Windows 11: 0. Uninstall any other Apple Wireless keyboard drivers 1. I will set the model to `MacBookPro16,4`, apparently the last model that supported Bootcamp 2. Run `brigadier.exe -m MacBookPro16,4` 3. Navigate to the created `BootCamp-041-96204\BootCamp\Drivers\Apple\AppleKeyboard` folder 4. Locate `Keymagic64.inf`, right-click and install 5. You may need to reboot your device 6. Your function keys should now work as both F1-F12 and media keys Warning, I don't know how to uninstall it, but this hasn't been a problem for me because I got what I wanted. But again, be warned, as I don't know yet what to do if I encounter an issue with this driver and I want to remove it. I've already tried deleting `oem37.inf` and `oem37.PNF` in `C:\Windows\INF` and deleting the KeyMagic driver in `C:\Windows\System32\DriverStore\FileRepository` (It's cryptic but its filename starts with `keymagic64`) and rebooting but to no avail. I think the driver could possibly be removed by installing another driver or editing something in the Registry, but I don't want to mess up what's working for me at this point and will only try these other methods if I ever encounter an issue. I'll also just post an issue in the brigadier Github repo. It *should* be undoable.
@@stanleychen3298 same one as you did I did try a couple others too but none of them seem to add it to registry. Although it does appear in the add or remove apps list as a driver
@@stanleychen3298 nope they don't work, fn key doesn't work too. It works once I download and install magic keyboard utilities but I have to pay for it annually which i'd rather not...
@@AllSWT Sounds like the Apple Drivers aren’t installed. Did you uninstall other related drivers as mentioned in the video? Because during my own testing conflicting drivers will make the keyboard flat out not work
