Page 15 of 25

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Sun Nov 20, 2016 5:14 pm
by EP_X0FF
Your screenshot indicate that patch table wasn't loaded by driver -> REFRESH_LIST failed.
I suggest you check if HKLM\System\CurrentControlSet\Services\Tsugumi@Parameters=VBoxDD.dll REG_BINARY exist, then reboot Windows and try again. Make sure that tsugumi.sys is the latest from github.

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Sun Nov 20, 2016 8:38 pm
by SSBIZ
Hi, true that. Sorry!

I downloaded the latest tsugumi.sys.

And then I ran everything from the beginning. And here what I got now. Attached the screenshots.

Again thanks a lot!

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Sun Nov 20, 2016 9:12 pm
by newcomer
Good afternoon,

My host system is windows 7.
Virtualbox version 5.1.8 r111374 (Qt5.5.1).
Patch the system successfully (thank to video in previous post).
Only one problem virtual machine start with my original processor id and serial number. As i understand configuration file already contain info for changing this details, additionally run command
Code: Select all
vboxmanage setextradata mx VBoxInternal/CPUM/
HostCPUID/80000003/ebx 0x50202952
for change this parameter, but still no effect. Is any one have same problem?
All other details is changed. I tried different iso - Windows7 and Debian, nothing.

Also in thread mentioned about configuration Virtualbox on Debain as host system. Is anywhere details instruction or even better step by step about installing and configuration process.

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Mon Nov 21, 2016 6:51 am
by EP_X0FF
SSBIZ wrote:Hi, true that. Sorry!

I downloaded the latest tsugumi.sys.

And then I ran everything from the beginning. And here what I got now. Attached the screenshots.

Again thanks a lot!
Recreate your VM. You are doing something wrong (or there is a conflict with something else you have installed), that all I can tell you. Note that running tsugumi installer only required one time and loader.exe can be started multiple times. In case if it still not working on your system - disable ACPI tables in config file and apply it again -> comment/remove these lines:
%vboxman% setextradata "%1" "VBoxInternal/Devices/acpi/0/Config/DsdtFilePath" "%vmscfgdir%ACPI-DSDT.bin"
%vboxman% setextradata "%1" "VBoxInternal/Devices/acpi/0/Config/SsdtFilePath" "%vmscfgdir%ACPI-SSDT1.bin"
however this will make your VM much more detect friendly.

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Mon Nov 21, 2016 6:57 am
by EP_X0FF
newcomer wrote:Only one problem virtual machine start with my original processor id and serial number. As i understand configuration file already contain info for changing this details, additionally run command
Code: Select all
vboxmanage setextradata mx VBoxInternal/CPUM/
HostCPUID/80000003/ebx 0x50202952
for change this parameter, but still no effect. Is any one have same problem?
All other details is changed. I tried different iso - Windows7 and Debian, nothing.
Hello,

can you post your VBox log?

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Mon Nov 21, 2016 11:43 am
by newcomer
They are pretty huge.
Attach an archive
Code: Select all
Password - send0943

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Tue Nov 22, 2016 5:29 pm
by newcomer
Reattach log files of VBox.

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Tue Nov 22, 2016 8:21 pm
by SSBIZ
Hi,

sorry for coming so late to you but I tried all ways.

I tried installing from the beginning Windows 7, then Windows 8 and then Windows 10. In order to refresh the machine in case it had some problems regarding any software conflict.

And then I did exactly what you said by even deleting those 2 strings at hdmi_ahci.cmd.

Am desperate as because a friend tried the same system in one of his machine and it works. To me it does not.

And on the command line everything shows exactly as to my friend machine. The only different step is the launch of the vmware itself. it gives that error I showed you above.

I am attaching as a desperate attempt the log of my system in details. Maybe you see something I dont see which can prevent my machine to work.

So thanks a lot in advance!

Re: VBoxAntiVMDetectHardened mitigation X64 only (20/10/16)

PostPosted:Wed Nov 23, 2016 4:12 am
by EP_X0FF
SSBIZ wrote:Hi,

sorry for coming so late to you but I tried all ways.

I tried installing from the beginning Windows 7, then Windows 8 and then Windows 10. In order to refresh the machine in case it had some problems regarding any software conflict.

And then I did exactly what you said by even deleting those 2 strings at hdmi_ahci.cmd.
If you deleted these two strings and applied these settings again (by re-running script) vm will start in any case. If no then you did something wrong.

Re: VBoxAntiVMDetectHardened mitigation X64 only (23/11/16)

PostPosted:Wed Nov 23, 2016 5:44 am
by EP_X0FF
Loader updated to support 5.1.10

Also confirmed, Oracle fixed NAT (NAT: fixed several 5.1.8 regressions on Mac OS X and Windows hosts) https://www.virtualbox.org/wiki/Changelog#v10