[Feature Request]Add Autoruns Module

[kidimbwi]

TaskExplorer is looking good, great work.

i'd like to suggest an addition to its existing features; an autoruns module. currently to manage autoruns exhaustively a user will turn to Autoruns from sysinternals which is an excellent piece of software. would you consider adding Autoruns like functionality to TaskExplorer ? this way we can manage autorun entries and the processes and services that they start from a single application. this would be convenient for users since TaskExplorer would be a one stop shop for processes, services and autoruns monitoring and management.

hopefully you'll consider this feature and implement it into future versions of TaskExplorer. keep up the good work on it.

[DavidXanatos]

That is indeed a useful feature, and it fits well in the scope of the project, although not with all that the sysinternals tool does. A list of codecs or explorer shell extensions is a bit offtopic, but all the autorun locations, registry and autostart folders, plus may be task schedule should be all one needs normally?

[kidimbwi]

That is indeed a useful feature, and it fits well in the scope of the project,

glad you agree with my suggestion.

although not with all that the sysinternals tool does. A list of codecs or explorer shell extensions is a bit offtopic,

agreed

but all the autorun locations, registry and autostart folders, plus may be task schedule should be all one needs normally?

i'd add drivers to that list as it'd be informative to see which drivers(along with any associated processes) are launched at system start.

[DavidXanatos]

i'd add drivers to that list as it'd be informative to see which drivers(along with any associated processes) are launched at system start.

Technically you already have drivers, they are listed together with the services in the service tab.

All the orange once are drivers. The reason is that in Windows NT services and drivers are handled by the same mechanisms

[kidimbwi]

hadn't noticed that, thank you for pointing it out.

however that view shows all drivers in the system both running and stopped. in an autoruns module, only drivers that are started at boot would be visible. this would give a user information on what drivers are being loaded at boot. a user would still use the services tab to view/manage all drivers on a system.