Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

[Cross-Posted on StackOverflow.com as well because the question relates to development. Feel free to let me know where it best belongs.]

Hi all,

I'll try to bullet-point to keep it short:

Background / Issue

  • Trying to install ASP.NET MVC 3 RC on my Windows 7 machine.
  • Uninstalled other versions of MVC (2 and 3 Beta 1).
  • Ran the installer -- got a generic error, 2203.
  • Log files said that it was a permissions error on C:\Windows\Installer.
  • Checked C:\Windows\Installer -- sure enough, it's marked as read-only.
  • I un-checked "Read-Only" in the folder properties and applied. It appears to open the dialog and apply to all files.
  • However, when clicking properties again, the read-only box is backed to checked.
  • Checked the security tab of the folder -- both system and the Administrators group have full access.
  • I checked ownership -- the Administrators group is listed as an owner.
  • Verified that I'm in the system as an Administrator (in fact, the only account in the Administrators group besides Administrator).

So, what gives? Thanks in advance for any help you can provide!

share|improve this question
add comment

2 Answers

Right click on the installer package and select "run as administrator", see if it installs now.

Windows 7 User accounts are limited admin accounts, not full admin accounts like they were in XP.

share|improve this answer
    
Thanks Moab. I did run the installer this way, by default (I always run MSI installers this way). The end solution ended up being to take over ownership of the files (twice), and change the attributes (twice). Not sure why that procedure worked, but it did, so I'm not going to question it. :) Thanks for your help! –  SeanKilleen Nov 11 '10 at 19:39
    
I agree, never question things when they go right. :-) –  Moab Nov 14 '10 at 2:31
add comment
up vote 0 down vote accepted

The end solution ended up being to take over ownership of the files (twice), and change the attributes (twice). Not sure why that procedure worked, but it did, so I'm not going to question it. :)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.