Windows 10: Windows 10 dev environment on Hyper-v

Hi, I am trying to install Windows 10 developer environment on virtual machine using Hyper-v quick create tool. As the tool already offers the Windows 10 developer environment.

My question is the environment only available for a limited period of time? The only relevant link I found is on this link: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines

which says that it's only available until 24th December 2018. Does anyone knows if the hyper-v installation has the same license or is it free on virtual machines?

Thanks

:)

 

How to enable Hyper V windows 10

fwiw;

Operating System Requirements

The Hyper-V
role can be enabled on these versions of Windows 10:

• Windows 10 Enterprise
• Windows 10 Professional
• Windows 10 Education

The Hyper-V role cannot be installed on:

• Windows 10 Home
• Windows 10 Mobile
• Windows 10 Mobile Enterprise

 

Hyper V deativication

Hi Geoffrey,

Hyper-V lets you run an operating system or computer system as a virtual machine on Windows. Before proceeding in disabling
Hyper-V, please create a backup of your files for security purposes.

To disable Hyper-V, please follow the steps below:

• On the Cortana search box, type Turn Windows Features on or off and press
  Enter.
• Look for the Hyper-V folder.
• Uncheck the tick-box next to the main Hyper-V folder and click
  OK.
• Restart your PC.

Should you have further questions, please let us know.

 

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 ?