Windows 11 sysprep

sjaak327 whatever 31

Please, no questions on to why I use a thick image, deployment time IS a concern here.

I have been using the same procedure to create an image, sysprep it and capture it for years, with various operating systems included Windows 10 21H2 and Windows 11 21H2, working just fine.

So... I tried to do the exact same procedure for Windows 11 22H2, using the same applications inisde the image, same language options. Exactly the same as with Windows 11 21H2.

The problem, after the successfull sysprep, rebooting the reference pc, will get the PC into the Getting Ready stage, and it will never move beyond it (even after 8 hours). The captured image deployed to another pc obviously has the same problem, after the first reboot, it is also stuck in Getting Ready.

The sysprep log indicates no problems.

I am at a loss here.

Craig Jackson 11 Reputation points

2022-09-29T07:47:36.25+00:00

I have the exact same issue with Win 11 22H2.

Both the build and capture within Configuration Manager and a manual sysprep result in the computer being stuck at "Getting ready" on boot.

Win 11 21H2 and Win 10 versions work fine.
Thomas Bouw 6 Reputation points

2022-09-29T09:04:08.647+00:00

Exactly the same issue here.
I did try out a clean install of Windows 11 22H2 sysprep and that didn't show any issues, but of course isn't the image I need.
I'm wondering if it has something to do with installing features or uninstalling specific unwanted apps.
Hudec Roman 11 Reputation points

2022-09-30T07:13:05.747+00:00

I have the same issue, after sysprep, next restart computer stuck on "Getting ready"
jaybird283 561 Reputation points

2022-10-01T07:17:24.717+00:00

Same issue here too. i just spent an entire Friday night trying to rebuild my image from scratch and it still ended up doing the same thing.
Thomas Bouw 6 Reputation points

2022-10-02T12:46:14.427+00:00

Not sure if the same applies to you all, but over here the issue only occurs when the reference machine has been domain joined during the build and capture.
Of course we unjoin the domain before the sysprep step.

As long as we don't perform a domain join, the machine get build properly and we don't get the endless loading screen.

I have to find some time what exactly in the domain join causes the issue over here.
Martin Schneeberger 76 Reputation points

2022-10-06T16:58:34.387+00:00

I have the same issue with Version 22621.525
After sysprep on next start on the Capture Device (Configuration Manager).
And when i deploy the capture image to a Device with Configuration Manager.

Update 20221009: Same issue with Version 22621.608
Johan Pol 11 Reputation points

2022-12-01T10:18:36.52+00:00

At November 29th Microsoft released a new Windows 11 version.

https://support.microsoft.com/en-us/topic/windows-11-version-22h2-update-history-ec4229c3-9c5f-4e75-9d6d-9025ab70fcce

Did someone already tested it with a Build&Capture?
Martin Schneeberger 76 Reputation points

2022-12-01T11:56:46.013+00:00

Yes. But it works only with a workaround: https://learn.microsoft.com/answers/users/14838839/marcelmeurer-7413.html
Johan Pol 11 Reputation points

2022-12-01T12:08:32.69+00:00

Ok so not resolved..then we need to wait until next release and test it then again.
Brandon M 1 Reputation point

2023-04-14T18:56:28.05+00:00

Having the same issue. 21H2 works fine and is only a problem with 22H2. Deploying with Configuration Manager (2111) Task Sequence and MDT extensions. Sits at Getting Ready for a really long time. It eventually goes through, but ends up booting to Windows without being joined to domain.
Johan Pol 26 Reputation points

2023-04-15T08:29:40.2133333+00:00

Brandon, use the latest w11 22h2 iso and the issue is resolved.
Brandon M 1 Reputation point

2023-04-17T11:13:06.6033333+00:00

@Johan Pol
SW_DVD9_Win_Pro_11_22H2.7_64BIT_English_Pro_Ent_EDU_N_MLF_X23-42597.ISO
I used this ISO from our MS Volume License portal. Just downloaded it on Friday. Is it not the latest for Enterprise Edition? Thankjs
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Yi Long Ma 0 Reputation points

2023-04-17T12:45:32.76+00:00

I used this ISO from our MS Volume License portal. Just downloaded it on Friday. Is it not the latest for Enterprise Edition? Thankjs

Martin Schneeberger 76

The error situation has been fixed since Patchday March.
Ideally you use the latest ISO from the MSDN portal. The last CU is already included in these ISOs.

22 answers

Johan Pol 26 Reputation points

2023-03-06T06:43:08.46+00:00

The latest Preview fix, solved the issue!

Try and see yourselves.
Please sign in to rate this answer.

1 person found this answer helpful.
König, Martin 0 Reputation points

2023-03-13T13:00:07.07+00:00

Hello Johan,

do you know wich fix exactly fixed this?

Kind Regards

Martin

Johan Pol 26 Reputation points

2023-03-13T17:25:06.06+00:00

this one:

https://support.microsoft.com/en-au/topic/february-28-2023-kb5022913-os-build-22621-1344-preview-3e38c0d9-924d-4f3f-b0b6-3bd49b2657b9
Sign in to comment
Martin Schneeberger 76 Reputation points

2023-03-13T13:05:17.1766667+00:00

"2023-02 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5022913)" updates to "OS Build 22621.1344". Then it will be fixed.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Patrick C 11

Exactly same problem here. Have been 'cooking' and deploying all our Win 10/11 images successfully since first release. Windows 11 22H2 build 525 installs and runs flawlessly, but hangs after sysprep. Thinking it has to do with apps or features we remove from the image, just not quite sure which one.
These are the apps we currently remove from the image:

Clipchamp.Clipchamp_2.2.8.0_neutral_~_yxz26nhyzhsrt  
Microsoft.549981C3F5F10_3.2204.14815.0_neutral_~_8wekyb3d8bbwe (CORTANA)  
Microsoft.BingNews_4.2.27001.0_neutral_~_8wekyb3d8bbwe  
Microsoft.BingWeather_4.53.33420.0_neutral_~_8wekyb3d8bbwe  
Microsoft.GamingApp_2021.427.138.0_neutral_~_8wekyb3d8bbwe  
Microsoft.GetHelp_10.2201.421.0_neutral_~_8wekyb3d8bbwe  
Microsoft.Getstarted_2021.2204.1.0_neutral_~_8wekyb3d8bbwe  
Microsoft.MicrosoftOfficeHub_18.2204.1141.0_neutral_~_8wekyb3d8bbwe  
Microsoft.MicrosoftSolitaireCollection_4.12.3171.0_neutral_~_8wekyb3d8bbwe  
Microsoft.StorePurchaseApp_12008.1001.113.0_neutral_~_8wekyb3d8bbwe  
Microsoft.WindowsAlarms_2022.2202.24.0_neutral_~_8wekyb3d8bbwe  
Microsoft.WindowsFeedbackHub_2022.106.2230.0_neutral_~_8wekyb3d8bbwe  
Microsoft.WindowsMaps_2022.2202.6.0_neutral_~_8wekyb3d8bbwe  
Microsoft.WindowsSoundRecorder_2021.2103.28.0_neutral_~_8wekyb3d8bbwe  
Microsoft.Xbox.TCUI_1.23.28004.0_neutral_~_8wekyb3d8bbwe  
Microsoft.XboxGameOverlay_1.47.2385.0_neutral_~_8wekyb3d8bbwe  
Microsoft.XboxGamingOverlay_2.622.3232.0_neutral_~_8wekyb3d8bbwe  
Microsoft.XboxIdentityProvider_12.50.6001.0_neutral_~_8wekyb3d8bbwe  
Microsoft.XboxSpeechToTextOverlay_1.17.29001.0_neutral_~_8wekyb3d8bbwe  
Microsoft.YourPhone_1.22022.147.0_neutral_~_8wekyb3d8bbwe  
Microsoft.ZuneMusic_11.2202.46.0_neutral_~_8wekyb3d8bbwe  
Microsoft.ZuneVideo_2019.22020.10021.0_neutral_~_8wekyb3d8bbwe  
MicrosoftCorporationII.QuickAssist_2022.414.1758.0_neutral_~_8wekyb3d8bbwe

HugeZhong 106 Reputation points

2022-09-30T09:03:53.927+00:00

I'm working at an OEM and I never have that kind of problem. Do you try the latest hotfix of this month?
Please sign in to rate this answer.
Thomas Bouw 6 Reputation points

2022-09-30T09:12:11.487+00:00

Still running a few versions back, however...even outside of SCCM the problem occurs.

Specifically: as soon as the device has been domain joined, the problem occurred.
So in this case I installed a bare Windows 22H2 pro from the ISO, domain joined the device, removing it again from the domain and sysprepping - this will give exactly the same result where it remains stuck.

I managed to create a task sequence w/o the domain join that captures a proper image (the join is done because of a few steps we perform in the usual build and capture).
The deployment of that image (and also domain joining the deployed device) seems to be doing OK - so far no issues yet.

I haven't had the time yet to pinpoint the exact issue in the domain join that causes this (might be a GPO or something else...).

Hopefully this will help some of the other experiencing the same issue.
Sign in to comment
SCCMDude 16 Reputation points

2022-10-04T21:54:26.607+00:00

We're in the same boat, always used a build and capture of a VM joined to the domain since Win 10 1703. Can't get past the "getting ready" screen on the deployment with 22H2.

After seeing this thread I did try disabling our step that runs a powershell script to strip out all the build in/unwanted apps... .no difference.

I also noticed that Microsoft had put up a slightly newer 22H2 on the visual studio site ('sept updated') so tried all the stuff I had already try last week and no dice.

As for someone thinking it's a domain policy applying, I'm skeptical, since when we join the capture VM to the domain, we put in an OU where we're no applying any GPOs.
Please sign in to rate this answer.
Hudec Roman 11 Reputation points

2022-10-10T06:29:43.593+00:00

We tried build image Win11 22H2 without domain join, but application install ended with error. After we replaced parameter FSP=xxx.xx in step "Setup Windows and Configuration Manager" with SMSMP=xxx.xx everything works after sysprep and capture image.

SCCMDude 16 Reputation points

2022-10-11T13:54:45.12+00:00

I ended up in the same scenario, creating a base image off domain and ran into the same issues as you and had to adjust the parameters for installing the configman client.

I was able to deploy that image but I'll need to refine the process as the capture image didn't have any updates and was missing a few apps that we'd normally deploy to a domain joined machine :/

I did put in a ticket with Microsoft but so far it hasn't been helpful.

SCCMDude 16 Reputation points

2022-10-11T20:31:14.777+00:00

Microsoft added a known issue to the October CU for 22h2 (and the out of band update from the end of September).

"Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows."

We use a single provisioning package and some other customizations so I'm gonna do some tests pulling those customizations out and see if we get further with deploying the image.

SCCMDude 16 Reputation points

2022-10-12T21:43:20.73+00:00

No advancements here. I did strip out our customizations and still I'm not able to deploy a previously domain joined image. I've gone through the sysprep logs and everything looks fine on that front.

No real help from Microsoft at this point, they just assumed that I didn't know how to properly capture a wim so I explained the process that we've been using since Windows 10 1703 and we haven't had an issue until Win11 22H2.

Tomorrow I'll dig further through the OOBE logs and see if there's any hints there and hopefully I'll get a bit further with Microsoft support.
Sign in to comment