So, I installed Windows 8 Pro on a custom built PC for a customer. He forgot to buy Windows, I told him no sweat, I will install Windows with a generic key, and after he buys Windows, I can install the new key and activate for him. Problem is, I installed Windows 8 Pro with generic retail key ending in C9WKB, and what he bought was an OEM System builder License. So, I cannot activate Windows for him. Can I change the install channel from Retail to OEM, and install his key? I sent him to the store to get a Retail version in case not. Stores have a pretty strict policy against returning opened software, so I am trying to save him $200. From what I know, I can change the install channel on the install cd (ei.cfg), but that would mean I would have to do a clean installation, and the customer has already spend an entire day transferring his files and programs to the new computer. Thanks for any help!
Make up your mind. Install the OEM system builder key... You'd probably have to change out the license files but IDK if you can do that on already installed OS.
@A30N You can simply change the key & the OS should automatically change its channel. Do it via slmgr.vbs /ipk (CUI) or slui 3 (GUI).
Sorry, to clarify, he forgot to buy Windows when he gave me all the parts to build the PC. He bought the OEM copy of Windows after I installed and setup the Retail version.
I tried slmgr.vbs /ipk in elevated cmd, and it said invalid key. I tried slmgr.vbs /upk first to remove the key (sucessful), but cannot install the OEM key printed on the DVD cover(error 0xc004f050). I can however, re-install the temp retail key, but cannot activate it. I will try slui 3 when he gets back from the store.
@ Tito - Could he try updown8. Run updown8. Set it as Win 8 Core. Put in the OEM System Builder disk. "Upgrade" Use the OEM System Builder key ?
Great idea, I will try this too when he gets back. I told him not to open the Retail version just in case you MDL wizards wave your magic wands.
Wait, the key is for Pro & you have installed Pro using generic key, right?? Oh!! That famous MediaBootinstall trick is needed. Run CMD as administrator. At the command prompt, type, regedit Go to HKLM/Software/Microsoft/Windows/CurrentVersionsetup/OOBE/mediabootinstall changed its value to 0 Go back to the Command Prompt, type the following: slmgr /rearm Restart the pc and use the product key. A simpler solution is posted above.
I don't know. I have used it before when I was working with my Windows 8.0 upgrade disk/key I bought from M$- how does this translate between Retail/OEM?
@ Tito, isn't that reg key only relevant for those that installed using a pro upgrade key? The "generic retail key ending in C9WKB" is not an upgrade key so therefore the reg key will already be set to 0.
Actually the factor is the Pro System Builder key. AFAIK, it requires a qualified version of previous edition of Windows (behaves same like an upgrade key).
Actually, I bought the same OEM System Builder version from the same store (where I work), and it clean installs without requiring any previous versions of Windows. I called Microsoft, but they don't provide activation support for OEM System Build keys. I'm ripping the disc now with ImgBurn, and going to extract the ei.cfg file so I can post the contents. Edit: The System Builder disk does not contain an ei.cfg file. However, the 8.1 disk I used to install on the customer's computer does. It has the following: [Channel] Retail And that's it.
Well the purpose of System Builder to me is to build a new machine, it would be illogical to require an update. Honestly, if all else fails I would perform the updown8 task and call it a night/day.
WOW yeah I wouldn't have done that. So what happened is that he bought two Windows 8.1 disk/keys. Seems like a lot of when a simpler/cheaper solution was at hand.
I can understand why you would want the issue resolved ASAP, from my personal experience lot of customers just want the problem fixed regardless of cost, and if the problem drags on they can be unpleasant to deal with. I think the retail disc was a good long term solution, customer has his own disk and can also call Microsoft support in the future if he has activation issues later on. I wonder what the deal is with the OEM System Builder keys - do they require a special pkeyconfig.xrm-ms to be accepted as valid?