[http://dev.modern.ie/tools/vms/windows/]
Chris & I have talked about VMs in the past... You install the VM Host software, then add VMs to it. A VM is a copy of Windows installed to a Virtual Hard Disk [VHD], which is a single file that your installed copy of Windows treats as if it was a real, physical hard drive. The VM Host software pretends to be a PC, emulating the PC's hardware in software. The end effect is that you have a copy of Windows [or another OS like Linux] running in a window or full screen.
Normally you set up a VM by creating a new VM in the host software, then installing Windows the same way you would to your PC or laptop. The Microsoft VMs are a larger download, but take all the work out of it. You don't have to worry about any settings, nor do you have to install Windows in the new VM -- with VirtualBox host software installed, you un-zip the download, them import the .ova file you get, wait a couple of minutes for the process to complete, & you're done.
Microsoft's VMs are 90 day trials -- they tell you several times [even on the initial desktop wallpaper] to create a snapshot or save your original download, so that after the 90 day expiration you can start over.
Besides being a great test environment, where your regular copy of Windows remains untouched, a VM lets you do stuff like run software that won't run on your version of Windows, or run software like some games in a window where otherwise you could not. It's also a fairly painless way to get a look at Windows 10.
Myself, I copy the virtual hard disk where a VM's installed somewhere else as a backup. If I check out an app that messes up Windows, or if I've installed several & want to go back to before I installed them, I copy that copy over the original, replacing it, & I'm back where I started.
Today when I checked, VMs were available from XP through 10. The 10 download was ~5GB, & the same for the unzipped .ova file -- importing that into V/Box created a virtual hard disk that was ~10GB.