Failed to connect pipe to virtual machine: the system cannot find the file specified.

• Home
• Virtualization
• VMware

Posted by harjeet_matharu 2017-04-30T09:30:30Z

check Best Answer

View Best Answer in replies below

40 Replies

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  Screenshot?
  

  Was this post helpful? thumb_up thumb_down

• Here it is. Sorry, forgot to attach the screenshot earlier. [Running as Admin]

  
  

  Here, without right-click and Run as Admin.

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  Make sure the VMware Workstation server service has started [on your machine]
  

  Was this post helpful? thumb_up thumb_down

• All the required VMware services are currently running. I have also restarted all the VMware services but no go.

  
  

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  Did you move the machine, can you look in the folder where you saved it, is it still there? Is it in the recycle bin, did you rename it in the folder?

  Something has changed since it says 'cannot find'
  

  Was this post helpful? thumb_up thumb_down

• I just saw this video 5 mins prior to posting this question here. Services are already running. Moreover, My error at the bottom seems to be different than in this video. :]

  Was this post helpful? thumb_up thumb_down

• No, nothing has changed. All the folders are exactly at the same location where they were originally created. I have not copied, moved, deleted or made any kind of changes to these folders.

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  Can you re-import the VMX file in to the browser and try that then
  

  Was this post helpful? thumb_up thumb_down

• Unfortunately, no luck! 

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  All the files needed are in the same folder?

  Can you edit the VMX file?
  

  Was this post helpful? thumb_up thumb_down

• Yes, all the needed files are in the same folder. Yes, what needs to be edited?

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  I wanted to see if it would let you edit it.

  Can you show me the folder contents and what the edit screen looks like, be sure to highlight the disk for the second screenshot
  

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  It sounds like you already have VMware running and the file is locked, can you confirm all VMware applications are closed and any processes terminated, then try again.

  You should also avoid suspending DCs, either power them off or leave them running
  

  Was this post helpful? thumb_up thumb_down

• The contents in the folder look like this:

  
  

  Sorry, VMware won't let me edit the virtual machine as its in 'Suspended' state:

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  I'm more interested in the hard drive page on the settings

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  I don't want you to make edits, I wanted to see if you can open the edit page.

  See above about suspending DCs
  

  Was this post helpful? thumb_up thumb_down

• The VMware was running but the file seems to be locked because of Suspended state of virtual machine. I tried closing the app and stopped all the processes and then re-running the VMware Workstation and again the same error.
  

  You're right. I would refrain from suspending DCs in future.
  

  Was this post helpful? thumb_up thumb_down

• pure capsaicin

  VMware Expert

  • check 355 Best Answers
  • thumb_up 976 Helpful Votes

  What does it show on edit settings if you highlight the disk?
  

  Was this post helpful? thumb_up thumb_down

• The hard drive page while edit:

  
  

  Was this post helpful? thumb_up thumb_down

• Try this

  Remove the Server from the Inventory. Shutdown VMware, open Task Manager and make all VMware service and processes are stopped. Create a new older within the folder where the VM is and then copy all the files or that particular VM into it.

  Restart your PC, then add the system back into Workstation. I it asks just say you moved the VM

   

  Was this post helpful? thumb_up thumb_down

• I removed the VM from Workstation, Shut down the VMware, closed all the processes and services from Task manager, copied all the VM machine folder contents to a new folder. Restarted the computer, added the VM to Workstation from newly created folder and got the same error. :[

  Was this post helpful? thumb_up thumb_down

• Sorry I should have create a new folder OUTSIDE of the folder, did you create a new folder completely?

  Was this post helpful? thumb_up thumb_down

• Yes. I already tried with creating a completely new folder OUTSIDE of the actual folder but that didn't work.

  Was this post helpful? thumb_up thumb_down

• You have to get rid of a few things to unlock it.

  Create a folder and copy all the unnecessary files to it. Call it whatever you like once your VM is running properly you can delete it.

  The files you need to keep are

  .vmdk

  .nvram

  .vmsd

  .vmx

  .vmxf

  now when you open VMware "Resume this virtual machine" should be gone. You should be able to run it now.

  Was this post helpful? thumb_up thumb_down

• I did exactly as you said:

  -Created a new folder and moved all the files to it except the files you have mentioned above and then removed the old VM from VMware, re-added it and it gives me exactly the same error.

  Was this post helpful? thumb_up thumb_down

• Edit: I have multiple VMware machines and the error appears while running any of them so I believed that its not an issue with the VMware machines but the VMware Workstation and I was right.

  So I did a complete uninstall of VMware Workstation from Programs and then registry as well. Restarted the computer and reinstalled VMware Workstation.

  Added the machine to VMware again and all of them opened flawlessly. :]

  Was this post helpful? thumb_up thumb_down

• Edit: I have multiple VMware machines and the error appears while running any of them so I believed that its not an issue with the VMware machines but the VMware Workstation and I was right.

  So I did a complete uninstall of VMware Workstation from Programs and then registry as well. Restarted the computer and reinstalled VMware Workstation.

  Added the machine to VMware again and all of them opened flawlessly. :]

  The issue is now RESOLVED.

  0 of 1 found this helpful thumb_up thumb_down

• harjeet_matharu wrote:

  Edit: I have multiple VMware machines and the error appears while running any of them so I believed that its not an issue with the VMware machines but the VMware Workstation and I was right.

  So I did a complete uninstall of VMware Workstation from Programs and then registry as well. Restarted the computer and reinstalled VMware Workstation.

  Added the machine to VMware again and all of them opened flawlessly. :]

  The issue is now RESOLVED.

  That would of been my next step too..Glad to see it's resolved

  I use VMware with Windows 10 and just about every major update breaks VMware.

  Was this post helpful? thumb_up thumb_down

• I faced the same issue this morning, running vmware workstation 12, out of no where, the vm stopped [hanged] and all trial to get it to start were failed, i removed the .lck files and folders from the VM sub folder, checked all services are running and forced stop all vmware running processes using task manager. i could have restart it the host computer instead .. any way, i started my VM again and it works fine

  apparently, one vmware running process was locking the start of any VM
  

  Was this post helpful? thumb_up thumb_down

• Haha Have you tried turning it off and on again?

  Sorry I couldn't resist. I had the same issue and after a power-cycle everything worked great.

  This should be the best answer. Unless you WANT to reinstall everything/ :]

  Was this post helpful? thumb_up thumb_down

• I have the same exact issue since few weeks: "vmware workstation cannot connect to the virtual machine" and below "failed to connect pipe to virtual machine". The only solution is to restart the whole system [Win 8.1 in my case], but then it appears again after few days of usage.The need to restart the system every few days is ridiculous. I tried all the suggested solutions, reinstalled the whole thing, no luck. The only thing that changed in the pass few weeks was me installing GPG 4 Win and I started using smart cards for SSH logins. I will disable GPG agent from starting to see if it helps, but I guess it is a long shot. Have no idea what to do with the bloody thing.
  

  Was this post helpful? thumb_up thumb_down

• I got the same error in vm14 after updating windows 10. I uninstalled vm14 and installed vmware player 15. And then all things worked well. 

  Was this post helpful? thumb_up thumb_down

• Problem getting VMware to work in Windows 10. Messages such as 'Failed to connect pipe to virtual machine...'. I encountered this and when I did get it to work, it froze up after a few minutes. I solved it.

  Switch the computer off

  Leave for a few minutes

  Switch the computer on

  Before you back into VM, go into the root directory where VM files are stored, and delete any '.vmem' or '.lck' files.

  Go into Virtual Machine. Once the VM is working, go into the Virtual Machine files and delete any new '.vmem' or '.lck' files. If you can't delete them, type 'old' at the end of the file extension. You should find that the Virtual Machine continues to work.

  
  

  Was this post helpful? thumb_up thumb_down

• This is due to unkillable zombie process on windows.

  - Turn off auto start of shared vm if you've got some. Stop all VM you can access to.

  - Do a full shutdown of windows [cmd in administrator mode,  command : shutdown /s /f /t 0]. Note, this will shutdown immediately, be sure you do it once your work is saved

  - Start your computer

  - Before starting any VM, delete the vmem file of the incriminated VM

  - Start your guest

  [Note : If your incriminated VM is a linux, you will likely get a fsck during boot].

  1 found this helpful thumb_up thumb_down

• I am using VMWare version 11 and found it locked up with messages including 'failed to connect pipe', 'cannot connect to the virtual machine'. The system dumped a .vmem file in the directory and it was difficult to delete. I discovered the reason was because I didn't close down my XP programme before switching off the computer. At the bottom left of my Windows XP screen, I just have click 'Start' and shut down properly.

  Previously, the .vmem file could often not be deleted straight away, but after switching off and on a few times, it was possible to delete.
  

  But exiting the programme properly has solved the problem.

  Was this post helpful? thumb_up thumb_down

• I had the same issue on W10 Pro x64 on VMware-workstation 15.5.5  After upgrade from 15.5.0 to 15.5.0 had error message on all virtual machines [existing and freshly created]:

  "VMware Workstation cannot connect to the virtual machine. Make sure you have rights to run the program, access all directories the program uses, and access all directories for temporary files. Failed to connect pipe to virtual machine "
  

  This error message was when started VMWare on normal user account [non admin]. The reinstall/repair/uninstall/install did not fixed the issue.

  During troubleshooting I've tried to run VMWare as W10 Admin and suddenly had another error message [!!! WTF !!!]:

  "The program can't start because VCRUNTIME140.dll is missing from your computer" 

  So I've reinstalled the "Microsoft Visual C Redistributable for Visual Studio 2015, 2017 and 2019" and this was ultimate fix to the problem !!!

  1 found this helpful thumb_up thumb_down

• Can remove all folders with ".lck" and restart the computer. For me solved!

  Was this post helpful? thumb_up thumb_down

• This same issue happened to me on a W10 Pro & Home [Desktop & Laptop] while using VMware Workstation version 15.5.1 on both machines. It first happened on my desktop, but rather than look up a solution for it, I just uninstalled, re-installed, and created a new VM. This time was on my laptop, but I decided to look it up which is what brought me to this thread. I read the top "Resolved" post [and more], but that would have been one step short of what I did on my desktop. So, instead I went to Control Panel/Programs and Features, right click VMware and selected "Change" which then gave me the option to "Repair", and I repaired it. This worked for me, and I am currently writing this post on my desktop while logged into my Kali Linux VM on my laptop.

  Was this post helpful? thumb_up thumb_down

• got the same issue. I ended all vmware related tasks. And restarted VMware NAT Service. VMUSBArbService and VMnetDHCP services. Issue resolved . 

  Was this post helpful? thumb_up thumb_down