Guest Agent not running Windows Server 2025

goldsmith

Active Member
Apr 11, 2019
7
0
41
Hello, Team.

I encountered this problem, after installation the agent works for less than a day, I tried different versions 285,271,266 with all the same problem.
Windows Server 2025 Version 24H2 Build 26100.32860.

It is impossible to restart the service from the system; the entire operating system must be rebooted.

Config Proxmox
Code:
proxmox-ve: 9.1.0 (running kernel: 7.0.2-4-pve)
pve-manager: 9.1.14 (running version: 9.1.14/7d542528ee1851f7)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-7.0: 7.0.2-4
proxmox-kernel-7.0.2-4-pve-signed: 7.0.2-4
proxmox-kernel-6.17.13-9-pve-signed: 6.17.13-9
proxmox-kernel-6.17: 6.17.13-9
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.6.1-1+pve2
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.1.1
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.5
libpve-cluster-perl: 9.1.5
libpve-common-perl: 9.1.12
libpve-guest-common-perl: 6.0.3
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.5.1
libpve-notify-perl: 9.1.5
libpve-rs-perl: 0.14.1
libpve-storage-perl: 9.0.18
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 7.0.0-1
lxcfs: 7.0.0-pve1
novnc-pve: 1.7.0-1
proxmox-backup-client: 4.2.0-1
proxmox-backup-file-restore: 4.2.0-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.2.1
pve-cluster: 9.1.5
pve-container: 6.1.8
pve-docs: 9.1.4
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-3
pve-ha-manager: 5.2.3
pve-i18n: 3.7.1
pve-qemu-kvm: 11.0.0-2
pve-xtermjs: 6.0.0-1
qemu-server: 9.1.12
smartmontools: 7.5-pve2
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.3.4-pve1

Config VM:
Code:
agent: 1
bios: ovmf
boot: order=sata0;ide2;net0
cores: 8
cpu: x86-64-v2-AES
efidisk0: hs-ala-pmh-ds03:vm-168-disk-0,efitype=4m,ms-cert=2023k,pre-enrolled-keys=1,size=528K
hotplug: disk,network,usb,memory,cpu
ide2: none,media=cdrom
machine: pc-q35-11.0
memory: 16384
meta: creation-qemu=11.0.0,ctime=1779963536
name: vm
net0: e1000=BC:24:11:69:4F:28,bridge=vmbr120,firewall=1
numa: 1
onboot: 1
ostype: win11
sata0: hs-ala-pmh-ds03:vm-168-disk-1,size=200G
scsihw: virtio-scsi-single
smbios1: uuid=4771cadd-7c23-4af9-938e-259e7f0cc3c9
sockets: 2
vmgenid: e506f8db-a5b7-495f-b377-1078e339bb02
 
is during backup ?
No, I don't backup virtual machines at all. That's why I want to figure this out, I have this problem on almost all of them WS 2025. Why does it freeze? The QEMU service can't be restarted; the entire operating system needs to be restarted.
 
have you tried with win 2022 ?
Unfortunately, it is not possible to check the 2022 version since it is licensed for 2025. I still think there's something wrong with the operating system itself. But I haven't figured out how to figure it out yet.
 
Microsoft allows downgrade. you need to get media and product key yourself or ask your OEM manufacturer.
Media/Keys sources are not really relevant, proof of the original 2025 purchase is.
You can try the eval ISO to dig out. win11 eval ISO can be used too as they use same binaries, same build 26100.
is there a MS SQL running ?
btw, no problem here with two 2025 VMs since day one, 1 on PVE 9.2 + 1 on PVE 8.4.