locked
DISM Error - Adding package Windows8.1-KB2919355-x64.msu RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    PS D:\Slipstreaming\oscdimg> dism /image:d:\Slipstreaming\2012mount /Add-Package /PackagePath:D:\test\

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031

    Image Version: 6.3.9600.16384

    Processing 1 of 1 - D:\test\Windows8.1-KB2919355-x64.msu: An error occurred applying the Unattend.xml file from the .msu
     package.
    For more information, review the log file.
     Error: 0x800f0823

    Error: 0x800f0823

    DISM failed. No operation was performed.
    For more information, review the log file.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    PS D:\Slipstreaming\oscdimg>

    Below are snippets from the DISM error log.

    2015-05-20 16:26:52, Info                  CBS    Failed to find a matching version for servicing stack: d:\Slipstreaming\2012mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2015-05-20 16:26:52, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    2015-05-20 16:27:21, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2015-05-20 16:27:21, Error                 CBS    Package "Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14" requires Servicing Stack v6.3.9600.17021 but current Servicing Stack is v6.3.9600.16384. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]
    2015-05-20 16:27:21, Info                  CBS    Failed to initialize internal package [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]
    2015-05-20 16:27:22, Error                 CBS    Failed to create internal package [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 The specified package cannot be added to this Windows Image due to a version mismatch. - GetCbsErrorMsg
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to open package at location [C:\Users\nsous91\AppData\Local\Temp\2\EE1E98F4-4822-443A-B5CC-007AC309ED97\Windows8.1-KB2919355-x64.CAB]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to install package from source [0] - trying next source location. hr = [0x800F0823] - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to Install the package [Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14]. - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Package failed to install [Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14]. - CPackageManagerUnattendHandler::Internal_UnattendProcessPackage(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to process package at node <package[0]>. - CPackageManagerUnattendHandler::Apply(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Unattend Manager: PID=3280 TID=2176 Error applying unattend for provider: DISM Package Manager - CUnattendManager::Apply(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM Package Manager: PID=3280 TID=2176 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0823)
    2015-05-20 16:27:22, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0823

    • Edited by nsousa1 Wednesday, May 20, 2015 9:40 PM
    Wednesday, May 20, 2015 9:33 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I opened up a case with Microsoft and they discovered that the OSCDIMG parameters were not correct to generate the ISO file.

    This is the command that worked:

    .\oscdimg -u2 -bD:\Slipstreaming\Server2012ISO\boot\etfsboot.com D:\Slipstreaming\Server2012ISO D:\Slipstreaming\Win2012-R2-Slipstream.iso

    • Marked as answer by nsousa1 Sunday, January 1, 2017 9:33 PM
    Wednesday, January 20, 2016 10:48 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Maybe you could use DISM.exe /Online /Add-Package /PackagePath: to check the result.

    http://blogs.technet.com/b/askcore/archive/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows.aspx

    Regards.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, May 22, 2015 3:09 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    This can happen if the servicing stack of Windows is not updated.

    The error in the DISM.log lies here :  CBS    Failed to find a matching version for servicing stack: d:\Slipstreaming\2012mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.16384_none_fa1dc1539b4180d8\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    You can look more into C:\Windows\Logs\CBS\CBS.log.

    For KB2919355 , it is mandatory to update the Windows Servicing Stack, Try installing # https://support.microsoft.com/en-us/kb/2919442

    When you install this update (2919355) from Windows Update, updates 2932046, 2937592, 2938439, 2934018, and 2959977 are included in the installation

    • Proposed as answer by Vivian_Wang Monday, May 25, 2015 7:54 AM
    Friday, May 22, 2015 9:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having a lot of issues with using DISM. Below are the commands that I am using to add KB2919355 and all dependent updates (taken from here: https://technet.microsoft.com/en-us/library/dn622020.aspx?f=255&MSPPError=-2147217396).

    dism /Mount-Wim /wimfile:D:\Slipstreaming\Server2012ISO\sources\install.wim /index:2 /MountDir:D:\Slipstreaming\2012Mount

    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2919442-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2919355-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2932046-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2934018-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2937592-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2937592-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2938439-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2959977-x64.msu /Image:D:\Slipstreaming\2012Mount\

    dism /Commit-Wim /MountDir:D:\Slipstreaming\2012Mount

    dism /Unmount-Wim /MountDir:D:\Slipstreaming\2012Mount /commit

    .\oscdimg -n -m -bD:\Slipstreaming\Server2012ISO\boot\etfsboot.com D:\Slipstreaming\Server2012ISO D:\Slipstreaming\Win2012-R2-Slipstream.iso

    There are no issues reported adding these windows updates to the base install.wim file. However, when I spin up a VM with this newly created ISO, I get the error below. I've searched around for this error, but nothing that I've tried will fix the issue.

    http://s22.postimg.org/q07136jc1/slipstream_error.png

    Is there an issue with OSCDIMG, maybe? What does everyone else use for creating ISO files?

    • Edited by nsousa1 Friday, May 22, 2015 1:25 PM
    Friday, May 22, 2015 1:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OSCDIMG can be used to make-up an ISO .

    Can you try to commit the image using this command : Dism /Commit-Image /MountDir:D:\Slipstreaming\2012Mount

    Friday, May 22, 2015 8:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I still get the same error. The packages are being added in the correct order, right? I followed the steps linked above from a TechNet article for applying the correct dependent updates.

    Can someone try to reproduce this issue? Is there a problem with a multiboot DVD - will I have more success using a dedicated ISO file for just Server 2012 R2 Standard?

    Friday, May 22, 2015 10:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No, the issue is not resolved. These are the commands that I ran:

    dism /Mount-Wim /wimfile:D:\Slipstreaming\Server2012ISO\sources\install.wim /index:2 /MountDir:D:\Slipstreaming\2012Mount

    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2919442-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2919355-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2932046-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2934018-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2937592-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2937592-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2938439-x64.msu /Image:D:\Slipstreaming\2012Mount\
    Dism /Add-Package /PackagePath:D:\Slipstreaming\2012U1\Windows8.1-KB2959977-x64.msu /Image:D:\Slipstreaming\2012Mount\

    Dism /Commit-Image /MountDir:D:\Slipstreaming\2012Mount

    dism /Unmount-Wim /MountDir:D:\Slipstreaming\2012Mount /commit

    .\oscdimg -n -m -bD:\Slipstreaming\Server2012ISO\boot\etfsboot.com D:\Slipstreaming\Server2012ISO D:\Slipstreaming\Win2012-R2-Slipstream.iso

    I still get the same error after running the installation.

    Monday, May 25, 2015 2:32 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    Hi,

    Based on the error message, the cause of this issue may be it didn’t meet the requirement to install this hotfix. Based on our knowledge, to apply this update, you must have the following update installed on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2: 2919442 (https://support.microsoft.com/kb/2919442/ ) A servicing stack update is available for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: March 2014

    2015-05-20 16:27:21, Error                 CBS    Package "Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14" requires Servicing Stack v6.3.9600.17021 but current Servicing Stack is v6.3.9600.16384. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    So please add the package of KB2919442 firstly. After installing KB2919442, please install KB2919355 again and test how the issue goes.

    If there are any concerns, feel free to let me know.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    • Proposed as answer by Vivian_Wang Wednesday, June 10, 2015 2:00 AM
    Friday, June 5, 2015 1:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Any update about the issue?

    Regards.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Wednesday, June 10, 2015 1:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We downloaded a newer version of the ISO (Windows Server 2012 R2 U1). KB2919355 is already installed with this new ISO.

    However I am still receiving the same error. I confirmed that KB3019215 is a new update that is not included within the new ISO file, but adding that package still generates the same error.

    Wednesday, June 10, 2015 1:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We're having the same issue as this trying to incorporate update KB2919355 into our MDT installation. I tried adding 2919442 but our update is still prematurely ending with the same error:

    2016-01-19 17:48:48, Error                 CBS    Package "Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14" requires Servicing Stack v6.3.9600.17021 but current Servicing Stack is v6.3.9600.16384. [HRESULT = 0x800f0823 - CBS_E_NEW_SERVICING_STACK_REQUIRED]

    So how can I get from service stack v6.3.9600.16384 to v6.3.9600.17021. Also does 16000 = LDR and 17021 = GDR? Maybe that's the issue? Any help tracking this down would be appreciated.

    Thanks

    Brad

    Tuesday, January 19, 2016 5:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I opened up a case with Microsoft and they discovered that the OSCDIMG parameters were not correct to generate the ISO file.

    This is the command that worked:

    .\oscdimg -u2 -bD:\Slipstreaming\Server2012ISO\boot\etfsboot.com D:\Slipstreaming\Server2012ISO D:\Slipstreaming\Win2012-R2-Slipstream.iso

    • Marked as answer by nsousa1 Sunday, January 1, 2017 9:33 PM
    Wednesday, January 20, 2016 10:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    All I can recommend is using a test VM and documenting the patch sequence, rebuilding the base slipstreamed ISO each time you verify that the ISO image works without any issue. That is what I did, in addition to the new comment I made just a moment ago about using the "u2" parameter switch.

    I hope this helps. Otherwise it might make sense to open up a case with Microsoft.

    Wednesday, January 20, 2016 10:51 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I know i am late..but for those who tried these commands and its not working..it's just because they first have to download and install kb2919442 update first and then install kb2919355.I hope this helps.
    • Proposed as answer by zaikun Thursday, October 25, 2018 11:42 AM
    Sunday, January 1, 2017 8:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Its working! Thanks Wang !
    Friday, December 22, 2017 5:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I know i am late..but for those who tried these commands and its not working..it's just because they first have to download and install kb2919442 update first and then install kb2919355.I hope this helps.
    you're a genius! helped me aswell
    Thursday, October 25, 2018 11:42 AM