[BUG]: The network icon shows as unavailable even though it is available

[mathmakgakpak]

Description

The network shows as unavailable even though it is available (I can browse the internet).
I don't know which one script caused it.
I briefly searched (wi-fi, network, icon, internet) open and closed issues but I couldn't find anything related to scripts I chose.
What's sad that it only happens on my local machine and it works just fine on virtual box machine.

OS

Windows 22H2 19045.2728

Reproduction steps

1. Run the script
2. Restart PC
3. The network shows as unavailable even though it is available
4. You still can browse the internet

Scripts

https://pastebin.com/a5nCqYku

Screenshots

Additional information

[mathmakgakpak]

well I can't reproduce it on other computers so I guess I was just unlucky.
Note: my pc got hibernated before restarting

[mshpp]

I would have to reopen this issue, this persists in my case and there's no solution I have found yet. Does anyone have any ideas?
This seems to be caused by a script blocking a domain used by Windows to determine if a WiFi network is connected to the internet. When I open the WiFi-popup, it shows "Connected, no internet", even though internet access is available.

UPD: So, the problem seems to have been solved. The culprit was the NCSI service, for which there's a toggle in the script settings. Turning it on (reverting the "disable" action) fixed the problem, and the icon works correctly even after turning NCSI active probing back off again.

[undergroundwires]

Thank you for sharing insights @mshpp, did Disable active probing to Microsoft NCSI server resolve the issue for you? Or do you mean something else as NCSI service? I will update the docs, and adjust recommendations based on your feedback.

Was this this script in particular, causing the issue:

:: ----------------------------------------------------------
:: -Disable active probing to Microsoft NCSI server (revert)-
:: ----------------------------------------------------------
echo --- Disable active probing to Microsoft NCSI server (revert)
reg add "HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet" /v "EnableActiveProbing" /t REG_DWORD /d "1" /f
:: ----------------------------------------------------------

[mshpp]

Correct, it was the "Disable active probing ..." script that caused the issue. Moreover, it seems that the script does need to be disabled/not applied (thus, the probing should be *enabled*) for the WiFi signal indicator to work correctly. Otherwise it works unreliably. I may be mistaken, but my desktop PC, which is connected through an Ethernet cable, has also had the "Strict" template applied, which includes the "Disable active probing ..." script. However, the issue does not seem to manifest when the connection is wired. Indeed, the normal "monitor with a cable" icon is being shown.

…

-------- Ursprüngliche Nachricht -------- Am 15.04.24 12:52 um undergroundwires schrieb :

Thank you for sharing insights ***@***.***(https://github.com/mshpp), did Disable active probing to Microsoft NCSI server resolve the issue for you? Or do you mean something else as NCSI service? I will update the docs, and adjust recommendations based on your feedback. Was this this script in particular, causing the issue: :: ---------------------------------------------------------- :: -Disable active probing to Microsoft NCSI server (revert)- :: ---------------------------------------------------------- echo --- Disable active probing to Microsoft NCSI server (revert) reg add " HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet " /v " EnableActiveProbing " /t REG_DWORD /d " 1 " /f :: ---------------------------------------------------------- — Reply to this email directly, [view it on GitHub](#216 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AKRY2ZELEE7FWR24E5M3SN3Y5OWPZAVCNFSM6AAAAAAWQLJLSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJWGUZTSNZWHA). You are receiving this because you were mentioned.Message ID: ***@***.***>

[undergroundwires]

Thank you, I will update the dosc with your findings and remove this script from Strict so it will no longer be recommended.

I found this article shared once by Microsoft.

It contacts www.msftncsi.com frequently, which still is a privacy issue:

IIS logs are stored on the server at www.msftncsi.com. These logs contain the time of each access and the IP address recorded for that access. These IP addresses are not used to identify users, and in many cases, they are the address of a network address translation (NAT) computer or proxy server, not a specific client behind that NAT computer or proxy server.
Microsoft

I see that it may even break captive portals.

In future, to both reach privacy and functionality, the safer way would be to change the NCSI server to somewhere audited and "trusted".