Testing unsecapp.exe

[CJW]

For years now I've had this process start-up seconds after my computer boots.
I've read A LOT of posts & explanations stating this is for WMI Asynchronous Callbacks, that it resides in 3 folders (C:\Windows\System32\wbem, C:\Windows\winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7601.17514_none_177a088436382a34 & C:\Windows\winsxs\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_6.1.7600.16385_none_1548f4bc3949a69a) & that it could also be a trojan/virus in disguise. I've done searches & virus checks over the years & never had a problem finding the file on my comfuser/having it show up as a trojan/virus.

The question I've not been able to answer is just WHO is this calling back to & WHAT is being sent to them?

I don't think it's truly needed because whenever I boot my comfuser, the 1st thing I do is open Task Manager (ctrl+shift+esc), right-click the process & select 'End Process Tree'. Then close Task Manager & go along my computing. After doing this, I've NEVER had any problems playing games, using programs or even searching through the web. So why do we have this if, once I end the process, nothing ever goes arwy?

I'm WAS going to do a test by going into Services.msc & disabling the process there to see just what would happen, but guess what? There IS no unsecapp entry listed. So I still have to wonder, Why do we need this on our comfusers?

 

[torchwood]

Hi CJW,
the SXS entries relate to Updating and Validation.
They are performed on EVERY boot, and this is reported in the event manager.
So the recipient is MS- product id detail & comp hardware setup data
(dissabling the Bits service may? stop these)

the WBEM ones are all to do with your Network connections, Ethernet & Wifi.
These i assume are your ISP provider.

Playing with WMI can easily stop a number of system reporting tools to fail.


Roy