Turns out that “garbage” won’t work without “goop”. Turns out that when you installed “garbage”, it also installed a copy of the helper API called “goop” (or it saw it was already there and skipped installing it). What are you going to tell your boss? You look at the clock and realize you’re in trouble. But instead of being greeted by your typical screen, you get a huge box on the screen that explains in some cryptic nonsense that “garbage” failed to start. You have to get your work done within the hour. So tomorrow, you start your day and launch “garbage”.
Now the program called “junk” is completely removed.īut, it turns out that you also have a program called “garbage” that you use every day.
Now you decide to use “crash” to remove the program called “junk” and it removed all the files that junk installed including the helper API called “goop”. Perhaps the developer of “crash” actually took the time to create a database of every program in the world, and that database includes a list of every file and API that is installed by every program. And you used a third party application called “crash” to remove old titles you no longer used. The problem is that even if they actually programmed definitions for every individual software title, and what each software title added to the system, they are still prone to breaking something.įor example, let’s say a hypothetical program called “junk” installed helper API software called “goop”. I couldn’t even begin to count the number of systems I’ve had to fix for people where the last thing they did was use a 3rd party utility to either clean their system or remove an application.
3rd party uninstallers have always been problematic on any platform.
0 kommentar(er)
