IsoBuster 5.0 Released!

July 4, 2022

Check out the many improvements and new functionality, such as 64 bit support, High dpi scaling, per monitor scaling, dark theme and much more.

From now on there will be two versions that can be used under the same license. A 32 bit version and a 64 bit version. Any modern system these days is 64 bit and that's the IsoBuster version you should be using as well. For legacy reasons however we will still maintain a 32 bit version as well, for as long as that is possible.

The 32 bit version supports Windows XP and higher (Windows XP (SP3), Vista, 7, 8, 10 and 11)

The 64 bit version supports Windows 7 and higher (Windows 7 (SP1), 8, 10 and 11)

Changes / New:

  • A 64 bit version
  • High DPI scaling and 4K/8K monitor support, crisp display at higher DPI instead of blurry fonts etc.
  • Dark Theme / Style support (Select under Options \ GUI \ Styles). Currently two dark and one light styles are included, but there's an option to use any other compatible VCL-Style out there, or you could make your own
  • Automatic switching between dark and light theme, depending on the system setting
  • Per monitor scaling
  • Panasonic DMR-BWT835 and DMR-BWT730 DVR/PVR support


  • LibEWF version 20130416 updated to version 20140608
  • Improvements for setting or resetting the image file associations in Options (Image Files / Supported Image File extensions)
  • Put back previous image file associations if possible, on reset or uninstall
  • Improved scanning for Panasonic DVR/PVR file systems
  • Panasonic and Pioneer DVR/PVR file/folder name entries are now considered UTF8
  • Multi-File + Multi-Session CUE files without a LEAD-OUT entry (even though faulty) are now supported
  • Plenty of other GUI improvements


  • Fixed an Exception Error that could happen while parsing certain IFO file systems on DVD
  • Fixed a Stack Overflow (IsoBuster would simply shut down) on highly fragmented files in the UDF file system
  • Fixed an issue that the 'Open File' Dialog didn't default to *.* when the CUE file didn't contain a file path
  • Fixed it so that CUE files without a quoted file/path still work properly

Please tell people about it, like and share it on Facebook and/or Twitter, post it on forums, reddit, etc. Practice safe and honest computing and stay away from cracks and keygens. Your help is appreciated.

Peter Van Hove,
Founder and CEO