Windows Setup Scenarios and Best Practices
Windows Setup installs the Windows operating system. Windows Setup uses a technology called Image-based Setup (IBS) that provides a single, unified process with which all customers can install Windows. IBS performs clean installations and upgrades of Windows and is used in both client and server installations. Windows Setup also enables you to customize Windows during installation by using Setup answer file settings.
In this topic:
Common Usage Scenarios
Common installation scenarios include performing clean installations, upgrades, and unattended installations.
Custom Installations
The most common scenario for Windows Setup is performing a custom installation. In this scenario, you install Windows onto a computer that does not have an operating system, or has a previous version of Windows. This scenario consists of the following stages:
Run Setup.exe from your Windows product DVD or network share.
Select the Custom installation type.
If you are installing from a previous installation of Windows, Windows Setup creates a local boot directory and copies all of the required Windows Setup files to this directory.
Windows Setup reboots, installs and configures Windows components, and, after installation is complete, launches Windows Welcome.
Custom installations do not migrate any settings or preferences from previously installed versions of Windows. Files from previous Windows versions are copied to a \Windows.old directory. All data from the Windows installation including the Users, Program Files, and Windows directories are saved to this directory.
Upgrades
Windows Setup can also perform upgrades from a supported operating system.
This scenario includes the following stages:
Run Setup.exe on the previous version of Windows.
Select the Upgrade installation type. Windows Setup upgrades the system and protects your files, settings, and preferences during the installation process.
Windows Setup reboots and restores your protected files, settings, and preferences. Windows Setup then launches Windows Welcome.
Notes
- Upgrades are used to upgrade a single computer to a newer version of Windows.
- Upgrades support migrating user data to a new system.
- Upgrades support the following customizations of the Windows image. This is not a change in Windows Setup support policy but instead a clarification:
- Applying a cumulative (quality) update
- Applying updates to the servicing stack necessary to complete the feature update (see Servicing stack updates for more information)
- Applying updates to Setup.exe binaries or other files that Setup uses for feature updates
- Applying updates for the "safe operating system" (SafeOS) that is used for the Windows recovery environment
- Adding or removing languages
- Adding or removing Features on Demand
For clarity, Windows Setup does not support upgrades to a Windows image that has been customized by adding / removing / changing applications, settings nor drivers.
Automated Installations
Automated installations enable you to customize a Windows installation and remove the need for a user to interact with Windows Setup. By using Windows System Image Manager (Windows SIM) or the Component Platform Interface (CPI) APIs, you can create one or more customized Windows installations that can then be deployed across many different hardware configurations.
The automated installation, also called an unattended installation, scenario includes the following stages:
Use Windows SIM or the CPI APIs to create an unattended installation answer file, typically called Unattend.xml. This answer file contains all of the settings that you configure in the Windows image. For more information, see Windows System Image Manager How-to Topics.
From Windows PE, a previous version of Windows, or another preinstallation environment, run Setup.exe with the explicit path to the answer file. If you do not include the path to the answer file, Setup.exe searches for a valid answer file in several specific locations. For more information, see Windows Setup Command-Line Options.
Windows Setup then installs the operating system and configures all settings listed in the answer file. Additional applications, device drivers, and updates can also be installed during Windows Setup. After the operating system is installed, Setup launches Windows Welcome.
Windows Setup Best Practices
The following section describes some of the best practices to use with Windows Setup.
Verify that there is sufficient space for Windows Setup temporary files. If you run setup from a previous version of Windows, verify that there is sufficient space on the disk for temporary Windows Setup files. The space that is required may vary, but it can be up to 500 megabytes (MB).
Previous Windows installations are moved to a Windows.old folder. As a best practice, you should back up your data before you upgrade. If you install Windows over a previous Windows installation, all previous Windows files and directories are moved to a Windows.old folder, including the contents of the Users, Program Files, and Windows directories. You can access your data in the Windows.old folder after Windows Setup completes. If you have additional folders not in the Users, Program Files, or Windows directories, those folders are not moved. For example, if you have a folder that is named C:\Drivers, that folder will not be moved to the Windows.old folder.
Review the Windows Setup log files. If you experience problems during Windows Setup, review the log files in %WINDIR%\panther. You will be able to identify and troubleshoot many issues by reviewing the installation log files. For more information, see Deployment Troubleshooting and Log Files and Windows Setup Log Files and Event Logs.
Windows Setup Limitations
The following sections describe some of the limitations of Windows Setup. Review this section before you run Windows Setup.
Enable UEFI-compatibility mode to install to an UEFI-based computer. On some UEFI computers, you cannot install Windows in BIOS-compatibility mode. You may need to switch to UEFI-compatibility mode.
Applications might require a consistent drive letter. If you install custom applications to your Windows image, install Windows to the same drive letter on the destination computer, because some applications require a consistent drive letter. Uninstallation, servicing, and repair scenarios might not function appropriately if the drive letter of the system does not match the drive letter specified in the application. This limitation applies to both the Deployment Image Servicing and Management (DISM) tool and Windows Setup.
Deploying multiple images to multiple partitions. If you capture and deploy multiple images on multiple partitions, the following requirements must be fulfilled:
The partition structure, bus location, and number of disks must be identical on the reference and destination computers.
The partition types (primary, extended, or logical) must match. The active partition on the reference computer must match that of the destination computer.
Installing Custom .wim files requires a description value in the .wim file. When you create a custom .wim file, Windows Setup requires that you always include a description value. If a .wim file does not include a description value, the image may not install correctly. You can provide a description value when you use the dism command with the /capture-image option. If you install a .wim file that does not have a description value, recapture the image and provide a valid description value. For more information, see the DISM - Deployment Image Servicing and Management Technical Reference for Windows.
Note For Windows Preinstallation Environment (Windows PE), the version of boot files must match the computer architecture. An x64 UEFI computer can only boot by using Windows PE x64 boot files. An x86 computer can only boot by using Windows PE x86 boot files. This is different from legacy BIOS. In legacy BIOS, an x64 computer can boot by using x86 boot files.
Related topics
Windows Setup Installation Process
Windows Setup Automation Overview
Windows Setup Configuration Passes
Windows Setup Supported Platforms and Cross-Platform Deployments