How to edit and customize OEM information in Windows

  • What is OEM information in Windows and where is it displayed?
  • How to customize logo, texts and manufacturer data from the Registry
  • How OEM registration pages work and are configured in OOBE
  • Design and security recommendations for HTML and data encryption
Lorena Figueredo

19 minutes

How to edit and customize OEM information in Windows

Customize OEM information in Windows It's one of those tricks that many people don't know about, but it lets you personalize your computer with your own unique touch: logo, manufacturer's name, model, support information, and even text about the hardware that appears in the System Properties window. Furthermore, manufacturers can go even further and configure OEM registration pages during the Out-of-Box Experience (OOBE) to collect customer data and display offers or additional information.

In this article you will see how to edit and customize both the classic OEM tab (the one that appears when you right-click on "This PC" > Properties or in Control Panel > System) as well as the OEM registry pages that appear when you set up Windows for the first time. We do this in detail, explaining each Registry key, the limitations, the recommended design for floating HTML, and, of course, precautions to avoid messing things up by changing sensitive values.

What is OEM information in Windows and where is it displayed?

OEM (Original Equipment Manufacturer) information This refers to the manufacturer's information and, in some cases, the owner's information, which Windows displays in the System Properties tab. It's what you usually see on some brand-name computers: the manufacturer's logo on the right and, below it, text with the manufacturer's name, model, support website, phone number, etc.

In classic versions of Windows, this information can be viewed by entering Control Panel > System (or by right-clicking on “My PC” / “This PC” > Properties). There you will see the operating system, architecture, amount of RAM, computer name and, if configured by the manufacturer, the OEM section with logo and additional information.

All that data is stored in the Windows Registry, specifically under the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformationThis means that, with administrator privileges, you can modify them to change both the text and the image displayed on the right.

In parallel, for new equipment or customized images, OEMs can configure Registration pages integrated into the OOBE experience (the initial Windows setup). These pages allow them to collect customer information, display privacy policies, offer promotions, or introduce customized legal terms before the user completes the initial system setup.

OEM registration pages are displayed at the end of the OOBE flowOnce the user has gone through the typical screens for language, region, network, Microsoft account, privacy, etc., these are optional, but very useful if you want to centralize user registration or do marketing directly during the first startup process.

OEM registration screens in Windows

How to customize the logo and OEM data in System Properties

The OEM tab in System Properties is controlled almost entirely from the RegistryHere you can: change the logo, edit the manufacturer's name, specify the equipment model, add a phone number and a support website, and other information that you will see when you open the System Properties.

To access the Registry, the easiest way in Windows 10 or Windows 11 is to open the search (Cortana or the search box in the Start menu), type Regedit and run the Registry Editor. It is essential that the user has Administrator privilegesOtherwise, you will not be able to modify the keys you are interested in.

Once inside, navigate to the route HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ OEMInformationIn the right panel you will see different values, including the one that displays the manufacturer's image and other text fields that you can use to personalize your device.

Change the OEM logo (manufacturer's image)

The key to the logo is the string value called “Logo”This value stores the absolute path to the image file that Windows will display in the OEM tab of System Properties. To modify it:

  • Double-click on the Logo value in the right panel of the Registry Editor.
  • In “Value Information”, write the full path to the image file you want to use (for example, C:\Windows\System32\mioemlogo.bmp).
  • Balance AcceptClose Regedit and reopen the System Information window to see the change.

If what you're looking for is that no OEM image appears, simply leave the value field Logo blank. Windows will stop displaying the logo in that area of ​​the Properties window.

It is important to respect the technical characteristics of the image so that it looks good and doesn't cause problems:

  • It must be a file .bmp (bitmap).
  • The recommended color depth is 32 bits.
  • A size of 100 × 100 pixelsIf the image has different dimensions, Windows will automatically resize it, which may distort it.
  • The image must be stored locally on the computer itself, not on a network drive or an external resource.
  • The path in the Registry must be Absolutaincluding drive, full path, and file extension.

The BMP file is usually placed inside the C:\Windows\System32 folderso that the system has guaranteed access to the image at all times. Many tutorials recommend saving the image there and then pointing the Logo value to that path.

Note that This logo is only displayed on the System Information tab of the Classic Control PanelThe modern Windows Settings app (the one you open with Windows + I) doesn't show any OEM images in its system information section, so don't be surprised if you don't see any changes there.

Other OEM fields that can be customized

In addition to the logo, the OEMInformation key can include several text values that define the manufacturer and equipment information. Depending on your Windows version and the original manufacturer, you can find and/or create values ​​such as:

  • Manufacturer: manufacturer's name (for example, "My Computer Workshop", "Techno-Solutions", etc.).
  • Door Design: equipment model.
  • SupportURL: support website.
  • Support Phone: customer service phone number.
  • Support hours: support hours.
  • Location of proprietary scripts or tools, if the OEM decides to include them.

Simply create or modify these REG_SZ type values (text string) within OEMInformation This will update the content on the OEM tab. It's a completely safe change if done carefully, as it only affects the displayed information, not the internal workings of the hardware.

This type of customization is typically used professionally by integrators and manufacturers, who often perform tasks such as Managing partitions in Windows when preparing images, but it is also exploited by advanced users such as A harmless “hack” to show off your equipmentYou can make your modest PC look like a high-end, branded model, or simply make it more elegant and in line with your identity.

Edit OEM data in the Windows Registry

Modify the hardware information displayed in System Properties

Windows obtains processor and memory data from various Registry keys and the system itself.Some of the text you see in System Properties about the CPU can be manually modified, allowing you to "make up" the visible specifications without touching the actual hardware.

The microprocessor information is stored in the key HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessorUnder this key you will find numbered subkeys (0, 1, 2, etc.) which correspond to the logical cores or processors of the system.

Each of those subkeys contains the value ProcessorNameStringThis is a text string containing the processor name that Windows displays in many places, including the System Properties window. If you want to change what's displayed, you just need to edit that value.

For example, you could change a modest “Intel(R) Pentium(R) 4” to something more impressive, such as:

  • Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
  • Intel(R) Core(TM) i7 CPU 950 @ 2.67GHz

From a system perspective, it's a cosmetic change: It does not alter actual performance or deceive Windows internally.It only modifies the displayed text. Even so, it's recommended to export the key. CentralProcessor before touching anything (right click > Export) so that you can restore it if needed.

Use a script to make the CPU change permanent.

The main problem with manually modifying ProcessorNameString is that Windows can restore the original value upon restarting.This is because the hardware information is re-detected at startup. To prevent this, a small script can be used to rewrite the desired information at each login.

The idea is to create a script in VBScript (.vbs) that uses the object WScript.Shell to write the new CPU name to the Registry. The basic scheme is something like this (adapted to your case):

Simplified script example (just the general idea, you need to adjust it):

Dim wshShell, RegKey
Set wshShell = Wscript.CreateObject("Wscript.Shell")

RegKey = «HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0»
wshShell.regWrite RegKey & “ProcessorNameString”, “CPU Name”, “REG_SZ”

Set wshShell = Nothing
Wscript.Quit

If your processor has multiple cores (and therefore several subkeys 0, 1, 2, 3…) you will have to repeat the logic for each one, adjusting the Registry path (for example, CentralProcessor\1, CentralProcessor\2, etc.).

Once the file with the extension is saved .vbs, copy it to the folder of Home from the user (or you configure a scheduled task at system startup) to run automatically every time Windows starts. That way, The "sham" CPU name is rewritten to the Registry on each reboot, maintaining the look you want for your team.

Introduction to OEM registration pages in OOBE

OEM registration pages are part of the first-time Windows boot experience, known as OOBE (Out-Of-Box Experience). These are optional screens that a manufacturer can activate to display its own information and collect additional user data before the entire setup process is complete.

Windows is designed so that each OOBE screen focuses on a single task, with the goal of maximize user engagement and avoid overwhelming them with options. That's why OEM registration pages are divided into two independent screensEach one has specific elements and a locked design that cannot be rearranged, although the texts and certain behaviors can be customized.

These screens allow, for example, Show special offers, explain additional advantages of the equipment or serviceYou could link to your own privacy policies, or simply complete the customer's contact information and preferences. The idea is that, if you decide to implement them, you use them to provide real value to the user and not just to ask for data for the sake of it.

The information that the user enters on these pages is saved in the folder %systemroot%\System32\Oobe\Info\, encrypted with a public key that the manufacturer includes in the Windows image. Subsequently, an OEM application (for example, a Microsoft Store UWP app marked as an “OEM app”) or a specific service can collect this encrypted data and send it to a server via SSL for processing, where it is decrypted with the corresponding private key. Additionally, preparing the image and firmware may require Update UEFI securely as part of the integration process.

OEM registration page: customer data

The first OEM registration page focuses on collecting basic customer information.The screen design is fixed: the elements appear in a specific order that cannot be changed, but many of them can be customized in content.

On this first page you will find the following main elements:

  • Page titleA main text that defines the purpose of the page (for example, “Product Registration” or “Complete your details”). This title also appears on the second registration page.
  • Page subtitleThis is secondary text that helps the user understand what they need to do or why they are being asked for that information. It will also be displayed on the second page.
  • Customer information fields: a set of fields that are not customizable in terms of type and structure, but are customizable in terms of the text that the user enters.
  • A customizable link: is usually used to display the privacy policy or other legal information.
  • Skip button: allows you to skip OEM registration.
  • Next button: advance to the next step of OOBE.

The page title and subtitle are controlled through the element from the Oobe.xml fileThis gives you room to adapt them to the tone and style of your brand, but always maintaining clear wording and focused on ensuring the user understands what is expected of them.

Customer information fields on the first page

The customer information fields on this first page cannot be structurally modified.In other words, you cannot add new fields or remove existing ones, nor can you change their type or validation. Windows defines a fixed set of fields:

  • Name
  • Last Name
  • Region / Country or region (drop-down list)
  • Email
  • Telephone

The email field includes validation To ensure the user enters a correctly formatted address before proceeding, the country or region field is presented as a drop-down list, and each option has an associated two-letter code based on the ISO 3166-1 Alpha-2 standard.

It is important to be clear that These fields cannot be reordered or replaced with othersYour customization options focus on the text (title, subtitle, link) and what you do with the data afterward, but the page structure is what it is.

Customizable link and navigation buttons

The first page includes a configurable link through the element from Oobe.xmlThis element allows you to customize:

  • El link title (the text that the user will see).
  • La path to the HTML file which will open when clicked (usually a local document with the privacy policy, registration conditions, etc.).

If the link is used to display a Privacy PolicyIt is essential that you keep the content updated and adapted to current regulations, as it forms part of the legal relationship between your company and the client.

El Skip button It appears visible by default, although you can hide it by configuring the element. hideSkip in the Oobe.xml file. If the client chooses to Skip, No registration data is sent of any kind. The button text is not customizable.

El Next button It simply serves to move the client to the next OOBE step. It is also not customizable in text or behavior, beyond what is defined by the standard Windows experience flows.

Customer information pre-filled from MSA

Windows attempts to reduce user effort by reusing information it already has.When a user signs in or signs up with a Microsoft account (MSA) during OOBE, some of the data requested on the OEM registration page has already been provided.

Depending on the account path chosen in OOBE, the first OEM registration page may appear with fields already completed:

Account routing Fields previously filled in
Registering a new Microsoft account Name, surname, email address
Sign in with an existing Microsoft account Name, surname, email address
Sign in with Azure AD account No pre-filled fields
Creating local accounts No pre-filled fields

This makes it so that, if the user has already entered their data when setting up their MSASee the Name, Surname and Email fields already filled in on the OEM page, and you can modify them before clicking Next if you want them to be different from those in the account.

Second OEM registration page: additional boxes and links

The second OEM registration page focuses on additional preferences and consentsUnlike the first one, here no extra personal data is requested by default, but check boxes and links are presented, typically aimed at commercial subscriptions, acceptance of conditions or selection of communication options.

This second screen includes:

  • Page title and subtitle: the same as on the first page, also defined through the element in Oobe.xml.
  • Up to four check boxes with their descriptive labels and default states.
  • Up to two additional links located below the boxes.
  • Next button to continue the OOBE flow.

The boxes and links are defined using the elements , , , (for the boxes) and and (for links) within the Oobe.xml file. There you can adjust both the text that is displayed and the default markup values.

The links on this second page, like the first, point to HTML files stored locally in %systemroot%\system32\Oobe\InfoAll associated content (legal texts, extended explanations, etc.) must be located within those HTML files, as external links and even online resources will not function within the floating control that OOBE uses to display information.

Oobe.xml architecture for activating registration pages

For OEM registration pages to appear in the OOBE, it is essential to correctly configure the Oobe.xml file.Without this file, or without the minimum necessary elements, Windows simply will not display those screens and the user will go directly to the desktop after completing the rest of the setup steps.

To activate the registration pagesYou must provide at least:

  • Un page title or with a subtitle defined in .
  • The element , which enables the collection of customer data.
  • At least one additional checkbox or link (for example, checkbox1 or link2).
  • An public key for the encryption of the collected data.

It is possible to have multiple Oobe.xml files. Differentiated by language or region, so that a single manufacturer selling equipment in different countries can display texts, conditions, and options adapted to each market. The system detects the language/region setting at startup and automatically displays the appropriate version.

The elements in Oobe.xml not only control the presence of registration pages, but also They determine which links are displayed, which HTML is opened in each case, and how certain options behave. (for example, whether or not the Skip button is displayed on the first page).

Design of the HTML files for the OEM links

When the user clicks on any link on the OEM registration pagesAn HTML file opens in a pop-up window (floating control) within the OOBE itself. These documents must be located in the folder %systemroot%\system32\Oobe\Info and follow specific design guidelines so that the experience is consistent with the rest of the Windows configuration environment.

Microsoft provides a Complete HTML example with inline styles which defines colors, typography, font sizes, margins, and headings. The official recommendation is to use that example as a base, with few or no modifications to the design elements, so that it doesn't clash with the other OOBE screens.

The OOBE environment uses a Dark blue background with light textThe EULA (End User License Agreement) content and other floating controls use this same scheme, as well as dark backgrounds for dropdown areas with light-colored text. Your HTML should align with this look and feel to provide a consistent experience.

Recommended colors

The basic colors defined in the CSS example are:

  • Background color: #2b2b2b
  • Font Color: #FFF (White)

Using these values ​​ensures that the content of your floating windows Don't break the OOBE aesthetic and maintain adequate contrast for reading on various screens, including those with reduced brightness.

Typography and text hierarchy

The standard font in OOBE is Segoe UITo maintain consistency, you should use “Segoe UI Webfont” in your HTML documents, and define a list of backup fonts in CSS in case a variant is unavailable.

The example CSS code establishes a font size 0.9375 rem, normal weight (400) and a line spacing of 1.25 remHeadings and paragraphs are treated separately to clearly mark the visual hierarchy of the content.

To structure the text, it is recommended to use:

  • for main headings within the floating control.
  • for the body of the text.
  • to highlight key fragments (bold).
  • to display indented lists or groups of hierarchical elements; it is necessary for some templates, such as the EULA content template, although in other floating controls it may be optional.

The styles apply both to oneself such as elements with dir and align attributes to support languages ​​with right-to-left (RTL) or left-to-right (LTR) writing, adjusting margins and alignments correctly according to the user's language.

Sample CSS provided by Microsoft

The recommended CSS code (to insert into a block) <style type="text/css"> ... </style> in it (from HTML) includes rules such as:

dir { padding: 0 12px; }
dir { padding: 0 12px; }
{ text-align: right; }
{ text-align: left; }
{ text-align: left; }
{ text-align: right; }
body { padding: 0 12px; }
body { padding: 0 12px; }
body { -ms-overflow-style: scrollbar; background: #2b2b2b; color: #FFF; font-family: "Segoe UI", "Segoe UI Webfont", ...; font-size: .9375rem; font-weight: 400; line-height: 1.25rem; margin: 0; max-width: 100%; overflow: auto; padding-bottom: 0; padding-top: 0; }
body b * { font-weight: 700; }
html { font-size: 100%; }
p { font-size: .9375rem; font-weight: 400; line-height: 1.25rem; max-width: 100%; padding-bottom: .0141875rem; padding-top: .0141875rem; }
h4 { font-size: 1.25rem; font-weight: 400; line-height: 100%; max-width: 100%; padding-top: 12px; margin: 0; }

This style set comes pre-tested and aligned with the OOBE interfaceTherefore, it is recommended to use it practically as is, limiting changes to small adjustments of textual content and structure, rather than rewriting the entire visual aspect from scratch.

Complete HTML example for an OEM float control

Microsoft also offers a complete example of HTML document including:

  • Declaration <!DOCTYPE html> and label <html dir="ltr"> to indicate the direction of the text.
  • Basic metadata: <meta charset="utf-8" /> y <meta name="viewport" content="width=device-width">.
  • A title (although it may remain empty if managed from outside).
  • The recommended CSS style block within the .
  • In it a header structure and paragraphs , with bold and multiple layers to reflect hierarchies, numbered enumerations, letters, Roman numerals, and bullet points.

The idea is that you use that HTML as a base template. for your own policies, conditions and informational texts, changing only the semantic content (what is said) but maintaining the structure, styles and hierarchy.

User data protection and collection

One of the key aspects of OEM registration pages is user privacy.All the information that the customer enters on these screens is encrypted using a public key that you, as the OEM, must generate and incorporate into the Windows image.

The encrypted data is stored in the folder %systemroot%\System32\Oobe\Info\ on the device. Then, a designated OEM application or dedicated service must be responsible for:

  • Read the encrypted data from that folder.
  • Send them to a server using a connection secure (SSL).
  • Decrypt them on the server using the corresponding private key.

This ensures that customer data does not travel in plain text.nor should they be stored unprotected on the computer. It is essential that the management of these keys (public in the image, private on the server) follows good security practices, and that subsequent processing complies with applicable data protection laws.

For integrators or companies that want to maximize customization, Create an OEM app from the Microsoft Store Centralizing the collection of this data is a very common strategy, as it allows updating business flows and logic without having to completely redo the Windows image with each change.

Among the OEM customization options and the possibilities of Oobe.xml, HTML and RegistryWindows offers a wide range of options for customizing both the system's appearance and behavior to suit the needs of each manufacturer or advanced user. By understanding the location of each setting (logo, OEM text, registry pages, scripts, floating control design, and data encryption), it's relatively easy to create a consistent, secure, and significantly more professional branded experience than the generic default configuration.

Windows Driver Kit on PC
Related article:
What is Windows Driver Kit (WDK)