0

Yesterday, I installed the November Update for Windows 10 on my computer, and since then, I've been having issues with my shutdowns taking an abnormally long amount of time. When I shut down my computer, the screen will shut off about a minute later, but the machine itself remains powered on for several more minutes before completely shutting down.

When I try restarting, I run in to the same issue: the screen will shut off, but the machine will remain running for several minutes before the reboot begins. I've read online that this issue can be resolved by disabling fastboot, and although it has helped improve my shutdown and startup performance, the issue is still present. Prior to installing the November Update, I didn't have any issues with shutdown or reboot times. I am running the 64-bit Professional version of Windows 10.

What can I do to resolve the issue?

Update: I used the Media Creation Tool to reinstall Windows 10 while leaving my files and programs installed. I observed the reboot issue even during the reinstall, and it is still an issue now. I also tried turning off Intel Virtualization as suggested here.

Update 2: I also tried downgrading my IMEI driver as was suggested here as well as in several other locations.

DaveTheMinion
  • 5,528
  • Install the Win10 WPT (part of the SDK: https://t.co/et4jctp0uW) and run the following command: http://pastebin.com/RFRkuc81. Share the compressed file, so that I can take a look at it. – magicandre1981 Nov 14 '15 at 19:52
  • @magicandre1981 Just want to let you know that I've started the installation process and will post again with the results when they are ready. – DaveTheMinion Nov 14 '15 at 19:58
  • @magicandre1981 The output contained two ETL files, so I've included both of them in the archive file. - https://www.dropbox.com/s/33j84y3mvdpprio/shutdowntrace.7z?dl=0 – DaveTheMinion Nov 14 '15 at 20:33

2 Answers2

1

Generating a summary of the shutdown by running D:\>"C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\xperf.exe" -i shutdown_BASE+LATENCY+DISPATCHER+FILE_IO+FILENAME+DISK_IO_INIT_1.etl -o summary_shutdown.xml -a shutdown shows this:

enter image description here

Windows needs 38.4 seconds to shut down and the longest part is to shutdown the kernel (14 seconds).

But I also see that 3 services hang (Terminal Services, Defender and WLAN service). Try a different AV suite and stop TeamViewer before doing a shutdown.

But I can't see from the trace, that Windows takes several minutes to shutdown. Maybe this is a BIOS/UEFI issue. Look if there is a newer BIOS/UEFI.

magicandre1981
  • 98,168
  • 30
  • 181
  • 248
  • There is no new BIOS version available, so I'll give the service killing thing a try first. – DaveTheMinion Nov 15 '15 at 16:59
  • I tried the service-kill thing, but it didn't work. Do you have any other ideas? – DaveTheMinion Nov 16 '15 at 01:05
  • is hibernation/resume slow? – magicandre1981 Nov 16 '15 at 05:31
  • Hibernation is slow, but resuming does not seem to be a problem, as it came up almost instantly. – DaveTheMinion Nov 16 '15 at 10:53
  • ok, run this command to trace he slow hibernation. looks like you use the fastBoot which does a logoff + hibernate. My command traced the normal full shutdown: http://pastebin.com/Y632phPU – magicandre1981 Nov 16 '15 at 20:38
  • I have fast-boot turned off in the settings because if I have it turned on, it causes problems with the VPN server I host on my computer, so I'm not sure why it's acting like I have it enabled. Here's the archive file containing the results of the trace of the hibernation - https://www.dropbox.com/s/pmsugdk2ptd0t2u/HibernateTrace.7z?dl=0 – DaveTheMinion Nov 18 '15 at 04:07
  • ok, in the hibernation the device "USB\VID_0CF3&PID_311D\Alaska_Day_2006"/Qualcomm Atheros AR3012 Bluetooth 4.0 Adapter take 84 seconds to sleep. and this causes the slowdown. If if you don't use fastBoot I have no other idea. the normal shutdown is done under 1 minute. – magicandre1981 Nov 18 '15 at 05:32
  • Great! It worked! It looks like I'll have to disable my Bluetooth hardware whenever I'm not using it. Would you have any idea what "Alaska_Day_2006" is? – DaveTheMinion Nov 18 '15 at 10:29
  • This is the hardware ID and I read the value from the ETL – magicandre1981 Nov 18 '15 at 18:11
  • I get an error on the -i argument: xperf: error: shutdown_BASE+LATENCY+DISPATCHER+FILE_IO+FILENAME+DISK_IO_INIT_1.etl: Unknown (0x8000ffff). I assume I'm missing some trace files? – MrCalvin Jan 16 '22 at 10:42
  • @MrCalvin maybe the file is damaged. capture a new one or try to open the etl in WPA and apply the FullBoot.Shutdown.wpaprofile to see also details about shutdown. – magicandre1981 Jan 16 '22 at 11:04
  • I just installed the Performance- and Accessment Toolkit, but no .etl files seem to be installed (at least not in the program folder). Where does these .etl files come from? – MrCalvin Jan 16 '22 at 11:45
  • 1
    you need to capture the shutdown ETL first wit xbootmgr.exe or WPRUI.exe @MrCalvin – magicandre1981 Jan 16 '22 at 16:34
0

Try deleting all the files under:

C:\Windows\Prefetch

And just leave Layout.ini, then reboot. The process might take some time.

After that, when the system has started again, try to shut down.

Insane
  • 2,902
Flavio Montagner
  • 1