Windows Setup
Windows Setup is a bootable program developed by Microsoft that installs or upgrades the Windows operating system on compatible hardware, handling tasks such as gathering user input, copying installation files, partitioning and formatting disks, and configuring system settings to prepare the computer for initial use.[1] It supports deployment from various media, including USB drives, ISO images, DVDs, or network shares, and can automate processes using answer files or command-line options for enterprise or customized installations.[1] The modern Windows Setup, introduced with Windows Vista and evolving through subsequent releases, ensures compatibility with modern hardware features like Secure Boot and UEFI firmware while providing options for clean installs, upgrades, or repairs.[1] As of 2024, Windows Setup for Windows 11 includes a revamped user interface based on the Upgrade Assistant.[2] The installation process occurs in distinct phases, beginning with the Windows Preinstallation Environment (Windows PE), a lightweight version of Windows that loads first to collect information, apply initial configurations, and prepare the disk for the full OS image.[3] During this phase, Setup copies the Windows image files, installs drivers and updates via offline servicing, and sets up boot information, often requiring restarts to transition to the next stage.[3] Following Windows PE, the online configuration phase customizes the installation by applying settings for the target environment, such as user accounts, network configurations, and software packages, without user interaction if automated.[3] The process concludes with the Windows Welcome or Out-of-Box Experience (OOBE), where final user-specific setups like account creation and privacy options are handled before the desktop loads.[3] Key features of Windows Setup include support for unattended installations through tools like Windows System Image Manager for creating answer files, integration with deployment tools such as Microsoft Deployment Toolkit (MDT), and command-line options like/auto for streamlined upgrades in volume licensing scenarios.[4] It also facilitates disk management, allowing partitioning, formatting, and conversion between BIOS and UEFI modes, while incorporating security measures like BitLocker encryption prompts during setup.[1] For IT professionals, Windows Setup enables scalable deployments across organizations by integrating with Windows Autopilot for cloud-based provisioning, reducing manual intervention in modern environments.[5]
Early Windows Versions
Windows 1.x and 2.x
Windows 1.x, released in 1985, and Windows 2.x, released between 1987 and 1989, functioned primarily as graphical shells layered atop a pre-installed MS-DOS operating system, necessitating manual intervention for all aspects of installation and configuration.[6][7] These versions required MS-DOS 2.0 or later as the base OS, with users booting into the DOS environment before initiating setup.[8] The process began by inserting the first installation floppy disk—typically 5.25-inch double-sided or 3.5-inch disks—and running the text-based SETUP.EXE command from the DOS prompt, such as by typingsetup after navigating to the A: drive.[9]
Installation involved manually copying files from multiple floppy disks (often three to five, depending on the edition and media type) to the hard drive or, less commonly, a second floppy for systems without fixed storage.[7][10] Users swapped disks as prompted by the setup program, a process that typically took 30 to 60 minutes due to the sequential nature of the media and limited hardware speeds of the era.[6] There was no graphical installer; the entire procedure remained text-based, relying on DOS commands and prompts, which made it error-prone without automatic hardware detection. System limitations, including a maximum of 640 KB conventional RAM under MS-DOS, further constrained the setup to basic 8088-based PCs with compatible graphics adapters like CGA, Hercules monochrome, or EGA.[7][8]
Hardware configuration demanded user input during setup prompts for peripherals such as mice, printers, and displays, with no automated detection available. For instance, users specified mouse type (e.g., serial or bus mouse) and printer models via on-screen questions, after which the installer might suggest or require manual edits to CONFIG.SYS for device drivers and AUTOEXEC.BAT for loading utilities like MOUSE.COM.[9] Windows 2.x introduced minor refinements, such as support for VGA displays and slightly higher minimum RAM (512 KB), but retained the same manual, prompt-driven approach for peripherals.[11]
Once installed, Windows launched via command-line execution of WIN.COM from the DOS prompt or by integrating the win command into AUTOEXEC.BAT for automatic startup at boot time.[12] This DOS-dependent method highlighted the shells' role as extensions rather than standalone systems, paving the way for more automated processes in subsequent versions like Windows 3.x.[6]