vI don't know if any one else has seen this I have at least one server so far that we were testing updates on that will not boot after appling the Windows 2016 server October 2025 roll-up update. Out host cluster is 3 hosts with a fiberchannel SAN - VM's hosted on the SAN.
current version of the host:
pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-11-pve)
VM is a converted VMware vm using Veeam backup and restore for the conversion process - VM has system drive and an EFI drive - replacing the EFI drive does not fix the issue. So far only a restore of the system prior to the update fixes the system, but the moment that the Window roll up update is applied the system no longer boots and is stuck on the proxmox boot screen with spinning windows cirlce, or produces a windows Blue screen as attahced.
I also updated the subscribed proxmox system to currently release on one Host and the issue persists with the same erorr shown here:
Updated Host versoin: pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve)
I am happy to provide any further informaiton that may help, has anyone else run in to these issues? This particular system failed on October 15th when the update was installed, luckily it was a application server that is rarely used. The system failed anytime the update is installed. Any help would be wonderful, I can open a case with Proxmox if needed but I figured I woudl start here first.
Thank you.
current version of the host:
pve-manager/8.4.1/2a5fa54a8503f96d (running kernel: 6.8.12-11-pve)
VM is a converted VMware vm using Veeam backup and restore for the conversion process - VM has system drive and an EFI drive - replacing the EFI drive does not fix the issue. So far only a restore of the system prior to the update fixes the system, but the moment that the Window roll up update is applied the system no longer boots and is stuck on the proxmox boot screen with spinning windows cirlce, or produces a windows Blue screen as attahced.
I also updated the subscribed proxmox system to currently release on one Host and the issue persists with the same erorr shown here:
Updated Host versoin: pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve)
I am happy to provide any further informaiton that may help, has anyone else run in to these issues? This particular system failed on October 15th when the update was installed, luckily it was a application server that is rarely used. The system failed anytime the update is installed. Any help would be wonderful, I can open a case with Proxmox if needed but I figured I woudl start here first.
Thank you.