VMware Workstation

 View Only

 ISBRendererComm: Lost connection to mksSandbox (3796)

Jump to  Best Answer
RedFox's profile image
RedFox posted Jun 04, 2025 10:54 AM
The virtual machine was working perfectly for me, without any issues at all. However, after I updated the Intel® Arc™ & Iris® Xe Graphics – Windows driver from version 32.0.101.5768 to version 32.0.101.6874 (WHQL Certified), I started receiving the following error when launching the virtual machine:
 
ISBRendererComm: Lost connection to mksSandbox (3796)
 
If I disable Accelerate 3D graphics in the virtual machine settings, the VM starts without the error. However, performance is extremely poor, which is expected since graphics acceleration is disabled. Simply unchecking this option is not a viable solution—it makes working in the virtual machine practically impossible.
The virtual machine was working without any errors before the graphics driver update, with graphics acceleration functioning properly and overall performance being good. Unfortunately, I cannot downgrade the graphics driver, as I updated it for a reason — I had a program that didn’t work at all with the previous version. That’s why it’s very important to find a solution that allows the virtual machine to work with the latest stable version of the graphics driver.
 
I’m attaching a log file that contains detailed information about the error.
System info:
Windows 11 24H2 26100.4061
VMware® Workstation 17 Pro 17.6.3 build-24583834
Github thread: https://github.com/vmware/open-vm-tools/issues/766
Attachment  View in library
vmware.log 227 KB
RedFox's profile image
RedFox  Best Answer

After analyzing mksSandbox.log I realized that VMware is trying to use Vulkan, but an error occurs, causing the program itself to crash. I added one line in the vmx file to prevent the use of Vulkan:

mks.enableVulkanRenderer = "FALSE"

Now, judging from the new log, VMWare selects DX12 and the problem is now solved, everything works again. My graphics support Vulkan 1.4.312, but apparently VMware doesn't work with that version.

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

Requesting you to recreate the issue and share full support bundle of the affected VM where you are seeing "ISBRendererComm: Lost connection to mksSandbox (3796)"

RedFox's profile image
RedFox

@Dhairya Tomar I have already provided the log above containing “ISBRendererComm: Lost connection to mksSandbox (3796)”. I don't understand what files you need. What do you mean by “full support bundle”?

Dhairya Tomar's profile image
Broadcom Employee Dhairya Tomar

By Full support bundle, what I mean is when you encounter this issue next on the VM you had mentioned, go to menu Help->Support->Collect Support Data, select the VM where the issue is happening, generate full support bundle and share the same here

RedFox's profile image
RedFox

@Dhairya Tomar I've collected the data you're requesting. But unfortunately I'm not going to publish it here. The archive created contains a lot of personal data that has nothing to do with VMware, and I can't make my system vulnerable.  I can only share with you with specific logs after I have thoroughly checked their contents. Let me know which ones you need specifically (but that's just in case you have a real desire to figure out the issue, not to mimic some action). 
It's just easier for me to uninstall VMware and switch to VirtualBox (because without graphics acceleration, VMware is slower than VirtualBox) than to put all my personal data out in the open.

RedFox's profile image
RedFox
RedFox's profile image
RedFox

mksSandbox.log

Attachment  View in library
Shibdas Bandyopadhyay's profile image
Broadcom Employee Shibdas Bandyopadhyay

Can you please try with this config option mks.enableVulkanRenderer=FALSE and see if it's better, thanks!

RedFox's profile image
RedFox

@Shibdas Bandyopadhyay I have already solved the problem, which I already wrote about in this thread. You probably didn't notice my post - it is marked as the best answer. But thanks anyway :)