Microsoft KB Archive/932224

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 10:26, 21 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Package Manager can install only the first package when you extract two or more packages to the same folder in Windows Vista

Article ID: 932224

Article Last Modified on 10/31/2007



APPLIES TO

  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise 64-bit Edition
  • Microsoft Windows Code Name “Longhorn”



Beta Information

This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

SYMPTOMS

In Windows Vista, the Package Manager tool can install only the first package when you extract two or more packages to the same folder.

For example, consider the following scenario:

  • On a computer that is running Windows Vista, you create a C:\Temp folder.
  • You download the following hotfix packages to this folder:
    • Windows6.0-KB929761-x86.msu
    • Windows6.0-KB932590-x86.msu
    These hotfix packages are for hotfix 929761 and hotfix 932590.
  • You run the following commands to expand the hotfix packages:

    c:\temp>expand c:\temp\Windows6.0-KB929761-x86.msu -F:Windows6.0-KB929761-x86.cab c:\temp

    c:\temp>expand c:\temp\Windows6.0-KB932590-x86.msu -F:Windows6.0-KB932590-x86.cab c:\temp

  • You run the following commands to install the packages:

    start /w Pkgmgr /ip /m:c:\temp\Windows6.0-KB929761-x86.cab

    start /w Pkgmgr /ip /m:c:\temp\Windows6.0-KB932590-x86.cab

In this scenario, Package Manager installs only the package for hotfix 929761.

When this problem occurs, information that resembles the following may appear in the Cbs.log file: 2007-07-25 13:17:05, Info CBS Pkgmgr: called with: "Pkgmgr /ip /m:c:\temp\Windows6.0-KB932590-x86.cab"
2007-07-25 13:17:05, Info CSI 00000001@2007/7/25:20:17:05.165 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x64ee2e32 @0xf72c09
@0xf6d617 @0xf6dffc @0x772e36ed @0x776fa174)
2007-07-25 13:17:05, Info CBS Session: 29871864:3301734882 initialized.
2007-07-25 13:17:05, Info CBS Pkgmgr: Installing package from: c:\temp\Windows6.0-KB932590-x86.cab
2007-07-25 13:17:05, Info CBS Appl: detect Parent, Package: Package_1_for_KB929761~31bf3856ad364e35~x86~~6.0.1.1, Parent: Microsoft-
Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386, Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp:1, Exist: 1

In this example Cbs.log file, Package Manager indicates that it will install the .cab file for hotfix 932590. However, it actually installs the Package_1_for_KB929761~31bf3856ad364e35~x86~~6.0.1.1 package. This is the hotfix 929761 package.

Note This problem also applies to Windows Server 2008.

CAUSE

This problem occurs because Package Manager cannot manage two or more packages in the same sandbox.

RESOLUTION

To resolve this problem, expand two or more packages to different folders before you install them. Or, create a different sandbox for each package in a folder. To do this, type the following commands at a command prompt:

Delete update*.*

Mkdir c:\temp\sandbox1

Mkdir c:\temp\sandbox2

Start /w pkgmgr /ip /m:c:\temp\CabFile /s:c:\temp\sandbox1

Start /w pkgmgr /ip /m:c:\temp\CabFile /s:c:\temp\sandbox2


In these commands, CabFile represents the .cab file for the hotfix package.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Keywords: kbtshoot kbprb kbexpertiseinter KB932224