RestartManager | Managed Windows Restart Manager API | REST library

I use this to check if a file is in use:

There is no option. Because all GUI elements are part of the MSI Installation. And normally the installation should be finished when the EndDialog is shown. In my special case the util:RestartResource of Wix was restarting all processes in the moment MSI is closing. Because of that it was after all GUI elements.

The only way it could work is to implement a CustomAction which is rendering a window by them self. But it would not recommend this way.

For question 2, in the document RM_PROCESS_INFO

bRestartable

TRUE if the application can be restarted by the Restart Manager; otherwise, FALSE. This member is always TRUE if the process is a service. This member is always FALSE if the process is a critical system process.

This value indicates if the application can be restarted by the Restart Manager.

For question 1, Note that services are running in session 0. If the process occupying the resource (registered in RmRegisterResources) is a service A, the RmGetList function which also running in the service process B will return lpdwRebootReasons = RmRebootReasonNone, bRestartable = TRUE.

But if A is not a service, then A & B are running in different sessions, lpdwRebootReasons = RmRebootReasonSessionMismatch and bRestartable = FALSE

other results:(B run with elevated privileges)

• A & B is a console and in the same session：lpdwRebootReasons = RmRebootReasonNone, bRestartable = TRUE, ApplicationType = RmConsole.
• A & B is a console and in the different session：lpdwRebootReasons = RmRebootReasonSessionMismatch, bRestartable = FALSE, ApplicationType = RmConsole.
• A: service, B: console: lpdwRebootReasons = RmRebootReasonNone, bRestartable = TRUE, ApplicationType = RmService

(B not run with elevated privileges):

• A & B is a console and in the different session：lpdwRebootReasons = RmRebootReasonCriticalProcess, bRestartable = FALSE, ApplicationType = RmCritical.
• A: service, B: console: lpdwRebootReasons = RmRebootReasonPermissionDenied, bRestartable = FALSE, ApplicationType = RmCritical

According the document bRestartable depends on ApplicationType. And then, we can see that if the bRestartable = TRUE, then the lpdwRebootReasons = RmRebootReasonNone. But when bRestartable = FALSE, It depends on the other members RM_PROCESS_INFO.