My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.

Hi,

I agree to this conclusion at this time.

Greetings

My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.

@Greg_E
Hi Greg_E

Thanks for your detailed report and informations I will try it with delayed start. It could be a solution indeed. When i have news on this, i will share it here.

@archw
Hi, i thought the same today so i gave a try. But unfortunately at my test server fully patched with fresh ADDC on it there are the same issues present. But i have to say that i did not a detailed test at this time.

@archw

You should also notice that you cannot run any task scheduler tasks any longer. The task starts, but the action is not taken and after the timeout it end. Also any .msi package cannot be installed due to the Windows Installer Service is not able to start.

@Greg_E

Hi Greg_E

Yea, that are exactly the same findings as mine

I think to disable the Service could be a workaround for the moment. 9.4.0 did not make a difference compared to 9.3.0.

We will start our new project with 2025 with workaround in place and monitor the situation when a new version become available where the issue may have been fixed.

I'm glad for any further comment on this topic when new informations become available from any the community members or the devs

Have a nice evening!

@Greg_E

Hello Greg_E

I would be interested to know if you have had the opportunity to take a look at the problem I described? Were you able to reproduce the behavior?

The server has been released in the meantime (some may even have been accidentally updated to 2025 ) so the problem should soon become more noticeable among early adopters.

I have gained new insights. First of all, I have to add that I have found another symptom.
Taskscheduler tasks are not executed correctly.
The tasks are started, but do not execute the action and then run into the task timeout.
This could be related to conhost processes.
After the fresh installation of the Citrix tools, these problems do not occur once.
At this point the Citrix Management Agent Service starts as intended.
But at the next reboot the problem seems to start.
I also noticed that after the reboot the Citrix Tools Management Agent Service gets stuck in the “Starting” state.
As soon as this process hangs there, the Conhost problems also start.
If I then set the Management Agent to “Disabled” so that it is not started when booting, the Schedules tasks work again.
Interestingly, no more Conhost processes are generated.
It seems that this hanging XenTools management service is blocking the task scheduler and its functions of other services.
This is why, for example, it is no longer possible to install an MSI package without deactivating the Management Agent Service.
I hope I have expressed myself reasonably clearly

EDIT:
As said in one of my first posts, this behaviour only applies to Server 2025 with ADDC Role installed on it and promoted to DC.
Memberserver or standalone servers does not show this behaviour.

I will give you a brief interim report.
Nothing has changed so far. After about 6 days I have almost 600 conhost processes again.
I have currently activated weekly reboots as a workaround.
On my Hyper-V test VM, this has still not occurred after 16 days.

@Greg_E

Hi Greg_E

Yea, the drivers are the latest available directly from citrix / XenServer.com.