Freeburne wrote:

I was trying to solve another problem when I discovered that.

1) A task for SlimCleanerPlus was there.
I deleted the task but am unable to uninstall the files.
Revouninstaller (free) does not find it.

I see no uninstall for SlimCleanerPlus.

How do I uninstall it ? just delete ?

C:\Documents and Settings\My LENOVO\Local
Settings\Temp\SlimCleanerPlus_en-US_x86_Silent.exe
C:\Documents and Settings\My LENOVO\Local
Settings\Temp\SIOUT24061234\SlimCleanerPlus_en-US_x86.msi
C:\Program Files\Common Files\Ahead\NAS\nas\presets\Slime.nvp

2) other tasks

DriverNavigator Scheduled Scan

PMTask

Microsoft Windows End of Service Notification logOn

Microsoft Windows End of Service Notification monthly

Should / can these Tasks be deleted ?
How to uninstall ?

You don't want to delete "SlimCleanerPlus_en-US_x86.msi"
as it's possible to use msiexec and a file like that, to
remove an installation. Once you delete that file, you
will *destroy* the automation involved. If the MSI is
missing, AppWiz will behave like a scalded cat.

https://superuser.com/questions/2935...e-with-msiexec

https://stackoverflow.com/questions/...055933#1055933

If I was doing such surgery, first I'd backup C: , and then
I'd try a few things. If I botched a command, I would restore
from backup.

Some program folders include things with names like "uninst"
or similar. But these might still have a .msi dependency, if
indeed the original installation used a .msi file.

There are multiple ways of installing software, and some
installers amount to no more than unpacking a tarball.
Since you've received a "hint" in this case, by the presence
of an actual .msi file, you know which method is being used,
and this will reduce the amount of research needed.

Badly designed installers, can barely remove the file set
they install. Removing registry entries or Scheduled Tasks
or Startup Items, who really knows whether those got handled.
But once most of the file set is removed, that tends to
neuter the other stuff, and the only remaining side effect
might be erroneous entries being added to EventVwr all the time.

I am philosophically opposed to doing uninstalls this way...
except in cases where you have good evidence that a single
command will do a thorough job. For example, what if
a procedure you use, doesn't update Add/Remove status properly ?
I think the .msi method is pretty good this way, but there
are lots of things that could go wrong.

HTH,
Paul