1

We have ".msi" installation package.
I try to uninstall it with appropriate commnd:

MsiExec.exe /x{5D719E68-C010-4DD9-A1C3-7BC1581781F0} /lv log.txt

In the log I see follow records: 

MSI (s) (D4:14) [17:38:41:595]: Executing op: ShortcutRemove(Name=n80p5njq|Sample Playlist Transcoding)
MSI (s) (D4:14) [17:38:41:601]: Verifying accessibility of file: Sample Playlist Transcoding.lnk
MSI (s) (D4:14) [17:38:41:602]: Using source file security for destination.
MSI (s) (D4:14) [17:38:41:602]: Note: 1: 2318 2: C:\Config.Msi\b5120.rbf 
MSI (s) (D4:14) [17:38:46:847]: Executing op: ShortcutRemove(Name=8vdz7yeg|Sample Writer)
MSI (s) (D4:14) [17:38:46:853]: Verifying accessibility of file: Sample Writer.lnk
MSI (s) (D4:14) [17:38:46:855]: Using source file security for destination.
MSI (s) (D4:14) [17:38:46:856]: Note: 1: 2318 2: C:\Config.Msi\b5121.rbf

All steps are taken acceptable interval except "ShortcutRemove".
What can I do, for increase the speed of uninstall process?

Olga Pshenichnikova
  • 1,509
  • 4
  • 22
  • 47
  • 1
    Did you find a solution? Was it a networking issue? – Stein Åsmul Sep 13 '19 at 16:51
  • Actually no... I was glad to have your answer, and marked it as right, but I think it will take much time to understand, what the problem. Enyway... all shortcut nodes of msi didn't point to network. It seems some mutual lock of files in the msi framework. – Olga Pshenichnikova Sep 14 '19 at 17:31
  • 1
    OK, then you might need more information. Let me extend the answer with some information on debugging logging and maybe some other links. Is this MSI compiled from a WiX source? Is it on [github.com](https://www.github.com)? A quick look at the source is usually revealing. – Stein Åsmul Sep 14 '19 at 17:52
  • 1
    I see you work with embedded stuff? Where does that shortcut actually point? What is it pointing to? Is the binary on some embedded device? Is that a URL? Is it a mapped drive? Or some other reference? Just trying to find the overall setup logic. – Stein Åsmul Sep 14 '19 at 18:07
  • 1
    Added some stuff in my answer below. – Stein Åsmul Sep 14 '19 at 21:53
  • 1. I tried to search you over the net, but it seems that you are very hide your identity ) 2. Yes, it actually from WiX. 3. It pointing to binary which is installed in same foled, no network device. Some time before it was working nice, I thing it related to MSI update, not to our code. 4. All my collegues who deals with it leaved for a business trip... So I can not get this issue into the deep... They will come in a week ) My telegramm @theservercat ) – Olga Pshenichnikova Sep 16 '19 at 09:12

1 Answers1

1

Question: A few questions:

  • If you remove the shortcuts in a test version, is the uninstall quick?
  • Is the binary on some embedded device?
  • Does the shortcut point to a URL, a local path, a network path or some other resource - like a mapped drive letter?
  • If you do a major upgrade, is that equally slow to uninstall?
  • Is the behavior different if the embedded device (if any) is connected and not in sleep or hibernation mode while you uninstall?

Need For Speed: I have some general "MSI speed improvement suggestions" here in this old answer from serverfault.com: How can I speed up MSI package install and uninstall?

I would try the MSIFASTINSTALL property and set it to either 3 or 7.

Debug Logging (Verbose): You can sometimes get better information by using a debugging logging option. Here is a command line to use advanced, slow logging for maximum details captured:

msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Path\Your.log

Logging Links: Here is more information and links on MSI logging: Enable installation logs for MSI installer without any command line arguments - this also contains a parameter explanation section for the command line used above. Please check it out. Also check the section "Interpreting MSI Log Files".

Links:

Stein Åsmul
  • 39,960
  • 25
  • 91
  • 164