This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 17%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENE%3C/text%3E%3C/svg%3E)
Trying to provision Windows 11 22H2 from OOBE using a provisioning package does not seem to work. The package loads and reboots the computer but then sits at the select country screen in OOBE. If you go through the steps an error pops up stating the device has already been enrolled. My provisioning package sets the wireless changes the device name and enrolls the device in Intune. Anyone have any ideas?
Tag not monitored by Microsoft.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 81%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
We are still experiencing the same, it was supposed to be resolved by March 2023 but we are still stuck on the same.
Did you find any solution?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 68%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENB%3C/text%3E%3C/svg%3E)
Installing a provisioning pack off a newer build of Windows 11 resolves this issue here, see the Update on This Post for info on the KB that resolves the issue. Since either capturing a newer image or installing that KB on a previously captured .wim this issue has been resolved.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 50%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECL%3C/text%3E%3C/svg%3E)
No issues here. I was one of the very first people to post on the initial issue when 22H2 came out. It took 6 months for a fix to happen. I have not had any issues since. I downloaded the newest image from vlsc last month and it worked fine.
Microsoft has acknowledged this is an issue. You can check for updates at the link below.
https://techcommunity.microsoft.com/t5/intune-customer-success/known-issue-provisioning-packages-don-t-work-on-windows-11-2022/ba-p/3643541
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 82%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEC%3C/text%3E%3C/svg%3E)
Hello N E,
First of all thank you for the link now I still have a little concern on this as this KB do not resolve all cases and sadly Nicolas Zhao closed the article.
The KB 5021255 resolves effectively but only if you are having a valid internet connection.
Case you are working offline the PPKG's are still failing.
We are still working with Microsoft support on our side to find a resolution (close 1 year now)
Good, I am glad I am not the only person having issues. I created another thread last week, I haven't gotten resolve. I get a 0x800700b7 error message with a fresh install. Pack works fine with the previous non 22h2 *.iso
This is my post.
Hello Chris,
First of all thank you for the link, feel we are close to a solution here and will post in both channels.
For now please refer to my reply to NE.
Experiencing exact same thing today.
Provisioning packs that worked perfectly fine when tested last year on 21H2, and that currently work on Windows 10 to enroll our fleet are not working today when i started tests on Windows 11 22H2 for our school district potentially upgrading.
I Image and apply drivers through WinPE the way we currently do on Win10, when the machine boots it picks up the .ppkg on the USB and says installing. Then the screen goes black and the Windows 11 OOBE splash screen starts up again, and detects the .ppkg again, and then fails to apply since it's now tried to apply twice.
At least our current workflow works on Win10 8/10 times. Definitely gonna keep our environment off 11 until it's truly necessary with these sort of problems even joining AD/Intune.
Hi,
We are encountering the same problem.
We use Windows Configuration Designer to generate a company PPKG package who we use to provision our new computers for internal usage.
Our package was correctly working on 21H2 but doesnt work anymore on 22H2.
It looks like the package is correctly installed but we are still blocked on OOBE country selection page.
It seems that HideOOBE parameters has not effect from 22H2, maybe linked with new politics of MS to force MS account connection during OOBE??....
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 30%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@Anonymous , For your issue, we suggest to open case to look into more detailed logs to see if we can find more. Here is a link with the steps to open case for your reference:
https://learn.microsoft.com/en-us/mem/get-support
@N E , From your description, it seems the device is already enrolled. Could you go to Intune portal and see if the devices is under All devices.
Meanwhile, please check if the device is register to Autopilot.
If yes, remove them and try again. In addition, please also check if the device is under AAD. If yes, try to remove it either.
If there's any update, feel free to let us know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes the device does appear to enroll into Intune but we cannot use the device as it goes back to the select country screen in OOBE and you cannot get through the steps because of the error stating the device is already enrolled. Removing the device from intune does not seem to matter once the provisioning starts the device reboots back into the select country screen. The same ppkg packages work to enroll 22h1 devices but fail when trying with 22h2.
@N E , Thanks for your update. It seems 22H2 reboot will still go to OOBE to select country, region screen. Then I try to do research, Currently, not find such issue recorded. But it seems the issue is not only with you. Here, we suggest to open case to look into more detailed logs to help on it. Here is a link with the steps to open case for your reference:
https://learn.microsoft.com/en-us/mem/get-support