You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been dealing with SAM seemingly wiping info.dat from time to time upon rebooting my computer for a couple weeks now.
Upon rebooting, it asks for my password, but returns a password error? (not an XML issue iirc, will have to screenshot it once it happens again).
Checking the folder shows a 1kb info.dat file which I don't have a hold of unfortunately, but I vaguely remember seeing a lot of gibberish (meaning the "generated" info.dat is either just corrupted or password-protected in some way?).
Running latest prebuilt release (1.5.4.0 as of this issue) from github.
Renaming the automated "info.dat.bak" provided by SAM works just fine, that's why it's puzzling me.
If you have any clues or ways to get a log out of SAM, I'm all ears
Have a great day!
The text was updated successfully, but these errors were encountered:
Reopening since I moved the entire folder to different drives, and it still does (sometimes) corrupt the dat file upon PC shutdown.
Tried shutting down with SAM still on, closing it before shutting down, re-opening it to close it again so it doesn't stay stuck on "SAM | WORKING" after , but couldn't find a reliable way to reproduce.
Hi!
I have been dealing with SAM seemingly wiping info.dat from time to time upon rebooting my computer for a couple weeks now.
Upon rebooting, it asks for my password, but returns a password error? (not an XML issue iirc, will have to screenshot it once it happens again).
Checking the folder shows a 1kb info.dat file which I don't have a hold of unfortunately, but I vaguely remember seeing a lot of gibberish (meaning the "generated" info.dat is either just corrupted or password-protected in some way?).
Running latest prebuilt release (1.5.4.0 as of this issue) from github.
Renaming the automated "info.dat.bak" provided by SAM works just fine, that's why it's puzzling me.
If you have any clues or ways to get a log out of SAM, I'm all ears
Have a great day!
The text was updated successfully, but these errors were encountered: