Windows 7: Remove InstallShield Update Manager

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 Use
The action can't be completed because the file is open in InstallShield Update Service Scheduler.

So 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.

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.

Windows 7 Installation - First Try

I decided to install Windows 7.  I had previously written up my preferred Windows XP installation process.  This post updates that previous writeup for Windows 7.  It seemed likely that I would find additional helpful Win7 tweaks after using it for a while, so I considered this my first try.  The version I was installing was Win7 Ultimate.  My efforts as described here were fairly comprehensive -- I worked through lots of issues -- but also pretty disorganized.  The second try, I hoped, would be better.

I decided to get and use a 32-bit version of Win7.  I had tried a 64-bit version of Ubuntu and found that there were quite a few problems.  Even at the time of this writing, I was hearing some indications that reminded me that 64-bit Win7 and other 64-bit operating systems were still not established.  This was from the perspective of someone who usesd the computer for work, and a wide variety of general-purpose work functions at that, and not much for play.  I would have had a different opinion if I had different needs.  Presumably 64-bit had more speed.

I also decided to do a clean installation, completely overwriting the previous Windows XP installation.  Although I didn't look into it, it sounded like there might be some kind of "hard link" alternative.  I didn't explore it, so I was not sure if it was actually much easier than the fresh install option.  For upgrades from Vista, apparently there was an Upgrade Advisor that might have been helpful.

In my case, with my Gigabyte motherboard, the essential first step, before even completing the Win7 installation, was to install two motherboard drivers that were supposed to be installed from floppy disk.  I did not realize this.  A belated search led to one source who claimed that reinstallation was not necessary, but I had only just done the installation, and it had been pretty easy, so I decided it was easier to just reinstall than to follow his directions.

I started by downloading the current drivers from the motherboard manufacturer's website.  Gigabyte's website contained a link to DriverAgent, which did a free scan for missing drivers but then wanted to charge me a fee to download and install them. I decided to just get them from the Gigabyte site. I unzipped them, but to see and actually install their setup files, I had to make adjustments in Windows Explorer (Tools > Folder Options > View > unhide everything). I made other changes to the View tab while I was there. It had not changed much since Windows XP, so I used pretty much the same settings as before. (For details, go to the previous writeup and search for "Windows Explorer.")  The drivers unzipped automatically into separate folders.

It then occurred to me that possibly a complete reinstallation was not necessary.  I left my new but imperfect Windows 7 installation in place for the moment and rebooted from the Windows 7 DVD.  I clicked Next to get past the first Install Windows screen and chose the "Repair your computer" option. In the System Recovery Options dialog, I clicked on the Load Drivers button, inserted the CD containing the drivers, double-clicked on the file that was a "setup information" file type in the folder for the first driver, and clicked Add Drivers. I repeated those steps for the other driver. Evidently these steps loaded the drivers into memory.  Then I clicked Next and proceeded to the System Recovery Options dialog.  I clicked Startup Repair, but it could not detect a problem.  So I gave up on this approach and did the complete reinstallation.

Gigabyte's webpage said that the two drivers that had to be installed during Windows 7 installation would have to be installed from a floppy drive.  I did not have a floppy drive.  I burned the folders containing those drivers onto a CD.  Then I inserted the Windows 7 DVD and rebooted.  When the BIOS was loading, I got an option to press any key to boot from the DVD.  I did that.  This put me at the Install Windows screen.  I clicked Next > Install Now.  I took the custom installation option.  When I saw the question, "Where do you want to install Windows?" I clicked "Load Driver."  But after a minute, it came back with a message:

No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.

One of these troublesome drivers was for a RAID array.  I had not actually set one up yet.  I unchecked the option that said, "Hide drivers that are not compatible with hardware on this computer," and then clicked Rescan. I still got the same message.  I wasn't sure what that meant regarding the quality of my download and the relevance of the drivers that Gigabyte's webpage had listed for my motherboard.  It appeared that I would be able to set up software RAID in Windows 7 regardless of my hardware, and that a hardware RAID array would have to be in place before I installed Windows.  As I was thinking this over, I came across a good article on RAID in Windows 7 that made me think that a Win7 software RAID array was actually better for my purposes anyway.  So at this point I bailed out of the attempt at reinstallation and just rebooted the Windows 7 installation that I had already set up.  I describe my actual RAID setup process in a separate post.

The other troublesome driver was for AHCI.  After installing the other drivers and rebooting, I got an option to set the BIOS to boot in AHCI mode.  Or something like that -- it had a short fuse and demanded a decision before I could really read what it was saying.  I went with the Yes option, I think, and that made Windows unable to run.  I had to reboot, hit Del to go into the BIOS, and look around to replace the AHCI option with the Native IDE option.  I then observed that, of course, the BIOS update had wiped out my settings, so I changed some other items while I was there.  Then I rebooted.

The next step was to install antivirus and firewall software.  I had always previously gone with free versions, most recently AVG.  For the moment, I decided to continue with AVG, but also looked into stronger alternatives, and on that basis, I thought I would eventually switch to F-Secure.

Next, updates.  I wanted to download them once and save them, so that I wouldn't have to re-download hundreds of megabytes' worth of updates and service packs every time I re-installed Windows 7.  But I had spent a lot of time taking the manual approach with Windows XP, it was hard to be sure of the right order to install them in, and it was a lot easier to just let the Windows Update site do it automatically.  I had already encountered an opportunity to set the downloads the way I wanted, which was to download but not install.  I preferred that because otherwise Windows XP, at least, would keep insisting on rebooting the system, until at some point that reminder would pop up right while I was in the middle of typing something and, presto! I would hit the wrong key and the system would reboot, taking all my work with it.  Unlike XP, Win7 wasn't showing me an icon in the system tray to indicate that it had downloaded updates and was waiting for a chance to install them.  It also didn't offer to do so when I clicked the Turn Off option to shut down the system.  But I could tell that it had downloaded updates because, when I did go to the Windows Update page, it didn't need to download anything; it just proceeded right into the installation of about 140MB worth of updates (counting those that weren't ready to install until after a reboot).

While updates were installing, I looked into user accounts.  For efficiency reasons, I had been running WinXP as administrator.  Microsoft said the user account would protect my computer by preventing users (me) from making changes that affect everyone who used the computer (me).  In other words, I decided to continue to do my work while logged in as administrator.  So before I installed programs that might configure themselves for individual user accounts, I did a search for how to delete my user account.  The advice I followed led me to the Control Panel, so at this point I decided to go ahead with the full Control Panel tour, which I had postponed until later when installed WinXP.

Ideally, I would have taken care of the accounts at this point.  But I didn't.  So some of the changes described below were made to my own personal account ("Ray"), and therefore had to be redone after I started up the Administrator account and deleted the Ray and Guest accounts.  Another thing that complicated that step of changing accounts was that I did not approach it through Control Panel.  I made the change in a different way, before looking at Control Panel > User Accounts.  So I was not sure what that User Accounts area would have looked like originally.

What actually happened was that I went ahead with the Control Panel tour (below), and toward the end of that process I discovered Ultimate Windows Tweaker (UWT), and used it to make some of the changes that I would have made through Control Panel.  UWT had some options that Control Panel did not have, but it also lacked some options that Control Panel.  It probably did not make much difference which came first, but in my own future installations I felt I would probably go through Control Panel first, and then run UWT, or possibly God Mode (below).

At any rate, I had to go into Control Panel > User Accounts (having switched, at the top right corner of Control Panel, from Category view to small icons), select the Ray account, and then click the "Delete the account" option.  There did not appear to be a way of deleting the Guest account, so I just left it turned off.  Then, to continue preparing for the Control Panel tour, I opened Internet Explorer and opened a separate tab for each webpage that I often checked in Internet Explorer (e.g., Hotmail).  Then, in Intenet Explorer, I went to Tools > Intenet Options > Home Page > Use current.

What I wanted, for this purpose, was to konw how to use the PowerShell ISE to create a set of modules for PowerShell that would do things (e.g., adding features) that otherwise I would have to do manually, by going into this menu and choosing that option, etc.  Why should so many of us spend so much time doing that sort of thing, when it was (in my understanding) entirely possible to use PowerShell commands, already installed in Win7, to share a set of commands that would do it all automatically, in one step?  But apparently I was misunderstanding something about this.  My search suggested that, while there were plenty of websites sharing Win7 tweaks, there were almost none sharing Win7 tweaks contained in PowerShell modules.

Registry edits were an alternative for some such tweaks.  My key sources for guidance, in these tweaks, included the massive collection of SevenForums tutorials and the How-To Geek list of registry hacks.  This was the point at which, in future installations, I would run Win7RegEdit.reg, a text file that I built up during the process of learning how to configure Win7.  Running it at this point, which I did not do, would have affected some of the other instructions shown below.  Before running it, I would need to adjust editing permissions for one branch of the registry.  Steps for that:  go into regedit, navigate to HKEY_CLASSES_ROOT\CLSID, right-click on CLSID, go tinto Permissions, highlight Administrators, click Allow Full Control, go into Advanced, check "Replace all child object permissions with inheritable permissions from this object."

Next, in Control Panel, at the top right corner, I switched from Category view to small icons.  Then, going down the list, I hit a number of other items.  These are shown here in alphabetical order as they appeared in Control Panel, but this order also happened to be important for a few of these items:

• Action Center:  I had already set my Windows Update settings.
• Administrative Tools:  in Computer Management > Storage > Disk Management, right-click on the CD-ROM drive (at the bottom) and change its drive letter to Y.  Then change other drive letters (after rebooting, if necessary) as needed.
• AutoPlay:  turned off for all devices.  Defaults set to "Take no action" for all items except movies and videos.
• Backup and Restore:  I had not had good luck with Windows System Restore.  I preferred Acronis True Image.  So I just verified that this option was turned off.
• Folder Options:  finished setting items I had not already set (above).
• Internet Options:  I went into Tools > General tab > Browsing history > Settings > Move folder to another drive. I also went to Tools > General tab > Tabs > Settings > adjust as desired. I went to Security tab > Custom Level > Scripting section (near the bottom) > Allow programmatic clipboard access > Enable.  Then I navigated to YouTube.com and played a video, so as to trigger the process of installing Adobe Flash Player.
• Notification Area Icons:  Always show all icons and notifications on the taskbar.
• Personalization:  Windows Classic theme.  Window Color > Adjust at least Active Title Bar, Inactive Title Bar, Menu, and Desktop.
• Power Options:  Show additional plans > High performance > Change plan settings > Change advanced power settings > Change settings that are currently unavailable > High performance > change individual items as desired > Apply.
• Programs and Features:  Turn Windows features on or off > Make sure Indexing Service is off.
• System:  Windows Activation > Activate.  System Protection > Hardware tab > Device Manager > verify are no yellow-circle exclamation marks.  Hardware tab > Device Installation Settings > Yes, do this automatically.  Advanced tab > Performance > Settings > Advanced > Change > Uncheck automatically manage paging file size for all drivers; instead, set a paging file of 4000-8000 MB (or more) on each hard drive.  System Protection tab > Configure > adjust Disk Space Usage as needed.
• Taskbar and Start Menu:  Start Menu tab > Customize.  Adjust various items to taste.  Turn on Run command.  Save and close.
• User Accounts:  see above.  When the dust settled, I had only the Administrator account here.
• Windows Defender:  turn on.
• Windows Update:  after installing desired updates, highlight all unwanted updates (e.g., foreign language packs, right-click, and select "Hide updates."  

For purposes of doing these tweaks, UWT (above) was not the only consolidated alternative to Control Panel.  Another was God Mode.  Apparently this was just originally going to be an All Tasks folder in Win7, but Microsoft didn't include it in the final version, and bloggers gave it the God Mode name.  It seems there were actually a number of different subcollections of tweaks which, at brief glance, didn't look like they added much to UWT for my purposes.  What I decided to do with this was to create a Start Menu entry for an All Tasks folder.  The full folder name was long, so I parked it further down in the Programs listing within the Start Menu (below), and just put a shortcut to it at the top level of the Start Menu.  To automate part of that last step, I wrote a command for a DOS batch file. That batch file (Win7NewInstall.bat) eventually came to have other lines as well.

In the past, I had overlooked some Control Panel items that would have been useful.  So in that God Mode (what I called the All Control Panel Options) folder, I hit Ctrl-A (i.e., I selected everything) and then right-clicked and said "Create shortcut."  This put 276 shortcuts on my desktop.  I moved them to a folder, where I could see their full names.  I deleted those that I didn't think I would need.  I moved a bunch of them to a folder for items that I would run only when installing a new system.  I put the rest in other categories, and moved them to relevant places in my Start Menu.  This was an alternative to the approach of removing or hiding unwanted items in Control Panel.  With these steps, I hoped to be able to do without Control Panel, but it was still there unchanged for purposes of following steps advised by others.

I had worked out a customized Start Menu, with several advantages.  Another post describes the process of making that work in Win7.

Something else that I should have done early in the process was to map my network drives.  The problem was, I was simultaneously doing some hardware changes.  I had a Synology Network Attached Storage (NAS) unit, but for performance reasons I wanted to change to some other arrangement.  I needed to get that other arrangement in place first -- actually, before proceeding with this installation -- or at least I needed to know which drives would be where, because of course when I mapped them I would assign them drive letters, and aspects of this installation would be looking for those letters.  So I took a detour, during this installation, to figure out that part of my hardware arrangement. 

The next task was to customize Windows Explorer.  It looked like I was stuck with the new menu bar that Microsoft added at the top, unless I wanted to risk seriously screwing up the system.  I wondered if there was a good alternative to WinExp.  When I started looking around, I saw statements that resonated with my experience regarding WinExp's slowness.  It developed that there were a bunch of alternatives.  I prepared a separate post leading to my conclusions in that area.  Basically, I decided to start with Total Commander and see if I liked it.  Of course, I could still use Windows Explorer regardless.  This somewhat took the fire out of my interest in more Windows Explorer tweaks.

Other Tweaks

Early in the process, I installed Google Chrome.  I had to.  It was impossible to get anything done in Internet Explorer, especially in terms of looking at lots of different webpages providing advice on how to solve problems.  Within Chrome Extensions, I installed Webpage Decorator.  The reason for this extension was to make it easier to see which links in Google searches I had already visited.  Their colors were almost identical in Chrome originally.  After installing it, I clicked its newly installed icon (at the right end of the Chrome search bar) and made the colors of links and visited links more clearly distinct.

I got an uninvited item on the taskbar saying, "Welcome to Windows Media Player."  I went through a custom installation, making it the default player for the time being.  Then I unpinned the icon from the taskbar.

Also, from almost the beginning, Windows Defender would give me an error message at startup:  "Service has stopped.  A problem caused this program's service to stop.  To start the service, click the Start now button or restart your computer."  I searched for a solution and noticed lots of posts on how to uninstall or disable Windows Defender.  I looked into that.  While Windows Defender appeared to be antispyware that ordinarily performed a valid function, it was also no different than other antispyware.  Apparently this problem could be caused by conflicts with other antivirus software (e.g., McAfee).  I originally thought Windows Defender kept being turned off after I turned it on because I had disabled UAC; apparently Windows Defender was related to that.  Ordinarily, to turn it off, I would go to Control Panel > Windows Defender > Turn it on > Tools > Options > Administrator > uncheck > Save.  This would still produce the error, "This program is turned off."  In another approach, I tried running services.msc and selecting Disabled as the Startup type under Windows Defender (right-click > Properties).  But that, too, left me with a reminder to turn on Windows Defender on startup.  Anyway, this approach of trying to shut Windows Defender up was not working.  If you can't beat 'em, join 'em.  I went back to services.msc and set it to Automatic; I went into Control Panel and uninstalled AVG antivirus; and I downloaded and installed Microsoft Security Essentials.  I planned to upgrade to better antivirus software later, but hoped that this would reduce conflicts for the short term.

Epilogue

By this point, it was time to start over again.  The reason was that this installation had somehow acquired a networking problem that I just could not fix. The reinstallation is described in another post.

Microsoft Office 2003 Updates in 2010 and Beyond

Introduction

At one point, I had installed Microsoft Office Professional 2003, and I wanted to know what updates were available.  Once upon a time, that was easy to determine.  You would just go to the Microsoft Office Updates webpage and let it take a look at your computer and tell you what you needed.  But that webpage was no longer available.

Microsoft was apparently still supporting Office 2003, and it was still possible to get updates from the general-purpose Microsoft Updates webpage.  But under various conditions, that would not work either.  For instance, Microsoft might decide to cut off that source of automated updates for Office 2003, just as it had cut off its Office Updates automatic detector.  Or you might not be able to go online when you were doing your installation.  Or if you did go online, as I had sometimes experienced, that webpage might not be willing or able to detect the condition of your computer and figure out which updates you needed.  Or you might be trying to install all available updates at once -- that is, you might not be willing to wait around until the webpage did detect all of the updates you might need.  That was the situation at present.  I was trying to convert Office 2003 into a set of portable applications, and for that purpose I needed to do all of my updates at once if they were to be included in the portable executable package.

To figure out what updates I needed, I went to the general-purpose Microsoft Office Downloads webpage and glanced at its hundreds of downloads, including many that were unnecessary and even obsolete.  Then, taking a different approach, I looked at another computer, where Office 2003 had been installed in March 2009.  (On that machine, all Office programs were installed except InfoPath, and Outlook 2007 had been installed in lieu of Outlook 2003.)  On that machine, I went into Start > Settings > Control Panel > Add or Remove Programs > Show Updates.  Under Microsoft Office Professional Edition 2003, it listed a number of updates.  Those updates had been installed automatically by Office Update between March 12, 2009 and March 10, 2010.  With one exception, all of the updates listed there were newer than Office Pro Service Pack 3 (SP3).  That one exception had not been included in SP3, so apparently Office Update knew that it still had to install it separately.

Armed with that information, I went back to the full list of Office updates.  At this writing, there were 3,204 items on that list.  I sorted them by Release Date and skipped ahead to the page for September 2007, when SP3 was released.  I noticed that there were other SP3 packages released at about that same time, for a variety of Microsoft products, including some that were related to Office 2003 tools or capabilities (e.g., Office 2003 Proofing Tools) that I had not installed and/or had not been using on that other computer, and that therefore had not been updated.  So the list that I was developing in this post would probably not be sufficient for all purposes and all users of Office 2003.

I decided to assume that the automatic Office updating feature had been giving me what I needed, for my Office 2003 installation, up through that last update on March 10, 2010.  Therefore, I skipped ahead again, in the Microsoft webpage list, to the page showing updates released on or after that date.  That page was very near the end of the list.  (I tried, here in this post, to provide links to these points in the list, so that other users would not have to page through the list manually, but I found that Microsoft had structured the pages so that the links invariably led to the start of the list.  Microsoft did not itself bother to provide a button leading to the end of the list.)  From that point forward in the list, starting in March 2010, there were not any other updates pertaining to Office 2003.  So it seemed that the March 2010 updates were the state of the art.

But that could hardly be correct.  After thinking a moment, I remembered that, because of a broken installer or some other problem that I had been unable to fix, that other computer had ceased to install updates from the regular Microsoft Update webpage.  So now I asked that webpage to examine that computer and indicate what other updates it needed.  It came back with a list that included several more updates specifically related to Office 2003.  I did not know why these additional updates had not appeared in that list of 3,204 updates on the Microsoft Office webpage.

The List of Updates Generally

I combined that list of uninstalled updates, from the Microsoft Update webpage, with the list of updates that had been installed successfully.  Here is that combined list, with links to the relevant KnowledgeBase pages:

Release Date	Programs Affected	KB Number
11/08/05	Excel, Word	KB907417
09/17/07	All Office 2003 (SP3)	KB923618
12/08/07	Outlook	KB943649
02/11/08	All Office 2003	KB945185
02/12/08	Works File Converter	KB943973
05/12/08	Publisher	KB950213
08/08/08	Access Snapshot Viewer	KB955439
08/08/08	All Office 2003	KB921598
09/08/08	All Office 2003	KB953404
11/07/08	All Office 2003	KB951535
10/09/09	Outlook	KB974554
10/09/09	Outlook	KB973705
10/13/09	All Office 2003	KB972580
10/22/09	Web Components	KB947319
11/09/09	All Office 2003	KB973443
12/07/09	All Office 2003	KB975051
12/17/09	All Office 2003	KB978551
02/04/10	PowerPoint	KB976881
03/05/10	Outlook	KB979771
03/05/10	Excel	KB978474
05/10/10	All Office 2003	KB976382
06/04/10	PowerPoint	KB982157
06/04/10	Publisher	KB982122
06/04/10	All Office 2003	KB982311
06/04/10	InfoPath	KB980923
07/07/10	Access	KB981716
07/08/10	Outlook	KB980373
08/05/10	Word	KB2251399
08/04/10	Outlook	KB2279246
08/04/10	Excel	KB2264403

Again, this list would vary if one were to install other components from Office 2003.  My purpose here is primarily just to sketch out what seems to be one way of determining what updates are needed for one Office 2003 configuration.

The List of Updates for Word 2003 Specifically 

This list of updates, and the other information provided above, seemed to provide a straightforward guide to the updates that would be needed for individual components within Office 2003.  I tested that assumption, starting with Word 2003.  That is, I installed only Word 2003, without any other Office 2003 components beyond those that were automatically installed for any Office configuration.

I expected, from the foregoing information, that the Microsoft Update webpage would detect and install all of the items from the foregoing list that pertained either to Word specifically or to Office generally,  I expected, in other words, that when the dust settled and all the updates were installed, Control Panel > Add or Remove Programs would show me just the following updates under Microsoft Office 2003:

Release Date	Programs Affected	KB Number
11/08/05	Excel, Word	KB907417
09/17/07	All Office 2003 (SP3)	KB923618
02/11/08	All Office 2003	KB945185
08/08/08	All Office 2003	KB921598
09/08/08	All Office 2003	KB953404
11/07/08	All Office 2003	KB951535
10/13/09	All Office 2003	KB972580
10/22/09	Web Components	KB947319
11/09/09	All Office 2003	KB973443
12/07/09	All Office 2003	KB975051
12/17/09	All Office 2003	KB978551
05/10/10	All Office 2003	KB976382
06/04/10	All Office 2003	KB982311
08/05/10	Word	KB2251399

That, however, is not quite how it had worked out.  After installing only Word 2003, the Microsoft Windows Update webpage was telling me that I had no other updates to install.  I thought maybe this was because it was a brand-new installation and it needed some stimulation to get busy and figure out where it stood.  In hopes of triggering some action, I started Word and fiddled with it for a minute, and then I rebooted the system.  But the Update webpage still showed no other updates available.  Likewise when I powered down the system and left it alone for a couple of days.

I wasn't sure what that meant.  Was the Windows Update webpage never going to detect that updates were needed?  Or did I just have to use Word for a while, triggering some unknown functions, before it would become aware of its desperate need for an update?  Did it matter that I was doing this inside a VMware virtual machine (VM), rather than in a native WinXP installation?

The alternative to the automated online update, of course, was to just go ahead and install that list of Word-specific updates manually.  So I did that.  I uninstalled and reinstalled Word; and when it ended, I accepted its offer to go online and check for updates.  Without the old Office Update webpage, however, that option just delivered me to the general-purpose webpage mentioned above.  I killed that and started down the list of updates, installing them one by one, beginning with SP3 (KB923618).

After doing that, I went into Control Panel > Add or Remove Programs > Show Updates and verified that those updates were all listed under Microsoft Office 2003.  They weren't.  KB945185 wasn't listed.  I ran it again, and it said, "This update has already been applied or is included in an update that has already been applied."  That puzzled me:  how would I have gotten its number in the first place, if it hadn't been listed previously?  Same thing with KB953404.  Anyway, then I went to the Windows Update website to double-check that there were no others.  There weren't.

Conclusion

I could have continued with the same approach for Excel 2003 and other components of Office 2003.  In the meantime, however, it had developed that the underlying goal of creating a portable version of Office 2003 was not feasible with existing programs and resources.  So I did not continue on to explore what updates would be needed for those other Office components.