Msiexec exe установщик windows

MSIEXEC.EXE – процесс, который иногда может включаться на Вашем ПК. Давайте разберемся, за что он отвечает и можно ли его отключить.

Сведения о процессе

Увидеть MSIEXEC.EXE можно во вкладке «Процессы» Диспетчера задач.

Картинка с сайта: lumpics.ru

Функции

Системная программа MSIEXEC.EXE является разработкой Microsoft. Она связана с Установщиком Windows и используется для установки новых программ из файла в формате MSI.

Работать MSIEXEC.EXE начинает при запуске установщика, и должен сам завершаться по окончании процесса инсталляции.

Расположение файла

Программа MSIEXEC.EXE должна располагаться по следующему пути:

C:\Windows\System32

Убедиться в этом можно, нажав «Открыть место хранения файла» в контекстном меню процесса.

Картинка с сайта: lumpics.ru

После этого откроется папка, где располагается данный EXE-файл.

Картинка с сайта: lumpics.ru

Завершение процесса

Останавливать работу данного процесса не рекомендуется, особенно при выполнении установки ПО на Ваш компьютер. Из-за этого будет прервана распаковка файлов и новая программа наверняка не будет работать.

Если же необходимость выключения MSIEXEC.EXE всё же возникла, то сделать это можно следующим образом:

1. Выделите этот процесс в перечне Диспетчера задач.
2. Нажмите кнопку «Завершить процесс».


Картинка с сайта: lumpics.ru

3. Ознакомьтесь с появившимся предупреждением и снова нажмите «Завершить процесс».


Картинка с сайта: lumpics.ru

Процесс работает постоянно

Бывает, что MSIEXEC.EXE начинает работать при каждом запуске системы. В этом случае стоит проверить статус службы «Установщик Windows» – возможно, по какой-то причине она запускается автоматически, хотя по умолчанию должно быть ручное включение.

1. Запустите программу «Выполнить», используя комбинацию клавиш Win+R.
2. Пропишите «services.msc» и нажмите «ОК».


Картинка с сайта: lumpics.ru

3. Отыщите службу «Установщик Windows». В графе «Тип запуска» должно стоять значение «Вручную».


Картинка с сайта: lumpics.ru

В противном случае дважды щёлкните по её названию. В появившимся окне свойств можно увидеть название уже знакомого нам исполняемого файла MSIEXEC.EXE. Нажмите кнопку «Остановить», измените тип запуска на «Вручную» и кликните «ОК».

Картинка с сайта: lumpics.ru

Подмена вредоносным ПО

Если Вы ничего не устанавливаете и служба работает как нужно, то под MSIEXEC.EXE может маскироваться вирус. Среди других признаков можно выделить:

• повышенную нагрузку на систему;
• подмену некоторых символов в имени процесса;
• исполняемый файл хранится в другой папке.

Избавиться от вредоносного ПО можно, просканировав компьютер с помощью антивирусной программы, например, Dr.Web CureIt. Также можно попытаться удалить файл, загрузив систему в Безопасном режиме, но Вы должны быть уверены, что это вирус, а не системный файл.

На нашем сайте вы можете узнать о том, как запустить в безопасном режиме Windows XP, Windows 8 и Windows 10.

Читайте также: Проверка компьютера на вирусы без антивируса

Итак, мы выяснили, что MSIEXEC.EXE работает при запуске установщика с расширением MSI. В этот период его лучше не завершать. Запускаться этот процесс может по причине неверных свойств службы «Установщик Windows» или из-за наличия на ПК вредоносного ПО. В последнем случае нужно своевременно решить проблему.

Наша группа в TelegramПолезные советы и помощь

msiexec.exe: The Windows Installer Engine

msiexec.exe is a crucial component of the Windows operating system, responsible for installing, modifying, and removing software packaged as Windows Installer packages (.msi files), Windows Installer patch packages (.msp files), and Windows Installer Transform files (.mst files). It acts as the engine that interprets and executes the instructions contained within these packages. It’s not a standalone application that you typically interact with directly; instead, it’s invoked when you double-click an .msi or .msp file, or when software installation is triggered programmatically.

Purpose and Functionality

The primary purpose of msiexec.exe is to manage the installation process of software on Windows. It handles a wide range of tasks, including:

• Package Interpretation: msiexec.exe reads the instructions embedded within .msi, .msp, and .mst files. These instructions define everything about the installation process, including files to be copied, registry entries to be created, services to be installed, and user interface elements to be displayed.

• File Copying and Extraction: It extracts the necessary files from the installer package and copies them to the appropriate locations on the system.

• Registry Management: It creates, modifies, or deletes registry keys and values as specified by the installation package.

• Service Installation and Configuration: If the software includes Windows services, msiexec.exe registers and configures these services.

• User Interface Handling: It displays the installer’s user interface (if any), allowing users to choose installation options, accept license agreements, and monitor the progress.

• Rollback and Transaction Management: One of the key features of Windows Installer is its ability to roll back an installation if something goes wrong. msiexec.exe keeps track of all changes made during the installation process and, if an error occurs or the user cancels the installation, it can revert the system to its previous state. This ensures system stability and prevents partially installed software from causing problems.

• Uninstallation: msiexec.exe also handles the uninstallation of software. It removes the files, registry entries, and services associated with the application.

• Patching and Upgrading: .msp files, which are Windows Installer patch packages, are applied using msiexec.exe to update existing software.

Is it a Virus? / Can it Become a Virus?

msiexec.exe itself is not a virus. It is a legitimate and essential component of the Windows operating system. However, like any executable, it could be exploited in extremely rare and sophisticated attack scenarios, but this would involve directly modifying the msiexec.exe file itself, which is highly unlikely due to Windows’ built-in security protections (like System File Protection).

The more realistic, though still uncommon, threat lies in malicious .msi or .msp packages. A specially crafted, malicious installer package could be designed to perform harmful actions when executed by msiexec.exe. The danger is not in msiexec.exe itself, but in the package it’s being instructed to install. Always obtain software from trusted sources, and consider using antivirus software to scan downloaded installers.

Command-Line Options

While msiexec.exe is often used implicitly when you double-click an .msi file, it also provides a rich set of command-line options for more advanced control over the installation process. These options allow you to perform silent installations, customize installation settings, generate log files, and more.

Here’s a breakdown of some of the most commonly used command-line options:

• /i <package> or /package <package>: Installs or configures a product. <package> specifies the path to the .msi file.

  • Example: msiexec.exe /i "C:\Downloads\MyApplication.msi"

• /x <package> or /uninstall <package>: Uninstalls a product.

  • Example: msiexec.exe /x "C:\Downloads\MyApplication.msi"

• /a <package>: Administrative installation — Installs a product on the network.

  • Example: msiexec /a "C:\Downloads\MyApplication.msi"

• /p <patch> or /patch <patch>: Applies a patch (.msp file).

  • Example: msiexec.exe /p "C:\Downloads\MyApplicationUpdate.msp"

• /f [p|o|e|d|c|a|u|m|s|v] <package> or /repair <package>: Repairs a product. The options within the brackets control what aspects are repaired:

  • p — Reinstalls only if the file is missing.
  • o — Reinstalls if the file is missing or an older version is installed.
  • e — Reinstalls if the file is missing or an equal or older version is installed.
  • d — Reinstalls if the file is missing or a different version is installed.
  • c — Reinstalls if the file is missing or the stored checksum does not match the calculated value.
  • a — Forces all files to be reinstalled.
  • u — Rewrites all required user-specific registry entries.
  • m — Rewrites all required computer-specific registry entries.
  • s — Overwrites all existing shortcuts.
  • v — Runs from source and re-caches the local package.
  • Example: msiexec.exe /fecms "C:\Downloads\MyApplication.msi" (This would repair the application, reinstalling missing or corrupted files, rewriting registry entries, and recreating shortcuts.)

• /l*v <LogFile>: Enables verbose logging to the specified log file. This is extremely useful for troubleshooting installation problems.

  • Example: msiexec.exe /i "C:\Downloads\MyApplication.msi" /l*v "C:\InstallLog.txt"

• /quiet: Quiet mode, no user interaction. This performs a silent installation.

• /passive: Unattended mode — progress bar only. Shows a progress bar but requires no user input.

• /norestart: Suppresses any restarts that might be required after the installation.

• /forcerestart: Always restarts the computer after the installation.

• /promptrestart: Prompts the user to restart if necessary. (Default behavior).

• PROPERTY=VALUE: Sets a public property to a specific value. This allows you to customize the installation process. The available properties are defined by the specific .msi package.

  • Example: msiexec.exe /i "C:\Downloads\MyApplication.msi" INSTALLDIR="D:\Program Files\My App"

• /qn: A shortcut for /quiet (no UI).

• /qb: Basic UI. Displays a basic progress bar.
• /qb-: Basic UI with a «Cancel» button.

• /qn+: Silent installation but will display a modal at the very end.

• /? or /help: Displays help information about msiexec.exe‘s command-line options.

Troubleshooting

If you encounter problems with msiexec.exe or Windows Installer, here are some troubleshooting steps:

1. Check the Event Viewer: Windows logs detailed information about system events, including errors related to msiexec.exe. Go to Event Viewer (search for it in the Start Menu) and look under «Windows Logs» > «Application» for errors related to «MsiInstaller.»

2. Generate a Verbose Log File: Use the /l*v option to create a detailed log file. This log file can often pinpoint the exact cause of an installation failure.

3. Run the System File Checker (SFC): SFC can scan for and repair corrupted system files, including msiexec.exe. Open a command prompt as an administrator and run sfc /scannow.

4. Re-register Windows Installer: Sometimes, the Windows Installer service becomes unregistered or corrupted. You can try re-registering it by opening a command prompt as an administrator and running these commands:

   msiexec /unregister
msiexec /regserver

5. Check for Conflicting Software: In rare cases, other software might interfere with Windows Installer. Try temporarily disabling your antivirus software or other security programs to see if that resolves the issue. Remember to re-enable them afterward!

6. Download a Fresh Copy of the Installer: The installer package itself might be corrupted. Try downloading a fresh copy from the software vendor’s website.

7. Windows Installer Cleanup Utility (MSIZAP): This utility (now deprecated and not recommended by Microsoft, use with extreme caution!) was designed to forcibly remove remnants of broken installations. It’s a powerful tool, but it can also cause problems if used incorrectly. Only use this as a last resort and back up your registry beforehand. Modern Windows versions often handle broken installations better without needing this. The better approach is usually to use the Program Install and Uninstall troubleshooter from Microsoft.

8. Program Install and Uninstall troubleshooter: This tool from Microsoft can often fix problems with installing or uninstalling programs. Download it from the official Microsoft website.

Conclusion

msiexec.exe is a fundamental component of Windows, providing a robust and reliable mechanism for software installation and management. While generally working behind the scenes, understanding its purpose, command-line options, and troubleshooting techniques can be invaluable for both system administrators and everyday users. Always obtain software from trusted sources to avoid potential security risks associated with malicious installer packages.

The Windows Installer technology uses Msiexec.exe for installing MSI and
MSP packages. But what is Msiexec.exe? Msiexec.exe is a process present on any modern Windows
operating system that is triggered whenever an MSI or MSP is executed.

Картинка с сайта: www.advancedinstaller.com

Using the built in msiexec switches, you gain full control over the installation
process, giving you the ability to set:

• install options (install, uninstall, administrative install, advertise a product)
• display options (full, basic or no UI during the installation)
• restart options (if the machine will be restarted after the installation)
• logging options
• update options (apply or remove updates)
• repair options (only for an installed package)
• public properties which are used by the
  installation

The usual form of the msiexec command line is this:

msiexec.exe <install_option> <path_to_package> [package_parameters]

msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>

msiexec.exe /i "C:\Example.msi"

msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]

msiexec.exe /i "C:\Example.msi" /qb!

msiexec.exe /i "C:\Example.msi" /qn

msiexec.exe /i <path_to_package> [/norestart][/promptrestart][/forcerestart]

msiexec.exe /i "C:\Example.msi" /norestart

msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log]
<path_to_log>

msiexec.exe /i "C:\Example.msi" /L*V "C:\package.log"

msiexec.exe [/p][/update][/uninstall[/package<product_code_of_package>]]
<path_to_package>

msiexec.exe /p "C:\MyPatch.msp"
msiexec.exe /p "C:\MyPatch.msp" /qb REINSTALLMODE="ecmus" REINSTALL="ALL"
msiexec.exe /update "C:\MyPatch.msp"
msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318}
  /package {AAD3D77A-7476-469F-ADF4-04424124E91D}

msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>

msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}

msiexec.exe /i "C:\Example.msi" MY_PROP="myValue"

The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives you full control over the installation process, allowing you to set:

• install options (install, uninstall, administrative install, advertise a product)
• display options (full, basic or no UI during the installation)
• restart options (if the machine will be restarted after the installation)
• logging options
• update options (apply or remove updates)
• repair options (only for an installed package)
• public properties which are used by the installation

The usual form of the msiexec command line is this:

msiexec.exe <install_option> <path_to_package> [package_parameters]

Install Options

When launching an installation package, you can set the install type through these options:

msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>

• /i – normal installation
• /a – administrative install
• /j – advertise the product
  • u – advertise to the current user
  • m – advertise to all users
  • /g – the language identifier used by the advertised package
  • /t – apply transform to advertise package
• /x – uninstall the package

Sample command line:

msiexec.exe /i "C:Example.msi"

Display Options

The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:

msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]

• /quiet – quiet mode (there is no user interaction)
• /passive – unattended mode (the installation shown only a progress bar)
• /q – set the UI level:
  • n – no UI
  • b – basic UI
  • r – reduced UI
  • f – full UI

Sample command line:

msiexec.exe /i "C:Example.msi" /qn

Restart Options

Sometimes an installation overwrites files which are in use or it needs to reboot the machine in order to finish. The reboot policy used by the installation can be set through these options:

msiexec.exe /i <path_to_package> [/norestart][/promptrestart][/forcerestart]

• /norestart – the machine will not be restarted after the installation is complete
• /promptrestart – the user will be prompted if a reboot is required
• /forcerestart – the machine will be restarted after the installation is complete

Sample command line:

msiexec.exe /i "C:Example.msi" /norestart

Logging Options

When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:

msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>

• /L – enable logging
  • i – include status messages
  • w – include non-fatal warnings
  • e – include all error messages
  • a – mention when an action is started
  • r – include action-specific records
  • u – include user requests
  • c – include the initial UI parameters
  • m – include out-of-memory or fatal exit information
  • o – include out-of-disk-space messages
  • p – include terminal properties
  • v – verbose output
  • x – include extra debugging information
  • + – append to an existing log file
  • ! – flush each line to the log
  • * – log all information, except for v and x options
• /log – the equivalent of /l*

Sample command line:

msiexec.exe /i "C:Example.msi" /L*V "C:package.log"

Update Options

The Windows Installer command line can apply or remove updates (patches for example) through these options:

msiexec.exe [/update][/uninstall[/package<product_code_of_package>]] <path_to_package>

• /update – apply updates (if there are multiple updates, you can separate them through the “;” character)
• /uninstall – remove an update for a product (if there are multiple updates, you can separate them through the “;” character)
  • /package – specifies the package for which the update is removed

Sample command lines:

msiexec.exe /update "C:MyPatch.msp"
msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318} /package {AAD3D77A-7476-469F-ADF4-04424124E91D}

TipIn the above command line the first GUID is the Patch identifier GUID and the second one is the Product Code of the MSI for which the patch was applied.

Repair Options

If you have an installed package, you can use the Windows Installer command line for repairing it:

msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>

• /f – repair a package
  • p – repair only if a file is missing
  • o – repair if a file is missing or an older version is installed
  • e – repair if file is missing or an equal or older version is installed
  • d – repair if a file is missing or a different version is installed
  • c – repair if a file is missing or the checksum does not match the calculated value
  • a – forces all files to be reinstalled
  • u – repair all the required user-specific registry entries
  • m – repair all the required computer-specific registry entries
  • s – repair all existing shortcuts
  • v – run from source and recache the local package

Sample command line:

msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}

In the above command line the GUID is the Product Code of the MSI which will be repaired.

Set public properties

The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY=”value”.
Sample command line:

msiexec.exe /i "C:Example.msi" MY_PROP="myValue"

Correct syntax:
msiexec /i A:Example.msi PROPERTY=VALUE
Incorrect syntax:
msiexec /i PROPERTY=VALUE A:Example.msi
Property values that are literal strings must be enclosed in quotation marks. Include any white spaces in the string between the marks.
msiexec /i A:Example.msi PROPERTY=”Embedded White Space”
To clear a public property by using the command line, set its value to an empty string.
msiexec /i A:Example.msi PROPERTY=””
For sections of text set apart by literal quotation marks, enclose the section with a second pair of quotation marks.
msiexec /i A:Example.msi PROPERTY=”Embedded “”Quotes”” White Space”
The following example shows a complicated command line.
msiexec /i testdb.msi INSTALLLEVEL=3 /l* msi.log COMPANYNAME=”Acme “”Widgets”” and “”Gizmos.”””
The following example shows advertisement options. Note that switches are not case-sensitive.
msiexec /JM msisample.msi /T transform.mst /LIME logfile.txt
The following example shows you how to install a new instance of a product to be advertised. This product is authored to support multiple instance transforms.
msiexec /JM msisample.msi /T :instance1.mst;customization.mst /c /LIME logfile.txt
The following example shows how to patch an instance of a product that is installed using multiple instance transforms.
msiexec /p msipatch.msp;msipatch2.msp /n {00000001-0002-0000-0000-624474736554} /qb
When you apply patches to a specific product, the /i and /p options cannot be specified together in a command line. In this case, you can apply patches to a product as follows.
msiexec /i A:Example.msi PATCH=msipatch.msp;msipatch2.msp /qb
Some Sample Commands for EXE files:–

MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL

psexec computer_name MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL
cmd=’msiexec /qn /i %SOFTWARE%adobereader93AdbeRdr930_en_US.msi TRANSFORMS=%SOFTWARE%adobereader93AdbeRdr930_en_US.mst’
‘msiexec /qn /update %SOFTWARE%AdobeReader93AdbeRdrUpd932_all_incr.msp’
‘MsiExec.exe /x{AC76BA86-7AD7-1033-7B44-A80000000002} /qn ‘
msiexec /qn /x{AC76BA86-7AD7-1033-7B44-A93000000001}
msiexec.exe /qn /update “%SOFTWARE%AdobeReader93AdbeRdrUpd932_all_incr.msp”‘
‘msiexec /qb /uninstall “%SOFTWARE%adobe-readerAcroRead.msi’
siexec /i “UNCPathfilename.msi” /qn

With the Product key

msiexec /i “UNCPathfilename.msi” /qn PIDKEY=”Key value without dashes

Java

jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1
jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /v”/qn ADDLOCAL=ALL IEXPLORER=1 INSTALLDIR=D:javajre”
start /w jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0n1n2n3n4n50}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000}
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0151020}
Creating a Log File
If you want to create a log file describing the installation/uninstallation, append /L C:<path>setup.log to the install/uninstall command. The following is an example for installation:
Installation Example
jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /L C:<path>setup.log
The following is an example for uninstalling:
Uninstalling Example
msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000} /L C:<path>setup.log

Note:- Adobe Customization Wizard 9 will help you to create MST file for silent installation

WINZIP:-

Below is available WINZIP MSI File https://download.winzip.com/ov/winzip100.msi
ymsgrie.exe /s /v/passive – install Yahoo! Messenger silent, with progress bar

Team Viewer :–

The /S switch for silent install of TEAMVIEWER WORKS!
but you must do the following :
download the program (preferably the latest version) ..or ..if you have it on your hard drive , open it… (AND LET IT OPEN! DO NOT CLOSE OR INSTALL THE APLICATION. JUST DUBLE-CLICK IT!!)
Then , go to C:Documents and SettingsAdministratorLocal SettingsTemp. There you’ll see a folder called TeamViewer. Open that folder. Inside you’ll have 2 files. Teamviewer.exe and tvinfo.ini
Copy the Teamviewer from that folder and paste wherever you want. After this you can close the other application.
With the new teamviewer.exew which you copyed from the temp folder , u can run it sillently. Use the /S Switch. Works with WPI also.
  If you find MSiexec has problem then you can run below two commands
msiexec /unregister  —> for unregistering the windows installer
  msiexec /regserver—> for registering the windows installer
Released Versions of Windows Installer
The table in this topic identifies the released versions of the Windows Installer.
Release
Version
Description
Windows Installer 2.0
2.0.2600.0
Released with Windows XP.
Windows Installer 2.0
2.0.2600.1
Released with Windows 2000 Server with Service Pack 3 (SP3).
Windows Installer 2.0
2.0.2600.1183
Released with Windows 2000 Server with Service Pack 4 (SP4).
Windows Installer 2.0
2.0.2600.2
Released as a redistributable.
Windows Installer 2.0
2.0.2600.1106
Released with Windows XP with Service Pack 1 (SP1).
Windows Installer 2.0
2.0.3790.0
Released with Windows Server 2003.
Windows Installer 3.0
3.0.3790.2180
Released with Windows XP with Service Pack 2 (SP2). Released as a redistributable.
Windows Installer 3.1
3.1.4000.1823
Released as a redistributable. This version is has the same functionality as version 3.1.4000.2435.
Windows Installer 3.1
3.1.4000.1830
Released with Windows Server 2003 with Service Pack 1 (SP1) and Windows XP Professional x64 Edition. Update this version to version 3.1.4000.2435 to address the issue discussed in KB898628.
Windows Installer 3.1
3.1.4000.3959
Released with Windows Server 2003 with Service Pack 2 (SP2).
Windows Installer 3.1
3.1.4000.2435
Released with a fix to address the issue discussed in KB898628. This is the latest version of Windows Installer 3.1.
Windows Installer 3.1
3.1.4001.5512
Released with Windows XP with Service Pack 3 (SP3).
Windows Installer 4.0
4.0.6000.16386
Released with Windows Vista.
Windows Installer 4.0
4.0.6001.18000
Released with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008.
Windows Installer 4.5
4.5.6002.18005
Released with Windows Vista with Service Pack 2 (SP2) and Windows Server 2008 with Service Pack (SP2.)
Windows Installer 4.5
4.5.6000.20817
Released as a redistributable for Windows Vista.
Windows Installer 4.5
4.5.6001.22162
Released as a redistributable for Windows Server 2008 and Windows Vista with SP1.
Windows Installer 4.5
4.5.6001.22159
Released as a redistributable for Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with SP1 and later.
Windows Installer 5.0 is released with Windows Server 2008 R2 and Windows 7.
  To create exe file by using winrar for silent installation / Self Extractor
  create SFX archive”. Change the archive name if you like but it must have the .exe extension.

Switch to the Advanced tab and select “SFX options” to open Advanced SFX options window.

On the General tab in the “Path to extract” box type the path you want to extract the installer to. Make sure it is the same path you have in the antivir.cmd file. Then in the “Run after extraction” box type in the path to the antivir.cmd file.

Change to the Modes tab and select the “hide all” and “overwrite existing files” radio buttons.

Close the “Advanced SFX Options” window by clicking OK, then click OK on the “Archive name and parameters” window to start creating the installer. The finished installer is created in the antivirpec folder.
  Also you can do with 7zip  where you will have more options compare to winrar or winzipself extractor.

Office 2007 silent install with SCCM 2007

So here is his tip on how to create a customized MSP file with OCT:

1. Go to the original package source that contains the Office 2007 setup files
2. From the directory that contains the Office 2007 setup files, run setup.exe /admin. This should open the Office Customization Toolkit (OCT)
3. Select to Create a new Setup customization file
4. In the “Install location and organization name”, set the default installation location and organization name.
5. Click on Licensing and user interface. Make sure you enter a valid product key, check the EULA checkbox and set Display level to None. Completion notice checkbox should not be checked and Suppress modal should be checked.
6. Save the MSP file by going to File –> Save. Give the file a name and save it to the Updates folder located in the Office 2007 installation source folder. By saving it to the Updates folder, the /adminfile switch will not need to be used as part of setup.exe. If the file is not saved to the Updates folder, make sure that the /adminfile switch is used as part of setup.exe and that it points to the MSP file just created.

Further more, with OCT you can customize almost everything regarding how your Word/Excel etc. applications will run. What I liked most is the possibility to create the default profile in Outlook if you are using an Exchange server in your organization.
Don’t forget to save the MSP file and to put the file in Updates folder or to use /adminfile <path to MST file> switch .
  Hope I will try to post when i get some time