Well, shoot. I have a machine that had the beta installed on it. I went
through both a manual and the automatic tool uninstaller for this, but I
can't get VS2005 to install. Even though I've used both msiinv.exe and XP's
msicuu.exe to uninstall anything .NET 2x-related, Setup keeps telling me that
I have the Microsoft .Net framework 2.0 installed and the Microsoft Windows
Installer 3.1 installed. And when it tries to set up the remaining components
- like the Document Explorer 2005 - it faults and fails the setup.
It's maddening because I've tried everything I can think of to find and kill
anything from the Betas, including manually going through the list. The .Net
framework 2.0 is either NOT installed on my machine or it is very good at
hiding. How do I kill these files and allow the setup to run sucessfully?

Signature
- elvisboats, a Camarillo, CA-based programmer
Michael D. Ober - 21 Dec 2005 14:28 GMT
Format/Reinstall windows. This is one of the risks you take when working
with Beta software.
Mike Ober.
> Well, shoot. I have a machine that had the beta installed on it. I went
> through both a manual and the automatic tool uninstaller for this, but I
[quoted text clipped - 8 lines]
> framework 2.0 is either NOT installed on my machine or it is very good at
> hiding. How do I kill these files and allow the setup to run sucessfully?
Elvisboats - 21 Dec 2005 17:42 GMT
Yeah, I see that's what MSFT recommends... Unfortunately that's not an
option. My box has a lot of stuff on it that would take too much time to
recreate. Since the problem seems to be orphaned registry keys / Setup
detecting an installation of Framework 2x that's not there, maybe somebody
out there knows how to isolate and fix this particular issue.

Signature
- elvisboats
> Format/Reinstall windows. This is one of the risks you take when working
> with Beta software.
[quoted text clipped - 19 lines]
> > framework 2.0 is either NOT installed on my machine or it is very good at
> > hiding. How do I kill these files and allow the setup to run sucessfully?
Patrick McGovern - 21 Dec 2005 18:19 GMT
> Yeah, I see that's what MSFT recommends... Unfortunately that's not an
> option. My box has a lot of stuff on it that would take too much time to
> recreate. Since the problem seems to be orphaned registry keys / Setup
> detecting an installation of Framework 2x that's not there, maybe somebody
> out there knows how to isolate and fix this particular issue.
i had this same problem and after using the clean tool it still wouldnt
install until i actually logged on as the local administrator. i resisted
this for a couple of days because i was sure it wouldnt matter since my id
was part of the admin group.
>> Format/Reinstall windows. This is one of the risks you take when working
>> with Beta software.
[quoted text clipped - 23 lines]
>> > hiding. How do I kill these files and allow the setup to run
>> > sucessfully?
guy - 04 Jan 2006 12:47 GMT
I had similar problems, I have a url to the fix but its on my home pc, i can
send to you on Saturday if you can wait
send email to guy_swettenhamAThotmail.com
replace AT with @
cheers
guy
> Well, shoot. I have a machine that had the beta installed on it. I went
> through both a manual and the automatic tool uninstaller for this, but I
[quoted text clipped - 8 lines]
> framework 2.0 is either NOT installed on my machine or it is very good at
> hiding. How do I kill these files and allow the setup to run sucessfully?
Anand - 16 Jan 2006 14:15 GMT
I am having the same issue.
When I try to use the tool that is suggested (as unofficial) to cleanup
previous installs - by Microsoft in the readme doc, it says it cannot cleanup
....
There was another tool which was posted in one of the msgs on this
newsgroup, it runs ok but does not resolve the problem.
I tried manually deleting any Visual Studio related folders from my PC and
then removed some references to dxplorer.exe (Document Explorer) but did not
help!
The installation fails in trying to install Document Explorer 2005 and then
says it did not even attempt to install the actual VS2005.
Any tips from MS folks?
thanks

Signature
Anand
> I had similar problems, I have a url to the fix but its on my home pc, i can
> send to you on Saturday if you can wait
[quoted text clipped - 18 lines]
> > framework 2.0 is either NOT installed on my machine or it is very good at
> > hiding. How do I kill these files and allow the setup to run sucessfully?
poc0123 - 28 Feb 2006 21:57 GMT
hello
i just experienced the same problem but with installing production version:
the vs 2005 install on my ibm t43 running win2kSP4 failed because of the
document explorer 2005 component returned an unexpected value...
Microsoft Document Explorer 2005: [2] Component Microsoft Document Explorer
2005 returned an unexpected value.
setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in
ISetupManager::InstallManagerHelper() with HRESULT -2147023293.
setup.exe: [2] Component error string not specified in
ISetupManager::AddToActionResultCollection()
VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not
installed.
VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Professional
Edition - ENU was not attempted to be installed.
anybody?
> I am having the same issue.
> When I try to use the tool that is suggested (as unofficial) to cleanup
[quoted text clipped - 36 lines]
> > > framework 2.0 is either NOT installed on my machine or it is very good at
> > > hiding. How do I kill these files and allow the setup to run sucessfully?