No Internet Access Fall Creators Update

scriptingsteve · 10 Nov 2017

We discovered that if Bitlocker is in use and you have this GPO enabled on your computer:

Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Disable New DMA devices when this computer is locked

then once you upgrade to v1709, any computer with a wifi adapter seems to be completely unable to use any networking at all (even the Ethernet adapter is inoperative). We reported the issue to Microsoft. Removing the GPO setting (i.e. setting it to 'Not configured') resolves the issue and v1709 works fine after that point. Since an affected computer can't get on the network to consume the updated group policy, a reimage is required (unless you want to find the reg keys that the bad GPO settings applied and try to remove them... I didn't bother).

It was an Intel site, not Microsoft, that had this info:

https://communities.intel.com/thread/118750

Good luck!

mmTalish33 · 10 Nov 2017

@scriptingsteve

I checked in group policy editor. it is already set to not configured.@
@Caledon Ken
When I unplug the device "Remote NDIS based internet Sharing Device#2" disappears from network adapters.

I contacted telco they say devices are compatible with all Windows 10 versions.

Caledon Ken · 11 Nov 2017

Okay then confirm manufacturer, date and version of driver associated with "Remote NDIS based internet Sharing Device#2" and then compare that to what the telco says it should be using.

If you look at properties of driver, under General tab, what is the device status box saying?

I assume there was only one device plugged in at time of screen shot and this is why it says #2. Does posting #11 apply to you?

You didn't say what AV or multiple AV's you are running. If you disable all, just for a quick test, can you connect?

Ken

mmTalish33 · 13 Nov 2017

Forget it. Couldn't take it anymore. I reverted back to 1703

Caledon Ken · 13 Nov 2017

Smart idea.

There is definitely an opportunity for improvement in terms of Windows wireless connections, either cellular or wifi. My opinion is that MS is accepting to many devices that stretch back at least 10 years. Of course they want the Win 10 install numbers so they didn't have a choice. Now we have such a mix of hardware / protocols in the environment it is causing issues. Time moves on.

Are you going to set connection to metered to prevent a re-install?

Good luck.

Ken