Visual Studio 2008, new looks, new features and probably with new bugs too. Well I got hit by one, by the first time itself as I started this damn Microsoft product. I installed Visual Studio 2008 with C# and C++ feature. I was able to create C# based projects but not C++ based ones. It said some strange thing like “Creating project <nameofproject> …. Project creation failed”.
After weeks of searching for solution, I finally found one. Following steps worked for me.
Problem is with HKLM\SOFTWARE\Classes\VSWizard.VsWizardEngine.9.0 registry key. Either it is not there and even if it is there, the permission thing is not correctly set. So, if it is not there, then you can create it using following command.
regsvr32 C:\[Visual Studio installation dir]\Common7\IDE\VsWizard.dllMake sure you did this as Administrator.
Then, you will have to set the permissions for the normal users and administrators. As well as, set the owners. The important keys are VSWizard.VsWizardEngine.9.0 and VsWizard.WizCombo.9.0
Run the regedit as Administrator and edit the permission as well as owners for these two entries. Make the administrator as Owner and give full control to all the users and administrator. Well, it may say that is not allowed but you should be able to do this after setting the owner. Make sure you check “Replace owner on subcontainers and objects” in the Owner tab of Advanced security settings.
You should set permissions and owners for all the sub entries of VSWizard.VsWizardEngine.9.0 and VsWizard.WizCombo.9.0
Well guys, this worked for me. Hope it will work for you too.
Credits: Various forums and blogs.
Filed under: Visual Studio | 18 Comments
Tags: Project creation failed, Visual Studio 2008, VSWizard.VsWizardEngine.9.0
Unique Hits
Visual Studio 2008 “Project Creation Failed”
This is due to some assembly redirects that are added to the devenv.exe.config file by installing the GAX (Guidance Automation Extensions).
Here is the fix, and it’s an easy one:
1) Navigate to: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE in Windows Explorer
2) Load devenv.exe.config in your favorite text editor.
3) Find this string: “Microsoft.VisualStudio.TemplateWizardInterface”
4) Comment out the element so it looks like this:
5) Restart Visual Studio 2008.
Hi Selva,
You are right. But, I think this GAX solution is the case only with the beta release. The later releases have this devenv.exe.config issue fixed. However, even if this devenv.exe.config is fixed, they still have this project creation failed issue. That happened in my case.
And I came around with this solution.
Hey Selva.. Thanks man, i follwed exactly what you have mentioned and now the problem with VS is solved …
Hey Selva, I could not found the key mention in the config file. But the Solution mentioned in original blog works for me, ThanX for solution
I didn’t have the key that selva mentioned.
I tried to run regsvr32 and got an error becuase it wasn’t run as administrator (0×80070005).
I then realised that an alternative to implementing these fixes is to run visual studio 2008 as an administrator.
This worked for me.
Hey, I am a bit of a noob when it comes to Visual Studio and registry editing, but this worked perfectly for me. Thanks a lot – now I can finally do some Uni work!
Aaaaaack!!! VS is sooooo aggravating, sometimes. Anyways, after following these instructions, I can finally create new projects now – imagine that. Thank you, thank you!! FYI – checking “Replace owner on subcontainers and objects” in the Owner tab of Advanced security settings when I changed ownership did not work for me. I had to leave that option unchecked, and just manually change the owner (and permissions) on each of the sub-nodes… no big deal. Bottom line – fixed!
Hi there,
Thank you for this comprehensive solution, it finally worked for me!
I had to manually set permissions for the sub nodes also, but recognized a different issue:
The VsWizard keys started out as having no sub-nodes and no set data. I couldn’t delete them, nor did I have permission to check the box to replace subcontainers and objects.
This is probably because I am a noob to Vista and just set the permissions on the pre-existing SYSTEM and msiserver groups.
By adding additional users (in my case ‘administrator’ and ‘tony’) to the list and setting the same permissions for those, all my problems were solved. The sub-nodes became visible and I could manually update them.
Yes, thank you all buddy
the above commenting out thing work for me.
thanks again it saves a lot of time.
Cheers,
A quick adjustment for users of Vista 64-bit.
This solution will not function correctly for 64 bit (at least it didn’t for me) because the registry key is different. Instead of “HKLM\SOFTWARE\Classes\,” look in “HKLM\SOFTWARE\Wow6432Node\Classes\”
Or, for simplicity’s sake (and in fact how I found this), just search the registry for “VsWizard” and you’ll eventually stumble across it. The rest of this fix works just the same.
It worked!!! I love you!
Great solution ! It worked for me.
Thank you very much! now everything works fine.
Thank you Selva.. It works
Thanks for the post – helped me a lot.
Slava’s solution worked for me: VS 2008 Pro, on XP pro SP3 (32 bit).
Yayyyy…it was like a marathon…one day searching and trying a lot of things and finally it works. THANKS very much for the post
)))