Windows 95 Setup Log File Format Explained

During installation, Windows 95 recorded system events, hardware detection results, and configuration changes to assist with troubleshooting and crash recovery. This article examines the file format used to record these setup details, outlines the key log files generated during the process, and explains why Microsoft chose this structure for operating system deployment.

Windows 95 primarily stored its installation and setup log details in standard plain text format (.TXT). By saving the installation progress as plain ASCII text, Microsoft ensured that users and system administrators could easily read, search, and troubleshoot installation problems using basic MS-DOS tools like TYPE or EDIT, even if the graphical interface failed to load.

During a typical Windows 95 installation, the setup program generated several specific text files in the root directory (usually C:\) or the Windows directory:

• SETUPLOG.TXT: The primary installation log. It documented the entire setup process in chronological order, recording which files were copied, what directories were created, and which system settings were applied. The file was organized using bracketed section headers and key-value entries, similar to the traditional Windows INI configuration format.
• DETLOG.TXT: A plain text log dedicated to hardware detection. It kept a detailed record of every hardware probe the setup utility executed, listing discovered devices, resource allocations (IRQs, I/O ports, and DMA channels), and any devices that failed detection.
• NETLOG.TXT: A plain text log focused on network architecture installation, tracking the installation of network adapters, protocols, and client services.
• BOOTLOG.TXT: Created upon the initial reboot and subsequent startups, this text log recorded the loading and initialization status of device drivers and system components.

While the diagnostic logs were written in plain text, Windows 95 also created a special binary file named DETCRASH.LOG if the computer froze during the hardware detection phase. Unlike the human-readable text logs, DETCRASH.LOG was a binary state file used exclusively by the Setup engine to identify the exact device probe that caused the crash, allowing the installer to skip that specific hardware check upon rebooting into Safe Recovery mode.