サインイン
 
ホームライブラリサポート情報ダウンロードラーニングセミナーフォーラムサイトマップ
マイクロソフトの技術情報ポータル >
> 
> 
Finding bad shell context menu

Answered Finding bad shell context menu

  • 2012年4月23日 12:14
     
     
    サインインして投票
    0

    Hi Guys,

    Running Windows 2003 Terminal Server. Right clicking on any file is creating a 30 second wait for the context menu to show. Same with opening the file type. It seems to be happening on all file types, specifically PDF.

    So far I have:

    • Disabled all non-Microsoft shells
    • Run sfc /scannow
    • remove/re-installed programs
    • Re-registered default shell dll's

    I still have the same issue. I am 100% certain it is one of the shells/context menus. I've run processmon and can't find anything out of the ordinary.

    Suggestions? At my wits end here.

     

すべての返信

  • 2012年4月23日 21:07
     
     
    サインインして投票
    0
    Bump. Really need some help with this. Borderline having to re-provision the server.
     
  • 2012年4月23日 22:49
     
     
    サインインして投票
    0

    Have you tried creating a new user and log in with the new account to see if the issue remains?  If so, then you do have a "computer" issue; if not, you have a user profile issue which can be easier to resolve.

    You mentioned that you "Disabled all non-Microsoft shells."  What non-MSFT shells do you have installed on a server?

     
  • 2012年4月23日 23:06
     
     
    サインインして投票
    0
    I'm probably using the wrong terminology. I disabled the non-microsoft context menus.
     
  • 2012年4月23日 23:24
     
     
    サインインして投票
    0
    I think I've tracked it down to bad profiles. New profiles don't seem to have the issue.
     
  • 2012年4月24日 2:25
    モデレータ
     
     
    サインインして投票
    0

    The likely cause for the issue mentioned in your initial post would be, bad or old user profiles ( which you have already mentioned), abruptly terminated TS sessions and active registry connections to files even though user is logged off.

    I have personally seen such issues in our environment and UPHC has helped a lot.

    I would suggest you to install "User Profile Hive Cleanup Service" on your 2003 TS. 

    http://www.microsoft.com/download/en/details.aspx?id=6676 

    The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending.

    P.S. You just have to install UPHClean-Setup.msi on TS which will start working immediately. no need to do any settings and Server reboot is also not needed.

    A UNIVERSE without WINDOWS is CHAOS !

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    About Me !!!

     
  • 2012年4月24日 6:59
     
     
    サインインして投票
    0

    The best way would be using the process monitor and Finding out the issue.The most important thing is you should use filter and only track "Explorer.exe" which will eventually show you everything.

    http://www.arabitpro.com

     
  • 2012年4月24日 9:38
     
     
    サインインして投票
    0

    Thanks for the feedback.

    The TS server already has User Hive Profile Cleanup tool installed and working correctly. The TS has been running for about 3 years with no issue until now.

    I've also run process monitor on explorer.exe, this was one of the first things I did. However, right clicking on a file gives a few hundred reg entries. I checked half a dozen, but there was nothing out of the ordinary. 

    Basically, new profiles have fixed the issue... You'd like it would be something else. I'm at a loss as to why it's the profiles. If someone could explain that a little more? Something to do with their reg hive being corrupt? 


    • 編集済み infused 2012年4月24日 9:38
    •  
     
  • 2012年4月29日 21:49
     
     
    サインインして投票
    0

    Just letting you know that new profiles did not fix this... are there any more ideas? I think I'm at the point where I will move the users to a 2008 R2 TS server as this problem has eaten up so much time.

    In Summary I've done the following:

    • Removed all shell context menus (3rd party)
    • Created new profiles for users
    • Removed all affected programs from the server (Adobe, FoxIT etc)
    • Run sfc /scannow

    Right clicking on any file takes 30 seconds or so to show the context menu.

    Any other suggestions?


    • 編集済み infused 2012年4月29日 21:50
    •  
     
  • 2012年4月30日 6:17
     
     回答済み
    サインインして投票
    0

    1) have you tried this tool ?

    http://www.nirsoft.net/utils/shell_menu_view.html

    2) Do a clean boot and check the behavior.

    http://www.arabitpro.com

     
  • 2012年5月1日 9:36
     
     
    サインインして投票
    0

    I have used that tool and disabled anything that is not Microsoft. Same issue.

    Will try the clean boot.