I'll try to keep this brief. Basically, I've given my computer a complete makeover. New mobo, new graphics card, new hd, new os. I used to keep my passwords safe through Keepass on my old system, which used XP. Now, after upgrading to 7, I attempted to access data off of my old HD to help make the move smoother
However, I've run into a major snag: I can't use Keepass to access my old passwords because the program believes I am a different user. It encrypts the old passwords in a hidden file, and I cannot even *find* the file to open through Keepass so I may enter my usual password and gain access to my other passwords!
I still have all my old parts. What are my options here? I just want to find the damn .kdb or .pwd or whatever file that Keepass is keeping my passwords in so I can open it just like I used to on XP. Is my only option running my hd through my old mobo or something, so it properly recognizes me as the user and stops hiding the file?
Please, someone give me some guidance. This is very frustrating as it has caused me to be locked out of my steam and email accounts
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you were using keepass v2.x the file has a .kdbx extension.
I have never used v1.x but I believe that version uses a .kdb extension.
I do not believe your .kdbx file is missing, its probably on your old HD and findable via a search command.
As for opening your .kdbx once you find it you kinda need to know how told keepass to encrypt the .kdbx when you first created the file.
Specifically when you first created the .kdbx you were presented with three encryption options.
These were presented as check boxes and you could have select any mix of the three but you had to have selected at least one.
a) A password (something you know)
b) key file (something you have)
c) a windows user account (something you are)
As already said, Each of these options were mere check boxes when you created your .kdbx
With regard to option "C", this optoin included the following text:
"If the windows account is lost, it will not be enough to create a new account with the same username and password."
"A complete backup of the user account is required."
"Creating and restoring such a backup is not a simple task."
"If you do not know how to do this do not enable this option"
Based on the description of your problem it is not clear if you are faced with trying to overcome item c (or not).
Since you say you can not find your .kdbx file I tend to think you are not yet faced with this problem.
If you were faced with this problem your question woudl be about not being able to open/decrypt the file versus not being able to find it.
If option c is your problem I can not help you, but assuming it is not,
I would start by doing a simple file search of your old HD looking for any/all *.kdb* files.
You should find it.
Once you get keepass back up and running.
Please look into protecting your .kdbx with as many backups as possible.
I reconmend you create multiple "auto-sync" triggers which will automatically peform a 2 way record sync the to files on folders you have defined. this two way record sync would occur each time you open your .kdbx
I personally use multiple auto sync triggers
- one to sync to my USB drive (if present)
- one to sync to my network backup device (if present)
- one to sync to my dropbox folder (if present)
the presence of these triggers guarantees remote versions of my kdbx are always current.
Conversly, if a remote .kdbx contained a change not present on the main .kdbx it would be automatically brought in.
What this pluggin does is allow you to multiplex the save of your kdbx to as many different devices as you like.
This pluggin will also maintain "x" versions of historical copies of your .kdbx on the multiplexed locations.
How nice would it have been to surf to a folder and find 20 historical copies of your .kdbx all timestamped for you.
Between multiplexing your save to multiple devices, as well as performing a sync to multiple remote files each time you open. You would have a cornicopa of options/backups/safeguards to your .kdbx making it impossible to ever lose your file.
As for how to create a sync trigger here is an example:
tools - triggers - add
Properties:
Name: autosync_1
x enabled
x initially on
Events:
opened database file equals c:\my_keepass.kdbx
Conditions:
file exists e:\usbfolder\my_traveling_keepass.kdbx
Actions:
Activate database c:\my_keepass.kdbx
synchronize active database with file e:\usbfolder\my_traveling_keepass.kdbx
Activate database c:\my_keepass.kdbx
Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you have any idea where your database was stored? Was it in My Documents?
Can you see the other files in that location on the old hard disk? If not you may have to change the file security settings to allow you to access the files. How to take ownership of files.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the replies you two. I should've clarified something in my original post
A: Yes, this is v1.x. It's a .kdb or .pwd file type, according to the automatic queries for filetypes the program makes when I open it
B: I *believe* it was with my other Keepass files in its folder, which is why I am completely mystified that I cannot find it
C: In regards to how I told Keepass to encrypt the file, I believe I simply used A, a password. I cannot be certain, however, as it has been many months since I began using it
D: In regards to the question of whether or not I can access other files on the hd, the answer is yes I can. Changing file security settings, at the very least, is something I'm capable of
Unfortunately for everyone involved, a hd-wide search for all kdb and pwd filetypes produces no results. I am simply at a loss. I am practically positive that it was there prior to taking apart my computer. Is there nothing else I can attempt to do to locate my password database?
Your recommendations are duly noted, develop1. I appreciate the sentiment. Hopefully when all this is behind me I'll learn from the ordeal and sync my password databases just so shit like this doesn't happen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
lets ignore the extension for a moment, its possible the extension was omitted or is something else, try doing wild card searches on any portion of the base name - instead of my_keepass.kdb look for *my*
You are going to get way more results than you want however if you know when you last modified the .kdb your choices should narrow considerably. I hope you find the file - be it by partial name or date alone, Good luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will try to continue refining my searches, although nothing has turned up yet. In the meantime; assume that I don't find it. What then? I was thinking of getting my old motherboard out and getting my old comp up and running to try to access the hd then. I am quite positive that the database should be in the same place as it was as I didn't move it prior to dismantling my old PC, as I had assumed I would simply be able to access it on the old hd through my new system
If nothing else, maybe Keepasses file opening prompter will automatically track down the database, wherever the hell it is
Is there anything else left for me to try?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Open the old KeePass.ini (with KeePass.exe) and look for the "KeeLastDb=" line. That is where you need to look for database file. The database file will only be 3 or 4kB.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll try to keep this brief. Basically, I've given my computer a complete makeover. New mobo, new graphics card, new hd, new os. I used to keep my passwords safe through Keepass on my old system, which used XP. Now, after upgrading to 7, I attempted to access data off of my old HD to help make the move smoother
However, I've run into a major snag: I can't use Keepass to access my old passwords because the program believes I am a different user. It encrypts the old passwords in a hidden file, and I cannot even *find* the file to open through Keepass so I may enter my usual password and gain access to my other passwords!
I still have all my old parts. What are my options here? I just want to find the damn .kdb or .pwd or whatever file that Keepass is keeping my passwords in so I can open it just like I used to on XP. Is my only option running my hd through my old mobo or something, so it properly recognizes me as the user and stops hiding the file?
Please, someone give me some guidance. This is very frustrating as it has caused me to be locked out of my steam and email accounts
If you were using keepass v2.x the file has a .kdbx extension.
I have never used v1.x but I believe that version uses a .kdb extension.
I do not believe your .kdbx file is missing, its probably on your old HD and findable via a search command.
As for opening your .kdbx once you find it you kinda need to know how told keepass to encrypt the .kdbx when you first created the file.
Specifically when you first created the .kdbx you were presented with three encryption options.
These were presented as check boxes and you could have select any mix of the three but you had to have selected at least one.
a) A password (something you know)
b) key file (something you have)
c) a windows user account (something you are)
As already said, Each of these options were mere check boxes when you created your .kdbx
With regard to option "C", this optoin included the following text:
"If the windows account is lost, it will not be enough to create a new account with the same username and password."
"A complete backup of the user account is required."
"Creating and restoring such a backup is not a simple task."
"If you do not know how to do this do not enable this option"
Based on the description of your problem it is not clear if you are faced with trying to overcome item c (or not).
Since you say you can not find your .kdbx file I tend to think you are not yet faced with this problem.
If you were faced with this problem your question woudl be about not being able to open/decrypt the file versus not being able to find it.
If option c is your problem I can not help you, but assuming it is not,
I would start by doing a simple file search of your old HD looking for any/all *.kdb* files.
You should find it.
Once you get keepass back up and running.
Please look into protecting your .kdbx with as many backups as possible.
I reconmend you create multiple "auto-sync" triggers which will automatically peform a 2 way record sync the to files on folders you have defined. this two way record sync would occur each time you open your .kdbx
I personally use multiple auto sync triggers
- one to sync to my USB drive (if present)
- one to sync to my network backup device (if present)
- one to sync to my dropbox folder (if present)
the presence of these triggers guarantees remote versions of my kdbx are always current.
Conversly, if a remote .kdbx contained a change not present on the main .kdbx it would be automatically brought in.
In addition to this I reconmend you install pluggin
http://www.keepass.info/plugins.html#databasebackup
What this pluggin does is allow you to multiplex the save of your kdbx to as many different devices as you like.
This pluggin will also maintain "x" versions of historical copies of your .kdbx on the multiplexed locations.
How nice would it have been to surf to a folder and find 20 historical copies of your .kdbx all timestamped for you.
Between multiplexing your save to multiple devices, as well as performing a sync to multiple remote files each time you open. You would have a cornicopa of options/backups/safeguards to your .kdbx making it impossible to ever lose your file.
As for how to create a sync trigger here is an example:
tools - triggers - add
Properties:
Name: autosync_1
x enabled
x initially on
Events:
opened database file equals c:\my_keepass.kdbx
Conditions:
file exists e:\usbfolder\my_traveling_keepass.kdbx
Actions:
Activate database c:\my_keepass.kdbx
synchronize active database with file e:\usbfolder\my_traveling_keepass.kdbx
Activate database c:\my_keepass.kdbx
Hope this helps.
Do you have any idea where your database was stored? Was it in My Documents?
Can you see the other files in that location on the old hard disk? If not you may have to change the file security settings to allow you to access the files. How to take ownership of files.
cheers, Paul
Thank you for the replies you two. I should've clarified something in my original post
A: Yes, this is v1.x. It's a .kdb or .pwd file type, according to the automatic queries for filetypes the program makes when I open it
B: I *believe* it was with my other Keepass files in its folder, which is why I am completely mystified that I cannot find it
C: In regards to how I told Keepass to encrypt the file, I believe I simply used A, a password. I cannot be certain, however, as it has been many months since I began using it
D: In regards to the question of whether or not I can access other files on the hd, the answer is yes I can. Changing file security settings, at the very least, is something I'm capable of
Unfortunately for everyone involved, a hd-wide search for all kdb and pwd filetypes produces no results. I am simply at a loss. I am practically positive that it was there prior to taking apart my computer. Is there nothing else I can attempt to do to locate my password database?
Your recommendations are duly noted, develop1. I appreciate the sentiment. Hopefully when all this is behind me I'll learn from the ordeal and sync my password databases just so shit like this doesn't happen
lets ignore the extension for a moment, its possible the extension was omitted or is something else, try doing wild card searches on any portion of the base name - instead of my_keepass.kdb look for *my*
You are going to get way more results than you want however if you know when you last modified the .kdb your choices should narrow considerably. I hope you find the file - be it by partial name or date alone, Good luck.
I will try to continue refining my searches, although nothing has turned up yet. In the meantime; assume that I don't find it. What then? I was thinking of getting my old motherboard out and getting my old comp up and running to try to access the hd then. I am quite positive that the database should be in the same place as it was as I didn't move it prior to dismantling my old PC, as I had assumed I would simply be able to access it on the old hd through my new system
If nothing else, maybe Keepasses file opening prompter will automatically track down the database, wherever the hell it is
Is there anything else left for me to try?
Open the old KeePass.ini (with KeePass.exe) and look for the "KeeLastDb=" line. That is where you need to look for database file. The database file will only be 3 or 4kB.
cheers, Paul
Thanks for the suggestions everyone. After trying Pail459's tip, I did actually manage to locate it and reobtain my passwords
You've all been very helpful, thanks!
Now you need to backup your database regularly - minimum of once a week.
cheers, Paul