Search
Active

70
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 487382
Opened: 9/1/2009 1:05:25 PM
Access Restriction: Public
2
Workaround(s)
48
User(s) can reproduce this bug
After installing Visual Studio 2008 SP1, if you attempt to add or remove any Visual Studio 2008 features via the add remove programs in windows, you receive an error similar too "A selected drive is no longer valid". I encountered this when attempting to add x64 compiler for c++. The only information I can find on this is at: http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/2f3d0378-3175-49ae-acb7-012594a1bf3c

This suggests that you must uninstall SP1 prior to making any changes to the install. This dose not sound like a solution in my opinion.
Details (expand)
Product Language
English

Version

Visual Studio 2008 SP1
Operating System
Windows Vista
Operating System Language
English
Steps to Reproduce
Install Visual Studio 2008;
Install Visual Studio 2008 SP1;
attempt to add or remove Visual Studio 2008 Feature via Windows add remove programs;
Actual Results
receive error "A selected drive is no longer valid"
Expected Results
ability to add or remove Visual Studio 2008 Feture.
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 9/3/2009 at 12:30 AM
Thanks for your feedback. We are routing this bug to the product unit who works on that specific feature area. The team will review this issue and make a decision on whether they will fix it or not for the next release.

Thank you,
Visual Studio Product Team
Posted by Walt Ritscher on 9/28/2009 at 5:51 PM
This is lame. There shouldn't be a need to uninstall VS 2008 in order to add or remove features. Isn't that the reason Microsoft created the msi installer and product features in the first place.

FWIW, I installed from an ISO file.
Posted by Waternymph on 10/2/2009 at 12:46 AM
Agree, very much agree with Walt! This is no serious solution. MOreover, this voting system is unfair. Google on "a selected drive is no longer valid" and you will find much, much more complaints than votes here. Not everyone takes the trouble of logging in and voting here, after having spent hours trying to add/remove components to an installed version of Visual Studio. This is just the tip of the iceberg!
Posted by Kondzio on 10/8/2009 at 8:50 AM
This is horseshit. Why can't you get it right the first time instead of patching the fix of the patch that was fixed by a previous patch. This Microsoft's MO is getting really annoying. I am at work and cannot afford to be wasting half days on uninstalling and re-installing things because you guys can't get your sh*t together. Charging this much for a product and releasing half-baked code is exactly the reason why your position in the market is and will continue to slip.
Posted by Carla_in_FL on 10/8/2009 at 12:13 PM
Agree with all the posts here, especially with Waternymph!
I took the trouble, over 15 minutes of my time, to reset my password, wait for emails, and fill out the requested info, before I could get here to agree with the comments already posted.

I am implementing MSVS 2008 in the builds for our newest Oracle PeopleTools release. This bug will affect every developer in our organization. The workaround is inadequate, no matter what internal documentation I provide to our dev organization.
Posted by John S Peterson on 10/8/2009 at 10:34 PM
Why haven't you updated SP1 so that this doesn't happen?
Posted by rcil on 10/22/2009 at 1:14 PM
This really does suck. I just wanted to install the x64 tools so I could try porting some of our apps. Now I find that I first need to remove and reinstall VS2008, just because I installed VS2008SP1! That's about 3 hours wasted.
Posted by Hello, I'm a Mac. on 10/29/2009 at 1:07 AM
Hello, I'm a Mac.
Posted by GeorgeZh on 11/2/2009 at 6:59 AM
Uninstall SP1 is not working any more. It'll show following errors and rollback the uninstallation:

Error 1402. Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Midrosoft\Updates\\SP1\KB945140. Verify that you have sufficient access to that key, or contact your support personnel.

I'm the admin on this box. It's XP SP2.

I checked the registry, it seems missing "Microsoft Visual Studio 2008 Professional Edition - ENU" before SP1 in above path. There are two \ in the path.
Posted by Tanveer on 11/7/2009 at 3:06 AM
This is completely ridiculous. Even when doing a no-op update this error message pops-up. FWIW, I am running Windows 7 x64 Ultimate. I even copied SP1 downloaded files back to %temp% in hopes that it would find the drive but still nothing.

Some excerpts from msi logs:

From: dd_install_vs_vstscore_90.txt
[11/07/09,15:56:26] Setup.exe: AddGlobalCustomProperty
[11/07/09,15:56:26] VS70pgui: ***ERRORLOG EVENT*** : Unable to retrieve the install directory for in COptionsPage::IsGoodAllComponenentsPath
[11/07/09,15:56:26] vs70uimgr: Entering DisplayMessage() method.
[11/07/09,15:56:26] vs70uimgr: DisplayMessage_START:A selected drive is no longer valid. Please review your installation path settings before continuing with setup.
[11/07/09,15:56:32] vs70uimgr: DisplayMessage_END:A selected drive is no longer valid. Please review your installation path settings before continuing with setup.
[11/07/09,15:56:32] VS70pgui: A selected drive is no longer valid. Please review your installation path settings before continuing with setup.

From dd_error_vs_vstscore_90.txt:
[11/07/09,15:56:26] VS70pgui: [2] Unable to retrieve the install directory for in COptionsPage::IsGoodAllComponenentsPath

My recommendation for the original reporter of this bug is to upload their msi log files as attachments for installer team to figure out which particular directory can't be found during maintenance, if they haven't already.
Posted by BMan28 on 11/8/2009 at 12:43 PM
This is rediculous. Come on M$ get a true solution for this in place.
Posted by MihaMarkic on 11/15/2009 at 3:31 AM
I join the protest. For developers Visual Studio has to be a robust tool even when it comes to adding or removing its features. As for now I am really scared to uninstall anything because I have a lot of various fixes and updates listed as installed and I am really scarred to mess it beyond repair.
Posted by Chris Hance on 11/16/2009 at 10:57 AM
The addition of Managed C++ appears to be working now, so I guess the workaround of uninstalling SP1 and any other updates is successful on XP 32-bit. But thanks a bunch for wasting a significant amount of time. I recalled mapping a drive during the MSDN installation from network media, so I dug through the registry to check what drive letter I used, mapped it again, and ran through the change/remove process for the third time before finally searching the web in frustration. If you're not going to make it possible to change anything after SP1 install, could you at least make an error message pop up as soon as the installer notices that VS has been updated? One that indicates the steps we'd need to take, instead of leading developers who have better things to do on (yet) a(nother) wild goose chase?
© 2009 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement