Windows 11 22H2: Provisioning packages may not work as expected

Windows[German]Microsoft had released the next rollout phase for the feature update to Windows 11 version 22H2 (as Windows 11 2022 Update). The stuff is to be distributed more broadly. Then on October 5, 2022, Microsoft followed up with a warning for administrators in the enterprise environment that the announced that provisioning packages may not work as expected.


Microsoft documented the issue on the Windows 11 22H2 Release Healt Status page as of October 5, 2022, and published the post Provisioning packages might not work as expected.

What are provisioning packages?

Microsoft wants to make it easier for IT administrators to configure end-user devices running Windows 10 or Windows 11 without imaging by doing this configuration through provisioning packages. A provisioning package (.ppkg) is a container for a collection of configuration settings. Based on a provisioning package, an IT administrator can easily specify the desired configuration and settings required to register devices for management. This configuration can then be applied to the target devices in a matter of minutes. It's best suited for small to medium-sized businesses with deployments of a few dozen to a few hundred computers. Microsoft describes the details in the post Provisioning packages overview on Windows 10/11. The Windows Configuration Designer for creating the packages is available as an app in the Microsoft Store.

Issues with provisioning packages

In the article Provisioning packages might not work as expected Microsoft has to admit that the use of provisioning packages under Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Especially nasty: Windows may be only partially configured by these packages – but the intended target configuration is not set up safely and clients may be restarted unexpectedly. You can also put it shorter: Provisioning packages are currently (under Windows 11 22H2) something for the chimney  – they don't work.

Microsoft writes that provisioning packages (.ppkg) used during initial setup to configure new devices on corporate or school networks are most likely affected by this issue. Provisioning Windows devices with Windows Autopilot is not affected by this issue. Windows systems used by home users or in small businesses in the office are also unlikely to be affected by this issue (since no deployment packages are used there).

Systems that have been upgraded to Windows 11 version 22H2 are affected. As a workaround, Microsoft suggests rolling out the deployment packages on Windows 11 21H2 and only then upgrading to Windows 11 version 22H2. Currently, the developers are investigating the problem and hope to provide an update in one of the next versions of Windows 11 22H2.


Similar articles
Windows 11 2022 Update (22H2) released
Windows 11 22H2: Issues and upgrade stoppers
Windows 11: Printer driver confirmed as upgrade stopper (Sep 29, 2022)
Windows 11 22H2: Out-of-band update KB5019311 (Sept. 27, 2022)
Windows 11: Compatibility issues with Intel Smart Sound Technology
Windows 11: Preview-Update KB5017389 (Sept. 30, 2022)
Windows 11 strengthens SMB traffic protection
Windows 11 22H2 rollout in new phase

Cookies helps to fund this blog: Cookie settings

This entry was posted in Windows and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *