Troubleshooting

Troubleshooting

.NET Desktop Runtime message

If Windows shows "You must install .NET Desktop Runtime to run this application", there are two common causes:

1. The runtime-required build is being used without Microsoft .NET 8 Desktop Runtime installed.
2. A build artifact such as obj...\apphost.exe was started instead of the published HakamiqChdTool.exe.

Fix

Use one of these options:

• Download the self-contained ZIP.
• Or install Microsoft .NET 8 Desktop Runtime.
• Always run HakamiqChdTool.exe from the extracted release folder.
• Do not run anything from obj or bin folders.

Correct executable

Run HakamiqChdTool.exe from the extracted release folder.

Do not run apphost.exe from obj</code> or bin</code>.

Those folders are for development/build output and are not end-user release folders.

Which ZIP should I use?

Use HakamiqChdTool-v1.1.1-win-x64-self-contained.zip if you want the easiest setup.

Use HakamiqChdTool-v1.1.1-win-x64-runtime-required.zip only if Microsoft .NET 8 Desktop Runtime is already installed.

Verify file integrity

Runtime Required SHA256:

8c867ad9b1e691d0ec6730d473bfe4adeb01bcd6b379e6d6e8ac28425e308b21

Self-contained SHA256:

fed2cc54c98021845e15563075dde06e551584e008a9beea5f7ca7df6cc0ffba

---

Additional troubleshooting

The application does not start

Check that you extracted the release package before running the application.

Do not run the application directly from inside a ZIP archive.

Use a normal local folder such as C:\Tools\HakamiqChdTool.

Avoid restricted folders such as C:\Program Files and C:\Windows.

The tool cannot read a source file

Check that:

• The file still exists.
• The file is not locked by another program.
• The drive is connected.
• The user account has permission to read the file.
• The source drive is not reporting I/O errors.

If the same file fails repeatedly at the same point, the source file or storage device may be damaged.

Output already exists

If the output CHD already exists, the tool may skip the item to avoid overwriting existing data.

Remove or rename the existing output file only if you are sure it is no longer needed.

Conversion failed

A failed conversion can be caused by:

• Unsupported input format.
• Incomplete disc image.
• Storage read/write error.
• Not enough free space.
• Permission problem.
• Damaged source file.
• External conversion tool failure.

Review the displayed status and logs before retrying.

Conversion was canceled

If the user presses cancel, the item should be treated as canceled, not as a normal failure.

Canceled operations may leave partial output files depending on when the cancellation happened.

Storage or temperature warning

If the tool shows a storage or temperature warning, review it before continuing.

Large conversions can put sustained load on storage devices.

PS3 experimental behavior

PS3 support is experimental. If a PS3-related input is rejected, skipped, or classified conservatively, this is intentional safety behavior.