Moved shared folder, now can't remount when booted by VMSvc

[oucil]

VB: 6.0.8 r130520
VBVMSvc: 6.0-Pumpkin
Host: Windows 10
Guest: CentOS 7

I had an existing VM with multiple shared folders mounted from the host and everything was working great. I wanted to move the location of one of the host folders which was shared to the VM. I made the move, and updated the shared folder location in the VB console. The location in the guest did not change.

When booting the guest from the VB console, everything worked as expected, I can access and manipulate files. However when the Guest is booted by VBoxVmService, it fails to mount the shared folder from the host. The permissions are limited to the root user and the mount point is "busy" when trying to access it.

I figured maybe the UUID was re-used and maybe for some reason this would not work, and so I updated the fstab entry to point to a new mount location, shut down the machine, created a new host folder and moved all my files to it, removed the old VB shared folder entry, saved the settings, then created a new shared folder entry, with a new name matching the new fstab entry, and tried again. Again, when booted from the VB console, it worked as expected, and again when booted via the SVC, it had the same failure. Not only did it fail though, but it created the OLD mount point folder automatically, even though it no longer existed in the Hosts VB settings.

I've tried looking through the logs in both c:/vms/ as well as the VB logs in my user dir and nothing looks out of the ordinary. There are no snapshots, so the SVC shouldn't be seeing anything other than the latest VM image. I can't see any files that would have any effect in either location either.

I'm at a total loss, please help!

[oucil]

I should add, I've also tried uninstalling and reinstalling VBoxVMService fully, had no effect.

[oucil]

Here is my .ini

[Settings]
VBOX_USER_HOME=C:\Users\Kevin\.VirtualBox
RunWebService=no
PauseShutdown=10000

[Vm0]
VmName=name.of.my.guest.vm
ShutdownMethod=acpipowerbutton
AutoStart=yes

... and here is my log file ...

09/16/2019, 14:23:25 - C:\vms\VBoxVmService64.exe
09/16/2019, 14:23:25 - C:\vms\VBoxVmService.ini
09/16/2019, 14:23:25 - C:\vms\VBoxVmService.log
09/16/2019, 14:23:25 - VBoxVmService started.
09/16/2019, 14:23:25 - List all the VMs found by VBoxVmService
09/16/2019, 14:23:25 - VM0: name.of.my.guest.vm is powered off.
09/16/2019, 14:23:28 - VM name.of.my.guest.vm has been started up.
09/16/2019, 14:23:33 - Received control command: list
09/16/2019, 14:23:33 - List all the VMs found by VBoxVmService
09/16/2019, 14:23:33 - VM0: name.of.my.guest.vm is running.
09/16/2019, 14:24:50 - Received control command: list
09/16/2019, 14:24:50 - List all the VMs found by VBoxVmService
09/16/2019, 14:24:50 - VM0: name.of.my.guest.vm is running.
09/16/2019, 14:24:52 - Received control command: stop 0
09/16/2019, 14:24:52 - VM name.of.my.guest.vm has being shutted down.
09/16/2019, 14:57:50 - Received control command: list
09/16/2019, 14:57:50 - List all the VMs found by VBoxVmService
09/16/2019, 14:57:50 - VM0: name.of.my.guest.vm is powered off.
09/16/2019, 14:57:58 - Received control command: start 0
09/16/2019, 14:58:01 - VM name.of.my.guest.vm has been started up.
09/16/2019, 15:18:46 - Received control command: list
09/16/2019, 15:18:46 - List all the VMs found by VBoxVmService
09/16/2019, 15:18:46 - VM0: name.of.my.guest.vm is running.

As you can see, nothing sticking out, just lots of tries to reboot back and forth with the VB console.

[oucil]

I've made some progress, I've found that the .vbox file for the VM contains the old path / name info for the shared folder still, even though the console reflects the saved changes. I can see another file with a .vbox-prev extension, which contains the new path / name info, but also the warning not to edit that file as the changes will be overwritten. I can't find a way to force VBox to push the changes out, and my changes are indeed overwritten. Any ideas? Going to post over in the VBox forums as well.