Answered by:
Error during setup: "Some components must be installed in ..."

Question
-
I'm trying to reinstall VS05 on my Server 03 dev platform. I did a first install of VS05 after SQL 2005 was installed, and the SQL-related designer packages (report designer, etc.) would not load in VS. (SQL had installed the mini-VS2005 with these packages.)
So, I uninstalled VS05 and SQL05 to start fresh. Now I can't get VS05 to install. I get a message "Some component must be installed in C:\Program Files\Microsoft Visual Studio 8\ directory. Check that you have write permissions and enough space in that directory". There is plenty of room for the setup options I selected. The same thing happens if I select an alternate drive letter that has 20GB free. I've tried this logged in as Administrator, too.
Any ideas what is causing this?
Update: I took a wild guess on the possibility it might be due to the fact that I have several partitions mounted as folders instead of with drive letters. My DVD drives are also mounted as folders. I unmounted drives from folders and retried Setup. This time it completed normally. I remembered I did not have drives mounted as folders the first time I installed VS.
This would seem to be a bug in VS Setup, if it can't handle this configuration.Monday, February 5, 2007 2:44 AM
Answers
-
It doesn't seem like Windows' support for mounting drives/partitions as folders really works yet. There are some known issues posted in the KB re failing to delete files because the Recycle Bin can't handle folder mounts, etc. The mounts seem to stick with the partition rather than as a 'mounttab' equivalent in the registry. For example, partitions I had mounted as folders under Server were also similarly mounted in the root of my XP partition in my dual-boot rig, and this causes the paths relative to <i>either</i> root partition to be simultaneously active under either OS, which is not good at all. A given partition should not have duplicate mount points.Wednesday, February 7, 2007 8:07 PM
All replies
-
You are right..it happened for me too....there seems to be a bug in VSWednesday, February 7, 2007 6:18 PM
-
It doesn't seem like Windows' support for mounting drives/partitions as folders really works yet. There are some known issues posted in the KB re failing to delete files because the Recycle Bin can't handle folder mounts, etc. The mounts seem to stick with the partition rather than as a 'mounttab' equivalent in the registry. For example, partitions I had mounted as folders under Server were also similarly mounted in the root of my XP partition in my dual-boot rig, and this causes the paths relative to <i>either</i> root partition to be simultaneously active under either OS, which is not good at all. A given partition should not have duplicate mount points.Wednesday, February 7, 2007 8:07 PM
-
I too am having this problem all of a sudden after uninstalling Team Suite (VS2008 beta2) and reinstalling it. but message reads:
Some components must be installed in directory. Check that you have write permissions and enough space in that directory"
Notice the space before "directory"...obviously the path is missing, so I have no idea where to check for this.
I have 3 available drives showing in the installer and I can't install on any of them: C,F,G.
I've tried rebooting and changing the drive letters around but no success.
Has anyone solved this problem? There are VERY few posts regarding this error.
Thanks,
Caesar
Saturday, October 20, 2007 1:35 PM -
Hi,
I have met the same problem with VS 2008 . I solved it by permit the USER GROUP to write in NTFS C partition.
Good Luck
Mars
Monday, March 17, 2008 1:15 PM -
I had to extract the files from an ISO image and put them on my hard drive in order for me to make it work.
- Proposed as answer by VikasBitin Wednesday, February 2, 2011 10:41 AM
Saturday, August 2, 2008 6:29 AM -
Had this issue when installing VS2008 on Win7. The problem was resolved by not running the install from a mounted ISO. Copy the files to the hard drive prior to installing.
Dag- Proposed as answer by DAG_BOYE Tuesday, February 17, 2009 11:00 AM
Tuesday, February 17, 2009 10:59 AM -
I too had the problem with VS2008 on Windows 7. As mentioned, the image mount was the cause of the problem
- Proposed as answer by _Jarrod_ Monday, May 18, 2009 7:16 PM
Friday, March 13, 2009 4:16 PM -
I had the same problem.
I extracted the iso to a folder on my hdd, and ran setup from there ... ran perfectly.
All things are possibleMonday, May 18, 2009 7:17 PM -
"there seems to be a bug in VS" -
They seem to spend their $ on advertizing VS. They should be spending there $ on writing good .NET documentation and developing good tools.
Tuesday, June 30, 2009 2:09 PM -
I had this same problem running ISO DVD when double-clicking Setup.exe. When I clicked Autorun.exe instead, it installed fine.Monday, July 5, 2010 8:19 PM
-
Here's a workarround:
- do the installation as you normally would
- after it fails open the log file dd_error_vs_procore_90.txt to find out which drive the setup program fails to access (in my case this was J:) ... (the log file is located under C:\Program Files\Microsoft Visual Studio 9.0\Microsoft Visual Studio 2008 Professional Edition - ENU\Logs\)
- plug in an USB memory stick with some free space on it
- start the Computer Management console and goto Storage -> Disk Management
- locate the volume which uses the drive letter from the log file (step 2.)
- change this letter to something other than the original value (in my case I changed it from J: to N:)
- locate the volume in which the USB memory stick was mounted and change it's drive letter to the one from the step 2. (J: in my case)
- run the setup again - it should run fine now
After completing these steps you can rearrange the drive letters back to the original state.The USB stick used in this workaround will remain unchanged - nothing will be written to it.
P.S.There's a case on Microsoft Connect which addresses the same issue (the same workaround can be found there):Tuesday, July 6, 2010 11:24 AM -
Thanks! Autorun.exe worked for me as well.
Wednesday, February 16, 2011 3:21 PM -
I have solved this issue in my pc today in the windows seven professional trying to install visual studio 2010.
Go to the properties of the disk where you'll install the program.
In the tab Security click on Advanced icon
Go to the tab Effective Permissions and select the group Users.
Go to the tab Permissions, select the group Users and click on "Change Permissions"
Click on the group Users, click on Edit, and select the option "Full Control".
Apply the changes and be happy!
Obs.: Sorry if i sad something wrong, I'm learning english yet, i'm brazilian.
- Proposed as answer by Er.asique Monday, June 13, 2011 2:35 PM
Tuesday, March 15, 2011 1:22 AM -
I've gone round and round on this myself, trying a lot of the solutions I read about to little avail. It turned out in my case at least it seemed to be a problem with the drive letter of the DVD drive I was using.
I have a C: and D: partition on drive 0, and two other drives E: and F:, so my DVD drive was G:. Looking at the installation log I saw it was trying to do something on drive E:, which should have been okay if it was writing. I took a wild guess that it was looking for something on the DVD and had assumed that it was drive E:. I just disconnected the E: and F: drives and changed the DVD to drive E: and it was happy.
Don't know why, don't care; it's done.
Friday, April 1, 2011 3:50 AM -
-
unfortunately it isnt as easy as that. if you are trying to install from a mounted ISO, you will encounter this problem regardless.
As others have already stated, the fix here is to copy the contents of the iso locally
Monday, April 2, 2012 11:30 AM -
Hi Ceeteeuk,
Thanks It's work for me also...
Thanks
Vittalaranga
Saturday, July 28, 2012 4:00 AM -
I was running autorun.exe and got the error. Then I tried setup.exe and that worked.Thursday, September 20, 2012 1:27 AM
-
Couldn't agree more, so infuriating, not to mention a waste of valuable time to try to chase down these bugs!Friday, December 14, 2012 11:03 PM