Windows 4.3.16 specifically for errors due to security
Re: Windows 4.3.16 specifically for errors due to security
bird:
VirtualBox-4.3.17-96101-Win.exe works correctly!
I am currently using the 4.3.16 Extensions. Looking forward to the official 4.3.17 release.
Env:
HDW: Acer Aspire 7540 AMD Athlon II Dual-Core M300 2.00GHz 4.00 GB (3.75 usable) 64-bit
OS: Windows 7 Home Premium SP 1 Build 7601
AntiVirus: Microsoft Security Essentials
AntiMalware: Malwarebytes Anti-Malware 2.0.2.1012 Build 5/12/2014
This was - and apparently continues to be - a real bear. I appreciate your work.
Many thanks! Muchas gracias! Vielen Danke!
VirtualBox-4.3.17-96101-Win.exe works correctly!
I am currently using the 4.3.16 Extensions. Looking forward to the official 4.3.17 release.
Env:
HDW: Acer Aspire 7540 AMD Athlon II Dual-Core M300 2.00GHz 4.00 GB (3.75 usable) 64-bit
OS: Windows 7 Home Premium SP 1 Build 7601
AntiVirus: Microsoft Security Essentials
AntiMalware: Malwarebytes Anti-Malware 2.0.2.1012 Build 5/12/2014
This was - and apparently continues to be - a real bear. I appreciate your work.
Many thanks! Muchas gracias! Vielen Danke!
Re: Windows 4.3.16 specifically for errors due to security
I would like to figure out why my system is different. I'm not familiar with the LPC. I found a related article here but the english translation (from russian I presume) isn't always too kind. I've uninstalled some third party drivers but no change. If you have any ideas or suggestions about how to investigate this please let me know. Thanksbird wrote:Now, to get to the ApiPort object I need the NT object type pointer. This is normally pointed to by the LpcPortObjectType export of ntoskrnl.exe. Except on your system it isn't. I've no idea why, that is so, I've got four theories: 1. The NT kernel may be configured to provide something compatible with the pre-Vista LPC implementation. 2. Some AV/protection software or the NT kernel has changed it on purpose so that getting to ALPC objects are more difficult. 3. Some driver is messing with it by accident. 4. Some rootkit-like thing is present and has hooked it.
Re: Windows 4.3.16 specifically for errors due to security
No improvement for me, I now get the attached error. Windows XP, using the test build. Running Symantec Endpoint Protection 12.1.3001.165 and Virtualbox 4.3.17 r96101. My log is attached. Not sure if this line has anything to do with it. I don't recognize the path 'c:\tinderbox..." Log is attached.
00:00:03.117507 VMSetError: C:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDMLdr.cpp(307) int __cdecl pdmR3LoadR3U(struct UVM *,const char *,const char *); rc=VERR_MODULE_NOT_FOUND
00:00:03.129522 VMSetError: Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=126
Thanks for continuing to work on this.
00:00:03.117507 VMSetError: C:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDMLdr.cpp(307) int __cdecl pdmR3LoadR3U(struct UVM *,const char *,const char *); rc=VERR_MODULE_NOT_FOUND
00:00:03.129522 VMSetError: Unable to load R3 module C:\Program Files\Oracle\VirtualBox/VBoxDD.DLL (VBoxDD): GetLastError=126
Thanks for continuing to work on this.
- Attachments
-
- Windows 7-2014-09-20-12-48-15.log
- (27.23 KiB) Downloaded 35 times
-
- untitled1.jpg (63.48 KiB) Viewed 13975 times
-
- Posts: 4
- Joined: 17. Feb 2011, 16:35
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Ubuntu
Re: Windows 4.3.16 specifically for errors due to security
This version does, in fact, work for me.bird wrote:Reposting test build #3 as the initial build (96096) was broken by some build server changes:
The previous build (#2) broke things for all avast users. Frightfully sorry about that. Here is a new build that fixes that blunder.
Test build #3: https://www.virtualbox.org/download/tes ... 01-Win.exe
@RobBrownNZ, @spider38: Please try the new build, it should fix the problem you were seeing with build #2.
@derscherjm, @Limeroli, @rnewman, @Gurvender.Bahia, @mattsnowboard: Would be great if you could take the new build for a spin.
Cheers,
bird
The only problem is it still regresses Vagrant support, as mentioned in this thread:
viewtopic.php?f=6&t=63703
Rolling back to .12 again
Re: Windows 4.3.16 specifically for errors due to security
I too get an error which seems linked to this:
On a Windows Server 2012 Essentials (not R2, 8gB ram, Dell PE T320, No Antivirus, logged on as an administrator) and a fresh install of VB (4.3.16) if I create any VM and press start I get (before anything):
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Tried 4.3.17 r96101 get same.
Att. is Vboxstartup.log. There are clearly some errors there, but I don't know how to address them.
Thanks.
On a Windows Server 2012 Essentials (not R2, 8gB ram, Dell PE T320, No Antivirus, logged on as an administrator) and a fresh install of VB (4.3.16) if I create any VM and press start I get (before anything):
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Tried 4.3.17 r96101 get same.
Att. is Vboxstartup.log. There are clearly some errors there, but I don't know how to address them.
Thanks.
- Attachments
-
- VBoxStartup.log
- (98.3 KiB) Downloaded 67 times
Re: Windows 4.3.16 specifically for errors due to security
Failed to Verify process integrity: (rc=-5662)
Please try reinstalling VirtualBox
Using the latest 4.3.17 build
Failed to open a session for the virtual machine Mint.
The virtual machine 'Mint' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\whyis_000\VirtualBox VMs\Mint\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Windows 8.1 Professional
Intel i5 with 8GB RAM
Symantec Endpoint Protection 12.1.4013.4013
VBoxStartup.log attached
Please try reinstalling VirtualBox
Using the latest 4.3.17 build
Failed to open a session for the virtual machine Mint.
The virtual machine 'Mint' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\whyis_000\VirtualBox VMs\Mint\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Windows 8.1 Professional
Intel i5 with 8GB RAM
Symantec Endpoint Protection 12.1.4013.4013
VBoxStartup.log attached
- Attachments
-
- VBoxStartup.zip
- zipped due to 128KB limit, File is 171KB uncompressed.
- (9.95 KiB) Downloaded 62 times
Re: Windows 4.3.16 specifically for errors due to security
After having many issues with 4.3.14 and 4.3.16, 4.3.17 r96101 is working for me!
Host: Home built Intel Core i7 2600K, 16GB RAM
OS: Microsoft Windows 7 Home Premium SP-1, 64-bit, all the latest updates
Antivirus: Avast! Free Antivirus 2014-9.0.2021 140923-0
Thanks to the hard working VirtualBox team for their dedication in getting this anomaly figured out...
Host: Home built Intel Core i7 2600K, 16GB RAM
OS: Microsoft Windows 7 Home Premium SP-1, 64-bit, all the latest updates
Antivirus: Avast! Free Antivirus 2014-9.0.2021 140923-0
Thanks to the hard working VirtualBox team for their dedication in getting this anomaly figured out...
- Attachments
-
- vbox logs.zip
- contains vbox.log and vboxstartup.log
- (44.84 KiB) Downloaded 29 times
Re: Windows 4.3.16 specifically for errors due to security
Same problem...
Host: Win7
Antivirus: Eset Endpoint Antivirus
Virtualbox: 4.3.17 from another post
Can't upload image, so link is: htt p:// martasdx.cz/vb.p ng
Tried newest Gentoo and Ubuntu linux.
Host: Win7
Antivirus: Eset Endpoint Antivirus
Virtualbox: 4.3.17 from another post
Can't upload image, so link is: htt p:// martasdx.cz/vb.p ng
Tried newest Gentoo and Ubuntu linux.
- Attachments
-
- VBoxStartup.zip
- (9.24 KiB) Downloaded 29 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 4.3.16 specifically for errors due to security
Vagrant has never been supported, so it's impossible to regress support for it.mattsnowboard wrote:The only problem is it still regresses Vagrant support
Re: Windows 4.3.16 specifically for errors due to security
Trend Micro Office Scan Client for Windows v10.6.2195 sp1
Windows 7 Pro x64 sp1 (fr)
Good afternoon,
> You will find vboxstartup.log in the zip file in attachment.
Below the historic of my issues with Trend Micro and VBox.
- vbox 4.3.12: launch vbox user interface and virtual machines ok
- update to vbox 4.3.14: unable to load vbox user interface
- update to vbox 4.3.16r95972: launch vbox user interface ok - launch any virtual machines: ko >exit code -1073741819 (0xc0000005)
- update to vbox 4.3.17r96047: launch vbox user interface ok - launch any virtual machines: ko >exit code -1073741819 (0xc0000005)
- update to vbox 4.3.17r96101: launch vbox user interface ok - launch any virtual machines: ko>exit code -1073741819 (0xc0000005)
- uninstall vbox 4.3.17r96101
- reinstall vbox 4.3.17r96101: launch vbox user interface ok - launch any virtual machines: ko>exit code -1073741819 (0xc0000005)
Windows 7 Pro x64 sp1 (fr)
Good afternoon,
> You will find vboxstartup.log in the zip file in attachment.
Below the historic of my issues with Trend Micro and VBox.
- vbox 4.3.12: launch vbox user interface and virtual machines ok
- update to vbox 4.3.14: unable to load vbox user interface
- update to vbox 4.3.16r95972: launch vbox user interface ok - launch any virtual machines: ko >exit code -1073741819 (0xc0000005)
- update to vbox 4.3.17r96047: launch vbox user interface ok - launch any virtual machines: ko >exit code -1073741819 (0xc0000005)
- update to vbox 4.3.17r96101: launch vbox user interface ok - launch any virtual machines: ko>exit code -1073741819 (0xc0000005)
- uninstall vbox 4.3.17r96101
- reinstall vbox 4.3.17r96101: launch vbox user interface ok - launch any virtual machines: ko>exit code -1073741819 (0xc0000005)
- Attachments
-
- vboxstartup-logs.zip
- In this zip file, you will find 2 vboxstartup.log for 2 differents machines.
Please note: all my vms post the same final error. - (4.26 KiB) Downloaded 38 times
-
- Posts: 8
- Joined: 26. Sep 2014, 06:53
Re: Windows 4.3.16 specifically for errors due to security
Windows 7 x64 SP1 with all latest updates
Symantec Endpoint Protection Version: 12.1.1101.401 (Release), RU1 MP1
I did try the 4.3.17 test build but both 4.3.17 and 4.3.16 are throwing the same error:
Attaching logs to help you guys debug the issue.
For now I'm rolling back to 4.3.12 as I need to get my virtual machines running. Let me know if further info is required.
Symantec Endpoint Protection Version: 12.1.1101.401 (Release), RU1 MP1
I did try the 4.3.17 test build but both 4.3.17 and 4.3.16 are throwing the same error:
Code: Select all
484.598: Error -5633 in supR3HardenedWinVerifyProcess! (enmWhat=1)
484.598: Failed to verify process integrity: Unknown image file \Device\HarddiskVolume1\Windows\System32\advapi32.dll at 000007fefea30000.
For now I'm rolling back to 4.3.12 as I need to get my virtual machines running. Let me know if further info is required.
- Attachments
-
- VBoxStartup.zip
- Arch Linux (64-bit) VM Startup Log for VirtualBox 4.3.17
- (11.09 KiB) Downloaded 28 times
Re: Windows 4.3.16 specifically for errors due to security
Failed to open a session for the virtual machine centos.
The virtual machine 'centos' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\sl4syh3r\VirtualBox VMs\centos\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
can anyone help me how to fix this problem,i use motherboard gigabyte H61M-WW and graphic card Nvidia Gt630,
The virtual machine 'centos' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\sl4syh3r\VirtualBox VMs\centos\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
can anyone help me how to fix this problem,i use motherboard gigabyte H61M-WW and graphic card Nvidia Gt630,
- Attachments
-
- Nvidia GT630 Grafik card X)
- virtualboxerror.jpg (43.06 KiB) Viewed 12998 times
Re: Windows 4.3.16 specifically for errors due to security
sl4syh3r wrote:Failed to open a session for the virtual machine centos.
The virtual machine 'centos' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\sl4syh3r\VirtualBox VMs\centos\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
can anyone help me how to fix this problem,i use motherboard gigabyte H61M-WW and graphic card Nvidia Gt630,
- Attachments
-
- VBoxStartup.rar
- (10.51 KiB) Downloaded 57 times
Re: Windows 4.3.16 specifically for errors due to security
.. as above..
Windows Server 2012 Essentials (not R2, 8gB ram, Dell PE T320, No Antivirus, logged on as an administrator)
Uninstalled any vbox then install of VB (4.3.17 96235) same error as previous post.
Exit code 1
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Haven't even managed to build a VM yet. startup log att.
Windows Server 2012 Essentials (not R2, 8gB ram, Dell PE T320, No Antivirus, logged on as an administrator)
Uninstalled any vbox then install of VB (4.3.17 96235) same error as previous post.
Exit code 1
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Haven't even managed to build a VM yet. startup log att.
- Attachments
-
- VBoxStartup.log
- (98.96 KiB) Downloaded 33 times
Last edited by Memiself on 27. Sep 2014, 18:02, edited 1 time in total.
-
- Posts: 129
- Joined: 23. May 2014, 12:35
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: XP Pro, Win7, Win10
Re: Windows 4.3.16 specifically for errors due to security
I'm getting an error when running this bat file:
The error I'm getting is:
What can I do to resolve this error?
Running this on a host Win7 Pro 64bit
Anti-virus Bitdefender 2015
Guest XP Pro 32 bit
Anti-virus None
With the Anti-virus turned off I got the attached BSOD:
Thank you,
Docfxit
Code: Select all
CD C:\Programs\VirtualBox
VBoxHeadless -s XPVirtualMachine -v on
cmd
Code: Select all
C:\Programs\VirtualBox>VBoxHeadless -s XPVirtualMachine -v on
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -5667 (0xff
ffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Program Files\
NVIDIA Corporation\coprocmanager\detoured.dll: supHardenedWinVerifyImageByHandle
: TrustedInstaller is not the owner of '\Device\HarddiskVolume2\Program Files\NV
IDIA Corporation\coprocmanager\detoured.dll'.
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\NVIDI
A Corporation\CoProcManager\detoured.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 4.3.17
(C) 2008-2014 Oracle Corporation
All rights reserved.
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -5667 (0xff
ffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Programs\Ultra
VNC\schook64.dll: supHardenedWinVerifyImageByHandle: TrustedInstaller is not the
owner of '\Device\HarddiskVolume2\Programs\UltraVNC\schook64.dll'.
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=1 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=2 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=3 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=4 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=5 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=6 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=7 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=8 \Device\HarddiskVo
lume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=16 \Device\HarddiskV
olume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=32 \Device\HarddiskV
olume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/Imports: rc=Unknown Status -22919 (0xffff
a679) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32
\igdusc64.dll: WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\Harddi
skVolume2\Windows\System32\igdusc64.dll'
VBoxHeadless: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status
-22919 (0xffffa679) fImage=1 fProtect=0x10 fAccess=0xf cErrorHits=1 \Device\Har
ddiskVolume2\Windows\System32\igdusc64.dll
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=64 \Device\HarddiskV
olume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -566
7 (0xffffe9dd) fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=128 \Device\Harddisk
Volume2\Programs\UltraVNC\schook64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Programs\UltraVNC\s
chook64.dll': rcNt=0xc0000190
Running this on a host Win7 Pro 64bit
Anti-virus Bitdefender 2015
Guest XP Pro 32 bit
Anti-virus None
With the Anti-virus turned off I got the attached BSOD:
Thank you,
Docfxit
- Attachments
-
- VBoxBSODReport2014-09-27.zip
- (9.42 KiB) Downloaded 37 times
-
- VBox.log
- (62.55 KiB) Downloaded 30 times