12-27-2014 08:34 AM
Secure Access V2.0 returned an error when I tried to open my vault. After I type in the password I get the error message, "Invalid Parent Path In Archive". When I click 'OK' I get the standard "4 Ways To Protect Your Data" screen as usual when I open a vault. When I click the 'Next" button I get the error, "This vault could not be loaded, it may be located on another computer or the original vault file has been manually removed." After I click OK the main screen opens. It has the vault listed, but if I click on it I get the same error message. Whats going on? How can I access my vault? It is my backup for important documents and archives.
No, I haven't moved or deleted the vault. The vault is located on the memory stick.I only work from one computer running Windows 7. This particular Sandisk 32 Extreme is never used with any other computer. I haven't changed the password. Everything was working fine until I just couldn't sign in.
01-02-2015 05:00 AM
There are some steps you can try in order to recover the vault files .
1) copy the vault and secure access application from the write protected drive over to the new drive
2) run secure access on the new drive
3) when it prompts to create a new vault go ahead and create a new vault with the exact same password as the old vault
4) encrypt any file in the new vault (this will generate two new system files)
5) close secure access
6) open the vault folder on the new drive via windows explorer, navigate to the system files folder, you should see several files, among them are two sets of "USB Flash Drive-XXXXXXXXXXXXXXX.idx and .bak files
7) Looking at the date stamps of the files, 2 will be older and 2 will be newer (you can also check on the old write protected drive to confirm the names of the older files, the older files contain the encryption information needed however the file name is associated with the previous drive we will need to rename the old files)
8) copy the 2 newer files and paste them into any temporary location outside of the flash drive (i.e.. desktop)
8) once you've copied the two new files to a temporary location delete the originals from the system files folder on the flash drive.
9) go to the temporary location and copy only the file name from the .idx file (the file name, not the file itself)
10) go to the vault / system files and rename the old .idx file with the name you copied from the new .idx file
11) repeat the same for the idx.bak file
12) now you should have renamed the old .idx and .idx.bak files with the names of the newly generated system files.
#Missing the keyboard? Press F1 for help#
06-24-2015 11:47 AM - edited 06-24-2015 11:48 AM
Deponia... Here is my issue... along the same lines...
When I tried to log in to my vault it said invalid archive...
I still have the system files full of the .dat files and I know the password... How I can get to where SecureAccess recognizes the vault again... or at the very least I can put the .dat files back under a new root directory so that I can decrypt them...
I have tried moving the system files folder over to my external HD... then opened a new vault with SAv2 using the same password then moving the .dat files into the new system files folder just as they appear before but when you open the vault it does not display these files...
Is it because of new .idk.bak file created?
Any help would be great... I have irreplaceable photos of my infant child on this thing!!
06-26-2015 03:46 AM
if you tried the steps and you still cant recover the files from the vault i would suggest providing pictures of the error message and the files to sandisk support so they can help you recover the files from the vault
i hope you can recover your important data from the drive.
#Missing the keyboard? Press F1 for help#
05-31-2016 01:29 PM
OMG - v3.0 Invalid parent path in archive.
But I do not have a second sandisk drive laying around - what is the fault that caused this please?
Is there a workaround, since this problem is obviously not new?
Thank you, data_guy
04-04-2017 04:33 PM
Same problem happend to me just now.
SanDisk customer support was helpless.
The level 1 and Level 2 tech didn't even know about re-naming a file. At every step, they only read from a script.
Re-installing the executable did NOTHING.
After the PW, the same error message came up (EVERY time): " Invalid path in archive"
Loading different versions of the SecureAccess did nothing.
(then they tried to blame the version difference on me).
Three hours of my life never to get back.
At the end, all they said was "sorry for the inconvenience" and 60 GB of encrypted data blown to electron dust.
All they cared about was the USB drive worked, and since Encryptstick wrote the software, SanDIsk is incapable of supporting it.
Come on guys: software can be fixed !!