![]() Then I am going to take option #1 and restore my full system from my last good system backup before the corruption (the Windows 10 Fall Creators update). My latest position is that I am going to get another backup drive and backup what I have right now. When he created my new VM, he had the filesystem set to full allocation mode to address the known issue. He acknowledged there were known issues with the file system and I didn't understand how this related to the the video drivers being corrupted. (Windows updates had to be disabled.) It is also not the greatest solution because it is a re-creation of my original Windows 10 VM and not exactly like my original. We tried option #2 and it works only because the new VM was created using an older version of Windows 10. ![]() He tried to repair one of my Windows 10 VMs but after numerous attempts he told me he was unable to fix it and I had 2 options - 1.) restore from backup and 2.) create a new Windows 10 VM and transfer the data after attaching to the broken VM. I reached out and was contacted by a representative from VMware and we setup a remote desktop session where he got onto my Mac and tried to help me out. While the Fusion GUI is running, can you once again open the terminal and see if there is a vmware-usbdiskarbitrator process running?Īlso, are there a set of USB arbitrator logs named vmware-usbarb*.log found in /Library/Logs/VMware ? If so, could you zip them up and post them.This has been quite a disappointing journey for me so far. In my Windows 11 log file, I'm seeing that the USB devices are being reported right after the poweredOn state. There's something else amiss here.Īccording to what I see in the logs, your VM is appearing to crash right after power-on as there are no more messages in the vmware.log after the power state is set to poweredOn.Īre there any vmware-vmx processes running after the transport error message (drop into a Terminal and issue: ps -ef | grep -i vmware-vmx ) You do not have to disable SIP or play around with root. VMs are working fine so I suspect something broken on your Mac and/or Fusion installation.įusion 13 does not use kexts any more. ![]() I'm running a very similar 2014 Mac mini with the same versions of Fusion and macOS. My system is running with Monterey 12.6.6, 8GB RAM, Intel Iris Graphics, 2,6GHz Intel Core i5.Ĭonnected devices: Monitor USB hub, Webcam Logitech 920 are available for the system.Īttached please find my log-files and the current settings from the VM (renamed to. So I assume that the necessary drivers (kexts) will not be loaded resp. ![]() I never received the message to allow "VMWare." in the general tab of system settings panel "Security&Privacy". Want to setup a Windows machine (Win11 圆4) from image.Īfter configuring basics and executing the VM a message appears "transport error (VMDB) -14: pipe connection has been broken".Īfter reading many posts related to this error message I still could not fix this.ġ) uninstalling (using "Remove-It") and reinstalling (with system restarts inbetween Ģ) putting "VMWare Fusion" app in system settings "Security panel" (accessability) ģ) manual registering VMWare's company ID in safe mode via terminal ġ) changing whole system via "sudo root" from terminal!Ģ) permantly disabling SIP via safe mode! Just installed new VM Fusion (VMware-Fusion-13.0.2-21581413_universal.dmg) on my mac mini 2014.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |