Hello, I had freezes of the console, which do not appear any more, I do not know any more exactly what I did on my W11 pro 24H2 new on XCP 8.3 on XOA, I tried at best to :
Disable the VM screen shutdown
Disable standby
Set to maximum performance
The screen is still “active” and not black

But I have another problem, probably related to microsoft, the vm freezes again but completely, inacessible in rdp, console, mouse keyboard, CPU and MEMORY statistics graphs freeze on XOA, restarting the VM by force is mandatory

24H2 has a lot of problems, notably the RDP freeze which also happens to me sometimes, impossible to rdp, sometimes yes sometimes no, I also modified the local strategy concerning this freeze problem but well... We'll see, Microsoft doesn't test its products anymore

EDIT : For RDP Freeze, on the VM, there is a strategy local who fix the bug :

1. Stratégie de l'ordinateur local > Configuration ordinateur > Modèles d'administration > Composants Windows > Services Bureau à distance > Hôte de session Bureau à distance > Connexions > Sélectionner la détection du réseau sur le serveur
   --> définir sur Activé
   ----->Chosir : Désactiver la détection du temps de connexion et la détection continue du réseau

2. do a : gpupdate /force

3. RDP Works fine now on W11 24H2

@Biggen said in [WARNING] XCP-ng Center shows wrong CITRIX updates for XCP-ng Servers - DO NOT APPLY - Fix released:

This is the reason I think xcp-ng Center should be abandoned and a prebuilt/stripped down XOA should be provided and take its place. People can then upgrade to a full blown XOA if they wish.

Having to maintain two points of entry seems a waste of resources and fraught with another way bugs could enter the system.

Glad you caught it!

XCP-NG Center is the Best interface GUI that I never seen for an hypervisor, simple fastest we see everything we need, the console is large, dont need to click 1000 time to find informations... Thanks to development team to continue to provide this soft, I use XCP-NG because this interface exist, I dont really like the New Web interface mode in our century, slow, refresh thé Web page, bug, slow console... Lot of Web in our century, it is an error to put everything in Web mode, like to put everything in the cloud, and have à management interface out of the hypervisor is smart, because if your internal management interface in VM MODE is broken, and if you dont have other solution, your dead

@dinhngtu Hi everyone,

Thank you all so much for your help and suggestions. After several tests, I’ve decided to stop troubleshooting and stick with Windows 10 in BIOS mode. UEFI doesn’t work properly for me, whether with Windows 10 or 11, but everything runs fine in BIOS mode.

I really appreciate the time and support from this great community!

@dinhngtu

I don't have a solution yet, so I'm going to do some more tests and install Windows 11:
23h2 --> if ok, ok otherwise :
22h2 --> if ok, ok otherwise :
21h2 --> if ok, ok otherwise :
WINDOWS 10 !

@dinhngtu

I spoke too quickly:

The problem finally came back, I've got at least an exact timestamp of the different phases, I'll see if I can find something, but it seems compromised.

@dinhngtu

Update: I haven't experienced any freezes in the last 24 hours. Here are the actions I performed during that time:

• Installed Windows update KB5052093 (February 2025, 24H2 preview)
• Reinstalled Xen Tools
• Installed a Prometheus exporter
• Installed a Wazuh agent

At this point, I’m considering a few possibilities:

• Microsoft might have fixed the bug with the update (most likely?)
• The Xen Tools reinstallation resolved it ? (less likely)
• The Prometheus exporter and Wazuh agent generate enough micro-activity to prevent the machine from freezing or hibernating ?
• The new Microsoft "Energy Saver" technology was causing the issue and is now fixed?
• Or maybe the bug just hasn't had time to reappear yet?!

I'll keep monitoring and report back if anything changes. Has anyone else noticed improvements after the recent update? (RDP bugs are resolved!)

Hi @dinhngtu , it is frozen

EDIT :
I'm installing prometheus and grafana and winsows exporter to have date, time and metrics for CPU, when freeze arrive, exact date and time, to coroborate logs

There is a new update on 24H2, correct RDP bugs, maybe freeze bug ? I test and i'm back if i have more informations :

https://www.it-connect.fr/windows-11-kb5052093-quels-sont-les-changements-apportes-par-cette-mise-a-jour/

"Il y a deux bugs corrigés dans la fonctionnalité de Bureau à distance, notamment où l'application cesse de répondre, et un autre bug lié à des problèmes d'affichage."

Hi everyone,

I'm experiencing a strange issue with a freshly installed Windows 11 Pro 24H2 VM on my XCP-NG 8.3 host. The VM runs fine for some time but then randomly freezes. Here’s what happens:

• The RAM usage graph in XOA freezes at the last recorded value.
• CPU drops to 0% usage.
• RDP disconnects and never comes back.
• XOA console is completely frozen, making interaction impossible.
• The VM still responds to ping (Uptime Kuma reports no ICMP downtime).
• Trying to connect via RDP results in a loading screen for several minutes, but eventually fails.
• It looks like the VM goes into some weird sleep/hibernation mode and won't wake up.
• The only solution is a forced reboot via XOA/XCP-ng Center.
• The Xen Tools are installed and up to date.

Does anyone have any idea what might be causing this? I'm completely stuck...

Here’s a graph showing the issue:

Thanks in advance for your help!

@dinhngtu Hi everyone,

Thank you all so much for your help and suggestions. After several tests, I’ve decided to stop troubleshooting and stick with Windows 10 in BIOS mode. UEFI doesn’t work properly for me, whether with Windows 10 or 11, but everything runs fine in BIOS mode.

I really appreciate the time and support from this great community!

@DevilDan it boot after re-enabled secure boot, i set 2 cpu not 4 like before

@DevilDan

I roll back action, freeze always, I set 2 CPU (not 4) and now i have blue screen :

@dinhngtu I try process, it freeze now at every boot :

@DevilDan I see, we have to disable secure boot, but it is mandatory for Win 11 NO ?

@dinhngtu You're right, in the first freezes, the CPU would drop to 0%. Now, in recent cases, one freeze spikes the CPU to 100% and then it drops, while another stays at 100%...

The VM still responds to ping for a while, but it eventually stops sometimes hours later. The console screen remains frozen on the Windows lock screen.

I'll look into your procedure and see if I can try it.

@dinhngtu I had freeze on Win 10 UEFI mode, not in BIOS mode, I have only this example 24H2 UEFI Bug, 23H2 UEFI Bug, Win 10 Uefi Bug, Windows 10 BIOS OK

@DevilDan

Console is... Frozen again..... I Think it's UEFI problem, Win 10 BIOS MODE no problem....

@DevilDan No bugs for the moment, PS : I choose the "other-media-install" template with all VM, maybe the static min memory is impacted finally ?

EDIT : 20 MARCH 2025 20H45 : always NO PROBLEM

@cirosantos0

Thanks! I changed this parameter yesterday, and everything is set to the exact same value down to the byte.

No bugs so far, but I did notice some CPU usage differences between Windows 10, Windows 11 23H2, and Windows 11 24H2. Only Windows 11 24H2 constantly consumes more CPU, staying between 6-10%, while the other versions peak between 0-3%. 24H2 is really bad...

That being said, the freezes don’t seem related to this. Let’s see if changing the static min RAM makes a difference. Would be great if it does! We’ll adjust accordingly.