During AppStack provisioning, the VMDK disk is attached as a symbolic link within Windows as part of the existing C drive. Not sure if there is a way to change this behavior to D drive (unless manually doing it).
Recommended to install the application on C drive so that the capture is redirected to the AppStack correctly.