Possible to run dual OS UEFI with Win10 activated + Win 10 trial ?

On a UEFI PC, do you know if it is possible to run dual boot with first OS being the PC's original activated Windows 10 and second OS being Windows 10 in trial mode ?

The issue is that the PC has a UEFI Bios which I am told automatically assigns a product key should windows 10 is installed on the machine. How do I make sure that this second Windows 10 trial does not pick up the product key from the UEFI bios and remains in trial mode, while the first Win 10 OS remains activated and functional ?

Not exactly sure why you would want to run a Windows 10 in notification mode (that's what non-activated "trial" is called). There are two ways to do what you want, though. Install a different version as the "trial" Windows 10 - if you have home installed and activated on your computer, then install the second copy and upgrade it to Pro using the Windows 10 Pro generic product key. If you already have Pro as the factory OS - then you would have to install Windows 10 as the second OS using the Windows 10 Home generic product key in a PID.txt file.

You could also run Windows 10 "trial" in a virtual machine.
Hyper-V virtualization - Setup and Use in Windows 10 - Windows 10 Forums

The generic product keys are:
Generic Windows 10 Home TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
Generic WIndows 10 Pro VK7JG-NPHTM-C97JM-9MPGT-3V66T

Also, I suppose if you have regular Windows 10 installed and activated, then you could install Windows 10 Single Language as the second "trial" Windows 10. Or vice versa.

cereberus said:

If you clean install windows 10 as a second dual boot option and pc has digital entitlement or windows 10 key is bios embedded (most situations), the second instance will activate automatically. It is hard NOT to activate this.

Stictly, this may be against EULA, but many do this to run the second instance as an Insider version (indeed MS support staff have even recommended that).

The only surefire way to run an unactivated version as NAVYLCDR says is to install it in a VM.

Why would you want to do this anyway?

Hi,

This Microsoft person is saying that the second Win 10 OS will not auto activate since there is already one activated Win 10 OS on the machine/bios.

http://answers.microsoft.com/en-us/w...=1452984265279

I will know soon.

I'm triple booting Builds 10240, 10586 and 11099 and they all auto activate regardless of how I install them.
You can only use one at a time anyway!

If you want the second install to be non-activated, uninstall the product key:
(don't know why you'd want to do that though)

https://www.tenforums.com/tutorials/3...dows-10-a.html

fixxinet said:

Hi,

This Microsoft person is saying that the second Win 10 OS will not auto activate since there is already one activated Win 10 OS on the machine/bios.

http://answers.microsoft.com/en-us/w...=1452984265279

I will know soon.

For crying out loud, the quality of MS support is terrible at times! Just complete garbage!

I checked the specific MS Support Engineer responded to that question and other answers by this Support Engineer in their forum.

This Support Engineer is a lightweight!

Provided you upgraded the machine in the proper manner, the machine receives 'Digital Entitlement' in the firmware.



You could run a hundred copies if you felt like it, it makes no difference, you can only use one at any given time anyway.
(Unless, of course, MS finds a way to revoke the Digital Entitlement per partition!)

In the end, you'll have one Windows in the system regardless.

Edwin said:

Provided you upgraded the machine in the proper manner, the machine receives 'Digital Entitlement' in the firmware.

Windows 10 - nor any previous version of Windows - has ever written any information to computer firmware. The digital entitlement is stored on Microsoft activation servers and is retrieved over the internet - not the computer's firmware.

NavyLCDR said:

Windows 10 - nor any previous version of Windows - has ever written any information to computer firmware. The digital entitlement is stored on Microsoft activation servers and is retrieved over the internet - not the computer's firmware.

Yes, sorry, the machine ID is linked to the DE in MS servers.