Thoughts Concerning Microsoft Windows Shell Integration for Applications

Presently, I'm endeavoring to replace Immunet with AVG 2015 Free edition -- having replaced my laptop's Mcaffee antivirus "trial run" software (whose registry features, some, are still in the registry, as namely in regards to Mcaffee's quarantine proces) having replaced that with Immunet -- the latter is derived from ClamAV somehow -- that, before the same "Trial run" had expired, and now Immunet has expired. I'm in no kind of a rush, really. I plan on installing AVG, shortly.

In the process of trying to determine where Immunet has suffixed away some files -- those that may have been "false positives," but such that Immunet states to have located a "Worm" in -- so, simply in trying to find what's the quarantine directory's pathname[1] I've been searching the Windows Registry for the string, "Immunet". In that process, I've noticed a couple of things that I would note on a sidebar, namely:  Concerning Microsoft Windows Shell Integration for Applications

Components for a Microsoft Windows Application, albeit in an ad hoc selection:

• Installer
• cf. Nullsoft Scriptable Installer (NSI) or otherwise
• Main application binary
• i.e. "The thing that shows up in the Start menu," using a classic Microsoft Windows shell or the similar.
• May be extended with an additional "Smart menu" feature, such that that "Thing that shows up in the start menu" would itself provide a submenu unique to the same "Thing." The Kindle application provides such a "Smart menu," using the classic Kindle application for Microsoft Windows platforms.
• Context menu integration
• Specifically for the file manager's context menu
• May or may not be relevant for an application, depending on the nature of the application
• Example: "Context menu" integration within TortoiseGit
• System tray integration
• "Like as" with regards to the Context Menu integration, may not be relevant for all applications
• Typically, system tray integration is a feature provided with "Service-like" applications, such as the iCloud Control Panel integration for Microsoft Windows platforms and its corresponding System Tray component
• Uninstaller
• Likely bundled with the installer.
• Documentation
• Manual
• Support forums
• Etc.

Simple outline!


[1] On further review, I've found the pathname for the Immunet quarantine folder at C:\Program Files\Immunet\Quarantine -- this, on Microsoft Windows 8.1. The files are all named peculiarly, there, and Immunet won't run so long as to provide more information about those files, now. I'll just have to re-install JabRef -- Immunet said it detected a worm in the same, though that seems peculiar to me, moreso for that Immunet had once scanned a *.crdownload file and said there was a worm in the same, though the file had not even finished downloading. So at this time, candidly, I'm not particularly trusting of Immunet's file scan architecture. and will be installing AVG instead.