Why close all programs when installing something?

  • Thread starter Thread starter curious
  • Start date Start date
C

curious

I've noticed that most installation programs will recommend that you close
all other programs before proceeding with the installation. I can understand
that if the installation is going to update a program that is running, then
you'll probably want to close that program first. But besides that, is there
any point in closing all other programs? Even if the installation program
needs to update a DLL in use by another program, it's not a big deal if you
leave it running, because the installation program will tell you to restart
the system, and then the new DLL will be put in during the reboot.

How many people close all programs when they install something? I rarely do
it. And I bet that those who do close all programs only close the programs
in their task bar... they forget to shut down everything in their system
tray.
 
curious said:
I've noticed that most installation programs will recommend that you close
all other programs before proceeding with the installation. I can understand
that if the installation is going to update a program that is running, then
you'll probably want to close that program first. But besides that, is there
any point in closing all other programs?
Click to expand...

The other worry is loss of data if a running program has problems
during the update.

My experience says this is a worry of minimal proportions.
 
The other worry is loss of data if a running program has problems
during the update.

My experience says this is a worry of minimal proportions.
Click to expand...

Me, too. I usually close down as many things as I can, but if I
forget... eh, such is life. I really don't recall even having a problem
if, say, my email program is open, or Solitaire, or something. Most
decent installation programs will warn you if something they need to
update is still open.
 
I have had occasional problems with installations when my anti-virus software is
running (Norton). Could be a coincidence, or maybe the anti-virus software
creates
some kind of timing problems. I always shut it down, unless the installation is
suspect as having a virus.

Sherwin D.
 
curious said:
I've noticed that most installation programs will recommend that you close
all other programs before proceeding with the installation.
Click to expand...

It's the flawed way Windows is built. Now on Linux, there is NEVER any
recommendation to "close all programs" when installing new. And there's
never any need to re-boot either, unless the kernel has been updated.
 
Gordon said:
It's the flawed way Windows is built. Now on Linux, there is NEVER any
recommendation to "close all programs" when installing new. And there's
never any need to re-boot either, unless the kernel has been updated.
Click to expand...

Actually, as others have pointed out, this is rarely
necessary, and as such isn't indicative of any serious
Windows flaw. The warning is coded by the application
developer; it isn't a system message.

Application developers insert that message because
they never bothered to figure out what shared components
(if any) the application uses. In most cases, there are
no shared components being updated, and if the install
is built using something reasonably modern, like Wise
or InstallShield, the installer will tell you if it
can't update something.
 
Gordon said:
It's the flawed way Windows is built. Now on Linux, there is NEVER any
recommendation to "close all programs" when installing new. And there's
never any need to re-boot either, unless the kernel has been updated.
Click to expand...

That's something else I've never really understood with Windows. Does
the reboot message simply mean that what you just installed won't be
active until you reboot - so it's really optional - or does it mean that
it's unsafe to continue running until you reboot - so it's mandatory to
reboot.

As a prime example, most windows update hotfixes want you to reboot
after each install. If I didn't reboot then but continued to install any
other hotfixes/updates that were available, would that be safe?
 
It the correct way to install something so that any files that are currently
in use wont be overwritten
"Flawed" is a matter of opinion but hey ~ everyone's got one

Is pretty funny that you claim "never any need to re-boot either, unless
......."
LOL, remember, you're NEVER correct when you ALWAYS use absolutes.....

~B
 
Sid said:
That's something else I've never really understood with Windows. Does
the reboot message simply mean that what you just installed won't be
active until you reboot - so it's really optional - or does it mean that
it's unsafe to continue running until you reboot - so it's mandatory to
reboot.

As a prime example, most windows update hotfixes want you to reboot
after each install. If I didn't reboot then but continued to install any
other hotfixes/updates that were available, would that be safe?
Click to expand...

Indeterminate. It -should- be safe; but developers can do
things the safe way and the hazardous way. As an example,
and install (in Windows or *nix) can write all temporary
files to the temp folder, run the install, and delete
everything in the temp folder -- whether the installer
created it or not. Alternatively, the installer can
create a subfolder, and remove it when finished.

Normally, with Windows updates and hotfixes, as long as
you reboot after all the hotfixes are applied, you should
be fine. MS is actually pretty good about this; just not
perfect.
 
Ron said:
Indeterminate. It -should- be safe; but developers can do
things the safe way and the hazardous way. As an example,
and install (in Windows or *nix) can write all temporary
files to the temp folder, run the install, and delete
everything in the temp folder -- whether the installer
created it or not. Alternatively, the installer can
create a subfolder, and remove it when finished.

Normally, with Windows updates and hotfixes, as long as
you reboot after all the hotfixes are applied, you should
be fine. MS is actually pretty good about this; just not
perfect.
Click to expand...

Interesting, thanks Ron.

As far as hotfixes go, hopefully it wont be a problem for a few months
anyway. I finally managed to make a new install cd slipstreamed with all
SP's, hotfixes, patches and software up to March 2006!
 
Back
Top