XNViewMP installation issue when using winget

[pv7721]

XnView: MP latest 2 versions - 64 bit
OS: Windows 10

Since I've discovered the new way of updating information using the winget, I was happy to see XnView software was added to it.

However, the last 2 times I wanted to update (together with whatever other software was to agree), XNViewMP installation failed.

As unfortunately these forums doesn't seem to allow upload .log files, i will post it as a separate message.

The issue is "around" here:

2025-02-18 05:21:54.833 RestartManager found an application using one of our files: Windows Explorer
2025-02-18 05:21:54.833 RestartManager found an application using one of our files: Total Commander
2025-02-18 05:21:54.833 Can use RestartManager to avoid reboot? Yes (0)
2025-02-18 05:21:54.907 Starting the installation process.
2025-02-18 05:21:54.924 Shutting down applications using our files.
2025-02-18 05:22:28.044 Some applications could not be shut down.
2025-02-18 05:22:28.044 Defaulting to Abort for suppressed message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.

i.e. setup manages to close Total Commander, it closes Windows Explorer (probably because of the shell extensions) but it never manages to restart Windows Explorer, my whole taskbar disappears and the only way to have it back is to reboot the PC.

I have 3 different systems I keep up2date with wget, and which have XNViewMP, the issue does NOT happen on Windows 11, and only on one of the two Windows 10 (they're both at the EXACT same of updates). Also the issue does NOT happen if I manually execute the setup, what's interesting is that in this case it complains ONLY about Total Commander being open, nothing about Windows Explorer (this was the only way I could update it on my machine).

Also, in all cases I use OpenShellSetup (that continued the ClassicShell, that makes my Start Menu look like Classic).

[pv7721]

And here's the error log, I managed to copy this time:

2025-02-18 05:21:54.028 Log opened. (Time zone: UTC+01:00)
2025-02-18 05:21:54.028 Setup version: Inno Setup version 6.2.2
2025-02-18 05:21:54.028 Original Setup EXE: C:\Users\pv772\AppData\Local\Temp\WinGet\XnSoft.XnViewMP.1.8.6.0\XnViewMP-win-x64.exe
2025-02-18 05:21:54.028 Setup command line: /SL5="$9170C,55420607,942080,C:\Users\pv772\AppData\Local\Temp\WinGet\XnSoft.XnViewMP.1.8.6.0\XnViewMP-win-x64.exe" /SP- /SILENT /SUPPRESSMSGBOXES /NORESTART /LOG="C:\Users\pv772\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-XnSoft.XnViewMP.1.8.6.0-2025-02-18-05-21-51.718.log"
2025-02-18 05:21:54.033 Compatibility mode: Yes (DetectorsAppHealth)
2025-02-18 05:21:54.033 Windows version: 10.0.19045 (NT platform: Yes)
2025-02-18 05:21:54.033 64-bit Windows: Yes
2025-02-18 05:21:54.034 Processor architecture: x64
2025-02-18 05:21:54.034 User privileges: Administrative
2025-02-18 05:21:54.043 Administrative install mode: Yes
2025-02-18 05:21:54.043 Install mode root key: HKEY_LOCAL_MACHINE
2025-02-18 05:21:54.043 64-bit install mode: Yes
2025-02-18 05:21:54.050 Created temporary directory: C:\Users\pv772\AppData\Local\Temp\is-U87CL.tmp
2025-02-18 05:21:54.098 -- DLL function import --
2025-02-18 05:21:54.098 Function name: MsiQueryProductStateA
2025-02-18 05:21:54.098 DLL name: msi.dll
2025-02-18 05:21:54.098 Dest DLL name: msi.dll
2025-02-18 05:21:54.098 Importing the DLL function.
2025-02-18 05:21:54.100 Successfully imported the DLL function. Delay loaded? No
2025-02-18 05:21:54.669 Found 141 files to register with RestartManager.
2025-02-18 05:21:54.669 Calling RestartManager's RmGetList.
2025-02-18 05:21:54.833 RmGetList finished successfully.
2025-02-18 05:21:54.833 RestartManager found an application using one of our files: Windows Explorer
2025-02-18 05:21:54.833 RestartManager found an application using one of our files: Total Commander
2025-02-18 05:21:54.833 Can use RestartManager to avoid reboot? Yes (0)
2025-02-18 05:21:54.907 Starting the installation process.
2025-02-18 05:21:54.924 Shutting down applications using our files.
2025-02-18 05:22:28.044 Some applications could not be shut down.
2025-02-18 05:22:28.044 Defaulting to Abort for suppressed message box (Abort/Retry/Ignore):
Setup was unable to automatically close all applications. It is recommended that you close all applications using files that need to be updated by Setup before continuing.
2025-02-18 05:22:28.044 User canceled the installation process.
2025-02-18 05:22:28.044 Rolling back changes.
2025-02-18 05:22:28.108 Starting the uninstallation process.
2025-02-18 05:22:28.108 Uninstallation process succeeded.
2025-02-18 05:22:29.623 Deinitializing Setup.
2025-02-18 05:22:29.635 Log closed.

[xnview]

by starting the XnViewMP-win-x64.exe, do you have the same problem?

[pv7721]

Nope, it happens only in winget context, and only on a single machine (but it happened twice, and I always have to pay attention NOT to proceed to the updates' installation, if there's XnView MP update to be installed).

[pv7721]

Initially, it was happen on my machine (Windows 10), but for a while it started to happen on my mum's machine (Windows 11). As it does NOT happen on my dad's machine (also Windows 10), I could run out that this would be an OS issue (somewhat the winget in Windows 10 was different than its counterpart in Windows 11). FWIW, the single thing I could find in common on the two machines where this crash (during installation in winget environment) happens is that they both they are laptops, and it doesn't happen on a desktop.

[RogueScholar]

It's not just WinGet that's succumbed to this issue, but now the xnview.install Chocolatey Community package as well. The debug log of the Chocolatey installer reports the installer self-terminating with an exit code of 5. I don't know much about the framework used to make the XnView installation package, but I have a hunch that this may be related to the inclusion of the shell extension. These package managers are all operating under the same premise and using mostly the same command line arguments that mandate that the installation proceed without any interactivity. For the last couple releases that hasn't seemed possible as the installer always requires an answer to whether I want it to be installed even though I'd done so previously.

Does this sound plausible?