On 2019-11-19 4:01 p.m., Paul wrote:
Rene Lamontagne wrote:
About 5 or 6 months ago running the then current Windows 10 ver 1903
my system used to do a shutdown in 6 or 7 seconds.
Now I find it taking about 19 to 26 seconds, Faststart is disabled and
so is hibernation and Hiberfil is uninstalled.
Everything is disabled in Task manager-startup and I have no other
programs running in the background.
Any hints, or as Paul would say breadcrumbs for me to look at.
This is not a great hardship but makes me wonder what is the cause.

Rene


Process Monitor from Sysinternals, can capture both
a shutdown and a startup session.

You could change the backing store to disk rather than RAM.
Select the option to capture the next startup. Leave the
tool running and shut down. Both the shut down and the
startup should be captured. Then have a look at the
ProcMon events, for the problem.


Never really having used ProcMon before I am struggling migthily to
learn how it works, I have set it to store to a disk file and have set
it to capture events which when I shutdown and restart with it running I
do get a file called in my case stop.pml on the desktop which covers
about 2 minutes and about 43,00 files. Is this what I need and what
should I be looking for



Note that some events on a computer, resist debugging.
When I discovered that Windows 10 was initializing RAM
somehow at startup, and taking 20 seconds to do so,
there was a "gap" in the trace. No activity for 20 seconds
in terms of things starting or stopping. I had to surmise
a compute-bound activity was happening (no disk access).
And perhaps, an activity proportional to the size of
the system RAM. A small VM for example, would start a
lot faster.

So while ProcMon can give you a trace, it's not gdb or
Windbg and doesn't trace at that level. And some activities
will remain elusive and require conjecture.

Â*Â* Paul


Do I need to look for some kind of shutdown event or some specific time
frame in seconds?

Rene