Ah stupid me! I went and paid for the upgrade and I could have fixed iMortaluz by adding drivers with my old laptop. I just now realized it. Oh well next time.
So, here's a million dollar question. What if one were to upgrade from W7 to W10 on machine A, then switch the hard drive to a new PC (machine B) and get re-activated by contacting Microsoft. Then, go back to Machine A, plug in a new HD and video card, and go through this process to upgrade to W10 all over again (although some of the hardware would be diff, the mobo & processor would be the same as the first time) - would one risk getting the same hardware ID a second time and causing problems with the activation that got switched over to the new machine (machine B)?
You could simply do it separately on both systems. Switching the hdd won't transfer the established HWID to the new system, it has to establish it's own.
Hmmm...yeah, that might be what I should have done. When I popped my existing hd into the new system, I had to call MS to have them "re" activate my W10. I wasn't sure if they had my old hardware ID in their system somewhere, tied to my new one, or something like that. Now, I want to sell my old mobo & processor...with w10 on it, naturally. So, I don't know if it's safe to perform this 'GenuineTicket.xml' method since I already went through the upgrade process once before...although I now have diff. hardware attached to the mobo...
Well, it's the same motherboard as when I did the original upgrade, but it's a different motherboard now that they "re"-activated my [original] activation, so I'm not sure if it's safe.....
sorry if this is a noob question. I have been reading through this thread to find the answer and am still a little unclear. Will this method work using windows 10 enterprise, using the original posted steps starting from a windows 7 pro? thank you
Quick question. I just failed many times at this... the copies of Windows that I used are: 
Windows 7 Professional 64Bit: X17-59186.iso from DigitalRiver. en_windows_10_multiple_editions_version_1607_updated_jan_2017_x64_dvd_9714399.iso from MSDN. I install only the same Pro 64 bit edition from both, and do all the steps as described. Is my problem that maybe my copy of Windows 10 might be a VL? I doubt it, because it still asks for a key after installation. Any tips?
Was your Win 7 Pro install activated by daz, legit key or slic before you generated the genuineticket.xml? Your copy of the windows 10 iso is MSDN = OEMRET, not VLSC = VL.
Yes, it was activated by DAZ, and also validated online before I generated the ticket, just in case. I think maybe I didn't run the ticket generator as administrator? Am trying again, will post results.
Interesting phenomenon. Fresh Win 10 install on a machine that never saw the system before. As expected my Win 8/8.1 RTM keys are rejected. After uninstalling the default key and entering an ancient and blocked Win 10 MAK and opening the Windows Key Prompt via 'slui 3' my Win 8 key was accepted and Windows showed a 'Digital License used' in Settings. Key is shown as the usual 3V66T one .
Method still works Test: Toshiba Satellite C50-B-138 Win 7 SP1 Ultimate (SLiC2.1) > Win 10 Pro (oemm for 8.1 Core/10 Home) Used ei.cfg for clean install 10 Pro: Code: [Channel] _Default [VL] 0
For some reason it's no longer working for me, at least with the computer I'm testing. It has a MSI Z68MA-ED55 motherboard and a 1TB HDD, here's what I did: - wiped hdd, installed Windows 7 SP1 Pro x64 (MBR) - activated it with Windows Loader 2.2.1 (bios didn't have SLIC), tried Asus and MSI - created GenuineTicket - wiped hdd, installed Windows 10 Pro x64 without a key (tried MBR and UEFI) - added GenuineTicket, rebooted, connected LAN cable - 0x803F7001, it can't activate because it doesn't have a valid digital license or a valid product key... I also flashed the BIOS with a DELL SLIC 2.2 modded one, activated Windows 7 with a DELL SLIC 2.1 certificate + Pro key (the same I've always used and worked before), repeated all the steps and still got the 0x803F7001 error. I successfully upgraded a laptop with this method earlier this week, so did M$ stop accepting it or is it just not working with this motherboard?
I always do it with Ultimate and Loader v2.2.2 (shouldn't be of any difference but it never failed me).
Nevermind, used MS Toolkit to activate it. I believe the owner once tried to upgrade to 10 with the "traditional" method and also failed, so the problem must be with the motherboard itself. Anyway it's out of my hands now