Tom G
unread,May 19, 2026, 9:45:31 AM (5 days ago) May 19Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to innosetup
Environment
OS: Windows 10 (10.0.26200), x64, admin install mode, RedirectionGuard enforcing
Inno Setup versions compared (same machine, same .iss, byte‑identical source):
• 6.7.1 - FAST (no delay)
• 6.7.2 - SLOW (regression appears here)
• 7.0.0‑beta (32‑bit edition, 32‑bit installer) - SLOW (same regression)
Script: very large single .iss (~33,000 lines; very large [Files] and [Components] sections - thousands of entries; ~10k‑line [Code] section)
Symptom
After InitializeSetup returns, there is a ~50 second freeze with HIGH CPU (single core pegged) BEFORE the wizard appears. No installer/script code runs during the gap (nothing is logged). Not network‑related - network calls in the script complete in milliseconds immediately after the gap.
Reproduction / measurement (from /LOG output, same script)
6.7.1:
[InitializeSetup] -- OK ... Extracting temporary file: ...top.bmp ≈ 4.5 s
6.7.2 and 7.0.0‑beta:
same gap ≈ 54 s, CPU‑bound, no log lines in between.
top.bmp is the first thing extracted in InitializeWizard, so the delay is entirely inside Inno Setup’s internal preparation between InitializeSetup returning and InitializeWizard being called - before any Pascal script code executes.
Only variable changed: Inno Setup version. Script is byte‑identical. Not caused by script code, network, antivirus, or machine state.
Scope note
The delay scales with the size of the [Files] / [Components] sections. Small scripts likely will NOT reproduce it. A large script is required. A reproducible large script can be provided privately if needed.
Impact
Makes 6.7.2 and 7.0.0‑beta unusable for large installers (users see ~1 minute hang before first page). Forced to stay on 6.7.1 for production.
Ask
• Is there a known change in 6.7.x/7.0 affecting startup / [Files] / [Components] preparation cost that could explain an O(n) worse regression?
• Any directive/workaround to restore 6.7.1 startup behavior on 6.7.2 / 7.0?
Regards,
Tom