9.21A: Drive not available when crypto-drive mounted during copy

[Dennis_Stevens]

Steps to reproduce:

1.) Start a copy (in my case 4GB) from harddrive to network-drive (in my case f (HDD) to Y (NWD) )
2.) Send copy-dialogue to background
3.) Mount a Crypto-Drive (Vera-Crypt; in my case assigned drive-letter is J )

The new Drive is not visible in TC (drive letter does not appear in button-bar) although Drive is mounted to the system. By entering "cd J:" to command-line the drive is accessible and drive letter is being added to button-bar.

Bug or feature?

64bit-System entirely, Windows 10 Pro Version 1803 Build 17134.228

[ghisler(Author)]

Unfortuantely I could not reproduce the problem. Here is what I tried:
1. Connect to network share
2. Copy folder with 2GB of files inside to the network share
3. Click on "Background"
4. Double click on Veracrypt container
5. Choose a drive letter
6. Click on Mount
7. Enter password
8. Return to TC
-> copying is still active, but the crypted drive has appeared just fine.

What am I doing wrong?

[Dennis_Stevens]

OK, then try this...
First of all create a user-command (e.g. em_mount_j) that starts VeraCrypt with command-line parameters to:
* load the specific crypto-file and
* mount it to J.

Then go on here, but at no. 3 use the user-command:
1.) Start a copy (in my case 4GB) from harddrive to network-drive (in my case f (HDD) to Y (NWD) )
2.) Send copy-dialogue to background
3.) Mount a Crypto-Drive from command-line with user-command em_mount_j.

[ghisler(Author)]

It would be helpful if you could tell me the exact parameters you use when calling VeraCrypt.

[Dennis_Stevens]

It would be helpful if you could tell me the exact parameters you use when calling VeraCrypt.

No Problem:

Code: Select all

[em_Mount_J]
cmd=PATH_TO_VERA_CRYPT\VeraCrypt.exe /v PATH_TO_THE_CRYPTO_FILE /l J /q /tc