Provision Package not able to apply

Question

Provision Package not able to apply

w raspe 336

Hi all,

I am trying to apply an custom made provision package through CMD, but it does not recognize the commands. If it works by hand via CMD then I will it push through MDT. The .ppkg contains settings to use within an school environment.

When I just open the .ppkg file it works fine, but I want to automate this process.

Below the error message on an Windows 11 device. It seems it also not recognize the /add-provisionpackage command.

w11

I am just trying the same in below url:

https://bjtechnews.org/2017/03/deploy-provisioning-packages-with-mdt/

I also tried below url for the command line section:

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-provisioning-package-command-line-options?view=windows-11

Accepted answer

1 additional answer

Your answer

Answer 1

AllenLiu-MSFT 49,316 Microsoft External Staff

Hi, @w raspe

Thank you for posting in Microsoft Q&A forum.

The error message in the screenshot indicates that the /Add-ProvisioningPackage command is not recognized. Make sure that you are using the correct syntax for the command, as shown in the DISM Provisioning Package (.ppkg) Command-Line Options article. Also, ensure that the DISM version you are using supports provisioning packages.

You can use the /Get-Features command to check if the DISM version supports provisioning packages. If the output includes "PPKGFeature", then provisioning packages are supported.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

w raspe 336 Reputation points

2024-04-10T09:02:43.4+00:00

Hi @AllenLiu-MSFT ,

Few days later and still having issues to apply the provision package.

I tried the following command: DISM.exe /online /Add-ProvisioningPackage /PackagePath:C:\oem.ppkg, but does not apply the settings.

Not sure where to look for the right solution.

Here some more information:

2024-04-10 10:53:56, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

2024-04-10 10:53:56, Info DISM DISM.EXE:

2024-04-10 10:53:56, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=6

2024-04-10 10:53:56, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.2792

2024-04-10 10:53:56, Info DISM DISM.EXE: Executing command line: "C:\WINDOWS\system32\Dism.exe" /Image=C:\ /Add-ProvisioningPackage /PackagePath:C:\Windows\Temp\PPKG\Kiosk\Kiosk1.ppkg

2024-04-10 10:53:56, Info DISM DISM FFU Provider: PID=7324 TID=1796 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

2024-04-10 10:53:56, Info DISM DISM Imaging Provider: PID=7324 TID=1796 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2024-04-10 10:53:56, Info DISM DISM VHD Provider: PID=7324 TID=1796 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2024-04-10 10:53:56, Info DISM DISM Imaging Provider: PID=7324 TID=1796 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

[7324.1796] [0x8007007b] FIOReadFileIntoBuffer:(1456): The filename, directory name, or volume label syntax is incorrect.

[7324.1796] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

[7324.1796] [0xc142011c] WIMGetMountedImageHandle:(2910)

2024-04-10 10:53:56, Info DISM DISM WIM Provider: PID=7324 TID=1796 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2024-04-10 10:53:56, Info DISM DISM Imaging Provider: PID=7324 TID=1796 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage

2024-04-10 10:53:56, Info DISM DISM Imaging Provider: PID=7324 TID=1796 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage

[7324.1796] [0x8007007b] FIOReadFileIntoBuffer:(1456): The filename, directory name, or volume label syntax is incorrect.

[7324.1796] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)

[7324.1796] [0xc142011c] WIMGetMountedImageHandle:(2910)

2024-04-10 10:53:56, Info DISM DISM WIM Provider: PID=7324 TID=1796 [C:] is not a WIM mount point. - CWimMountedImageInfo::Initialize

2024-04-10 10:53:56, Info DISM DISM FFU Provider: PID=7324 TID=1796 [C:] is not recognized by the DISM FFU provider. - CFfuImage::Initialize

2024-04-10 10:53:56, Info DISM DISM VHD Provider: PID=7324 TID=1796 [C:] is not recognized by the DISM VHD provider. - CVhdImage::Initialize

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 physical location path: C:\ - CDISMManager::CreateImageSession

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Event name for current DISM session is Global{1482CCDD-310A-4F22-96DE-949A722D17AA} - CDISMManager::CheckSessionAndLock

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Create session event 0x278 for current DISM session and event name is Global{1482CCDD-310A-4F22-96DE-949A722D17AA} - CDISMManager::CheckSessionAndLock

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Successfully loaded the ImageSession at "C:\Users\Kiosk1\AppData\Local\Temp\AAD26B06-5C07-416B-93FC-83E246876FDC" - CDISMManager::LoadRemoteImageSession

2024-04-10 10:53:56, Info DISM DISM Image Session: PID=11044 TID=7372 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

2024-04-10 10:53:56, Info DISM DISM OS Provider: PID=11044 TID=7372 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

2024-04-10 10:53:56, Info DISM DISM OS Provider: PID=11044 TID=7372 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

2024-04-10 10:53:56, Info DISM DISM Provider Store: PID=11044 TID=7372 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

2024-04-10 10:53:56, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2024-04-10 10:53:56, Info DISM DISM Provider Store: PID=11044 TID=7372 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

2024-04-10 10:53:56, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2024-04-10 10:53:56, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Image session successfully loaded from location: C:\Users\Kiosk1\AppData\Local\Temp\AAD26B06-5C07-416B-93FC-83E246876FDC - CDISMManager::CreateImageSession

2024-04-10 10:53:56, Info DISM DISM OS Provider: PID=11044 TID=7372 Setting SystemPath to C:\ - CDISMOSServiceManager::SetSystemPath

2024-04-10 10:53:56, Info DISM DISM.EXE: Target image information: OS Version=10.0.22631.2861, Image architecture=amd64

2024-04-10 10:53:56, Error DISM DISM.EXE: Invalid command line option: Offline image specified is the running system.

2024-04-10 10:53:56, Info DISM DISM Manager: PID=7324 TID=1796 Closing session event handle 0x278 - CDISMManager::CleanupImageSessionEntry

2024-04-10 10:53:56, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

2024-04-10 10:53:56, Info DISM DISM.EXE:

2024-04-10 10:53:56, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

Answer 2

w raspe 336

@AllenLiu-MSFT I fixed it with the install-provisioningpackage command

AllenLiu-MSFT 49,316 Reputation points Microsoft External Staff

2024-04-12T01:26:09.6866667+00:00

@w raspe

Thanks very much for your feedback. We're glad that the problem is solved now.

Share via

Provision Package not able to apply

1 additional answer

Your answer