I am trying to add a package to a WinPE following the tutorial at http://technet.microsoft.com/en-us/library/hh824926.aspx .  I keep getting "The specified package is not applicable to this image".  The only hint I saw was make sure that your are matching your x86 with amd64 and don't get them confused.  Why else would the package not be applicable?

(the x86 image is located at c:\temp\x86 using the pecopy.cmd and them mounted to c:\temp\x86\mount"

c:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment>dism /add-package /image:"c:\temp\x86\mount" /packagepath:"x86\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384

Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.2.9200.16384
[==========================100.0%==========================]

Error: 0x800f081e

The specified package is not applicable to this image.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log  (the log is 99% chinese - so it's not helpful)

Hi,

What's the package would you need to deploy?Please upload your dism logto OneDriveand share the link withus. don't worry language problem.

Thanks Roger,

I'm new at the oneDrive thing - I put the dism.log in the public folder and here is the embed option for it.

DISM.log

I was trying to include the WMI package per the tutorial.  But I tried all the packages in here that came with WAIK for windows 8.

C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs

I tried the same approach with the amd64 files, changing the path accordingly to amd64, but the result was the same - "The specified package is not applicable to this image."

Any insight you have into this would be appreciated.  I started over four times going through the docs.  I'm missing something.  Thanks.

• Edited by dnaughton Monday, May 12, 2014 1:38 PM

Thanks Roger,

I'm new at the oneDrive thing - I put the dism.log in the public folder and here is the embed option for it.

DISM.log

I was trying to include the WMI package per the tutorial.  But I tried all the packages in here that came with WAIK for windows 8.

C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs

I tried the same approach with the amd64 files, changing the path accordingly to amd64, but the result was the same - "The specified package is not applicable to this image."

Any insight you have into this would be appreciated.  I started over four times going through the docs.  I'm missing something.  Thanks.

• Edited by dnaughton Monday, May 12, 2014 1:38 PM

I'm missing something.

Me too.  I can't read your DISM.log.  Try DISM.log redirection, e.g.  /LogPath:  and  /LogLevel:4

on your DISM command?

Done,

I uploaded the DISM.log to the new location.

This looks like where it fails:

Plan: Skipping package since its start state and target state are both absent for package:

I uploaded the DISM.log to the new location.

That's more readable but as usual I don't have any access to the source or internals documentation which lets support staff "read between the lines" of these diagnostics.  I would try running ProcMon, filtering first on Operation Is WriteFile (or at most Category Is Write).   Then when you detect a match for a write of a record in a log that you have a question about, remove the filter and look back for any related registry and file access events which may help explain it.

Otherwise, you might need to look into both the CBS.log and DPX.log

Info                  DPX    DpxException hr=0x80070002 code=0x020109
Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
Error                 DISM   DISM Package Manager: PID=4836 TID=6412 The package WinPE-Scripting-Package is not applicable to the image.

That is seen by applying this findstr filter to your log

findstr  "0x8007 Error Warning"

but I don't know if it significant nor do I know whether you are supposed to have at least one provider, which the above findstr filter will also highlight for you.

 

Good luck

Thanks for the suggestions Robert.  I think I'm going to abandon ship rather than go down the ProcMon path to try to debug this.

I'll just not that you can't add packages with dism with Windows WAIK for WinPE under window 8 64 bit as the tool broken.  I will check back periodically, or post back if I ever find a solution?

I have had enough of DISM  and WinPE :)

i fixed the same issue you were having by add package from the non-language specific path instead (you mentioned chinese, i wonder if the language qualification of "en-us" isnt compatible with the winpe....?:

So this fails
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\en-us\winpe-wmi_en-us.cab"
this succeeds
Dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:"C:\Program Files\<version>\Tools\PETools\x86\WinPE_FPs\winpe-wmi.cab"

In order to add the localised WinPE packages, you need to first add the qualifying LP. You can see in the WinPE_OCs\en-us dir, there is an lp.cab. If your WinPE is not en-US, you add the LP, then you can add the en-US packages you want.

You can first verify the language of your mounted WinPE with this command:

Dism /image:c:\winpe_x86\mount /Get-Intl
If your WinPE is already en-US, you do not need to add the en-US specific cabs, just add the stock ones.
The same goes for if you add (say) the Japanese LP, then you can add the ja-jp localised CABs.