Failed to connect pipe to virtual machine не удается найти указанный файл
Sharing ideas about cybersecurity, digital forensics and programming.
VMware VMs Not Running Problem
06/03/2017
Problem
Today something weird happened on my VMware Workstation 12 Player. I was unable to run any of my virtual machines(VMs) stored on my computer. When I tried to run a VM, an error message pop up, saying:
VMware Player 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. The system cannot find the path specified.
If start VMware Workstation Player in administrator mode, the second part of the error message became:
The vmx process exited prematurely.
Cause
Lots of attempts were performed based on the solutions found on Internet, including disabling anti-virus software, re-installing VMware Workstation. But none of the methods worked.
I then checked the Windows event log to see if I could find some useful information there. Run the Event Viewer, go to Windows Logs - Application. Then I found an application error record with the following message:
Combined with the previous error message displayed by VMware Workstation, I was able to determine that the vmware-vmx.exe encountered some errors brought by gameudp.dll while starting and was terminated.
Solution
Further research about this gameudp.dll indicates that it is not a part of the original Windows system file and is safe to be removed. So I backed up this file, then deleted it from C:\Windows\System32. After that, I restarted VMware Workstation. This time, the VM successfully started and the problem was solved.
Interestingly, later I restore the gameudp.dll back to its original location. The VMware Workstation still functioned normally. The actual cause of the problem is yet to be found and the role of gameudp.dll is still not clear.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- VMware Technology Network
- :
- Desktop Hypervisor
- :
- VMware Workstation
- :
- VMware Workstation Pro Discussions
- :
- VMWorkstation 16 on windows 11 Failed to conect pi.
michaelsaunders
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I have freshly installed VMWorkstation on Windows 11.
I am running fully paid licenses on both.
I created my first machine on VMWorkstation which is Ubuntu.
When I hit the play button I get error message:
Failed to connect pipe to virtual machine: The system cannot find the file specified.
I have tried the following steps.
1. Create a new virtual machine
2. Reinstalling Visual studio redistributables 2015 as per a post I found
3. Reinstall VM Workstation
Nothing has worked. Should I request a product refund as this product seems faulty.
Parradoxx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
I get exactly the same problem.
Dialog box error immediately after attempting to start any VM:
"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: The system cannot find the file specified.
VMware "failed to connect pipe to virtual machine""
Nothing fixes it:
Ran total uninstall, deleting old config, and re-install of of VMware Workstation v16.2 latest download.
Ran a repair of all the Microsoft C++ redistributables.
Same problem if a new virgin VM is created.
I am surprised there is no response to this thread.
I am going to roll back to Windows 10 and try again in 12 months time.
Parradoxx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Error still persists - Further to my above post:
My VMware VM's have been fully functional on Windows 10 for years.
Microsoft just auto-upgraded me to Windows 11.
I still get the same error as the above post when trying to start a VM.
VMware Workstation 16 Pro, Version: 16.2.2 build-19200509
Can somebody please provide a solution to this problem.
Parradoxx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
Performed a Windows 11 operating system 'Reset', then reinstalled VMware Workstation from scratch - still the same problem.
VMware 'Help - About' say's Host OS Version: Windows 10 Pro, 64-bit (Build 22000.434) 10.0.22000
This is incorrect - the host OS is now Windows 11 but VMware cannot detect that, even after a fresh install.
vmware.log exists but has no log entries for the failed startup
Parradoxx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Email to a Friend
From a new install of Windows 11: Performed VMware removal using the VMware uninstall utility, with the option to remove/wipe all previous settings. Reboot. Ran cCleaner to purge all redundant VMware registry settings remaining. Reinstalled VMware using factory defaults. Created a new VM. Attempting to start the VM - same error: 'Failed to connect pipe to virtual machine'
Reinstalled Windows 11, this time resetting all Windows 11 settings to factory default. Reinstalled VMware Workstation with factory default settings. Created a new VM. Attempting to start the VM - same error: 'Failed to connect pipe to virtual machine'
This is a Z590 MSI motherboard with latest firmware and with current release hardware peripherals. I have owned VMware for over a decade, and know my way around it.
VMware should fix this bug. Customers should not have to pay VMware for technical support to fix VMware's own software bugs. Customers should not have to do VMware's R&D bug troubleshooting for them.
I've been running vm 5.1.0 for the last 6 months roughly. I access the servers remotely (still in the building) through the vm client on my windows 7 desktop. Now suddenly (first time every) with no changes I'm aware of I cannot access any of the VMs on the network. Im presented with the following error
"Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe: The system cannot find the file specified"
P.S. I can still get into the servers using RDC
Tony3300
Popular Topics in VMware
Yes, Im thinking maybe some other software is getting in the way and a reboot clears it until it starts again. You could check if it works after you start other programs/services that you use on that PC.
Spark! Pro Series - 10 May 2022
Today in History: 10 May1291 - Scottish nobles recognize authority of English King Edward I1497 - Italian navigator Amerigo Vespucci leaves for his first voyage to the new world (disputed)1534 - French navigator Jacques Cartier reaches Newfoundland176.
40 Replies
- check 338 Best Answers
- thumb_up 879 Helpful Votes
Here it is. Sorry, forgot to attach the screenshot earlier. (Running as Admin)
Here, without right-click and Run as Admin.
- check 338 Best Answers
- thumb_up 879 Helpful Votes
Make sure the VMware Workstation server service has started (on your machine)
All the required VMware services are currently running. I have also restarted all the VMware services but no go.
- check 338 Best Answers
- thumb_up 879 Helpful Votes
What else changed?
- check 338 Best Answers
- thumb_up 879 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'
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. :)
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.
- check 338 Best Answers
- thumb_up 879 Helpful Votes
Can you re-import the VMX file in to the browser and try that then
Unfortunately, no luck!
- check 338 Best Answers
- thumb_up 879 Helpful Votes
All the files needed are in the same folder?
Can you edit the VMX file?
Yes, all the needed files are in the same folder. Yes, what needs to be edited?
- check 338 Best Answers
- thumb_up 879 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
- check 338 Best Answers
- thumb_up 879 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
The contents in the folder look like this:
Sorry, VMware won't let me edit the virtual machine as its in 'Suspended' state:
- check 338 Best Answers
- thumb_up 879 Helpful Votes
I'm more interested in the hard drive page on the settings
- check 338 Best Answers
- thumb_up 879 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
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.
- check 338 Best Answers
- thumb_up 879 Helpful Votes
What does it show on edit settings if you highlight the disk?
The hard drive page while edit:
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.
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. :(
Sorry I should have create a new folder OUTSIDE of the folder, did you create a new folder completely?
Yes. I already tried with creating a completely new folder OUTSIDE of the actual folder but that didn't work.
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
now when you open VMware "Resume this virtual machine" should be gone. You should be able to run it now.
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.
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. :)
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.
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.
I use VMware with Windows 10 and just about every major update breaks VMware.
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
Corey7373
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/ :)
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.
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.
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.
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).
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.
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 .
Sharing ideas about cybersecurity, digital forensics and programming.
Snap! BIG-IP vuln, Lincoln College, instant messaging, Google I/O, & space!
Your daily dose of tech news, in brief. You need to hear this. Hackers are actively exploiting BIG-IP vulnerability with a 9.8 severity rating We spotlighted this last week but it is back in the news. Shortly after F5 released patches for a c.
If you could take an extended break from work, what would you do with the time? Not only that, but how intentional would you be in planning for that break? In part 2 of the interview with Mike Wood we explore the planning and thought processes that went.
I am getting error - Failed to connect pipe to virtual machine. The system cannot find the path specified, while powering on virtual machine.
I have already tried restarting VMware Authorization service. Running VMware as Admin didn't help either.
It was working all fine until yesterday and suddenly stopped working.I am using VMware Workstation 12 Pro on Windows 10 Pro machine with full local admin privileges.
I would appreciate a quick fix on this issue.
Enter to win a Bose Sleepbuds II and more!
Contest ends 2022-05-20 Contests Fill out the form fill, and answer a question in the thread! Contest Details View all contests
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.
VMware VMs Not Running Problem
06/03/2017
Problem
Today something weird happened on my VMware Workstation 12 Player. I was unable to run any of my virtual machines(VMs) stored on my computer. When I tried to run a VM, an error message pop up, saying:
VMware Player 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. The system cannot find the path specified.
If start VMware Workstation Player in administrator mode, the second part of the error message became:
The vmx process exited prematurely.
Cause
Lots of attempts were performed based on the solutions found on Internet, including disabling anti-virus software, re-installing VMware Workstation. But none of the methods worked.
I then checked the Windows event log to see if I could find some useful information there. Run the Event Viewer, go to Windows Logs - Application. Then I found an application error record with the following message:
Combined with the previous error message displayed by VMware Workstation, I was able to determine that the vmware-vmx.exe encountered some errors brought by gameudp.dll while starting and was terminated.
Solution
Further research about this gameudp.dll indicates that it is not a part of the original Windows system file and is safe to be removed. So I backed up this file, then deleted it from C:\Windows\System32. After that, I restarted VMware Workstation. This time, the VM successfully started and the problem was solved.
Interestingly, later I restore the gameudp.dll back to its original location. The VMware Workstation still functioned normally. The actual cause of the problem is yet to be found and the role of gameudp.dll is still not clear.
On premises Central password manager with granular access?
Hi,Looking to have on premises Central password management solution, where we can store all passwords securely, updated, giving access to users based on their requirements etc.Looking for on premises option, for paid option, prefer perpetual license.Thank.
24 Replies
Try re-installing the client on your PC.
OP Tony3300
Just got done with that, still fails (also restarted).
Issue started last night with just on vm, now cant get into any servers.
I can log into the vm system, but from there, I get that error and black screen when accessing individual servers. No one else here is having that issue. All roughly have the same system.
OP Tony3300
Nope didn't work
OP Tony3300
Ok, restarted the computer earlier then wa-la im in so i was like that was weird.
Now serveral hours later same computer, problem arrives again.
FYI- I logged into another computer using all the same credientials no issue, so whatever it is, is this computer i think
I had the same issue yesterday only on one computer, but the other workstations that run Win 7 had to log out and back in or reboot in and then go to one of the network drives and log in with their network credentials to gain access to the network files and printer. We run SMS 2003. Our one last XP machine had no issues. We run a SQL program that kept it's access to the database on the server, but we couldn't print or email from it.
I would really like to know what changed. Was it a Windows update? Was it something with our antivirus? We use VIPRE.
OP Tony3300
From what understand, I've had no system changes. So not sure there. Was able to get in fine today. But when I did happen a restart was a temporary fix.
Try turning of the firewall. And check if any other software/services are running that could be blocking the connection.
OP Tony3300
Firewall is off via GPO, What am I looking for that would be blocking the connect. ports in use?
Yes, Im thinking maybe some other software is getting in the way and a reboot clears it until it starts again. You could check if it works after you start other programs/services that you use on that PC.
OP Tony3300
Wondering if Acrobat would be causing my issues. I've noticed in the past then when running OCR certain functions of windows and other software cease to stop working.
One way to find out :)
OP Tony3300
Ok, I closed my vm ran a ocr on a pdf, was not able to connect to my vm.
closed acrobat and re-opened my vm and was able to get in without restarted.
Looks like this is something I'll have to deal with, not sure why this suddenly happened, neither of the two software has updated. but w/e.
OP Tony3300
Ok, the issue is back again. Thought it went away. Started this morning, only had Microsoft Lync running (closed still failed).
So I flushed my DNS, added the esx host IP to my host file, still not working?
The console is looking for \\.\pipe\vmware-authdpipe
I have same issue, but it solved when I find a correct way to resolve the DNS name.
My ESXi host was added to vCenter with FQDN not IP address, but my newly installed PC did not point to the right DNS server and cannot resolve the FQDN of host.
Since other operations were worked fine via vCenter client, I did not know the FQDN issues until I got the MKS connection error as same as yours.
This problem has gone immediately after I fixed the DNS resolving.
Background: I have my hosts added to vCenter by FQDN and not IP address. When it was last working I had the hosts added via IP address, but changed it to easily identify hosts.
Solution: Checked DNS on the client I was on and no DC's were present, corrected that and instantly started working with no reboot.
Thank you raytracy!
Everyone else, check your DNS!
ITControl.gr is an IT service provider.
raytracy, how to selved this. can you tell me the steps.
Cause after i install vCenter then appear me this error.
2 ways you can solve this.
1. Put all your hosts names into your DNS server and make sure your PC, and the hosts, vcenter are all using the same DNS Server IP
2. Modify your host file to include the IP and the hostnames
Let me know if you need more detailed information.
I also met this problem but discovered finally that it's a network problem. As my vSphere Client was running a a my laptop and i am using a VPN connection to reach the vCenter server and the ESX hosts.
So I would say the same thing as JayMar but i a more basic words: We make sure that the vSphere client can reach by IP first but also by FQDN:
%u2003a. the vCenter server(s)
%u2003b. the ESX host(s)
@mouuali / Mocroc - Thank you!
APropes
I just had this problem, but to multiple but not all VMs; vCenter was set up using IP addresses, so it wasn't DNS. My solution was to do a vMotion to another host (leaving storage as-is), rebooting the host, and migrating all the VMs back.
i have solved this issues installing version of vSphere Client VMware-viclient-all-6.0.0-4437566, hope thas helps
Thanks for the info. After spending hours I solved this by installing latest version of vSphere client in my virtual lab.
thank you, make sure dns for all esx/vcenter resolve from vSphere client.
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Encryption for servers, workstations and devices
I would like to know how others are handling this, our auditors wants us to have all of our data encrypted on our servers, workstations, and devices.I want to know the best way to go about this and how well does it work with MS SQL server and our ERP syst.
Читайте также: