<p>Have a look at <a href="https://code.vmware.com/apis/217/vsan#/doc/vim.EnvironmentBrowser.html" rel="nofollow noreferrer">this page</a> which documents <code>EnvironmentBrowser</code> for clues of which setting to edit.</p>

<p>Possibly something has a <strong>relative path that is now modified</strong>, or a <strong>resource that's fully used up</strong> or no longer available (or no longer valid, but that makes little sense if it's the same VM host).</p>

CC BY-SA 3.0
2018-03-13T15:14:28.447Z
2018-03-13T15:14:28.447Z
Danny Schoemann
<p>I cloned a VM in Vsphere Client as described <a href="https://www.experts-exchange.com/articles/9249/HOW-TO-Clone-or-Copy-a-virtual-machine-in-VMware-vSphere-Hypervisor-ESX-ESXi-4-x-or-ESXi-5-0.html" rel="nofollow noreferrer">here</a>. When I try to start it, it unexpectedly reboot over and over itself. I get this error in console:</p>

<pre><code>Call "EnvironmentBrowser.QueryTargetCapabilities" for object "45-envmgr" on ESXi "192.168.100.172" failed.
</code></pre>

<p>Which also shows another status message saying:</p>

<pre><code>The object has been deleted or not created completely.
</code></pre>

<virtualization><vmware>
Error starting cloned VM in Vsphere Client
Zeinab Abbasimazar
# Error starting cloned VM in Vsphere Client

(Asked by: username_0 on 2018-03-10)

I cloned a VM in Vsphere Client as described here. When I try to start it, it unexpectedly reboot over and over itself. I get this error in console:
Call "EnvironmentBrowser.QueryTargetCapabilities" for object "45-envmgr" on ESXi "192.168.100.172" failed.

Which also shows another status message saying:
The object has been deleted or not created completely.

**Tags:** virtualization, vmware


---

## 1 answers

### Answer by username_1 on 2018-03-13. Score: 1

Have a look at [this page](https://code.vmware.com/apis/217/vsan#/doc/vim.EnvironmentBrowser.html) which documents `EnvironmentBrowser` for clues of which setting to edit.

Possibly something has a **relative path that is now modified**, or a **resource that's fully used up** or no longer available (or no longer valid, but that makes little sense if it's the same VM host).


---

