If you frequently install, restore, or set up Windows systems for others , you've probably wanted to add your personal touch more than once. A custom logo, your contact information, or shortcuts to your most recommended tools. All of this is controlled through Windows OEM information, and it can be edited and customized with considerable flexibility.
In this article, we'll take a detailed look at how OEM customization works in Windows. From the data displayed in the System window and the manufacturer's logo , to the registry pages the user sees during the first boot (OOBE), and even the Start menu design with custom OEM groups and shortcuts to applications or websites, we'll cover it all. You'll see both manual options (Registry, XML, system paths) and tools that simplify the process.
What is OEM information in Windows and where is it displayed?
When you buy a computer from a manufacturer like HP, Acer, Lenovo, and others, you'll usually find, when you open Control Panel > System or the classic "System Information" window , that the manufacturer's name, model, support information, and a logo appear at the bottom. This block is the infamous OEM information , which many technicians use to add their own branding and contact details.
This data isn't hardcoded in Windows: it's stored in the system registry , in a very specific key. This means you can change, delete, or create it from scratch if the computer doesn't come with any factory settings. You just need administrator privileges and a little care to avoid touching anything you shouldn't.
In addition to the information visible in the System window, OEMs have much more advanced mechanisms to customize the initial Windows experience : registry pages during OOBE, Start menu design with a group of OEM tiles, icons that launch UWP applications, desktop programs or web links, and even region-specific settings.
It's important to understand that the OEM information in the Control Panel is separate from what's displayed in the modern "Settings > System > About" app. Even if you customize the logo and text in OEMInformation, those changes will only be reflected in the classic System window, not the modern Settings screen.
Edit OEM information from the Windows Registry
The most direct way to change the OEM data visible in the System window is to go to the Windows Registry and edit the OEMInformation key . It's a simple method, although it requires caution and should always be done with a user account that has administrator privileges.
To open the Registry Editor, simply search for "regedit" from the Start menu (or in the taskbar search box in older versions, such as Windows 10 with Cortana), run the result, and accept the User Account Control prompt. Once inside, navigate through the branches until you reach the key you're looking for.
The complete route is as follows (both in 32-bit and 64-bit systems):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation
This key stores the text values and logo displayed in the System Information panel.
Within OEMInformation, you can define several REG_SZ (text string) entries that control what the user sees. The most common ones used by manufacturers—and which you can also use to your advantage—are:
- White WaveDesign logo : full path to the BMP file that will be displayed as the logo.
- Manufacturer : manufacturer's name.
- Door Design : equipment model or a custom description.
- Support hours : business hours or technical support.
- Support Phone : support phone number.
- SupportURL : support website or your professional site.
To change any of these fields, simply double-click on the corresponding value , type the new text in "Value data" and accept.
OEM logo requirements and change (logo.bmp)
The OEM logo is the image that usually appears on the side of the System window. Windows doesn't accept just any file type or size. Therefore, it's important to respect the system's limitations to ensure everything looks correct and there are no loading problems.
For Windows to display the OEM image correctly, the file must meet these basic requirements: BMP format, 32-bit color depth , and recommended dimensions of around 100x100 pixels (some guides suggest 120x120, but the idea is to maintain a small square size). If the image is a different size, Windows will automatically resize it. This can cause distortion or loss of quality.
Another key point is location. The image must be located on a local path on the computer itself.not on a network drive or a shared resource. The path must be specified in the Registry Logo value. Absolutaincluding drive, folders and file extension, for example:
C:\Windows\System32\oemlogo.bmp
If you want to completely remove any OEM logos, simply leave the Logo value blank (empty string) or delete the OEMInformation key. You'll see the change as soon as you close and reopen the System Information window. No need to log out or restart your computer.
Also note that this customization only affects the classic System screen in the Control Panel . In the Windows 10 or 11 Settings app, the "About" section will not display any OEM image, even if you have configured the logo and data in the Registry.
Advanced OEM customization during Windows OOBE
OEM information customization is not limited to the System window. Manufacturers (and any organization that prepares custom images) can integrate their own pages into the Out-of-Box Experience (OOBE) flow —that is, the wizard the user sees the first time they boot a computer or after a factory reset.
Windows allows you to add OEM registration pages to the initial setup experience, primarily intended to collect basic customer information and offer promotions, additional services, or links to support resources. Microsoft's philosophy is that these pages should only be used to provide real value to the user, not to overwhelm them with endless forms.
The OOBE flow is designed so that each screen focuses on a single thing. That's why the fields on these OEM pages are typically spread across two separate registration screens . This way, the information is presented more clearly, and the user isn't overwhelmed by too many fields at once.
The OEM registration pages appear at the end of the OOBE wizard , after the user has configured everything else (account, language, region, privacy, etc.). They are, so to speak, the last step before reaching the desktop. This makes them a good place to request contact information or display manufacturer-specific offers.
An interesting detail is that these pages can leverage the Microsoft account (MSA) information the user entered during the OOBE. If the customer creates or signs in with an MSA, Windows can automatically fill in fields such as first name, last name, and email address on the first OEM registration page, so the user doesn't have to type everything again (although they can always modify it before clicking "Next").
Design and configuration of OEM registration pages
For OEM registration pages to appear in the OOBE, simply activating them "magically" isn't enough. You need to correctly configure the Oobe.xml file in the Windows image. This file defines the screen elements: titles, subtitles, customer info fields, additional checkboxes, links, etc.
Microsoft sets a minimum amount of required information for Windows to accept and display these pages within the initial setup wizard. You must include, at least, the following:
- A page title.
- A subtitle.
- The customerinfo element (which defines the data to be collected).
- An additional checkbox or a link.
- A public key that will be used to encrypt the collected data.
The design of the registration pages can also be highly customized. The idea is that the appearance and content should match the OEM's branding while remaining clear and user-friendly.
For devices that will be sold in multiple countries, it's common practice to create different versions of Oobe.xml for each language and region . This way, users see registration information in their language from the first boot, without having to resort to generic English text. It's possible to use multiple Oobe.xml files to adapt both legal terms and region-specific elements.
In addition to the content of the pages, it is crucial to protect user data . Windows automatically encrypts the information that the client enters on these screens using the public key that the OEM embeds in the image. Only the corresponding private key, which is managed on the manufacturer's or company's server, can decrypt that information.
OEM Log Encryption Chain and Data Collection
The data that the user enters on the registration pages is not stored directly on the computer. Windows saves it encrypted in the system folder. %systemroot%\System32\Oobe\Info\, using a public key that the OEM has previously included in the Windows imageThis architecture is designed to protect customer privacy from the very beginning.
To retrieve this information, the OEM needs a specific application or service . A common option is to create a UWP app (distributed through the Microsoft Store) marked as an OEM application, which reads the encrypted data and uploads it to a secure server using SSL. Another alternative is to develop a custom Windows service that performs the same function.
Once the encrypted data reaches the server, the manufacturer or user company uses the associated private key to decrypt and store it in their CRM system, customer database, or other designated storage method. Under no circumstances should this data be handled unencrypted on the device. This is essential to prevent leaks or unauthorized access if the device falls into the wrong hands.
Taken together, this scheme of public key in the image, local encryption, and private key decryption on the server allows OEM registration pages to meet current privacy requirements , provided the OEM properly implements the server-side portion and respects applicable data protection regulations.
Customize the Home page design using LayoutModification.xml
In addition to system information and log screens, OEMs can customize the Start menu design to add your own icon group at the end of the predefined design. This is done using a file called LayoutModification.xmlwhich indicates which tiles should appear, what size, and what application or resource each one opens.
In desktop editions of Windows 10, the default Start menu layout is determined by the edition (Home, Pro, Enterprise, etc.) and region . Windows then processes the LayoutModification.xml file (and, in some cases, Unattend.xml) to apply additional customizations, including the OEM group.
The standard approach involves defining an OEM group at the end of the Start menu , so the user can clearly see that it contains applications and shortcuts customized by the manufacturer. In recent versions, Microsoft has consolidated this concept into a single OEM group, instead of several. This is a good way to simplify the user experience.
The element used within LayoutModification.xml <AppendGroup Name="OEM Group Name"> To create this group and specify its display name, you can choose a name that reflects the hardware brand or the OEM's trade name, as long as it's not confusing for the user. In some specific cases, if there's only one row of icons and the first one clearly displays the brand logo, you're allowed to omit the group name.
Definition of mosaics, sizes and position in the OEM group
In LayoutModification.xml, each Start icon is defined with a specific element. For Universal Windows Platform (UWP) apps and Windows 8/8.1 apps, the following is used: <start:Tile ... />, while for desktop programs (Win32) one uses <start:DesktopApplicationTile ... />There are also elements for web link icons and other special cases.
Attribute Size de start:Tile It accepts four values: 1x1 (small), 2x2 (medium), 4x2 (wide) and 4x4 (large)By playing with these combinations, you can create an attractive grid within the OEM group, always trying to avoid visual gaps that give a sense of disorder or "blank spaces" within the design.
The position of each tile within the group is determined by the attributes Row (row) and Column (column), which mark the upper left corner of the icon in that grid. The coordinate 0,0 This corresponds to the first row, first column of the group. From there, rows and columns are added according to the desired combination of sizes.
Regarding the icon type, for a UWP application, the app's user model identifier (AUMID) is specified in the attribute AppUserModelID de start:TileThis identifier is case-sensitive, so it should be copied exactly as shown. For example, a tile for the Windows Calculator would be declared by specifying the application's AppUserModelID in the XML.
When it comes to classic desktop programs (Win32), it is used <start:DesktopApplicationTile ... /> And there are two ways to specify which executable should be launched: by using the path to a shortcut (.lnk) with the DesktopApplicationLinkPath attribute (for example, pointing to the Command Prompt shortcut in the Start menu), or by using a DesktopApplicationID if the application has that registered identifier.
Office options, regions, and dynamic applications
The design of the Start menu is also influenced by the presence of Microsoft Office and dynamically delivered applications . Throughout Windows 10 versions, there have been several options and parameters in LayoutModification.xml to control how Office icons are displayed depending on the installation type and version.
In modern versions (starting with Windows 10, version 1903), it is recommended to install the Click-to-Run (C2R) version of Office using the OPK and let Windows automatically add the corresponding icons to an expandable folder within Startup. You no longer need to include Office-related tags in LayoutModification.xml. The system now detects the installation and places the shortcuts automatically.
In earlier versions (1803, 1809) there were specific labels such as <AppendOfficeSuite/> y <AppendOfficeSuiteChoice Choice="Desktop2016" /> or variants such as DesktopBridgeSubscription, DesktopBridge or options for Office Mobile, designed for specific scenarios (devices downgraded to Windows 7, bridge subscriptions, small screens, etc.). Many of these configurations are already available. in disuse for modern installations.
Another important aspect is the regional customization of the Start menu layout. The Region attribute in the RequiredStartGroups tag of LayoutModification.xml allows you to define different layouts for different geographic areas. Alternatively, you can use multivariate support in Windows provisioning to decide which layout to apply based on the device's region.
Regarding dynamically delivered apps , some of the tiles you see on Start are downloaded after the OOBE, depending on your network connection and Windows edition.
Starting with Windows 10, version 1903, these dynamic app delivery features only apply to non-domain-joined Home and Pro editions. Domain-joined Pro, Enterprise, and Education editions do not receive these programmable icons. Furthermore, regulations in some countries, such as China, have led to the disabling of dynamic app and game delivery in certain regions since version 1809.
Commercial devices, LayoutOptions, and first execution tasks
For Windows 10 Pro devices sold to businesses, OEMs can specify that these devices should be treated as business devices even if the user does not join them to a domain during out-of-box implementation (OOBE). This is done by setting the DeviceCategoryHint attribute in the LayoutOptions element of the LayoutModification.xml file.
By including a line like <LayoutOptions DeviceCategoryHint="Commercial" /> In the XML, the device with SKU Pro is considered commercial and, therefore, receives Enterprise's own Home designWith fewer icons and no dynamically delivered apps, this option is intended for devices clearly geared towards professional use. It should not be used on Pro devices that might end up in the hands of home users.
In addition to LayoutModification.xml, it's possible to define First Run Tasks , which are background tasks that are activated the first time a user logs in. These tasks are not configured in LayoutModification.xml, but rather in Unattend.xml, using StartTiles tags associated with the same AppID used in LayoutModification.xml for the corresponding application.
It's important to note that if the layout XML includes an AppendGroup tag for a tile group, this setting can override the Start anchors in Unattend.xml. However, when a StartTiles tag exists in Unattend.xml for the same AppID defined in LayoutModification.xml, the FirstRunTask property specified in Unattend.xml will be respected, thus combining both files.
All these possibilities – OEM system information, OOBE registration pages, Startup layout with OEM group, web links, Office icons, region settings, and first-run tasks – allow for a highly customized experience for manufacturers, technicians, and companies preparing Windows images for their customers, provided that good security and privacy practices are respected and each component is carefully configured.
