You should use that shortcut to open it.
This is what my shortcut says and I use it all the time for the Hyper-V Manager
%windir%\System32\mmc.exe "%windir%\System32\virtmgmt.msc"
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Running an activate version of Windows 10 Pro 64 bit (v1709 build: 16299.309)
A few weeks ago I tried to run a VM on Hyper-V which previously worked fine. I clicked start, type Hyper-V Manager, right click and choose run as Administrator (as I typically do). It then opens Microsoft Management Console which is not what I want.
When I look at the shortcut target it's pointing to: %windir%\System32\mmc.exe which doesn't seem right.
I've tried turning off and turning back on Hyper-V using Windows Features on/off.
I've confirmed Hyper-V Host Compute service is Running and Hyper-V Virtual Machine Management is running (which they are).
I run vmconnect.ext as admin it shows the VMs and tries to start them but I get errors about a virtual port. I can't fix that because I can't get into Hyper-v manager.
Been trying to get this to work for weeks and about to scrap it for VirtualBox.
Any suggestions?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
You should use that shortcut to open it.
This is what my shortcut says and I use it all the time for the Hyper-V Manager
%windir%\System32\mmc.exe "%windir%\System32\virtmgmt.msc"
Thanks. After I posted the question I put "%windir%\System32\virtmgmt.msc" in mine and it works but I'll add the mmc.exe in there as well.
Hey! Regarding your issue, what I had to do was open the shortcut you are using to open Hyper-V manager. Press rightclick and open its destination, right click the shortcut and press properties, and check that the destination is: " %windir%\System32\virtmgmt.msc " . At my computer it was changed to %windir%\System32\mms.msc. This is the wrong location for the console. By changing this everything should work as normal :)
You can also create a new shortcut to: " %windir%\System32\virtmgmt.msc " that will also work.
Hi Michael,
Regarding your issue with Hyper V, we highly recommend to post your issue in our TechNet forum. They are trained experts who cater this kind of scenario.
Feel free to post back if you have other concern.