Windows Installer logging
Windows Installer handles its installations through Msiexec.exe. The logging options offered by this tool allow you to create different types of logs, depending on the information you need about the installation. These options are:
Join Date Dec 2005 Location Leeds/York area, North Yorkshire Posts 9,362 Thank Post 960 Thanked 1,230 Times in 913 Posts Rep Power 464. The full path to the predefined 64-bit Program Files folder. ProgramFilesFolder: The full path to the predefined 32-bit Program Files folder. ProgramMenuFolder: The full path to the Program Menu folder. RecentFolder: The full path to the Recent folder. SendToFolder: The full path to the SendTo folder for the current user.
- i - Status messages
- w - Nonfatal warnings
- e - All error messages
- a - Start up of actions
- r - Action-specific records
- u - User requests
- c - Initial UI parameters
- m - Out-of-memory or fatal exit information
- o - Out-of-disk-space messages
- p - Terminal properties
- v - Verbose output
- x - Extra debugging information
- + - Append to existing log file
- ! - Flush each line to the log
- * - Log all information, except for v and x options
The logging command is issued by the /L parameter. The above options can be used only after this parameter (the options cannot be used by themselves).
Create a log
The most used logging command is /L*V. This command will create a verbose log which offers a lot of information about the installation. Here are the steps for creating a log:
- find out the path of the MSI file, for example C:MyPackageExample.msi
- decide the path of the log, for example C:logexample.log
- open cmd.exe (you can use any command shell)
- use the msiexec command line to launch the MSI with logging parameters
For creating an installation log, you can use a command line which looks like this:
Msi File Download Windows 10
The /i parameter will launch the MSI package. After the installation is finished, the log is complete.
The example command line uses the sample paths in this How-To. For your package you must use the path of your MSI file.
Note that any logging command line should have this form:
After you use the logging command, you need to specify the log's complete path. If you want the log to be created next to the MSI, you can specify only the name of the log file:
When the package is included in an EXE bootstrapper, the command line no longer uses 'msiexec'. For example, the command line can look like this:
In order to create a log for an uninstall process, you can replace the /i parameter with /x. Therefore, a command line which creates a log for an uninstall can look like this:
The package path can also be replaced by the package Product Code (it can be obtained by using the Project -> Options menu inside the project). The command line would look like this:
Drive File Stream Msi Software
When the package is included in an EXE bootstrapper and it's already installed on the machine, you can launch the installer again with the logging command. For example:
This will make the package go into maintenance mode and you can choose to uninstall it. Since the package was launched with logging, an uninstall log will be generated.
Patch Install Log
You can create a log for a patch installation by using the /p parameter instead of /i:
Use the EXE boostrapper
Another approach is to create a log file by using the /L*V parameters in the command line of the Advanced Installer Bootstrapper. Also, these parameters can be always passed to the MSI when the package is launched through the EXE bootstrapper.
If you want your installation package to always create a log, you can follow these steps:
- open your installation package's Advanced Installer project
- go to the Builds page and select the Configuration Settings Tab tab
- check the EXE setup option
- set the MSI Command Line field to: /L*V 'C:package.log'
This way, when the user launches the installation through the bootstrapper, an installation log ('package.log') will be created automatically in the 'C:' drive.
The command line received by the bootstrapper overrides the command line in the 'MSI Command Line' field. Therefore, if you launch an EXE package with logging parameters, these parameters will be used for creating the log.
Automated logging with the Windows Installer Logging Policy
The logging policy is particularly useful for troubleshooting Active Directory/Group Policy deployments, in which case the installation is carried out without a user interface and there is no possibility to specify a command line for the MSI package.
In order to enable this option, you need to import the registry settings below. Please create a new text file with a '.reg' extension and then copy the following lines into it. After this, double click the '.reg' file you just created and answer 'Yes' to the confirmation prompt.
The .LOG file will be created in the currently logged on user's Temp folder and will have a name in the following format: 'MSI*.LOG'.
In case of a Active Directory/GPO deployment, there will be no logged on user at the time the installation occurs. In this case the log file will be created in the 'WindowsTemp' folder.
This option should not be left active since every install/uninstall operation of an MSI package will create a new log file, thus unnecessarily occupying disk space. Therefore, this option should only be used for debugging purposes.
In order to disable the debugging policy, you can delete the registry values you have previously added using 'RegEdit.exe' or you can import the following .reg file as you did with the previous one:
For information on how to make a custom event appear in the log, please see How to write a specific event in the log
- Write a custom event in the log file
How to log an event using custom actions.
- Read a log
How to read an installation log
There have been reports of system administrator preventing the installation of .msi files (please refer to the screenshot below).
We do not have any policy in place that disallows an installation. Every filetype/software is allowed from our side.
Drive File Stream Missing
Importing/creating a registry key allowing you to run an .msi file “As Administrator” often offers a solution to this known issue. Below two how-to guides (first one to create the registry key manually, second one to import it via a .reg file).
1. Create reg keys manually
a. Open regedit
b. Browse into HKEY_CLASSES_ROOTMsi.Packageshell
c. Add a new key called “runas”
d. Modify the value of the Default entry “runas” to Install as &Administrator
e. Add a subkey under key “runas” called “command”
f. Modify the value of the Default entry “command” to msiexec /i “%1”
2. Add the reg keys via .reg file (easiest solution)
a. Launch your cloud Desktop
b. Open notepad and paste the following content:
c. Select “Save As”, fill in “MSI_install_as_administrator.reg” as file name, select “All Files (*.*)” as type; location of the file doens’t matter.
d. Run the file by double-clicking it.
e. Allow MSI_install_as_administrator.reg to adjust the Registry by clicking “Yes”
f. All keys are added successfully
Msi Files Windows 10
After executing one of the 2 guides above, you should be able to right click an .msi file & select “Install as Administrator”.
The software should install properly. If not, please contact support via [email protected]