TRogers

@NolaITGuy I posted the solution above but forgot to quote you. Making those changes didn't seem to cause any issues but it's still a bit sketchy having to change the sysprep configuration files for it to work properly.

Ended up getting it figured out. The problem is a sysprep bug on W11 22H2 only. It works fine on W11 22H1. The lines in the file "C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml" with "Capisp.dll" need to be removed for it to image properly.

I am using the best practice standards with Hyper-V found at https://support.smartdeploy.com/support/solutions/articles/48001201629-capturing-and-deploying-windows-11 I am also shutting down before capture using "shutdown /s /t 0" as stated on https://support.smartdeploy.com/support/solutions/articles/48000960051-best-practices-to-create-your-reference-virtual-machines

Hello, I am currently working on our company's upgrade to Windows 11 from Windows 10 with a brand-new image. There is one program that requires the image be put on our domain to be installed correctly. Adding the image to the domain and then putting it back to workgroup before capturing it is causing the deployment to fail at the post sysprep "Getting Ready" stage. It sits there endlessly and never fails. I left a laptop sitting at this stage for over 48 hours to see if anything would eventually happen. If I manually reboot the installer, it says "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation". I am attempting to deploy the image with both ISO and Push methods. If I leave the image with all other steps done to it except adding to the domain, it works as expected and deploys to multiple systems and VMs. I have narrowed down the failure to adding the image to the domain. The default OU it is being added to does not apply any group policy. This process has also worked successfully on Windows 10. What steps should I take to further investigate this issue, or where can I attempt to gather logs for this issue?