Have an idea?

Tell us how we could make Inno Setup more useful to you. Share your ideas, suggestions, and feature requests below, and to upvote ideas from others.

This board will be open during April 2026. After that, we will close it and use your input as inspiration for our development roadmap. We will not be able to act on every suggestion, but we read everything.

Thank you for sharing your thoughts with us.

You can interact anonymously, or create an account if you prefer. This board is powered by Featurebase. Their privacy policy is available here.

Native Auto-Updater Module and Built-in Functions

Hello Inno Setup Team, First of all, thank you for maintaining such a fantastic and reliable tool. I would like to suggest adding native support for an auto-updater mechanism. Currently, creating a proper updater requires writing complex Pascal Script from scratch (using WinHttpRequest to check versions, handling custom downloads, and executing the new setup silently). It would be incredibly helpful to have a dedicated [Updater] section or a set of simplified native functions to handle this workflow. The ideal implementation would include: Remote Version Checking: A native function to easily read a remote URL (like a plain TXT or JSON file) and compare it with the installed version. Integrated Download UI: A built-in wizard page that handles the download of the new installer, showing a native progress bar without needing custom script logic. Seamless Execution: A simple command or flag to automatically run the downloaded installer (e.g., with /SILENT), close the currently running application, and apply the update. Having these tools built into Inno Setup would save developers a massive amount of time when building web installers and update systems. Thank you for your time and consideration!

An Anonymous User 4 days ago

1

Search/filtering functionality to the Components list

Currently, Inno Setup supports basic incremental search in the components list (jumping to an item by typing its name). However, this behavior often conflicts with the installer's navigation hotkeys. In complex setups, typing to find a component can accidentally trigger a page change unless all hotkeys are manually disabled. Many times it works only for just few first letters and doesn't find all components I would like to propose a more robust filtering system for the Components page: 1. Search UI: A dedicated search/input field that appears when the user starts typing or presses a shortcut (like Ctrl+F). This would provide visual feedback of what is being typed. 2. Dynamic Filtering: Instead of just jumping to the first match, the checklist should dynamically filter the view to display only the components that match the entered string. 3. Conflict Resolution: By having a focused search state, the installer could temporarily suspend global navigation hotkeys, preventing accidental jumps to the Next/Back pages while the user is searching. This would significantly improve the UX for installers with large component lists, making the selection process faster and more reliable. I’m having two installers with very extensive component lists one have ~1500, the other one ~600, and it’s a nightmare for the users (around 300k) to find what they want.

Tom G 4 days ago