Ziomario

Hello to everyone. I'm trying to fix the error 43 given by the nvidia driver when I install it on a Windows 10 virtualized OS. I'm interested to use the nvidia driver of my graphic card (RTX 2080ti) on a esxi client and on a xen client. I've got this patch,that can help me : https://github.com/sk1080/nvidia-kvm-patcher This is what the patch does : $pattern = '\xBB\x00\x00\x00\x40\x48\x8D\x44\x24\x50' # + 0x30 $patch = [Byte[]]@(0x31, 0xC0, 0x90, 0x90, 0x90, 0x90, 0x90, 0x85, 0xC0) it detect the hex value of BB00000040488D442450 and replace it with "31C0909090909085C0". This is the value called "Cpu ID" that's located inside the file "nvlddmkm.sys" of each nvidia driver and it is used to detect if the driver is running inside a KVM vm. Good. This is not what I want to do. I don't need to patch the nvidia driver to hide the KVM hypervisor. I want to hide the ESXI and the XEN hypervisor from the nvidia driver. I gave a look inside the nvlddmkm.sys file and I found something that's really interesting (attached pic called before) is this the hex value associated with the vmware hypervisor ? It's enough to change it with this,for example,to fool the nvidia driver ? (attached picture called after) In addition to this,looking inside the nvidia kvm patcher,I see that it used an offset,like this : $offset = $matches[0].Index + 0x40 I would like to know in my case what's the offset ? Maybe 0x40 ? C40 is 0x40 ? thanks.