Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Denc nañu waxtaan wii. Yónneel yeneen laaj soo soxlaa ndimbal.

TB 102 not remember passwords

  • 1 tontu
  • 1 am na jafe-jafe bii
  • 11 views
  • i mujjee tontu mooy dchod

dchod
dchod
more options

My TB profile is on my home NAS, which has worked fine until I installed TB 102 (64-bit). Now when I enter my account password and check the Save Password box, login to the account fails and the password is not saved. I can access my accounts if I don't check the Save Password box.

I've tried deleting the key4.db and cert9.db files. While they are recreated, it doesn't fix the problem. There are no file called "logins*" in the profile directory, which I've seen mentioned in previous discussions of this type of problem.

I used Sysinternals PROCMON to try and get some idea what's going on; i.e., what files are referenced when saving passwords. I did notice repeated attempts to read key4.db at offset 24 , length 16 which always failed with NETWORK_ERROR. Other accesses to key4.db succeeded.

I have programming experience and am willing to use the Debugger under Developer Tools. I just have no idea what to look for.

Thnk you for any suggestions you can provide.

My TB profile is on my home NAS, which has worked fine until I installed TB 102 (64-bit). Now when I enter my account password and check the Save Password box, login to the account fails and the password is not saved. I can access my accounts if I don't check the Save Password box. I've tried deleting the key4.db and cert9.db files. While they are recreated, it doesn't fix the problem. There are no file called "logins*" in the profile directory, which I've seen mentioned in previous discussions of this type of problem. I used Sysinternals PROCMON to try and get some idea what's going on; i.e., what files are referenced when saving passwords. I did notice repeated attempts to read key4.db at offset 24 , length 16 which always failed with NETWORK_ERROR. Other accesses to key4.db succeeded. I have programming experience and am willing to use the Debugger under Developer Tools. I just have no idea what to look for. Thnk you for any suggestions you can provide.

All Replies (1)

dchod
dchod Ki laajte
more options

I created a new profile, imported everything from the profile that was problematic, and everything now works. As the Guardian of Forever said, "All is as it was before."