FileCorruptedException when opening OneNote files


A FileCorruptedException is thrown when trying to open a .one document with Aspose.Note.

The exception message is “The MD5 hash is not correct for referenced struct.”

The .one file was created with MS OneNote 2016 and can be opened with OneNote without any problems.

This exception is thrown when using Aspose.Note for .NET 17.8 as well as the lastest available version 18.9, when executing the following code:

// filePath points to the file: Section
var fileStream = new FileStream(filePath, FileMode.Open);
var doc = new Aspose.Note.Document(fileStream);

Files: (175.1 KB)



We have reproduced this issue and it has been logged under ID “NOTENET-2675” for further investigation. You will automatically be informed here once we have more information to share.


Hi there,

Is there an ETA on this issue?

Thanks in advance…



We are working on this issue and it is not resolved yet. We will update you here soon.


Just to say one more person interested in this bug fix (btw. I also opened more than few OneNote tickets, all ending with bug creation). If you can accelerate a bit with OneNote that would be great (this was created 3 months ago :frowning: )



We regret to share that the issue is not resolved yet due to other pending issues in the queue. Please note that issue is logged under free support model and has low priority. Moreover, if you want this issue to be resolved on an urgent basis, you may opt for the paid support where issues have high priority.

Furthermore, please be patient and give us some time, we will let you know as soon as we have more information to share.


I need this bug fixed, too. Any ETA from Aspose?



I am afraid, still the issue is not sorted out. Also, there is no ETA on it yet.

Once we have any information, we will share it with you.


Thank you for your reply, but this is needed by multiple people. Any chance of an ETA? And it’s a straight-up shortcoming in the OneNote handler — not something obscure.


@Amjad_Sahi, if we had Paid Support ($1,699 per year for a maximum of six cases), how fast could we expect this bug to be fixed?

BTW, I can totally understand paying extra (“Paid Support”) to get higher priority for new features. But this is a bug fix. Shouldn’t bug fixes just be handled fast based on the merits of the bug, rather than based on how much the reporting companies have paid Aspose?



Thanks for sharing your concerns.

Well, if you avail paid support for the issue, it would take higher priority for resolution for sure. Regarding how fast we could fix it, well, it totally depends upon complexity of the issue.

In normal support, we try our level best to deal with every customer fixes and other enhancements in a timely fashion, But for certain scenarios, we unfortunately cannot guarantee a delivery date to every customer issue due to different factors. We work on issues on first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers. There might be some other limitations involved for resolution of issues too due to important updates, new features and other priorities tasks (on hand) which needs to be addressed first.

Anyways, could you spare us a little time as we will thoroughly evaluate the issue and then could give you updates or ETA (if possible).

We are sorry for any inconvenience caused!


Thank you for your reply, @Amjad_Sahi.

I do still believe that Aspose bugs which cause file harm should be generally given higher priority than “first come, first served.”


@JohnGrahamLT, @dr_oli, @eirens,

We have made a quick investigation of the issue.
It seems the sample file is really corrupted but OneNote automatically successfully recovers it.

  1. If open and save the sample file by OneNote 2016 then Aspose.Note successfully loads saved file.
  2. We manually prepared *.one file with intentionally corrupted hashes for some elements:
  • Aspose.Note failed to load these files
  • OneNote 2016 successfully loads these files
  • if open and save these files by OneNote 2016 then Aspose.Note successfully loads saved files.

The algorithm used to recover corrupted document is not known.
So at the moment we consider providing an option to load corrupted documents + flag to signal user that integrity of the provided document is under question.
Due to having a lot of other high priority items we might not fix this issue earlier than in v19.5 release.


We investigated your issue further.
We struggle to do further investigation and plan to contact with Microsoft support desk about it. Please, let us know if it is acceptable for you and we can share your files with third party (Microsoft)?


The issues you have found earlier (filed as NOTENET-2675) have been fixed in Aspose.Note for .NET v19.9. This message was posted using BugNotificationTool from Downloads module by ahsaniqbalsidiqui