Visual Studio 2013: Turn Off the Uppercase Menu

Tips Search

Visual Studio 2013: Turn Off the Uppercase Menu

  • Comments 28

NOTE: This is an older feature. I’ve updated the information for VS2013.


This is one change to Visual Studio that I’m not a fan of and I still continue to see a ton of posts on this change so thought I would share here as well. 


I always try to give credit where credit is due and I believe the earliest mention of this fix is by Richard Banks in his post 6\1\2012 here: 




Mixed Case is Your Friend

Okay so you really, really don’t like the Uppercase menu in VS2012 because you feel like it is shouting at you:

5-16-2012 7-50-41 PM



You would rather go back to mixed case for your menu:

5-16-2012 7-43-08 PM


Not a problem! Below are ways you can fix this feature in VS2013.




Manual Registry Change

WARNING:  Making changes to the registry can cause unexpected results so do any changes at your own risk!

  1. Open the registry editor and go to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General\
    (For Windows 8 Express go to HKEY_CURRENT_USER\Software\Microsoft\VSWinExpress\12.0\General)
    (For Web Express go to HKEY_CURRENT_USER\Software\Microsoft\VSWDExpress\12.0\General)

  2. Create a new DWORD value called SuppressUppercaseConversion set to 1

  3. Restart Visual Studio and you should see the change

NOTE: Watch your spelling if you are typing this manually.




If you like to “simplify” this a bit you can use PowerShell to run a nice script to make this happen.  However, if you haven’t used PowerShell before this may not be faster for you.

  1. Go to the Start button or (Start Screen in Windows 8) and type powershell then select the Windows PowerShell Entry:


  2. In the PowerShell window copy the script below and paste it in then press Enter:

    Set-ItemProperty -Path HKCU:\Software\Microsoft\VisualStudio\12.0\General -Name SuppressUppercaseConversion -Type DWord -Value 1


  3. Restart Visual Studio and you are good to go.
  • This also works with Visual Studio 2012 by changing "12.0" to "11.0"

  • Thanks! I don't like the shouty menu either

  • Showww

  • First MS gives us a "feature" then shows us how to turn it off.

  • I can't find that registry entry. I am on a new W8 installation and only installed VS2013 Express for Web...

  • Gawd, THANK YOU, finally....

  • It's idiotic that we should have to do this. Any designer with a minimal understanding of Gestalt theory knows ALL CAPS is bad design. Same goes for the stupid bland icons that some suit seems to have forced on MS apps in the Metro era.

  • Not again... I just completed a 1000+ deployment of VS 2012 with instructions to disable this. I ended up doing it manually for each system.

    I am NOT looking forward to doing this again when we upgrade to 2013... Is there a domain option for this nonsense?

  • All caps menus are not an issue, I just wanted to test and see the difference.

    But since lots of users seem to be raging about it, VS should add a simple switch to turn on/off.

  • Hey Craig,

    You could in theory create a domain group polilcy registry entry to set this options for all machines in your domain.

    Next time the user logs in, the policy would be applied and no more upper case menus..

  • Hey folks :)

    Sorry for the late reply to the thread but I just got back from an offsite conference and am catching up. I'll try to address comments as concisely as I can. In general I am most definitely NOT a fan of the all caps menu. There may be a good reason for it but I haven't heard one yet.

    BrunoLM -- Did you manage to find the correct reg path? I agree we should add a way to easily turn it off and I know there is a couple of extensions that will do that:

    Craig / cmb -- looks like a great solution to me and it ensures consistency.


  • While it's good that there's at least a manual way to do turn this nuisance "feature" OFF, it should be a SETTING in the options, not a registry HACK. (caps intentional)

  • Seems like this no longer works in the RTM version. Am I missing something here?

  • Oh, never mind, turns out the Express version checks a different registry key (WDExpress instead of VisualStudio)

  • Check out this extension.  Right now it is for VS 2012.  It turned the whole development back to a 2010/2008 look and feel, maybe just maybe Donny can upgrade it to support VS 2013

    NiceVS extension

Page 1 of 2 (28 items) 12
Leave a Comment
  • Please add 5 and 6 and type the answer here:
  • Post