What Is Compatibility Support Module (CSM) in UEFI?

The Compatibility Support Module (CSM) is an integrated component of modern Unified Extensible Firmware Interface (UEFI) firmware designed to emulate a traditional legacy BIOS environment. This article explains what CSM is, how it operates within system firmware, and the critical role it played during the early adoption of UEFI by bridging the gap between aging legacy hardware, older operating systems, and modern firmware architecture.

Defining the Compatibility Support Module (CSM)

The Compatibility Support Module is a sub-component within UEFI firmware that provides legacy BIOS (Basic Input/Output System) emulation. When CSM is enabled, the system does not boot entirely through modern UEFI pathways. Instead, it recreates a legacy 16-bit PC environment, offering traditional interrupt calls (such as INT 10h for video and INT 13h for disk access) and support for the Master Boot Record (MBR) partition scheme.

This mechanism allows computers with UEFI motherboards to run legacy operating systems and load older device firmware that are not natively compatible with the 32-bit or 64-bit execution environments of pure UEFI.

Why Early UEFI Implementations Included CSM

When the computing industry began transitioning from legacy BIOS to UEFI in the late 2000s, an immediate and total replacement was impractical. Early UEFI implementations relied heavily on CSM for several essential reasons:

1. Operating System Compatibility

During the initial rollout of UEFI, mainstream operating systems lacked native UEFI support. For example, Windows XP and 32-bit versions of Windows Vista and Windows 7 required a legacy BIOS environment to boot. Early UEFI systems included CSM so users and enterprises could upgrade to newer hardware platforms without being forced to abandon their existing operating systems or software environments.

2. Legacy Option ROM Support

Expansion hardware—such as discrete graphics cards, RAID controllers, and network interface cards (NICs)—traditionally relied on legacy 16-bit Option ROMs stored on the expansion cards themselves to initialize during the boot phase. Until hardware manufacturers shifted entirely to developing UEFI-compliant drivers (UEFI Option ROMs), CSM was strictly necessary to initialize these components during system startup.

3. Master Boot Record (MBR) Reliance

Modern UEFI systems natively boot from drives using the GUID Partition Table (GPT) scheme. Prior to widespread GPT adoption, storage drives relied entirely on the MBR partitioning method. CSM enabled systems to continue reading MBR-partitioned boot drives, preventing boot failures on existing storage setups during hardware upgrades.

4. Facilitating an Industry-Wide Transition

The original PC BIOS had been the computing standard since 1981. Transitioning the global ecosystem of system builders, component vendors, and IT departments to an entirely new standard required a phased approach. Firmware developers introduced the "UEFI Class" system, where Class 2 systems featured UEFI with CSM capabilities, providing a fallback mechanism that mitigated hardware incompatibility risks.

The Obsolescence of CSM

As the hardware and software ecosystems matured, modern operating systems added native UEFI and GPT support, and expansion devices began shipping exclusively with UEFI Option ROMs. Furthermore, critical security features like Secure Boot require UEFI to run natively without CSM, as legacy BIOS emulation cannot enforce modern signature checks.

Consequently, CSM has been phased out. Modern systems (classified as UEFI Class 3 and Class 3+) operate exclusively in pure UEFI mode, eliminating CSM entirely to improve boot performance, enhance system security, and streamline firmware maintenance.