Sudden Slow-down in Vista

[howardparsons]

I've been having some issues w/ Vista services. All of a sudden, it seems to take "forever" for me to right click on a folder in LBC to get the context menu. Any suggestions or ideas?

[mouser]

is it possible its an antivirus (or similar) program causing it?

[howardparsons]

It's "theoretically" possible though I haven't touched my AV software, etc. (I've obviously "touched" something.) The only new software is MS IIS.

[mouser]

howard check this:

"Fix for Very Slow or Hang When Right Click On a File or Folder"
http://www.raymond.c...on-a-file-or-folder/

[howardparsons]

Well,
   I've determined that it's none of the non-MS shell extensions but there are 312 (+/-) MS shell extensions to sort through. I've also determined that when I right-click on a folder, say, on my desktop I get the context menu almost instantly. When I try & right-click on a folder via LaunchBar Commader, it's 2 -3 minutes before I get the context menu.

[howardparsons]

Update -
    I think that I've narrowed it down as to having something to do w/ IIS. Apache started givening me problems last week & I subsequently exhausted all possible avenues short of completely re-installing Vista or going to 7 & hoping that the trouble will go away. As part of my debugging efforts, I took a snapshot of all the services (running or not) on my box.

   I installed IIS on 1/2/10 because there is some work that I have to get out. That's when the slow-down began w/ LaunchBar. Anyway, I compared the list from before IIS w/ the list after IIS & the only difference is the addition of the IIS services. Everything else that was running then is still running now. Now if someone would code an on-off switch things like IIS . . .

[howardparsons]

A Second Update.

    I decided to see just how long it takes between the moment I right-click on a folder in LBC & the moment the context menu appears. The total time is 60 seconds on the nose. Sounds like theres a setting for a 60 sec. delay/timeout somewhere. Just where that "somewhere" may be is beyond my ken at the moment.