https://forums.antwise.com/ Mon, 18 May 2026 06:01:46 +0000 MyBB https://forums.antwise.com/showthread.php?tid=185 Tue, 30 Jan 2024 20:15:17 +0100 Sontec]]> https://forums.antwise.com/showthread.php?tid=185 To get rid of the Vm blackscreen, you somehow pause the the VM and unpause it.

Now I was wondering, if somehow you could recreate the VmWare Workstation GUI,
couldn't you incorporate VNC viewer within Vimarun GUI ?

This way the VM would always be visible in the GUI (no black screen).
Securiy wise one could even lock down the firewall (automomatically) to only be 
able to view the VMs locally (if network security was an issue).

This way the VM should never be paused even if it was briefly.
If the "Vimarun" GUI would work over the network,
one could even use it as a command centre GUI to
stop and start diffirent VMs on diffirent hosts.

What are you thought on this suggestion ?]]> To get rid of the Vm blackscreen, you somehow pause the the VM and unpause it.

Now I was wondering, if somehow you could recreate the VmWare Workstation GUI,
couldn't you incorporate VNC viewer within Vimarun GUI ?

This way the VM would always be visible in the GUI (no black screen).
Securiy wise one could even lock down the firewall (automomatically) to only be 
able to view the VMs locally (if network security was an issue).

This way the VM should never be paused even if it was briefly.
If the "Vimarun" GUI would work over the network,
one could even use it as a command centre GUI to
stop and start diffirent VMs on diffirent hosts.

What are you thought on this suggestion ?]]> https://forums.antwise.com/showthread.php?tid=156 Tue, 06 Jun 2023 10:30:28 +0200 catac404]]> https://forums.antwise.com/showthread.php?tid=156 I am using Vimarun for some time and I think it will be useful to have some more settings.
There are cases when I do not want for a specific VM to auto start, so would be useful an option to check which VMs should start automatically.
Another useful option would be the possibility to set a time delay for VMs resuming. Because if you are using a lot of VMs, starting all in the same time is very slow.
Do you think it will be possible to implement these on a future release?
Thanks.]]> I am using Vimarun for some time and I think it will be useful to have some more settings.
There are cases when I do not want for a specific VM to auto start, so would be useful an option to check which VMs should start automatically.
Another useful option would be the possibility to set a time delay for VMs resuming. Because if you are using a lot of VMs, starting all in the same time is very slow.
Do you think it will be possible to implement these on a future release?
Thanks.]]> https://forums.antwise.com/showthread.php?tid=155 Tue, 16 May 2023 13:54:01 +0200 srk]]> https://forums.antwise.com/showthread.php?tid=155
The VM is set to auto start using the VM built in service and although it appears to work fine the USB Zigbee co-ordinator stick which is set to auto connect doesn't work in Home Assistant after a PC restart although everything else is fine.

I discovered this was due to the VM suspending and resuming as a full power off and restart of the VM resolves the issue.  I added a batch file to stop and restart the VM under my normal login credentials after booting but before login and although that resolves the issue with HA I can no longer use VMware Workstation interactively when I log in to the machine as it cannot take ownership of the HA VM presumably due to being used by the session 0 instance of VMware.

This brings me to Vimarun and whether what it does will give me a means of working around the issue.  I assume it still relies on VM suspend and resume but after it resumes the VM can it trigger a stop and start to force the USB device to reconnect and still be able to use VMware Workstation interactively with this VM?]]>
The VM is set to auto start using the VM built in service and although it appears to work fine the USB Zigbee co-ordinator stick which is set to auto connect doesn't work in Home Assistant after a PC restart although everything else is fine.

I discovered this was due to the VM suspending and resuming as a full power off and restart of the VM resolves the issue.  I added a batch file to stop and restart the VM under my normal login credentials after booting but before login and although that resolves the issue with HA I can no longer use VMware Workstation interactively when I log in to the machine as it cannot take ownership of the HA VM presumably due to being used by the session 0 instance of VMware.

This brings me to Vimarun and whether what it does will give me a means of working around the issue.  I assume it still relies on VM suspend and resume but after it resumes the VM can it trigger a stop and start to force the USB device to reconnect and still be able to use VMware Workstation interactively with this VM?]]> https://forums.antwise.com/showthread.php?tid=101 Tue, 08 Feb 2022 09:19:23 +0100 firstascent]]> https://forums.antwise.com/showthread.php?tid=101
Everything ALMOST works perfect for my use case. when my system boots up, VMware loads, my VM starts to load but I get a popup that says The VMware Tools resume script did not run successfully in this virtual machine. The VM will not continue until I hit the OK button.

If I hit the OK button the VM does continue to load, but the problem for me is I need it to load without any user input, so no error/popup screen. 

VMworkstation 16
Host OS: Win11
Guest OS: HomeAssistant OS

For what it's worth, I'm not too concerned about the VM shutting down or suspending etc whenever my Host OS reboots for any reason. I just need it to start automatically with the GUI in the foreground.

Any thoughts?

So basically, if I didn't get this error/popup, this would be absolutely perfect for me.]]>
Everything ALMOST works perfect for my use case. when my system boots up, VMware loads, my VM starts to load but I get a popup that says The VMware Tools resume script did not run successfully in this virtual machine. The VM will not continue until I hit the OK button.

If I hit the OK button the VM does continue to load, but the problem for me is I need it to load without any user input, so no error/popup screen. 

VMworkstation 16
Host OS: Win11
Guest OS: HomeAssistant OS

For what it's worth, I'm not too concerned about the VM shutting down or suspending etc whenever my Host OS reboots for any reason. I just need it to start automatically with the GUI in the foreground.

Any thoughts?

So basically, if I didn't get this error/popup, this would be absolutely perfect for me.]]> https://forums.antwise.com/showthread.php?tid=100 Mon, 07 Feb 2022 09:20:44 +0100 Bodenseematze]]> https://forums.antwise.com/showthread.php?tid=100 So I bought VimaRun and added them to it, so they should start at system start and keep running even if nobody has logged in.

As far as I can see, they all got started - but only after I login (as Administrator) to the machine.
After that login, the VMware Workstation window pops up and all the VMs got started - but not if I don't log in...
...and when I log out the user, all running VMs will go to suspend state - which is totally unwanted!

Why?
And how can I prevent this?

Do I need to automatically log in my Administrator after server start?
But even if I do this - how can I prevent it from suspending the machines?]]> So I bought VimaRun and added them to it, so they should start at system start and keep running even if nobody has logged in.

As far as I can see, they all got started - but only after I login (as Administrator) to the machine.
After that login, the VMware Workstation window pops up and all the VMs got started - but not if I don't log in...
...and when I log out the user, all running VMs will go to suspend state - which is totally unwanted!

Why?
And how can I prevent this?

Do I need to automatically log in my Administrator after server start?
But even if I do this - how can I prevent it from suspending the machines?]]> https://forums.antwise.com/showthread.php?tid=97 Tue, 01 Feb 2022 21:42:17 +0100 dmelnyk]]> https://forums.antwise.com/showthread.php?tid=97
     I have been evaluating Vimarun for a few days and had one issue resolved by setting the service to Delayed Start, however I have been testing it with the Wake on Lan feature which does start the computer after it is powered off, but then Vimarun fails to start VMware workstation or the VM I have selected for auto start in Vimarun.

    I have tried the following sequences:
         
          1) Manually start VMware workstation then power up VM; do a "reboot" command to windows on the Host system; 

                     Windows shuts down, the system does the normal motherboard post and restarts Windows and Vimarun starts VMware workstation and restores
                      the VM that was powered on;

           2) Manually power off the running VM and then close VMware workstation; do a "reboot" command to windows on the Host system;

                      Everything works the same as in test (1) above;

           3) Manually start VMware workstation then power up VM; do a system shutdown -i.e. windows power off command on the host system;

                       Powering on the system by hitting the start button on the system or using the WOL feature of the network card results in the system
                       doing the normal motherboard post and restarts windows on the host system - however Vimarun fails to start VMware workstation and
                        restore the VM;

      I have attached the log files from Programdata/vimarun/systemlogs below
  VimarunLauncher.txt (Size: 12.52 KB / Downloads: 1)
  VimarunService.txt (Size: 30.99 KB / Downloads: 1)       


     Just wondering if anyone has run into this and whether they can suggest a solution.

Best regards, Dave Melnyk]]>
     I have been evaluating Vimarun for a few days and had one issue resolved by setting the service to Delayed Start, however I have been testing it with the Wake on Lan feature which does start the computer after it is powered off, but then Vimarun fails to start VMware workstation or the VM I have selected for auto start in Vimarun.

    I have tried the following sequences:
         
          1) Manually start VMware workstation then power up VM; do a "reboot" command to windows on the Host system; 

                     Windows shuts down, the system does the normal motherboard post and restarts Windows and Vimarun starts VMware workstation and restores
                      the VM that was powered on;

           2) Manually power off the running VM and then close VMware workstation; do a "reboot" command to windows on the Host system;

                      Everything works the same as in test (1) above;

           3) Manually start VMware workstation then power up VM; do a system shutdown -i.e. windows power off command on the host system;

                       Powering on the system by hitting the start button on the system or using the WOL feature of the network card results in the system
                       doing the normal motherboard post and restarts windows on the host system - however Vimarun fails to start VMware workstation and
                        restore the VM;

      I have attached the log files from Programdata/vimarun/systemlogs below
  VimarunLauncher.txt (Size: 12.52 KB / Downloads: 1)
  VimarunService.txt (Size: 30.99 KB / Downloads: 1)       


     Just wondering if anyone has run into this and whether they can suggest a solution.

Best regards, Dave Melnyk]]> https://forums.antwise.com/showthread.php?tid=87 Wed, 24 Nov 2021 11:16:53 +0100 fil72]]> https://forums.antwise.com/showthread.php?tid=87 I can't understand why Vimarun starts automatically my VMs, but doesn't suspend them when the host reboots.
Any idea?
Host is Windows 10, guests are one Windows 10 and one Linux.
Best regards.
Filippo]]> I can't understand why Vimarun starts automatically my VMs, but doesn't suspend them when the host reboots.
Any idea?
Host is Windows 10, guests are one Windows 10 and one Linux.
Best regards.
Filippo]]> https://forums.antwise.com/showthread.php?tid=83 Thu, 28 Oct 2021 15:27:37 +0200 wila]]> https://forums.antwise.com/showthread.php?tid=83 It is called the Experimental vTPM feature (I wrote a more indepth article about it here)

Sadly this experimental feature is not 100% compatible with Vimarun.
If you added the experimental vTPM to a VM then some features of Vimarun no longer work for that VM.
It has no impact on your other VMs.

The reason for this is that the VMware automation programming interface that Vimalin uses thinks the VM is encrypted, but there is no password. As such the automation interface cannot resume or start a VM in the foreground.
I have contacted VMware about these problems and got a reply.
Last night they informed me that "it currently works as designed" and that we will have to wait for this to be resolved at their end.

What does work?

The VM is suspended on shut down as before.
The VM also resumes on start up as long as your VM is set to start in the background.
If your VM was already shut down then the VM will start if set to start in the background.

If you then want to use your VM in the foreground, it shows up as "black" and you will have to suspend & resume manually in order to get access to your VM in the foreground again.]]> It is called the Experimental vTPM feature (I wrote a more indepth article about it here)

Sadly this experimental feature is not 100% compatible with Vimarun.
If you added the experimental vTPM to a VM then some features of Vimarun no longer work for that VM.
It has no impact on your other VMs.

The reason for this is that the VMware automation programming interface that Vimalin uses thinks the VM is encrypted, but there is no password. As such the automation interface cannot resume or start a VM in the foreground.
I have contacted VMware about these problems and got a reply.
Last night they informed me that "it currently works as designed" and that we will have to wait for this to be resolved at their end.

What does work?

The VM is suspended on shut down as before.
The VM also resumes on start up as long as your VM is set to start in the background.
If your VM was already shut down then the VM will start if set to start in the background.

If you then want to use your VM in the foreground, it shows up as "black" and you will have to suspend & resume manually in order to get access to your VM in the foreground again.]]> https://forums.antwise.com/showthread.php?tid=79 Thu, 28 Oct 2021 05:26:16 +0200 angrycustomer]]> https://forums.antwise.com/showthread.php?tid=79
]]>
]]> https://forums.antwise.com/showthread.php?tid=76 Fri, 17 Sep 2021 18:16:10 +0200 passta]]> https://forums.antwise.com/showthread.php?tid=76
I am seeing the errors below in the event log.

The VimarunSvc service was unable to log on as DOMAIN\Username with the currently configured password due to the following error:
The user name or password is incorrect.

The service is set to use a domain account since there are no local accounts on domain controllers, and if I go to the service, and attempt to start it, it starts every time, with me logged on as the same user that is specified in the service or any other user, to logon, so I know the password is correct, and that it actually works, but not when the server restarts, only when I start it manually after being logged in.

I've tried other accounts with admin rights, same thing happens. I have also tried use local system, and that does not work.]]>
I am seeing the errors below in the event log.

The VimarunSvc service was unable to log on as DOMAIN\Username with the currently configured password due to the following error:
The user name or password is incorrect.

The service is set to use a domain account since there are no local accounts on domain controllers, and if I go to the service, and attempt to start it, it starts every time, with me logged on as the same user that is specified in the service or any other user, to logon, so I know the password is correct, and that it actually works, but not when the server restarts, only when I start it manually after being logged in.

I've tried other accounts with admin rights, same thing happens. I have also tried use local system, and that does not work.]]> https://forums.antwise.com/showthread.php?tid=75 Wed, 15 Sep 2021 07:05:15 +0200 jdh2n]]> https://forums.antwise.com/showthread.php?tid=75 https://forums.antwise.com/showthread.php?tid=69 Fri, 25 Jun 2021 20:16:42 +0200 sindripa]]> https://forums.antwise.com/showthread.php?tid=69 https://forums.antwise.com/showthread.php?tid=54 Thu, 21 Jan 2021 17:08:31 +0100 Sontec]]> https://forums.antwise.com/showthread.php?tid=54 Today I say you have a new software called Vimarun.
Could you please give an explanation what it does and why it should be used instead of shared VM within Vmware's Workstation?
What are the benefits of using it?

In the past, I have used several contraptions with Taskscheduler and scripts to start and stop my Vmwares using vmrun.exe.
I even started an Autoit project to add a GUI, but never finished.

However because the session # of the account not matching the (same) user on the computer, I was never able to interact with the VM using Vm Workstation.(blank/black screen)
So I always had to use a remote viewer (Teamviewer, VNC, RDP) to get into my VM.


P.s. Wanted to post some links I used with my program, but I am not allowed to post links :-(]]> Today I say you have a new software called Vimarun.
Could you please give an explanation what it does and why it should be used instead of shared VM within Vmware's Workstation?
What are the benefits of using it?

In the past, I have used several contraptions with Taskscheduler and scripts to start and stop my Vmwares using vmrun.exe.
I even started an Autoit project to add a GUI, but never finished.

However because the session # of the account not matching the (same) user on the computer, I was never able to interact with the VM using Vm Workstation.(blank/black screen)
So I always had to use a remote viewer (Teamviewer, VNC, RDP) to get into my VM.


P.s. Wanted to post some links I used with my program, but I am not allowed to post links :-(]]> https://forums.antwise.com/showthread.php?tid=55 Tue, 19 Jan 2021 14:02:14 +0100 Brancato]]> https://forums.antwise.com/showthread.php?tid=55 the software VIMARUN install and run, but all automatically started VM's after autimatically started remain with a complete black screen (either in Vmware workstation 16.0 16.1 and also 15.x)
I tried on several windows version (win10, windows 2019 server, Windows 2016 etc.) and different hardwares.
All the same behaviour: when the VM starts, they are in black (even if their internal processes work)


Any suggestion?]]> the software VIMARUN install and run, but all automatically started VM's after autimatically started remain with a complete black screen (either in Vmware workstation 16.0 16.1 and also 15.x)
I tried on several windows version (win10, windows 2019 server, Windows 2016 etc.) and different hardwares.
All the same behaviour: when the VM starts, they are in black (even if their internal processes work)


Any suggestion?]]> https://forums.antwise.com/showthread.php?tid=56 Sun, 10 Jan 2021 11:25:13 +0100 Ande]]> https://forums.antwise.com/showthread.php?tid=56 Worksation version 16 with newest updates.]]> Worksation version 16 with newest updates.]]>