Jump to content
LaunchBox Community Forums

Updated to 12.6 a couple of weeks ago; everything was fine and today my settings.xml is corrupted


3dlollo

Recommended Posts

This is a weird one; I didn't use LB much recently, so few weeks ago I ran it to get the latest update, and it did update to 12.6. The app started as usual, everything was fine, I quit the app and move on.

Today I launched it and I get an error message about my settings.xml having issue, and the message invite me to restore a backup. I opened the file and there is nothing except a string of NUL in it. Goes without saying that I didn't make any backup since I never had such issues.

Is this something that was reported by anyone? I have no repro steps except the ones I just described. The backup for the shutdown was also corrupted, although the startup one before was not. Which makes me think that something went south after the 12.6 update.

Please let me know if there is anything saved/logged that I can look at.Thanks

failure.PNG

corrupt.PNG

Edited by 3dlollo
Link to comment
Share on other sites

This usually happens when you kill Launchbox while it is writing to files, which it does when you close it. You should have backup zips in your Launchbox/Backups folder, i believe this is on by default, so unless you specifically turned that feature off (which would of been unwise) you should have backups. just unzip the newest one and look at the settings.xml, if it looks OK copy it to Launchbox/Data and overwrite, if that also looks bad try the next older one, and so on.

Link to comment
Share on other sites

6 hours ago, neil9000 said:

This usually happens when you kill Launchbox while it is writing to files, which it does when you close it. You should have backup zips in your Launchbox/Backups folder, i believe this is on by default, so unless you specifically turned that feature off (which would of been unwise) you should have backups. just unzip the newest one and look at the settings.xml, if it looks OK copy it to Launchbox/Data and overwrite, if that also looks bad try the next older one, and so on.

I thought so, although I shut it down as I always do.

I found that not only the config file was corrupted but all the xml files in the data folder. The good thing is that the backup before the last one was still recent enough and not corrupted (the backup was corrupted too), so I managed to restore its state.

First time I get this behavior, and I've been using LB for quite a while now; so I connected the last update to this issue, although since it happened only once it is not statistically relevant, unless other people got that too.

Updating to 12.8 today; will keep an eye to see if this happens again.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...