Fix Task Sequence Delays in Windows 11 24H2 During Bare Metal Deployment in SCCM
Let’s discuss Fix Task Sequence Delays in Windows 11 24H2 During Bare Metal Deployment in SCCM. Some reporting issue When installing Windows 11 version 24H2 from scratch (called “bare metal deployment”), the process is much slower than when installing Windows 10.
The Admins follows nearly the same setup steps for Windows 11 and Windows 10 devices, but Windows 11 takes longer to move through certain parts of the installation. In 2 places Admins feels slower which are After a reboot and at the very end.
After a reboot, Windows 10 takes about 1 second to continue setup after restarting and Windows 11 takes around 2 minutes. At the very end, Windows 10 finishes up in about 14 seconds and Windows 11 takes over 4 minutes.
Due to this issue, admins seeking helps to fix the issue. Admins are confused why it’s taking such a longer time to deal with policy work in 24H2? Is this a Win11 24H2 issue, a ConfigMan issue, or ConfigMan configuration issue?
Table of Contents
Fix Task Sequence Delays in Windows 11 24H2 During Bare Metal Deployment in SCCM
The root cause of this issue due to mismatch between he Windows 11 24H2 image being deployed, the ADK version used to build the boot image, possibly missing SCCM hotfixes or updates (KB33177653, KB34503790). The below table shows the environment details.
| Environment Details |
|---|
| CM 2503 (5.0.9135.1000) without KB33177653 or KB34503790 installed. Windows 11 = 24H2 customized reference image built from August 2025 ISO. ADK = 21H2 (10.1.22000.1). |
- How to Fix Windows 11 24H2 Download Issue using WSUS SCCM
- SCCM 2503 Step-by-Step In-Console Update Guide and Key Improvements
- SCCM Task Sequences with UI++Now Open Source on GitHub
Difference between End of the Task Sequence of Winodws 10 22H2 and Windows 11 24H2
At the end of the task sequence, after executing the last task, following The task execution engine successfully completed the current task sequence step smsts.log entry to when the smsts.log stops being written to, it takes 14 seconds for the Windows 10 device.
At the end of the task sequence, after executing the last task, following The task execution engine successfully completed the current task sequence step smsts.log entry to when the smsts.log stops being written to, it takes 4:29 seconds for the Windows 11 device.
Suggested Fixes for this Issue
Update to the latest version of ADK and WinPE (another setup tool). That should help speed things up by making the tools better match the version of Windows being installed.
Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.
Discussion