This project has moved and is read-only. For the latest updates, please go here.


(VC 1.15) Error 0x8007000F when deleting folders


Hi folks,

today i switched from tc 7.1a to vc. i created new containers and copied all the old stuff into them. now when i try to delete folders i got the error 0x8007000F. Deleting files works normally...

I'm using VC 1.15 on Windows 7 Pro.
Filesystem NTFS
Enryption: AES
Hash: SHA512

Cheers jay

file attachments

Closed Nov 2, 2015 at 8:41 PM by idrassi
Fixed in version 1.16. Registry instructions are provided below by Enigma2Illusion for those who need to manually clean the registry.


Sneazel wrote Sep 30, 2015 at 10:09 AM

Same issue here

But u can use Shift + Delete to remove it and dont move to Recycle Bin ;)

I would suggest ya to use shift + delete for files too.

jayes wrote Sep 30, 2015 at 10:47 AM

I also noticed problems with the recycle bin, too. I cannot delete files from it.....

Enigma2Illusion wrote Sep 30, 2015 at 1:24 PM

Hello Jay,

This is an issue with 1.15 version. Can you update the title to include 1.15 at the beginning of the title to make it easier on Mounir to see issues directly related to 1.15 version?

Kind Regards.

Fenderluvr wrote Oct 1, 2015 at 6:00 PM

Confirmed bug behavior with Windows 7/SP1 (64bit).

Undeletable wrote Oct 1, 2015 at 10:34 PM

I would like to confirm that I am also experiencing this same issue, as well as the inability to empty the Recycling Bin if the files therein originated from the encrypted drive. I believe these issues are related.

Win 7 64x, version 1.15 of VeraCrypt, encrypted drive is non-system and not hidden.

Undeletable wrote Oct 5, 2015 at 12:37 PM

Hi Enigma2Illusion,

1.16 did not solve this issue for me, mainly because I am having difficulty with the instruction to "remove any entries containing "Veracrypt" from the MountedDevices registry hive". I have nearly 50 entries in my registry at that location and I can't tell which ones are TC/VC related and which ones are not. How do I know which ones to delete?

Enigma2Illusion wrote Oct 5, 2015 at 2:51 PM


I use the utility DriveCleanup to remove all currently non present USB Storage Devices, Disks, CDROMs, Floppies, Storage Volumes and WPD devices from the device tree. Furthermore it removes orphaned registry items related to these device types.

I request you use version 0.9.0 and not the latest version due the latest version does not wipe existing devices from the registry.

Create a directory and unzip the files into the directory.
Start a command line prompt.
Change into the directory where unzipped the files. If you are using 64-bit Windows OS, change into x64 subdirectory.
Dismount all volumes.

To see what the utility will remove from the registry:

drivecleanup -T

To remove items the registry:


Reboot PC after running utility.

Any USB that was not currently connected to your PC will be install again by Windows and you may have to manually reassign the drive letters in Windows Disk Management if you had certain drive letters for an external hard drive or thumbdrives.

I have performed this numerous times on my system to remove all registry entries including valid devices due to tests with file containers.

If anyone knows of a better free utility, please post it.

Kind Regards.

idrassi wrote Oct 5, 2015 at 3:18 PM

@Undeletable: I can't reproduce the error 0x8007000 with 1.16-BETA. With this version, the removal of folders and files works normally.
What software are you using to delete folders? Any screenshot or video?

Undeletable wrote Oct 5, 2015 at 11:33 PM

Hello idrassi,

Thank you for your help. Here is a quick video demonstrating the error on my machine:

This is occurring after using Enigma2Illusion's drive cleanup tool.

Any thoughts as to what might be occurring or any questions regarding my setup? Did I not remove the drives successfully?


Enigma2Illusion wrote Oct 5, 2015 at 11:55 PM

Hello Undeletable,

Can you make the video public so other forum members can view the video and possibly see the issue?

Kind Regards.

idrassi wrote Oct 6, 2015 at 12:04 AM

@Undeletable: I don't have access to the video neither.

Undeletable wrote Oct 6, 2015 at 1:35 AM

My apologies, I listed it as "Private" rather than "Unlisted". It should be viewable now.

Enigma2Illusion wrote Oct 6, 2015 at 2:03 AM

Hello Undeletable,

I see the problem. DosDevice/G is your Z drive which can be temporarily created when performing the create volume wizard as VeraCrypt briefly mounts the new volume to create the filesystem.

Let's try the following.
  1. Dismount all VeraCrypt volumes.
  2. Run the DriveCleanup tool.
  3. Reboot PC.
  4. Use the following instructions below from Idrassi that I modified and reboot PC if you had to manually delete anything during this step.
  5. After your PC boots-up, try your delete folder again on a mounted VeraCrypt volume and report back your results.
Using a modified version of Idrassi's instructions:
Check the registry key "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices" using regedit. Scroll down and you'll find entries starting with "\DosDevices\" which indicate the drive letters that are taken by the system. Before mounting any volume, remove the ones that are unused.
Also, there are other entries whose name start with "#{" and "\??\Volume{": double click on each one of them and remove the ones whose data value contains the name "VeraCrypt" or "TrueCrypt".
Thank you.

Enigma2Illusion wrote Oct 6, 2015 at 2:11 AM

PS: If your OS is 64-bit, make sure you run the DriveCleanup.exe located in the x64 directory.

Undeletable wrote Oct 6, 2015 at 6:25 AM

Enigma my good man or woman, you've done it! After running the tool and rebooting, I looked in that reg entry, and one of the previous VeraCrypt entries was still there (G:). After manually deleting it, rebooting, and mounting, it is now deleting as it should be. Recycling bin also working fine.

Thanks for your assistance!

Enigma2Illusion wrote Oct 6, 2015 at 6:30 AM

Excellent! I am glad the issue is resolved.

BTW: I am a man. :-)

Morthawt wrote Oct 6, 2015 at 9:59 PM

Apparently this issue will be covered live on Security Now in a few minutes:

Here are the show notes:

I hope this gets resolved. So far I do not think I have experienced this issue yet, but I have high trust and faith in the developer, so I feel pretty good about this being quickly resolved.