The usage of wub windows update blocker in fresh win10 1803 vm obliterates the vm.
(https://www.sordum.org/9470/windows-update-blocker-v1-7/)
On reboot after install, windows will not boot, and you get critical error.
All troubleshooting fails, safe boot critical error, startup recovery fails, boot logging critical error
Rolling back to snapshot, reenabling windows update through wub, reboot, everything works.
This makes zero sense to me, I dont believe this to be a proxmox issue, but I also don't believe this to be a wub issue.
How can disabling a windows service, kill safe boot ?
This behavior does not exist on esxi, as i have been using wub for years over there.
Does anyone have any ideas ?
I've sent a message to wub developer regardless.
****
More detail:
I'm new to proxmox, but been using esxi for years, was banging my head against this for the past day, finally resorted to trial and error.
Thought it was the cpu flags, maybe the virtio drivers, maybe the cache, or the async, maybe the machine type.
I did a fresh install, all defaults, and started going one by one, and restarting.
After disabling windows update through wub, thats when it stopped restarting.
Went back to my original VM, live snapshot after disabling windows update through wub, and reenabled windows update through wub.
Rebooted and everything was good.
Fresh proxmox 7 install
The install disc boots, and I get all the way to the desktop, at which point Im thinking Im good.
I install virtio drivers, agent, pause windows update, disable windows update with wub, enable rdp, set timezone.
I then restart, and get critical error.
I have tried this numerous times now with different iterations, to make sure any changes I made were not breaking anything.
Which led me to wub being the issue.
(https://www.sordum.org/9470/windows-update-blocker-v1-7/)
On reboot after install, windows will not boot, and you get critical error.
All troubleshooting fails, safe boot critical error, startup recovery fails, boot logging critical error
Rolling back to snapshot, reenabling windows update through wub, reboot, everything works.
This makes zero sense to me, I dont believe this to be a proxmox issue, but I also don't believe this to be a wub issue.
How can disabling a windows service, kill safe boot ?
This behavior does not exist on esxi, as i have been using wub for years over there.
Does anyone have any ideas ?
I've sent a message to wub developer regardless.
****
More detail:
I'm new to proxmox, but been using esxi for years, was banging my head against this for the past day, finally resorted to trial and error.
Thought it was the cpu flags, maybe the virtio drivers, maybe the cache, or the async, maybe the machine type.
I did a fresh install, all defaults, and started going one by one, and restarting.
After disabling windows update through wub, thats when it stopped restarting.
Went back to my original VM, live snapshot after disabling windows update through wub, and reenabled windows update through wub.
Rebooted and everything was good.
Fresh proxmox 7 install
The install disc boots, and I get all the way to the desktop, at which point Im thinking Im good.
I install virtio drivers, agent, pause windows update, disable windows update with wub, enable rdp, set timezone.
I then restart, and get critical error.
I have tried this numerous times now with different iterations, to make sure any changes I made were not breaking anything.
Which led me to wub being the issue.
Bash:
root@wraithe:~#
root@wraithe:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.11.22-7-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
root@wraithe:~#
root@wraithe:~#
Bash:
agent: 1
bios: ovmf
boot: order=ide0;scsi0;net0
cores: 8
cpu: host,hidden=1
efidisk0: local-lvm:vm-100-disk-1,size=4M
ide0: none,media=cdrom
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1647461082
name: vfio-wintest
net0: virtio=B2:BE:0E:63:3F:A7,bridge=vmbr0
numa: 0
ostype: win10
scsi0: local-lvm:vm-100-disk-0,size=120G
scsihw: virtio-scsi-pci
smbios1: uuid=c79634d9-0a27-4e7a-ad6f-dfae46e63ba8
sockets: 1
vmgenid: f88fc0d8-f9d8-4346-89c3-7228518f39a9
Bash:
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;scsi0;net0;sata0
cores: 8
cpu: host,hidden=1
efidisk0: local-lvm:vm-101-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/Win10_Edu_1803_English_x64.iso,media=cdrom
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1647711936
name: win10-baseline
net0: virtio=3E:00:5D:51:C7:A7,bridge=vmbr0
numa: 0
ostype: win10
parent: win10_installed
sata0: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
scsi0: local-lvm:vm-101-disk-0,discard=on,iothread=1,size=150G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=7b193d61-178c-4f76-be2e-a765194f6b33
sockets: 1
vmgenid: 920e2c1a-e31a-4003-a942-aa5c04321812
[bare_metal]
#never booted
#never installed
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;scsi0;net0;sata0
cores: 8
cpu: host,hidden=1
efidisk0: local-lvm:vm-101-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/Win10_Edu_1803_English_x64.iso,media=cdrom
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1647711936
name: win10-baseline
net0: virtio=3E:00:5D:51:C7:A7,bridge=vmbr0
numa: 0
ostype: win10
sata0: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
scsi0: local-lvm:vm-101-disk-0,discard=on,iothread=1,size=150G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=7b193d61-178c-4f76-be2e-a765194f6b33
snaptime: 1647714896
sockets: 1
vmgenid: 7b8d93bd-4f4b-411b-8ff8-024eb8bb1190
[fubar]
#does not boot
#fubar critical error
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;scsi0;net0;sata0
cores: 8
cpu: kvm64
efidisk0: local-lvm:vm-101-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/Win10_Edu_1803_English_x64.iso,media=cdrom,size=4582388K
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1647711936
name: win10-baseline
net0: virtio=3E:00:5D:51:C7:A7,bridge=vmbr0
numa: 0
ostype: win10
parent: win10_installed
sata0: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
scsi0: local-lvm:vm-101-disk-0,discard=on,iothread=1,size=150G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=7b193d61-178c-4f76-be2e-a765194f6b33
snaptime: 1648756021
sockets: 1
vmgenid: 7b8d93bd-4f4b-411b-8ff8-024eb8bb1190
[win10_installed]
#- win10 installed
#- virtio drivers installed
#- virtio guest tools installed
#- paused windows updates
#- wub deactivated windows updates
#- rdp enabled
#- timezone to eastern
#- windows activation key saved to c%3A/key.txt (not activated)
#- copied over some files
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;scsi0;net0;sata0
cores: 8
cpu: host,hidden=1
efidisk0: local-lvm:vm-101-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: local:iso/Win10_Edu_1803_English_x64.iso,media=cdrom
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1647711936
name: win10-baseline
net0: virtio=3E:00:5D:51:C7:A7,bridge=vmbr0
numa: 0
ostype: win10
parent: bare_metal
runningcpu: host,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,kvm=off,+kvm_pv_eoi,+kvm_pv_unhalt
runningmachine: pc-q35-6.1+pve0
sata0: local:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
scsi0: local-lvm:vm-101-disk-0,discard=on,iothread=1,size=150G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=7b193d61-178c-4f76-be2e-a765194f6b33
snaptime: 1647774310
sockets: 1
vmgenid: 7b8d93bd-4f4b-411b-8ff8-024eb8bb1190
vmstate: local-lvm:vm-101-state-win10_installed
Bash:
agent: 1
balloon: 0
bios: ovmf
boot: order=ide2;scsi0;net0;sata0
cores: 8
efidisk0: local-lvm:vm-102-disk-1,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1648771409
name: win10-t2-baseline
net0: virtio=52:51:3F:31:00:4E,bridge=vmbr0
numa: 0
ostype: win10
sata0: none,media=cdrom
scsi0: local-lvm:vm-102-disk-0,discard=on,iothread=1,size=300G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=fb44b50f-d03d-4bc4-ba29-d4d9a8dac2ce
sockets: 1
vmgenid: 6dbb5cca-e25e-43d2-af47-f03fc2aeb966
Bash:
boot: order=ide0;ide2;net0;ide3
cores: 8
ide0: local-lvm:vm-103-disk-0,size=320G
ide2: none,media=cdrom
ide3: none,media=cdrom
machine: pc-i440fx-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1648811110
name: test
net0: e1000=9A:91:42:42:48:A7,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=2e72005d-21ef-4e27-a5a8-d5f185c88cac
sockets: 1
vmgenid: 6206edaa-c5eb-4fbd-a3b9-20f28920826d
Bash:
boot: order=ide0;ide2;net0
cores: 8
ide0: local-lvm:vm-104-disk-0,size=320G
ide2: none,media=cdrom
machine: pc-i440fx-6.1
memory: 8192
meta: creation-qemu=6.1.1,ctime=1648813073
name: test-novirtio
net0: e1000=0E:75:10:8E:22:DE,bridge=vmbr0
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=05404542-c432-4653-b151-b88ce7b84254
sockets: 1
vmgenid: 3049b3fe-55ae-4f6b-bda7-71f0429a5323