"Tony Susa" <susa.anthony...@neosporum.com> wrote in message
news:1tsrsce0x9yx8.hn6n0du6e11a.dlg@40tude.net...
> On Fri, 9 Dec 2005 16:16:28 +0530, Ramesh, MS-MVP wrote:
>
>> Tony,
>> Follow Method 2 in that article, which is the easiest method.
>
> OK, I'll follow your advice since you definately seem to know what you are
> doing.
>
> Here are existing value (before any new changes) of the registry keys:
> HKCR\Folder\shellex\contextmenuhandlers
> = {969223c0-26aa-11d0-90ee-444553540000}
> = PropertiesPlus
> = VirusScan
> = WinZip
>
> HKCR\Directory\shellex\contextmenuhandlers
> = ACShell
> = EncryptionMenu
> = Offline Files
> = Sharing
> = VirusScan
> = WinZip
> = ZipGenius5
>
> I wonder which one is the culprit (time will tell).
>
> For the record, I think the hundreds of DLLs that SFC wants is due (maybe)
> to the fact a month ago I changed all the dates on the machine to a single
> date using setfiledate. Otherwise, I don't know why SFC is asking for so
> many files (hundreds). BTW, SFC is a really really really dumb program.
> After OK'ing a few hundred of these "Windows File Protection" dialogs,
> you'd think it would have an "ok for all" button. But noooooo ....
>
> Tony


Try using NirSoft's ShellExView which shows the shell extensions. It will
let you disable them. Obviously pick the ones that are not included in a
Windows install, like your anti-virus context menu items, WinZip, 3rd party
search tool, etc. NirSoft also has a ShellMenu utility that might help.