Hotfixes available for ‘scrolling context menu’ problem

Hotfixes available for ‘scrolling context menu’ problem

Rate This
  • Comments 52

 

We’ve been looking into the widely-reported problem with Visual Studio 2010 where context menus contain scrollbars even when there is sufficient screen real estate to show the menu without one. We’re pleased to announce that there are patches available for Visual Studio and Windows Presentation Foundation that fix this problem. You will need to install both patches to fix this issue

  1. Visual Studio 2010 patch: http://code.msdn.microsoft.com/KB2345133
  2. Windows Presentation Foundation 4.0 patch: http://code.msdn.microsoft.com/KB2413613
    1. X86: NDP40-KB2413613-x86.exe.
    2. X64: NDP40-KB2413613-x64.exe.

 

If you have any additional questions, post here (on the blog comment section) and we will follow up to ensure a bug is filed or a solution is found.  

Thanks,

Matt Kaufman
Senior Program Manager
Microsoft Visual Studio

Leave a Comment
  • Please add 4 and 3 and type the answer here:
  • Post
  • @Ryan

    I have uninstalled the patches and VS, reinstalled and I still get the message "Cannot create window". This is becoming a serious problem...

  • @Ryan

    Thanks for the reply. This is indeed a single-monitor laptop.  I do not get the full/maximized right click menu displayed; but I do get it on my now-patched 32-bit Vista setup, so that's why I decided to give the patch a try on a single monitor setup.

    I did email a screen of installed updates to matt-kaufman at hotmail in case it helps you guys find a cause.

    Thanks

  • @Max

    I am confused, you uninstalled/reinstalled the patches AND VS?  Or you uninstalled/reinstalled the patches only?  The easiest way to avoid the issue is not install either patch, at least that way VS will still be launching.  Obviously you will still have the context menu bug, but having a working VS is probably more useful than having fixed context menus at this point.

    Have you tried JUST installing the first patch and NOT installing the second one?  If so is VS still not starting? If so have you tried downloading Windbg (free download) and using it to launch VS?  That would give us an idea as to what exception is happening during startup (which is generally what leads to the 'window cannot be created' problem).  If you need more detailed instructiongs on that feel free to e-mail me at rmolde AT microsfot DOT com and I can help out there, without that exception info there isn't much more I can do to help as we haven't been able to repro this failure on our side to investigate more.

    Ryan

  • @gm

    On your laptop you should only need the first patch.  Do note that WPF restricts the height of popups (which is what a context menu is) to 75% of the overall screen height, there is nothing we can do to avoid that restriction.  This means that even after the patch if your menu is so large that it would require more than 75% of the vertical real-estate to display in full that you will still get the scroll arrows, there is nothing we can do to avoid it in that situation as far as I know.

    Ryan

  • @Ryan

    Yeah, I am seeing the 75% ratio on the laptop you mention, but on the successfully patched Vista machine I am getting 100% height: The pop-up menu goes from the top of the screen to the top of the Windows task bar.

    Thanks

  • @gm

    Interesting, I thought WPF restricted to 75% of the screen, maybe I have to check that again, or maybe they are doing the 75% check before the nudging allowing us to 'subvert' the restriction (unintentionally).  If it is showing at 100% screen height on the Vista box I would imagine you should get the same on the laptop with just the first patch (the VS patch).

    Ryan

  • @Ryan

    I have sent a WinDBG log per E-mail. I hope you can find something.

  • @Ryan

    You are indeed correct, I feel a little foolish for not having tested it again since my install attempt (Laptop is not the primary development machine).  What I needed on this laptop to get 100% high popup menus was the VS patch only, and not the WPF patch.  So I am good to go on the Win7 x64 laptop as well.

    Thanks for your help.

    I have offered Matt Kaufman continuing help in debugging the update installer in case it helps, even though the machine does not need the update.

    Thanks again.

  • I also the the message "KBxxxxxxx does not apply, or is blocked by another condition on your computer." in both patches.

    VS10-KB2345133-x86 has the following installation log:

    OS Version Information: ...

    OS Version = 6.1.7600, Platform 2

    OS Description = Win2K8R2 - x64 Enterprise Edition

    Environment details: ...

    CommandLine = d:\a3227b8a2c454f0af0128f84\Setup.exe

    TimeZone = GMT Daylight Time

    Initial LCID = 2070

    Global Block Checks no blocking conditions found

    OpenFileMapping fails with last error: 6

    The handle to the section is Null

    OpenFileMapping fails with last error: 6

    The handle to the section is Null

    Applicability for Installing: evaluating each item...

    Determining state: of d:\a3227b8a2c454f0af0128f84\VS10-KB2345133.msp...

    evaluating ApplicableIf:

    Exists: evaluating...

    MsiXmlBlob: this patch is not applicable

    Exists evaluated to false

    Determining state of d:\a3227b8a2c454f0af0128f84\VS10-KB2345133.msp - not applicable

    I have visual studio 2010 ultimate Version 10.0.30319.1 RTMRel

    .Net framework Version 4.0.30319 RTMRel

    I also have visual studio 2008 Team System Version 9.0.30729.1 SP

    Can you please help-me with this issue?

  • Can you confirm that the WPF fixes include the memory leak fixes that were posted earlier?  The file version for both Presentationframwork and WindowsBase are .366 in this one whereas the earlier memory leak hotfix was 353.  

    I know they're not packaged together, but I'm not sure how the scrolling fix couldnlt include the memory leak issue as the file is newer.  Installing the other QFE wouldn't have any effect as the installer wouldn't overwrite the newer file.

    Am I missing something?

    Thanks

  • @Oren: If the 'memory leak' is the one address by support.microsoft.com/.../2297328 then you should be ok, the fixes in KB2413613 include the changes from KB 2297328.

    @Rui: Unfortunately not a lot of information to go on; it may be you have a newer hotfix that blocks the install of KB 2345133 or the hotfix registry information on your system might be corrupted somehow.

    This is the first we've heard of the VS hotfix failing to apply.  Please collect the install and patch logs using the collect tool: www.microsoft.com/.../details.aspx

    and send them to matt-kaufman [at] hotmail [dot] com.

  • Matt,

    Yes, that's the memory leak fix I was referring to, thanks!

  • I've been waiting for this patch for a while, and I'm glad to see it has made it out! It was one of those annoyances that didn't keep you for getting the job done, but it did add extra steps to a common repetitive task!

  • I've been waiting for this patch for a while, and I'm glad to see it has made it out! It was one of those annoyances that didn't keep you for getting the job done, but it did add extra steps to a common repetitive task!

  • With the help of Matt the "KBxxxxxxx does not apply, or is blocked by another condition on your computer" issue is fixed.

    The solution is running a visual studio 2010 product repair from the Programs and features, located on windows control panel.

    Then rerun the patch and the hotfix installed correctly.

    Thank you for the help Matt.

Page 3 of 4 (52 items) 1234