Recommended Posts

How would I get a Windows 8 license for a virtual machine? Do I really need to spend $300 - $500 to get it (Windows 7 THEN Windows 8 Pro)?

NOTE: I do not want to do any hacks, tweaks, or anything like that. What is the appropriate way to get a brand new Windows 8 license? I have to buy Windows 7 first?

Link to comment
https://www.neowin.net/forum/topic/1146908-windows-8-for-a-virtual-machine/
Share on other sites

You can't do it legally anymore..

I'd just suggest you have a license for the install and install it..

Here is a pretty good overview of the new licensing.

http://www.picacommu...hanges1208.html

**** me Microsoft are becoming evil..

EDIT::

After further thought I'd interpret this as meaning you cannot move the VM. You can install it onto a machine in a VM, but not move it to another device :\

Either way, epicly scumbaggy..

use an OEM disk, the licensing has been changed with windows 8 so this works similarly to the way the old Retail version worked

http://www.amazon.com/Windows-System-Builder-OEM-64-Bit/dp/B0094NY3R0/ref=sr_1_1?ie=UTF8&qid=1365865834&sr=8-1&keywords=windows+8

Buy it online (http://windows.micro...ShopHP_FPP_Null) or buy it at retail. The same way you would buy a Windows 7 license.

I thought those were only upgrades? I did buy it online for my main OS. It needed Windows 7 or something else installed or it would not work.

So the only way to get a fresh copy for a virtual machine is to buy an OEM license? What happens if I need to reinstall the Virtual Machine or use a different VM software? How does that work with the Windows Activation with OEM licensing (since it is no transferrable)?

I thought those were only upgrades? I did buy it online for my main OS. It needed Windows 7 or something else installed or it would not work.

So the only way to get a fresh copy for a virtual machine is to buy an OEM license? I thought OEM licenses were ONLY for system builders?

that's how they were in the past, but with 8 the license for them has changed to basically take the place of the normal retail copy

System builder as defined by Microsoft is literally anyone who uses a machine.

You take on all requirements for support of the operating system in using it (no ringing MS for help).

You need an existing NTFS partition on the drive to install it. After that you can.

System builder as defined by Microsoft is literally anyone who uses a machine.

You take on all requirements for support of the operating system in using it (no ringing MS for help).

You need an existing NTFS partition on the drive to install it. After that you can.

How would it work with a virtual machine if I need to reinstall it, or change the VM software to something else? Since OEM licenses are non-transferrable, how would that work during windows activation?

How would it work with a virtual machine if I need to reinstall it, or change the VM software to something else? Since OEM licenses are non-transferrable, how would that work during windows activation?

that's the main thing that changed in the license for 8, the OEM system builder license actually is transferable now

Legally it doesn't..

All you can do is try your best to keep to the spirit of the terms of use. Just install to a VM. When you need to reinstall, just reinstall into the VM. It should work?

I know a couple of people have been using 8 in a VM. I suspect they are just ignoring the legality of it all (which I think you should do also >.<)

Well, if you consider you can't move the VM, I don't think you breach the license..

All I can suggest is ringing Microsoft on that note.

OEM 8 copy is still the best answer if 7 isn't a good answer >.<

I do not know much about VMs. I need to use it for testing purposes. What if (just for example) I use VMWare and decide to switch to Parallels or something? Will it consider that a different hardware setup with the way they operate?

Or if I want to move it to my mac laptop vs my windows desktop. How will that work?

I'd just do it. Microsoft won't give a damn whatsoever.

The internal policy (when I worked for them) was that so long as you bought a license, we don't care. That having been said, I can't speak for Microsoft even if they still employed me.

Just do it >.< (Sorry for bringing up the licensing (feeling like a dick for making this overly complex))

You're allowed to transfer the System Builder software if you buy it with the "Personal Use License". I'm not sure if you'd have to contact Microsoft to explain what you're doing, but the right is granted just as with a full Windows 7 license.

http://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/personal-use-license.aspx#fbid=FawIJ6YfbQM

http://personaluselicense.windows.com/en-US/default.aspx

If you're purpose in installing Windows 8 is to test it, you might want to use the free 90-day evaluation copy.

http://technet.microsoft.com/en-us/evalcenter/hh699156.aspx

You can't do it legally anymore..

I'd just suggest you have a license for the install and install it..

Here is a pretty good overview of the new licensing.

http://www.picacommu...hanges1208.html

**** me Microsoft are becoming evil..

EDIT::

After further thought I'd interpret this as meaning you cannot move the VM. You can install it onto a machine in a VM, but not move it to another device :\

Either way, epicly scumbaggy..

Actually, once you license a VM, you can move it; however, you cannot have two copies of the same VM running at once. In that sense, it is no different from a license for a physical PC.

You have two choices - you can start with a legally-licensed Windows 7 VM and upgrade it (same process as upgrading a physical PC) or buy Windows 8 OEM and license the VM that way.

This is, in fact, per the most recent Microsoft post on the Unified Licensing Schema.

Actually, once you license a VM, you can move it; however, you cannot have two copies of the same VM running at once. In that sense, it is no different from a license for a physical PC.

You have two choices - you can start with a legally-licensed Windows 7 VM and upgrade it (same process as upgrading a physical PC) or buy Windows 8 OEM and license the VM that way.

This is, in fact, per the most recent Microsoft post on the Unified Licensing Schema.

And the same goes for when I get my Macbook pro? I can use the OEM version and it will be legal?

  • 4 weeks later...
This topic is now closed to further replies.
  • Posts

    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
    • Normally, I admit when a title is clickbait (unfortunately, it's become somewhat necessary to compete against AI-dominated news sections today), but in this case, all supported versions is implied and doesn't need to be spelled out in the title. Of course, I'm covering a Patch Tuesday update bug that is only available to supported Windows SKUs. All our coverage relates to supported Windows software and SKUs only unless we expressly state that it's "unsupported", "unofficial", or "third-party". I'm sorry, but supported/official SKUs don't need to be spelled out as such in every Neowin headline.
    • ALL versions or ALL SUPPORTED versions? Neowin does it again.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      595
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!