Menu

VC 1.25.9 Transferring not converting my drives?

Nick
2024-10-25
2024-11-21
  • Nick

    Nick - 2024-10-25

    I've been away a while. This regards the notice in quotes from a while back.
    "Starting from version 1.26.7, VeraCrypt discontinued support for the TrueCrypt format to prioritize the highest security standards. However, recognizing the transitionary needs of our users, we have preserved version 1.25.9"

    All my drives are running on version 1.24 update 7 under windows 7 and I also have a win10 machine. I'm ok with the idea of creating new volumes if that works better. I will buy new hard drives and create new volumes on them. My question is: What is the best way to MOVE my files from the old trueCrypt formatted drives to the new updated formatted drives? Do I have to install 1.25.9 in order for the old and new formats to see each other? (Much in the way we use exFAT to transfer windows files to macs) I guess what I'm asking is, should I install 1.25.9 to both create the new volumes on the new drives and also move the old volume files to the new drives with this version?
    I would rather just create new drives rather than converting things. But I need my data moved to the new format. I read a few posts here where data got corrupted from converting so I wanted to be clear if converting was the reason 1.26.7 was recommend, or if it does not matter if you're just moving your files from the old to the new volumes?

    Thank you

     

    Last edit: Nick 2024-10-25
  • Enigma2Illusion

    Enigma2Illusion - 2024-10-25

    Hi Nick,

    I not sure I understand your upgrade path for Win7 and Win10.

    Are you decommissioning the Win7 and plan only to use Win10?

    Are you wanting to use 1.26.x and newer versions?

    The 1.26.x version does not support Win7 and is not tested to work on Win7. Per the release notes for 1.26:

    VeraCrypt may still run on Windows 7 and Windows 8/8.1, but no active tests are done on these platforms.

    .
    At some point in the future, newer VeraCrypt versions will no longer install on older Windows OSes other than Win10/11.

    There is no corruption issue upgrading the VeraCrypt versions. The nearly two year old post you refer to is likely a problem with the build image not updated with the correct drivers and other Windows software for the new hardware.

     
  • Nick

    Nick - 2024-10-31

    Hello Enigma2Illusion. Thank you.

    I would like to keep my old drives from 1.24 update 7 as long as these older win7 computers are still working. The concern is, I will eventually build a new computer and be forced to upgrade to windows 11 at that point. The concern is: I don't want a situation where I can't transfer a copy of my data off the older formatted drives to the newer drives.

    As far as Win7/10, I just wanted to mention that I have a Win10 machine, but I don't use it with VC, it's a gaming computer. I think by the time I build a new system, I'll probably have to go with Win11

    I'm just wondering, is the preserved version 1.25.9 something I'm going to have to install on the new computer when it's time to copy my files from the old drives to the new drives? In that case maybe use the portable version of 1.25.9 to transfer if a later version is already installed by then?

     

    Last edit: Nick 2024-10-31
  • Enigma2Illusion

    Enigma2Illusion - 2024-10-31

    Hi Nick,

    Are you using VeraCrypt for system encryption and "data" partition drives located on the system drive?

    Are you using VeraCrypt on external drives?

    Are you using file containers?

    For the file containers and external drives, you do not have to recreate them to use the newer versions either 1.25.9 nor 1.26.x versions.

    Version 1.25.9 is fully compatible with Win7.

    Version 1.26.x for Win10/11 and may work on Win7.

    See the link below to change either your hash and/or TrueCypt Mode. Both are a simple and quick procedures.

    https://www.veracrypt.fr/en/Conversion_Guide_VeraCrypt_1.26_and_Later.html

    When you build your new PC on Win11, install 1.26.x or latest VeraCrypt version available at the time.

    For Windows, I would use NTFS unless you need to use external drives on both Windows and Mac or Linux.

    The only issue you will likely encounter on the Win11 PC is the Windows ownership and/or permission issues due to the user ID number (SID) is different than the old users ID numbers were on the previous Windows OS was using for your user name.

    You can search the internet to get procedures of how to take ownership grant permissions and ownership should you encounter access issues.

    For file containers, make sure to take ownership of the file container when dismounted and when mounted to take ownership of the directories and files.

     
    👍
    1
  • Nick

    Nick - 2024-11-02

    Hello Enigma2Illusion. That helps clarify it. Thanks.
    Yes, the only encrypted system I use is on Win7 machine. But all my encrypted data is on external drives and in containers. I don't don't store anything on my main OS drive.
    Yes I always use NTFS.

    By the way, All my drives are HMAC-SHA-512 (Dynamic). The page at that link you posted mentions to convert the 160 Hash Algorithm. Does that also apply to SHA-512 drives and vols?
    Should I convert the hash on all my older drives from SHA-512?

    Those security permissions sounds like they can be a nightmare. So If I'm understanding correct, I can't just Copy (Not Move) but copy the files from the old drives to the new drives under windows 11? How are people who are not even using VeraCrypt getting their older files into windows 11 if the (SID) is different? I would think that would be an issue even if your drives are not encrypted.

    By the way, I've been away from the VC forms for a few years. I'm really glad to see you still around Enigma2Illusion.

     

    Last edit: Nick 2024-11-02
  • Enigma2Illusion

    Enigma2Illusion - 2024-11-02

    Hi Nick and welcome back to the VeraCrypt forums!

    The hash algorithm HMAC-SHA-512 that you are using is compatible with the 1.26.x version.

    If you are currently mounting your VeraCrypt volumes without having to enable the TrueCrypt Mode checkbox and/or your file containers do not use the .tc file extension, then you do not need to perform any remediation from the link I provided.

    There are too many variables if you will be able to connect your old external drives to the new Win11 PC and you will be able to copy all the files to the new encrypted external drives created using the Win11 PC.

    If you encounter access issues to the old drives from the Win11 PC, then you can search the internet to get procedures of how to take Windows ownership and grant permissions on the old drives using the Win11 PC.

     
  • Nick

    Nick - 2024-11-08

    wow, I have a LOT of drives. I asked an AI bot about this. It said,
    "The SID is unique to each user account, and if the SID changes, it can cause problems with accessing encrypted files and volumes.
    To resolve these issues, you might need to re-encrypt the drive after upgrading to Windows 11

    Your right, there are many variables. The part I made in bold is scary. It makes it sound like every time I install a new account (Even on the same system) these drives are going to give me issues. Or if I build a new computer? I usually make local accounts only. But with this Microsoft login becoming more required with each new OS version, how is all this going to work with VC? It's sounding like we better keep the same Microsoft account. I don't even have an MS acc online. I only have a local account.

    Is there anything I can do now, or today that will circumvent this permissions issue down the road? Like I can order a few new drives tomorrow for example. Or is this issue just an unfortunate circumstance of moving to Win11 for anyone who has VeraCrypt volumes on win10 (even created on the new versions of VC?)

     

    Last edit: Nick 2024-11-08
  • Enigma2Illusion

    Enigma2Illusion - 2024-11-11

    AI answer you posted:

    To resolve these issues, you might need to re-encrypt the drive after upgrading to Windows 11

    Incorrect. I have already told you to search for the procedures of how to take Windows ownership and grant permissions on the old drives using the Win11 PC.

    https://www.howtogeek.com/301768/how-to-take-ownership-of-files-and-folders-in-windows/

    BTW: I Google search and Microsoft introduced Security Identifier (SID) in Windows NT that was released in 1993.

    Version of VeraCrypt has nothing to do with Windows Security Identifiers. This is a Windows issue and not a VeraCrypt issue.

    Even without encryption, you would encounter access errors if the SIDs are different when you connect the Win7/10 external drives to the Win11 PC.

     

    Last edit: Enigma2Illusion 2024-11-13
  • Nick

    Nick - 2024-11-21

    I'm aware that it's not a VC issue. My bigger concern is taking ownership on 4TB drives and I have more than a few because I make so many clones. How long will it take after you apply this setting to millions of folders, and if there is a power interruption will some of the permissions get corrupted -That's my only concern.
    Anyway, Thanks for the link.

     

    Last edit: Nick 2024-11-21

Log in to post a comment.

MongoDB Logo MongoDB