

The key is injected at the mfg not in Redmond so I'm thinking the mfg gets a tool. You now have an OEM license that passes the Microsoft screening.Īs to whether you can access the table to alter or edit the Product key? I just found out about the product key in the eufi, we'll have to wait and see. Whether it's limited in duration or scope, or or not, doesn't matter. This is the workaround as recommended by Microsoft in their ADK tutorial Creating a Custom Windows for Deployment tutorial at msdn (i think). The process of making (or learning about making or deploying) a branded Custom Windows for your own Company that makes a hardware device requires you to be an OEM.

You are a Computer manufacturer and your company name is mine was Used-Parts Custom Computers and Tailor Made Winstallations. Visual Studio Community is free.ĭownload and install the Software development Kit (SDK) and the Windows Assessment and Deployment Kit (ADK). Right click the desktop and go through your settings and set your computer as a developer.

Not the oem end-user but an OEM hardware manufacturers license.
