First, I forgot the the fact that Win8 doesn't like doing upgrades from DVD boots--as in I booted to the burned install DVD, selected the recommended "upgrade" install option--and then the program tells me, "Did you think we were *really* going to let you upgrade from here? Well, we aren't--reboot and run the upgrade from your Win8 boot, 'kay?"
Yeah, that was nice. ( Next, I get "refresh" language confused with "upgrade" language--although I certainly do think that Microsoft should be consistent when it says, "apps," don't you? When upgrading within 8.0 "apps" apparently means "all of the programs installed on your system", but when doing a "refresh" suddenly "apps" means "only those programs installed via the Microsoft store."
Thanks, Superfly. Tell the truth, Microsoft has done and said so many contradictory things this year--2013 has to be a record for Microsoft misstatements, turn-arounds, and bloopers. It's a wonder any of us has a decent handle on things, anymore, because it doesn't appear that Microsoft does.
I mean--just look at this situation...First Microsoft says, "Were doing 8.1 RTM beginning today but we aren't releasing to the public/developer community until October 18 (or thereabouts)." Predictably, the RTM is leaked and Microsoft goes ahead and releases to the public/developer, anyway. Then there's the whole "We aren't releasing an iso to consumers" Microsoft-employee blog, which seems like an incredible statement since 8.1 will be replacing 8.0 on retail shelves very soon (as we have already discussed.)
This entire year, Microsoft announcements--then retractions--have often sounded like they were coming from people who had never been a part of a Windows release before and for whom the whole thing was a brand-new experience. But the fact is that many of those people responsible for making the bad decisions this year had been at Microsoft for years--and *should* have known better (Mattrick and the xBone fiasco, for instance.) Weird & strange times, no doubt about it.
ACPI Table > MSDM tab. Product key is at the bottom.
Thinking about this a bit more. May be it does read the embedded code but because its a Windows 8.0 code it ignores it? It's looking for an 8.1 code on a full install. Just for fun I did try entering one of my TechNet Windows 8.0 product codes and it wouldn't except that. I didn't get anywhere until I entered an actual 8.1 product code.
Hi guys, thanx for the info.. was just wondering..
If you use a pid.txt with the default installation key, it should skip that initial request for a key, but will it still then require manual input of your OEM key from the bios ie. setup does not grab it like a it would for an original edition install and overwrite the initial key - so that all one would need to do is click 'activate now' or something?
If not, to automate one would then have to have a setupcomplete script to -upk and -ipk (with correct OEM key) and activate -ato?