Windows Installer
Purpose
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. The installer provides new capabilities to advertise features without installing them, to install products on demand, and to add user customizations.
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 will be released with, and require Windows Server 2008 R2 or Windows 7. 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 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 Redistributables are available for Windows Installer 4.5 and earlier versions. There is no redistributable available for Windows Installer 4.0.
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.
You can find all the available Windows Installer redistributables at the Microsoft Download Center.
In this section
| Topic | Description |
|---|---|
|
A guide to Windows Installer documentation. | |
|
General information about the installer. | |
|
Lists additions and changes to Windows Installer. | |
|
Documentation of Windows Installer functions. | |
|
Windows Installer examples using script. |
Send comments about this topic to Microsoft
Build date: 9/7/2011
- 1/11/2012
- Lsquared22
- 1/1/2012
- Harufy
- 12/27/2011
- rosevillechica
- 12/17/2011
- Monarch458
"This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package"
The error code is 1620.
Any help?
- 11/7/2008
- Rob Mensching
- 11/20/2011
- r duggan
- 8/3/2011
- daulat mundae
- 7/7/2011
- wmBrown
- 7/4/2011
- ALOK CHANDRA SINGH
Microsoft claim, over and over again, that what I've sent them countless evidence of...is not possible. Then today, I find this page.
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.
Run-Time Requirements
Windows Installer 5.0 will be released with, and require Windows Server 2008 R2 or Windows 7.
There is no Windows Installer of any kind on my Genuine Advantage Windows 7 Ultimate (64x, 86x), Home Professional (86x), Starter (86x), XP (86x) installed operating systems. I have paid thousands of dollars for these discs and the computers they have corrupted.
I paid $600 to Microsoft Emergency Tech Support to remote access my PC and for two hours, I showed three of them all the symptoms of the horrifically corrupted Windows image installed on my drive. In three hours, they provided zero solutions. Claimed to be clueless about what was happening.
How do I get out of this insanity? New computers are corrupted with this identical image minutes after I purchase them. Computers that have never had Windows of any kind touch their drives. They'll show ActiveX symbols and desktop.ini files magically communicated into the 'Recovery' partition of a computer which has never had its networking adapters switched on (deactivated hard and soft in BIOS and external switch), instantly corrupting the drive. PERMANENTLY.
Help me, please!
- 7/3/2011
- jonnygs1
User Account Control displays press continue the application displays a progress bar then stops and displays a dialog box
Saying "Not enough storage space is available to process this command" press ok and a further dialog box displays
Saying "Installation not complete" press ok and it all stops
My C: drive has 38GB of 137GB available free
Can anyone help
John
- 6/30/2011
- JohnEC50
- 6/18/2011
- error 1321 cannot install anything
- 1/3/2011
- imromeosgi
- 6/1/2011
- kfisherman
- 2/8/2011
- shannontrey
- 5/14/2011
- FlickRr01
Then a window opens up called “Client Security-Password Manager and another “Client Security Password Manager-Internal error 25002”. I can remove these temporarily by clicking
Cancel 4 or 5 times. This all started 10-28-10 when I cancelled abruptly a software download.
Can you help me remove these two windows permanently?
- 1/2/2011
- paponando
- 12/28/2010
- debo instalar window installar
hr: 0X80040001 gracias
- 12/23/2010
- eduguille
- 1/29/2009
- Robert Flaming - MSFT
- 12/18/2010
- lonelyheart
A: Zrušení registrace a zaregistrovat Windows Installer
Z tohoto
1. On "Start "menu klikněte na "Běh :.
2. V "Open "zadejte "msiexec / Unreg" a stiskněte klávesu ENTER.
3. On "Start "menu klikněte na "Run ".
4. V "Open "zadejte "msiexec / regserver" a stiskněte klávesu ENTER.
Já taky tried tato a ono did ne nález ono dosadit , Nainstaloval jsem z této stránky , a říká, že nenainstaloval správně a ještě neprokazuje , že instalované v rámci programů na ovládacím panelu je uveden s 0 kousnutí ....... ....
může někdo pomoci ?
Já taky nelze přeinstalovat operační systém , aby správně
- 8/16/2009
- Darrel Lancaster
- 12/18/2010
- xooxoxoxo
The following solutions have resolved this error in the majority of cases:
- Make sure short file name creation is enabled on the target machine. You can check to ensure that the target machine does not have short file name creation disabled by navigating to the following registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
Make sure the value "NtfsDisable8dot3NameCreation" is equal to 0. This indicates that short file name creation is enabled. A value of 1 indicates that this functionality is disabled. You should change the value to 0.
After modifying this value, the target machine should be rebooted before attempting to launch the setup again.
Note: If the target machine should normally have short file name creation disabled, it can be disabled after the install completes by resetting "NtfsDisable8dot3NameCreation" to 1 and rebooting. - To ensure that the Windows Installer Service is properly installed and configured, it is recommended that users install the file InstmsiA.exe on Windows 95/98/Me or InstmsiW.exe on Win NT systems. These files are shipped with your InstallShield product and are located in the following location:
<Product Path>\Redist\Language Independent\i386
- Empty all temporary folders. The specific temporary folders for a machine can be determined by accessing the DOS prompt and typing set. Note the values listed for TEMP and TMP, and delete all files in those locations.
- Make sure no other applications, including utilities such as virus scanners, are running in the background. Close all running applications and utilities, and launch the installation again. ( it would be better you install the software in CLEAN BOOT MODE)
- If this error occurs during un-installation, use the Microsoft Windows Installer CleanUp utility to uninstall the installation.
- Once the installation has been successfully un-installed, you can then debug the project to determine what caused the original error.
- 7/11/2009
- lance440
- 11/30/2010
- Barbara38mama
- 11/4/2010
- perplexed1
hi, please help. having trouble downloading itunes 9.2. error message comes up saying that windows installer service could not be accessed. this can occur if it is not installed correctly. contact support personnel for assistance.... have been looking through the thousands of sites and forums with no luck
try installer 4.5
Thanks
Gary
- 9/10/2010
- Gary Young
- 10/4/2010
- vapz
Start
Run
type
msiexec.exe /?
click OK
[tfl - 19 07 10] Hi - and thanks for your post. You should post questions like this to the MSDN Forums at http://forums.microsoft.com/msdn or the MSDN Newsgroups at http://www.microsoft.com/communities/newsgroups/en-us/. You are much more likely get a quicker response using the forums than through the Community Content. For specific help about:
Visual Studio : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.vstudio%2C&
SQL Server : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.sqlserver%2C&
.NET Framework : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public.dotnet.framework
PowerShell : http://groups.google.com/group/microsoft.public.windows.powershell/topics?pli=1
All Public : http://groups.google.com/groups/dir?sel=usenet%3Dmicrosoft.public%2C&
- 4/16/2009
- Sonny Crockett
- 10/4/2010
- vapz