vagrant provision etc commands given from F:/Laravel/Homestead in old PC -- now exist but as D:/

[lse123]

consider this real scenario

My PC
C:/ SSD System disk
F:/ Data Disk

when reinstalled Windows 10 2004 due to problems with updates
C:/ SSD System disk
D:/ Data Disk // same as F:/ untouched

Before Reinstall I created VM from PC with StarWind V2V Converter but only C:/ disk 0 did as VM

I have been running Vagrant In the old PC -- but Now in Reinstalled PC I run a new version of Vagrant
I wanted to recover my vagrant/Homestead/Laravel ONLY Databases from VM now because only there exist, for Laravel etc Frameworks --- since installed in VM PHPMyAdmin...
The problem is vagrant up, vagrant provision etc commands given from F:/Laravel/Homestead in old PC -- now exist but as D:/ -- but Not exist in VM since only c:/ drive Converted as VM guest - also files of PHP apps all in F:/ were --- VM guest run in the host WITH Vmware workstation pro hypervisor ... but vagrant is in it but point VM DATA FILES & HOMESTEAD install in F:/ --- I guest if modify sthg can recover databases ????

[scottgus1]

Both aspects of this question are unfortunately outside the scope of the Virtualbox forum.

Vagrant is not supported here, as they are a 3rd-party provider that just happens to use Virtualbox, and they have their own help forums.

Changing a Windows drive letter is supported by Microsoft and can be web-searched easily.

I would try to change D:\ to F:\ and re-import the data from the old PC.

[lse123]

you say
"and re-import the data from the old PC."

having a vmdk or vdi Virtual Box file, how create VM by opening it, eg from Vagrant VMDK or VDI file?

Like in VMware workstation I open the vmx file, by clicking in this file...