CodingWonders / CodingWonders/DISMTools
Program exception
@CodingWonders is already working on this.
Since Mar 15, 2026.
- Dominant language
- Visual Basic .NET
- Stars
- 1.5k
- Forks
- 72
- Avg merge
- 11m
- Merged PRs (30d)
- 4
Description
If you have run into an internal error (program exception), we would like to learn more about it. When an error occurs, its information will be copied to your clipboard. If you can't find error information on your clipboard, a local copy was also saved at <program directory>\Logs\Errors.
PLEASE PROVIDE DETAILS ABOUT THE EXCEPTION, OR YOUR ISSUE WILL BE CLOSED WITHIN 4 HOURS
Exception information: please tell us what happened below:
How did it happen? What steps did you perform in order to experience this problem?
Attaching DynaLog event logs
DISMTools 0.6.1 and later use DynaLog as a means to write diagnostic information to a log file that you can send to the developers. The log is stored in <program directory>\Logs:
- If you are using an installed copy, go to
\Program Files\DISMTools\<Stable or Preview>\logs - If you are using a portable copy, go to
<startup location>\logs
The file in question is DT_DynaLog.log. Attach this log by dropping it below:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.