This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Win Explorer doesn't restart when shut down via Restart Manager (RMRegisterResources)
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 18, 2013
03:22 PM
Win Explorer doesn't restart when shut down via Restart Manager (RMRegisterResources)
We have a few MSIs that successfully shut down Windows Explorer, but don't restart it about 50% of the time (guesstimate); RmRegisterResources() is used. A number of other functions and methods were also tried (including looking for all process threads and passing them all to the restart manager, killing the oldest process etc.) but nothing has worked thus far.
Has anyone else been seeing this? Any suggestions on how to improve the success rate of restart?
Thanks!
Has anyone else been seeing this? Any suggestions on how to improve the success rate of restart?
Thanks!
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 22, 2015
03:17 PM
Did you ever figure out the solution to this issue? I'm finding the same thing happens to me. Restart Manager will successfully shut down explorer.exe, but some times it will fail to restart it. A look in the event logs shows me this message:
"Application 'C:\Windows\explorer.exe' (pid 5376) cannot be restarted - Application SID does not match Conductor SID.." So, it appears to be some kind of permissions issue, but I'm not sure yet how get restart manager to launch explorer.exe with elevated privileges.
"Application 'C:\Windows\explorer.exe' (pid 5376) cannot be restarted - Application SID does not match Conductor SID.." So, it appears to be some kind of permissions issue, but I'm not sure yet how get restart manager to launch explorer.exe with elevated privileges.