none
Powershell WinPE Error help RRS feed

  • Question

  • Hi,

    We are getting this error when adding Powershell to WinPE in MDT.

    Processing 1 of 1 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~x86~~6.3.9600.16384
    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
    Exit code = -2146498530

    Can anyone help? Can't see anything useful in the logs...

    Monday, August 4, 2014 1:25 PM

Answers

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

    Can anyone help? Can't see anything useful in the logs...

    I don't see anything useful in the logs either. :^)

    I Suspect that you may have some mix matched OS Versions. *Specifically* What OS Version is the WinPE image? Verify by cracking it open and getting the version string for NTOSKrnl.exe. You might be able to fix this by disabling the <Boot.x86.UseBootWim> feature in the \deploymentshare\control\settings.xml file.

    If you still need help, please copy your logs(s) to a public site like OneDrive, and copy the link here.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, August 6, 2014 12:08 AM
    Moderator

All replies

  • To my understanding, the package will be applied to the local operating system that is being deployed. This is something that must be prevented at all times.

    Please check your deployment task sequence, phase: preinstall\apply patches, and make sure it is set to Nothing (as selection profile) then perform a redeployment of the operating system to see what happens.

    Cheers!


    If this post is helpful please click "Mark for answer", thanks! Kind regards

    Monday, August 4, 2014 3:04 PM
  • The DISM log file can be found at C:\windows\Logs\DISM\dism.log

    Can anyone help? Can't see anything useful in the logs...

    I don't see anything useful in the logs either. :^)

    I Suspect that you may have some mix matched OS Versions. *Specifically* What OS Version is the WinPE image? Verify by cracking it open and getting the version string for NTOSKrnl.exe. You might be able to fix this by disabling the <Boot.x86.UseBootWim> feature in the \deploymentshare\control\settings.xml file.

    If you still need help, please copy your logs(s) to a public site like OneDrive, and copy the link here.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, August 6, 2014 12:08 AM
    Moderator
  • Just tossing this out there, but you don't by any chance have McAfee AV with Access Protection do you?

    https://kc.mcafee.com/corporate/index?page=content&id=KB76867

    The error isn't exactly the same, but its possible Symantec is doing the same type of thing, or some other AV.

    Wednesday, August 6, 2014 4:18 AM