![](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(227.2, 9%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYY%3C/text%3E%3C/svg%3E)
![](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(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIN%3C/text%3E%3C/svg%3E)
Welcome to Microsoft Q&A forum.
Thank you for reaching out regarding your Windows 11 deployment strategy.
Regarding your query about performing a feature update (23H2 > 24H2) prior to running Sysprep: To maximize stability and image integrity, we recommend building your golden image from a clean Windows 11 24H2 installation rather than upgrading a 23H2 reference device and then Sysprepping. In‑place upgrades alter the OS state, especially with Microsoft Store (Appx) provisioning and system configuration, making Sysprep /generalize more likely to hit validation issues or post‑generalize boot issues on 24H2.
Recommended procedure:
- Clean install Windows 11 24H2 (Volume Licensing media as needed). Windows 11 image creation for OEMs
- Customize in Audit Mode (Ctrl+Shift+F3) and avoid Store app updates or per‑user changes. Sysprep (Generalize) a Windows installation
- Run Sysprep (/generalize /oobe /shutdown) and capture the image (DISM/WinPE/MDT).
This approach yields a generalized, clean image without artifacts from prior versions and aligns with standard Windows deployment methodologies.
I hope it clears your concerns. Should you have any further questions or concerns, please feel free to reach out.