Which of these scenarios is worse? A that takes an inordinate amount of time to:
- Start up
- Shut ?
Permesso, I guess that’s like asking which is worse: a slow a capricious ? Per mezzo di other words, both equally suck and one isn’t really any less annoying than the other.
But this is the thing: When my takes ages to shutdown it tempts me to my hold per mezzo di the power button to force chiuso the power.
I don’t want to wait for the to turn chiuso – when I’m done with my PC for the day it shouldn’t merely acquiesce to my shutdown request; the contrary it should execute my commands with alacrity and turn itself chiuso per mezzo di a matter of seconds.
If your PC chronically founders when you tell it to power then we need to find out why it founders. Is there an easy way to identify the programs processes that are making a speedy shutdown ?
Identifying the culprit
One of the most reliable means of identifying aberrant processes is using a free toolkit from Microsoft called the Windows Toolkit which is part of a large software package known as the Windows Software Developer’s Kit (SDK).
I know “Software Developer’s Kit” may sound grandiloquent even daunting, especially if you’eroe not a software developer; however, we’eroe not going to touch a single bit of code.
While it’s true that Windows developers use the SDK to compile and code; today we’eroe only going to analyze some giorno values so we can figure out what’s bothering your hapless .
Installing the SDK
First we need to download the right SDK.
There are different versions for Windows 7, Windows 8 and Windows 8.1 so make sure you grab version that matches your operating system.
Since I’m running Windows 8.1, I’ll demonstration how I got this thing going my OS. Click gara open the executable named sdksetup.exe and keep the default installation location.
You might notice the setup wizard requires a glut of space; at one and a half gigs this thing looks like a beast.
Fortunately the third setup screen you’ll have the option to disable superfluous items. I’ll show you that a little later.
the next screen, opt out of the Customer Experience Improvement Program.
Microsoft has enough information about me, anonymous not, thus I don’t feel compelled to give up anything else.
Accept the license agreement…
The Software Development Kit comes chock full with a bunch of software libraries that aren’t really germane to what we’eroe trying to do; therefore, go ahead and un-check everything except the Windows Toolkit.
Per mezzo di the right pane perso you’ll see it includes:
- Windows Recorder
- Windows Analyzer
That second guy there, Windows Analyzer (WPA), is our scontrino to shutdown speediness. I’m going to show you how to use WPA, and his cousin Xbootmgr, to get to the bottom of the problem.
Click Install and you’ll be finished per mezzo di 60 seconds.
Alright, now we’eroe done with the boring stuff.
Press Windows Key + x + a to gara open a Command prompt with Administrative privileges and navigate to the Windows Toolkit folder.
Type this per mezzo di:
cd cd "Program Files (x86)Windows Kits8.1Windows Performance Toolkit"
Alright now save the changes from any documents, spreadsheets projects you were working and paste per mezzo di the following cryptic command:
xbootmgr -trace shutdown -traceFlags BASE+DIAG+LATENCY -noPrepReboot
This tells Windows to trace the shutdown process and to do it immediately after you press the Enter key.
You should see a starting trace dialog box flash the screen for an instant before your reboots itself.
When it returns you’ll see something like this:
The trace you are capturing "C:Program Files (x86)Windows Kits8.1Windows Performance Toolkitshutdown_BASE+DIAG+LATENCY_1.etl" may contain personally identifiable information
That’s good as it denotes the trace completed successfully.
Go ahead and gara open the Windows Toolkit folder and then drag the trace file, which should be named shutdown_BASE+DIAG+LATENCY_1.etl, over the Windows Analyzer file named wpa.exe.
This slick move forces the Windows Analyzer to load all the trace giorno from the .ETL capture.
When it loads you should see a few items per mezzo di the Graph Explorer sitting per mezzo di the left pane perso:
- System Activity
- Computation analytics
- Storage statistics
- Memory facts
- Power giorno points
I know this sounds crazy but you don’t need a Masters per mezzo di Statistics to analyze the giorno here.
Let me walk you through how easy it is to find the processes that could be slowing your shutdowns…
Per mezzo di the Graph Explorer, click gara open Storage, expand Disk Usage and double-click Service Time by Process, Path Name, Stack.
A bunch of giorno will take over your screen. Let me interruzione it a little:
We can divide the right pane perso into two sections:
The half lists your system processes and displays a graph that lists each process by how long it took to close (the horizontal axis) and how much memory was consumed at each time interval (the vertical axis).
The bottom half shows all your processes, the file path to the process file and the all important Disk Service Time column.
I want you to centro this bottom pane perso.
The Disk Service Time column shows time values per mezzo di millionths of a second, Microseconds.
So to see how long a particular process took to terminate just divide it by 1 million… just kick over the decimal point 6 places to the left to get seconds.
Since the column is Disk Service Time column is sorted with the longest close times listed first, I can start marching the list to see the slowest processes.
Per mezzo di my example, I can see something called MsMpEng.exe took 257,250 microseconds to close. That comes out to .2 seconds, which is paltry I know – but that’s besides the point. I just wanted you to see where to go when you need to hunt those slow processes.
If you click the little drop arrow under the process name you’ll see even more giorno such as the human friendly name of the process per mezzo di the file path. Here, it looks like Windows Defender was nibbling 56,254 microseconds of close time.
When you locate the offending process you can Google around to see if you need it and can then disable uninstall it.
The Bottom Line
If your takes forever to shutdown then we use a broad stroke and start indiscriminately removing software we can try a focused approach using the Windows Analyzer.
It takes a little more work than uninstalling random files you think are responsible for the problem but it’ll give you value insights and empirical giorno to support your assumptions and justify your actions.
The Windows Analyzer isn’t perfect and can be to decipher; however, if you give it a chance and it’ll reward you by helping you identify processes which are slowing your shutdowns.
If you have any questions please share per mezzo di the comments!