[SOLVED] Anti-Cheat KVM Settings

Well, I did everything you did, and it finally changed from QEMU Device to ASUS System Device. However, loading Halo Infinite still causes it to cancel out and close the game. I cannot activate "args: -cpu host,-hypervisor,kvm=off" as my computer gets stuck in the windows boot logo. Any other ideas I can try?

View attachment 59645
Just hv_vendor_id=amd !!! its work!
args: -cpu host,-hypervisor,hv_vendor_id=amd
 
Hello, I'm also having problems with the NewWorld game. I can't start the game, it detects directly that it's a VM.
error message: cannot run under Virtual Machine.
I've tried your configurations but the problem is still there.
I may have made some errors in my .conf file (present on /etc/pve/nodes/pve/qemu-server)?

Can you help me please ?

Here is my Proxmox server:
CPU(s)

24 x AMD Ryzen 9 3900X 12-Core Processor (1 Socket)
Kernel Version

Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)
PVE Manager Version

pve-manager/7.2-3/c743d6c1


Here is one of my vm.conf files after all of this (some fields REDACTED to protect the innocent):

Code:
agent: 1
args: -cpu host,-hypervisor,hv_vendor_id=amd
bios: ovmf
boot: order=sata0;net0
cores: 20
cpu: host
efidisk0: SSDtmp:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:09:00,pcie=1,x-vga=1
machine: pc-q35-6.2
memory: 50048
meta: creation-qemu=6.2.0,ctime=1663513997
name: Windows10
net0: virtio=REDACTED,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata0: SSDtmp:vm-100-disk-1,cache=writeback,discard=on,size=200G
scsihw: lsi
smbios1: REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
usb0: host=1-4,usb3=1
usb1: host=7-1,usb3=1
usb2: host=7-4,usb3=1
usb3: host=7-2,usb3=1
virtio2: /dev/disk/by-id/nvme-eui.6479a72452222020,size=976762584K
vmgenid: REDACTED
 
Last edited:
Hello, I'm also having problems with the NewWorld game. I can't start the game, it detects directly that it's a VM.
error message: cannot run under Virtual Machine.
I've tried your configurations but the problem is still there.
I may have made some errors in my .conf file (present on /etc/pve/nodes/pve/qemu-server)?

Can you help me please ?

Here is my Proxmox server:
CPU(s)

24 x AMD Ryzen 9 3900X 12-Core Processor (1 Socket)
Kernel Version

Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)
PVE Manager Version

pve-manager/7.2-3/c743d6c1


Here is one of my vm.conf files after all of this (some fields REDACTED to protect the innocent):

Code:
agent: 1
args: -cpu host,-hypervisor,hv_vendor_id=amd
bios: ovmf
boot: order=sata0;net0
cores: 20
cpu: host
efidisk0: SSDtmp:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:09:00,pcie=1,x-vga=1
machine: pc-q35-6.2
memory: 50048
meta: creation-qemu=6.2.0,ctime=1663513997
name: Windows10
net0: virtio=REDACTED,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata0: SSDtmp:vm-100-disk-1,cache=writeback,discard=on,size=200G
scsihw: lsi
smbios1: REDACTED,manufacturer=QkVTU1RBUiBURUNIIExJTUlURUQ=,product=SE04MA==,version=NS4xNg==,serial=RGVmYXVsdCBzdHJpbmc=,sku=RGVmYXVsdCBzdHJpbmc=,family=RGVmYXVsdCBzdHJpbmc=,base64=1
sockets: 1
usb0: host=1-4,usb3=1
usb1: host=7-1,usb3=1
usb2: host=7-4,usb3=1
usb3: host=7-2,usb3=1
virtio2: /dev/disk/by-id/nvme-eui.6479a72452222020,size=976762584K
vmgenid: REDACTED
"args: -cpu host,-hypervisor,hv_vendor_id=amd"- this configuration work not always. after reboot I've blue-screen error. i do hard stop and remove string -hypervisor, startup windows, shutdown, and again add -hypervisor and startup. and no more shutdown and reboot, because again and again bsod.
sorry for my english ¯\_(ツ)_/¯
 
Hey everyone, I just updated my computer to windows 23H2 and I can confirm that this update breaks the windows loading. If I revert before to 22H2 it works fine. Any ideas?
 
Well, I did everything you did, and it finally changed from QEMU Device to ASUS System Device. However, loading Halo Infinite still causes it to cancel out and close the game. I cannot activate "args: -cpu host,-hypervisor,kvm=off" as my computer gets stuck in the windows boot logo. Any other ideas I can try?

View attachment 59645
Could be your windows version. When I tryed with win 11 I had the same mistake than yours, I changed for win10 and worked
 
If you are dealing with EAC, all you have to do is set up the SMBIOS of your VM, dump your OG bios data and paste them in the SMBIOS. if it doesnt work, use the Intel card with a real listed Mac address
 
Could be your windows version. When I tryed with win 11 I had the same mistake than yours, I changed for win10 and worked
It indeed was a windows update that had busted this method. I had reverted before the update and it worked. Unfortunately I run windows 11 and have not found a new solution to the problem.
 
playing fortnite since one month, noticed some issues because was running with sata and Lsi controller, changed now to scsi and virtio and everything is smooth, also no issue with anticheat
 
playing fortnite since one month, noticed some issues because was running with sata and Lsi controller, changed now to scsi and virtio and everything is smooth, also no issue with anticheat
Hi. I would like to try this as well. Could you please share the conf file.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!