BrokenEvent.ISULR (InnoSetup Uninstall Logs Reader) is an open-source development library and utility tool designed to parse and inspect the proprietary binary uninstall log files (unins000.dat, unins001.dat, etc.) generated by the widely-used Inno Setup installer system.
Created as an independent side project by the developer group Broken Event, ISULR acts as a “comprehensive guide” or bridge for developers and system administrators who need to unpack exactly what an installer has written to a user’s machine. Why ISULR Exists: The Problem with .dat Files
When an application is deployed using Inno Setup, the installer automatically generates an uninstall log file containing information on every file copied, directory created, and registry entry modified. Because this file is encoded in a compiled binary format, you cannot read it using a standard text editor.
If a system administrator wants to verify a package deployment, or if a developer needs to build a custom launcher or updater that requires altering or reading existing installation files, they face a wall. ISULR provides the keys to unlock and inspect this data. Core Features of ISULR
The library provides deep programmatic and visual inspection into the underlying architecture of an installation history:
Read uninsXXX.dat Files: Decodes the structural data, compression layers, and headers used by Inno Setup.
Explore Record Contents: Pinpoints exactly what the installation did, mapped out by categories:
Related Files: Every binary, asset, and document extracted to disk.
Registry Entries: Every key, value, or string path added or altered in the Windows Registry.
Other Metadata: Directories created, shortcuts added, and specific structural configurations.
Data Exporting: Allows users to translate the binary data into easily readable formats including TXT, CSV, and XML for automated reporting or scripting.
Developer-Friendly Delivery: The engine is written in C# and is split into two implementations:
LibISULR: A reusable API assembly (UninstallLog class) to load logs directly into custom applications.
ISULR CLI / GUI: A rudimentary WinForms desktop interface and command-line companion allowing simple drag-and-drop file previews. Practical Use Cases 1. Designing Clean Application Updaters
When designing a launcher or updater (such as the open-source Collapse Launcher project, which famously adapted ISULR logic), the utility must know what files are already present. By using LibISULR, an updater can query the existing unins000.dat file, find outdated game or application assets, modify the records, or clean up leftovers safely. 2. Enterprise Auditing and Forensics
Sysadmins deploying applications across corporate domains can extract data using the CLI component to verify that software isn’t silently creating registry keys or writing to unauthorized paths outside of standard application directories. 3. Resolving Failed Uninstallations
If an application uninstall crashes halfway through or gets corrupt because files were manually manipulated, ISULR allows you to manually export the file list to a text document, giving you a definitive checklist of everything you need to delete by hand to completely clean the system. Where to Find It
Because it is a developer resource, the code is completely open-source and transparent. You can learn more, read documentation, or download the tools directly via the Official Broken Event ISULR Project Page or its preseverence/isulr GitHub Repository.
Are you hoping to use ISULR to build a custom update application, or are you trying to manually debug a broken uninstaller on a specific computer? Let me know so I can provide the exact command-line parameters or code snips you will need! AI responses may include mistakes. Learn more ISULR – Broken Event
Leave a Reply