How Windows 98 Handled Corrupt Startup Files

Windows 98 handled corrupt system files during startup through a combination of automated registry restoration, driver-level error catching, and dedicated recovery modes. Unlike modern operating systems with background silent repairs, Windows 98 relied heavily on early boot-stage utilities like the Registry Checker, diagnostic fallback states like Safe Mode, and manual extraction tools to resolve system corruption before reaching the desktop.

The Role of Registry Checker (Scanreg)

The registry was the most vulnerable set of files in Windows 98. To protect core files like SYSTEM.DAT and USER.DAT, Windows 98 executed the Registry Checker (SCANREG.EXE) during the early MS-DOS phase of boot.

  • Integrity Scanning: SCANREG.EXE verified the registry's data structure and checksums before the graphical user interface initialized.
  • Automated Rollback: If corruption was detected, the utility halted the standard boot process and automatically restored the most recent clean backup from compressed archive files (RB000.CAB through RB005.CAB) stored in the \Windows\Sysbckup directory.
  • DOS Recovery: If automated recovery failed, users were dropped into MS-DOS mode, where they could manually run scanreg /restore to select a specific working backup from the past five days.

Virtual Device Drivers (VxD) and Core File Halts

When critical dynamic-link libraries, executable files, or Virtual Device Drivers (.VXD) failed to load or were corrupted, the bootloader intervened before the desktop loaded:

  • Missing/Corrupt File Prompts: The system displayed a text-mode warning stating that a required device file was missing or damaged, identifying the specific file path or entry in SYSTEM.INI.
  • Bypass Execution: In many non-fatal cases, pressing a key allowed the system to bypass the corrupt driver and attempt loading the operating system with reduced hardware functionality.
  • Blue Screen Exception: If a corrupted file was critical to kernel operation (such as VMM32.VXD, KRNL386.EXE, or GDI.EXE), the system threw a fatal blue screen exception, halting the boot entirely to prevent filesystem damage.

Fallback to Safe Mode

When Windows 98 detected that a previous startup attempt had failed unexpectedly, it automatically bypassed standard configuration files and presented the Windows Startup Menu.

  • Minimal Loading: Selecting Safe Mode forced the operating system to load without startup programs, bypassing AUTOEXEC.BAT, CONFIG.SYS, and the standard registry hardware configurations.
  • Generic Drivers: Windows bypassed third-party hardware drivers in favor of generic fallback drivers, such as standard VGA display drivers, allowing the user to reach the GUI despite corrupted hardware drivers.

Manual Repair with System File Checker and CAB Extraction

Because Windows 98 lacked the automated background file-locking mechanisms found in newer systems, corruption of generic system files often required manual resolution once basic access was restored:

  • System File Checker (SFC): Windows 98 introduced SFC.EXE, an administrative tool used within Windows or Safe Mode. It scanned system directories for modified, deleted, or corrupted files, comparing them against an initial baseline database.
  • Cabinet (CAB) Extraction: When a corrupted file was verified, users used SFC or the command-line utility EXTRACT.EXE to pull clean copies of system files directly from the Windows 98 installation CD archives.
  • Emergency Startup Disk: For failures where the operating system could not boot at all, users relied on the 3.5-inch floppy Startup Disk, which provided real-mode CD-ROM drivers, format tools, and MS-DOS utilities to replace damaged files manually.