Windows Server 2025 on XCP-ng
-
Hi,
Are you sure it's not a Windows issue itself?
-
Hello Olivier
Thank you for your quick reply.
I have not investigated this topic further as the server is still in preview at the moment and things can change quickly.
I have to say that the Windows is more or less freshly installed with an AD role on it.
Nothing else has been done.
So I just wanted to ask in advance whether other community members have already had any testing experience or whether any of you developers have any experience, plans or background information.Best regards
-
Got it, let's see if there's other Windows Server 2025 users around it!
-
@Chemikant784 I have Windows Server 2025 installed on XCP 8.3 and I don't see and conhost.exe processes. Normally I have 2025 shut down, I'll leave it running and see if I find any stuck processes.
Both XCP 8.3 and WS 2025 are fully updated and using XenTools 9.3.3-125.
-
WinServ 2025 on xcp-ng 8.2.1, xcp-ng tools v.8.2.2 rc1. No additional roles, except Windows Admin Center preview installed. Uptime about 2 months. No conhost processes at all.
-
I currently suspect that the ADDC role could cause this on the 2025 server. I have reinstalled the server with the new ISO to 8.2.1 to see how it works. No entries for a few days. But as soon as the ADDC role is installed, it starts. Could also be due to the role itself. I haven't tested this on any other hypervisor yet. If it occurs also on others it's not related to XCP-ng
-
Conhost process is related to command-line / console apps. It could be that something (either a server role in Win Server 2025, or perhaps the Citrix/XCP-ng guest tools, or at worst malware) is stuck in a loop and spawning these multiple instances.
If you absolutely need to salvage this particular OS install, perhaps hunt through the process IDs to find what is spawning them, or setup some debug/trace tools to determine the same. Or try remove roles / software one at a time to see which one, if any, stop the conhost spawning.
EDIT: must have missed your previous post where you've nailed it down to the ADDC role. If you typically install the role via GUI, switch to PowerShell to see if the same problem persists, or vice versa, if you typically use PowerShell, switch to the GUI
Beyond that, I have no insights except to point at the current "Preview" status of Win2025. I'm not familiar with which OS components (not to mention server roles, frameworks, etc.) Microsoft have re-used and which are entirely new.
Also, sadly, conhost process issues have been a sporadic problem in Windows for decades...
-
Hi
Thanks for your reply.
Yes you are right. It's not the first time that this problem occurs within windows.
To countercheck i've set up a comparable vm on another hypervisor to see if it behaves differently.
Also at this time i would think it's not XO backup related because my second scenario does not make any backups.
I will report back how it goes.
-
Installed AD DS role on my test Winserv2025 VM and conhost processes are appeared and already gone from 7 to 10 in about hour. In the same pool Winserv2022 AD DC VM no conhost processes at all.
-
@TS79 said in Windows Server 2025 on XCP-ng:
Also, sadly, conhost process issues have been a sporadic problem in Windows for decades...
What hasn't ??????
-
I have now found time to run a test VM on another hypervisor (Hyper-V).
It is also freshly installed and an ADDS role has been set up on it.
My observations show that the VM has now been running for 3 days and so far no hanging conhost processes have occurred.
I will continue to monitor this for a while. -
I'll have to try installing this on my lab which is XCP-NG 8.3.0 and see what I see (downloading now at very slow speeds).
Did you try the latest management tools and drivers from https://www.xenserver.com/downloads
This is version 9.3.3 and latest drivers.
-
-
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. -
@Chemikant784 I haven't had time to check this, I don't even remember where I put the 2025 eval, but I'll get to it soon. If I put the eval on my VMware system, then I'll likely try it sooner and remember to put it on my XCP-NG system too.
-
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 clearlyEDIT:
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. -
Hmmm... That interesting that it has some kind of tie in with the management agent and ADDS. I still haven't even thought about this, but I like to stay on top of the server versions so I can figure out what I need for when I need it.
Even Win11 24h2 has some oddities, and I'm running it on metal, this is the LTSC version, but shouldn't matter. I turned off hyperthreading on one machine and it was not happy compared to HT left on. Might have to do with being an older HP Elitedesk 800 G6 (intel 10500).
Since Server 2025 is based on 24h2, I might have to load up the LTSC eval or Enterprise eval as well as Server 2025 eval when I get some time.
-
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 haven't, but I just grabbed the latest eval version which seems to be refreshed for release. I need to set up an AD with DHCP and DNS in my lab to move forward on some VMware learning, so I'll get to this soon. I just finished harvesting the vmware products from my VMUG Advantage account since Broadcom is doing their thing and killing these lab licenses (just announced a few day ago)!!! Broadcom leaving no stone unturned in their quest to really make people hate them!
Any gotchas I should look out for aside from the issue you are having? I'll run through the GUI role/feature installer and of course will install the OS with desktop.
-
I created a VM using the RTM release ISO and installed the latest Citrix tools (9.4), i've left this VM running for 5 days now and i don't see any runaway conhost.exe processes, granted the VM is just sitting there doing nothing.
