InnoSetup: Find out reason for restart

Question

I have an Inno Setup script that installs my application and its accompanying files. On some systems a restart is required, on some not. I would like to find out the reason for the required restart. How would I do this most intelligently? Thank you very much.

Just for debugging? You can peek in HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations to see if there are queued moves/deletes awaiting the next reboot — Alex K., Oct 30 '12 at 13:06
@Alex, there's no direct way to determine it from the InnoSetup script, so it could be the answer. — TLama, Oct 31 '12 at 16:17

Alex K. · Accepted Answer · 2012-10-31T17:13:27.133

5

For debugging purposes you can peek inside

HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

to see if there are any moves/renames/deletes queued for the next reboot.

(Sysinternals utility viewer)

edited Oct 31 '12 at 17:13

answered Oct 31 '12 at 17:06

Alex K.

171,639
30
264
288

score 1 · Answer 2 · answered Nov 01 '12 at 08:15

Use /LOG when you run the install and then look at the log file that it generates (by default in %TEMP%). It should fairly clearly show in there which files were queued for replacement on restart, or which other reasons caused a restart request to be issued.

Usually restarts are triggered by overuse of restartreplace without using something like AppMutex to ensure that the application has been shut down properly before installing, or from subinstalls executed during [Run].

InnoSetup: Find out reason for restart

2 Answers2