Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 27, 2013 05:49 AM by Michael Randrup
Nov 16, 2012 03:21 PM|LINK
Using VS 2012 Ultimate & Team Foundation Server (TFS). We code in C#, web apps, .csproj for our project files.
I am an Admin on my box, I am running VS 2012 in Admin mode. I am an Admin on my box, I am running VS 2012 in Admin mode. I am an Admin on my box, I am running VS 2012 in Admin mode. There, I said it three times. Don't ask in your reply. : )
I just installed VS 2012, got it hooked up to our TFS. Whenever I click (left mouse click) on any project folder in any branch I get a pop up error window: "Requested registry access is not allowed".
I tried using regedit to change permissions on the VisualStudio.csproj.11 (something like that) key. Turns out I don't have permission to change permissions on my registry.
Did I miss something during the install?
Any help is mucho-appreciated.
Nov 16, 2012 05:18 PM|LINK
At the suggestion of a teammate, I just finished Uninstalling/Reinstalling VS 2012. At first 'Launch' I received the same error (See below).
What the heck?!
This came without me doing anything, it must be a feature.
Nov 16, 2012 06:08 PM|LINK
I rebooted, went in to Registry, changed a setting in Google Chrome, exited and then put it back without problem.
Then went down to the Visual Studio area: HKEY_CLASSES_ROOT\VisualStudio.csproj.11.0 and got this (see below).
So now I’m thinking I have a registry error of some kind.
Nov 16, 2012 06:23 PM|LINK
As I'm trying to edit my registry to up the 'Permissions' on the affected folder(s) I notice the only folders giving me problems are the folders ending in "11.0" . All the others are fine. The 11.0 folders also do not have sub-folders.
Feb 27, 2013 05:49 AM|LINK
Yes, this is a very serious problem, mainly because you do not have access to restore the ACL's either (I havent found any). So re-installing, etc. will not help you.
I have the same issue (different error), when I try to add code to our TFS. I have created a bug on Microsoft Connect, please go Vote up this bug as important: