How Windows 95 Backed Up the Registry on Boot

Windows 95 relied on an automated, single-generation safety mechanism to protect its central configuration database during system startup. This article explains how the operating system handled the daily boot process by validating the active registry, duplicating critical database files into hidden backup copies, and using those archives as an automated recovery fallback when corruption occurred.

The Core Registry Files

The Windows 95 registry is split into two primary binary files stored in the main Windows directory (typically C:\WINDOWS):

  • SYSTEM.DAT: Contains machine-specific settings, hardware configurations, and device driver information.
  • USER.DAT: Stores user-specific preferences, desktop configurations, and software environments.

Because these files are vital for system stability, Windows 95 required a method to preserve a working state before running newly installed software or device drivers.

Integrity Checks at Startup

When the computer boots, the real-mode operating system loads core system files and initiates the registry check before loading the graphical user interface.

During this initial phase, Windows validates the structure and checksums of SYSTEM.DAT and USER.DAT. The system ensures that the file headers are intact and that the internal tree structure of keys and values can be parsed without read errors.

Generation of the .DA0 Backup Files

If the system boots successfully and confirms that the current registry files are healthy, it creates a backup copy:

  1. Attribute Modification: The operating system removes the file attributes of the existing backup files so they can be overwritten.
  2. Duplication: Windows copies SYSTEM.DAT to SYSTEM.DA0 and USER.DAT to USER.DA0.
  3. Attribute Restoration: The newly created .DA0 files are assigned the Read-Only, Hidden, and System attributes to prevent accidental modification or deletion by standard users and software.

This backup operation occurred once per successful startup session. Unlike later versions of Windows, which scheduled daily compressed archives (such as .CAB files via Windows 98's Registry Checker), Windows 95 maintained only this single prior copy representing the "last known good" bootable configuration.

Automatic Recovery from Boot Corruption

If Windows 95 detects that SYSTEM.DAT or USER.DAT is damaged, missing, or structurally corrupt during the boot sequence, the daily backup logic shifts from backup mode to recovery mode:

  • The boot process halts the normal GUI load sequence.
  • Windows reports the registry error and attempts to substitute the damaged file with the corresponding .DA0 copy.
  • If the .DA0 copy is structurally valid, the system copies SYSTEM.DA0 over SYSTEM.DAT (and USER.DA0 over USER.DAT), allowing the machine to start using the configuration from the previous successful session.
  • If both the primary files and the .DA0 backups are damaged, Windows 95 stops and drops the user to a real-mode MS-DOS prompt, requiring manual restoration via emergency disks or setup utilities.