Problems with Creators Update and Broadcom 440x adapter

August 2 cumulative update seems to have fixed my Broadcom 440x NIC problem.

I can confirm that the latest cumulative update has the Broadcom 440x fix.  It was released 18 hours ago.  For those that are curious this is build 15063.502.  This has been a long four month drive to getting this fix investigated, fixed, and released.  Thank you all for your patience.  If you continue to have issues with the Broadcom 440x after applying this update please let us know on this thread.

So, thanks to you Travis for seeing it through and to all other posters for your contributions. Hope everybody gets their systems successfully patched or reinstalled to fix this issue.

Thanks Guys!  That means a lot.

In case you are curious about my role here and how we do this...I am an engineer in the Quality team that owns Core Networking.  This includes LAN, firewall, TCP/IP, and a host of other basic networking technologies.  I also work closely with those in wifi, cellular, and printing.  My job is to identify bugs after we release and drive the fixes back in the product.  In this case I was notified from a colleague that our telemetry was reporting a disproportionate rise in update roll backs with this network adapter.  I went to this forum and to reddit to try to corroborate what we were seeing.  Once I saw it was an issue I tried to get hardware that had this adapter.  This was hard to do as this is Vista era.  I went through Tyler who is our Support contact to get logs directly from some of you.  I also found a guy I worked with that had a personal Dell Inspiron 9300 at home that he donated to the cause.  With logs from the community and the repro laptop we determined the cause quickly.  I built a fix myself to prove that it worked and started engaging with the owners of TCPIP to get the fix put in.

A question that is often asked is "how many people are affected by this".  The answer for the Broadcom 440x issue is about 150,000.  That represents a very small percentage of all windows 10 users.  Something like .03%.  However I was always able to point to this thread for justification to get the fix in.  In other words...this fix was brought by you.  Without your engagement I would not have had the ammunition to get the fix approved.  So thank you very much!

Please continue to post your issues on the forums, reddit, twitter, and most importantly Feedback Hub.  There are lots of here that read through what you have to say.  I weekly present your posts to managers and directors so they understand the joys and pains you experience.