New
#11
Noel, hard to think of not doing anything on the computer until 30 minutes after an update.
Hans L
Noel, hard to think of not doing anything on the computer until 30 minutes after an update.
Hans L
There's only two things I definitely avoid doing if possible during that period -
1) Shutdown/restart/reboot
2) System maintenance tasks (CHKDSK/SFC/Defrag/etc)
Otherwise, I just tend to get on with what I'm doing, and accept the temporary slowdown that occurs.
To be honest, I don't know
It seems to me to make sense to allow one set of updates to totally complete before attempting the next.
In theory, Windows will suspend whatever it's doing gracefully - but there are any number of external factors that could make it stumble.
Generally, anything to do with TrustedInstaller is WU-related. There are a couple of .NET optimisation processes that tend to continue for quite a while as well.
No - always look in the Processes list.
TrustedInstaller service runs most of the time anyhow.
If I remember right, the .NET routines are something like 'clr NET optimisation'