I’m looking at the Autoruns one right now and “Gather Network Info” is highlighted in redĪutoruns is excellent but I prefer TaskSchedulerView‘s handling of ‘Properties’ for each entry. Similarly, I ran Autoruns and Process Monitor after the original issue happened and can share the logs if need be. I did save a log if you’d like to go over it. The issue didn’t happen again when I logged in today. It looks like the only “Run on Logon” entry that was last run yesterday is something called “Logon” that was published by Microsoft.
Tasks which are triggered at ‘logon’ are the most likely cause of the 2 command prompt windows which briefly appear, even though the Hidden column ( c) shows there should be no user interface.įor more info you can *right*-click on entries and choose Properties (or use ALT+Enter).
Scroll across to the Run On Logon column ( b). When TaskSchedulerView opens, click on the Last Run column header ( a) once or twice to sort the entries so the latest run tasks appear at the top of the list.ģ. *Right*-click on TaskSchedulerView.exe and choose Run as administrator then accept the UAC (User Account Control) prompt that appears by clicking on the Yes button.Ģ.
Perhaps the easiest way of checking is to download and unzip Nir Sofer’s small, free and portable TaskSchedulerView (making sure to download the ‘bitness’ version that matches the ‘bitness’ of your OS… most likely 64-bit).ġ. The other is almost certainly one of the many other scheduled tasks that have ‘logon’ as a trigger.Īs scheduled tasks, they do not appear as startup items in Task Manager. One of them is probably the GatherNetworkInfo script (C:\Windows\System32\gathernetworkinfo.vbs), triggered as a scheduled task at every ‘logon’.
0 kommentar(er)
