I made a ISO from the upgrade on one PC and when I tried using it on a Different PC it asked for a activation Key during install? The default Key wouldn't work. Neither did the one You posted in another thread. I tried some Generic Win 8.* install Keys that didn't work either, but I'm not sure if I was using the right Version Keys.
Odd, I've made several ISOs already as well of TP but none have requested a key during install. Although I was worried that it might, but it didn't. Do you have ei.cfg in there or anything different?
I just tried making it from the esd that I downloaded on my Homebuilt just like the instructions said, then tried to install it on a mostly stock HP. I'm a Techie "Hardware" type person so most of what's posted on MDL is far above the little Geek Skills I have.
If the ISO is 'clean', there's no need to an P-Key for installation. Also the activation normally is done automatically. While using the Enterprise of the TP and like to create an Windows to Go external Drive, manuell activation is required after the install. Although, it's not possible to doing an update to an later build of an USB Windows to Go drive. Maybe that will be possible in Final but yet!
Might apply for the 9840 build ISOs MS offered (those contain pid.txt), but when using a self created build 9860 ISO it needs the key during install (exception would be option 3 in abbodis script which creates an ei.cfg file).
I used option 4. So I can try 3 and see if that'll work? I'm always willing to learn what I can understand. Sometimes that's not much
Afaik the Upgrade Process offers the option to create an ISO with install.esd. Not sure if they have an ei.cfg, without they won't accept generic keys. Abbodis script adds an ei.cfg for that reason.
Hmm... I don't believe that's correct. These 9860 esd files have a pid.txt Perhaps there is some upgrade method that I'm not aware of? I, admittedly, haven't done the win7-to-TP upgrade thing that faikee was talking about.
Ahh, didn't know they have pid.txt. In the Repo abbodi mentions that ISOs with install.esd generally don't accept generic keys, so they need ei.cfg.
Yes, 9860 build also have pid.txt file (originally included in esd "iso layout" index, not manually added) not sure if pid.txt get accepted when used with install.esd (option 3)
Short test with Win TP 9860 ISO with install.esd (no ei.cfg present): with pid.txt >> no key prompt, starts to install without pid.txt >> key prompt accepted the generic key and starts install
I talked about the original ISO from MS and not an home brew ISO, which an self created one from and ESD file seems to be.
Well I took the ESD - converted to install.wim made the USB iso, and a PID was included - I have upgrade installed 9860 and clean installed 9860 and never needed a key. and the DL from M$ which is in the ~BT sources has a pid.txt also... Original ISO from M$ insider v9841 has a pid.txt and if you upgrade the ~BT has a pid.txt
"Well I took the ESD - converted to install.wim made the USB iso, and a PID was included" For me too.