Add driver to the system Run WindowsSupport BootCamp Drivers Broadcom BroadcomBluetooth64.exe (probably similar procedure will work for WiFi, so you could also run BroadcomWirelessUDMx64.exe to add drivers to the system) Install the driver 1. Open Device Manager 2. Right-click on the device (Bluetooth USB Host Controller) 3. Update the driver 4.

• Macbook Windows 10 Wifi Driver
• Network Controller Driver Windows 10 Macbook Air Download
• Macbook Pro Drivers Windows 10

Windows and USB Ethernet Adapter I have talked to Applecare twice in the past couple of days about the USB Ethernet Adapter not working on the Windows side of the Air, and the need for drivers. They do not have anything available in their system about this problem (hopefully they do now!). Download this driver package and unzip it to a folder on the Intel NUC. Connect a Thunderbolt device to the Thunderbolt port. Browse to and select the folder where you unzipped the driver package. Right-click on all four.inf files and select Install. By clicking on the 'I ACCEPT' below I agree to the terms of the Limited Use License Agreement display above on behalf of myself and my company.

This worked for me; it might not work for you. Remember I’m just same random guy on the internet so I take no responsibility for anything that happens to your machine. Okay?

The Problem

As yet (5th Aug 2015) there’s no official support from Apple for Windows 10 running through Boot Camp. So, when I upgraded from Windows 8.1 to 10, I was expecting there to be a couple of issues. One of these was a lack of Bluetooth. Also getting the fn key working.

But, it turns out to be easy to fix.

Get the Driver

The driver for Windows 8.1 works with 10, so you just need to grab that.

Go to https://support.apple.com/en-us/HT204048 and find your machine in the list. You want to look for the zip file download of the Boot Camp Assistant software.

For me, it was this one:

Download that file (it’s pretty big – 882Mb for my one) and unzip that once done.

Install the Driver

Inside the unpacked folder, go into the BootCamp folder and then into the $WinPEDriver$ folder under that.

The driver needs to be installed via device manager so just confirm that the AppleBluetoothBroadcom64 folder is there for now.

In Windows, open up device manager (the easiest way to do this is just hit the Windows key and type ‘device manager’ – it’ll be the first result).

Expand other devices and you should see an unknown device.

Right click it and select Update driver software.

Chose the second option on the pop up to browse your computer for the driver software.

Browse to the $WinPEDriver$ from your downloads and select that. Make sure Include subfolders is checked and then click Next and Windows will install the Bluetooth driver for your Mac Book.

Update Oct 2015: Updated for 10.11 El Capitan!

If you bought a cheap aftermarket USB-Ethernet adapter like me and found that it doesn't work on El Capitan or Yosemite, here's what you need to get it going.

Macbook Windows 10 Wifi Driver

Seriously. You can stop tearing you hair out now. It'll all be ok.

As with all advice on the internet, you can't sue me if this sets fire to your cat or sends ninjas to your house. You're doing this on your own, and I assume no liability or warranty for what you do.

Steps to get your adapter working if you just upgraded to Mac OS 10.11 El Capitan.

1. Reboot. As soon as the screen goes black, hold down 'Command' and 'R' until you see a black screen with an Apple logo and a white progress bar. Let go, and wait for your computer to boot into recovery mode.
2. From the top bar, select 'Utilities' and then 'Terminal'
3. In the terminal, run csrutil disable.
4. From the top bar, select '', then 'Restart'
5. When you boot back up, you'll have a working adapter!
6. Definitely take a read down below to see what's changed in El Capitan, and if disabling SIP makes sense for your setup.

Network Controller Driver Windows 10 Macbook Air Download

Steps to get your adapter working if you've never used the adapter before in Mac OS 10.11 El Capitan.

1. Uninstall the dozens of other drivers you may have installed in the process of trying to get this working.
2. Unplug your USB adapter, and reboot and give yourself a clean slate.
3. Reboot. As soon as the screen goes black, hold down 'Command' and 'R' until you see a black screen with an Apple logo and a white progress bar. Let go, and wait for your computer to boot into recovery mode.
4. From the top bar, select 'Utilities' and then 'Terminal'
5. In the terminal, run csrutil disable.
6. From the top bar, select '', then 'Restart'
7. Once you're booted back up, download and install the drivers from the CD, kindly uploaded by this fine human being.
8. Reboot.
9. Open your terminal, and run sudo kextload /System/Library/Extensions/USBCDCEthernet.kext
10. Reboot.
11. Plug in your USB Adapter, with a live ethernet cable.
12. Open System Preferences, and go to the Network Pane.
13. Hit the + button in the bottom right, select the 'USB 2.0 10/100M Ethernet Adapter', and hit add.
14. You're all set! Your adapter works!
15. Apologize to the people you care about for the things you've said over the past few hours. They won't understand, but they will forgive you.

Steps to get your adapter working on Mac OS 10.10 Yosemite

1. Uninstall the dozens of other drivers you may have installed in the process of trying to get this working.
2. Unplug your USB adapter, and reboot and give yourself a clean slate.
3. Download and install the drivers from the CD, kindly uploaded by this fine human being.
4. Reboot.
5. Open your terminal, and run sudo nvram boot-args='kext-dev-mode=1'
6. Reboot.
7. Open your terminal, and run sudo kextload /System/Library/Extensions/USBCDCEthernet.kext
8. Reboot.
9. Plug in your USB Adapter, with a live ethernet cable.
10. Open System Preferences, and go to the Network Pane.
11. Hit the + button in the bottom right, select the 'USB 2.0 10/100M Ethernet Adapter', and hit add.
12. You're all set! Your adapter works!
13. Apologize to the people you care about for the things you've said over the past few hours. They won't understand, but they will forgive you.

What's going on. (Yosemite Version).

The old drivers still work, no problem, but are being blocked in Yosemite because they aren't 'signed' properly, since they weren't re-issued for Yosemite. As 'unsigned' drivers, Mac OS refuses to load them, saying they constitute a security hazard.

What step 5 does is instructs your computer to set itself to 'developer mode', which allows you to load unsigned kexts. This is a mild security risk, but it should be fine for most people. If you're in doubt, please make the decision that makes the most sense for your security concerns. You might be better off just buying legit Apple hardware so you don't have to disable the security. That's your call.

Macbook Pro Drivers Windows 10

If you ever do go legit and want to undo it, just run sudo nvram boot-args='kext-dev-mode=0, and things will be back where you left them.

What's going on. (El Capitan Version).

In short, it's the same scenario as Yosemite, just stricter. Apple has a new security mode, called 'System Integrity Protection' (SIP) that prevents anyone - even you with your password - from modifying system files.

The old drivers still work, no problem, but are being blocked in El Capitan because they aren't 'signed' properly, since they weren't re-issued for El Capitan. As 'unsigned' drivers, Mac OS refuses to load them, saying they constitute a security hazard.

The csrutil disable step turns off SIP for your entire system, which allows you to load and use the drivers. This also disables malware protection for your machine, and given that we've started to see genuine malware for OS X in the wild, it's a slightly larger security risk than it was in Yosemite.

If you're in doubt, please make the decision that makes the most sense for your security concerns. You might be better off just buying legit Apple hardware so you don't have to disable the security. That's your call.

If you ever do go legit and want to undo it, just reboot into recovery mode and run csrutil enable, and things will be back where you left them.

Anyhow, after hours of searching and pulling out my own hair, I thought it'd be worth sharing the solution! Enjoy!