none
When I try to add packages to my Win7 x64 WinPE image using dism, it fails

    Question

  • When I try to add packages to my WinPE image using dism, it fails with an error:

    c:\winpe_x64>dism /image:C:\winpe_x64\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab"

    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385

    Image Version: 6.1.7600.16385

    An error occurred trying to open - C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab" Error: 0x80070003

    Error: 3

    The system cannot find the path specified.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    c:\winpe_x64>

    Here are the errors from the dism.log:

    2009-08-11 14:24:14, Error                 DISM   DISM Package Manager: PID=2708 Incorrect parameter C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab” - path not found - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070003)
    2009-08-11 14:24:14, Error                 DISM   DISM Package Manager: PID=2708 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x80070003)
    2009-08-11 14:24:14, Error                 DISM   DISM Package Manager: PID=2708 Failed to open the package at location: "C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab”" - CPackageManagerCLIHandler::ProcessPackagePath(hr:0x80070003)
    2009-08-11 14:24:14, Error                 DISM   DISM Package Manager: PID=2708 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070003)
    2009-08-11 14:24:14, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070003

    I have tried this on a Win7 RC x86 PC with both amd64 and x86 versions.
    I have also tried this on a Win7 Enterprise RTM x64 with both amd64 and x86 versions.
    I am running the released AIK that I got with Win7 Enterprise and Microsoft Deployment Toolkit 2010 Beta 2.

    Thanks,
    Ed


    Ed Hammond - System Admin
    Tuesday, August 11, 2009 10:19 PM

Answers

All replies

  • Hi Ed,

    The format of the command is correct. Did you run it in Windows 7 system, or your Win PE system? If it is Win PE, I suggest that you try to locate the package file manually. Because the C drive in your Windows 7 system may be not the C drive in the PE environment.

    Additionally, the latest Windows AIK is downloaded from the following website. You may verify if your program is from there.

    The Windows® Automated Installation Kit (AIK) for Windows® 7


    Arthur Xie - MSFT
    Saturday, August 15, 2009 3:19 AM
    Moderator
  • Greetings Arthur,

    Is the ISO file you linked the same one subscribers we have available in our TechNet Downloads area?

    I'm getting some weird errors with DISM.

    Regards.
    W7 RTM x64 running along with Office 2010 x64 TP hope my computer won't crash! ;)
    Tuesday, August 18, 2009 9:24 AM
  • Thanks for the reply Arthur,
    I got my AIK from technet:
    en_windows_automated_installation_kit_for_windows_7_and_windows_server_2008_r2_x86_x64_ia64_dvd_400053.iso

    I have tried the following:
    3 different PCs
    Win7 RC x86
    Win7 RTM x64 (2 like this)
    I was going to put the x86 Win7 RTM on Virtual Server 2005 R2, but it stopped working after I installed the VM tools.  Nice.

    I have tried building both the x64 and x86 versions of WinPE on Win7 Enterprise RTM and Win7 Ultimate RC.
    I have tried running the Deployment Tools Command Window as both a normal run and as Administrator.
    It always fails, and on top of that, if I make the WinPE disc anyway, it still fails to boot the PC (There is something wrong with the WinPE disk too)
    I tried creating a x64 WinPE boot disc with no modifications and it failed to boot both a Gateway FX540 and a Dell Vostro 220.  It stops with an error. (I forgot to write down the error)


    Ed Hammond - System Admin
    Tuesday, August 18, 2009 2:42 PM
  • Here are some newer logs that have some warnings included. (I missed those last time)

    -08-17 09:00:15, Warning               DISM   DISM Provider Store: PID=5028 Failed to Load the provider: C:\Users\EDB767~1.SKI\AppData\Local\Temp\730CD4B9-CC34-4FFE-B3E5-48DC02B1EA44\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2009

    -08-17 09:00:15, Warning               DISM   DISM Provider Store: PID=5028 Failed to Load the provider: C:\Users\EDB767~1.SKI\AppData\Local\Temp\730CD4B9-CC34-4FFE-B3E5-48DC02B1EA44\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2009

    -08-17 09:00:15, Error                 DISM   DISM Package Manager: PID=5028 Incorrect parameter C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab� - path not found - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070003)
    2009-08-17 09:00:15, Error                 DISM   DISM Package Manager: PID=5028 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x80070003)
    2009-08-17 09:00:15, Error                 DISM   DISM Package Manager: PID=5028 Failed to open the package at location: "C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-hta.cab�" - CPackageManagerCLIHandler::ProcessPackagePath(hr:0x80070003)
    2009-08-17 09:00:15, Error                 DISM   DISM Package Manager: PID=5028 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070003)
    2009-08-17 09:00:15, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070003
    2009
    Ed Hammond - System Admin
    Tuesday, August 18, 2009 2:48 PM
  • Can you please checkout this post regarding adding packages to WinPE?

    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/10dd2dd8-5ee9-40a3-954d-08169f70cf34

    I have not yet tested this in my own environment, but it sounds like a bug to me.
    Ray
    • Marked as answer by Mr.Ed Tuesday, August 18, 2009 8:42 PM
    Tuesday, August 18, 2009 8:25 PM
  • I had my package file names in lowercase, but not C:\, when I changed that to c:\ (lowercase c) it worked!
    How STUPID is that!  Doesn't anyone test this stuff???

    Now to see if my WinPE will boot this time!

    Thanks Ray! (and thanks to Adam Leinss)
    Ed Hammond - System Admin
    Tuesday, August 18, 2009 8:43 PM
  • I just resolved the WinPE boot problem I had. It turned out that the instructions in Microsoft TechNet article "Step-by-Step: Basic Windows Deployment for IT Professionals" is slightly different to the instructions provided in the AIK help file. Specifically, the TechNet article failed to mention the following: -

    Copy the file "C:\winpe_x86\winpe.wim" to the folder "C:\winpe_x86\iso\sources" and rename the copied file to "boot.wim".

    I used this command:    copy C:\winpe_x86\winpe.wim C:\winpe_x86\iso\sources\boot.wim

    After this step, I created the "winpe_x86.iso" file using the "oscdimg" command and burned it to a CD-ROM media and it worked.


    Good thing they sell CDs in 50 packs!

    Ed Hammond - System Admin
    Tuesday, August 18, 2009 10:32 PM
  • I had this same problem with the Windows 7 OPK. I tried all the solutions suggested here, including changing upper case to lower case, with no success. I did manage to get it to work, however. Here is what I did.
    1. Create a root folder named \Packages
    2. Change to the C:\Program Files\Windows OPK\Tools\PETools\amd64\WinPE_FPs directory and copy the files to the directory above: xcopy *.* \packages /s
    3. Run the command: C:\Packages>Dism /image:C:\winpe_x64\mount /Add-Package /PackagePath:c:\Packages\winpe-hta.cab
    The command should run fine.
    However, this command does not work:
    C:\Packages>Dism /image:C:\winpe_x64\mount /Add-Package /PackagePath:"c:\Packages\winpe-hta.cab"
    So, my assumption is that the problem is in the use of the quotation marks, which the DISM program doesn't seem able to interpret. Since there are no spaces in this short path, there is no need for quotation marks, and things just work.
    • Proposed as answer by GS Dilip Tuesday, November 01, 2011 8:26 PM
    Monday, June 28, 2010 5:39 PM
  • I'm trying to build a custom installation with the WAIK. After I have mounted the install.wim file and try to add the  language pack I get a Error

    This is the command line I use to Mount the WIM file
    dism /Mount-Wim /WimFile:E:\7Work\DVD\sources\install.wim /index:1 /MountDir:E:\7Work\WIM

    This is the command line I use to Add-Package
    dism /Image:E\7Work\WIM /Add-Package /LogPath:AddPackage.log /PackagePath:E:\7work\LP\lp.cab

    Then I get this Error

    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385


    Error: 3

    Unable to access the image.
    Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    What's going wrong here?
    Friday, February 25, 2011 8:35 AM
  • This is the command line I use to Add-Package
    dism /Image:E\7Work\WIM /Add-Package /LogPath:AddPackage.log /PackagePath:E:\7work\LP\lp.cab

    you miss the : after the E

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 25, 2011 2:55 PM
  • Jack, Thanks, that worked for me.

     

    I have Windows 7 x64, with Windows AIK for Windows 7 installed and the Windows AIK for Windows 7 SP1 installed, and this add-package problem exists.  I tried the other suggestions with no success.  Your suggestion that it is the quotation marks was excellent and was the situation in my case as well.  I agree with a previous poster "doesn't anyone at Microsoft check this stuff?".  Anyway, I moved the .cab file from C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs to the C:\ folder and it installed fine.  Thanks.

    Sunday, March 13, 2011 6:45 PM
  • thanks jack it worked
    Tuesday, November 01, 2011 8:27 PM