Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Windows shutdown hanging for long periods

2 Weeks Ago   #11
F22 Simpilot

Windows 7 Ultimate x64
 
 

In the search box enter dxdiag and see if there are any errors in there and in the 64 bit version.

Just to clarify. This started to happen once you connected the new screen? And it only happens with HDMI and not VGA?
My System SpecsSystem Spec
.
2 Weeks Ago   #12
Davidk101

windows 7 home premium 64bit
 
 

F22 simpilot,
1. I ran the 64bit dxdiag as requested, 2 screenshots of the results attached: the main system result, and for the display. All the tabs had a no problem reported advice at the bottom, but I've omitted the sound tabs because there's no apparent issue with them.
2. Yes, the long hang times on shutdown were noticed when I changed the display, but they happened for both VGA and HDMI. It was just that the hang time for HDMI was more than twice the time noted for VGA. My apologies if that wasn't clear in my earlier posts about the problem.


So, thru this 'test and suggest' cycle, it seems clear that the shutdown 'blue screen' hang time reflects a timeout, or a series of them, in succession. And we haven't identified just why the HDMI connection made the shutdown time so much longer than with a VGA connection: the only difference is the presence or absence of a cable on one connector: no other change made to switch between one mode or the other.



I've been working on getting the shutdown times consistently short or normal for VGA, and when that seems to have some consistency, I'll give the HDMI connection to the display another shot. today.



I think everything suggested has helped, but the thing that made the most difference was setting windows update to "never". Which doesn't bother me at all - we are now past the extended support date and the only thing that's still coming out monthly is the malware removal tool; and I usually manually checked updates regularly 2 days after patch tuesday. Why 2days later? about 3-4 years ago I used to do it on the release night and one month a particular KB item borked the PC windows license key: it was withdrawn within 2 days after everyone screamed at MS, but for the early adopters, it was pain establishing which KB did it, and then reversing it out. So my manual update check habit changed . . . .
Altho why an update check should be being made during a routine windows shutdown process - when there are other quite specific things that do that - is mystifying.


Attached Thumbnails
Windows shutdown hanging  for long periods-dxdiag_1-14-may-20.jpg   Windows shutdown hanging  for long periods-dxdiag_2-14-may-20.jpg  
My System SpecsSystem Spec
2 Weeks Ago   #13
F22 Simpilot

Windows 7 Ultimate x64
 
 

I wanted you to check the 32 bit version of dxdiag as well as the 64 bit version.

Try this once, it will work in 7. Turn On AutoEndTasks at Restart, Shut down, or Sign out of Windows 10 | Tutorials


Go to Control Panel | Administrative Tools | Event Viewer and open Windows logs. Right click the system and application logs and save all events as and zip those two files. Upload here.
My System SpecsSystem Spec
.

2 Weeks Ago   #14
Davidk101

windows 7 home premium 64bit
 
 

F22,
I've run the 32bit dxdiag as requested, screenshot attached, no change in results from the 64bit version.


That AutoEndTasks item looks interesting. I've:
- exported a precautionary copy of the registry - all 1.081Gb of it !!
- taken a screenshot of the registry control/desktop item that is discussed in the tutorial link you supplied, attached. No entry at all for this AutoEndTasks variable

- downloaded the "Turn_On_AutoEndTasks_for_all_users.reg" file
but I have 2 questions about this before I go ahead.

q1 You said "it will work in 7". But tutorial is all about win10, and the action part - step 6 - talks about double click to merge it. It's the term merge that makes me edgy. I understand that to mean executing the file will insert an entry for AutoEndTasks=1 in the registry here, save and exit. Can you clarify please.
q2 this looks like an essential item, so why isn't it in the system and on as a default? Or maybe MS has not ever said?



System and application logs: zipped and attached.


Attached Thumbnails
Windows shutdown hanging  for long periods-dxdiag-32bit-14-may.jpg   Windows shutdown hanging  for long periods-registry_-autoendtasks.jpg  
Attached Files
File Type: zip application log.zip (2.30 MB, 1 views)
File Type: zip system log.zip (3.43 MB, 2 views)
My System SpecsSystem Spec
2 Weeks Ago   #15
Megahertz07

Windows 7 HP 64
 
 

Once I question why my computer was taking so long (20 sec) to shut down.
After tracking shutdown I found that it was due to antivirus (Avira).
Why it takes so long to shut down?

You didn't mentioned your antivirus but some can be set to do a scan of critical files on shut down.
Have a look at your antivirus settings.
My System SpecsSystem Spec
2 Weeks Ago   #16
Davidk101

windows 7 home premium 64bit
 
 

Mhz7,
I run the AVG Internet security suite. It has 2 update settings for itself: 1 for virus definitions, and 1 for the application itself. screenshot attached. No other update settings apparent. Updates usually happen as part of startup. Which means I generally wait several minutes for all that to get done and out of the way.

BUT
Normally I notice that a software update is available thru a notification balloon on the program open page. However I now see that the app has been set for auto update - possibly as a result of recent update, on 4 may (the app update is dated 4 may and I would have downloaded it a day later). So I changed it to "ask when an update is available". We'll see how that pans out.
Not sure that would affect the shutdown process??



My normal shut down process is to close all the working apps (email, browser, etc), and then click the shutdown button. With a pretty fast cpu (3.7ghz), 8gb of RAM and a 250gb SSD for the C drive closing any background bits should not take that long: typically about 7-10 sec from button press to blue screen, including the black closing programs screen. From that point, the differences I have been experiencing are all about just how the new screen is connected to the PC motherboard - by VGA cable or HDMI.


As to shutdowns when HDMI connected to the screen after the various change suggestion you'all have made, yesterday I shutdown the VGA connection, plugged the HDMI cable into the screen and proceeded to test (boot, work, close), as indicated in the prior post. I did 4 shutdowns, spaced thru the morning, afternoon and evening. Timed each with particular reference to the period the blue shutdown screen was displayed. Happily surprised at the data: at 1030, shutdown took 30 sec, at 1155 it took 25 sec, at 1750 20 sec, and at 2115, 25 sec.


With the pandemic, the local broadband networks have been getting hammered all day, not just in the evenings, so network access might explain that sort of variability. Which gets to the question of what might be doing that: your AV query very relevant, answer at the top of this post. F22's data may also help that: not so much which process it is, but running the AutoEndTask to close whatever it is. Still waiting on his reply re my concerns . . .


Attached Thumbnails
Windows shutdown hanging  for long periods-avg-update-settings-15-may-20.jpg  
My System SpecsSystem Spec
2 Weeks Ago   #17
F22 Simpilot

Windows 7 Ultimate x64
 
 

Okay, I'm seeing some application errors for AVG. As a test completely uninstall AVG. Uninstalling AVG Antivirus using AVG Clear | AVG Support

To answer your question. The registry key doesn't exist by default in Windows 7. I have added it myself to my computer's with no harm. Yes, it adds the values to the registry. If you want to see where you can open the .reg file with notepad or Notepad ++ and see.

You can create a system restore point in lieu of a registry backup.
My System SpecsSystem Spec
.
2 Weeks Ago   #18
Davidk101

windows 7 home premium 64bit
 
 

F22,
Thanks.
So, re AVG, what I think you want me to do is:
- uninstall
- cleanup the system and registry with cclean or similar
- reboot
- reinstall AVG (because I'm twitchy about being on the net without this sort of security security blanket).
- re-test as needed.
???


Re AutoEndTasks, the file I cited is the right one??
My System SpecsSystem Spec
2 Weeks Ago   #19
torchwood

W7 home premium 32bit/W7HP 64bit/w10 tp insider ring
 
 

Hi

had a look at the event logs,

You appear to have a "business" type setup with NAS
its creating problems all over the place

please give us your set-up, and are you dual booting?

please run the built in MS disk clean-up tool, less to look at



Roy
My System SpecsSystem Spec
2 Weeks Ago   #20
Davidk101

windows 7 home premium 64bit
 
 

Torchwood,
I would not call it a 'business' setup, but it's a way for 3 PC's to connect to the internet, and and some off-PC network storage they all might use, without specific windows peering. This configuration allows me to plug-n-replace capacity as needed once the stores have been mapped into explorer.
And that map into explorer need is one of the major reasons I abandoned a win10 upgrade (tried it 3 times!!) that I mentioned really early in this thread.
The home LAN configuration drawing attached.
The machine that's been hanging in the 'blue page' shutdown phase is the desktop in that drawing.


Attached Thumbnails
Windows shutdown hanging  for long periods-home-lan-20191201.jpg  
My System SpecsSystem Spec
Reply

Thread Tools




Similar help and support threads
Thread Forum
Shutdown taking a very long time (6+ minutes), hanging on group policy
Windows Domain (Windows 2012 r2 DC) environment Windows 7 64-bit client computer in question I enabled the Verbose key in regedit so I can see what process shutdown.exe is hanging on, and it gets stuck, for 6+ minutes, on "Shutting down Group Policy Client service...". Could someone point me...
General Discussion
BSOD Random, all of a sudden after long periods of being on
Hey everyone, Hopefully you guys can help with some in sight. I used an online bsod reader osronline but it didn't really help. I tried updating my mobo driver because it originally said CPU issue/Mobo. It happens at random intervals doing different things. I first noticed it having twitch up...
BSOD Help and Support
BSODs during long periods of activity, 4-5 hours.
I just started having bsods on a brand new harddrive (and 8 gb ram) that replaced a bad one. Recently, the bsods happen randomly after about 15-30 minutes of activity and have changed to just black screens, then restarting the boot process.
BSOD Help and Support
W7 system: suddenly long boots and periods of ultra slow performance
I have a W7 Professional system running an i7. It was working ok until yesterday. Started by noticing the sound system had stopped working. There was a red X through the speaker icon in the lower right corner. So I rebooted. It went into a chksdk mode (that made me nervous) and then booted but...
Performance & Maintenance
Frequent BSOD's after long periods of standby or sleep
Even since I purchased my laptop, I've been getting BSOD's when I go to "wake up" my laptop by either opening it or moving the mouse. This occurs usually after it has been in "sleep" mode due to closing the notebook, or letting it sit in standby for a while. I've updated drivers and BIOS, and the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 09:44.
Twitter Facebook