VMware Communities
jefazo92
Contributor
Contributor

Virtual machine not detected when VMware Workstation is started

Hi everyone,

Until today, whenever I opened VMWare my VM would be ready just for me to click on "Power on this machine. For some reason it has now disappeared and I have to go manually into the folder in which I have the VM stored. Also I have gone to File -> Scan for VMs -> "Folder in which I have my VMs stored but the scan yields no results at all. However, if Open a Virtual Machine manually, the VM file appears and I can select it to be built up in VMWare. The only thing I did on my Windows host was to disable VMWare on start up. Could that be the reason? If so how may I fix this without enabling VMWare on startup? Thanks in advance.

6 Replies
knordby
Contributor
Contributor

Old thread but I want to help out others when they're searching for this.

I'm on VMWare 15.5 Workstation Pro, for reference. I do not know if this is the same in 16.x, but I would assume so.

As a check beforehand, if you click F9 (View > Customize > Library), any VMs that are already added in there will not show up on another scan, from what I've seen. I would try launching the VM from there if you see it listed, but if it fails, then you will need to troubleshoot that before getting into this.

If you don't have anything listed in there, or VMs are missing, I would recommend doing the following:

Delete everything out of your library, right click on "My Computer" and also select "Remove Non-existant Virtual Machines", close VMWare completely, and then reopen. I *think* this is happening because at launch it doesn't recognize the VMs, but still has it added to the library for when it does recognize it later on.

 

As an additional note:
I found a related thread from a few years back, but the solution of "double check permissions" doesn't seem to work. Also, as the user in there pointed out, I cannot open up a support ticket with their tech team because the standard support license only lasts 30 days.

https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-pro-16-does-not-scan-for-existi...

I've also done some digging into this because it's very annoying.

Per the documentation: https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-A8614A58-610B-43...

It considers .vmx a valid VM.

Reply
0 Kudos
continuum
Immortal
Immortal

> Ive also done some digging into this because it's very annoying.

??? - sorry what is so anoying about finding your vmx-files ?
Would you expect  that when you run MsPaint it scans all your harddisk and finds all bmps and png files for you ?



________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
knordby
Contributor
Contributor

Hi continuum,

I'm happy to hear this hasn't ever been an issue for you. Or if you've never used the feature before, you can click on File > Scan for Virtual Machines. I hope this helps.

Reply
0 Kudos
continuum
Immortal
Immortal

I just doubleclick the vmx-files.
On my harddisks I usually have several hundred VMs - so I just pick those I need in my current environment and doubleclick them. Done ...

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
anilspp
Enthusiast
Enthusiast

Learn something from this post.

Reply
0 Kudos
xqxqxq
Contributor
Contributor

This feature is broken?

Permissions are correct, used it previously comes up blank now

Please only reply with helpful answers