Seems to be there is a serious bug in BCM43xx adapter firmware (MacBook Pro 15 mid 2014) resulting in failed S3 resume initialization (wake-up from Sleep) under Windows 10. Detection algorithm: 1. Using Device Manager completely uninstall Broadcom 802.11ac network driver with option 'Delete the driver software for the device'. Press 'Scan for hardware changes' button to detect device instance named as 'Network Adapter' and select 'View' >'Show hidden devices' from menu, so you can see only one 'Network Adapter' device. Put your computer into sleep mode by selecting 'Power' >'Sleep' from start menu and some times later resume it by pressing space bar for eg.

Jan 29, 2016. Because the Apple should provide us with firmware update to solve. Windows 10: BCM43xx S3 resume firmware. Firmware Version: Broadcom BCM43xx 1.0. Top 3 Ways to Download and Update Broadcom Drivers on. You could try the Broadcom driver update utility. Controller driver. BCM4318 BCM43XX driver. Broadcom USH. Windows x64 driver update for NetXtreme I/II Broadcom Ethernet adapters. Driver Details. For more downloads go to the Drivers and downloads. Broadcom Limited is a diversified global semiconductor leader built on 50 years of innovation. Software Development Kit Logical Table. Download Agreement.

Now you can see another detected (duplicated) 'Network Adapter' device instance as active, but the first one becomes inactive. This is because failed adapter firmware initialization on S3 resume. Reboot your computer, open Device Manager again with 'View' >'Show hidden devices' option to see (vice versa) the first 'Network Adapter' device instance as active, but another one (duplicated) becomes inactive. As a result you always have annoying problem with wi-fi network connection after sleep mode until reboot.

Of course you can repeat steps with Broadcom 802.11ac network driver installed, it doesn't matter, because the Apple should provide us with firmware update to solve this hardware problem. Any other ideas? Best Regards. MacBook Pro with Retina display, Windows 10 Posted on Jan 12, 2016 1:33 PM. As far as I already described above, the Broadcom wireless driver was completely removed to perform clear test for just device (no driver) initialization and detection to avoid confusion.

Device initialization test passed with 'Power-On', 'Reboot' and 'Resume from Hibernate' modes, but this test failed with 'Wake-Up from Sleep' mode, so I got duplicated 'Network Adapter' instances for one physical device. It looks like the adapter firmware doesn't perform correctly EFI specification S3 Resume algorithm that results in failed hardware device initialization. In this case I have no idea except the Apple should provide firmware update to correct this serious hardware issue. It would be interesting also to get reports on test (in the first post) from the MacBook Pro late 2013 users, and probably from MacBook Pro 2015 users as well. Jan 12, 2016 4:45 PM.

In addition I have attached test report in pictures with the latest available Broadcom driver 7.35.338.0 and without driver also powercfg.exe /A The following sleep states are available on this system: Standby (S3) Hibernate Hybrid Sleep Fast Startup The following sleep states are not available on this system: Standby (S1) The system firmware does not support this standby state. Standby (S2) The system firmware does not support this standby state.

Standby (S0 Low Power Idle) The system firmware does not support this standby state. Jan 13, 2016 4:39 AM. Looking at 'Device Manager' window as well I can say that only second instance of device initialization successful, but why not the first one? I don't have the full project of Apple EFI for my platform, so I guess the right way to address such questions to the Apple Engineers.

For example, I don't know why Apple still use old Intel ME firmware v9.0.5.1367 while v9.0.50.1022 is the newest one for Haswel microarchitecture. Even better, Intel released ME v9.1.37.1002 (for Broadwel and Haswell) to support ME Software v11.0 for the Windows 10 launch and Most of problems could be solved better by keeping EFI and its OEM components firmware up to date, than by dreaming about bugs. In my opinion, if I pay gorgeous price to Apple then I consider to get reciprocal support. Is it right condition? Jan 13, 2016 10:40 AM. Its a hardware problem from manufacturer that probably could be fixed by firmware update. The 'EFI and firmware' must report single device instance for single Broadcom Wireless network adapter (NOT TWICE!) after S3 resume (wake up from sleep), no matter which operation system is booted.