Push button reset

Hello,

I'm working for a project where we want to customize Win10 and retain the customization after a Push Button Reset.

I was able to create a ppkg package with scanstate to retain apps.

We would like to find a way to retain some user settings as well like favorites and background. I was customizing the Administrator account and using the copy profile in the unattend.xml. This works fine for initial deployment. So I thought that I would scanstate the Administrator profile and run loadstate with Push Button Reset as well. The resetconfig.xml located in C:\recovery\oem point to an enablecustomization.cmd.

"%TARGETOSDRIVE%\Recovery\OEM\usmt10\loadstate.exe" "%TARGETOSDRIVE%\Recovery\OEM" /c
copy "%TARGETOSDRIVE%\Recovery\OEM\Unattend.xml" "%TARGETOS%\Panther\Unattend.xml" /y
copy "%TARGETOSDRIVE%\Recovery\OEM\Startmenu.xml" "%TARGETOSDRIVE%\Users\Default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml" /y

The usmt.mig file is in C:\recovery\oem\usmt

After Push Button Reset is finished. I can create a new account and see that the startmenu and applications are retained. However not the profile. Setupact.log. I see that it runs loadstate and a few lines below there is an error code 36. According to docs.microsoft.com, error code 36 means USMT_ERROR_UNSUPPORTED_PLATFORM

Maybe loadstate cannot be run in this environment during setup. Do I have other option to retain settings after Push Button Reset?

Thanks,

Edy

No this is not a domain. It's a project to roll out a tablets with Windows 10 to clients.

Thanks,

Is it possible to have more than one ppkg in the C:\recovery\customizations folder? Would a reset apply more than one? What about the naming convention? Does it matter? In the tutorial I see it is named usmt.ppkg. The same name is used by docs.mircosoft.com too.

Thanks - Let's see if David steps in.

Thanks Kari - Is it possible to use this recovery partition with Push Button Reset too? About the boot menu, does it start Windows 10 after a certain time automatically or will the user need to select the startup partition each time?

Bree said:

Not my area of expertise, perhaps the tutorial author @DavidY would be able to help.

Thanks for the mention Bree.

Fafaxx said:

Thanks,

Is it possible to have more than one ppkg in the C:\recovery\customizations folder? Would a reset apply more than one? What about the naming convention? Does it matter? In the tutorial I see it is named usmt.ppkg. The same name is used by docs.mircosoft.com too.

Apologies I've not been here much lately so hadn't noticed the thread until Bree linked me into it

I'm pretty sure you can have multiple provisioning packages, but I think you may only be able to have one .ppkg to capture your applications with Scanstate as per the tutorial linked to earlier. The other .ppkgs would contain other customisations to settings but not desktop applications.

However there is something called 'Siloed provisioning packages' which relies on creating several incremental packages.

On that page it says:

Push-button reset

When using ScanState to capture traditional provisioning packages, only one package with all the applications and system settings can be placed in %systemdrive%\Recovery\Customizations folder. During push-button reset (PBR), the single provisioning package is processed to restore the applications and system settings.

Beginning with Windows 10, version 1607, applications can be captured in multiple siloed provisioning packages and system settings can also be captured in a separate siloed provisioning package. As a result, PBR is enhanced to allow multiple siloed provisioning packages to be applied, in the preserved order in which they were applied using Dism /Apply-Siloed Package. The packages can then be queued and processed in the right order during PBR to restore the applications and system settings captured in these packages.

So I think that might be the way to do it if you want to use provisioning packages containing applications. Although I've not tried it and the creating siloed provisioning packages does seem like a fiddly process.

Hope this helps.