Command "netsh lan show interfaces" and no interface

Question

_{Monday, May 23, 2016 2:15 PM}

Hello all,

On Windows 10 ENT, (build 10586.164), i need to configure a Wired profile

My problem is there is no interface to export a profile.

When i launch the command "netsh lan show interfaces", i receive the message :

There is no interfaces on the system.

What could i do for get a interface and use it for create profiles from netsh.

My computer is a VM on Hyper-V with no specific network issue (i can go online and on LAN).

Thanks for any idea !

All replies (7)

_{Wednesday, May 25, 2016 8:29 AM ✅Answered | 1 vote}

I tried to deploy W10 on a physical computer and the command is working :)

That's mean the problem is only with my Hyper V VM. Maybe because my network card is legacy on Hyper-V ?

Need to make others tries...

_{Monday, May 23, 2016 3:46 PM}

My bet it's a bug in Windows 10. Can you run the same on a Win 7 (VM) machine and test?

Best regards, George

_{Tuesday, May 24, 2016 8:27 AM}

Yes the same command works on W7 VM...

On W10, i'm using the "Command Prompt(admin)", so that's not a problem with the UAC.

_{Tuesday, May 24, 2016 8:32 AM}

Hi Pierre,

I test on my Windows 10 10586.318 VM, there is a screenshot, I suggest to update system to the latest version to see the result.

Regards

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected]

_{Tuesday, May 24, 2016 1:11 PM}

Thanks for your reply.

I just made the update build 318 but got the same issue :

There is no interface on the system

other idea ?

_{Tuesday, May 31, 2016 1:27 AM}

Yes, I agree with your idea, your Hyper-V virtual machine may exist network issue.

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected]

_{Tuesday, May 31, 2016 7:07 AM}

I tried to deploy W10 on a physical computer and the command is working :)

That's mean the problem is only with my Hyper V VM. Maybe because my network card is legacy on Hyper-V ?

Need to make others tries...

  Perhaps it is a legacy NIC problem, as you suggest. It works fine on my Win 10 guest with the standard synthetic NIC.

Bill