I think the problem is going to be the drive letter assignment for the user profiles and that you need VeraCrypt to use the same drive letter which is in use by Windows Disk Management. If the user profiles are not available during Windows OS startup, you are
going to problems like this user had in the thread link below.
For example, if your user profiles are on the D drive and you perform the in-place encryption of the D drive, you need to remove D drive letter assignment from Windows Disk Management so you can assign D drive letter in VeraCrypt System Favorites for the device/partition
so Windows OS can find the profiles at boot-up. But you should not remove the D drive letter from the Windows OS while logged into Windows. It is a chicken or the egg problem.
The user above kept the D drive letter in Windows and mounted in System Favorites to a different drive letter. This worked, however you are using two drive letters to accomplish the goal.
One idea you could try at your own risk after you encrypt the drive using the in-place option is the following:
- Mount the encrypted drive to another available drive letter. For the sake of this example, use T.
- Add the mounted volume to VeraCrypt System Favorites as T drive letter.
- Using Notepad, manually edit the VeraCrypt System Favorite Volumes.xml file to use D (or whatever drive letter the user profiles are currently located) instead of T. The VeraCrypt System Favorite Volumes.xml is located in the folder %windir%\system32 for
32-bit systems or in the folder %windir%\SysWOW64 for 64-bit systems.
- Boot Windows into Safe Mode.
- Use Windows Disk Management to remove the D drive from the device/partition.
Hopefully, this will allow VeraCrypt to use the D drive letter assignment at the pre-boot startup.
Also be aware if for some reason in the future you are not able to mount the device/partition with the user profiles, you will not be able to use Windows.
Proceed at your own risk.