Acronis True Image costs performance when not used
4 days ago
- #Acronis
- #Windows
- #Performance
- Acronis True Image causes high CPU usage in Explorer.exe when plugging/unplugging an external monitor.
- The issue stems from tishell64.dll, part of Acronis True Image, which excessively calls CreateToolhelp32Snapshot and Process32NextW.
- Debugging revealed that these calls consume significant CPU time, sometimes up to 60 seconds, making the system sluggish.
- Acronis has acknowledged the issue and plans to fix it in the next release, but a workaround involves deleting a specific registry key.
- Uninstalling Acronis True Image is the most effective solution for users experiencing this issue.
- The article also highlights missing metadata in DLLs shipped by both Microsoft and Acronis, calling for better automated checks.
- The investigation was thorough, involving ETW traces, Visual Studio debugging, and discussions with Acronis.