Adopting Windows Installer 4.5

re: Adopting Windows Installer 4.5

Paul Bunyard — Fri, 15 May 2009 20:41:38 GMT

Can any body help? my windows installer does not work? I cannot install programs or unistall them?

re: Adopting Windows Installer 4.5

rishu — Mon, 20 Apr 2009 12:05:16 GMT

i need to downlaod a Microsoft Windows Insttaller 4.5 /5.0 XP SP2+, Server 2003 SP1+, Vista, and Server 2008

re: Adopting Windows Installer 4.5

gautam — Mon, 20 Apr 2009 12:02:46 GMT

I'm attempting to adopt Windows Installer 4.5 by integrating KB942288 into a Windows XP SP3 installation source, and I think there is a bug in the integration routine. When I install the update on its own, everything seems to work fine. But when integrating the update, the following registry entry is not getting set properly:

"HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\MsiInstaller\EventMessageFile"

The update_sp3qfe.inf file says this value should be "msi.dll", but when running "msiexec.exe /regserver" the value gets set to "msimsg.dll". It appears that in Vista and Windows7 the msimsg.dll file works fine as the message file, but it does not work in XP; XP needs to use the msi.dll file as its message file. Maybe this is just a bug in the msimsg.dll file not working properly in XP?

This causes a problem when viewing the Application Eventlog. None of the MsiInstaller events display properly, and have the below text in the description field. "The description for Event ID ( xxxx ) in Source ( MsiInstaller ) cannot be found. etc..." This text means the defined EventMessageFile is incorrect. Once I manually change the EventMessageFile value, the event log entrys read as they should.

Thanks for your time.

I also posted this in the microsoft.public.win2000.msi discussion groups, so i'm sorry for the duplication, but I honestly didnt know where best to post.

Windows Installer 4.5 does not work on Windows Home Server

aspen8102 — Fri, 17 Apr 2009 02:03:57 GMT

I created a MSI package which has an embedded msi package (I used the chained msi method in InstallShield 2009). This chained MSI package installer works on XP, but it failed to install on Windows Home Server. Does anyone have suggestions?

(I downloaded Windows Install 4.5 for Windows 2003 server, because there is no version for Windows Home Server)

re: Adopting Windows Installer 4.5

Chea Manit — Sat, 11 Apr 2009 06:35:03 GMT

i need to downlaod a Microsoft Windows Insttaller 4.5 /5.0 XP SP2+, Server 2003 SP1+, Vista, and Server 2008

re: Adopting Windows Installer 4.5

Tim Owers — Tue, 07 Apr 2009 16:27:20 GMT

Can anyone explain why on some systems, both MSI 4.0 and 4.5 versions of dialog MsiRMFilesInUse will report only PID's instead of the actual names? I have searched high and low for the smallest of clues yet have found absolutely nothing! If it helps, this only applies to windowless processes, i.e. services.

Many thanks,

timowers@gmail.com

Can't tell if installed failed or not. Where do you go for support?

SteveU — Fri, 27 Mar 2009 23:31:08 GMT

Installing Windows Installer 4.5 does not say if it is successful or not. When I go to Services Windows Installer is not there.

I believe that either .net 3.5 or Live Setup tools or OMNItech support caused problems with Windows Installer.

Where do I go for help as I have followed all of the general suggestions on technet and other sites in the web

I have tried registering

I have tried totally uninstalling and reinstalling and I do not see the service.

Ironic that windows installer can't install windows installer.

re: Adopting Windows Installer 4.5

foleys — Wed, 25 Mar 2009 17:37:58 GMT

"HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\MsiInstaller\EventMessageFile"

Thanks for your time.

I also posted this in the microsoft.public.win2000.msi discussion groups, so i'm sorry for the duplication, but I honestly didnt know where best to post.

re: Adopting Windows Installer 4.5

David Gardiner — Mon, 23 Mar 2009 07:32:40 GMT

Slightly off-topic but I couldn't find an explanation for how to install multiple packages using msistuff, which is implied by the following paragraph in the Best Practices page.

"Do not use a repackaging tool to consolidate several Windows Installer packages into a single package. Instead you can use the Msistuff.exe tool to configure the Setup.exe bootstrap executable to install the packages one after another."

-dave

No Single Redistributable

Nicholas Piasecki — Thu, 19 Mar 2009 07:28:41 GMT

Not having a single redistributable is a royal PITA. Who cares if there are different installation technologies? That doesn't stop you from writing a bootstrapper (say, Instmsi45.exe) that launches/downloads the correct installer based on the platform that the bootstrapper detected.

Now *I* have to do all that myself just to provide a seamless prerequisite install. And our application can be installed on Windows XP, Server 2003, or Vista. Sigh....