7.1 needs to be run as an admin account?

[Man-Grove]

In the latest version, the VM wouldn't start, and the log showed this:

02/13/2025, 17:33:55 - VBoxVmService started.
02/13/2025, 17:33:56 - List all the VMs found by VBoxVmService
02/13/2025, 17:33:56 - Error finding machine! Could not find a registered machine named 'Debian'

Changing the user running the service to Administrator worked fine, however:

02/13/2025, 17:35:01 - VBoxVmService started.
02/13/2025, 17:35:01 - List all the VMs found by VBoxVmService
02/13/2025, 17:35:01 -   VM0: Debian is powered off.
02/13/2025, 17:35:07 -   VM Debian has been started up.

I don't think I did anything wrong here -- I have been running different versions for many years. Might there be some workaround for this?

[kazsaj]

Make sure the user that runs the service has permission to read all the VM related files.

[frozn]

I encountered this problem today on Windows 10 too, just after updating VB from 7.0 to 7.2 together with VBoxVmService-7.0-Persimmon to VBoxVmService-7.2-Prune.

[frozn]

I found the solution. After reinstalling the VBoxVmService service, everything works fine again: