The InstallShield Update Manager (ISUM) had somehow installed itself on my system. It would sometimes appear in my system tray, and would also pop up messages telling me that I needed to install updates. I wanted it gone.
I ran a search and found a Flexera Software webpage that offered a link to a SoftwareManagerUninstall.exe program. I ran that uninstaller and was greeted with a question: "Are you sure you want to remove the FLEXnet Connect Software Manager? Odd question; I hadn't installed any such thing. Logically, though, it couldn't hurt, so I said sure, do it. A moment later, it said the software manager had been removed from my system. I was glad for that. But the ISUM icon was still in my system tray, and when I double-clicked on it, it informed me that it was currently updating two important programs, namely, ON-OFF Charge B10.0427.1, which I had never heard of, and the InstallSheild Update Manager itself. Marvelous.
The idea seemed to be that there were different versions of the ISUM, depending on which program installed it on my system, which would explain why various sites pointing me toward specific registry entries didn't work for me -- and I couldn't just delete all references to InstallShield, because all kinds of programs used that as their installer. I went into Control Panel > Programs and Features to verify that, as I recalled, the InstallShield Update Manager was not listed there. With the aid of a thread, I found that C:\Program Files\Common Files\InstallShield\UpdateService\ISUSPM.exe was the operative program -- running the Update Manager, I mean -- but somebody said that deleting that wouldn't solve the problem; it would just be reinstalled by the related registry entries at some point. There was the option to set it not to check for updates, but somebody in that thread said it would then pop up to remind me that I had set it to not remind me.
I ran a better search and got a suggestion to use Autoruns instead of Start > Run > msconfig to identify ISUM as a starting program and untick it. But before trying the Autoruns/msconfig route, I did a Ctrl-F in Start > Run > regedit for ISUSPM.exe. This gave me the idea to delete the C:\Program Files\Common Files\InstallShield\UpdateService folder and then run Glary Registry Repair to wipe out references to it. Thanks to previous tweaks (see links above), I was already running as administrator with about as much freedom as I could persuade Win7 to give me, so I figured the only thing left to do, before I could delete that folder, would be to use my right-click Lockhunter option to free it up in Windows Explorer. That didn't work, though, so I tried deleting the contents of C:\Program Files\Common Files\InstallShield\UpdateService individually. Everything went except issch.exe. For that, I got an error:
File In UseSo I went into Task Manager (Ctrl-Alt-Del) > Processes tab, highlighted issch.exe, and clicked End Process. That took care of that. (When I tried this on another machine, I also had to use Task Manager to shut down agent.exe, ISUSPM.exe, and one or two other processes.) Then I closed Task Manager. Now I could get rid of the folder. I ran Glary. I was watching one of the references to ISUSPM.exe in regedit, and it did not change when Glary was done, so I rebooted, ran Glary again, and did another search in regedit for ISUSPM.exe. That reference was still there; so, maybe, were others. I wasn't sure what to do about that, so I left it alone for a while.
The action can't be completed because the file is open in InstallShield Update Service Scheduler.
Nothing further emerged, so I left things as they were. The InstallShield Update Manager seemed to be gone. There was still an InstallShield Program Updates icon in Control Panel, though. I got rid of that by going to C:\Windows\System32. There, I clicked on the Type heading (in Windows Explorer) to sort by that field, scrolled down to the .cpl (Control panel item) files, and deleted ISUSPM.cpl. The icon was still in Control Panel, but I thought maybe it would go away after a reboot. That may have been correct. When I checked a week later, it was gone.