a packaged dll file is changed in MSIX-packaging

[kerenor]

Hello,
We've encountered an issue in which an application that worked correctly outside MSIX worked extremely slower when packaged in MSIX and launched.
Debugging the issue showed us this is because it is failing to correctly load one of its dll files (that are included in the MSIX package as well).
Specifically, it's turbojpeg.dll (which is part of Zoom sdk).

We unzipped the MSIX using winrar & used dumpbin.exe on the turbojpeg.dll file that was inside as well as on the file that is configured to be included in the project - their headers are slightly different, see below the differences("broken file" is the file that was extracted from MSIX, and "working file" is the file in the filesystem):

turbojpeg.dll-headerdiff.jpg (130.66 KiB) Viewed 7199 times

This is reproducible when creating a project that include only the turbojpeg.dll file, without digitally signing it (so it's not related to the digital signature).
(I will send the AIP file & relevant dll to support@advancedinstaller.com , or if there is another mail please let me know, For some reason I get a general "ERROR" when trying to upload them.)


What causes this change? How can we prevent it & maintain the same file?

Thanks, Keren.

[kerenor]

if interested -
This behavior doesn't happen with the microsoft msix editor, which creates a package that contains a dll that is binary-same to the dll I intended to package.

Would appreciate an explanation for this

Thanks
Keren

[Liviu]

Hello Keren,

As I see, my colleagues have replied to you over the email.

Please continue the conversation there to avoid duplicate threads.

Best regards,
Liviu