Doing "Extract" on this MSI file produces no results

[RDHWalker]

Loading provided MSI file into lessmsi and doing "Extract" produces no output, and no error message.

MSI file is too large to attach to this report. Please download zipped copy from:
https://1drv.ms/u/s!AjghbfTMZUJuh9lUCbagMQll0GMjUQ?e=SgOzCx

Repro:

• open provided MSI file into lessmsi;
• if necessary, click "Select All".
• click "Extract";
• select target folder, click OK;
• a popup "Extracting (Initializing)" appears then quickly disappears;
• observe that no results are produced, and no error messages.

Expected:
that the MSI file be unpacked into the target folder, or that some explanatory error message be provided.

Other info:
Another application (jsMSIx.exe) is capable of extracting the contents of this MSI file.

Edition Windows 10 Pro
Version 22H2
OS build 19045.4291
Experience Windows Feature Experience Pack 1000.19056.1000.0

[activescott]

@mega5800 If you're looking for issues to investigate, this would be a good one since it has been reported by an active user recently.

[mega5800]

@activescott, I will check what is going on with this ticket during the day.
Thank you.

[mega5800]

@RDHWalker, are you using LessMsi CLI or LessMsi GUI?

Thank you.

[RDHWalker]

@RDHWalker, are you using LessMsi CLI or LessMsi GUI?

The GUI.

[mega5800]

A few updates from a brief investigation.

I am able to extract the contents of Sibelius.msi to the LessMsi GUI, by using the app itself or by right clicking on the msi file and selecting the option “Lessmsi Explore”.

However, once I try to run a right click menu option called "Lessmsi Extract Files", I encounter the described problem in this ticket.
A CMD window appears for a few seconds, and leaves an empty folder that supposed to have the msi file contents.

I started debugging the code and I believe I found a cause for the issue in this line

I get the next exception thrown: System.Exception: 'Failed to open cabinet. Last error:MSPACK_ERR_DATAFORMAT'
And here is the visual exception I get as well:

@activescott, I believe that the problem is perhaps caused by some part in MSCabinet class under the LibMSPackN library.

[activescott]

Thanks for looking at this one @mega5800 I also encountered the error, and I'm not exactly sure what the issue is yet, but was struggling to setup debugging on a C++.NET library that LibMSPackN library is. I'll have to spend more time on this later. Currently am busy with some other projects.