Page '312e8a59-2712-48a1-863e-0ef4e67961fc'

Question

When I click on the home-icon of Team Explorer, I get the following error:

Page '312e8a59-2712-48a1-863e-0ef4e67961fc' not found instead of all the options.

I have this error since I reinstalled the Visual Studio 2012 Ultimate trial and installed the Visual Studio 2012 Premium edition. Repair and reinstall didn't work out.

Answer 1

I faced similar issue. Running devenv /setup did not help me.

Just wanted to share some additional info:

At first, devenv /setup did not help me as well. Then I realized that I was using the wrong Visual Studio command prompt version.

Make sure that you run devenv /setup for the appropriate Visual Studio version.

For example: for Visual Studio 2013, use the "Developer Command Prompt" under the Visual studio 2013 "Visual Studio Tools" folder.

*And like it stated in the selected answer, run as administrator.

Answer 2

I had the same error in Visual Studio 2013 and tried:

Control Panel → Programs .... → Visual Studio → Repair

It did not work

devenv /setup

It did not work

devenv /clearcache
devenv /updateconfiguration

It did not work

And then THE solution:

• *Close all Visual Studio instances
• Delete the %LOCALAPPDATA%\Microsoft\VisualStudio\12.0\ComponentModelCache folder
• Start Visual Studio

It is explained in more detail in this blog post: When the EditorPackage does not load correctly

Answer 3

I had the same exact issue in Visual Studio 2013. I renamed ComponentModelCache to ComponentModelCache2, and it fixed it.

C:\Users\{..}\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache

Answer 4

To fix this, run this from the Visual Studio command prompt as administrator:

devenv /setup

It will not mess up your environment, and you can just continue to use Visual Studio afterwards was my experience.

Answer 5

After I reinstalled my Visual Studio 2012 Trial, I've never deleted the documents directory. In this directory there were some backup files. This maybe have caused the problem.

After deleting this directory and installing Visual Studio 2012 Premium again the problem was solved.

Answer 6

Running Visual Studio as administrator resolves this for me.