OEM registration pages

You can customize OEM registration pages to gather customer information, and introduce offers, during OOBE. If you choose to implement the optional registration pages, we recommend that you use them to provide information and opportunities that benefit your customers. The Windows OOBE is designed to maximize customer engagement by creating pages that focus on one thing at a time. As a result, OEM registration fields are divided between two separate pages.

Here is an example of the two OEM registration pages:

The OEM registration pages work with a Microsoft Account (MSA) to help customers enter in their information only once during OOBE. Microsoft prompts customers to sign up for an MSA or sign into an existing MSA during OOBE. When a customer does this, their first name, last name, and email address for the MSA, if provided, will be pre-filled in on the first registration page. The customer can change their information before clicking Next if desired.

If the customer has not used an MSA, the fields on the OEM registration pages will be empty, and the customer can fill them in if and as desired.

The OEM registration pages are the last screens in the OOBE flow, after the user goes through all other steps in OOBE.

The customer information submitted through the registration pages will be stored in the %systemroot%\System32\Oobe\Info\ folder, and will be encrypted using a public key that you place into the Windows image. Collect the encrypted data using a Microsoft Store app designated as your OEM App, or write a service that does this, and upload the data to your server. Decrypt the data using the corresponding private key once it's on your server.

To include your registration pages in OOBE, you must configure the appropriate settings of your OOBE.xml file. For the registration pages to display, you have to provide a minimum amount of information: a page title, a page subtitle, the customerinfo element, and at least one additional checkbox or one link, and a public key for public/private encryption.

Note

If the MSA used during OOBE is recognized as owned by a minor, the OEM registration pages will be hidden during the OOBE flow to maintain compliance with the Age Appropriate Design Code (AADC) in the United Kingdom and European Union.

In this section

The following topics describe how to add your registration pages to OOBE.

Topic	Description
Design your registration pages	Guidance on customizing the registration page fields and HTML flyout pages.
Configure OOBE.xml	The elements of Oobe.xml are used to customize your registration pages. Create a custom Oobe.xml file or files as determined by the languages and regions where you ship your company's PCs. You can use multiple Oobe.xml files for language- and region-specific terms and settings so users see the correct language as soon as they start their PCs.
Protect and collect user data	To protect customer privacy, Windows encrypts the customer data that's created via the Registration pages using a public key that you generate and store in the Windows image. Create an OEM App or write a service that collects the encrypted data and uploads it to your server using SSL. You can then decrypt the data using the corresponding private key.