[prev in list] [next in list] [prev in thread] [next in thread] 

List:       patchmanagement
Subject:    RE: Windows Installer 3.1 build numbers
From:       "Allen McGuire" <amcguire () flad ! com>
Date:       2005-05-16 20:33:44
Message-ID: 002901c55a56$8e0f6cb0$ea1e010a () L1617
[Download RAW message or body]

A new "Microsoft Windows Installer 3.1" package has been published on 5/15
around 8:00pm PST to resolve the download failure issue.  The update id of
the latest package is B166A6A9-398B-4C81-B8DB-2043CF0672A1 and revision is
101.  All other Windows Installer 3.1 packages are expired.  Please decline
all the expired packages and approve the latest package.

The new version of Windows Installer 3.1 package will be installed only if
the file version of %windir%\system32\msi.dll is less than 3.1.4000.2435.
Some of the previous packages released over the last few days also had the
same version of msi.dll and hence those machines are likely to have
installed that package. (especially Windows 2000 machines).

The last few re-releases of the package did not change the binaries that
will be installed on the machine. There were only changes in the detection
logic.

-----Original Message-----
From: Richard_May@Edwards.com [mailto:Richard_May@Edwards.com] 
Sent: Monday, May 16, 2005 11:22 AM
To: Patch Management Mailing List
Subject: Windows Installer 3.1 build numbers


"Michael Curley" <Michael.Curley@xdctech.com> wrote on 05/14/2005 11:20:54
AM:

> This may not be the most sage thing to do, but at least now my WSUS
> clients are continuing down the path of patchedness.

Another one just appeared on WSUS.  However, the version numbers of the
files look to be the same as the last package.  Maybe MS modified the
install behavior a bit?

The downloadable on MS's site contains MSI.DLL ver. 3.1.4000.2435.
MSIEXEC.EXE, MSIHND.DLL, MSIMSG.DLL, MSISIP.DLL are all 3.1.4000.1823.  I
spot-checked a couple of machines that had downloaded the previous
Installer 3.1 package from WSUS and the version numbers of their files are
the same.

RM <--- has users getting sick of the Update bubble already.



---
PatchManagement.org is hosted by Shavlik Technologies

To unsubscribe send a blank email to
leave-patchmanagement@patchmanagement.org.
If you are unable to use this unsubscribe address (because you've changed
mail
accounts or your from address doesn't match the address known by the
listserver)
you can still unsubscribe by sending an email to the unique
'List-Unsubscribe' 
address listed in the header of each email.


---
PatchManagement.org is hosted by Shavlik Technologies

To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org.
If you are unable to use this unsubscribe address (because you've changed mail
accounts or your from address doesn't match the address known by the listserver)
you can still unsubscribe by sending an email to the unique 'List-Unsubscribe' 
address listed in the header of each email.
[prev in list] [next in list] [prev in thread] [next in thread]