virtualbox.org

Hi,

Using test build #4: 4.3.17 r96342, I can't start any VM. I'm on Windows 7 64-bit with avast (but disabled from the tray icon).

Logs attached.

1. Windows 8.1 Pro, x64, v 6.3.9600, build 9600, virtualbox 4.3.17 r96342
2. log attached.
3. SEP 12.1.4013.4013

thanks for the hard work!

Hi,

I am using build 4.3.17.9642.
antivirus ESET NOD antivirus: temporarily disabled.

When I try to start an existing vm, or create a new vm, I get rc:5633 Failed to verify process integrity, Please try reinstalling VirtualBox, and an Abort button.


VBoxStartup.log is here:

http://tempsend.com/3569496DE1

1) Windows 8.1 x64 Professional , VBox Version: 4.3.17 r96342
2) 3) McAfee VirusScan Enterprise 8.8 Patch 4 (though it does the same thing even with this turned off.

Version 4.3.12 was working fine. I updated to 4.3.16 and this issue begin:

Hi,

i used the new Version "4.3.17 r96342", but i still have the problem that my old VM-Image (Debian 32) doesn't start on my Windows 7 Host.
Error -3738 "VERR_SUPDRV_HARDENING_EVIL_HANDLE"

1) Host and version
Windows 7 64bit

2) VBoxStartup.log
attached

3) Host virus software or debugging programs:
AVG Antivirus FRee 2014

Update:
I've also tried this solution, doesn't work:
1. \Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf - right mouse > install
2. \Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.inf - right mouse > install

Also disabeling AVG Antivirus via Try doesn't work

Hi All!

Test build #5 is finally here, been working around the clock for since last week on this. It include some radical changes to the code that has been running head first into several antivirus/antimalware/firewalls/quickcam/protection software. The changes should better contain the conflict situation, ruling out a lot of annoying factors. (For the curious, I've moved the securing of the VM process and opening of vboxdrv till before NTDLL.DLL is initialized. Not pretty, but hopefully efficient.)

Test build #5: https://www.virtualbox.org/download/tes ... 26-Win.exe

Changes since test build #4:
- Fixes problem on windows 8.1, especially for symantec endpoint protection users (but also avast and others).
- General improvements (hopefully).

Would be great if as many as possible could give this build a spin, even if things works for you already. (Consider it a 4.3.18 release candidate.)

Enjoy,
bird.

RyanSpooner wrote:1) Windows 8.1 x64 Professional , VBox Version: 4.3.17 r96342
2)

VBoxStartup.zip

3) McAfee VirusScan Enterprise 8.8 Patch 4 (though it does the same thing even with this turned off.

Version 4.3.12 was working fine. I updated to 4.3.16 and this issue begin:

error.png

error2.png

Try uninstalling Hyper-V and you will be able to run 4.3.14 & 4.3.16 (worked @ least for me).
This will also allow you to configure more than 1 CPU.

Bird,

Do you know if Test Build #5 fixes the problem that we reported using Host Windows 10 Technical Preview? My initial testing shows that it does, but I just was curious if you put in a specific fix for that, or if it's working just by chance

Thank you very much for the update.
I have installed Test build #5: 4.3.17 r96426

I'm having trouble running the Vboxheadless. The command window opens. The Vbox window doesn't open

This is the bat file I am running:
Thank you for working on the fixes,

Docfxit

Update:

- Is the problem specific to VBoxHeadless. I mean, can you run VMs in the GUI?

I can run the VM in the GUI.

- Iff this is related to the AV issues, I need VBoxStartup.log to see what's going on with DLLs and verification. Could you get me both VBoxStartup.log and VBox.log for a hung VBoxHeadless session, please?
The VBox.log was attached to this original post.

- Even better, a process dump (minidump is fine if you know process explorer) of the hung VBoxHeadless would rock.
If anything else would help please let me know.

Thank you for working on it.

Docfxit

bird wrote:Hi All!

Test build #5 is finally here, been working around the clock for since last week on this. It include some radical changes to the code that has been running head first into several antivirus/antimalware/firewalls/quickcam/protection software. The changes should better contain the conflict situation, ruling out a lot of annoying factors. (For the curious, I've moved the securing of the VM process and opening of vboxdrv till before NTDLL.DLL is initialized. Not pretty, but hopefully efficient.)

Test build #5: https://www.virtualbox.org/download/tes ... 26-Win.exe

Changes since test build #4:
- Fixes problem on windows 8.1, especially for symantec endpoint protection users (but also avast and others).
- General improvements (hopefully).

Would be great if as many as possible could give this build a spin, even if things works for you already. (Consider it a 4.3.18 release candidate.)

Enjoy,
bird.

Hey Bird,

The recent test candidate resolved my issue.

For reference, the following is now working

Windows 7, 64 bit Version 6.1.7601 Service Pack 1

Virtual Box 4.3.17 r96342 ( The latest test build to my knowledge as of writing )

Eset Endpoint Antivirus Version 5.0.2228.1

ESET SPECIFIC VERSIONS:
Virus signature database: 10494 (20141001)
Rapid Response module: 4819 (20141001)
Update module: 1052 (20140801)
Antivirus and antispyware scanner module: 1438 (20140917)
Advanced heuristics module: 1153 (20140915)
Archive support module: 1209 (20140812)
Cleaner module: 1100 (20140827)
Anti-Stealth support module: 1060 (20140514)
ESET SysInspector module: 1243 (20140903)
Self-defense support module: 1018 (20100812)
Real-time file system protection module: 1006 (20110921)
Translation support module: 1232 (20140624)
HIPS support module: 1146 (20140909)
Internet protection module: 1140 (20140806)
Database module: 1060 (20140714)

Thanks very much.

Hi,

"Test build #5" also doesn't work for me
I've attached the StartupLog again.

Mucky wrote:Hi,

i used the new Version "4.3.17 r96342", but i still have the problem that my old VM-Image (Debian 32) doesn't start on my Windows 7 Host.
Error -3738 "VERR_SUPDRV_HARDENING_EVIL_HANDLE"

1) Host and version
Windows 7 64bit

2) VBoxStartup.log
attached

3) Host virus software or debugging programs:
AVG Antivirus FRee 2014

Update:
I've also tried this solution, doesn't work:
1. \Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf - right mouse > install
2. \Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.inf - right mouse > install

Also disabeling AVG Antivirus via Try doesn't work

@Jacob Klein: Sorry, I haven't had time to test the win10 preview with yet.

@docfxit: Some questions:
- Is the problem specific to VBoxHeadless. I mean, can you run VMs in the GUI?
- Iff this is related to the AV issues, I need VBoxStartup.log to see what's going on with DLLs and verification. Could you get me both VBoxStartup.log and VBox.log for a hung VBoxHeadless session, please?
- Even better, a process dump (minidump is fine if you know process explorer) of the hung VBoxHeadless would rock.

@cadoretti: Very happy to hear that it's finally working for you. (I'd love to see more posts like this! )

@Mucky: I have reproduced that one a few times here, but when I even think about debugging it, it disappears. Real heisenbug. I'll try again in the morning.

-bird

bird wrote:
@docfxit: Some questions:
- Is the problem specific to VBoxHeadless. I mean, can you run VMs in the GUI?
- Iff this is related to the AV issues, I need VBoxStartup.log to see what's going on with DLLs and verification. Could you get me both VBoxStartup.log and VBox.log for a hung VBoxHeadless session, please?
- Even better, a process dump (minidump is fine if you know process explorer) of the hung VBoxHeadless would rock.

I have added the information to my last post so you can keep things together.

Thank you,

Docfxit

@bird

I just got this new laptop and tried to make a new VM with vbox 4.3.16, and encountered the problems I detailed before.

So far so good with the latest build. Started my new VM with no errors. My current, working setup:

1. Windows 8.1 Pro, x64, v 6.3.9600, build 9600, virtualbox 4.3.17 r96426
2. SEP 12.1.4013.4013

thanks!

Jacob let me know about this latest beta and I've tested test build #5 as working in a Windows 10 host now:
viewtopic.php?f=6&t=63923

Thanks bird