Changing Extension of Word Doc Changes Imaging Behavior - Bug

Imaging the attached corrupted .docx file behaves differently when changing the extension to .0. Changing the extension to .0 is a requirement of our product, and we expect the functionality to be identical in both cases.

This is the output when imaging eargdf.docx:
image.png (56.7 KB)

This is the output when imaging eargdf.0:
image.png (41.6 KB)
image.png (59.3 KB)

eargdf.docx and eargdf.0 are binary equivalent, their MD5 hashes are the same. The .docx imaging errors out, while the .0 imaging completes successfully. We need imaging these two files to behave identically.

eargdf.docx (73.5 KB)

@mpkostek , this is aspose. Imaging related forum please address your question to aspose. Words related forum.

@mpkostek The question is already answered here:
https://forum.aspose.com/t/changing-extension-of-word-doc-changes-imaging-behavior/282542