TrueCrypt 7.1a Does Not Worik With My New Win 7 Ultimate

It says in the TC guide that TC works with Win 7. Evidently, my new 8
core computer with Windows 7 Ultimate is too new for the old TC, which
works fine on my other computer running XP SP 3.

It blew my C: Windows. It booted into the DOS screen and said it
could not find an O.S. It asked for the password, but wouldn't accept
it. What saved my butt was the recover disk I had made when I got the
computer.

I have used TC full disk encryption a number of times through the
years, including on my standby XP machine. It ain't that hard to use.
The instructions are very easy to follow.

I don't know if VeraCrypt is truly as safe as True Crypt. The latter
has sent the powers that be into court a number of times in an effort
to force a computer owner to open an encrypted drive. So far as I
know, that has yet to be the case with drives encrypted with
VeraCrypt. That's why I still trust TrueCrypt. However, I now have
to trust VeraCrypt. It is open source, so hopefully enough high
powered techs have examined it. Since in the few years it's been
around, I haven't read of any of those encryption savants point out
any serious compromises in it.

My advice is that anyone with a newer updated Windows 7 to make dang
sure you have created a full save of your system and files, system
restore points, plus having made a recovery disk before you attempt
using TC. My machine would now be a doorstop had I not had all these.

Just thought I'd give out this warning of what happened to me.

none wrote:

It says in the TC guide that TC works with Win 7. Evidently, my new 8
core computer with Windows 7 Ultimate is too new for the old TC,
which works fine on my other computer running XP SP 3.

It blew my C: Windows. It booted into the DOS screen and said it
could not find an O.S. It asked for the password, but wouldn't
accept it. What saved my butt was the recover disk I had made when I
got the computer.

Truecrypt (TC) is not a multi-core program. It doesn't care. I am
running TC 7.1a on Windows 7 Home x64 SP-1 with no problems and that's
on a quad-core CPU.

You never mentioned *HOW* you are using TC. It has no problems
creating, opening, and allowing file reads & writes into TC containers
even on the latest hardware. What TC won't work with is when using it
for whole-disk encryption on newer *hardware*. It will work with
old-style BIOS that uses MBR on the active disk. It will /not/ work
with UEFI -- and that's probably what you changed in your new computer
config from your old MBR BIOS on WinXP.

You only mentioned operating systems as a differentiating factor between
where TC works and where it does not. You never mentioned how your
Windows XP and Windows 7 Ultimate hosts differ in their HARDWARE.

I have used TC full disk encryption a number of times through the
years, including on my standby XP machine. It ain't that hard to use.
The instructions are very easy to follow.

Yeah, you've used whole-disk encryption with TC on MBR BIOS *hardware*.

I don't know if VeraCrypt is truly as safe as True Crypt.

One of the updates to TC in Veracrypt's adaption was to support UEFI.

The latter has sent the powers that be into court a number of times in
an effort to force a computer owner to open an encrypted drive.

Since when has Veracrypt sued anyone to access the contents of encrypted
containers or encrypted disks? Please cite a case.

So far as I know, that has yet to be the case with drives encrypted
with VeraCrypt.

Yet to be the case ... for what? That a gov't agency could not invade
into a TC or VeraCrypt container or encrypted disk? It can be done but
requires lots of brute strength (which is available these days), the
will or desire to do so and permission to allocate those crunching
computers, and perhaps legal requirements, like a judge's order.

To thwart the brute force method, use multiple encryption schemes. TC
gives you a benchmark when creating an encrypted container showing you
how much impact each encryption algorithm will incur on reading and
writing files along with benchmarking when you select multiple schemes.

You could also use the dummy pseudo-partition within a TC container so
under duress, like someone holding your kids with a knife at their
throat and drawing blood and threatening to do worse, you could give the
password to the dummy section of the TC container (where you should put
some bait files) but keep the other section safe since it uses a
different password. Obviously if you're writing your passwords down in
a logbook, on Post-It notes, or elsewhere then those are discoverable.

That's why I still trust TrueCrypt.

I trust Truecrypt and will continue to use it. However, if I build a
new computer that uses UEFI BIOS then I'll have to move to Veracrypt.
Veracrypt started with TC's code, fixed some problems found in the 2
audits of its code, and added new features. Veracrypt is open source
(https://github.com/veracrypt/VeraCrypt) just as was TC so anyone with
the expertise could audit Veracrypt, too.

However, I now have
to trust VeraCrypt.

Well, you had to do that, too, when you first started using TC.

schreef in bericht
...
It says in the TC guide that TC works with Win 7. Evidently, my new 8
core computer with Windows 7 Ultimate is too new for the old TC, which
works fine on my other computer running XP SP 3.

It blew my C: Windows. It booted into the DOS screen and said it
could not find an O.S. It asked for the password, but wouldn't accept
it. What saved my butt was the recover disk I had made when I got the
computer.

I have used TC full disk encryption a number of times through the
years, including on my standby XP machine. It ain't that hard to use.
The instructions are very easy to follow.

I don't know if VeraCrypt is truly as safe as True Crypt. The latter
has sent the powers that be into court a number of times in an effort
to force a computer owner to open an encrypted drive. So far as I
know, that has yet to be the case with drives encrypted with
VeraCrypt. That's why I still trust TrueCrypt. However, I now have
to trust VeraCrypt. It is open source, so hopefully enough high
powered techs have examined it. Since in the few years it's been
around, I haven't read of any of those encryption savants point out
any serious compromises in it.

My advice is that anyone with a newer updated Windows 7 to make dang
sure you have created a full save of your system and files, system
restore points, plus having made a recovery disk before you attempt
using TC. My machine would now be a doorstop had I not had all these.

Just thought I'd give out this warning of what happened to me.





I use TC 7.1a on my dual core computers under Windows 7, without problems.




--


|\ /|
| \/ |@rk
\../
\/os

In message , VanguardLH
writes:
none wrote:
[]
I don't know if VeraCrypt is truly as safe as True Crypt.

One of the updates to TC in Veracrypt's adaption was to support UEFI.

The latter has sent the powers that be into court a number of times in
an effort to force a computer owner to open an encrypted drive.

Since when has Veracrypt sued anyone to access the contents of encrypted
containers or encrypted disks? Please cite a case.
[]
You've done what I did the first time, misread what he said - his "the
latter" referred to TC not VC.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"I'm not against women. Not often enough, anyway." - Groucho Marx

On Tue, 13 Feb 2018 01:23:18 -0600, none wrote:

It says in the TC guide that TC works with Win 7. Evidently, my new 8
core computer with Windows 7 Ultimate is too new for the old TC, which
works fine on my other computer running XP SP 3.

It blew my C: Windows. It booted into the DOS screen and said it could
not find an O.S. It asked for the password, but wouldn't accept it.
What saved my butt was the recover disk I had made when I got the
computer.

I have used TC full disk encryption a number of times through the years,
including on my standby XP machine. It ain't that hard to use.
The instructions are very easy to follow.

I don't know if VeraCrypt is truly as safe as True Crypt. The latter has
sent the powers that be into court a number of times in an effort to
force a computer owner to open an encrypted drive. So far as I know,
that has yet to be the case with drives encrypted with VeraCrypt.
That's why I still trust TrueCrypt. However, I now have to trust
VeraCrypt. It is open source, so hopefully enough high powered techs
have examined it. Since in the few years it's been around, I haven't
read of any of those encryption savants point out any serious
compromises in it.

My advice is that anyone with a newer updated Windows 7 to make dang
sure you have created a full save of your system and files, system
restore points, plus having made a recovery disk before you attempt
using TC. My machine would now be a doorstop had I not had all these.

Just thought I'd give out this warning of what happened to me.

First, for those of you claiming no problems with TrueCrypt, note the op
wants to encrypt the whole drive which may be more problematic than
creating volumes.
Second, either one is sufficiently secure for whatever it you are trying
to protect. If an agency has to go to court to gain access it means some
pretty savvy people couldn't access the data.
Being security conscience is prudent, paranoia is another matter. I
switched to VeraCrypt when I moved to Linux, it's a little slower to
decode the password and annoyingly slow if you type in the wrong
password, although this might discourage people's guessing attempts.
I only create one volume to hold just the stuff that needs protecting. I
create similar volumes on backup media for easy file backups.
Of course, everyone should make an image of their os and backup data
files, preferably confining those to a separate partition.

J. P. Gilliver (John) wrote:

In message , VanguardLH
writes:
none wrote:
[]
I don't know if VeraCrypt is truly as safe as True Crypt.

One of the updates to TC in Veracrypt's adaption was to support UEFI.

The latter has sent the powers that be into court a number of times in
an effort to force a computer owner to open an encrypted drive.

Since when has Veracrypt sued anyone to access the contents of encrypted
containers or encrypted disks? Please cite a case.
[]
You've done what I did the first time, misread what he said - his "the
latter" referred to TC not VC.

Very early on there was a suit from some parent company claiming one of
their employees (who was involved with TrueCrypt) of stealing that
company's encryption code. I don't recall what happened in that lawsuit
but TrueCrypt survived.

I have never heard of TrueCrypt or Veracrypt suing any user of their
product "to force a computer owner to open an encrypted drive". Maybe
he meant that gov't agencies attempting (during a court proceeding or
through coercion) to get a user to divulge the contents of a TrueCrypt
container or encrypted drive. I seem to recall 3 cases of persons
charged with espionage or spying that were ordered to divulge their TC
containers but refused and forensics teams didn't manage to invade the
TC containers. I don't know about all countries where some may have
prosecutors make such demands but aren't legally enforceable due to laws
against self-incrimination.

On Tue, 13 Feb 2018 21:36:05 -0600, wrote:
The "latter", meaning TrueCrypt, has "sent" - read: "caused" the
powers that be - the government/cops, whomever - to resort to a court
order to get the drive decrypted by the computer owner.


And your proof of that outlandish statement would be ... ?

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://BrownMath.com/
http://OakRoadSystems.com/
Shikata ga nai...