Hi, TMG! Thank you for the link. I found out what was going on, and the answer is two-fold: I know what the problem is, but I do not know how to fix it.
I installed xCHM, which is a third-party tool that allows you to view .CHM files, the files that are freqently [always?] targeted when you click on "Help" inside a given program. Although I don't regularly rely on Help, it is one of those things that occasionally comes in handy. However, when I removed Windows help/Internet Explorer, I also crippled the viewer that is supposed to open those .CHM files. That explains the problem as demonstrated in the screenshot above.
Now, here is what I discovered with the help of some folks on MSFN. I installed xCHM viewer, and told Windows to use it to view .CHM files. Many programs on my computer obey this new assoiciation, and when I click "Help," the file opens correctly in xCHM. However, *certain* programs act stupidly, and ignore the setting; instead of attempting to open the help files with xCHM as instructed, they continue to try and use the crippled Windows component, resulting in the error as seen above. The problem, therefore, is not with xCHM or Windows; the problem is that certain programs are not "listening" to me/the Windows registry, and opening the .CHM file with xCHM. I have no idea how to *make* the offending programs follow the directions as outlined in the registry to open the help file with xCHM.
At this point, it appears that when necessary/needed, I should be able to open the file manually by opening xCHM first, and then using the "File"/"Open" sequence on the menu to pull up the help file I need. However, it would be nice to have the programs use the utility (xCHM) instead of the broken one (Windows Help).
http://www.msfn.org/board/index.php?showtopic=135582