Windows Installer 4.5 доступен
ВВЕДЕНИЕ
Microsoft Windows Installer является компонентом операционной системы Windows. Windows Installer обеспечивает стандартную основу для установки и удаления программного обеспечения. Производители программного обеспечения могут создать настройку своих продуктов для использования Установки Windows, чтобы сделать установку программного обеспечения, техническое обслуживание и неустановку простым и простым. Windows Installer 4.5 выпущен с Windows Vista Service Pack 2 (SP2) и Windows Server 2008 SP2. А Windows Installer 4.5 выпущен амебативой для следующих операционных систем:
Windows Server 2003 с пакетом обновления 1 (SP1)
Windows Server 2003 с пакетом обновления 2 (SP2).
Windows Vista SP1
Windows Server 2008
Важный Установщик Windows 5.0 выпущен со следующими операционными системами. Таким образом, Windows Installer 4.5 не применяется к этим операционным системам. Кроме того, для установки Windows 5.0 не используется перераспределителя.
Windows 7 с пакетом обновления 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 с пакетом обновления 1 (SP1)
Windows Server 2012
Windows Server 2012 R2
Как получить установку Windows 4.5 перераспределителя
Перед загрузкой этой перераспределительной версии необходимо определить, работаете ли вы 32-битную или 64-битную версию Windows.
Результат обнаружения автоматической версии
Заметка Если результат автоматического обнаружения не отображается на экране, просмотрите Как определить, работает ли компьютер 32-битной версией или 64-битной версией системы работы Windows.
Скачать Windows Installer 4.5 перераспределительных
Следующий файл доступен для скачивания из Центра загрузки Майкрософт: СкачатьWindows Installer 4.5 .Заметка Проверьте следующую таблицу, чтобы найти файл, который выбрать для вашей операционной системы:
Файлы на выбор из Центра загрузки Майкрософт
Windows XP SP2 Windows XP SP3
Для 32-разрядных: WindowsXP-KB942288-v3-x86.exe Для 64-разрядной: WindowsServer2003-KB942288-v4-x64.exe Для платформы IA64: WindowsServer2003-KB942288-v4-ia64.exe
Windows Server 2003 SP1 Windows Server 2003 SP2
Для 32-разрядных: WindowsServer2003-KB942288-v4-x86.exe Для 64-разрядной: WindowsServer2003-KB942288-v4-x64.exe Для платформы IA64: WindowsServer2003-KB942288-v4-ia64.exe
Windows Vista Windows Vista SP1 Windows Server 2008
Для 32-разрядных: Windows6.0-KB942288-v2-x86.msu Для 64-разрядной: Windows6.0-KB942288-v2-x64.msu Для платформы IA64: Windows6.0-KB942288-v2-ia64.msu
Установка пакета Windows Installer 4.5 требует перезагрузки для успешного обновления необходимых бинарных файлов. Для получения дополнительной информации просмотрите Как получить файлы поддержки Майкрософт из онлайн-сервисов.
Корпорация Майкрософт проверила этот файл на наличие вирусов с помощью последней на момент его публикации версии антивирусного программного обеспечения. Файл хранится на защищенных серверах, что предотвращает его несанкционированное изменение.
Следующие новые и улучшенные функции были реализованы в Windows Installer 4.5.
Транзакция нескольких пакетовВ транзакции с несколькими пакетами можно создать одну транзакцию из нескольких пакетов. В транзакции с несколькими пакетами цепь используется для динамического включения пакетов в транзакцию. Если один или несколько пакетов не устанавливаются, как ожидалось, можно откатить установку.
Встроенный обработчик uIМожно внедрить пользовательский интерфейс (пользовательского интерфейса) в пакет Установки Windows. Это упрощает интеграцию пользовательского пользовательского системы. Вы также можете вызвать встроенный обработчик пульт из элемента Добавления или Удаления программ в панели управления. Или можно вызвать встроенный обработчик uI во время процесса ремонта установки Windows.
Встроенный цепиВстроенный цепь можно использовать для добавления пакетов в транзакцию с несколькими пакетами. Можно использовать встроенный цепь для включения событий установки в нескольких пакетах. Например, можно включить события установки по требованию, события ремонта и удалить события в нескольких пакетах.
Обновление устойчивости к заменеЭта функция позволяет исправить изменения в таблице FeatureComponent во время заменяния.
Устойчивость совместного исправления компонентов во время удаленияЭта функция гарантирует, что самая последняя версия компонента доступна для всех продуктов.
Пользовательское выполнение действий при удалении обновленияЭта функция позволяет обновить или изменить пользовательское действие, чтобы пользовательские действия были вызваны, когда обновление не установлено.
Проблемы, присутствующие в более ранних версиях установки Windows, которые рассматриваются в Windows Installer 4.5, следующие:
Право пользователя SeBackupPrivilege отсутствовало в службе установки Windows. Этот недостаток препятствовал любым пользовательским действиям, которые требовали этого права пользователя.
Некоторые конфиденциальные сравнения имен служб в действии InstallValidate привели к ненужным сообщениям «файлы в использовании» в Windows Vista.
При отсвагивании обновления, добавляемого нового компонента, компонент также не установлен. Это произошло даже в том случае, если компонент был общим для других продуктов.
Patching and Upgrades
Because an installation package can contain the files that make up an application as well the information needed for their installation, Windows Installer can be used to update the application. The installer can update information in the following parts of the installation package:
- The .msi file.
- The files of the application.
- The Windows Installer registration information.
The type of update can be characterized by the changes the update makes to the application’s product code, product version, and package code. The application’s product version is stored in the ProductVersion property. The application’s product code is stored in the ProductCode property. The application’s package code is stored in the Revision Number Summary Property.
An update that changes the application into another product is required to change the ProductCode of the application. For more information about which updates require changing the ProductCode see Changing the Product Code. The update can change the ProductVersion and leave the ProductCode unchanged if future versions of the application will need to differentiate between the updated and nonupdated versions of the current product. The Package Code uniquely identifies the installation package and should always be changed whenever update or upgrade changes any information in the installation package.
When deciding whether to change the product version, you should consider If future versions of the application will need to differentiate between the updated and nonupdated versions of the current product. To ensure differentiation in the future, a minor upgrade should be used instead of a small update.
- If an update changes the .msi file and application files, but does not change the ProductCode property or ProductVersion property, it is termed a small update.
- If the update changes the ProductVersion, but does not change the ProductCode, it is termed a minor upgrade.
- If the update changes the installation into an entirely different product, the ProductCode must change and the update is termed a major upgrade.
To ensure differentiation of versions of the current product in the future, a minor upgrade should be used instead of a small update.
The following table summarizes the different types of updates.
| Type of update | Productcode | ProductVersion | Description |
|---|---|---|---|
| Small Update | No change | No change | An update to one or two files that is too small to warrant changing the ProductVersion. The package code in the Revision Number Summary Property does change. Can be shipped as a full installation package or as a patch package. |
| Minor Upgrade | No change | Changed | A small update making changes significant enough to warrant changing the ProductVersion property. Can be shipped as a full installation package or as a patch package. |
| Major Upgrades | Changed | Changed | A comprehensive update of the product warranting a change in the ProductCode property. Shipped as a patch package or as a full product installation package. |
The Windows Installer can install an application, or an update, for all users of a computer (per-machine context) or for a particular user (per-user context) depending on the access privileges of the user, the value of the ALLUSERS property, and the version of the operating system. Application developers should consider in which context updates will be installed. If the contexts of the application and update are different, the application may not be updated as expected.
Users can update to an application by reinstalling a Windows Installer package for the application. Note that Minor Upgrades can be applied in the same way as Small Updates. For more information about updating an application by reinstalling the application, see these sections:
An update to an application can be provided to users as a Windows Installer patch package. A patch can contain an entire file or only the file bits necessary to update part of a file. This means that the user can download an upgrade patch that is much smaller than the entire product and that preserves user customizations through the upgrade. Note that Minor Upgrades can be applied in the same way as Small Updates. For more information about updating an application using a patch, see these sections:
Install method of the Win32_Product class
The static Install WMI class method installs an associated Win32_Product instance using the installation package provided through the PackageLocation parameter, and any supplied command line options.
For more information about support or requirements for installation on a specific operating system, see Operating System Availability of WMI Components.
This topic uses Managed Object Format (MOF) syntax. For more information about using this method, see Calling a Method.
Syntax
Parameters
Path to the Installer package, which is relative to the computer on which the software is being installed and which can be referenced using a Universal Naming Convention (UNC) path.
Command-line options required for installing the software. Format as property**=**setting. If no options are required, this parameter should be left blank.
Boolean value that indicates whether the software should be available to all the users on a computer or just the currently logged-on user. If True, the software will be installed under the All Users profile. If set to False, the software will be installed under the profile of the user whose credentials are being used to run the script. For example, if the script is running under the Administrator account, the software will be installed under the Administrator profile and thus will not be accessible to other users.
Return value
| Return code | Description |
|---|---|
| 0 | Successful completion |
| 13 | The data is invalid. |
| 87 | One of the parameters was invalid. |
| 120 | This value is returned when a custom action attempts to call a function that cannot be called from custom actions. The function returns the value ERROR_CALL_NOT_IMPLEMENTED. Available beginning with Windows Installer version 3.0. |
| 1259 | This error code only occurs when using Windows Installer version 2.0 and Windows XP. If Windows Installer determines a product may be incompatible with the current operating system, it displays a dialog box informing the user and asking whether to try to install anyway. This error code is returned if the user chooses not to try the installation. |
| 1601 | The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered. |
| 1602 | The user cancels the installation. |
| 1603 | A fatal error occurred during the installation. |
| 1604 | Installation suspended, incomplete. |
| 1605 | This action is only valid for products that are currently installed. |
| 1606 | The feature identifier is not registered. |
| 1607 | The component identifier is not registered. |
| 1608 | This is an unknown property. |
| 1609 | The handle is in an invalid state. |
| 1610 | The configuration data for this product is corrupt. Contact your support personnel. |
| 1611 | The component qualifier is not present. |
| 1612 | The installation source for this product is not available. Verify that the source exists and that you can access it. |
| 1613 | This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. |
| 1614 | The product is un-installed. |
| 1615 | The SQL query syntax is invalid or unsupported. |
| 1616 | The record field does not exist. |
| 1618 | Another installation is already in progress. Complete that installation before proceeding with this install. |
| 1619 | This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package. |
| 1620 | This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. |
| 1621 | There was an error when starting the Windows Installer service user interface. Contact your support personnel. |
| 1622 | There was an error opening installation log file. Verify that the specified log file location exists and is writable. |
| 1623 | This language of this installation package is not supported by your system. |
| 1624 | There was an error applying transforms. Verify that the specified transform paths are valid. |
| 1625 | This installation is forbidden by system policy. Contact your system administrator. |
| 1626 | The function could not be executed. |
| 1627 | The function failed during execution. |
| 1628 | An invalid or unknown table was specified. |
| 1629 | The data supplied is the wrong type. |
| 1630 | Data of this type is not supported. |
| 1631 | The Windows Installer service failed to start. Contact your support personnel. |
| 1632 | The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it. |
| 1633 | This installation package is not supported on this platform. Contact your application vendor. |
| 1634 | Component is not used on this machine. |
| 1635 | This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package. |
| 1636 | This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package. |
| 1637 | This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. |
| 1638 | Another version of this product is already installed. Installation of this version cannot continue. |
| 1639 | Invalid command line argument. Consult the Windows Installer SDK for detailed command-line help. |
| 1640 | Installation from a Terminal Server client session is not permitted for the current user. |
| 1641 | The installer has initiated a restart. This message is indicative of a success. This error code is not available on Windows Installer version 1.0. |
| 1642 | The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. This error code is not available on Windows Installer version 1.0. |
| 1643 | The patch package is not permitted by system policy. This error code is available with Windows Installer version 2.0. |
| 1644 | One or more customizations are not permitted by system policy. This error code is available with Windows Installer version 2.0. |
| 1645 | Windows Installer does not permit installation from a Remote Desktop Connection. Available beginning with Windows Installer version 2.0 for Windows Server 2003. |
| 1646 | The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0. |
| 1647 | The patch is not applied to this product. Available beginning with Windows Installer version 3.0. |
| 1648 | No valid sequence could be found for the set of patches. Available beginning with Windows Installer version 3.0. |
| 1649 | Patch removal was disallowed by policy. Available beginning with Windows Installer version 3.0. |
| 1650 | The XML patch data is invalid. Available beginning with Windows Installer version 3.0. |
| 1651 | Administrative user failed to apply patch for a per-user managed or a per-machine application that is in advertise state. Available beginning with Windows Installer version 3.0. |
| 3010 | A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0. |
| 2147549445 | RPC Server Fault Error |
Remarks
The ability to install software without using Group Policy can be an enormous boon to administrators; this allows you to install software without requiring user interaction and without requiring the user to log off and log on or the computer to restart. In addition, a WMI script can help ensure a successful installation by doing such things as checking for available memory or available disk space before beginning the installation process. If there is not enough memory or disk space on the target computer, your script can terminate without installing the software. This prevents any problems that can occur from attempting to install software on computers not capable of running that software.
The install method of Win32_Product can be used to install software on the local or remote computer.
Examples
The following VBScript sample installs software for all users on a local computer.
The following VBScript sample installs software for all users on a remote computer.
