Since the Workbench interface is graphically intensive, driver issues are the primary suspect.
Open the .log file using Notepad or a text editor. While the content may appear highly technical, look for these keywords:
If the crash persists, some Windows prerequisites (like C++ Redistributables or .NET Framework) might be broken.
When AnsysWBU.exe crashes, Windows generates a diagnostic crash dump file—typically named AnsysWBDumpFile.dmp —inside your local %TEMP% directory. While the dump file requires debugging tools like the Windows Debugger to read directly, years of user data point to several primary culprits:
Try running Workbench as an to see if the crash is related to folder write permissions. 6. Re-Registering DLLs (The Last Resort) When AnsysWBU
Some users have fixed Mechanical crashes by renaming libiomp5md.dll in the C:\Windows\System32 directory to libiomp5md.dll.old .
Right-click the Workbench icon and select to bypass restricted folder read/write rules. Security Softwares Antivirus Whitelisting
Relaunch Workbench; it will rebuild these folders with default settings. Update Graphics Drivers:
I can then provide specific steps to fix your exact simulation environment. Share public link Re-Registering DLLs (The Last Resort) Some users have
Under , choose "High-performance NVIDIA processor" instead of Auto-Select. F. Check File Permissions
import os import subprocess import shutil import time from datetime import datetime
Step 1: Close all running Ansys Workbench and License Manager instances. Step 2: Press the Windows Key + R, type "%appdata%" and hit Enter. Step 3: Open the "Ansys" folder and locate your version folder (e.g., v231, v241). Step 4: Rename that specific version folder to "vxxx_old". Step 5: Press the Windows Key + R again, type "%temp%" and hit Enter. Step 6: Locate the folder named ".ansys" and rename it to ".ansys_old". Step 7: Relaunch Ansys Workbench to build clean configuration profiles. Use code with caution. 2. Remediate Intel OpenMP Conflict ( libiomp5md.dll )
Navigate to %Temp% and rename the .ansys folder to .ansys_old . In the vast majority of cases
Corrupted project or license issues
a general crash notification in ANSYS Workbench, typically indicating that the Mechanical application has failed . The "diagnostic file" is a memory dump (
Share it in the comments – ANSYS troubles are better solved together.
Crash occurs when rotating, zooming, or generating mesh previews. Diagnostic file may show OpenGL error or EXCEPTION_ACCESS_VIOLATION with graphics-related stack traces.
The "ansyswbu.exe encountered a problem" error, while alarming, is almost always resolvable through systematic troubleshooting. In the vast majority of cases, a simple graphics driver update or clearing of user settings restores stability. By following the structured approach outlined above, engineers can minimize downtime and return to productive simulation work. Always remember to back up your project files regularly, as no software is entirely immune to unexpected crashes.