Printable View
I have an installation that "sometimes" displays a "This system must be restarted to complete the installation" message after it is done. How can I tell what part of the installation generates this condition?
We done run one or more external installs that are "chained" as part of the overall installation - could one of them be returning the "reboot required" condition?
I've attached the log file from the last run that generated the message.
Mark,
If a file to be replaced is locked (in-use) then Windows needs a reboot. It only requests a reboot if the file can't be replaced because exclusive write access is not possible (file is locked/in-use).
You can very easily check this. If the reboot message comes up, simply check the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager->PendingFileRenameOperations
http://technet.microsoft.com/en-us/l.../cc960241.aspx
There you'll find the file(s) that need(s) to be replaced at next reboot.
As far as I can see, all kind of files are locked in your case:
M:\MuniSoft\SM\SM_DATA.dll
M:\MuniSoft\SM\C60ASCX.DLL
M:\MuniSoft\SM\C60CLAX.DLL
M:\MuniSoft\SM\C60DOSX.DLL
M:\MuniSoft\SM\C60MSSX.DLL
M:\MuniSoft\SM\C60RUNX.DLL
M:\MuniSoft\SM\C60TPSX.DLL
M:\MuniSoft\SM\LSPUZIPX.DLL
and more...
Hope this helps.
Friedrich
Is there a flag or variable I can check to see if this condition exists?
Mark,
Get System Info -> Reboot Status. It lets you determine whether the system should be restarted. Returns "1" if the system should be restarted.
BTW, all (or most of) your files are locked. So I think your application is "in-use" (active) when you do the update. You can test this BEFORE the file installation is performed if you would like to avoid a reboot.
Friedrich
That's a big help, thanks.Quote:
Originally Posted by linder