Registry Permission for Visual Studio 2012

Question

During the creation of the web application, I received the following pop-up message:

"Visual Studio does not have permissions to read template information from the registry, which is often caused by a registry permission problem."

Anyone have any solution? Please help me. I wana to see the new features of Visual Studio.

thanks

Answer 1

it may be quite late as an answer, but I tried this problem and found a solution on the msdn page: here is the original message with the message:

I ran into this problem with Visual Studio 2010 and Windows 7. At the moment, I did not find this source of problems, but I found that many Visual Studio users are encountering this. I tried Mike's solution to this problem, and he did more damage than anything else. It even made Visual Studio boot into Shell mode and say that the registration was invalid. Using System Restore, I canceled the changes made using the subinacl tool and the Michaels script (it was probably not designed for Windows 7, which caused the errors in the first place). Being a long-time visual studio user and a pretty good shooter, I knew that the subinal was the right tool to fix the problem, but the script was wrong for my percussion setup. I adjusted the script as follows: (this is a script package)

cd /d "%programfiles% (x86)\Windows Resource Kits\Tools" subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /setowner=domain\user subinacl /subkeyreg HKEY_CLASSES_ROOT\VisualStudio* /grant=everyone=f /grant=administrators=f /grant=system=f pause 

I tried to include the setowner command with grant commands (on the same line), but that would throw errors all the time. This script is corrected by MY "Requested registry access is not allowed" with Windows 7 and Visual Studio 2010. if you want to try this script command: follow Michael's instructions, but use the script provided in this post and replace "domain \ user" with the appropriate credentials data. You may also need to change the Windows Resource Set Path if you installed it in the diffrnet location or are not using a 64-bit OS. Before using this script, back up your registry.

I hope this helps!

* The original web page was: http://social.msdn.microsoft.com/Forums/en-US/c273b0e1-7f46-4065-afaf-4edf285d2531/vista-wpfapplication-requested-registry-access-is-not-allowed

Answer 2

I also had this problem. After that, user 2698666 failed. I stuck Process Monitor on it and found that there were more registry entries that caused the WDExpress problem. Thought I'd post my fix if anyone else had the same problem:

subinacl / subkeyreg HKEY_CLASSES_ROOT \ VisualStudio * / setowner = domain \ user

subinacl / subkeyreg HKEY_CLASSES_ROOT \ VisualStudio * / grant = every = f / grant = administratorators = f / grant = system = f

subinacl / subkeyreg HKEY_CLASSES_ROOT \ WDExpress * / setowner = domain \ user

subinacl / subkeyreg HKEY_CLASSES_ROOT \ WDExpress * / grant = every = f / grant = administratorators = f / grant = system = f

Answer 3

I had a problem with Visual Studio 13 where I wanted to add a webtest project for my newly created solution. I tried the above tricks to set the ACL, but that didn't work.

Finally, I used Procmon.exe to determine what visual studio was doing (including only the process name devenv.exe) and look for the result. Access denied. It will tell you which registry key is not available.

In my case, this caused a problem with the HKCR.webtest key (HKEY_CLASSES_ROOT.webtest). Respecting ownership and granting access to it helped solve my problem.

I do not know what the main cause of the problem is.

Answer 4

The above did not work for me, as I was constantly denied regedit, although I was an administrator.

I found this on another site:

 psexec -i -d -sc:\windows\regedit.exe 

psexec is available from Microsoft here

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

This gave me full registry access. I tried to provide the administrator with specific keys, such as above, but VS 2012 Express still threw this registry permission error. Therefore, I finally just added the Administrator to the permissions list of the entire HKEY_LOCAL_MACHINE \ SOFTWARE \ Classes \ directory in regedit. Then he gave the administrator full control.

It worked. Now I can create a project without this hellish mistake!

Answer 5

This issue has nothing to do with permissions in the context under discussion. The problem is due to the incorrect path to the template files in the registry due to testing the sloppy operating system. The wrong path causes an error when the user tries to start a new project and, true to the Microsoft style, displays a general and meaningless error message.

Here is the problem specifically. On some machines (assuming that C: is the main drive and user1 is the username and version of 2013), the location of the template files is C:\users\user1\my documents\visual studio 2013\projects . Unfortunately, the installation path recorded by the installer in the registry is C:\users\user1\documents\visual studio 2013\projects . Thus, it points to \documents , and the correct location is \my documents . Of course, look where your visual studio 2013\projects folder is located - documents or my documents - and change the registry key to the correct location.

In my example, the key is in HKEY_CURRENT_USER\software\Microsoft\VisualStudio\12.0\NewProjectDialog\MRUSettingsLocalProjectLocationEntries , the path is in the Value0 . Check it and change it to indicate exactly where your project folder is located.

Answer 6

Using Lanc Meldgard ProcMon was good advice and helped me. I just wanted to include an image of what denial of access looks like in ProcMon. I had to do this one registry key at a time - it was not the only one. It was very cumbersome and slow, but I was able to knock them one by one and give all the rights to everyone. (This part is also complicated, because I had to take responsibility, then close regedit, and then go back so that I can set permissions, you cannot do it all in one fell swoop).