Windows 10: HYPER

Hello,

I am trying to use HYPEr (not Hyper-V) for a course that I am enrolled in and on W10 it comes up as the WIN 10 command prompt and that's where it stays. does Microsoft not use Hyper anymore?

comes up as:

C:\WINDOWS\system32\cmd.exe


Microsoft Windows [Version 10.0.18362.418]

(c) 2019 Microsoft Corporation. All rights reserved.


C:\users\rondo>


This looks like the dos command prompt to me


Any suggestions?


Cheers

Ron Doran

:)

 

Even after Uninstalling Hyper-V - msinfo32 shows "A hypervisor has been detected"

Hi,

To address your concern, we suggest that you disable the Hyper V services. Kindly follow the steps below:

• Type Services on the search bar.
• Right click one Hyper V service, then select Properties.
• On Startup type, choose Disabled.
  
  
• You have to disable all the Hyper V services one at a time by following the same steps.

If the issue persists, we suggest that you check out your post on TechNet (IT Pro’s) to make sure you get better answer.



Let us know if you need further assistance.

 

Moving Hyper-V to Another Disk

1. Export the virtual machines to the drive where you want to move them (tutorial).
2. When all VMs have been exported, delete them in Hyper-V Manager.
3. When Hyper-V Manager is empty, not showing any VMs, import the previously exported VMs (tutorial). In Option One Step 6 of the tutorial, you need to select Register the virtual machine in-place, or if choosing Option Two in tutorial, select Step 2.

Easy!

 

Where is the Hyper V Manager, How to I start it ?

I am trying to setup an XP virtual Machine on Windows 10 Pro.

I followed the steps in Neil Peterson article of 5/9/2016.

System Requirements - done - ok

Install Hyper-V - done - ok

Create a Virtual Switch - skip

Create a Virtual Machine

Create a Virtual Machine with Hyper-V Manager

These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.

• 
  In Hyper-V Manager, click Action > New >
  Virtual Machine to bring up the New
  

Uhhhhhhhhh - this step obviously implies one knows

1) Where the Hyper-V Manager is

2) How to start the Hyper-V Manager

Isn't that odd ?