Windows 10: Provision package during OOBE, cannot deploy app because "the system cannot find the path...

Hello,I'm trying to create a provisioning package for deploying a WIndows image for a small company, I created the package and put the installer as the Windows configuration designer ask.After installing Windows, the laptop restart and I plug the USB to choose the provision packaging, during the OOBE. Then the machine reboots and start resetting.After the reset I got a screen with "installing" and a percentage, then I start getting an error about the app installers and all of them are regarding the "the system cannot find the path specified".Do anyone knows why?

:)

 

Provision package during OOBE, cannot deploy app because "the system cannot find the path specified"

Hello,

I'm trying to create a provisioning package for deploying a WIndows image for a small company, I created the package and put the installer as the Windows configuration designer ask.

After installing Windows, the laptop restart and I plug the USB to choose the provision packaging, during the OOBE. Then the machine reboots and start resetting.

After the reset I got a screen with "installing" and a percentage, then I start getting an error about the app installers and all of them are regarding the "the system cannot find the path specified".

Do anyone knows why?

 

Offline provisioning packages do not start during OOBE

Hello,

In previous versions of Windows 10 I could use dism to add a provisioning package offline that would automate OOBE for me. I do this by applying the image in WinPE then running dism /image:c:\ /add-provisioningpackage /packagepath:test.ppkg.

Starting with 1903 the package is not executed when I get to the first OOBE string. If delete the ppkg from recovery\customizations and run from a flash drive it works as expected. Is this a known issue with 1903? I don't want to put a flash drive into the
450 devices to complete this action and need it to be baked into the image.

Thanks,

Shawn

 

Provisioning package fails to install

Hi Mikeyn,

If it's a provisioning package created by capturing installed apps with Scanstate, my understanding is that you can't apply it at runtime.

From: Configure customizations using Windows ICD - Windows 10 hardware dev

In this context, the ppkg from Scanstate is "reference device data".

It seems from that note that this sort of ppkg won't work at OOBE time either. So I think you're looking at some sort of Windows installation process.

Ways you might try are:

1. use ICD to include the provisioning package into an installer, which can then put onto a bootable USB and installed afresh
2. from a clean install, install the apps, use scanstate to capture the software to C:\recovery\customizations and then use Sysprep to get an image which you deploy with the more traditional route
3. try copying the ppkg to C:\recovery\customizations and running a Reset

For a running PC, I *think* number 3 should work, but I'm not 100% sure, so I'd strongly advise having a good backup before trying it - a Reset will clean a lot of stuff off the PC in any case.