Anyway no... it was unescapp.exe.... I terminated it in my task manager but then it started up again when I wasn't looking.... so I cut that fucker out and pasted on my desktop.... I'l leave it there until I figure out what to do with it.
Its an important process. If you keep killing it you're going to have problems with a lot of programs. It shouldn't be pegging your cpu for over 50% though. Make sure its sitting in system 32 and do a sfc /scannow in command line. If its not in system32 you might have a virus.
Makes no difference to me... Wether its a bit coin miner or a vital system process.... anything that leeches 50% of my resources (and tries to hide while doing it) has no business being in my Rig.
It doesn't try to hide, its right there in the details tab. If you have home edition of windows it shouldn't be doing much and at most taking a few kilobits of memory and shouldn't even be pegging the cpu. Killing the process instead of finding out the cause is really a bad idea.
LoL... not after I found what it is doing... and yeah it was definitely hiding. I had to toggle the option that shows processes from all users to find the bastard.
You mean the more details button? Task manager by default shows all users/systems that are running a process. Again, if you had a core windows process pegging your cpu to that extreme then there's something else going on, most likely malware or a virus. Unsecapp.exe is a harmless process that generally just sits idle. Most of its WMI functions are almost completely used in pro and enterprise windows version.
Killing a legit windows process that runs WMI will 100% lead to other problems down the line on your windows. Most likely a lot of blue screens and some programs just not working correctly when they need to run off WMI.