If you have enabled any "Beta" features in the ANSYS options, turn them off, as these are prone to triggering diagnostic dumps. 5. Review the Diagnostic File
Look for .log or .err files. Scroll to the bottom to find the . If you see "Access Denied," it is likely a permissions issue; try running Workbench as an Administrator . 6. Anti-Virus Exceptions
The file is typically found in your temp directory ( %TEMP% ) or the project folder. If you have enabled any "Beta" features in
The most common culprit is a corrupted user settings folder. ANSYS stores temporary UI configurations in a hidden folder that can become "clogged." Close all ANSYS applications. Open File Explorer and type %AppData% in the address bar. Navigate to the Ansys folder.
Find the folder corresponding to your version (e.g., v241 for 2024 R1) and rename it to v241_old . Scroll to the bottom to find the
If the crash happens specifically when opening the "Geometry" or "Mechanical" cells, the issue might be the display scaling or the workspace layout. In Workbench, go to View > Reset Workspace .
The ansyswbuexe process is the core executable for the ANSYS Workbench user interface. When it crashes and generates a diagnostic file, it usually means there is a conflict between the software and your system environment, hardware drivers, or corrupted temporary data. 1. Clear Your AppData (The "Soft Reset") Anti-Virus Exceptions The file is typically found in
Sometimes, a pending Windows update or a missing .NET Framework library causes instability. Ensure your Windows OS is fully updated.
ANSYS Workbench relies heavily on hardware acceleration. If your GPU drivers are outdated or if you are using an integrated chip instead of a dedicated NVIDIA/AMD card, ansyswbuexe may fail.