Hey, calm down. You never should create new topics based on the same question more than one time. You can't do it with NSIS naturally, but you can create 2 installers in which one of them will be executed when the computer restarts. You can use the code below to make Windows to execute the second installer when the computer restarts next time: code: WriteRegStr 'HKLM' 'SOFTWARE Microsoft Windows CurrentVersion RunOnce' 'Program Name' 'C: Path To File.exe' (Where 'Program Name' is the name of the program, and 'C: Path To File.exe' is where the second installer is located). The mechanism to start the installer after reboot in the middle of the installation using RunOnce section in the registry works fine, but I need to continue the installer from the position that it was restarted. I know that I can use a plug-in to jump on the needed state.

But before the reboot I have to store some data, needed for the second reboot (for example the page that the installer have to jump, the selected components and so on.). The question is where to store the data? I can write it on the HDD, but where (temp folder???) or in the registry. What is the typical storage for such information in such case? I don't have experience with this and I need advice what is the best way to do it.

From NSIS Wiki. Reboots the computer. Be careful with this one. If it fails,.onRebootFailed is called. NSIS: Nullsoft Scriptable Install. I discovered that the Au_.exe file of $TEMP ~nsu.tmp directory was deleted on reboot after having uninstalled a. Check for updates in the running product. It downloads the build 4737. Install it from the running product into C: Temp2. Indeed, the problem is confirmed, as the installer for build 4737 asks for a reboot. TEST2: Install product 4720 into C: Temp1 Run the installer for build 4737 manually (interactively by double-clicking). And install into C: Temp2.

Warning: The /REBOOTOK switch requires administrator rights on Windows NT and later. 4.9.1.2 Exec command Execute the specified program and continue immediately.

Note that the file specified must exist on the target system, not the compiling system. $OUTDIR is used as the working directory. The error flag is set if the process could not be launched. Note, if the command could have spaces, you should put it in quotes to delimit it from parameters.

E.g. Gta Vice City Gasoline. : Exec '$INSTDIR command.exe' parameters'. If you don't put it in quotes it will not work on Windows 9x with or without parameters. Exec '$INSTDIR someprogram.exe' Exec '$INSTDIR someprogram.exe' some parameters' 4.9.1.3 ExecShell [/INVOKEIDLIST] action command [parameters] [SW_SHOWDEFAULT SW_SHOWNORMAL SW_SHOWMAXIMIZED SW_SHOWMINIMIZED SW_HIDE] Execute the specified program using ShellExecuteEx.

I'm launching my Windows application this way after the installation. On the end of installation. From NSIS), and restart it from the start.