问题
Microsoft's documentation for msiexec says this:
/lv Turns on logging and includes verbose output in the output log file.
/l* Turns on logging and logs all information, except verbose information (/lv) or extra debugging information (/lx).
Examples To install package C:\example.msi, using a normal installation process with all logging information provided, including verbose output, and storing the output log file at C:\package.log, type:
msiexec.exe /i "C:\example.msi" /L*V "C:\package.log"
I think it might help to have an example installer log. What is 'all logging information' vs verbose logging? Isn't verbose just that & historically shows all logging info? Guessing this is going to be a unique Microsoft thing
回答1:
The /l switch takes a bunch of switches, each of which identifies particular items to log and is independent of the others. Likewise, v indicates a particular set of items to be logged; it's not a generic verbose logging level.
/l* says include all the switches except for v and x so it's equivalent to /loicewarmup. /l*vx includes all the switches and adds v and x to get everything.
回答2:
Debug Logging (Verbose): Advanced, slow logging for maximum details captured. This is - as far as I can tell - the most information you can capture in an MSI log:
msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Your.log
Interpreting MSI logs: MSI log files can be very verbose indeed. Advanced installer and an old blog from the MSI team of many years ago have a few clues to their content:
- https://www.advancedinstaller.com/user-guide/read-log.html
- How to interpret an MSI Log File (and the actual PDF resurrected from WayBack Machine)
This old dialog from a log-command generation tool might help. The flush to log means the log is written directly and continuously and not in batches. This continuous writing slows things down a lot, but no log buffer is lost if there is a crash:
WiLogUtl.exe: The Windows SDK contains this tool to analyze MSI log files. It can be helpful, although it is quite old-fashioned to look at GUI-wise. Search for it under: C:\Program Files (x86)\Windows Kits - if you have Visual Studio or the Windows SDK installed. Here is a screen shot:
Some pre-existing answers on logging:
- A comprehensive answer on logging
- Stefan Kruger on logging: http://www.installsite.org/pages/en/msifaq/a/1022.htm
来源：https://stackoverflow.com/questions/64341212/difference-between-msiexec-log-lv-vs-lv