
OpenRuntime.efi (opens new window)( Required). For Sandy Bridge and older(as well as low end Ivy Bridge(i3 and Celerons), see the legacy section below. macOS Installers and Recovery partitions/images). HfsPlus.efi (opens new window)( Required). Getting started with ACPI (opens new window)įor the majority of systems, you'll only need 2. You can use the "Hide Update" option in Windows Update to fix that :). It might be that Windows 8 will at some point overwrite the driver with a newer Windows 8 driver version. Next and finish should leave you with a working network adapter. It should automatically highlight the correct option: Windows will now show you the driver to install. Select the "bcmwl6.inf" file and click "open". Right click it and choose Update Driver:Īnd finally navigate to the location you extracted the driver files (which you placed on the clipboard if you followed the instructions to the letter): Open the Device Manager en locate the Broadcom Wireless-N network adapter. Navigate to the Drivers\Win7\WL folder and put that location on your clipboard: Wireless WLAN 1510 Half MiniCard (4322). Wireless 1520 802.11n MiniCard WLAN for Desktops. Wireless WLAN 1501 Half Mini-Card (4313bgn). Wireless WLAN 1397 Half MiniCard (4312bg). So, for a Dell Latitude 6510, download the following Broadcom driver from the Dell support site (Windows 7 圆4): File Title Hide any updates pushed by Windows Update. Choose Let me pick the driver to install. Go into Device Manager and click Update Driver. Extract the installer to find the driver files.
Locate a Windows 7 圆4 driver for that card.Rolling back to a Windows 7 network driver disables that specific feature on the Windows 8 side, thus allowing you to connect without further issues. The issue is still a compatibility issue between the Windows 8 802.11w implementation and that of Cisco.
Except, I had not yet encountered his wireless network adapter. And he was indeed experiencing the same issues, where connections would always fail at work, but not at home. A colleague came to me today, having heard of my attempts to get my Samsung //Build slate to work on our internal (Cisco AP) wireless network.