VMware Workstation 15 Pro showing black screen with rest api

[Loopback92]

If i open them manually works good, but if i use rest api for load them i get black screen in all machines.

Vmware workstation: 15.1.0 build-13591040

Windows10 version 1809 ( Compilation of OS 17763.557)

Api version: VMware Workstation REST API //vmrest 1.2.0 build-13591040

Virtual Machine OS: Windows 7

I have these python script for run the api and run the vms with api

[Python] import requests  import subprocess  from requests.auth import HTTPBasicAuth  imp - Pastebin...

wich I call from a .bat file from task scheduler, like these vms start when i need them with a simple job

For start =

cd "C:\Users\localhost\PycharmProjects\Scripts Python\VM_Manager"
set VAR_1=On
python Main.py %1 %VAR_1%

for switch them off

cd "C:\Users\localhost\PycharmProjects\Scripts Python\VM_Manager"
set VAR_1=off
python Main.py %1 %VAR_1%

start task scheduler windows job

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2019-06-08T02:08:37.8509653</Date>
    <Author>DESKTOP-09RV55J\localhost</Author>
    <URI>\Microsoft\Windows\UserTasks\Start1</URI>
  </RegistrationInfo>
  <Triggers>
    <CalendarTrigger>
      <StartBoundary>2019-06-08T01:05:27</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByDay>
        <DaysInterval>1</DaysInterval>
      </ScheduleByDay>
    </CalendarTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>S-1-5-21-12982169-1001</UserId>
      <LogonType>S4U</LogonType>
      <RunLevel>HighestAvailable</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
    <UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT72H</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>"D:\Virtual Machines\StartAll.bat"</Command>
    </Exec>
  </Actions>
</Task>

[wenwang_myheave]

Did you have ever try the API by the webpage? What's the output? Can you give the RESTAPI log?

[glennatred8]

Would like to report same.  If I control power state as I write in this article: https://wp.me/p5IdLQ-7t , you cannot go into the VMW app and access the VMs via the built-in console. Even if you exit VMW and run the VM's in the background and re-enter, it does not attach to the console process for those machines. The machines are otherwise fully functional and can be accessed via SSH/RDP, even from the app's SSH context menu option.

This looks like a bug, folks.

Thanks

@loopback92 Please let me know if you got anywhere on this.

[maniamscripty]

I have the same problem.

Using a python script.

this gist contains the python script