Windows X86 Msi Installer

[Lara Preece]

Ifyou're looking for a Redistributable for Windows Installer 4.5 and earlier, see Windows Installer Redistributables. There's no Redistributable for Windows Installer 5.0. This version is included with the operating system 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 doesn't 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 can't 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 more information, see Securing resources.

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.

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 hasn't been signed by Microsoft can't 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.

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.

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.0 requires Windows Vista or Windows Server 2008. There's no Redistributable for installing Windows Installer 4.0 on other operating systems. An updated version of Windows Installer 4.0, which doesn't add any new features, is available in Windows Vista with Service Pack 1 and Windows Server 2008.

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. It's available as a Redistributable for Windows 2000 Server with Service Pack 3 and Windows 2000 Server with Service Pack 4, Windows XP RTM and Windows XP with Service Pack 1, and Windows Server 2003 RTM.

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

Yesterday I ran ESET NOD32 and was notified that my computer was infected with 3 files similar to C:\Windows\Installer\4a824.msi. I was very concerned that my computer was infected, so I did a clean windows 7 install. Now when I run ESET NOD32 I get 1 threat notification for C:\Windows\Installer\4a824.msi. I can't imagine my computer is infected as I just did a clean windows 7 install. Windows update downloaded almost 200 updates, is it possible that Windows Update installed infected files on my computer, or is it likely that this is a false positive?

I tried to submit the file to ESET but it didn't work. It didn't clean the file, and although it said it was quarantined, it said it was unable to move the file and it still shows up as a threat when I do a scan. Do you think I still have a problem? Thanks in advance.

Yes, that would have been helpful, sorry about that. It said: "C:\Windows\Installer\4a824.msi MSI Cabs.w1.cab CAB WINZIPSSRegClean.exe - probably a variant of Win32/Systweak potentially unwanted application - action selection postponed until scan completion." It wouldn't clean it and even after quarntining it, it said it was unable to move the file. I was reluctant to let it delete the file as after researching online, this may be a necessary file for windows to operate correctly (if this is a false positive).

So, I did another clean install and this time I didn't download any windows updates, and NOD32 says my system is clean, so Microsoft is sending me this suspect file as part of it's normal windows update. Is it possible that Microsoft is sending out an infected file/program?

Now Nod32 is telling me that my computer is at risk because there are critical windows updates that need to be installed, but I'm reluctant to let it update as I'm afraid it will infect my computer again. I tried to submit the file to you but even after compressing, it's too big for my email system, and when I right click on the file and use the ESET submission option, it says "file not submitted," again, I suspect due to the size.

I used the recovery disks that came with my computer originaly, a probook from hp, so the software is totally legit. Keep in mind, all was well till I did a windows update - after which I ran NOD32 and it said I had several threats similar to what I posted above.

I did cautiously install the critical updates for windows and NOD32 is still happy. I'm doing the important updates one at a time, then running NOD32. This will obviously take a bit of time, but hopefully I can identify the update that is causing the problems. Thanks for the reply.

I suspect, like you, that this file has been on my computer for quite some time - I clicked on properties for the file and it said it was last accessed about a year ago. Do you think it's possible that Microsoft is sending me an infected file as part of a windows update?

I am not an expert in these areas (although, fairly well versed/experienced). I cannot say for certain, but I find it *highly* unlikely that Microsoft is distributing software via Windows Update (which employs a robust framework in terms of security) that should qualify as a PUA, potentially dangerous application, or outright malware.

I would personally feel a bit more comfortable/validated to hear something back from ESET that explains the reason as to why the file in question is now suddenly flagged as a PUA, but I can only assume it is something to do with a subtle change in the detection logic.

Windows Update didn't install WinZIP on your computer. It's a known fact that WinZIP is bundled with potentially unwanted applications (PUA). PUA is an optional detection; if you think that the benefits of using a particular PUA outweigh the potential risks, you can exclude it from detection by unfolding advanced options in the alert window and selecting "Exclude from detection".

What I did say -- is that I have had both ESET and WinZip on my system for years; and now, for no apparent reason, ESET is suddenly detecting an installed file (and not a newly installed file, mind you -- or a file that has actually been run) as a PUA. Therefore, something did change in a module that is causing ESET to flag a specific file in one of the WinZip directories (see my above note) during normal background scanning operations.

What I inferred, based on this thread, is that there may be something going on with ESET that is causing it to be slightly more aggressive than it had been before last week in terms of PUAs -- if indeed ESET is flagging MSI files that are being downloaded with Windows Update.

3a8082e126