SendOfJive wrote:
uschwarz wrote:
What was being launched was "c:/windows/system32https://www-secure....(much deleted)". It's easy to see that NIS wasn't attempting to launch a web page, instead it prepended "c:/windows/system32" to the call. Very odd behavior.
That is because the file association did not point to a browser. Clicking Help should launch your default browser, which then retrieves the page. The following screenshot shows Firefox.exe as a child process of ccsvchst.exe when the Help link is clicked in the Norton GUI:

Hi, SendOfJive. I agree with DaveH, that the text editor is "hijacking" the .htm and/or .html extensions as part of both its install routines and its normal operation. This happens with a bunch of different programs.
For example, If both QuickTime and Windows Media Player are installed, the *.MP3 extension can be played by either program. Which program gets selected will vary depending upon which program has the "hijack" function enabled. If you go and look at the QuickTime Preferences under the File Types tab , one of the options there is to "Notify me if other programs modify these associations". This is QuickTime's way of enforcing its hold on the set of associations marked by default (at first) or modified by the user (if desired).
Similarly, in Windows Media Player, by selecting Tools/Options/File_Types and ticking the desired items, the user can "claw back" associations hijacked by other programs like RealPlayer, various Creative Labs products, various Roxio products, and so on.
However, if any one of the programs installed that manipulates a particular file extension has an "auto clawback" feature - then that program will automatically pull back that file extension to itself whenever it runs or whenever its "enforcer" is run at startup. This is what causes any modification to a particular file extension to "not stick". The problem is especially vexing when a user has 2 or 3 or more programs which all have auto-clawback features. Then what happens is whichever program was run last will take the association, and you will never have peace in the land at all, at all, at all. 
What is necessary to sort this out is to disable auto-clawback in all the programs that have that feature. This usually means deselecting a checkbox in the Options for each particular program. If the user wishes to reliably associate one particular program with a particular file extension - they can enable auto-clawback on one of the associated programs. However, if they want the association to occur with any program that does not have auto-clawback capability, then auto-clawback must be disabled on all the programs that have the ability to associate with that particular file extension.
Note: "Open With" will still allow the user to select whichever program they wish to use for a particular file - by selecting from the list of available options using that feature. This allows full flexibility if the user wants to use something other than the default program selected for that extension. But this does not work for automated situations such as the use of the Default Browser for NIS' Helpfile access.
A similar problem occurs with multiple Internet Browsers. It is necessary to disable auto-clawback in all but one of the Browsers in order to prevent "hunting" between default Browsers.
This is also the case for the difference between Outlook and Outlook Express/Windows Live Mail. There is a similar problem with "hunting" there as well.