Windows Installer 3.1 Update v1 to v2 fails

Aim -- I want to upgrade from Windows Installer (WI) 3.1 V1 to V2.

Motivation -- WI 3.1 V1 can cause problems during Windows Updates (e.g.
installation of .NET framework or Visual Studio 2005 silently fails)

Problem -- WI V1 has version number 3.1.4000.1823, WI V2 has version
number 3.1.4000.2435. After download of V2 and seemingly successfull
installation of V2 and reboot the WI version still is 3.1.4000.1823.

Solution -- Any suggestions? Chewing on my keyboard doesn't help.

Go to Add/Remove programs. Uninstall Windows Installer v3.1

Reboot

Install Windows Installer v3.1v2

<tmp4@nigeno.de> wrote in message
news:1132838934.994243.111550@o13g2000cwo.googlegr oups.com...
> Aim -- I want to upgrade from Windows Installer (WI) 3.1 V1 to V2.
>
> Motivation -- WI 3.1 V1 can cause problems during Windows Updates (e.g.
> installation of .NET framework or Visual Studio 2005 silently fails)
>
> Problem -- WI V1 has version number 3.1.4000.1823, WI V2 has version
> number 3.1.4000.2435. After download of V2 and seemingly successfull
> installation of V2 and reboot the WI version still is 3.1.4000.1823.
>
> Solution -- Any suggestions? Chewing on my keyboard doesn't help.
>

I already did the usual stuff: local installation, windows online
update, following a microsoft knowledge base article "The WI service
can not be accessed". Doesn't work.

Windows online update breaks with the following - undocumented - error
code: 0x800F0102
Local installation of v2 gets me v1 - although I de-installed v1 before

<tmp4@nigeno.de> wrote in message
news:1133166427.047443.205950@g49g2000cwa.googlegr oups.com...
>I already did the usual stuff: local installation, windows online
> update, following a microsoft knowledge base article "The WI service
> can not be accessed". Doesn't work.
>
> Windows online update breaks with the following - undocumented - error
> code: 0x800F0102
> Local installation of v2 gets me v1 - although I de-installed v1 before


Try a search?

Here's how I answered a similar question in October

http://groups.google.com/group/micro...20aa4d985b5a42

(Google Groups search for
0x800F0102 group:microsoft.*
- first hit
)


---