Windows 11 sysprep

Question

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.

Answer 1

Hi,

Thank you for posting your query.

To resolve your issue kindly follow the steps provided below.

Perform ‘Prepare using Sysprep - Configure:’ prerequisite tasks:

1. Disable Automatic update of Windows Store apps
   Open ‘Windows Store’
   Click ‘Windows Start Button > Store’
   For build 1703 click on the three horizontal lines in the upper left-hand corner
   For build 1709 click on the person icon
   Click ‘Settings’
   Move slider on setting ‘Update apps automatically’ from ‘on’ to ‘off’
2. Use ‘Windows update’ to install latest patches to the system.
3. Install Ghost Solution Suite Dagent on client machine
   Use the Remote Agent Installer to push the Dagent to the client machine.

Go to this link for your reference https://knowledge.broadcom.com/external/article/171149/preparing-windows-10-or-windows-11-to-ru.html

Note: This is a non-Microsoft website kindly take precautions before downloading anything.

--------------------------------------------------------------------------------------------------------------------------------------------------

If the answer is helpful kindly click "Accept as Answer" and upvote it. Thanks.

Answer 2

Same issue here and after joining Workgroup instead of Domain it starts working. Now I only have issues with application installation due to SSL issues. Domain certificate is not loaded now.

Answer 3

Same here.
After the reboot stuck at "Getting Ready". Machine is domain joined.

Later, I attached the virtual disk of the failed machine to another VM so I could go search for clues. Although the sysprep did succeed, I saw something curious :

2022-10-18 15:05:39, Info SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Generalize_Net' from C:\Windows\System32\spnet.dll
2022-10-18 15:05:39, Info [0x0f0008] SYSPRP spnet.dll::IsDomainMember:This machine is not joined to a domain
2022-10-18 15:05:39, Info [0x0f000e] SYSPRP spnet.dll::UnjoinNetworkDomain:Not a domain member, nothing to do
2022-10-18 15:05:39, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Generalize_Net' from C:\Windows\System32\spnet.dll

Sysprep states the machine is not joined to a domain, although it clearly is. You guys have the same?

Also can confirm that leaving the domain manually before running sysprep, does not help.

Answer 4

I tested deployment with the "CryptoSysPrep_Specialize" workaround and that seems to work fine.....

Answer 5

I think i found a simple workaround for those of you (like me) who are struggling with this issue.

1. Apply your current image to a VM (like you would normally do when updating the image)
2. Purposely cause the domain join to fail during OOBE (use bad domain join credentials or cut the network or something).
3. After the domain join step fails, OOBE will give up trying to join the domain and bring you to a logon screen.
4. In my case, the local admin account was disabled (so i couldn't login), but i had an agent running on it that allowed me to re-enable the admin account and login as admin with a "net user administrator active:yes" or similar command.
5. Once you get logged in you can now update your image and sysprep it like normal. just don't join the domain!