Thanks for your inquiry. After an initial test with Aspose.Words 16.11.0, we were unable to reproduce this issue on our end (see attachment). We would suggest you please upgrade to the latest version of Aspose.Words. You can download it from the following link: