I have been having an issue since I installed VeraCrypt, with which I hope someone can give some advice. I searched through the archived topics, but cannot seem to see any that touch on this specific point; and those I did find blame the issue either on file names containing illegal characters or issues with the hard drive, neither of which would seem to apply here.
To review the situation: I created two VeraCrypt entities, one of which is a folder that I installed on my D: drive; in the second case, I encrypted an entire external hard drive. I am experiencing the same issue with both installations.
I can move .jpg files into both installations without issue. However, when I try to put those files in a preexisting folder (named "Image Files (JPG, PNG)" -- though I have also tried changing the name of that file to various other things), I get the error message: "Error 0x80070052: The directory or file cannot be created." Note that this occurs when I am moving files from my C: drive into the container, as well as when I try to move image files that already exist in the container into the folder where I want to keep them.
If I create a new folder (regardless of the name I give it), I can put those .jpg files into it; but when I try to move the other files from the "Image Files (JPG, PNG)" folder into the new one, all of the files move except for one. Always one (and only one) random file remains in the old folder; and when I try to move it, I get the "Error 0x80070052: The directory or file cannot be created" message. I found suggestions that changing the name would help, and one time this worked. However, since then, changing the names (even to something extremely simple like "1.jpg" or "a.jpg") has no effect. Since the purpose of the archive is, in part, to store and protect image files, this is very frustrating. Exactly the same thing happens with both installations (and I have noticed this because the external hard drive is a backup of the container installed on my D: drive).
It is not a case where any of the files contain illegal characters (indeed, as I said, many of the files were already being stored in the "Image Files (JPG, PNG)" folder); and it is also not a case where I have any reason to suspect that the drives are damaged (the external hard drive was brand new and had never been used for anything prior to the installation of VeraCrypt; and the D: drive is also only a month or so old, with a CrystalDiskInfo rating of good, which is the highest rating; and running programs like scandisk revealed no issues at all). These details seem to rule out every solution that I have read regarding the "Error 0x80070052" issue.
Does anyone have a suggestion that could allow me to completely resolve this issue, once and for all? At this point, none of the work-arounds work.
Thank you all very much for any suggestions that you can make. Please have a good day, all.
-- DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That sounds like filesystem issues, you should run chkdsk on your volume. You should also be able to launch it from VeraCrypt GUI by rightclicking the mounted volume and hitting "Check filesystem" or "Repair filesystem".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran that program (selecting the "check file system" option), but nothing. According to Scandisk, there were no errors present on either the external hard drive or the encrypted folder. Because it said that running the repair file system option could result in corruption of my files, I did not attempt that (though, as I said, the check option showed no errors).
Maybe I should add that this issue affects only image (.jpg, .png, etc.) files. No problems with other kinds of files (such as .gif, .txt, and assorted audio and video files). This is frustrating.
DMB
Last edit: Daniel M. Burkus 2024-04-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to provide more information before anyone could possibly help with this!
a. Don't understand 'created ... a folder that I installed on my D: drive'; do you mean a 'file container'? If so, what drive letter do you mount it to?
b. How do you move/copy files files? Drag and drop? Cut/copy and paste? Command line/batch file with move or copy commands> Or robocopy? Or some other copy software?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used VeraCrypt to create a file container on my D: drive. This file container is called Z:. I used VeraCrypt to completely encode an external hard drive; this device is called Y:.
The original batch of data was already stored on another (internal) hard drive, which I copied and pasted from that drive into both Z: and Y:. I attempted to drag and drop subsequent image files into folders that I named "Image Files (JPG, PNG)" in both locations (Z: and Y:); when that failed, I tried copy and paste. When that failed, I copied and pasted the files onto empty space in both locations.
I read somewhere that one solution would be to create a new file folder, which I did in both locations (Z: and Y:), and was able to move the new image files into those. I then tried to move all of the other image files into the same new folders, and they all could be moved except for one file that remained behind in the old "Image Files (JPG, PNG) folder." That file gave the same error message ("Error 0x80070052"). It was possible to move that file out of the old folder and onto empty space within the VeraCrypt folder. But not into the newly created file folder. If I created a second new file folder, I could move that file into that; and when I tried to move all of the other files into that folder as well, the same thing happened: one or two files remained behind, and could not be moved into the new folder ("Error 0x80070052" again). The same thing happened with the VeraCrypt encrypted external hard drive (though different file/s were left behind in that case).
After rebooting my PC, I tried all of this again, with the same results (though each time different files were left behind and could not be moved).
That describes what I did. As suggested by Jertzukka, I ran chkdsk, via the VeraCrypt GUI. There were no issues reported. Afterward, however, the same issues persisted: I cannot move new files into the "Image Files (JPG, PNG)" folders in either location; I can move them into empty space, and into newly created folders; and if I attempt to move all of the other image files into the newly created folder, I can do so except for several random files, which stay behind and give the "Error 0x80070052" message. Changing one file name worked on one occasion, but changing their names (even to something as simple as "a.jpg" or "1.png") did not work at any other time. This seems to exhaust the suggestions that I read elsewhere.
I can't imagine that there is anything else that I can tell you, but if so, please let me know. As I mentioned above, this issue occurs ONLY with image files. All other file types can be moved into both VeraCrypt file containers with no problems.
DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I do not believe I selected anything -- I went with the default (as the instructions seemed to recommend). Checking now, both are FAT32. Could this be the issue? (Sorry, I am not really well enough versed in computers to know, which is why I try to follow what the FAQ or installation instructions suggest.) If it is the issue, is there a way to change the file system type (to NTFS, for example) without damaging the files that are already resident in the VeraCrypt containers?
DMB
Last edit: Daniel M. Burkus 2024-04-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You say "I used VeraCrypt to create a file container on my D: drive. This file container is called Z:. I used VeraCrypt to completely encode an external hard drive; this device is called Y:."
Can you confirm that what you mean is, that the file container is 'mounted to Z', and the encrypted drive is 'mounted to Y'. (That is, they are allocated those drive letters in Windows when decrypted for use.)
If so, what is the actual name (file name) of the file container?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are correct, the VeraCrypt containers are mounted as/to Y: and Z: respectively.
The file container (on my D: drive) is named "A" ("VeraCrypt Container" seemed as if it would give the whole thing away). The fully encrypted external hard drive is just named "External Drive."
DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would recommend NTFS for Windows only usage since the filesystem is more robust and has more features than FAT32 and exFAT.
FAT32 has 4 GB file size limit and filename length is shorter than NTFS. There are other differences that you can Google search.
There are probably utilities to convert without destroying the existing data to go from FAT32 to NTFS filesystem. However, I have never looked for those utilities nor used those utilities. Therefore, I have no recommendations other than start over.
Again, Google search: Error 0x80070052
The results show corruption or file name issues.
Last edit: Enigma2Illusion 2024-04-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you, Enigma2Illusion. Yes, I read the Google results and, as detailed above, tried to take corrective action. When that failed, I turned to this forum for program-specific help.
Ok, since it seems there is no other way to do this, I will start by reformatting the external hard drive, reinstalling VeraCrypt with a NTFS file system, and then reinstalling all my files from the D: drive. Then I will do the same for the D; drive. It will all take several days.
Thank you very much for your comments. I guess this means this thread can be marked "solved." Please have a good weekend, everyone.
DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will start by reformatting the external hard drive, reinstalling VeraCrypt with a NTFS file system, and then reinstalling all my files from the D: drive. Then I will do the same for the D; drive. It will all take several days.
Just so I understand clearly, you mean that:
You are having to in Windows (not in VeraCrypt) reformat your external HDD back to using NTFS filesystem?
Then in VeraCrypt you will recreate the volumes selecting the NTFS filesystem?
.
You can use Windows quick format to initialize the drive/partition which is very fast.
Last edit: Enigma2Illusion 2024-04-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your reply, Enigma2Illusion. I deleted all of the files from the external hard drive, then did a quick reformat of the drive with Windows (yes, I knew how to do that -- hahaha). Now I am installing VeraCrypt (encrypting the whole drive). I found the place where I could change the file system (during the VeraCrypt installation process), which is almost hidden for some reason (the FAT file system was what VeraCrypt installed by default).
VeraCrypt seems to format the drive while it installs -- I did not select quick format here, because it seemed better for VeraCrypt to write over everything with white noise. VeraCrypt will install the NTFS file system when it gets to that point in the installation process.
I am an old man, so I am not well versed in computers, and probably use the wrong terms from time to time. Sorry!
Thank you for your help, Enigma2Illusion! I deeply appreciate your kindness!
DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is great you are eager to learn the technology. Age does not matter as we all started to learn various technologies as a novice.
Unfortunately, the tutorial documentation is based on TrueCrypt pre-NTFS and for the Windows platform should one-day be changed to show NTFS and default to NTFS in the volume creation wizard. That is a very low priority for the developer at this time based on his recent post.
Just to help you with future posts so other forum users can better assist you, "installing VeraCrypt" means installing the VeraCrypt software on your computer.
VeraCrypt does not begin to encrypt anything automatically.
What you are meaning to say is that you are encrypting Disk, Partition or creating a File Container.
You have to open the VeraCrypt application (aka GUI = Graphical User Interface) and in your case, click the Create Volume button to begin the process of creating an encrypted volume (Disk, Partition or File Container).
I hope your efforts will be successful by using the NTFS filesystem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you very much for your help, Enigma2Illusion! I deeply appreciated it! Yesterday I used VeraCrypt to encrypt my external hard drive, and then transferred all of the files back again. Then, when that was done, I moved everything else from the D: drive, reformatted it, and then created a VeraCrypt volume (file container); early in the morning that was ready, so I first moved all of the ordinary files back onto that drive, and am now in the process of copying my data from the external hard drive back into the VeraCrypt container on the D: drive. So, in 6 hours, the whole thing will be done! Then I can move on to other projects that do not involve VeraCrypt! Hahaha!
Thank you, again, for everything. Please have a good week!
-- DMB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been having an issue since I installed VeraCrypt, with which I hope someone can give some advice. I searched through the archived topics, but cannot seem to see any that touch on this specific point; and those I did find blame the issue either on file names containing illegal characters or issues with the hard drive, neither of which would seem to apply here.
To review the situation: I created two VeraCrypt entities, one of which is a folder that I installed on my D: drive; in the second case, I encrypted an entire external hard drive. I am experiencing the same issue with both installations.
I can move .jpg files into both installations without issue. However, when I try to put those files in a preexisting folder (named "Image Files (JPG, PNG)" -- though I have also tried changing the name of that file to various other things), I get the error message: "Error 0x80070052: The directory or file cannot be created." Note that this occurs when I am moving files from my C: drive into the container, as well as when I try to move image files that already exist in the container into the folder where I want to keep them.
If I create a new folder (regardless of the name I give it), I can put those .jpg files into it; but when I try to move the other files from the "Image Files (JPG, PNG)" folder into the new one, all of the files move except for one. Always one (and only one) random file remains in the old folder; and when I try to move it, I get the "Error 0x80070052: The directory or file cannot be created" message. I found suggestions that changing the name would help, and one time this worked. However, since then, changing the names (even to something extremely simple like "1.jpg" or "a.jpg") has no effect. Since the purpose of the archive is, in part, to store and protect image files, this is very frustrating. Exactly the same thing happens with both installations (and I have noticed this because the external hard drive is a backup of the container installed on my D: drive).
It is not a case where any of the files contain illegal characters (indeed, as I said, many of the files were already being stored in the "Image Files (JPG, PNG)" folder); and it is also not a case where I have any reason to suspect that the drives are damaged (the external hard drive was brand new and had never been used for anything prior to the installation of VeraCrypt; and the D: drive is also only a month or so old, with a CrystalDiskInfo rating of good, which is the highest rating; and running programs like scandisk revealed no issues at all). These details seem to rule out every solution that I have read regarding the "Error 0x80070052" issue.
Does anyone have a suggestion that could allow me to completely resolve this issue, once and for all? At this point, none of the work-arounds work.
Thank you all very much for any suggestions that you can make. Please have a good day, all.
-- DMB
That sounds like filesystem issues, you should run chkdsk on your volume. You should also be able to launch it from VeraCrypt GUI by rightclicking the mounted volume and hitting "Check filesystem" or "Repair filesystem".
I ran that program (selecting the "check file system" option), but nothing. According to Scandisk, there were no errors present on either the external hard drive or the encrypted folder. Because it said that running the repair file system option could result in corruption of my files, I did not attempt that (though, as I said, the check option showed no errors).
Maybe I should add that this issue affects only image (.jpg, .png, etc.) files. No problems with other kinds of files (such as .gif, .txt, and assorted audio and video files). This is frustrating.
DMB
Last edit: Daniel M. Burkus 2024-04-24
You need to provide more information before anyone could possibly help with this!
a. Don't understand 'created ... a folder that I installed on my D: drive'; do you mean a 'file container'? If so, what drive letter do you mount it to?
b. How do you move/copy files files? Drag and drop? Cut/copy and paste? Command line/batch file with move or copy commands> Or robocopy? Or some other copy software?
Adrian, thank you for taking the time to reply.
I used VeraCrypt to create a file container on my D: drive. This file container is called Z:. I used VeraCrypt to completely encode an external hard drive; this device is called Y:.
The original batch of data was already stored on another (internal) hard drive, which I copied and pasted from that drive into both Z: and Y:. I attempted to drag and drop subsequent image files into folders that I named "Image Files (JPG, PNG)" in both locations (Z: and Y:); when that failed, I tried copy and paste. When that failed, I copied and pasted the files onto empty space in both locations.
I read somewhere that one solution would be to create a new file folder, which I did in both locations (Z: and Y:), and was able to move the new image files into those. I then tried to move all of the other image files into the same new folders, and they all could be moved except for one file that remained behind in the old "Image Files (JPG, PNG) folder." That file gave the same error message ("Error 0x80070052"). It was possible to move that file out of the old folder and onto empty space within the VeraCrypt folder. But not into the newly created file folder. If I created a second new file folder, I could move that file into that; and when I tried to move all of the other files into that folder as well, the same thing happened: one or two files remained behind, and could not be moved into the new folder ("Error 0x80070052" again). The same thing happened with the VeraCrypt encrypted external hard drive (though different file/s were left behind in that case).
After rebooting my PC, I tried all of this again, with the same results (though each time different files were left behind and could not be moved).
That describes what I did. As suggested by Jertzukka, I ran chkdsk, via the VeraCrypt GUI. There were no issues reported. Afterward, however, the same issues persisted: I cannot move new files into the "Image Files (JPG, PNG)" folders in either location; I can move them into empty space, and into newly created folders; and if I attempt to move all of the other image files into the newly created folder, I can do so except for several random files, which stay behind and give the "Error 0x80070052" message. Changing one file name worked on one occasion, but changing their names (even to something as simple as "a.jpg" or "1.png") did not work at any other time. This seems to exhaust the suggestions that I read elsewhere.
I can't imagine that there is anything else that I can tell you, but if so, please let me know. As I mentioned above, this issue occurs ONLY with image files. All other file types can be moved into both VeraCrypt file containers with no problems.
DMB
Hi DMB,
In VeraCrypt during the creation of the file container and encryption of the other drive, did you select NTFS as the filesystem type?
Google search: Error 0x80070052
Hello, Enigma2Illusion. Thank you for your reply.
I do not believe I selected anything -- I went with the default (as the instructions seemed to recommend). Checking now, both are FAT32. Could this be the issue? (Sorry, I am not really well enough versed in computers to know, which is why I try to follow what the FAQ or installation instructions suggest.) If it is the issue, is there a way to change the file system type (to NTFS, for example) without damaging the files that are already resident in the VeraCrypt containers?
DMB
Last edit: Daniel M. Burkus 2024-04-26
You say "I used VeraCrypt to create a file container on my D: drive. This file container is called Z:. I used VeraCrypt to completely encode an external hard drive; this device is called Y:."
Can you confirm that what you mean is, that the file container is 'mounted to Z', and the encrypted drive is 'mounted to Y'. (That is, they are allocated those drive letters in Windows when decrypted for use.)
If so, what is the actual name (file name) of the file container?
Thank you, Adrian.
You are correct, the VeraCrypt containers are mounted as/to Y: and Z: respectively.
The file container (on my D: drive) is named "A" ("VeraCrypt Container" seemed as if it would give the whole thing away). The fully encrypted external hard drive is just named "External Drive."
DMB
Hi DBM,
I would recommend NTFS for Windows only usage since the filesystem is more robust and has more features than FAT32 and exFAT.
FAT32 has 4 GB file size limit and filename length is shorter than NTFS. There are other differences that you can Google search.
There are probably utilities to convert without destroying the existing data to go from FAT32 to NTFS filesystem. However, I have never looked for those utilities nor used those utilities. Therefore, I have no recommendations other than start over.
Again, Google search: Error 0x80070052
The results show corruption or file name issues.
Last edit: Enigma2Illusion 2024-04-26
Thank you, Enigma2Illusion. Yes, I read the Google results and, as detailed above, tried to take corrective action. When that failed, I turned to this forum for program-specific help.
Ok, since it seems there is no other way to do this, I will start by reformatting the external hard drive, reinstalling VeraCrypt with a NTFS file system, and then reinstalling all my files from the D: drive. Then I will do the same for the D; drive. It will all take several days.
Thank you very much for your comments. I guess this means this thread can be marked "solved." Please have a good weekend, everyone.
DMB
Just so I understand clearly, you mean that:
.
You can use Windows quick format to initialize the drive/partition which is very fast.
Last edit: Enigma2Illusion 2024-04-27
Thank you for your reply, Enigma2Illusion. I deleted all of the files from the external hard drive, then did a quick reformat of the drive with Windows (yes, I knew how to do that -- hahaha). Now I am installing VeraCrypt (encrypting the whole drive). I found the place where I could change the file system (during the VeraCrypt installation process), which is almost hidden for some reason (the FAT file system was what VeraCrypt installed by default).
VeraCrypt seems to format the drive while it installs -- I did not select quick format here, because it seemed better for VeraCrypt to write over everything with white noise. VeraCrypt will install the NTFS file system when it gets to that point in the installation process.
I am an old man, so I am not well versed in computers, and probably use the wrong terms from time to time. Sorry!
Thank you for your help, Enigma2Illusion! I deeply appreciate your kindness!
DMB
Hi DMB,
It is great you are eager to learn the technology. Age does not matter as we all started to learn various technologies as a novice.
Unfortunately, the tutorial documentation is based on TrueCrypt pre-NTFS and for the Windows platform should one-day be changed to show NTFS and default to NTFS in the volume creation wizard. That is a very low priority for the developer at this time based on his recent post.
Just to help you with future posts so other forum users can better assist you, "installing VeraCrypt" means installing the VeraCrypt software on your computer.
VeraCrypt does not begin to encrypt anything automatically.
What you are meaning to say is that you are encrypting Disk, Partition or creating a File Container.
You have to open the VeraCrypt application (aka GUI = Graphical User Interface) and in your case, click the Create Volume button to begin the process of creating an encrypted volume (Disk, Partition or File Container).
I hope your efforts will be successful by using the NTFS filesystem.
Thank you very much for your help, Enigma2Illusion! I deeply appreciated it! Yesterday I used VeraCrypt to encrypt my external hard drive, and then transferred all of the files back again. Then, when that was done, I moved everything else from the D: drive, reformatted it, and then created a VeraCrypt volume (file container); early in the morning that was ready, so I first moved all of the ordinary files back onto that drive, and am now in the process of copying my data from the external hard drive back into the VeraCrypt container on the D: drive. So, in 6 hours, the whole thing will be done! Then I can move on to other projects that do not involve VeraCrypt! Hahaha!
Thank you, again, for everything. Please have a good week!
-- DMB