Honorbuddy stops after logging in with this error

[TimeSaverZealot]

Honorbuddy logs in, then shows a long error message in red color and stops with all its buttons grayed out:

System.TypeInitializationException: The type initializer for 'Styx.Helpers.LevelbotSettings' threw an exception. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos)
   at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlReader.MoveToContent()
   at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
   at System.Xml.Linq.XElement.Load(String uri, LoadOptions options)
   at Styx.Helpers.Settings.Load()
   at Styx.Helpers.Settings..ctor(String settingsPath, String oldSettingsPath)
   at Styx.Helpers.LevelbotSettings..ctor()
   at Styx.Helpers.LevelbotSettings..cctor()
   --- End of inner exception stack trace ---
   at Honorbuddy.MainWindow.‏‎‫‪‫***‫*‏*‫**​*‬​*‬‬*****()
   at Honorbuddy.MainWindow.\]UV!ZED\&|;X>Yq/\.wJd@nlD=!.MoveNext()

I've already a “Repair” run of the installation file. I'm going to try complete uninstallation, then re-installation next and update this thread with how things go. However, regardless to what happens after complete re-installation, I thought it may be worth it to share this error with you. This error happened after a sudden shutdown of my machine.

 

[chinajade]

Hi, TimeSavorZealot,

This article will sort the problem for you, and explain why it can happen:

Honorbuddy:HelpDesk:Corrupted settings​

cheers,
chinajde

 

[TimeSaverZealot]

Thank you!

That would've been easier than a complete uninstallation, but obviously the complete uninstallation also worked. I'll keep the Settings folder in mind, though, should this happen again. Thanks again for the speedy reply and helpful info.