Jump to content
Posted 28 February 2010 - 07:56 AM
Posted 28 February 2010 - 10:34 AM
Posted 28 February 2010 - 11:12 AM
Posted 28 February 2010 - 11:17 AM
The dllhost.exe process is amongst the integral components of MS Windows OS versions. Also known as the Microsoft DCOM DLL Host Process, the dllhost.exe application is an OS-initialized file. This means the dllhost.exe process is executed by the MS Windows OS to run during boot time.
The dllhost.exe process is important for the stability and functionality of MS Windows-based machines since it monitors DLL-based activities in the background. Thus, the dllhost.exe file manages the applications installed on the MS Windows-based machine with regards to its DLL-based activities. With this, the dllhost.exe file should not be altered, removed, or renamed in any way. In addition, the dllhost.exe process should not be terminated through the Windows Task Manager since doing so will affect the functionality of the applications running on the MS Windows-based machine, which frequently results to system crashes, data corruption, and registry damage among others.
Posted 28 February 2010 - 11:22 AM
Edited by CPU10, 28 February 2010 - 11:23 AM.
Posted 28 February 2010 - 01:45 PM
Posted 28 February 2010 - 02:24 PM
Never do a hard shutdown (holding down the power button) unless you absolutely have to. It is not healthy for the computer. The only time this should be done is if it is unresponsive for a few minutes ("locked up" or "frozen" as I like to say), and you have no other option than to do a hard shutdown. But like I said, don't do it unless you have to.
Posted 28 February 2010 - 02:49 PM
I absolutely second the above.
Never do a hard shutdown (holding down the power button) unless you absolutely have to. It is not healthy for the computer.
My help doesn't cost a penny, but if you'd like to consider a donation, click
Posted 28 February 2010 - 03:05 PM
Posted 28 February 2010 - 04:36 PM
No, it's not. The hardware doesn't know the difference between a hard shutdown (power button) and a peaceful shutdown (doing it through Windows). But the software DOES know the difference. That's why you get the "Windows did not shut down successfully" screen when you try to boot after a hard shutdown. It knows that it did not go through the shutdown sequence and things were left "open/unresolved/unfinished". I've had problems before with software (including Windows itself) not working correctly after a hard shutdown. One word of advice: NEVER do a hard shutdown while the system is booting. You will most certainly screw it up. I've done it once, but fortunately System Restore was able to save me. Some things got corrupted and was making things act screwy (the screen resolution being the obvious one). Windows can usually recover from a hard shutdown while it is just running normally (although like I said, you shouldn't do it unless you absolutely have to), but doing it during a boot can render it unoperable. A hard shutdown essentially crashes Windows.
Its just like using the shutdown/restart method on Windows or any other OS.
Posted 28 February 2010 - 04:55 PM
Posted 28 February 2010 - 05:50 PM
0 members, 0 guests, 0 anonymous users