Provisioning Windows 11 22H2 and error 0x800700b7

Provisioning Windows 11 22H2 and error 0x800700b7

A new problem for Windows 11 22H2! This time, it is the provisioning phase of the machine that is concerned, because the system is partially configured or crashes at the end of the installation. What’s going on ?

This problem affects companies that use the Intune / Microsoft Endpoint Manager solution (via Windows Autopilot, in particular) and Microsoft has acknowledged the existence of this bug. A dedicated article is available at techcommunity.microsoft.com. Microsoft’s Nicole Zhao clarifies: “We wanted to inform you about an issue with the provisioning of packages (.ppkg) on ​​Windows 11 2022 Update.

Indeed, it is the deployment of the “.ppkg” packages that seems to be the problem and that can crash the provisioning of the machine. Microsoft clarifies:This issue stuck the device in the OOBE (out-of-box experience) process. During provisioning, the .ppkg file is applied but the OOBE process hangs and may cause the device to reboot unexpectedly.

It is Windows 11 22H2 that is the problem, because the same package works well on Windows 11 22H1. When deployment crashes on Windows 11 22H2, error 0x800700b7 is thrown. Here is the full text of this error message:Provisioning failure , Installation of a provisioning package failed. Please work with the package author to diagnose the problem. Reported error code: 0x800700b7″.

Windows 11 22H2 - Provisioning failed

The Redmond company is working on a fix, and in the meantime there is no real solution. Except that Microsoft recommends its users to do package provisioning on the computer before upgrading to Windows 11 22H2.

For the past few days, the problems have been linked for Windows 11 22H2:

In addition, machines equipped with the Intel SST audio driver cannot yet benefit from Windows 11 22H2 due to a bug that can generate a blue screen of death on the computer.

Source

Logiciel – OS,Microsoft,Windows 11,

#Provisioning #Windows #22H2 #error #0x800700b7

Leave a Comment

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