Manufacturer override of monitor EDIDs

This article describes how vendors and manufacturers can override the Extended Display Identification Data (EDID) of any monitor through an INF file. A sample INF file (Monsamp.inf) is provided.

All monitors, analog or digital, must support EDID, which contains information such as the monitor identifier, manufacturer data, hardware identifier, timing info, and so on. This data is stored in the monitor's EEPROM in a format that VESA specifies.

Monitors provide the EDID to Windows components, display drivers, and some user-mode applications. For example, during initialization, the monitor driver queries the Windows Display Driver Model (WDDM) driver for its brightness query interface and device driver interface (DDI) support, which is in the EDID. Incorrect or invalid EDID information on the monitor's EEPROM can lead to problems such as setting incorrect display modes.

There are two approaches to correcting EDIDs:

  • Have the customer send the monitor back to the manufacturer, who reflashes the EEPROM with the correct EDID and returns the monitor to the customer.
  • The better solution is for the manufacturer to implement an INF file that contains the correct EDID info, and have the customer download it to the computer that is connected to the monitor. Windows extracts the updated EDID information from the INF and provides it to components instead of using the EEPROM EDID information, effectively overriding the EEPROM EDID.

In addition to replacing the EDID information, a vendor can provide an override for the monitor name and the preferred display resolution. Such an override is frequently made available to customers through Windows Update or digital media in the shipping box, and receives higher precedence than the EDID override mentioned here. For more information, see Monitor INF File Sections.

EDID format

EDID data is formatted as one or more 128-byte blocks:

  • EDID version 1.0 through 1.2 consists of a single block of data, per the VESA specification.
  • With EDID version 1.3 or enhanced EDID (E-EDID), manufacturers can specify one or more extension blocks in addition to the primary block.

Each block is numbered, starting with 0 for the initial block. To update EDID info, the manufacturer's INF specifies the number of the block to be updated and provides 128 bytes of EDID data to replace the original block. The monitor driver obtains the updated data for the corrected blocks from the registry and uses the EEPROM data for the remaining blocks.

Updating an EDID

To update an EDID by using an INF:

  1. The monitor manufacturer implements an INF that contains the updated EDID information and downloads the file to the user's computer. This download can be done through Windows Update or by shipping a CD with the monitor.
  2. Device installation reads the updated EDID information from the INF and stores the information as values under the hardware key of the monitor device. Each EDID override is stored under a separate key under the hardware key of the device.
  3. The monitor driver checks the registry during initialization and uses any EDID information stored there instead of the corresponding information on EEPROM. EDID information that is added to the registry always takes precedence over EEPROM EDID info.
  4. Windows components and user-mode apps use the updated EDID info.

Overriding an EDID with an INF

To override an EDID, include an AddReg directive in the INF for each block that you want to override, in the following format:

HKR, EDID_OVERRIDE, BlockNumber, 0x1, Byte 1, Byte 2, Byte 3, Byte 4,...

The block number is a zero-indexed value of the EDID block to override. The data bytes should be formatted as 128 hexadecimal integers that contain the binary EDID data. The "0x1" value after the block number is a flag indicating that this registry value contains binary data (FLG_ADDREG_BINVALUETYPE).

Manufacturers must update only those EDID blocks that are incorrect. The system obtains the remaining blocks from EEPROM. The following example shows the relevant sections of an INF that updates EDID blocks 0, 4, and 5. The monitor driver obtains blocks 1 - 3 and any extension blocks that follow block 5 from EEPROM:

HKR, EDID_OVERRIDE, 0, 1, 00, FF, ..., 3B
HKR, EDID_OVERRIDE, 4, 1, 1F, 3E, ..., 4E
HKR, EDID_OVERRIDE, 5, 1, 24, 5C, ..., 2D

For more information on INFs in general, and AddReg and DDInstall in particular, see Creating an INF File.

Sample INF file: Monsamp.inf

For information on how to use and modify Monsamp.inf, see Monitor INF File Sections.

; monsamp.INF
; Copyright (c) Microsoft Corporation.  All rights reserved.
; This is a generic INF file for overriding EDIDs
; of any monitors, starting with Windows Vista.

Signature="$WINDOWS NT$"

; Be sure to add the directive below with the proper catalog file after
; WHQL certification.



; Enable the following section to copy a monitor profile.


; Modify the hardware ID (MON1234) to match that of the monitor being used.

; Modify the hardware ID (MON1234) to match that of the monitor being used.

AddReg=MS_EDID_OVERRIDE-1.AddReg, 1024, 1280, DPMS

AddReg=MS_EDID_OVERRIDE-1.AddReg, 1024, 1280, DPMS





; Pre-defined AddReg sections. These can be used for default settings
; when a given standard resolution is used.




; Enable the following section to copy a monitor profile.

SourceDisksNames="MS_EDID_OVERRIDE Monitor EDID Override Installation Disk"