This issue occurs because Remote Desktop Protocol (RDP) does not transmit the local Wi-Fi network list to the remote session's login screen. The authentication interface runs in a secure desktop environment that is isolated from the host’s active network discovery services, making local wireless networks invisible during the credential entry phase.
Understanding the Architecture of RDP Login
When you initiate an RDP connection to a Windows 11 machine, your client establishes a tunnel to the host. However, the login screen you see is rendered by the host operating system, not your local client. This screen operates within the "Secure Attention Key" (SAK) desktop, a protected layer designed to prevent keyloggers or malware from capturing credentials entered on the screen.
Because this desktop is isolated for security reasons, it does not have access to the same network stack visibility as the standard user session. Specifically, the Wi-Fi adapter’s driver and the Network List Service are often suspended or restricted in their ability to broadcast available networks to this isolated context. Consequently, when you attempt to connect via Wi-Fi credentials on the login screen, the system cannot populate the list of available SSIDs.
This behavior is intentional by Microsoft to maintain the integrity of the authentication process. It ensures that the login screen remains lightweight and secure, avoiding potential latency or security vulnerabilities that could arise from full network enumeration in a pre-authentication state.
Primary Solution: Use Wired Connection for Initial Setup
The most reliable workaround is to ensure the target Windows 11 computer is connected to the network via an Ethernet cable during the initial setup or if you need to log in remotely without prior Wi-Fi configuration. A wired connection provides a stable IP address and does not rely on the dynamic scanning of wireless networks that fails in the RDP context.
If you are currently locked out or setting up a new machine, plug in an Ethernet cable. Once logged into the main Windows session, you can configure the Wi-Fi settings normally. After the Wi-Fi profile is established, you may disconnect the Ethernet cable if desired, though keeping it connected for critical administrative tasks is recommended.
For users who frequently need remote access, consider configuring static IP addresses on your router for the target machine. This eliminates the need to constantly re-associate with different networks and reduces the dependency on the login screen’s network visibility.
Connecting Internet to VM outlines similar principles regarding network stability and IP assignment, which are relevant when managing remote connectivity reliability.
Alternative Workaround: Enable Fast Startup and Power Settings
In some cases, aggressive power-saving features can exacerbate the issue by fully disabling the Wi-Fi radio when the system enters sleep or hibernation modes. If the Wi-Fi adapter is powered down completely, it will not be visible even after waking, and certainly not on the login screen.
To mitigate this, navigate to Control Panel > Hardware and Sound > Power Options. Select Change plan settings for your active power plan, then click Change advanced power settings. Expand the Wireless Adapter Settings section and ensure both On Battery and Plugged In are set to Maximum Performance.
Additionally, disable Fast Startup in Windows 11. Go to Control Panel > Power Options > Choose what the power buttons do. Click Change settings that are currently unavailable, then uncheck Turn on fast startup. This forces a full driver initialization upon boot, which can sometimes resolve hardware detection issues on the secure desktop.
Network Profile Configuration
Ensure that your Wi-Fi network is classified as a Private network rather than Public. Public networks restrict discovery and sharing features, which might interfere with how the system advertises availability in certain contexts.
Right-click the Start button and select Network Connections. Click on your Wi-Fi adapter properties and ensure the network category is set to Private. This allows the system to trust the network identity, potentially improving how the OS handles network resources during the pre-login phase.
Enable WIN10/11 LAN File Sharing discusses network trust levels and their impact on system behavior, providing broader context on how Windows manages network profiles.
Using SSH or Alternative Protocols
If RDP continues to present challenges, consider enabling SSH access as an alternative method for initial login or troubleshooting. SSH operates at a lower level and does not require the graphical login screen’s network visibility.
You can enable OpenSSH Server via PowerShell using
Install-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0. Once enabled, start the service with
Start-Service sshd. This allows you to execute commands and verify network status without relying on the graphical interface.
Windows Computer: Gaining SSH Access Outside Local Network Using PowerShell provides detailed steps for configuring external access, which can serve as a robust fallback when RDP limitations hinder connectivity.
Frequently Asked Questions
Can I see Wi-Fi networks on the login screen if I am already logged in?
No, once you are logged into the main session, the Wi-Fi icon appears in the taskbar, but the login screen itself remains isolated. The isolation persists until a user successfully authenticates and the Secure Desktop is dismissed.
Does updating network drivers fix this issue?
Updating drivers rarely fixes this specific problem because it is a design limitation of the RDP protocol and Windows security architecture, not a driver bug. However, keeping drivers updated ensures general network stability once you are logged in.
Is there a registry hack to force Wi-Fi visibility on the login screen?
There is no supported registry key to expose Wi-Fi networks on the RDP login screen. Attempting to modify system files to bypass the Secure Desktop can compromise system security and stability.
Why does Ethernet work but Wi-Fi does not on the login screen?
Ethernet connections are typically detected as physical link-layer events that do not require the same dynamic scanning process as Wi-Fi. The wired connection is established at the hardware level before the OS fully initializes network discovery services.
Should I use a different remote access tool like TeamViewer?
Third-party tools like TeamViewer may handle network selection differently, but they still face the same underlying Windows security restrictions on the login screen. They cannot bypass the Secure Desktop’s inability to query Wi-Fi adapters directly.