Windows 10 shows "No Internet" although LAN/WLAN works - NCSI error - The company configuration is not available...

Question

Hi

We have been struggling with the NCSI error "No Internet connection" despite a working LAN/WLAN for some time now.

This error only occurs sporadically with some clients, but it is common throughout the company.

It's not always the same clients that are affected - it's someone else every day. Unfortunately, there is no direct pattern (same VLAN, same switch, same department). Only that it exclusively affects Windows 10 clients (no matter which version).

PS: We do not have a proxy or similar in use.

Here are some excerpts from the eventlog:

Client 1 (Windows 10 22H2)

 Information 09/20/2023 1:43:51 PM Microsoft-Windows-NCSI 4039 Internet Connectivity Detection "No hotspot was detected on interface ""0x6008001000000"" (Family: v4)."

Information 09/20/2023 1:43:51 PM Microsoft-Windows-NCSI 4039 Internet Connectivity Detection "No hotspot was detected on interface ""0x6008001000000"" (Family: v6)."

Information 09/20/2023 1:44:04 PM Microsoft-Windows-NCSI 4044 No state change for passive polling (ShouldPassivePollRun: true, WasPassivePollRunning: false, IsPassivePollAllowed: true, ClientPresent: true, UserPresent: true, NetworkQuietMode: false, DeadUserPollCount: 0, DeadNetPollCountV4 : 0, DeadNetPollCountV6: 0)

Warning 09/20/2023 1:44:04 PM Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is invalid.

Warning 09/20/2023 1:44:04 PM Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is not available.

Warning 09/20/2023 1:44:04 PM Microsoft-Windows-NCSI 2003 Check internal/external company location The check of the internal/external company location is skipped. Cause: The company configuration is not available.

Information 09/20/2023 1:44:05 PM Microsoft-Windows-NCSI 4004 Waiting for local connectivity Transition to status: Internet connectivity Interface LUID: 0x47008000000000

Information 09/20/2023 1:44:05 PM Microsoft-Windows-NCSI 4005 Waiting for Internet connectivity Entered status: Internet connectivity Interface LUID: 0x47008000000000

Information 09/20/2023 1:44:05 PM Microsoft-Windows-NCSI 4006 Waiting for Internet connectivity Transition to status: Internet connectivity Interface LUID: 0x47008000000000

Information 09/20/2023 1:44:05 PM Microsoft-Windows-NCSI 4027 Internet Connectivity Detection The opportunistic Internet flag on interface {28865042-2a52-4756-9a3e-d079a85c2933} for family v4 has been flagged.

Information 09/20/2023 1:44:05 PM Microsoft-Windows-NCSI 4052 No interface diagnostics for {28865042-2a52-4756-9a3e-d079a85c2933} (0x47008000000000): IPv4 address: true, IPv6 address: true, IPv4 function: true , IPv6 function: no data, IPv4 test used: Passive, IPv6 test used: no data

Warning 09/20/2023 1:44:14 PM Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is invalid.

Warning 09/20/2023 1:44:14 PM Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is not available.

Warning 09/20/2023 1:44:14 PM Microsoft-Windows-NCSI 2003 Check internal/external company location The check of the internal/external company location is skipped. Cause: The company configuration is not available.

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4040 None "The connection to the interface ""{48d7a9f3-85c9-4695-a203-7e1ae082297e}"" (0x6008001000000) has been established."

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4001 Waiting for NetReady Entered status: Interface reception Interface LUID: 0x6008001000000

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4007 Waiting for enterprise connectivity Entered status: No enterprise connectivity Interface LUID: 0x6008001000000

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4047 None "Default gateway has been set for ""{48d7a9f3-85c9-4695-a203-7e1ae082297e}"" (Family (0x6008001000000): v4, GatewayIP: 192.168.0.1 , GatewayMAC: 0xEC9B8BC58C53, KnownProxyless: false, KnownHotspot: false, KnownOppInternet: false, KnownProxiedOppInternet: false)"

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4049 No "Change of preferred address for ""{48d7a9f3-85c9-4695-a203-7e1ae082297e}"" (Family (0x6008001000000): v4, HasPreferredAddress: true, AddressSuffixOr igins : 0x8)"

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4048 None "Next hop to Internet has been changed for ""{48d7a9f3-85c9-4695-a203-7e1ae082297e}"" (Family (0x6008001000000): v4, HasNextHopToInternet: true , NextHopAddress: 192.168.0.1)"

Information 09/20/2023 1:44:28 PM Microsoft-Windows-NCSI 4035 Internet Connectivity Discovery Aborting hotspot discovery scenario for interface {48d7a9f3-85c9-4695-a203-7e1ae082297e}.

Client 2 (Windows 10 22H2)

Information 09/20/2023 09:52:27 Microsoft-Windows-NCSI 4039 Internet Connectivity Detection "No hotspot was detected on interface ""0x6008002000000"" (Family: v4)."

Information 09/20/2023 09:52:27 Microsoft-Windows-NCSI 4037 Internet Connectivity Detection "Starting hotspot detection for family ""v4"" on interface ""0x6008002000000""..."

Warning 09/20/2023 09:52:28 Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is invalid.

Warning 09/20/2023 09:52:28 Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is not available.

Warning 09/20/2023 09:52:28 Microsoft-Windows-NCSI 2003 Check internal/external company location The check of the internal/external company location is skipped. Cause: The company configuration is not available.

Information 09/20/2023 09:52:29 Microsoft-Windows-NCSI 4025 Proxy detection The proxy detection has been started.

Information 09/20/2023 09:52:29 Microsoft-Windows-NCSI 4026 Proxy detection The proxy detection was ended (HasProxy=122).

Information 09/20/2023 09:52:38 Microsoft-Windows-NCSI 4004 Waiting for local connectivity Transition to status: Local connectivity Interface LUID: 0x6008002000000

Information 09/20/2023 09:52:38 Microsoft-Windows-NCSI 4005 Waiting for Internet connectivity Entered status: Local connectivity Interface LUID: 0x6008002000000

Information 09/20/2023 09:52:38 Microsoft-Windows-NCSI 4052 No interface diagnostics for {fcaee3b5-232b-4ba2-a594-6818bdc386b2} (0x47008000000000): IPv4 address: true, IPv6 address: true, IPv4 function: false , IPv6 function: no data, IPv4 test used: Passive, IPv6 test used: no data

Client 3 (Windows 11 22H2)

Warning 09/20/2023 11:50:31 Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is invalid.

Warning 09/20/2023 11:50:31 Microsoft-Windows-NCSI 2001 Waiting for enterprise connectivity The enterprise connectivity check is skipped. Cause: The company configuration is not available.

Warning 09/20/2023 11:50:31 Microsoft-Windows-NCSI 2003 Check internal/external company location The check of the internal/external company location is skipped. Cause: The company configuration is not available.

However, on this Windows 11 machine, the connectivity display works despite the same errors. Generally we have no such problems with Windows 11.

I have already tested all settings via the registry + GPO's and unfortunately come to no viable solution. On the contrary, only got worse.

I'm at my wit's end and can't find anything on the internet that I haven't already tested. I hope someone knows this error and can help me.

Here is the configuration of our registry and GPO's:

Answer 1

This has been an ongoing issue. We have done everything in our power to correct this problem.

We had the issue resolved after Cisco Umbrella and Microsoft made changes to their system but after upgrading to Windows 11 the issues have returned.

We can ping the Testserver successfully w/o issues. We have nearly identical logs to what is displayed here. The only solution we've found that works is disabling the active/passive polling entirely from the Registry.