PENDING Windows 11 and Tasksequence

[gfritz]

Hello everyone,

I'm having an issue with Windows 11 24H2 and the execution of task sequences via MECM.
I'm launching the task sequence using a script from the Software Center – it appears and is marked as started immediately.
However, it usually takes about 7 minutes until the task sequence actually begins running as defined in MECM.

Here's an excerpt from the smsts.log:

Shutdown complete.  TsProgressUI  20.05.2025 13:27:38  8104 (0x1FA8)

Successfully initialized Logging for Task Sequence Manager.  TSManager  20.05.2025 13:34:30  18112 (0x46C0)

Nothing happens during this time. It doesn't matter whether I use a script or deploy a package in the task sequence – the behavior is always the same.
On Windows 10, everything runs smoothly and without delay. This only happens on Windows 11.

Has anyone else experienced this issue or found a solution?

Thanks in advance and best regards!
gfritz

 

[Stanley Road]

Is it an upgrade TS?

 

[gfritz]

Is it an upgrade TS?

This concerns a PowerShell script – but the script itself is not the issue.

After conducting some research, I identified a problem that explains the significant performance difference between Windows 10 and Windows 11 when executing the “Downloading policy body {example}” task.
It appears that Windows 11 takes considerably longer to perform this operation.

While Windows 10 processes approximately 20–23 policies per second, Windows 11 only manages about 2 per second.
Given that around 750 policies need to be processed in our case, this results in a considerable delay – which, of course, is problematic in a corporate infrastructure.

For your reference, I have attached the respective TSAgent.log files.
Do you happen to have any idea what could be causing this behavior?

 

[Stanley Road]

I'm curious why "Executing Policy Body Request locally" cant be found anywhere in your W10 log? Are you sure the W10 deployment works correctly? Just asking

 

[gfritz]

I'm curious why "Executing Policy Body Request locally" cant be found anywhere in your W10 log? Are you sure the W10 deployment works correctly? Just asking

Yes im Sure. You can See in the TSagent.log from Windows 10.