Yes, that's what the license says.
In practice, what corporate VM users do is get MSDN licenses, which are assigned to the developer. I have one. It's basically a license to not worry about licensing: I can run as many copies of whatever I like, so long as it's "for testing and development purposes". I think there's a different volume licensing programme available if, god help you, you wanted to run a production datacentre on Windows.
Edit: this is obviously a big reason why Windows is never going anywhere in the cloud space outside of Azure.
The cheapest MSDN subscription (OS-only) is $699/yr. For that price I could buy about 6 copies of Windows 10 Home edition. Or 2 new laptops each with a Windows license included. Sheesh.
Generally if you have an MSDN subscription, you're using it for other products like Visual Studio, and the free copies of Windows are just for helping you get a development environment set up.
Use with Virtualization Technologies. Instead of using the software directly on the licensed
computer, you may install and use the software within only one virtual (or otherwise emulated)
hardware system on the licensed computer.That is indeed the case. Otherwise you can buy licenses meant for ISPs and cloud-hosting providers. Your "personal use of multiple VMs" is simply not contemplated. You could probably get by with a MSDN subscription, which gives you some leeway.
Edit: sounds like pretty much whatever you want.
http://stackoverflow.com/questions/584162/what-is-the-window...
http://www.itassetmanagement.net/2011/05/31/msdn-subscriptio... : there is a lot of fractal madness in this. "This applies to virtual machines as well – so if even one application on one virtual machine hosted on a physical server is used for production purposes, then ALL the virtual machines AND the physical host must be licensed as if they were production machines."
"Training is NOT considered a development activity, so all those being trained and the machines used for the training must be licensed appropriately." may be one of the reasons nobody ever gets any training in this business.
If you're using it rarely, why not use the trial version, and reset to a snapshot whenever you use it? You can save data on a separate virtual disk, and only reset the operating system disk.
There used to be VMs at https://dev.modern.ie/tools/vms/. I don't see Windows 10 there right now, not sure why, but I know I've downloaded from there before; maybe wait a few weeks or so.
Besides, I think you can "rearm" and use for another 90 days or more.
The question is what happens if you have two VMs with identical hardware where you only ever have one active? Microsofts licensing probably doesn't consider this scenario, so I think it would be a matter of interpretation. In theory you could transfer the license back and forth between the VMs (assuming that stopping and unmounting the inactive VM disk counts as "removing the software" from that machine).
I can't technically guarantee that my system hasn't been duplicated (say, by the NSA), but that isn't my responsibility. I'm just not supposed to run two copies simultaneously.
I only run it when I need it, in my case cost is negligible (in the $1/month range, Windows license inclided), launches a lot faster than VMware Fusion and best of all, my Mac is not slowed down considerably by VMWare Fusion VM image running.
Suggestions on VM software? I'm looking into getting my wife set up with Win10 on her Mac.
I'll probably, eventually be using a pirate copy of W10 in a VM as well, despite being entitled to run a copy natively.
I never run Windows on bare metal. I only run Windows on virtual machines on my Mac desktop and Mac laptop; only for personal use; and only on the rare occasion when I need to run the odd Windows-only application.
I would like to go legit this time around, but it's nigh-impossible to find any specific documentation from Microsoft which states, in plain, simple English, how I would go about getting the proper license to cover my use case. I find this hard to believe as it's 2015 and certainly there must be countless others who do the same as I (and at least a few of them here on HN).
The only official Microsoft document I can find about Windows licensing and virtual machines pertains specifically to business use, and appears to be focused on running Windows in a "Virtual Desktop Infrastructure" (VDI) environment, so I don't believe it applies to me. (I confess I did not read the entire document as it contains so much unfamiliar jargon that I have a hard time parsing it past page one.)
Anyway, from what I can tell by gathering bits and pieces posted on various forums by Microsoft community reps or third-party Microsoft "solution providers," Microsoft expects me to buy a separate, full Windows license for each virtual machine I create, for each host machine I run it on (i.e., M * N licenses).
Can anybody here tell me whether that's correct? Because if that's correct, Microsoft can go fly a kite.