How Windows 95 Handled System Restore Tasks

Before the introduction of modern recovery environments and Automated System Recovery (ASR), recovering a corrupted Windows 95 installation was a largely manual, decentralized process. Without automated rollback points or shadow copies, users and administrators relied on DOS-level troubleshooting, hidden Registry backups, utility floppy disks, and manual file replacement to revive an unbootable operating system.

The Foundation: Reliance on MS-DOS Mode

Because Windows 95 was built on top of an MS-DOS foundation, MS-DOS served as the primary recovery platform. If Windows failed to boot into the graphical user interface, pressing F8 during the boot phase summoned the Windows 95 Startup Menu. This allowed users to boot into Safe Mode—which loaded minimal drivers—or bypass the GUI entirely into a pure MS-DOS command prompt. From the command prompt, critical system files could be inspected, modified, or restored without the Windows operating system locking them.

Manual Registry Restoration

The configuration core of Windows 95 resided in two hidden files located in the C:\WINDOWS directory: SYSTEM.DAT and USER.DAT. If a driver or application corrupted these files, Windows 95 could not load.

Windows 95 provided a rudimentary automated safeguard: upon every successful boot, it created hidden backup copies of these files named SYSTEM.DA0 and USER.DA0. To recover from a catastrophic Registry failure, users had to boot into MS-DOS and manually replace the corrupted files using command-line instructions. This required using the ATTRIB command to remove hidden, system, and read-only attributes, copying the .DA0 files over the .DAT files, and rebooting the machine.

The Emergency Recovery Utility (ERU)

Microsoft included a specialized tool on the Windows 95 installation CD named the Emergency Recovery Utility (ERU.EXE), located within the Other\Misc\Eru folder.

ERU allowed users to proactively back up crucial system configuration files directly to a floppy disk or custom directory. The utility backed up:

  • SYSTEM.DAT and USER.DAT
  • WIN.INI and SYSTEM.INI
  • AUTOEXEC.BAT and CONFIG.SYS
  • COMMAND.COM, IO.SYS, and MSDOS.SYS

Along with these files, ERU placed a restoration executable (ERD.EXE) on the recovery disk. If the operating system became unstable, users could boot from a floppy and run ERD.EXE to restore original configurations with a single command.

The Windows 95 Startup Disk

During installation, Windows 95 prompted the user to create a Startup Disk (an Emergency Boot Disk on a 1.44 MB floppy). This disk contained a minimal DOS environment with critical recovery tools such as FDISK, FORMAT, SYS.COM, and SCANDISK.

If the Master Boot Record (MBR) was damaged or the primary DOS boot files were missing, the startup disk allowed users to boot the computer, repair disk structures, and execute SYS C: to transfer fresh boot files to the system drive.

In-Place Reinstallations

When manual Registry replacement and file repairs failed to solve system instability or missing DLL issues, the standard recovery procedure was an "in-place reinstallation." Users booted from the startup disk or DOS, navigated to the Windows setup files on their CD-ROM or local hard drive, and ran SETUP.EXE.

Windows 95 would recognize the existing installation and rewrite the core system files, drivers, and dynamic link libraries while leaving personal files, installed third-party programs, and general settings intact.