Hi Kerry:
Thanks a lot for your reply. Yes, I think the files are encrypted
while I was trying to transfer them from the external HD to the new
laptop with Vista.
I think what I did is as follows: At first, I was trying to copy the
file from the HD to the laptop, but got the error of "Access Denied".
Then, I right click the files's properties and click the security tab,
and change the files' owner to the account I used to log in the new
laptop. Then I try to copy again, but it did not work neither, then I
gave up and disconnect the external HD and connect it back to my old
XP Home laptop, then I found the files are shown as green and unable
to open anymore. I connected the HD to the new laptop with Vista again
trying to see whether I can open those files from there? But quite
unfortunately, they are shown as green in Vista laptop as well, and
unable to open neither.
I highly appreciated your help with this issue! Just cannot lose those
data. Is there any way I can do to recover this, I did not change
password nor account for the new laptop with Vista.
Regards
Annie
Sorry, odds not good you can recover. Sadly yours is the second post
in a few days I've seen where somebody did the same kind of thing. The
good news is you see encryption works. Bad news, maybe too well. When
you use Windows' build-in encryption the encrypting is tied to the
instance of Windows that the files were encrypted under. What that
means will be come clearer later.
NEVER copy any file in its encrypted state, you're asking for trouble.
A long shot, but did you make a personal encryption certificate along
with a recovery agent certificate and put it on a floppy? I remember
XP nags you do this, I'm guessing most people don't bother. This is
the only way I can think of to still unlock the files. It has to be
done BEFORE something bad happens, not after, won't have any effect if
you try to make them now, but I haven't tried so who knows.
IMPORTANT for anybody that has encrypted files. Before moving to Vista
you MUST decrypt them all first. Don't and those files are probably
gone forever if you copy/move them in a encrypted state, depending on
what you have or havne't done.
Here's why:
It is very easy, some would say too easy to lose your private key.
This isn't a physical key, rather it is a bit of code that only
Windows knows about and hides and that too, of course, is encrypted,
but not with your key, one that Windows creates with further encoding
based on the instance of Windows the key was created in.
In English, that means this:
Lets say you have your data all encrypted and stored on your drive E.
For whatever reason you decide to reinstall Windows or upgrade to
another version of Windows or move this "E" drive to another box with
the same version of Windows.
The human midset would be why should you worry, you're going to
reinstall Windows on your C drive, your encrypted files are safe and
sound on your E drive.
Wrong!
When you reinstall Windows (or try to upgrade) it won't tell you but
its creating a new SID or security indenifier for each user and that
happens even if you do everything exactly the same as before. In order
words even if you use the same name for your computer, the same user
names, the same log on passwords it is still "different" to Windows
because of how it makes the SID. That's because part of the encryption
key is based on real time events, like a date or system time so the
new encryption certificate is different from the one its replacing and
as far as Windows cares, you're a intruder and it won't (actually
can't) access your priceless unreplacable encrypted files any longer.
Its too late if you don't already have one. For others with encrypted
files right now make a data recovery agent. This is just a second user
account. This is a safety net just in case your encryption certificate
you should have made itself gets corruputed or your lose the floppy.
In effect you're going to make a second trusted user with
administrative rights that will also be able to decrypt YOUR encrypted
files. Which may defeat the purpose. How is a little involved, but
covered in Microsoft's KB, somewhere. The last several paragraphs
apply to XP, could have all changed in Vista.