So... that would theorically confirm MS KNOWS about Daz Loader and how it works... Still, they didnt block upgrading from an OEM system... The naive one is me I should guess...
See folks, we just mention the idea, and they gotta come out and say something. So lonely these MS spy's lives are
Hi All, Forgive me if I misunderstand or have a unclear question. I read in the first post as follows. @ mtrai 1. Can I do a clean install: Yes but you have to upgrade first then you can do a clean ISO install. My question is that I've upgraded Windows 10 Pro from Windows 8.1 Pro activated. After upgrading my pc is activated automatically. Now I would like to install a clean Windows 10 Pro ISO only. Do I have to activate Windows 10 Pro again with Windows 10 key or It will automatically activate after clean installation ? Thanks a lot for your explanations in advanced.
While doing a clean installation of Windows 10 Pro, simply hit skip when prompted to enter product key. And, yes, the clean install of Windows 10 Pro would activate itself once you are online again.
I have used Daz on a couple of my computers from 7 and upgraded to 10 with no problems , and a friends computer was done the same with 7 Ultimate , but with a hitch when he upgraded to 10 from 7 it cancelled his up and said he had a Non genuine copy of Windows and it removed his genuine water mark on windows 7 Cheers
Before, I have dual-boot Windows 10 Pro and Windows 10 Enterprise LTSB on C and D drives respectively (original graphical boot menu options working as normal). Currently I had a clean installation of Windows 10 Education on Drive C but now I lose graphical boot menu options (only legacy boot menu options available). How to get back the graphical boot menu options? I have tried several methods by Googling but no luck. Thanks
Also, when in Windows 10 EDU, run bcdedit /set {current} description "Windows 10 Education" bcdedit /set {d2c00310-461a-11e5-835f-e21ddc2541de} description "Windows 10 Enterprise LTSB" EDIT: Okay, looking back, GUID in the second command should be that of the other OS entry, that might not be {d2c00310-461a-11e5-835f-e21ddc2541de}, something that I just presumed. Correction: It should have been bcdedit not bootmgr. Sorry.
But like in SS for first. I am on Windows 10 Eduation (bootmgr /set {current} description "Windows 10 Education")