Getting Question Marks Whenever I Try to Set Netsh Interface Names in CMD on Windows 10

Getting Question Marks Whenever Try Set Netsh Interface Names in CMD on Windows 10

If you are running Windows 10 on a TOSHIBA work computer and trying to manually set a specific MTU for your Wi-Fi, you may encounter an issue where you see question marks instead of the interface names when running the netsh int ipv4 set subinterface "Wi-Fi" mtu=1480 store=persist command in the Command Prompt (CMD). This article will provide a detailed explanation of this issue and offer potential solutions.

Understanding the Issue

The issue arises due to the way Windows 10 handles interface names, particularly when there are multiple network adapters present. When you run the netsh int ipv4 show interfaces command, you may notice that the Wi-Fi interface is listed as "Wi-Fi 2" or "Wi-Fi 3" instead of simply "Wi-Fi". This naming inconsistency can cause problems when trying to set specific MTU values for the Wi-Fi interface.

Potential Solutions

There are a few potential solutions to this issue:

1. Use the Index Number: Instead of using the interface name, you can use the index number associated with the Wi-Fi interface. To find the index number, run the netsh int ipv4 show interfaces command and look for the number in the "Idx" column next to the Wi-Fi interface. You can then use this number in the netsh int ipv4 set subinterface command, like so: netsh int ipv4 set subinterface 11 mtu=1480 store=persist
2. Rename the Interface: You can rename the Wi-Fi interface to a more consistent name using the netsh interface set interface name="Current Name" newname="New Name" command. For example, you could rename "Wi-Fi 2" to just "Wi-Fi". However, this change may not persist across reboots, so you may need to run this command each time you start your computer.
3. Use PowerShell: Instead of using CMD, you can use PowerShell to set the MTU value for the Wi-Fi interface. The syntax is slightly different, but the basic idea is the same. Here's an example: Set-NetIPInterface -InterfaceAlias "Wi-Fi" -MTU 1480

Getting question marks instead of interface names when running the netsh int ipv4 set subinterface command in CMD on Windows 10 can be frustrating, but there are a few potential solutions. By using the index number, renaming the interface, or using PowerShell, you can set the MTU value for your Wi-Fi interface and avoid this issue in the future.

References

• Microsoft Docs: Netsh Interface IP
• TechNet Forums: Netsh Interface IP Set Subinterface Wi-Fi MTU
• Super User: Netsh Interface IP Set Subinterface Command Not Working on Windows 10