It sometimes takes rather long time to shutdown windows.
When XP SP2 shows the normal blue screen on exit
the time the message “loggin you of” shows is ok,
the time the message “saving your settings” shows in ok,
the time the message “windows is closing” shows is rather long (2-3 minutes)
When avast is disabled the shut down process is normal.
Is it possible to debug this situation?
Hey Eddy, I guess your kidding huh ?
I did this once and at the next boot, it took 5 minutes for a harddisk-scan before windows booted, so I guess this is meant as a joke ?
No I am not kidding. I really do it. No problems at all when doing so.
Only thing is that if you changed some settings they will not be safed, but that’s all.
I’m stunned !
I really thought when shutting down this way, the most terrible things would happen, smoke coming out of the pc-case and so on ;D
So, how do you configure it in windows xp ?
And is there a gracious way to exit windows with the keyboard (like in SuSE ctrl+alt+backspace/alt+s) when the system hangs when exiting ?
Of course the system should be shut down before powering off. And this is the reason why ATX motherboards does not turn the power imediately off, but instead signal this to be handled by OS.
On my system Holding in the power button (not reset) for 5 seconds shuts down the system and generally there are no problems, like having to check the drives on the next boot. It is not something that I do regularly.
If people are deleting/clearing the page file on exit this can slow the exit considerably.
And what if the systems “hangs”?
Is there a keyboard-combination (as described above in SuSE) to shut down the system immediately in a non-destructive manner ?
When I try ctrl+alt+del the same thing happens: on boot, windows complains it isn’t shut-down gracefully and starts a disc-scan before booting the operating system.
Getting back on topic, I also noticed my system takes longer to shut down since avast has been installed. Same thing on my friend’s system where I installed avast. It is not always consistant though. Sometimes is does shutdown normally but many times it takes a while now. I wish this could be debugged. I don’t want to install a third-party app to shutdown.
Such problems are almost impossible to debug (at least without the aid of the kernel debugger). This is because the system refuses to load any monitoring tools at this stage - it just sits there and waits for something - without the ability to determine for what it’s waiting…
I get these Application warnings when this happens.
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 7/15/2005
Time: 9:52:09 PM
User: NT AUTHORITY\SYSTEM
Computer: xxx
Description:
Windows saved user xxx\yyy registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
I have tried msconfig and disabled some services but it takes too much time to disable/enable services. From time to time the system shudown is normal and I can’t trust that the disabled sevice was the cause.
I think it would be funny to find out the cause of this shutdown delay.
Microsoft has some KB articles about shut down problems (eg USB).
Is it possible to enable logging in Avast in this late stage?
I would like to try a debugger, please tell me more!