Fusion 26H1 (25388279) crashes Windows 11 ARM on Apple Silicon when WinTrack 17 uses 3D acceleration

[Javier Mota Gonzalez]

Hello VMware Fusion Team,

I would like to report what appears to be a reproducible graphics bug in VMware Fusion.

After several hours of testing and log analysis, I managed to isolate the issue to VMware Fusion's 3D acceleration.

Environment

Host

• MacBook Pro M5 Pro
• Apple Silicon
• macOS Sequoia

VMware Fusion

• VMware Fusion Professional 26H1
• Build 25388279

Guest

• Windows 11 ARM (fully updated)

Application

• WinTrack 17

---

Problem

When 3D Acceleration is enabled for the virtual machine, VMware Fusion crashes while WinTrack is rendering its 3D scene.

Fusion loses the graphics renderer and Windows is restarted.

---

Steps to reproduce

1. Create a Windows 11 ARM virtual machine.
2. Enable Accelerate 3D Graphics.
3. Install WinTrack 17.
4. Open any layout.
5. Switch to the 3D view.

---

Expected result

The application should display the 3D scene normally.

---

Actual result

The virtual machine crashes and Windows restarts.

---

Troubleshooting performed

I performed multiple tests to isolate the problem.

Test 1

3D Acceleration Enabled

Result:

• VM crashes every time.
• Crash is reproducible.

Test 2

3D Acceleration Disabled

Result:

• WinTrack starts correctly.
• The same layouts open correctly.
• The 3D view also works.
• I did not notice any significant performance degradation.
• No crashes after repeated testing.

This strongly suggests the issue is related to VMware Fusion's graphics acceleration rather than WinTrack itself.

Relevant log entries

The attached VMware Fusion Problem Report contains GPU-related failures including:

PANIC: Error during command buffer execution
kIOGPUCommandBufferCallbackErrorOutOfMemory

The vmx lost its connection to the mksSandbox

PANIC:
ISBRendererComm: Lost connection to mksSandbox

The VM configuration confirms that:

mks.enable3d = "TRUE"

Because the only changed variable was VMware Fusion's 3D acceleration setting, I believe this points to a problem in Fusion's graphics stack (Metal/OpenGL translation or mksSandbox) rather than in the application itself.

The complete VMware Fusion Problem Report is attached.

If additional logs or testing would help reproduce the issue, I would be happy to assist.

Thank you for your work.

I hope this report helps improve VMware Fusion on Apple Silicon. I would be happy to test future builds if additional verification is useful.

Javier Mota

[Rajeswara Reddy Kotla]

Thanks for the detailed info. We have filed a bug for this issue and the respected developer will be looking into it.