How Windows XP ASR Restored Disk Partitions

Automated System Recovery (ASR) in Windows XP Professional served as a specialized disaster recovery framework designed to return a non-bootable computer to an operational state. Unlike standard file-level backups, ASR had the unique ability to reconstruct entire disk partition structures and volume configurations from scratch. This article explains how ASR recorded disk geometry during backup and precisely recreated partition states during recovery using low-level setup instructions and metadata files.

The ASR Backup Phase and Metadata Generation

When creating an ASR set using the Windows Backup utility (ntbackup.exe), the system generated two primary components: the actual backup archive (stored on a tape or secondary storage medium) and an ASR floppy disk containing recovery instructions.

The floppy disk contained two critical files:

  • asr.sif (ASR Setup Information File): The primary blueprint storing disk layouts, partition structures, volume designations, and system state metadata.
  • asrpnp.sif: Stored hardware Plug and Play details to ensure proper device and storage controller enumeration during setup.

During the backup, ASR queried the system’s storage subsystem to map out every physical disk, Master Boot Record (MBR) signature, partition offset, sector count, partition type (such as primary or extended), and volume file system.

Structure of the asr.sif File

The partition layout logic was mapped out directly inside plain-text sections within asr.sif:

  1. [DISKS]: Documented physical drive parameters, including physical disk indexes, drive signatures, bus types, and total sectors.
  2. [PARTITIONS]: Specified individual partition definitions, mapping them to specific disks. Each entry detailed the partition style, starting sector offset, partition length in sectors, partition type ID (such as 0x07 for NTFS), and whether the partition was marked active (bootable).
  3. [VOLUMES]: Outlined the logical volumes, their assigned drive letters, volume labels, cluster sizes, and file systems (NTFS, FAT32, or FAT16).

The Restoration Process: Rebuilding the Partition Layout

When recovering a failed system, the user booted from the Windows XP Professional installation CD and pressed F2 when prompted to initiate Automated System Recovery.

1. Hardware Initialization and Disk Matching

Windows XP Text-Mode Setup loaded core storage drivers and prompted for the ASR floppy disk. Setup parsed asrpnp.sif and asr.sif to identify the connected storage hardware. It scanned the system's physical drives, attempting to match existing drives to the disk signatures recorded in asr.sif. If blank or replacement disks were detected, ASR prepared them for repartitioning according to the original disk index.

2. Partition Deletion and Recreation

Once the physical targets were established, Text-Mode Setup automated the disk preparation process:

  • Disk Cleaning: Any existing partition tables on target drives identified in the recovery profile were zeroed out.
  • Writing the Partition Table: Setup read the exact sector offsets and partition sizes defined in the [PARTITIONS] section of asr.sif and wrote the Master Boot Record (MBR) and partition table directly to the primary sectors of each drive.
  • Setting Boot Flags: The active partition flag was applied to the designated system partition to ensure bootability.

3. Formatting and Volume Mapping

After the physical partitions were committed to disk, setup proceeded to format each volume based on the directives in the [VOLUMES] section. Partitions were formatted with their original file system types and default cluster configurations, restoring their drive letters and volume identifiers so they matched the exact pre-crash environment.

Transition to Data Restoration

Once disk partitioning and formatting were complete, Text-Mode Setup installed a minimal, temporary Windows installation environment onto the system drive. The machine then rebooted into the graphical phase of setup, where ASR launched the backup restoration tool to stream user files, system state components, and the registry back onto the newly prepared partitions. Because the partition geometry and drive letters were identical to the original system, the operating system and installed software could boot and function without path or driver conflicts.