Troubleshooting

This article explains common issues and assists you in finding solutions to problems you may be experiencing.

Disc Image Editing

Files that are added into an image file are referenced until the image file is saved. Keep the referenced original files unchanged before saving to avoid inconsistent results.

Update a File

WinISO does not have a built-in editor for editing the content of files contained in image files. If you want to modify a file based on its original content, you can extract it from the image, make some changes, and then add it back to replace the old one.

In WinISO 6, double-clicking a file in the main window will extract the file to a temporary folder and then open it with the corresponding default application on your system. Modifications to the extracted file will not be automatically added back to the original image file.

In WinISO 7, double-clicking a file opens the built-in viewer for the file. The built-in viewer supports plain text and images. For unsupported formats, the raw content is displayed in hexadecimal format.

Reduce Image Size

With the quick save feature enabled, the image file size never shrinks, even if the files contained within the image have been deleted. Use "Save As" to rebuild a smaller image file that does not contain unused data.

In addition, enabling the file deduplication feature can result in a smaller image file if there are a lot of duplicate files existing in it.

Unable to Open

Some apps, mostly disc mounting tools, open image files in exclusive mode. This behavior prevents the image file from being opened by WinISO or other apps. Such an app may run in the background, making it difficult to notice.

On the contrary, an image file being opened by WinISO can not be opened by apps that require exclusive access. Some apps may give vague information when they fail to open a file, giving a false impression that the file is damaged.

To avoid such a conflict, close WinISO before using the saved image file in other apps.

Making vs Saving

Making an image file in the Make Image dialog box creates an exact copy of the original disc. It is ideal for backing up discs.

Saving will result in a different image file because the file system data is reconstructed on each save. It can be considered as a file-level backup if you open a disc and then just save it to an image file without making changes.

Bootable CDs

Usually, the bootable image contained in a bootable CD is dependent on the contents of the disc. WinISO tries to identify the bootable images commonly used in Windows or Linux installer discs, and automatically modifies them to avoid boot failure. However, if the bootable image is unrecognizable, WinISO will leave it unchanged. In this case, modifying the disc image file is very likely to cause boot failure.

WinISO supports extracting and importing bootable images, but it does not support authoring or editing bootable images.

Bootable USB drives

Booting from a USB drive is different from booting from a CD. Rufus is recommended for creating a Windows or Linux USB installation drive from an ISO image file.

Mounting

When mounting or burning an image with unsaved changes, the file system data is reconstructed in memory, and the file data is provisioned from the original image file, or from the original files if they were just added.

No drive letter

In rare cases, there is no drive letter assigned to the mounted image. You can manually assign a drive letter to it in Disk Management.

This is usually caused by the automount feature being disabled on your system, which is enabled by default. To enable automount, open an elevated command prompt and run the following diskpart command:

C:\> diskpart
DISKPART> automount enable
Automatic mounting of new volumes enabled.

or the following mountvol command:

C:\> mountvol /e

Disc Burning

Disc burning is supported via IMAPI version 2.0, which is supported natively starting with Windows Vista and Windows Server 2008. Enabling IMAPI 2.0 functionality for Windows XP and Windows Server 2003 requires the installation of the KB932716 update package.

Error Codes

The detailed descriptions of the error codes that may be encountered when burning a disc are listed in the IMAPI Reference.

Verification

IMAPI offers three verification levels: None, Quick, and Full. Quick Verification usually takes only a few seconds to perform the heuristic checks. Full Verification requires a relatively long time to read and verify the entire disc.

The behavior of the Verification checkbox in the disc burning dialog was changed in WinISO v6.4.

WinISO VersionsVerification UncheckedVerification Checked
WinISO v6.3 and earlierNo VerificationQuick Verification
WinISO v6.4 and laterQuick VerificationFull Verification

Limitations

ISO files store only the user data from each sector on an optical disc, which is 2,048 bytes per sector. And there is no concept of a "track" inside an ISO image. CDs with multiple tracks, audio tracks or video tracks, can't be stored inside a single ISO image.

WinISO is designed for editing ISO files, and it has a similar limitation that multi-track discs are not supported.

Formats such as CUE/BIN, CCD/IMG and MDS/MDF formats can be used to store multi-track disc images, including audio CDs. But WinISO does not support image files that contain multiple tracks either, regardless of their format.

Overall, WinISO can not be used for:

  • Backing up Audio CDs or Video CDs;
  • Manipulating image files of Audio CDs or Video CDs;
  • Converting videos (e.g., Converting DVD Video to VCD or MP4, or vice versa);
  • Authoring or customizing boot images;
  • Creating bootable USB drives.