#Windows 8.1 pro team os license install

Windows 8вЂ™s license changes were widely reported on at the time. вЂњWith the Personal Use License, end users can buy an OEM System Builder License and use it on a machine they self-build, or as an operating system installed on its own partition in a dual-boot configuration, or in a virtual machine.вЂќ Really, they were just undoing a ridiculous licensing change they made forВ Windows 7.ДЄs MicrosoftвЂ™s Windows 8 licensing guide puts it: This was good, because people were doing this anyway.

#Windows 8.1 pro team os license install

This means that you could purchase a Windows 8 System Builder license and install it on a new PC you were building. To fix it, they added a вЂњPersonal Use LicenseвЂќ allowance to the Windows 8 System Builder license. But Microsoft did licensing right with Windows 8 - they saw that the Windows 7 OEM System Builder licensing situation was crazy. Microsoft knows exactly how it got to that #1 position - because normal computer usersВ boughtВ it. Just look at the screenshot below - the Windows 7 Home Premium System Builder edition, which is вЂњintended for pre-installation on a new PC for resale,вЂќ is the #1 best selling operating system product on. Read вЂњ Is it OK to use OEM Windows on your own PC? DonвЂ™t ask MicrosoftвЂќ for more background. This problem was chronicled excellently by Ed Bott over at ZDNet in 2009. Normal people were no longer allowed to use it to build their own PCs, but Microsoft continued selling them like hotcakes to those same people. With Windows 7, Microsoft changed the popular System Builder/OEM license of Windows. In fact, there are legitimate drawbacks to this cheaper license - no support direct from Microsoft and the copy of Windows being tied to a single PC, for example. Prior to Windows 7, purchasing an OEM System Builder license for your own PC was perfectly fine.