Create installation media for Windows

You can use installation media (a USB flash drive or DVD) to install a new copy of Windows, perform a clean installation, or reinstall Windows 10.

To create installation media, go to the software download website, where you’ll find step-by-step instructions. On that website, you can select a version of Windows and create your own installation media using either a USB flash drive or a DVD. To go directly to one of the versions, select one of these links:

Windows 10 (Then select Download tool now.)

Important: Back up your files before you install or reinstall Windows on your PC. Learn how for Windows 10 or for Windows 7 and Windows 8.1.

To create the installation media, here’s what you’ll need:

A PC with a reliable internet connection. The download time will vary, depending on your internet connection.

A USB flash drive or DVD. A blank USB flash drive with at least 8 GB of space, or a blank DVD (and DVD burner). We recommend using a blank USB or blank DVD because any content on it will be deleted. When burning a DVD from an ISO file, if you’re told the disc image file is too large, you’ll need to use dual layer (DL) DVD media.

A product key. Your 25-character product key (not required for digital licenses). For help finding it, go to Find your Windows product key.

After you’ve created the installation media, you can reset or reinstall Windows. To learn more, go to Recovery options in Windows 10.

Создание файла Установщика приложений вручную Create an App Installer file manually

В этой статье показано, как вручную создать файл установщика приложения, который определяет связанный набор. This article shows how to manually create an App Installer file that defines a related set. Связанный набор — это не один объект, а сочетание основного и дополнительных пакетов. A related set is not one entity, but rather a combination of a main package and optional packages.

Чтобы получить возможность установить связанный набор как один объект, необходимо указать основной и дополнительные пакеты как один объект. To be able to install a related set as one entity, we must be able to specify the main package and optional package as one. Для этого необходимо создать XML-файл с расширением appinstaller , чтобы определить связанный набор. To do this, we will need to create an XML file with an .appinstaller extension to define a related set. Установщик приложения использует файл appinstaller и позволяет пользователю установить все определенные пакеты одним щелчком. App Installer consumes the .appinstaller file and allows the user to install all of the defined packages with a single click.

Пример файла установщика приложения App Installer file example

Прежде чем мы перейдем к более подробной информации, ниже приведен полный пример файла msixbundle *. appinstaller: Before we go in to more detail, here is a complete sample msixbundle *.appinstaller file:

При развертывании файл Установщика приложений сверяется с пакетами приложений, на которые ссылается элемент Uri . During deployment, the App Installer file is validated against the app packages referenced in the Uri element. таким образом, значения Name , Publisher и Version должны соответствовать элементу Package/Identity в манифесте пакета приложения. So, the Name , Publisher and Version should match the Package/Identity element in the app package manifest.

Инструкции по созданию файла Установщика приложений. How to create an App Installer file

Для распределения связанного набора как одного объекта необходимо создать файл Установщика приложений, содержащий элементы, которые требуются соответствующей схеме Установщика приложений. To distribute your related set as one entity, you must create an App Installer file that contains the elements that are required by that appinstaller schema.

Шаг 1. Создание файла *.appinstaller Step 1: Create the *.appinstaller file

Используя текстовый редактор, создайте файл (который будет содержать XML) и назовите его .appinstaller Using a text editor, create a file (which will contain XML) and name it .appinstaller

Шаг 2. Добавление базового шаблона Step 2: Add the basic template

Базовый шаблон включает в себя сведения о файле Установщика приложений. The basic template includes the App Installer file information.

Шаг 3. Добавление сведений об основном пакете Step 3: Add the main package information

Если основным пакетом приложения является файл. msix или. appx, используйте , как показано ниже. If the main app package is an .msix or .appx file, then use , as shown below. Обязательно включите ProcessorArchitecture, так как он обязателен для пакетов, не относящихся к пакету. Be sure to include the ProcessorArchitecture, as it is mandatory for non-bundle packages.

Если основным пакетом приложения является msixbundle или appxbundle или файл, используйте вместо, как показано ниже. If the main app package is an .msixbundle or .appxbundle or file, then use the in place of as shown below. Для пакетов ProcessorArchitecture не требуется. For bundles, ProcessorArchitecture is not required.

Сведения в атрибуте или должны совпадать с элементом Package/Identity в манифесте пакета приложений или пакета приложения соответственно. The information in the or attribute should match the Package/Identity element in the app bundle manifest or app package manifest respectively.

Шаг 4. Добавление дополнительных пакетов Step 4: Add the optional packages

Как и атрибут основного пакета приложений, если дополнительный пакет может являться пакетом приложения или пакетом приложений, дочерний элемент с атрибутом должен являться

или . Similar to the main app package attribute, if the optional package can be either an app package or an app bundle, the child element within the attribute should be

or respectively. Сведения о пакете в дочерних элементах должны соответствовать элементу идентификатора в манифеста пакета приложений или пакета приложения. The package information in the child elements should match the identity element in the bundle or package manifest.

Шаг 5. Добавление зависимостей Step 5: Add dependencies

В элементе зависимостей можно указать требуемые пакеты платформы для основного пакета или дополнительных пакетов. In the dependencies element, you can specify the required framework packages for the main package or the optional packages.

Шаг 6. Добавление параметра обновления Step 6: Add Update setting

В файле Установщика приложений можно также указать параметр обновления, чтобы связанные наборы автоматически обновлялись при публикации нового файла Установщика приложений. The App Installer file can also specify update setting so that the related sets can be automatically updated when a newer App Installer file is published. является необязательным элементом. is an optional element. В параметре OnLaunch указывает, что проверки обновлений должны выполняться при запуске приложения, а хаурсбетвинупдатечеккс = «12» указывает, что проверка обновлений должна выполняться каждые 12 часов. Within the OnLaunch option specifies that update checks should be made on app launch, and HoursBetweenUpdateChecks=»12″ specifies that an update check should be made every 12 hours. Если параметр HoursBetweenUpdateChecks не задан, интервал проверки обновлений по умолчанию — 24 часа. If HoursBetweenUpdateChecks is not specified, the default interval used to check for updates is 24 hours. Дополнительные типы обновлений, например фоновые обновления, можно найти в схемепараметров обновления. Дополнительные типы обновлений для запуска, такие как обновления с запросом, можно найти в схеме OnLaunch. Additional types of updates, like background updates can be found in the Update Settings schema; Additional types of on-launch updates like updates with a prompt can be found in the OnLaunch schema

Полные сведения о схеме XML см. в разделе Справочник по файлу Установщика приложений. For all of the details on the XML schema, see App Installer file reference.

Тип файла установщика приложений является новым в Windows 10, версия 1709 (Windows 10 Creators Update). The App Installer file type is new in Windows 10, version 1709 (the Windows 10 Fall Creators Update). Развертывание приложений Windows 10 с помощью файла установщика приложения в предыдущих версиях Windows 10 не поддерживается. There is no support for deployment of Windows 10 apps using an App Installer file on previous versions of Windows 10. Элемент хаурсбетвинупдатечеккс доступен начиная с Windows 10, версия 1803. The HoursBetweenUpdateChecks element is available starting in Windows 10, version 1803.

Windows Installer

This documentation is intended for software developers who want to use Windows Installer to build installer packages for applications. If you’re looking for a redistributable for Windows Installer 4.5 and earlier, see this article. Note that there is no redistributable for Windows Installer 5.0. This version is included with the OS in Windows 7, Windows ServerВ 2008В R2, and later client and server releases (including Windows 10).

Microsoft Windows Installer is an installation and configuration service provided with Windows. The installer service enables customers to provide better corporate deployment and provides a standard format for component management. The installer also enables the advertisement of applications and features according to the operating system. For more information, see Platform Support of Advertisement.

This documentation describes Windows InstallerВ 5.0 and earlier versions. Not all the capabilities available in later Windows Installer versions are available in earlier versions. This documentation does not describe versions earlier than Windows InstallerВ 2.0. Installation packages and patches that are created for Windows InstallerВ 2.0 can still be installed by using Windows InstallerВ 3.0 and later.

Windows InstallerВ 3.0 and later, can install multiple patches with a single transaction that integrates installation progress, rollback, and reboots. The installer can apply patches in a specified order regardless of the order that the patches are provided to the system. Patching using Windows InstallerВ 3.0 only updates files affected by the patch and can be significantly faster than earlier installer versions. Patches installed with Windows Installer 3.0 or later can be uninstalled in any order to leave the state of the product the same as if the patch was never installed. Accounts with administrator privileges can use the API of Windows InstallerВ 3.0 and later to query and inventory product, feature, component, and patch information. The installer can be used to read, edit, and replace source lists for network, URL, and media sources. Administrators can enumerate across user and install contexts, and manage source lists from an external process.

Windows Installer 4.5 and later can install multiple installation packages using transaction processing. If all the packages in the transaction cannot be installed successfully, or if the user cancels the installation, the Windows Installer can roll back changes and restore the computer to its original state. The installer ensures that all the packages belonging to a multiple-package transaction are installed or none of the packages are installed.

Beginning with Windows Installer 5.0, a package can be authored to secure new accounts, Windows Services, files, folders, and registry keys. The package can specify a security descriptor that denies permissions, specifies inheritance of permissions from a parent resource, or specifies the permissions of a new account. For information, see Securing Resources. The Windows Installer 5.0 service can enumerate all components installed on the computer and obtain the key path for the component. For more information, see Enumerating Components. By Using Services Configuration, Windows Installer 5.0 packages can customize the services on a computer. Setup developers can use Windows Installer 5.0 and Single Package Authoring to develop single installation packages capable of installing an application in either the per-machine or per-user installation context.

Where applicable

Windows Installer enables the efficient installation and configuration of your products and applications running on Windows. The installer provides new capabilities to advertise features without installing them, to install products on demand, and to add user customizations.

Windows Installer 5.0 running on Windows ServerВ 2012 or WindowsВ 8 supports the installation of approved apps on WindowsВ RT. A Windows Installer package, patch, or transform that has not been signed by Microsoft cannot be installed on WindowsВ RT. The Template Summary property indicates the platform that is compatible with an installation database and in this case should include the value for WindowsВ RT.

Windows Installer is intended for the development of desktop style applications.

Developer audience

This documentation is intended for software developers who want to make applications that use Windows Installer. It provides general background information about installation packages and the installer service. It contains complete descriptions of the application programming interface and elements of the installer database. This documentation also contains supplemental information for developers who want to use a table editor or a package creation tool to make or maintain an installation.

Run-time requirements

Windows InstallerВ 5.0 is included with, Windows 7, Windows ServerВ 2008В R2, and later releases. There is no redistributable for Windows Installer 5.0.

Versions earlier than Windows Installer 5.0 were released with Windows ServerВ 2008, WindowsВ Vista, Windows ServerВ 2003, WindowsВ XP, and WindowsВ 2000. Windows Installer Redistributables are available for Windows Installer 4.5 and some earlier versions.

Windows InstallerВ 4.5 requires Windows ServerВ 2008, WindowsВ Vista, WindowsВ XP with Service PackВ 2 (SP2) and later, and Windows ServerВ 2003 with Service PackВ 1 (SP1) and later.

Windows InstallerВ 4.0 requires WindowsВ Vista or Windows ServerВ 2008. There is no redistributable for installing Windows InstallerВ 4.0 on other operating systems. An updated version of Windows InstallerВ 4.0, which does not add any new features, is available in WindowsВ Vista with Service PackВ 1 (SP1) and Windows ServerВ 2008.

Windows InstallerВ 3.1 requires Windows ServerВ 2003, WindowsВ XP, or WindowsВ 2000 with Service PackВ 3 (SP3).

Windows InstallerВ 3.0 requires Windows ServerВ 2003, WindowsВ XP, or WindowsВ 2000 with SP3. Windows InstallerВ 3.0 is included in WindowsВ XP with Service PackВ 2 (SP2). It is available as a redistributable for WindowsВ 2000 Server with Service PackВ 3 (SP3) and WindowsВ 2000 Server with Service PackВ 4 (SP4), WindowsВ XP RTM and WindowsВ XP with Service PackВ 1 (SP1), and Windows ServerВ 2003 RTM.

Windows InstallerВ 2.0 is contained in Windows ServerВ 2003 and WindowsВ XP.

Windows InstallerВ 2.0 is available as a package for installing or upgrading to Windows InstallerВ 2.0 on WindowsВ 2000. This package should not be used to install or upgrade Windows InstallerВ 2.0 on Windows ServerВ 2003 and WindowsВ XP.