>

Disable or enable IPv6 on a network adapter

Toggle the ms_tcpip6 binding per adapter with Disable-NetAdapterBinding / Enable-NetAdapterBinding.

Windowsadapteripv6powershellMedium risk
Run `Disable-NetAdapterBinding -Name "适配器名" -ComponentID ms_tcpip6` as administrator to switch IPv6 off for that adapter.

01Command

Command
$ Disable-NetAdapterBinding -Name "以太网" -ComponentID ms_tcpip6

02What it does

IPv6 is a protocol binding on each network adapter, and disabling it is the standard fix for issues such as slow browsing, VPN conflicts or apps that prefer a broken IPv6 route. `Get-NetAdapterBinding -ComponentID ms_tcpip6` first shows which adapters currently have IPv6 enabled, and the name must match the adapter name exactly. Only the chosen adapter is affected; other adapters keep IPv6.

03Risk

RiskMedium risk
RequirementsAdministrator terminal required. Adapter name must match `Get-NetAdapter` output.
!Warning: Microsoft recommends leaving IPv6 on unless you have a specific problem. Re-enable it afterwards with Enable-NetAdapterBinding.

04Undo

Undo
$ Enable-NetAdapterBinding -Name "以太网" -ComponentID ms_tcpip6

05Sources

  • Disable-NetAdapterBinding
    Microsoft Learn · vendor-doc · 2026-09-17
    Evidence: Disables a binding on an adapter; ComponentID ms_tcpip6 targets the IPv6 protocol binding.
  • Get-NetAdapter
    Microsoft Learn · vendor-doc · 2026-09-17
    Evidence: Returns adapter objects with Status, LinkSpeed and MacAddress properties.

Last verified: 2026-09-18 · Category: Network

06Related solutions

Grep on Windows: Select-String
Windowssearchtextpowershell

Search inside text files and logs with regex, returning file, line number and match.

Low risk ✓ 2026-09-17
Zip Files with Compress-Archive
WindowsZip & Archivesarchivepowershell

Create or update a .zip from any files or folder contents straight from PowerShell.

Low risk ✓ 2026-09-17
Test a TCP port connection on Windows with Test-NetConnection
Windowsnetworktroubleshootingpowershell

A built-in PowerShell one-liner that answers 'is port 5432/3389/443 actually open through this network?' — no telnet client needed.

Low risk ✓ 2026-09-17