This project has moved. For the latest updates, please go here.

Win10 explorer crash when copy from Vc volume to VC volume

Topics: Technical Issues
Aug 18, 2016 at 3:58 PM
Edited Aug 18, 2016 at 4:18 PM

I suspect a strange problem on Vecracrypt 1.7 and 1.8.
I have a VC volume created with standard settings, as removable medium, from a .vc file on my hard disk

Location: D:...
Size 85899083776 bytes
Type Normal
Read-Only No
Hidden No
Enc Algo AES
Prim K size 256b
sec k size 256 b
block size 128b
mode of op XTS
PKCS5 PRF: Hmac-Sha512
vol fformat version 2
embeded backup header yes

preserve modification timestam of file container
cache pw in memory
temporary cache password during mount as favorite
accelerate AES ((I tested with NO and it crashes the same)
use all processors
NO enable extended disk control code support

when I copy a file (a PDF, and ODT) from the volume to another directory, with the explorer, the explorer crash after few seconds of hanging.

if I copy to HD then to VC back, it works

in the event manager I get an even entry (error) :
(I translate from french locale)

name of falty app Explorer.EXE, version : 10.0.14393.0, timestamp: 0x57899981
name of faulty module : support.dll_unloaded, version :, timestamp: 0x572a0944
exception code: 0xc0000005
error offset : 0x00000000000053c0
faulty process id : 0x141c
faulty app stat time : 0x01d1f964e7ca7a80
path to falty app: C:\WINDOWS\Explorer.EXE
path to falty module: support.dll
report id : cc08d160-7d2e-471d-898e-8f1210269463
full name of faulty module :
app id relative to faulty package (???) - "ID de l’application relative au package défaillant" :

my system is
Win 10 family x64 (latest service pack, probably aniversary) version 1607 os version 14393.51
AsusTek X751LX - intel core i5-5200U 2.20GHz

It may be a local problem with my (recently purchased Win10-native) laptop, but if someone can replicate it is in interesting bug to solve.

Best regards.


I'm sorry but the even give me the idea of a search on the error code, and this fall to a problem with PDF Architect of PDF Forge .
What is strange is that the problem happens only on a VC volume from a VC volume.

the solution was to call the un-installer,(which also does modify) of PDF Architect and uncheck the shell integration in "create" module.

My problem is solved, but maybe you could see why VC triggers such a dysfunction with the cooperation of PDF architect.