How to Check Network Adapter Status with PowerShell in Windows 11
Checking the status of your network adapters shows which are connected, disabled, or disconnected, useful for troubleshooting connectivity. PowerShell gives a clear overview of every network interface and TANGKAS39 its current state in Windows 11.
The Command
Get-NetAdapterWhat It Does
`Get-NetAdapter` lists your network interfaces with their name, status, link speed, and type. The Status column shows whether each adapter is Up (active), Disabled, or Disconnected. This lets you quickly see which connections are working, making it a good starting point when a network connection is not behaving as expected.
When You’d Use This
This is a good starting point when troubleshooting connectivity, since it shows at a glance which network interfaces are active, disconnected, or disabled. Before diving into address or DNS details, confirming that your adapter is actually up and connected rules out the simplest causes, such as an Ethernet cable not plugged in or Wi-Fi not joined to a network.
Useful Variations
To see only a specific adapter, add its name: `Get-NetAdapter -Name “Wi-Fi”`. To view more detail, pipe to `Format-List *` for all properties. To check just the status column, use `Get-NetAdapter | Select-Object Name, Status`. These focus the output on exactly the adapter or details you need.
If It Doesn’t Work
If your adapter shows Disconnected, check the physical connection for Ethernet or that Wi-Fi is joined to a network. A Disabled status means the adapter was turned off, so enable it with `Enable-NetAdapter`. If the adapter does not appear at all, a driver issue may be preventing Windows from recognizing it, which you would investigate in Device Manager or by reinstalling the network driver.
Good to Know
An adapter showing Disconnected has no active link, such as an Ethernet port with no cable or Wi-Fi not joined to a network, while Disabled means it has been turned off in settings. Identifying an adapter’s exact state helps direct troubleshooting toward the right cause, whether a physical connection or a configuration setting.
Putting It Together
Once you have run it once or twice, this becomes second nature. As part of diagnosing and configuring your connection, this command belongs in your toolkit for whenever the network acts up. Used alongside the other networking commands here, it helps you methodically work from confirming basic connectivity to pinpointing exactly where a problem lies. Like anything in the terminal, the real value comes from trying it on your own system and adapting the variations above to what you actually need, so it is worth experimenting with in a safe, low-stakes situation before relying on it in a script or during troubleshooting. Keeping a note of the commands you find most useful, along with the variations that fit your workflow, turns scattered one-off tricks into a personal reference you can draw on whenever a similar task comes up again.