Windows Installer 4.5 Beta 2 Now Available!


Hello everyone —


I am pleased to announce that Windows Installer 4.5 Beta 2 is now available from the Microsoft Connect site. If you have not signed up for the beta yet, please do – we are listed as “Windows Installer 4.5” under the “Available Connections” section of the site. If you have already joined the beta, please head back to the Connect site and download the updated bits, tools and documentation.


This is our last planned beta release before we ship, so your feedback at this stage is especially important!


Thanks.


 – Tyler


PS: Due to some unfortunate timing, the Microsoft Connect team will be rolling out a new version of the Connect site on Saturday, March 22nd and the site will not be available from 10:00 AM and 2:00 PM (PDT). If you have issues accessing the beta program afterward, please leave a comment on this thread so we can follow-up on any issues.  


[Author: Tyler Robinson]
This posting is provided “AS IS” with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.

Comments (5)

  1. Windows Installer 4.5 Beta 2 Now Available!

  2. consumer4beta@hotmail.com says:

    Hey MSI team, pls help. MSI 3.1 on XPSP2 had stopped working so I uninstalled it, and now MSI 3.0 works properly but I tried reinstalling 3.1 and now I’m getting the error message "System must be restarted before installing to allow prior file update operations to complete". There are no pending rename or delete operations in the registry and I’ve tried restarting but still get the same error.

  3. The Windows Installer team released Windows Installer 4.5 Beta 2 recently. While not a lot has visibly

  4. vrapp says:

    Hello,

    I have a question…

    I noticed that ICE validation by ORCA 4 forgives ICE33 when information from Typelib table is duplicated in Registry table. Specifically, Wise Installer when adding COM object to the project always puts Typelib key in Registry, hence subsequent ICE33 when using ORCA 3; but validating the same package by ORCA 4 did not produce the warning. Could someone comment on this? is this not considered a violation anymore?