Hi AmandaMYOB
I keep the software up to date as updates are released and am currently on version 2026.2.1.12, which I installed recently.
Unfortunately, the updates have made no difference to the frequency of the crashes. If anything, they appear to be increasing.
I have not been performing online backups or restores. These crashes are occurring on launch and during normal day-to-day use of the software.
Regarding diagnostic logs, I submit the automated email report to MYOB every time a crash occurs.
Are you able to check your end for the hundreds of error report emails that I have sent through?
The following are sample error messages:
Hey Matty72
You may need to manually update your .NET Framework to get around the error message. Please follow the instructions below. If you continue to experience an error even after continuing these steps, please raise a support ticket via your My Account dashboard and we'll be able to take an in-depth look for you from there.
Please note: Please consult an IT professional for further assistance if you are not comfortable completing these actions alone. If the box is blank or you get an error activating a component, you will also need to reach out to an IT professional as this is a Microsoft component that interacts with the operating system, not just AccountRight.
These instructions apply for Windows 10, 8.1 and 8.
Hi AmandaMYOB,
Thank you for the response, however I need to push back on this advice.
I am an IT professional and .NET developer. This is not an isolated incident. I have experienced a persistent pattern of errors across AccountRight that point to application-level defects, not environmental issues. Two recent errors illustrate this clearly.
**Error 1: Assembly mismatch (System.TypeLoadException)**
This error was caused by a method signature mismatch between MYOB's own signed assemblies: Huxley.UI.Decorators and Huxley.UI.Framework, both version 2026.2.1.5, both bearing PublicKeyToken=947f70fecdd4159f. This is unambiguously an internal MYOB binary compatibility issue, likely a DLL mismatch introduced in the 2026.2.1 release. The .NET runtime assemblies (mscorlib, System.Core) appear only in the stack trace as the reflection machinery that surfaced the error. They are functioning correctly.
**Error 2: XmlSerializationReader type load failure**
'Could not load type System.Xml.Serialization.XmlSerializationReader from assembly System.Xml, Version=4.0.0.0.' While System.Xml is a Microsoft assembly, XmlSerializationReader has been present in every version of .NET Framework since 1.x. A genuinely missing or corrupt System.Xml would break core Windows functionality far beyond AccountRight. The most likely cause is that MYOB's runtime-generated XML serialisation assemblies, or the binding redirects in MYOB's application configuration, are mismatched against the installed framework. Again, an application packaging and deployment issue on MYOB's side.
In both cases, the root cause lies within MYOB's own assemblies and configuration, not the .NET Framework installation or the operating system.
Additionally, the troubleshooting steps provided in your response reference Windows 8 and 8.1, both of which have been out of Microsoft support since January 2016 and January 2023 respectively. These instructions are not applicable to a current, supported Windows environment.
The recurring nature of these issues, combined with support responses that redirect blame to the OS or .NET Framework, is not an acceptable resolution. I would ask that this be escalated to your development or tier-2 support team, and that the broader pattern of experienced errors be reviewed.
Hey Matty72
Thanks for the detailed explanation. If you haven't already, can you please raise a case from your My Account dashboard with the diagnostic log attached. Let me know what the case number is and I will check this with the team and come back to you when I have more information.
