2021-05-22, 09:50:31
For anyone reading this and having similar issues.
The problem has been resolved.
Somehow the VMware automation interface (VIX/vmrun) used by Vimalin wasn't functioning properly when invoked from Vimalin, but worked OK when called directly.
As such Vimalin was not able to detect that the VM was running.
A possible reason for that might be that a different user account was used during install than the account under which the user runs.
Rob has re-installed Vimalin using the same account as what he runs under and then it started to work as intended.
The problem has been resolved.
Somehow the VMware automation interface (VIX/vmrun) used by Vimalin wasn't functioning properly when invoked from Vimalin, but worked OK when called directly.
As such Vimalin was not able to detect that the VM was running.
A possible reason for that might be that a different user account was used during install than the account under which the user runs.
Rob has re-installed Vimalin using the same account as what he runs under and then it started to work as intended.