UM.MSI question

WinXP Home, SP2

I removed a demo program called R-Drive Image, a backup program.

When i rebooted, I get the Windows Installer frame and it tries to install
(update?) something called UM.MSI. I dont have an update or the original of
this program.

This happens everytime i have to reboot or boot up.

I dont have an update disk.

A google didnt turn up anything usefull.

Any help?
savagcl

 

Hi PeteC,

More info first. Apparently this has something to do with Sonic Update Manager,
Still looking tho.

I dont recognize any thing like Sonic in the Starter utility.
Here is the "Starter" results.

Clif

 

More info:

Its tied into an InstallShield (in the PF\common files folder) and relates to the
ISUSPM in the Starter jpg attached in previous msg.

Just what application controls it, i dont know. I dont know where it came from
but its been there a long time.

savagcl

 

Youre ahead of me, PeteC.
Was just going to post:

http://startup.iamnotageek.com/srch-ISUSPM.exe.html

and here

http://www.liutilities.com/products/wintaskspro/processlibrary/issch/


ISUSPM.exe
Description:
InstallShield Update Service related; Automatically searches for and performs any updates to the software. Not required.

issch - issch.exe - Process Information
Process File: issch or issch.exe
Process Name: InstallShield Update Service

Description:
issch.exe is an update service relating to the InstallShield utility which keeps this software up to date. This program is non-essential process to the running of the system, but should not be terminated unless suspected to be causing problems.

 

OK, I disabled it in msconfig and the problem has gone away but i have to
wonder, at what price?

Did this kill the windows auto-update?

savagcl

 

No , this is unrelated to windows update.
Windows automatic update shows up as a service as
C:\WINDOWS\System32\svchost.exe -k netsvcs

 

i ahve the same problem and i dont know how to disable it in msconfig. Can you please show me step by step how to disable it anyone. Thank-you

 

Just use code stuff starter as listed above.
Remove the check.
It will not only remove the MSCONFIG single registry entry , but it will check for and correct any dependencies.
It is a far better and safer and more thorough way to control a bad startup. IN fact, you can even permanently delete them once you confirm they are not needed using code stuff starter.