cbonner

Further to my previous post, we have found that setting 'Specify global DNS' to enabled fixes the issue. This was a new group policy setting in 1709. https://docs.microsoft.com/en-us/windows/client-management/new-policies-for-windows-10#new-group-policy-settings-in-windows10-version-1709 The registry setting can also be manually set: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator\UseGlobalDNS DWORD Value 1 Hope that helps.

Been having the exact same issues described in the original post. So far seems to be related to 2004 update. For wireless devices the workaround here fixes the issue, but I don't think it works for ethernet connected devices. https://support.microsoft.com/en-gb/help/4494446/an-internet-explorer-or-edge-window-opens-when-your-computer-connects#:~:text=NLA%20uses%20a%20component%20that,has%20intranet%20or%20internet%20connectivity.&text=These%20probes%20are%20triggered%20by%20changes%20in%20any%20of%20the%20network%20interfaces.