Install programming is terrible

I use SQL server 2005 for a year now at work and home.
The intsall process and logic is TERRIBLE compared to previuos versions.

The most common problem I get on developers machines is when they are using EXpress and then upgrade to the Developer or Enterprise edition.

Sql Server 2005 Express database instances get left in the registry or somewhere, and the next install sees it and refuses to install its instance.

The ARPWrapper.exe. tool in the boot strap can be run and you can see the instance there, but they is NO POSSIBLE WAY to remove it..

I have been woring on this for 2 days and really hoping someone has a fix for this.
I have tried the variosu registry HACS out there on the net, but no luck still.

I noticed that a huge proportion of the bogs in this formum relate to problmes around this issue and setup in general.

gedw99Here is the ouput form the ARWrapper.exe tool:

Its shows the express version, I cant get rid of the bugger, and its stopping me installing a default instance for the enterprise edition.
I am using the Developer server of SQL server in a x86 machine.
Any ideas? HELP !

The following components are installed on this server

MSSQLSERVER
Database Engine
[Version: 9.1.2047.00 Edition: Express Edition Patch level: 9.1.2047 Language: English (United States)]

Common components
Workstation Components
[Version: 9.1.2047.00 Edition: Enterprise Edition Patch level: 9.1.2047 Language: English (United States)]|||

Starting out a thread by using a title like this is probably not going to attract very many people to even answer the thread.

I have Express Edition along with Developer Edition on dozens of machines. Sometimes Express was installed first and sometimes Developer Edition was installed first. Not once have I ever had a problem with a blocked installation.

As for this one, stating the obvious, why don't you just install a named instance? Does it really matter whether it is a default instance or a named instance? You have to connect to the SQL Server anyway and that means specifying the SQL Server name, so whether you type in the machine name or machine\instance seems pretty irrelevant to me.