cannot have File Access

I just "redone" my computer,
Motherboard,mem,Hd, Big upgrade... kept my old hd as was
and used as slave{because folders I wanted to keep). They
were encrypted, now I cannot access them to retrive the
files. The other non encrypted folders are accessable. I
use the same username and password, and have admin
access, but it shows them as 0mb on the properties and as
not being encrypted, I dont know what to try next any
ideas?

Give up. If you did not backup your encryption certificates, your
previously encrypted files are history.

Now, if you only used the standard NTFS options of restricting access, See
Help and Support and search for "take ownership"

HOW TO: Take Ownership of a File or Folder in Windows XP
http://support.microsoft.com/?id=308421
--
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Associate Expert
ExpertZone - http://www.microsoft.com/windowsxp/expertzone
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.

"James McGee" <ace@bulloch.com> wrote in message
news:05a601c379a7$3f36ef50$a401280a@phx.gbl...

> I just "redone" my computer,
> Motherboard,mem,Hd, Big upgrade... kept my old hd as was
> and used as slave{because folders I wanted to keep). They
> were encrypted, now I cannot access them to retrive the
> files. The other non encrypted folders are accessable. I
> use the same username and password, and have admin
> access, but it shows them as 0mb on the properties and as
> not being encrypted, I dont know what to try next any
> ideas?

Wouldnt they still be on the old drive somewhere?

>-----Original Message-----
>Give up. If you did not backup your encryption

certificates, your

>previously encrypted files are history.
>
>Now, if you only used the standard NTFS options of

restricting access, See

>Help and Support and search for "take ownership"
>
>HOW TO: Take Ownership of a File or Folder in Windows XP
>http://support.microsoft.com/?id=308421
>--
>Doug Knox, MS-MVP Windows XP/ Windows Smart Display
>Win 95/98/Me/XP Tweaks and Fixes
>http://www.dougknox.com
>--------------------------------
>Associate Expert
>ExpertZone -

http://www.microsoft.com/windowsxp/expertzone

>--------------------------------
>Please reply only to the newsgroup so all may benefit.
>Unsolicited e-mail is not answered.
>
>"James McGee" <ace@bulloch.com> wrote in message
>news:05a601c379a7$3f36ef50$a401280a@phx.gbl...

was

They

I

as

>
>
>.
>

If when you indicated that you kept the old harddrive,
you mean that you have all of the old XP install there
as it was, then you do have options.
First, I would make a full backup of that other drive
so that anything you do can be undone.
Your options are
1. try to make the old XP install bootable - provided
that you do remember the encrypting account and its
password when last used. To do this you may be so
luck as to just boot and have plug and play take care of
hardware changes (but that would be quite lucky). Else,
an upgrade repair install can be used to get the needed
driver changes in place. In either situation you will
likely have to reactivate - although if it only warns and
lets you in that would be sufficient to get the files out
into the clear. If you do have to use the upgrade install,
then do not be connected to the network afterwards as
you will be back without service beyond the level of the
CD you have used (and will get worm-holed in no time).
Option 2 - as you have the complete profiles from the old
system you can call MS and open a paid support call to
get you EFS files back accessible.
Option 3 - try Peter's or other third-parties' methods,
some of which are free and some not. Sorry that I do not
have a link at hand on this machine for Peter's directions,
but a google search should give you a few alternatives.

--
Roger Abell
Microsoft MVP (Windows, Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"James McGee" <ace@bulloch.com> wrote in message
news:07fd01c379ac$fcc1a1f0$a101280a@phx.gbl...

> Wouldnt they still be on the old drive somewhere?
>
>
>

> certificates, your

> restricting access, See

> http://www.microsoft.com/windowsxp/expertzone

> was

> They

> I

> as

http://www.beginningtoseethelight.org/efsrecovery/

>-----Original Message-----
>If when you indicated that you kept the old harddrive,
>you mean that you have all of the old XP install there
>as it was, then you do have options.
>First, I would make a full backup of that other drive
>so that anything you do can be undone.
>Your options are
>1. try to make the old XP install bootable - provided
>that you do remember the encrypting account and its
>password when last used. To do this you may be so
>luck as to just boot and have plug and play take care of
>hardware changes (but that would be quite lucky). Else,
>an upgrade repair install can be used to get the needed
>driver changes in place. In either situation you will
>likely have to reactivate - although if it only warns and
>lets you in that would be sufficient to get the files out
>into the clear. If you do have to use the upgrade install,
>then do not be connected to the network afterwards as
>you will be back without service beyond the level of the
>CD you have used (and will get worm-holed in no time).
>Option 2 - as you have the complete profiles from the old
>system you can call MS and open a paid support call to
>get you EFS files back accessible.
>Option 3 - try Peter's or other third-parties' methods,
>some of which are free and some not. Sorry that I do not
>have a link at hand on this machine for Peter's directions,
>but a google search should give you a few alternatives.
>
>--
>Roger Abell
>Microsoft MVP (Windows, Security)
>MCSE (W2k3,W2k,Nt4) MCDBA
>"James McGee" <ace@bulloch.com> wrote in message
>news:07fd01c379ac$fcc1a1f0$a101280a@phx.gbl...

>
>
>.
>

"Peter Clark" <clark@hushmail.com> wrote in message
news:093001c379e7$50cbb6c0$a301280a@phx.gbl...

> http://www.beginningtoseethelight.org/efsrecovery/
>

Thanks Peter, So now I have the link on this machine too.

Roger