While using the latest version of Aspose.Words i.e. 17.2.0, we managed to reproduce this issue on our end. We have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-14972. Your thread has also been linked to the appropriate issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.
Unfortunately your issue (WORDSNET-14972) is not resolved yet. Our product team has completed the analysis of this issue and the root cause has been identified. We will inform you via this thread as soon as this issue is resolved. We apologize for any inconvenience.