Software Deployment

as of my knowledge only some applications will ask for reboot but not every application.

There are a limited set of circumstances which absolutely require a reboot, e.g. kernel-level device driver installation, files in use during an installation, additions to System path or environment. A cursory examination of the package will tell you which applies in your case.

Actually, to be blunt, for you to ask whether every application install requires a reboot betrays such a fundamental lack of knowledge about Windows OSes that I really must countenance against you continuing in your chosen career path without first undergoing some extensive training.

use this tool WhyReboot-1.0.1.537 it a freeware google it

thanks raj

OK, this is a conspiracy, right? You're trying to hospitalise me with chronic side-aching?

WhyReboot is a simple registry look-up tool (I *think* there's already a similar thing...FridgeEdit, is it called? It'll come to me...) which queries the PendingFileRenameOperations key. THAT'S ALL IT DOES! If your reboot is caused by anything else, this brain-dead tool won't help.

Ian - I think you misunderstood the question. "Is REBOOT is mandatory for every application?" would here mean, if every application asks for reboot really requires reboot?

hp_orc - Not every application which asks for restart requires a restart. As Ian said, a close examination of the package is required before we decide.

So what? My comment still stands. If he/she doesn't know how to investigate why a reboot might be requested, he/she should give up now.

murali.bhat - how we can investigate that which apllication really requires a REBOOT.

Open your MSI and see if it has any command-lines under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" or "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" registry keys. Generally, the command-lines under these keys will be executed only at the time of machine startup.

Also, check if your MSI has any KERNEL drivers to be installed and started as part of the installation.

Thanks!

Neither of the HKLM entries mean that the machine requires a reboot, just that the listed program will run at start-up.

Given the question, do you imagine that the OP would know what a kernel driver is, much less how to recognise one in an MSI?

Lastly, it's probably not a particularly smart idea to use your email address as an alias in a public forum...

Additionaly:
Most of all changes in HKLM\System require REBOOT. Most common reasons: services and drivers. Sometimes reboot could be avoided by restarting services (spooler service for printer drivers).

There are plenty of reasons why you should reboot the workstation after you install an application.

1. If you enable the logging in an MSI, you will see an error code "3010". It needs a reboot.

2. If you have included an Active Setup. It needs a reboot or log off.

3. If you open the application without reboot and is throwing an error or is behaving differently. You probably need a reboot.

4. The owner who requested it to be packaged wants a reboot for some reasons we sometimes don´t know then it needs a reboot.

5. Other reasons stated earlier in this thread.