This error is notorious among engineers using ANSYS Workbench (versions 15.0 through 2024). The message indicates that the core solver executable ( ansyswbuexe.exe ) has crashed unexpectedly. The mention of a “diagnostic file” suggests that ANSYS attempted to save crash logs (usually .dmp or .err files), but more often than not, that file is empty or impossible to decipher without ANSYS customer support.
If you are still having issues, it may help to check the to see if others have experienced the same issue with your specific version.
— In a particularly obscure but well-documented case, users with MSI laptops discovered that the "Nahimic" audio service, when set to autostart, was causing the crash. Disabling Nahimic from startup resolved the issue.
The diagnostic dump file itself might be triggering the error:
If you recently updated Windows:
Ansys caches temporary simulation states, user preferences, and window layouts in the Windows AppData directory. If these cache files corrupt due to an unexpected power outage, software crash, or update, AnsysWBU.exe will fail to launch. Resetting these folders creates clean, uncorrupted configurations.
Troubleshooting the "ansyswbuexe encountered a problem" Error in ANSYS Workbench
The error is one of the most frustrating obstacles an engineer or student can face in ANSYS Workbench . It typically flashes on the screen immediately after double-clicking Mechanical or DesignModeler , bringing simulation workflows to a grinding halt.
: Specific DLLs, such as libiomp5md.dll , can conflict between Windows system folders and Ansys libraries. Step-by-Step Fixes 1. Reset the Ansys User Profile This error is notorious among engineers using ANSYS
: Open a command prompt as an administrator and manually register key libraries using commands like regsvr32.exe ole32.dll .
A glitch in checking out a license feature.
Follow these troubleshooting methods in order from the most common, non-invasive solutions to deeper system adjustments. 1. Clear and Reset Ansys Application Data
A full Windows temporary directory or locked temporary diagnostic files will block ANSYS from writing new computational cache files. Press the to open the Run dialog box. Type %temp% and click OK . Press Ctrl + A to highlight every file in the directory. If you are still having issues, it may
Remember: The “diagnostic file” is your single biggest clue. Do not delete it immediately. Learn to read its first 20 lines, and you will become the person in your department who actually fixes ANSYS crashes instead of just rebooting and praying.
Incompatible gaming-class architectures or missing professional graphics processor priorities.
This is the most common fix. It forces Ansys to rebuild its configuration folders. Close all Ansys applications.