View Single Post
  #20  
Old 01-29-2020, 02:08
Stingered Stingered is offline
Friend
 
Join Date: Dec 2017
Posts: 123
Rept. Given: 0
Rept. Rcvd 1 Time in 1 Post
Thanks Given: 151
Thanks Rcvd at 77 Times in 41 Posts
Stingered Reputation: 2
Quote:
Originally Posted by DavidXanatos View Post
I have a small inquiry for you guys...

What features would you like to see in the next builds?


I was thinking about the ability to set priorities and CPU affinities persistently, i.e. the tool would remember it on an file name basis and whenever a process is seen with one of the preset paths (or only exe name, in the end probably a wildcard path really) its priorities and stuff will get adjusted accordingly.

I was also thinking about adding an option to perpetually kill processes on the same basis, when one gets seen it will get killed.
thinking here about typical telemetry processes like vctip.exe (VS2017/2019), software_reporter_tool.exe (Chrome), NvTelemetryContainer (NVidia) etc....


With regard to not allowing processes to start I could enforce that using the driver so that the process never goes past created suspended. But is that overkill?
Is that the right thing for a task manager or should that go into some separate HIPS tool? I don't want to cram thematically unrelated features together, but well not allowing processes to start is still in the scope of a process manager.

What do you think?
Is useful to have option for suspend process?
Reply With Quote