Why Ventoy enabled LinuxMint.vdi file not booting in VirtualBox?

[rJD#v6]

I am facing an issue while trying to run a LinuxMint.vdi file on Virtual Box on a Windows 10 host machine. I get the following error message:

(1) "cryptsetup: waiting for encrypted source device /dev/mapper/ventoy3...
https://i.imgur.com/U2YU5WM.jpeg

(2) "Volume group "vgmint" not found"
https://i.imgur.com/vOXpMP7.jpeg

Having said that Earlier, it was working fine and I was able to run it both in the real system (using a Ventoy-enabled USB drive) as well as in VirtualBox. However, after trying the USB drive on a secure boot enabled laptop (by following this) I am now only able to run the LinuxMint.vdi in the real system using a Ventoy-enabled USB drive NOT in VirtualBox.

Is there a solution to this problem, or any other way I can run the .vdi file in VirtualBox on my Windows 10 host machine? I was just hoping that since it can run on a real machine, I could run a script or something in Linux Mint terminal which would make the .vhd file work again in VirtualBox?

FAQ:

Q1. If it wokring on a real system then why I need to run this into VirtualBox?
Ventoy may require running the LinuxMint.vdi in VirtualBox in cases where there are updates to the Linux Mint kernel. These updates can cause Ventoy to stop functioning on a real system, and a special Script must be run within Linux Mint to restore its compatibility with the Ventoy-enabled USB drive.

Q2. Software Version?
Running Lattest VirtualBox Version 7.0.6 r155176 (Qt5.15.2) on Windows 10 and latest version of Ventoy.

Q3. Have you tried reaching out to the Linux Community or VirtualBox Community for help?
I asked the same question in both the Linux Community and VirtualBox Community, but have not received any help so far. They directed me to the Ventoy community, as it is related to Ventoy.

Q4. Its may be related to LUKS encryption?
Actually, I chose LUKS encryption while installing Linux Mint, and it worked flawlessly both on the real system (using a Ventoy-enabled USB drive) and in virtualbox. 

Q5. Have you copy the LinuxMint.vdi in local disc before trying to open the Ventoy enabled LinuxMint.vdi file in VirtualBox?
Yes, I tried it both ways: directly on a Ventoy-enabled USB drive (by renaming it back to.vid) and by copying it to a local disc before running it through VirtualBox. Both time same error.

[rJD#v6]

Hi everyone, I hope you are having a great day. I just wanted to bump this post in case anyone missed it. I would really appreciate it if you could take a look and share your input. Thank you for your time and attention.

[rJD#v6]

Just a bump

[rJD#v6]

@longpanda I'm not sure why my question was ignored; are there any traditions here that prevent a new user from getting any response?

[Steve2926]

Slightly confused?

So you have a .vdi file on a local disk and you are booting directly from it using VBOX with the vdi file attached as a local SATA drive?

i.e. you are not booting to Ventoy?

But if you boot the same file as .vdi.vtoy via ventoy on a real system, it boots fine?

Have you tested both UEFI64 and BIOS modes?

Have you tried setting up a new VM in VBOX?

[rJD#v6]

Slightly confused?

So you have a .vdi file on a local disk and you are booting directly from it using VBOX with the vdi file attached as a local SATA drive?

i.e. you are not booting to Ventoy?

But if you boot the same file as .vdi.vtoy via ventoy on a real system, it boots fine?

Have you tested both UEFI64 and BIOS modes?

Have you tried setting up a new VM in VBOX?

No, I was using a vetoy enabled USB 3.0 Pen Drive, and it is working fine both UEFI mode on a real system. Yes i tried to setup the on diffrent VM in VBOX.