![](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(185.6, 95%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJK%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(284.8, 33%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDV%3C/text%3E%3C/svg%3E)
Dear Jashir K,
Based on your description, it appears the Windows 11 upgrade task sequence is not being received by one of the systems, and the absence of the SMSTS.log file suggests the task sequence has not yet begun execution.
To begin troubleshooting, please verify that the device is part of the correct collection targeted by the deployment and that the deployment is marked as “Available” or “Required” for the client. Additionally, confirm that the SCCM client is healthy and fully registered with the site—checking ClientIDManagerStartup.log and LocationServices.log may help identify registration or policy retrieval issues.
Since the SMSTS.log file is only generated once the task sequence starts, its absence indicates the task has not been triggered. Reviewing the Execmgr.log for any policy evaluation or advertisement errors is a good next step. Also, ensure that the client has received the latest machine policy and that there are no boundary or content access issues.
I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Best regards,
Domic Vo