Partager via

All the Project templates missing in Visual Studio 2012

  • Article

 

Issue Description:

After installing Visual Studio 2012 successfully when we launch the IDE and click “New Project” all the Project templates are missing in the IDE.

Root Cause:

When we take a Procmon log while clicking “New Project” and check for ‘Access Denied’, we can find that devenv.exe doesn’t have permissions to access the below key

HKEY_CLASSES_ROOT\TypeLib\{DF848FFC-700C-4F55-B4E7-3338946DD300}

Which is the typelib for “C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\dteproperties.tlb”

Resolution:

1. Opened Registry and browsed to “HKEY_CLASSES_ROOT\TypeLib\{DF848FFC-700C-4F55-B4E7-3338946DD300}”

2. Observed that the logged in user isn’t having access to that key.

3. Logged in as administrator and gave ‘Read’ permissions to ‘Users’ on “HKEY_CLASSES_ROOT\TypeLib\{DF848FFC-700C-4F55-B4E7-3338946DD300}”

4. After this we were able to view all the Project templates in the IDE

Content By : Sarat Chandra

Comments

  • Anonymous
    August 21, 2013
    All the Project Templates were missing after my install too.  (I did not notice the issue for a week or so.)  Was reluctant to do a registry edit thus, on a colleagues suggestion, tried doing a 'repair' first.  In my case, the repair worked.  It did take several hours – a successful registry edit would have been faster.  Bredon

  • Anonymous
    October 30, 2013
    Thank you! This helps!

  • Anonymous
    November 07, 2013
    I have a problem where periodically some, or all, of the templates that came with VS disappear from the new project dialog. Templates installed by third parties, such as the Telerik KendoUI templates, remain. It's just the default templates. Sometimes it's all, sometimes it's not. For example, right now I'm missing the web forms and web api while the MVC3, MVC4 and the Telerik templates are available. So far, the only thing I've found that gets them back is to do a "repair" install from the Visual Studio 2012 Professional ISO that I download from MSDN. Any suggestions? The repair takes a very log time during which I'm pretty much out of commission. I haven't yet isolated the root cause of the issue. I only notice it if I try to create a new project which I do frequently to experiment before I implement a new feature or a bug fix in a production project.