this post was submitted on 11 Feb 2024
40 points (100.0% liked)
Technology
37720 readers
408 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Most likely an app updater written by someone who is too lazy to make their updater hidden.
As others suggested, look in task scheduler, but make sure you run it elevated. Focus on any updater that's calling an app from a bat file, and move out from there.
I feel seen!!
Honestly it can be really tricky to keep that crap from popping up and if the guy that wrote the install did it all dirty and didn't hide his windows, calling a boatload of processes, it can be truly difficult for the guy that writes the updater to keep everything hidden.
I've been there.
Guilty as charged. At least in my case the updater is always started by the app, and when it's done it starts the app again