This topic contains 5 replies, has 2 voices, and was last updated by Rob 1 year, 1 month ago.
March 23, 2017 at 22:26 #5815
I’ve encrypted a stored .vhdx file which is 90gb (its not used, just stored). AxCrypt split this into three 35Gb files (.vhdx, .vhdx1 .vhdx2). Does it recompile into one file when its decrypted?
thanksMarch 23, 2017 at 22:56 #5816
I guess AxCrypt would reconstruct although if you’re using VHDX files would I be correct in assuming you’re using a professional version of Windows? If this is the case then the best and easiest option would be to use BitLocker to encrypt the VHDX as BitLocker is native to the Operating System. Every time you go to mount the VHDX you’ll be prompted for your BitLocker password.
VHDXs are essentially system files and I’d be very wary about using third-party encryption to protect these. AxCrypt is designed primarily for individual files – not system critical files. The mount point that Windows use may cause AxCrypt to malfunction causing loss of your data.
Simple instructions for activating BitLocker on VHDX (scroll down the page).March 23, 2017 at 23:04 #5817
thanks Andrew. This vhdx is not used, just stored in case so not keen on using Bitlocker etc. The fact AxCrypt has split is this a feature of processing large files? Would it also split other files if they are similar size? just trying to be aware of limitations etc…March 23, 2017 at 23:10 #5818
That’s something I think Svante would have to answer. Most people on here, like myself, are users of the software.
I’ve had a cursory look through the official specification and there’s no mention of the maximum file size.
If you’re feeling adventurous you could look through the source code (it’s open source) for the answer or you could drop support a message; or somebody from the official support team might respond in due course.March 24, 2017 at 08:46 #5825
AxCrypt does *not* split files. There is no limit except available storage concerning file size.
AxCrypt will use a digit suffix (but not quite like you’re showing) in certain situations when there’s a file name collision but that does not seem to be the case here.
If you have a file named “MyVirtualDisk.vhdx”, and you encrypt it, you will get a file named “MyVirtualDisk-vhdx.axx”.
Are you sure you’re using AxCrypt ;-) ?March 24, 2017 at 10:43 #5826
Thanks Svante, I’ll delete this and retry the process to check it does it ok…. i’ll update you!