- 1
We are unable to decode the file storing your credentials. Need help?!
You are about to reply to a thread that has been inactive for 1407 days.
Please take a moment to consider if this thread is worth bumping.
Please take a moment to consider if this thread is worth bumping.
Question
Aisling Jameson
I am using the firestorm viewer. I was in the middle of logging off when my computer unexpectly shut down on me. I reboot it and upon relogging into sl the following message appeared:
We are unable to decode the file storing your credentials. At this point saving or deleting your credentials will earse all those previously stored. This may happen when you change your network setup. Restarting the viewer with the previous network configuration may help recovering your saved login credentials.
I have tried uninstalling the viewer and restarting. I have tried to look for any extra hidden files (even though I can't seem to locate certain parts like c:\user\name\library ... or c:\user\name\appdata. I also can't seem to find where the xml files are located as another post has stated to try to delete.
Please if someone can help me or walk me through this I would greatly appreciate it.
Update: 7/7/13
I followed the link as provided and did a clean uninstall and deleted all hidden files. It is no longer stating the previous error message but now will not allow me to login. I have double checked my user name and password and it should work. I have even tried logging into Smith, Hippo Hallow and Hatton but it still says that I cannot login due to wrong username/password or caps lock on.
Additional help is needed. Thank you!
Update part 2
I tried a new password and that still didn't help. I found that previously (before the new install) I was able to log into SL with my first/last name and no space between them. After the new install there has to be a space between first/last name. Everything is in working order now.
Link to comment
Share on other sites
Top Posters For This Question
7
7
5
4
Popular Days
Apr 14
7
Jul 7
4
Jan 7
4
Mar 4
4
Top Posters For This Question
Lindal Kidd 7 posts
LittleMe Jewell 7 posts
NoahGoldFox 5 posts
angelpatty 4 posts
Popular Days
Apr 14 2017
7 posts
Jul 7 2013
4 posts
Jan 7 2020
4 posts
Mar 4 2019
4 posts
Popular Posts
Lindal Kidd
I'm not sure what all the fuss is about. I've gotten this message a time or two when I updated my Firestorm viewer (including with a clean install), and at least once when Windows 10 did updates.
augmeta
Sorry for the necro bump but I thought I would leave this here to help anyone who has this issue in future. I have just had this problem in Firestorm after recieving a new router from my ISP. I solved
Whirly Fizzle
This is unfortunately expected behaviour with the way login credentials are stored. The login credentials are hashed using the machine ID. Larger Windows 10 updates often issue a new machine ID - he
Posted Images
53 answers to this question
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now