Delay shutdown

When I shutdown the pc I occasionally get the message that Windows is waiting for background program to close. However, nothing is listed. It’s hard to pinpoint the cause because it’s random but it only occured after the 2013 installation. I suspect it’s due to the upgrade. I remember shutting down Internet Explorer and then immediately shutting down.

As long as it does shut down and does not freeze up, you should not have to worry about it.

 

I get that occasionally, but it usually goes away on the next reboot.

 

There could be some update to Windows or another program that is delaying the shutdown.

 

 


peterweb wrote:

As long as it does shut down and does not freeze up, you should not have to worry about it.

 

I get that occasionally, but it usually goes away on the next reboot.

 

There could be some update to Windows or another program that is delaying the shutdown.

 

 


Hi peterweb

 

This is a Norton 2013 issue and appears to relate to a timing issue between the Windows Log Off process and the Smart Firewall:

 

http://community.norton.com/t5/Norton-360-2013-Norton-Internet/Smart-Firewall-Automatic-Program-Control-Off-issues/m-p/737126/highlight/true#M1907

 

NIS 2013 20-0-0-119 APC Off - Force Log Off.png

 

Your post above is the current solution though.

Strange thing is that everything IS on default with program control set to automatic.

Hi elsewhere,

 

Go to Event Viewer, then applications, then Microsoft, then Performance, and check for events with ID 100-109 (boot), or events with ID 200 to 209 (shutdown).

Then you will see what process(es), is slowing down Windows.

Since no program appears in the dimmed screen, it's a process or many, that causes the screen to appear because they exceed the default value of 12000μs.

Please report back.

 

Regards,  

I'm seeing a lot of "NIS" in the shut down delay log.

 

And your instruction is a little wonky.  It's Applications and services logs > Microsoft > Windows > Diagnostics-Performance > Operational.

WLP,

 

I was a bit on the hurry, that's why I gave the instructions in brief.

The essential is that you managed to find the logs.

If you're seeing many NIS entries like BASH driver or others, then I think that Symantec should update NIS drivers.

I have a similar issue, but only sometimes, with some NIS processes, Windows Font cache and other processes.

Maybe in the future, Microsoft will release a fix, because if you try manually to increase the value in the registry, let's say to 30000μs, the changes are not applied because of a known W7 issue: http://support.microsoft.com/kb/2549760

There is a hotfix available, via email, but many people reported that if you try to install it you get the message:

"This hotfix is not applicable to your computer".

 

Hope this helps,

 

Best regards,

I see occasional "NIS" listed or ccvhost listed.  However, as I said above, something is triggering the shutdown delay dialogue and I suspect is is Norton cause it only happened after the installation of the 2013 version.  I cannot isolate the incident cause it happen pretty much randomly but usually occurs after I close Internet Explorer and then immediately shut down the PC without waiting.

WLP,

 

I have 2 laptops with W7 HP 64-bit, I have NIS 2012 on one and NIS 2013 on the other.

It is strange, but on the laptop with NIS 2012 (i7 Intel, 8 GB DDR3 RAM), I have the dimmed screen "waiting for background.....", for 1 second or less,and on the other with NIS 2013, (Intel T9600 and 4 GB DDR2 RAM),, I have NOT that screen.

One partial solution, was to update my Nvidia driver to 306.97 WHQL, and now I see the message for 1 sec or less, before it was for 4-5 secs.

I think that both NIS versions have some common drivers, and depending on the OS configuration, you get this message which is only informational.

That's why I mentionned that some NIS drivers need to be updated by Symantec.

 

B/R,

 

Elsewhere -

 

Thanks for your intellectual insight on this problem. But may I ask, how does timing have anything to do with this issue? As I may be a new member to the forums, I would be best suited if you could enlighten me in the knowledge you have to offer.

 

Cheers, and remember to always follow the moral of my name.

This is really annoying especially on a SSD drive. :(

This problem seem to have been resolved in the latest 20.2 patch.

Glad to hear.

 

Keep an eye on things and let us know if it stays 'fixed'.