I have tried installing Visual Studio 2005 on two different machines under Windows XP SP2 and have gotten voluminous errors reporting that a component could not be installed because it was currently being installed by another process.
After ONE WEEK of experimentation I have gotten it down to one single failure ...
***EndOfSession***[09/24/05,08:06:20] .NET Compact Framework 1.0 SP3: [2] Error code 1618 for this component means "Another installation is already in progress. Complete that installation before proceeding with this install.
"
[09/24/05,08:06:20] .NET Compact Framework 1.0 SP3: [2] Setup Failed on component .NET Compact Framework 1.0 SP3
***EndOfSession***
EXACTLY what do I have to do to correct this condition
... Thom
Compact Framework 1.0 SP3 - Error Code 1618
Manish Agnihotri
I have not had this much fun since Windows 3.1 ...
I have tried solving this problem multiple times. I do a full restore of two hard drives of a system that has ALL development tools uninstalled and ActiveSync installed. I then can run a "fresh" install of Visual Studio 2005.
When I do this I do a "Full" install and get a 1618 for some component. It is usually .NET Compact Framework 1.0 SP3 and .NET Compact Framework 2.0. The last time it was only .NET Compact Framework 1.0 SP3.
Please assume that I am "dumb as dirt" and tell me EXACTLY what I am supposed to do ...
Restore and install again.
Don't restore and install specifying repair.
Uninstall and then request an install.
Install and specify a specific component.
Custom install Full install repair Restore and custom install Restore and Full install
I was serious ... I have been at this now for about eight days. (I tired using an MSDN pre-paid incident for this problem and was told that support was not available for Visual Studio 2005 - yet.) I have run some permutational of this install about 30 times. I REALLY want to try out Mobile 2003 SE and Mobile 2005 development using Visual Studio 2005.
I assume that there are more than one activity (thread ) executing in the Visual Studio 2005 install and it is "stepping on its own foot".
I have executed nothing in Visual Studio 2005 since getting the last error except to submit these messages.
I will gladly try EXACTLY what you recommend and report the result.
... Thom
Anders E. Aabakken
1618 means another MSI is currently running. You have to wait until that install completes.
TechArtists
Morten Brun
I have moved on to RC and do not have any problem with it.
I heard from one other person who reported weirdness with Deta 2. We were both running with 3 Ghz + CPUs and 1 GB of memory. I wonder if this may have been causing the problems. POerhaps the problems only showed up in a fairlyu unconstrained environment
Thanks again.
... Thom
JGauthier
The install process is apparently changed since Beta 2. In Beta 2 there was a system reload in ghr middle of the install and in RC there is a reload at the end. I assume that Beta 2 was causing the colisons taht I noted earlier.
... Thom
karenpcg
It's my fault, I'm sure you're not as dumb as dirt :)
When you restore, Windows Update is probably deploying patches again to your machine which causes the 1618 error.
1618 problems occur when two setup programs are running at the same time (second one fails witha 1618).
Workaround if you see this happen again is to wait until all the patches are installed by windows update and then try installing VS.