I suggest to use always Imdisk because I found a couple of limitations /
problems with AIM:
1. Creating a large volume (several GB) it takes a lot of minutes before
asking to format the new drive. Creating the volume with -imdk allows the new
drive immediately available for formatting.
2. Having a ProxyCrypt volume mounted on a specific letter, if a second volume
is mounted then a random letter is used (instead the one specified as
mount point). Example: volume 1 mounted as L: as specified, volume 2 mounted
as D: also if P: was specified as mount point. This problem does not occur
using Imdisk (-imdk option).
3. Some times PC hangs on creating volumes (or mounting unformatted volumes).
This does not happen with -imdk.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Starting from Windows 11 24H2, you can no longer start an executable that requires administrative privileges from an ImDisk volume.
If this is fine for you, then you can continue to use ImDisk...
An alternative is to install a fork called "ImDisk 3.0", which may not fix all the compatibility issues.
The work with AIM is not totally finished. But I don't know what I will able to do.
Anyway, thanks for using this extremely unpopular software, which is yet much better than VeraCrypt, at least in my point of view. :p
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I suggest to use always Imdisk because I found a couple of limitations /
problems with AIM:
1. Creating a large volume (several GB) it takes a lot of minutes before
asking to format the new drive. Creating the volume with -imdk allows the new
drive immediately available for formatting.
2. Having a ProxyCrypt volume mounted on a specific letter, if a second volume
is mounted then a random letter is used (instead the one specified as
mount point). Example: volume 1 mounted as L: as specified, volume 2 mounted
as D: also if P: was specified as mount point. This problem does not occur
using Imdisk (-imdk option).
3. Some times PC hangs on creating volumes (or mounting unformatted volumes).
This does not happen with -imdk.
Starting from Windows 11 24H2, you can no longer start an executable that requires administrative privileges from an ImDisk volume.
If this is fine for you, then you can continue to use ImDisk...
An alternative is to install a fork called "ImDisk 3.0", which may not fix all the compatibility issues.
The work with AIM is not totally finished. But I don't know what I will able to do.
Anyway, thanks for using this extremely unpopular software, which is yet much better than VeraCrypt, at least in my point of view. :p