Repository navigation
troubleshooting
Start with the log pane in the main window and the newest file in the logs folder — most
problems are explained there. See Usage for the log locations.
The download bundles are framework-dependent: they do not embed the runtime. Install the .NET 10 runtime (on Windows the Desktop Runtime; x64 or ARM64 to match your bundle) and start CHDMounter again.
This message appears when the WinFsp build cannot initialize the WinFsp.NET bindings. Causes:
- WinFsp is not installed — install the latest release.
- An old WinFsp version is installed — the bindings require the native DLL to expose every function they use and to match the expected version. Install the latest release and reboot.
-
A mismatched
winfsp-*.dllis next to the executable — remove straywinfsp-a64.dll,winfsp-x64.dllorwinfsp-x86.dllfiles from the application folder and let CHDMounter use the registered installation.
CHDMounter detects these situations before mounting and shows a dialog with the WinFsp download link. The single-file release extracts its content correctly, which is required for the WinFsp.NET bindings to load.
The driver for the selected mount core is missing or cannot be loaded. Install the latest Dokany or WinFsp release and restart the application, or switch cores in Settings → Mount core.
The FUSE 3 library is missing. On Linux install it with your package manager (for example
sudo apt install libfuse3-3 fuse3) and make sure /dev/fuse exists (sudo modprobe fuse).
On macOS install macFUSE.
All drive letters are in use, or the chosen letter is reserved by another process (drives mounted
in another session can be invisible to DriveInfo). Pick a free letter in the Mount point
box or let CHDMounter choose automatically. On Linux/macOS use a folder path instead.
NTSTATUS 0xC0000035 (STATUS_OBJECT_NAME_COLLISION) means the folder mount point is already in
use. CHDMounter retries with suffixed folders automatically; if the problem persists, unmount any
stale CHDMounter mount or restart the application.
CHDMounter retries the remaining mount candidates when a folder cannot be created, and reports the reason in the log. Check the folder permissions or choose a different mount point.
- Verify you selected the correct console type. Try
iso9660orpsauto, or the alias recommended in Console Types. - Some discs ship with unusual layouts; try a generic mode (
iso9660,isoraw2352). - Check the log pane for the parser's error message.
- Make sure a CHDMounter window is focused when you press F8.
- Screenshots are written to the
Screenshotfolder next to the executable first; if that folder is not writable the application falls back to the application data folder. The saved path is written to the log — see Screenshots. - A failure to save is logged but never interrupts the application.
The update check is best-effort. If GitHub cannot be reached (offline, firewall, rate limit) no notification is shown and the failure is logged at Information level. You can always check the Releases page manually.
- On Windows, settings are DPAPI-encrypted for the current user. Copying
settings.datbetween user accounts or machines makes it unreadable; CHDMounter then resets to defaults. - A corrupt settings file is reset automatically (and removed) on the next launch.
- To reset manually, close the application and delete
settings.datfrom the application data folder — see Settings.
That is expected. CHDMounter mounts images read-only and never modifies the CHD file.
- Reproduce the problem once.
- Open Help → Open AppData Folder and pick the newest file in
logs. - Open an issue on the issue tracker and attach the log plus a description of the disc and console type used.
See Privacy and Telemetry for what the application may send automatically.