I've never found it necessary to install anything other than network drivers on Win7 prior to running the gatherosstate.exe to generate the genuineticket. I've performed quite a few (>10) upgrades using this method. I certainly don't bother installing audio ,videoand chipset drivers - generic MS VGA and SATA drivers seem fine. Definitely no need to install all the windows updates. I appreciate other people may have had different experiences and require other drivers to be installed, but it hasn't been my experience.
I had generated GenuineTicket.xml on my Windows 7 Ultimate. But during partitioning part of the installation I chose to delete and reformat C:/ drive. Was that a mistake? Because I couldn't see C:/Program Data folder after installation finished? I also made a mistake when connecting the laptop to a wifi to setup Microsoft account. I will do a reinstall because I messed up the installation after installing GPU driver (I have one of those hybrid GPU notebook). I should have settled with drivers from Windows since it worked just fine. Btw, I got the home version. I read that we can add ei.cfg file to get option for pro version. There are different text people put on ei.cfg. Which one is suitable with the Redstone image?
if you made genuineticket for home. u cant just install pro.. wont activate. to see c:\programdata goto run and type it or explorer top address bar.
No, it can't, for 2 reasons: - The ticket is generated on non n windows - Enterprise n and non n are not included in the free upgrade offer (and doesn't use HWID/Digital License to activate)
Thanks, so does it means downloaded isos from technet are not retails but volume license? Or does it depends on how we activate them? Thanks. I can find it by typing manually. The license I made was from W7 Ultimate. It supposed to be be used on W10 Pro if I'm not mistaken. I tried and it doesn't work on Home version. Another thing, does the license XML file deleted after each restart?
TechNet? The TechNet software subscription service was retired on 31st August, 2013. Now untouched ISOs are sourced either from mSDN or VLSC. mSDN provides both retail & VL ISOs, whereas VLSC provides only VL ISOs.
1. I confirm that ( > 10 upgrades also ) no drivers are necessary just a network online ok . validation on ms site is not necessary also. 2. on new mainboards like a gigabyte with intel 110 series ( gen. 6th) you cannot install win7 will ask for drivers for chipset gigabyte has a solution for that I suppose will work for all manufacturers. 3. you can grab the ticket from a 32bit and will be ok to use it on a 10 64bit installation just match the version ( home/pro) c
on Win 8.1 pro - Cant we just activate win 8 via MS toolkit, upgrade windows 10 via Micrososft by using assistive upgrade explot and get a permanently activated copy of win 10 ?
Oh !! I wanted to upgrade my laptop original Win 10 home to Pro... was going to install Win 8.1, activate via KMS and upgrade to win 10 Pro. It wont work ? if I understood the 1st post correctly...
Since it comes to the win logo already it is highly likely no UEFI related matter. (it boots successfully past bootloader) I guess it is an unsupported driver issue since there are no working drivers for w7 available. W7 64 bit is UEFI compatible already. The right approach would be to go the other way around...install it as MBR legacy boot (Daz loader does not work in UEFI mode)...but I guess there is no option to boot it in legacy mode (CSM)? Also disable secure boot either way... I am afraid without the right w7 compatible drivers for your device you cannot install w7 on it...
Search for this ghost sysprep image : Spoiler GHOST WIN 7 32BIT 2015 TOMMY_PHAN.GHO MD5: 21A41EC2CD21D6159BB3E5DC302F8C6C SHA1: A6AF42621E9C0D6157FB5B231BCB8A55036657AF CRC32: 7F7E530D clone to your laptop's hdd and let it boot.... drivers will be automatically installed. You may then use DAZ loader to activate it and gatherosstate.exe to generate genuineticket.xml and finally upgrade to get permanently activated win 10 Pro ... Good Luck!
I had a lot of issues with different USB 3.0 flash drives plugged in a blue USB 3.0 port on different modern computers. [no boot] Problem solved instantly just by plugging USB 3.0 flash drive in a black USB 2.0 port on same computer. [boot OK] c
