FirstLogon is way too far into the process for things like MultiOEM to have kicked in. Im trying to figure out why its only WMC that's doing it, wondering if theres a way I can get it to install without thinking theres a OEM key in it so it will install 'normally' and then have MOEM kick in for the activation during OOBE. I don't know much about the WMC side of it or how its created (still reading) but its all pointing to the post on TechNet. If it was only OOBE or only SeutopComplete that wasn't working then I could look in that direction but they work fine on all other indexes, same folder works on 7 & 10 as well. Im thinking it might be ei.cfg related? (just reading up on this now, never used it before) and saw it was Code: [EditionID] [Channel] OEM [VL] 0 which makes sense for the OEM side of it and this apparently stops the product key entry on the other indexes. Im gonna try this tomorrow see if it makes a difference: Code: [Channel] Retail [VL] 0 TLDR: Trying to get everything working, no product key prompt, MultiOEM and SetupComplete on all indexes. WMC being the only one that isn't playing ball.
Use the first one and your problems will be gone. Code: [EditionID] [Channel] OEM [VL] 0 I use to make flawless AIOs with these skus: Windows 8.1 Single Language with Bing Windows 8.1 Single Language Windows 8.1 with Bing Windows 8.1 Windows 8.1 Pro Windows 8.1 Pro with Media Center Windows 8.1 Enterprise
This is the one Im currently using, everything but WMC are working fine. I did not know about this so worth a look at. Does this practice have a proper 'name' as googleing 'Windows 8 embedded product key' brings up BIOS stuff and Embedded stuff
Awesome that fixed it Used DISM /Set-ProductKey to insert a gVLK key (ending J8D3P) into the wim, used this ei.cfg for them as was before but this time WMC installed with OOBE and SetupComplete running as normal. Code: [Channel] OEM [VL] 0 Many thanks guys, sorted it and learnt something new along the way