VMware Communities
AquayaJeff
Contributor
Contributor
Jump to solution

Another user with the "Transport (VMDB) error -14: Pipe connection has been broken" question

Greetings all-

Can't access my Virtual Machine due to Transport (VMDB) error -14: Pipe connection has been broken.

My Virtual Machine is Windows XP, and I am running Fusion Player Version 12.2.4 (20071091) on a 2016 MacBook Pro, running MacOS Monterey 12.5.1. My Mac's processor is 2.9GHz dual-core Intel Core i5, Turbo Boost up to 3.3GHz, with 4MB shared L3 cache.

This problem occurred suddenly - it was working without issue last week. I've been reading the various suggestions and fixes and not sure how to proceed. I can verify SIP is enabled on my Mac.

Deeply grateful for any help here - this is a major work disruption for me.

 

Reply
0 Kudos
24 Replies
AnhHaLong
Contributor
Contributor
Jump to solution

Hi guy, 

Thank you very much for your kind guidelines, actually I used OpenCore My iMac to use Ventura and I had to take back Mac OS Catalina and then used VMware fusion 12 and now everything is fine. But I was appreciated with your spending time to guide us carefully and your knowledge of tech is clear. 

Thank you very much for your kind help. 

Have a nice day, 

Reply
0 Kudos
ColoradoMarmot
Champion
Champion
Jump to solution

Opencore isn't supported, and has known issues with Ventura and Fusion 13.  It's time to start planning to upgrade your machine to a supported configuration - catalina has unfixed security vulnerabilities and isn't safe to run anymore.

Reply
0 Kudos
ccaadduu
Contributor
Contributor
Jump to solution

For those with Opencore, try to select ˜Secure Boot" on advanced settings and rewrite your EFI partition.

Just got it running with my old Macbook Pro 11,1, with unsupported Ventura installed.

Reply
0 Kudos
SvenGus
Expert
Expert
Jump to solution

FYI, AMFIPass - with which Fusion works perfectly - is now integrated in the latest OCLP main release:

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/tag/0.6.8

Reply
0 Kudos
BenButz
Contributor
Contributor
Jump to solution

Thanks for this post - I experienced this issue after updated to MacOS 14 Sonoma.  This resolved my issue.

Reply
0 Kudos