A specific Windows library file often causes this crash in newer versions of Ansys. Ansys Innovation Space Locate the file libiomp5md.dll C:\Windows\System32 Rename it to libiomp5md.dll.old
The error " AnsysWBU.exe encountered a problem. A diagnostic file has been written
Security software sometimes flags the inter-process communication tools used by ANSYS as malicious activity, killing ansyswbu.exe unexpectedly.
Visit the official NVIDIA or AMD website and download the latest enterprise or studio drivers for your GPU. Avoid generic Windows Update drivers. Set High-Performance GPU: A specific Windows library file often causes this
In the Windows File Explorer address bar, type %temp% and hit Enter. Find the .ansys folder and delete or rename it. Restart your computer. C. Change Scratch Solver Files Directory
This solves the crash instantly for many users:
When ANSYS Workbench crashes, you might see a pop-up window with the following text: "AnsysWBU.exe encountered a problem. A diagnostic file has been written: C:\Users\[YourUsername]\AppData\Local\Temp\AnsysWBDumpFile.dmp" . This crash can happen during various operations, such as generating a mesh, opening a project, solving a model, or even simply when closing the application. Visit the official NVIDIA or AMD website and
: Open a fresh instance of ANSYS Workbench. Create a new Mechanical component system, right-click the Model cell, select Import Mechanical Database , and target the recovered .mechdb file.
The executable AnsysWBU.exe acts as the primary graphical user interface (GUI) wrapper for Ansys Mechanical. It connects the core simulation solvers, like Mechanical APDL, with the visual environments where you build constraints, apply loads, and review results. When this wrapper loses communication with its sub-engines or hits a hard operating system limit, it forces a shutdown and logs a dump file—usually named AnsysWBDumpFile.dmp —in the local Windows temporary directory ( %USERPROFILE%\AppData\Local\Temp ). Direct Comparison of Primary Root Causes Primary Cause Typical Trigger Point Resolution Urgency Core Fix Strategy Clicking "Model" or "Mesh" Reset %APPDATA%\Ansys folder. Graphics Driver Conflicts Launching Mechanical GUI Update to certified GPU drivers. Special Characters in File Paths Opening or saving projects Rename paths using standard ASCII. Antivirus / Firewall Blocking Initializing add-ins or solvers Add whitelist exclusions for Ansys. Insufficient System Memory High-density mesh generation Increase pagefile or optimize mesh. Step-by-Step Troubleshooting Framework 1. Reset Corrupted User Profiles
Outdated or incompatible drivers can crash the 3D graphics interface. Ansys Innovation Space Find the
Reinstall Microsoft VC++ Redistributables (2015–2022) via the official Windows deployment packages. .NET Framework
Right-click ANSYS Workbench → . Some crashes happen because ansyswbu.exe can’t write to temp directories or license logs.
When Ansys Workbench ( AnsysWBU.exe ) crashes unexpectedly, it generates a .dmp (dump) file—often found in the %temp% directory—to help diagnose the root cause. However, the message itself rarely explains why the crash occurred. Common causes range from graphics driver conflicts and corrupted user profiles to insufficient solver memory or licensing issues.
As a last resort: