Task Host Window

It's a good policy to shutdown the PC 'periodically'.

as seen here:
net statistics server
Server Statistics for \\___PC7

Statistics since 3/15/2018 4:10:47

Sessions accepted

..... .....
I last rebooted 3/15 (MS update applied), but frequently I let it run/hibernate for a week or two.

REBOOT reorgs memory, refreshes all programs and services. It also
  • recycles thru BIOS POST to discover new issues (if any) and
  • allows TMP files to be cleaned-up
  • frees any Zombie Ports not closed
  • interfaces with CHKDSK if so necessary
We've all experienced "what the heck is going on now - - guess I'll just reboot". Why wait to experience issues when you are busy and need your system when you can choose the time that fits your schedule? I use the same reasoning on MS Updates -- I'll run them when I am ready to, not on some arbitrary Scheduled Task timer interval.
 
If that were true, it would have been in a condition that would have allowed the T.H. to kill it :)
Um, perhaps 'should' instead of 'would'?
Granted BITS is visible in Task Manager, but I'm inclined to think there may have been a 'wait' in place which made the predecessor unnoticeable - and not declared except as " Microsoft\Windows\DeviceDirectoryClient\RegisterUserDevice " which I could not identify or define.
ps: I cold boot nightly.
 
Naa -- I cant count, BITS is shown in the third column
Code:
svchost.exe                    652 Appinfo, BITS, Browser, EapHost, gpsvc,
                                   IKEEXT, LanmanServer, MMCSS, ProfSvc,
                                   Schedule, seclogon, SENS, ShellHWDetection,
                                   Themes, wercplsupport, Winmgmt, wuauserv
 
Thanks. I'm in Windows 10 Pro (64) and my BITS is a standalone (PID 3816) scvhost task. There are 16 separate PIDs in the netsvcs group. I'm guessing that you are still Win7 Pro?

I remember checking this while I was hung... zeroes except 4204k of memory (just sitting like a lump).... Waiting for Godot
 
Back