Msiexec exe x64 windows 10

Похоже, что-то изменило вашу конфигурацию Windows 10, чтобы изменить стандартную ассоциацию типов файлов .msi . В результате они не будут работать должным образом.

Используйте следующий код, вставив его в Блокнот, сохранив его как файл .reg и объединив его с правами администратора, чтобы восстановить стандартную ассоциацию типов файлов. Вы также можете скачать тот же код в легкодоступном файле .reg из оригинального источника, на который ссылаются ниже:

Windows Registry Editor Version 5.00

; Created by: Shawn Brink
; http://www.tenforums.com
; Tutorial: http://www.tenforums.com/tutorials/8703-default-file-type-associations-restore-windows-10-a.html


[-HKEY_CLASSES_ROOT.msi]

[HKEY_CLASSES_ROOT.msi]
@="Msi.Package"

[HKEY_CLASSES_ROOTMsi.Package]
@="Windows Installer Package"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,
  00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,
  32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,
  00,2d,00,33,00,34,00,00,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"

[HKEY_CLASSES_ROOTMsi.PackageDefaultIcon]
@="C:\Windows\System32\msiexec.exe,0"

[HKEY_CLASSES_ROOTMsi.Packageshell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOTMsi.PackageshellOpen]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,36,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellOpencommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellRepair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,37,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellRepaircommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.Packageshellrunasuser]
@="@shell32.dll,-50944"
"Extended"=""
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"

[HKEY_CLASSES_ROOTMsi.Packageshellrunasusercommand]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOTMsi.PackageshellUninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,38,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellUninstallcommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellexContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOTMsi.PackageshellexContextMenuHandlersCompatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[-HKEY_CLASSES_ROOTSystemFileAssociations.msi]

[-HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionExplorerFileExts.msi]

[-HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsRoamingOpenWithFileExts.msi]

(Источник: восстановить сопоставления типов файлов по умолчанию в Windows 10)

Если проблема не устранена, откройте командную строку с повышенными правами и запустите sfc /scannow чтобы попытаться восстановить операционную систему.

It sounds like something modified your Windows 10 configuration to change the default .msi file type association. As a result, they won’t execute properly.

Utilize the following code by pasting it into Notepad, saving it as a .reg file and merging it with admin privileges to restore your default file type association. You can also download the same code within a readily available .reg file from original source referenced below:

Windows Registry Editor Version 5.00

; Created by: Shawn Brink
; http://www.tenforums.com
; Tutorial: http://www.tenforums.com/tutorials/8703-default-file-type-associations-restore-windows-10-a.html


[-HKEY_CLASSES_ROOT.msi]

[HKEY_CLASSES_ROOT.msi]
@="Msi.Package"

[HKEY_CLASSES_ROOTMsi.Package]
@="Windows Installer Package"
"EditFlags"=hex:00,00,10,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,
  00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,
  32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,
  00,2d,00,33,00,34,00,00,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"

[HKEY_CLASSES_ROOTMsi.PackageDefaultIcon]
@="C:\Windows\System32\msiexec.exe,0"

[HKEY_CLASSES_ROOTMsi.Packageshell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOTMsi.PackageshellOpen]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,36,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellOpencommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellRepair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,37,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellRepaircommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.Packageshellrunasuser]
@="@shell32.dll,-50944"
"Extended"=""
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"

[HKEY_CLASSES_ROOTMsi.Packageshellrunasusercommand]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOTMsi.PackageshellUninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,
  00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,
  33,00,38,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellUninstallcommand]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,
  00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,
  73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,
  00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOTMsi.PackageshellexContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOTMsi.PackageshellexContextMenuHandlersCompatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[-HKEY_CLASSES_ROOTSystemFileAssociations.msi]

[-HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsCurrentVersionExplorerFileExts.msi]

[-HKEY_CURRENT_USERSOFTWAREMicrosoftWindowsRoamingOpenWithFileExts.msi]

(Source: Restore Default File Type Associations in Windows 10)

If the problem still persists, open an elevated command prompt and run sfc /scannow in an attempt to repair your operating system.

Sometimes Windows system displays error messages regarding corrupted or missing msiexec.exe files. Situations like that can occur, for example, during a software installation process. Each software program requires certain resources, libraries, and source data to work properly. Corrupted or nonexistent msiexec.exe file can therefore effect in failed execution of the started process.

msiexec.exe file Windows® installer. The file was developed by for use with software. Here you will find detailed information about the file and instructions how to proceed in the event of msiexec.exe related errors on your device. You can also download msiexec.exe file compatible with Windows 10, Windows 8.1, Windows 8, Windows 7, Windows 7, Windows Vista, Windows Vista, Windows XP devices which will (most probably) allow you to solve the problem.

Compatible with: Windows 10, Windows 8.1, Windows 8, Windows 7, Windows 7, Windows Vista, Windows Vista, Windows XP

User popularity

Fix msiexec.exe errors

• 1 Information about msiexec.exe file
• 2 Errors related to msiexec.exe file
• 3 How to fix msiexec.exe related errors?
• 3.1 Scanning for malicious software
• 3.2 System and driver update
• 3.3 System File Checker tool
• 3.4 System recovery
• 4 Download msiexec.exe
• 4.1 List of msiexec.exe file versions

File info

General information
Filename	msiexec.exe
File extension	EXE
Description	Windows® installer

Software
Program	Windows Installer — Unicode
Author	Microsoft Corporation

Details
MIME type	application/octet-stream
File type	Executable application
System	Windows NT 32-bit
Copyrights	© Microsoft Corporation. All rights reserved.
Character set	Unicode
Language cod	English (U.S.)

There are various types of errors related to msiexec.exe file. msiexec.exe file may be located in wrong file directory on your device, may not be present in the system, or may be infected with malicious software and therefore not work correctly. Below is a list of most common error messages related to msiexec.exe file. If you encounter one listed below (or similar), please consider the following suggestions.

• msiexec.exe is corrupted
• msiexec.exe cannot be located
• Runtime Error — msiexec.exe
• msiexec.exe file error
• msiexec.exe file cannot be loaded. Module was not found
• cannot register msiexec.exe file:
• msiexec.exe file could not be loaded
• msiexec.exe file doesn’t exist

msiexec.exe

Application could not be started because msiexec.exe file is missing. Reinstall the application to solve the problem.

OK

Problems related to msiexec.exe can be addressed in various ways. Some methods are meant only for advanced users. If you don’t have confidence in your skills, we suggest consulting a specialist. Fixing msiexec.exe file errors should be approached with utmost caution for any mistakes can result in unstable or unproperly working system. If you have the necassary skills, please proceed.

msiexec.exe file errors can be caused by various factors, so its is beneficial to try to fix them using various methods.

Step 1: Scan your computer for any malicious software

Windows files are commonly attacked by malicious software that prevents them from working properly. First step in addressing problems with msiexec.exe file or any other Windows system files should be scanning the system for malicious software using an antivirus tool.

If by any chance you don’t have any antivirus software installed on your system yet, you should do it immediately. Unprotected system is not only a source of file errors, but, more importantly, makes your system vulnerable to many dangers. If you don’t know which antivirus tool to choose, consult this Wikipedia article – comparison of antivirus software.

Step 2: Update your system and drivers.

Installing relevant Microsoft Windows patches and updates may solve your problems related to msiexec.exe file. Use dedicated Windows tool to perform the update.

1. Go to the Windows «Start» menu
2. Type «Windows Update» in the search field
3. Choose the appropriate software program (name may vary depending on your system version)
4. Check if your system is up to date. If any unapplied updates are listed, install them immediately.
5. After the update has been done,restart your computer in order to complete the process.

Beside updating the system, it is recommended that you install latest device drivers, as drivers can influence proper working of msiexec.exe or other system files. In order to do so, go to your computer or device producer’s website where you will find information regarding latest driver updates.

Step 4: Restoring Windows system

Another approach is to restore system to previous state, before the msiexec.exe file error occured. In order to restore your system, follow the instructions below

1. Go to the Windows «Start» menu
2. Type «System Restore» in the search field
3. Start the system restore tool – it’s name may differ depending on version of the system
4. The application will guide you through the process – read the messages carefully
5. After the process has finished, restart your computer.

If all the above-mentioned methods failed and the msiexec.exe file problem has not been resolved, proceed to the next step. Remember that the following steps are intended only for advanced users.

Download and replace msiexec.exe file

The last solution is to manually download and replace msiexec.exe file in appropriate folder on the disk. Select file version compatible with your operating system and click the «Download» button. Next, go to your web browser’s «Downloaded» folder and copy the downloaded msiexec.exe file.

Go to the folder where the file should be located and paste the downloaded file. Below is the list of msiexec.exe file example directory paths.

• Windows 10: C:\Windows\System32\
• Windows 8.1: C:\Windows\System32\
• Windows 8: 1: C:\Windows\System32\
• Windows 7: C:\Windows\System32\
• Windows 7: C:\Windows\System32\
• Windows Vista: —
• Windows Vista: —
• Windows XP: —

If the steps did not solve your msiexec.exe file problem, you should consult a professional. A probability exists that the error(s) might be device-related and therefore should be resolved at the hardware level. A fresh operating system installation might be necessary – a faulty system installation process can result in data loss.

File versions list

Filename
msiexec.exe

System
Windows 10

File size
59392 bytes

Date
2017-03-18

File details
	MD5	98eebf39b025339cf12672030777707d
SHA1	b01c43926548dd741a2143e7d6092e545225b063
SHA256	9be9929e382ad16adab4c02a87aa67dfaef951dafdef87d0324deae666bd8f62
CRC32	cb42fb21
Example file location	C:\Windows\System32\

Filename
msiexec.exe

System
Windows 8.1

File size
59904 bytes

Date
2014-11-21

File details
	MD5	055cce830a54c2c1b598e2066f65c9ab
SHA1	ef388bad3b34ca12b30913184b971ad36760d679
SHA256	289288735d5e6c39e11f3c4c321c540718215a18a654736d7a605f25a27abf7b
CRC32	cdb1c05a
Example file location	C:\Windows\System32\

Filename
msiexec.exe

System
Windows 8

File size
62976 bytes

Date
2012-07-26

File details
	MD5	07eab0a1dcf20b91a30eb6822d63483c
SHA1	bbd9e24249889f74aec9132593dc3c6fa8dcb71e
SHA256	642533166530468ba9a5848d97960001416990317e2385f278ea3deb2ea32450
CRC32	4e127932
Example file location	1: C:\Windows\System32\

Filename
msiexec.exe

System
Windows 7

File size
128000 bytes

Date
2010-11-21

File details
	MD5	a190da6546501cb4146bbcc0b6a3f48b
SHA1	443aac22d57edd4ef893e2a245b356cba5b2c2dd
SHA256	5ae0bf71e770c2959fe2022c43e4c6f43e361089a3431aa3180ebf4ec0465cac
CRC32	65239bd9
Example file location	C:\Windows\System32\

Filename
msiexec.exe

System
Windows 7

File size
73216 bytes

Date
-0001-11-30

File details
	MD5	eee470f2a771fc0b543bdeef74fceca0
SHA1	bd9bbb448dec04b1aaa8ae530e9814fdbce0a3d5
SHA256	78617ddf9a0067a32cb5d87a796c93a9618ac006ccdcb3c7c824fdeb6ec5fd59
CRC32	c5dd3cd2
Example file location	C:\Windows\System32\

Filename
msiexec.exe

System
Windows Vista

File size
125440 bytes

Date
2009-04-11

File details
	MD5	ac545df9370a3e1bf538e403abe51cc0
SHA1	565bb6914d6b9c7f5fe7e462d400e678f93e8313
SHA256	cf87a909560e59aede01d49dbaecb17c244f80f6b6afed37d8a8b0c1e1b00164
CRC32	85dd2164
Example file location	—

Filename
msiexec.exe

System
Windows Vista

File size
73216 bytes

Date
-0001-11-30

File details
	MD5	c559672f31abe6ba7277dd73c4502238
SHA1	92e3ecbbaf611b9a967f802732c25e27d462f5ab
SHA256	dce701a4b6a824f5b71cc9be150a87d07b2b581cb06e5ad91cc5757c67386975
CRC32	6ab5e55c
Example file location	—

Filename
msiexec.exe

System
Windows XP

File size
78848 bytes

Date
2008-04-14

File details
	MD5	5879d691e842574a20fe63817cb76df9
SHA1	2007d2c57e7b68b550db764f3cb4f43bb0274460
SHA256	083827b4af9a2da6ddf672265f9774fb73f9ad8455d51e8fe5cb33df2b960836
CRC32	82928e5f
Example file location	—

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"

MSIEXEC.EXE – the MSI executable, the program that performs the actual installation of the application.

/I – this switch informs the Windows Installer to install the specified application (as opposed to removing, reinstalling or repairing the application)

/QB-  – this switch instructs the Windows Installer to perform the installation with a basic user interface requiring no dialog boxes to be displayed. You might also use /QN to perform the installation with no user interface at all.

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:–

setup.exe /q

setup.exe /qn

setup.exe /silent

setup.exe /s

setup.exe /NoUserInput

setup.exe /unattended

setup.exe /CreateAnswerFile

setup.exe /quiet

Symantec

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

• 13.02.2020
• 30 817
• 0
• 04.10.2021
• 17
• 16
• 1

• Содержание статьи
  • Описание
  • Установка и настройка продукта
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Использование режима административной установки
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Восстановление продукта
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Удаление продукта
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Объявление продукта
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Установка уровня ведения журнала
    • Синтаксис
    • Параметры
    • Примечания
    • Примеры
  • Справочная информация
  • Добавить комментарий

Описание

MSIEXEC — Средство установки, изменения и выполнения операций установщика Windows из командной строки.

Эта команда поддерживается в CMD.EXE и в PowerShell.

Установка и настройка продукта

Синтаксис

msiexec /i {пакет|код_продукта}

Параметры

• /i — Установка или настройка продукта.
• пакет — Имя файла пакета установщика Windows.
• код_продукта — Глобальный уникальный идентификатор (GUID) пакета установщика Windows.

Примечания

• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.

Примеры

Чтобы установить продукт из файла A:\Example.msi, введите:

msiexec /i A:\Example.msi

Использование режима административной установки

Синтаксис

msiexec /a пакет

Параметры

• /a — Выбор режима административной установки.
• пакет — Имя файла пакета установщика Windows.

Примечания

• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.

Примеры

Чтобы установить продукт из файла A:\Example.msi в режиме административной установки, введите:

msiexec /a A:\Example.msi

Восстановление продукта

Синтаксис

msiexec /f [p][o][e][d][c][a][u][m][s][v]{пакет|код_продукта}

Параметры

• /f — Включение одного или нескольких параметров командной строки, перечисленных в следующей таблице.
• пакет — Имя файла пакета установщика Windows.
• код_продукта — Глобальный уникальный идентификатор (GUID) пакета установщика Windows.

Параметр	Описание
p	Переустановка только в случае отсутствия файла.
o	Переустановка при отсутствии файла или если установлена его старая версия.
e	Переустановка при отсутствии файла или если установлена его текущая либо старая версия.
d	Переустановка в случае отсутствия файла или если установлена другая его версия.
c	Переустановка в случае отсутствия файла или в случае, если контрольная сумма не совпадает с вычисленным значением.
a	Принудительная переустановка всех файлов.
u	Перезапись всех необходимых пользовательских записей реестра.
m	Перезапись всех необходимых записей реестра компьютера.
s	Перезапись всех имеющихся ярлыков.
v	Запуск файлов из источника и повторное кэширование локального пакета.

Примечания

• Параметром по умолчанию для этой командной строки является параметр /fpecms.
• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.

Примеры

Чтобы восстановить пакет установки, введите:

msiexec /fpecms Example.msi

Удаление продукта

Синтаксис

msiexec /x {пакет|код_продукта}

Параметры

• /x — Удаление продукта.
• пакет — Имя файла пакета установщика Windows.
• код_продукта — Глобальный уникальный идентификатор (GUID) пакета установщика Windows.

Примечания

• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.

Примеры

Чтобы удалить или отменить установку пакета, введите:

msiexec /x Example.msi

Объявление продукта

Синтаксис

msiexec /j [{u|m}] пакет

msiexec {u|m} пакет /t список_преобразований

msiexec {u|m} пакет /g код_языка

Параметры

• /j — Объявление продукта. u — Объявление для текущего пользователя. m — Объявление для всех пользователей компьютера.
• пакет — Файл пакета установщика Windows.
• /g код_языка — Служит для задания языка.
• /t список_преобразований — Применение преобразований к объявляемому пакету.

Примечания

• При необходимости установить приложение с повышенными привилегиями используйте параметр /jm.
• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.

Примеры

Чтобы объявить пакет для всех пользователей этого компьютера, введите:

msiexec /jm Example.msi

Установка уровня ведения журнала

Синтаксис

msiexec /L [i][w][e][a][r][u][c][m][p][v][+][!]файл_журнала.txt

Параметры

• /L — Путь к файлу журнала.
• i — Занесение в журнал сообщений о состоянии.
• w — Занесение в журнал некритических предупреждений.
• e — Занесение в журнал сообщений об ошибках.
• a — Занесение в журнал выполнения действий.
• r — Занесение в журнал записей со сведениями о действиях.
• u — Занесение в журнал запросов пользователей.
• c — Занесение в журнал исходных параметров пользовательского интерфейса.
• m — Занесение в журнал нехватки памяти.
• p — Занесение в журнал свойств терминала.
• v — Занесение в журнал подробных сведений. Для использования параметра v следует задавать /L*v.
• + — Добавление в существующий файл.
• ! — Сброс в журнал каждой строки.
• * — Занесение в журнал всех сведений, кроме параметра v. Это подстановочный знак.
• файл_журнала.txt — Имя и путь к текстовому файлу журнала.

Примечания

• Регистр букв при вводе параметров командной строки установщика Windows не учитывается.
• Чтобы включить в файл журнала параметр v при использовании подстановочного знака, введите в командной строке /L*v.
• Параметры файла журнала установщика Windows могут также использоваться для процессов удаления и восстановления.

Примеры

Чтобы установить пакет и создать файл журнала, включающий в себя сведения о состоянии, сообщения о нехватке памяти и все сообщения об ошибках, введите следующую команду:

msiexec /i Example.msi /L ime logfile.txt

Справочная информация

msiexec /Option <обязательный параметр> [необязательный параметр]

Параметры установки
</package | /i> Установка или настройка продукта
/a Административная установка — установка продукта в сеть
/j<u|m> [/t <список преобразований>] [/g <код языка>]
Объявление о продукте: «m» — всем пользователям; «u» — текущему пользователю
</uninstall | /x> Удаление продукта
Параметры отображения
/quiet
Тихий режим, без взаимодействия с пользователем
/passive
Автоматический режим — только указатель хода выполнения
/q[n|b|r|f]
Выбор уровня интерфейса пользователя
n — Без интерфейса
b — Основной интерфейс
r — Сокращенный интерфейс
f — Полный интерфейс (по умолчанию)
/help
Вывод справки по использованию
Параметры перезапуска
/norestart
Не перезапускать после завершения установки
/promptrestart
Запрашивать перезапуск при необходимости
/forcerestart
Всегда перезапускать компьютер после завершения установки
Параметры ведения журнала
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <файл_журнала>
i — сообщения о состоянии
w — сообщения об устранимых ошибках
e — все сообщения об ошибках
a — запуски действий
r — записи, специфические для действий
u — запросы пользователя
c — начальные параметры интерфейса пользователя
m — сведения о выходе из-за недостатка памяти или неустранимой ошибки
o — сообщения о недостатке места на диске
p — свойства терминала
v — подробный вывод
x — дополнительные отладочные сведения
+ — добавление в существующий файл журнала
! — сбрасывание каждой строки в журнал
* — заносить в журнал все сведения, кроме параметров «v» и «x»
/log <файл_журнала>
Равнозначен /l* <файл_журнала>
Параметры обновления
/update [;Update2.msp]
Применение обновлений
/uninstall <Код_Guid_обновления>[;Update2.msp] /package Удаление обновлений продукта
Параметры восстановления
/f[p|e|c|m|s|o|d|a|u|v] Восстановление продукта
p — только при отсутствии файла
o — если файл отсутствует или установлена старая версия (по умолчанию)
e — если файл отсутствует или установлена такая же либо старая версия
d — если файл отсутствует или установлена другая версия
c — если файл отсутствует или контрольная сумма не совпадает с подсчитанным значением
a — принудительная переустановка всех файлов
u — все необходимые элементы реестра, специфические для пользователя (по умолчанию)
m — все необходимые элементы реестра, специфические для компьютера (по умолчанию)
s — все существующие ярлыки (по умолчанию)
v — запуск из источника с повторным кэшированием локальных пакетов