Windows Update dependencies automation

Ditto | at | by Mike

Courtesy of our beta insider, Ditto.

Dear Beta Tester,

Currently, many Hotfixes produced by Windows team already include the dependent binaries. The dependent binaries are picked up from the current service pack even though the dependency binaries might have been introduced in the N-1 (or earlier). Before an update is published, the test team must check the bugs fixed for the dependent binaries in the current service pack. This process increases the risk and time it takes to test the extra payload and reported bugs. This also applies to regular Hotfixes where the customer running the latest service pack is put at the same risk as someone running an older service pack.

The purpose of this tool is to relieve both the test team and the end user of this risk by managing the package dependencies automatically. It will not be released to the Windows Update live site.

We have released four beta versions of updates built with this new binaries dependency technology. They are posted on the Windows Update V4 beta site.

Again, these items will not be released to the live site. Please uninstall the updates after the beta testing is done. Titles are as follows:

  1. Software Update Dependency Management Tool Beta for Crypto Components (KB835719)
  2. Software Update Dependency Management Tool Beta for Kernel Components (KB835721)
  3. Software Update Dependency Management Tool Beta for DS Components (KB835722)
  4. Software Update Dependency Management Tool Beta for Mobile Components (KB835723)

General testing information is located at the bottom of this mail. More testing information is posted at: http://beta.microsoft.com under Test Cases page (log in with your .NET passport)

These beta items are classified as Critical updates and are available through the Consumer site, Catalog site, and AU. They are offered only to Windows 2000 platforms and apply to English only. Other platform users should verify that this update is not offered to them. We need your help getting a lot of test coverage on these items.

Testing Information
Each item has a list of binaries for you to compare against your system binaries before and after you install. You'll find four sets of binary lists posted on the Test Cases page on the BetaPlace site. Please refer to the lists while you are testing.

Important Note
Before installing any of the four updates, please compare the binary files on your system against those in the list. If the file numbers on your system are equal to or greater than the file numbers on the list, those files won't be updated. If they are less, they will update. · With each scenario, please check the list of binaries to ensure all the files have updated. · Use Add or Remove Programs to uninstall this update before installing each subsequent service pack.

Testing Feedback

  1. Did the program install correctly?
  2. Which files are updated? What are the post-install binary file version numbers?
  3. Does the program work properly?
  4. What happens upon installation? Did any odd behavior occur after installation?

Our goal with this beta release is to evaluate the performance of the detection and installation segments of this content. The system should not crash after you install this update. Please focus your work on verification of how your system functions before and after the installation of this beta driver content.

The project will run for one month (4/14/2004 to 5/14/2004). We'd like to gather the majority of the data within the next two weeks. Please help us by initiating the beta testing as soon as possible.

The customer experience on the Windows Update site is very important to Microsoft. Your beta testing input has been and will continue to be helpful toward the release of an update package that represents the best of what Microsoft has to offer. If your computer is not running one of these operating systems with the specified hardware configurations, please verify this update is not offered to your system.

Bug Reports
Please include the following information when you submit a bug report:

  1. For tracking purposes, please include the KB###### in the bug report title for bugs related to the beta contents - (KB######)
  2. Detailed information and repro steps - Required
  3. The Windows Update.log file - Required (%WINDIR%\)
  4. The Luhist.xml file - Required (C:\Program Files\WindowsUpdate\V4)
  5. The Setupapi.log file - Required (%WINDIR%\)

If you encounter any trouble or have questions while testing this package, please send us feedback via a bug report or the Newsgroup.

Thank you very much!
Windows Update Beta Team