﻿ticket,summary,guest,version,created,modified,_changetime,_description,_reporter
20955,Debian Jessie not booting on VBox 6.0.24,Linux,,2022-05-23T11:15:00Z,2022-05-23T16:45:03Z,2022-05-23T16:45:03Z,"Hello,

Recently downloaded VirtualBox under Windows, and I'm struggling to run Debian 8.11.1 ('''Jessie''') as my ''guest'' OS.

At the moment, I've tried to boot it from a ''DVD'' iso (after successful installation), but as soon as it's meant to login the screen prompts a message like ""Something went wrong, and the system can't recover""...

I've read this might be due to VBox graphical settings, and that a VBoxSVGA controller was suggested in place of VMSVGA.

Almost nothing changed by enabling or disabling 3D acceleration...

Please, can you help?

Mine was the first installer from here: [https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-dvd/]

Thanks",Antonin
20767,Limit of 2047 bytes when transferring in the clipboard from host to guest.,Windows,,2022-01-11T11:33:13Z,2022-01-12T11:32:29Z,2022-01-12T11:32:29Z,"In version 6.1.97-148976 there is a bug with a 2kb limitation when transferring to the clipboard, from host (Windows) to guest (Windows). Any size larger than 2047 bytes simply disappears during transfer. In the opposite direction, there is no such behavior.

This does not depend on the installed add-ons in the guest, any installed version of the add-ons in the guest behaves the same with the buffer.

It looks like it only depends on the version installed on the host. Development snapshots 6.1.97-148976 always works with this bug, in release 6.1.30 there is no such behavior. ",megaslowpoke
17553,Une erreur critique est survenue pendant l'execution de la machine virtuelle,Windows,,2018-02-19T17:28:55Z,2020-10-11T12:57:45Z,2020-10-11T12:57:45Z,"Hi!
after an update of the version ubuntu 17.04 and restart my virtual machine is not accessible anymore and a window appear containing this words "" Une erreur critique est survenue pendant l'execution de la machine virtuelle et cette derniere a été suspendue"" .
thanks",mohamed degaci
19833,virtualbox showing : The VM session was aborted.   Result Code:  E_FAIL (0x80004005) Component:  SessionMachine Interface:  ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7},all,,2020-08-26T06:27:01Z,2020-08-26T06:27:01Z,2020-08-26T06:27:01Z,The VM session was aborted,TGT
19753,Guest Additions 6.1.12 don't support screen autosizing anymore on Windows 7 guests,Windows,,2020-07-22T19:30:08Z,2020-07-30T19:13:09Z,2020-07-30T19:13:09Z,"After upgrading VirtualBox to version 6.1.12, I upgraded '''Guest Additions''' (GA) on my virtual machines (VMs), all Windows 10 guests except one, which is Windows 7. I use screen autosizing to get full-screen display on all my VMs.

The upgrade worked properly for all Windows 10 VMs. However, after upgrading GA to version 6.1.12 on the Windows 7 guest, I ran into repeated blue screens. After changing the graphics driver to VBoxSVGA, I could properly start the VM again, but I couldn't get the screen to autosize anymore.

Actually, the behaviour I observed looks like GA are not working at all anymore on Windows 7 guests.

The only way I could get back this feature (and GA to work properly) was to rollback GA to version 6.1.10.

Bottom line: This looks like a '''compatibility issue between Guest Additions 6.1.12 and Windows 7 hosts'''.",jfmorin
19748,VirtualBox 6.1.12 allows to create a fixed disk bigger than free space,Windows,,2020-07-22T12:35:44Z,2020-07-22T12:35:44Z,2020-07-22T12:35:44Z,"Good afternoon,

Creating a virtual machine allows you to also add a new disk. In my opinion, if you choose fixed size, the program shouldn't allow to create disks bigger than the free space.

You can see it in [https://streamable.com/fr8dyj this video].

Regards.",Antonio López Fernández
19719,Virtualbox 6.1.12 r139181 Win7 Guest Crash VboxVGA,Windows,,2020-07-14T20:14:12Z,2020-07-17T04:36:02Z,2020-07-17T04:36:02Z,"Just installed the VBox 6.1.12 update and updated the Guest Additions. Windows 7 x64 (newest updates) does not start anymore, it crashes with a blue screen.
Graphics Adapter is VBoxVGA. It works with other graphics adapters configured in settings.",JayEm1
19569,The virtual machine 'XXX has terminated unexpectedly during startup with exit code 1,all,,2020-05-07T07:52:54Z,2020-05-07T07:52:54Z,2020-05-07T07:52:54Z,"I upgraded to VirtualBox 6.1.7r137622 to escape the bug https://www.virtualbox.org/ticket/19496.
Now, all my VM doesn't start : I have the message bellow.
[[Image(https://i.postimg.cc/nVwkVjK4/supR3.png)]]
",Vbox43532
19174,Guest List disappears abruptly if dragged too far left,all,,2019-12-19T16:03:35Z,2019-12-19T16:03:35Z,2019-12-19T16:03:35Z,"There is a join between the guest list and the settings where the mouse cursor changes to indicate that the join can be dragged. Dragging this to the left causes the guest list to shrink in width. Eventually the guest list stops shrinking as the mouse continues dragging left. Continue dragging left more than half the width of the now-non-shrinking guest list, and the whole guest list disappears, with no visible indication of any possible way to restore it, or any column to show there's something that can be dragged to the right. 

In Virtualbox.xml, this is shown:

{{{<ExtraDataItem name=""GUI/SplitterSizes"" value=""0,###""/>}}}
('###' being the actual width of the GUI window)

It is still possible to show the list by dragging right from the far left, or issuing this commmand:

{{{VBoxManage setextradata global GUI/SplitterSizes}}}

I don't know if the hard disappearing snap or having no visible sign something is draggable there is by design, but a slightly showing guest list (~20 pixels?) might mitigate the forum users wondering where their guest list has gone.

The hard disappearing snap occurs in 5.2.28, 6.0.14, and 6.1.0. 
5.2.28 does show a thin vertical drag bar.",scottgus1
17376,unable to start vm: VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH,Linux,,2017-12-18T14:07:49Z,2019-03-28T09:33:28Z,2019-03-28T09:33:28Z,"I'm getting the following error again when trying to restore a saved machine. Same machine worked fine a couple of days ago.
No update or reinstall of VirtualBox in the meantime.

{{{
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)

Please try reinstalling VirtualBox.

where: supR3HardNtChildPurify what: 5
VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH: (rc=-5618)- Process Verification 
Failure: Executable file name and process image name does not match up.
}}}

After reinstalling VirtualBox by choosing ""repair"" when running the executable, and rebooting Windows, I was able to start the vm guest just fine from the saved state.

VirtualBox: 5.2.3r119650

Host: Windows 10 64bits",rosch
18040,Failing to attach USB device,Windows,,2018-10-09T15:53:07Z,2018-10-25T10:01:59Z,2018-10-25T10:01:59Z,"Not able to attach a USB device to VM with USB over Ethernet Connector ([https://www.eltima.com/products/usb-over-ethernet/]) installed on the host.

Virtualbox is the latest version.

Host and guest are both Win7 64-bit.

If I uninstall USB redirection software from the host, then everything works fine.

Attached a screenshot of the error message.",redhotchili
14545,"""Failed to create host network interface"" on Windows 10",other,,2015-09-05T17:15:35Z,2018-09-12T08:34:35Z,2018-09-12T08:34:35Z,"I'm trying to get Xamarin Android Emulator working on Windows 10.  It's failing because VirtualBox does not have a host network adapter set up.  It worked fine on Windows 8.

When I attempt to create a host network adapter in Virtual Box, I get this error:

""Failed to create the host network interface
Result Code: 
E_FAIL (0x80004005)""

I've tried doing a uninstalling/reinstalling, and doing a repair install.  I don't know if this is related to #14040, but I'm using the latest beta, which supposedly fixed that issue..

Version: 5.0.3-102322-Win",BlueRaja
14747,No sound. Windows 7 host / Arch Linux guest.,Linux,,2015-10-26T09:00:58Z,2018-02-28T09:22:23Z,2018-02-28T09:22:23Z,"I have the same problem as described in https://www.virtualbox.org/ticket/14361.
I see ""DSound: CreateCaptureBuffer E_FAIL"" and ""DSound: playback start E_ACCESSDENIED"" in the logs.

VirtualBox v5.0.8 (it is not available in the version list for some reason).
",noname1
15630,Virtualbox guest control controls inaccessible with NVDA on Windows,all,,2016-07-17T19:37:02Z,2017-08-30T12:55:11Z,2017-08-30T12:55:11Z,"When pressing for example host+q to access the shutdown dialog or accessing the menu with the usb devices, NVDA can not determine any type of a control and reports everything as unknown.",tyrylu
16919,"Crash, possibly when pressing several keys very fast or simultaneously",Windows,,2017-07-19T20:00:06Z,2017-07-19T20:00:06Z,2017-07-19T20:00:06Z,"After installing version 5.1.24 and worked for a while in an XP guest, it crashed. It did that a 2nd time and that's when i got the attached log. Both times i was typing, so i got the impression (without being sure) that it crashed because i was typing too fast or because i pressed many keys simultaneously.

After a fresh start, i tried to reproduce the crash by typing fast and pressing many keys at the same time but without any success.

The same host/guest combination has worked without such issues from version 5.1.0 up to 5.1.22.

Host: WIn7 SP1, Guest: WinXP SP3.

P.S. After installing 5.1.24, i noticed a certain slugginess (even after installing guest additions) when maximizing/restoring/resizing the guest window. Again, was not happening in 5.1.22.",Wand
14634,Win 10 VM dual screen terminates to a single screen,Windows,,2015-09-24T19:00:03Z,2016-10-17T04:41:11Z,2016-10-17T04:41:11Z,"I am using test build Version 5.0.5 r102814. The win 10 VM loses the second screen intermittently. i have to restart the VM in order to get 2 screens again. The Display setting on the Win 10 VM are as follows:

Video Memory - 256 MB
Monitor Count - 2
Scale Factor - 100%
No 3D or 2D acceleration
no Remote Display
no Video Capture
VM Memory allocated: 3072 MB
VM processors: 2

Current laptop system: Windows 10 Professional
laptop memory 32 GB
",Centurion
13816,Random crashes when NVDA or Narrator are running,all,,2015-02-08T05:47:39Z,2015-09-30T20:12:08Z,2015-09-30T20:12:08Z,"​In general, the GUI is quite accessible with both ZoomText's Reader and NVDA (I've tested both independently); however, when NVDA is running, VirtualBox will randomly crash at certain points when using the GUI. For example, I could get it to consistently crash when opening the File => Preferences menu, and then pressing ESC to exit. Another example is that I could get all the way through creating my first VM, but then VBox crashes when clicking to create the virtual disk. As a final example, when going to the Settings menu of my VM and pressing ESC to exit/cancel, VBox crashes (I was only able to create the VM in the first place by turning off NVDA).  Please take time to investigate this issue by installing the free NVDA screen reader and just performing one of these actions while it is running.  Thank you.",IcepickSU
14112,BSoD in VBoxNetAdp6.sys with STOP 0x9F,other,,2015-05-13T14:51:58Z,2015-06-30T18:47:27Z,2015-06-30T18:47:27Z,"Version: VirtualBox 5.0 Beta 2 (previously same error in VBoxNetAdp.sys in 4.3.26, 4.2.?).  I'm trying out the beta to try to get past this annoying error.  The last few times I've followed steps similar to

http://dottech.org/101997/how-to-uninstall-virtualbox-drivers-on-windows/

to remove all traces of any drivers/any registry settings I could find to remove any prior copy of VirtualBox

This issue is most similar to: https://www.virtualbox.org/ticket/11730

Win7x64 Host, Bridged Networking turned on, the VirtualBox program isn't running when the crash occurs.

Network Adapters:

* Intel(R)82567V-2 Gigabit Network Connection on latest driver:   10.0.6.0 ( confirmed via windows and HP websites )
* VirtualBox Host-Only Ethernet Adapter

Minidump for v5.0 Beta2:

{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051315-86174-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0ec26c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0023a662?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9a500?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e62730
Debug session time: Wed May 13 06:57:38.999 2015 (UTC - 7:00)
System Uptime: 0 days 21:49:09.234
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009aa44d0, fffff80000b9a518, fffffa8014ff7010}

Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetAdp6.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp6.sys
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009aa44d0, Physical Device Object of the stack
Arg3: fffff80000b9a518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8014ff7010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff8800413e000 VBoxNetAdp6

IRP_ADDRESS: fffffa8014ff7010

DEVICE_OBJECT: fffffa800c4cd050

DRIVER_OBJECT: fffffa800c1f1ce0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF80000BA0FB0

STACK_TEXT:  
fffff800`00b9a4c8 fffff800`02cfe510 : 00000000`0000009f 00000000`00000003 fffffa80`09aa44d0 fffff800`00b9a518 : nt!KeBugCheckEx
fffff800`00b9a4d0 fffff800`02c9b72c : fffff800`00b9a600 fffff800`00b9a600 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x324a0
fffff800`00b9a570 fffff800`02c9b5c6 : fffffa80`0d4d5748 fffffa80`0d4d5748 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a5e0 fffff800`02c9b4ae : 000000b6`e2fdfdf7 fffff800`00b9ac58 00000000`004cd4a7 fffff800`02e12768 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9ac30 fffff800`02c9b297 : 00000031`e222c6c4 00000031`004cd4a7 00000031`e222c6c3 00000000`000000a7 : nt!KiTimerExpiration+0x1be
fffff800`00b9acd0 fffff800`02c875ca : fffff800`02e0ee80 fffff800`02e1ccc0 00000000`00000000 fffff880`013b24c0 : nt!KiRetireDpcList+0x277
fffff800`00b9ad80 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetAdp6
start             end                 module name
fffff880`0413e000 fffff880`04161000   VBoxNetAdp6 T (no symbols)           
    Loaded symbol image file: VBoxNetAdp6.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp6.sys
    Image name: VBoxNetAdp6.sys
    Timestamp:        Tue Apr 14 11:38:41 2015 (552D5EB1)
    CheckSum:         0001F0DE
    ImageSize:        00023000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa8014ff7010 1
Irp is active with 3 stacks 2 is current (= 0xfffffa8014ff7128)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa8014ff7030
ThreadListEntry.Blink = fffffa8014ff7030
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa8014ff7088
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa80139c8eb8
Tail.Overlay.ListEntry.Blink = fffff80002e44bc0
Tail.Overlay.CurrentStackLocation = fffffa8014ff7128
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 fffffa800c4cd050 00000000 fffff80002ee1210-fffffa800ec22a30 Success Error Cancel pending
	       \Driver\VBoxNetAdp	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800ec22a30    

			Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800c4cd050 f
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800c4cd050) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c4cd020
 \Driver\VBoxNetAdp DriverObject fffffa800c1f1ce0
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800c4cd1a0 DevObjExt fffffa800c4ce8e0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8009aa44d0 \Driver\PnpManager
Device queue is not busy.
0: kd> !drvobj fffffa800c1f1ce0 f
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
fffff80002e45070: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa800c1f1ce0) is for:
 \Driver\VBoxNetAdp
Driver Extension List: (id , addr)

Device Object list:
fffffa800c4cd050  

DriverEntry:   fffff8800413f860	VBoxNetAdp6
DriverStartIo: 00000000	
DriverUnload:  fffff880016aecd0	ndis!ndisMUnloadEx
AddDevice:     00000000	

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88001608920	ndis!ndisCreateIrpHandler
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff8800169e490	ndis!ndisDummyIrpHandler
[02] IRP_MJ_CLOSE                       fffff88001608160	ndis!ndisCloseIrpHandler
[03] IRP_MJ_READ                        fffff8800169e490	ndis!ndisDummyIrpHandler
[04] IRP_MJ_WRITE                       fffff8800169e490	ndis!ndisDummyIrpHandler
[05] IRP_MJ_QUERY_INFORMATION           fffff8800169e490	ndis!ndisDummyIrpHandler
[06] IRP_MJ_SET_INFORMATION             fffff8800169e490	ndis!ndisDummyIrpHandler
[07] IRP_MJ_QUERY_EA                    fffff8800169e490	ndis!ndisDummyIrpHandler
[08] IRP_MJ_SET_EA                      fffff8800169e490	ndis!ndisDummyIrpHandler
[09] IRP_MJ_FLUSH_BUFFERS               fffff8800169e490	ndis!ndisDummyIrpHandler
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff8800169e490	ndis!ndisDummyIrpHandler
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff8800169e490	ndis!ndisDummyIrpHandler
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff8800169e490	ndis!ndisDummyIrpHandler
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff8800169e490	ndis!ndisDummyIrpHandler
[0e] IRP_MJ_DEVICE_CONTROL              fffff8800169e020	ndis!ndisDeviceControlIrpHandler
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff8800169e490	ndis!ndisDummyIrpHandler
[10] IRP_MJ_SHUTDOWN                    fffff8800169e490	ndis!ndisDummyIrpHandler
[11] IRP_MJ_LOCK_CONTROL                fffff8800169e490	ndis!ndisDummyIrpHandler
[12] IRP_MJ_CLEANUP                     fffff8800169e490	ndis!ndisDummyIrpHandler
[13] IRP_MJ_CREATE_MAILSLOT             fffff8800169e490	ndis!ndisDummyIrpHandler
[14] IRP_MJ_QUERY_SECURITY              fffff8800169e490	ndis!ndisDummyIrpHandler
[15] IRP_MJ_SET_SECURITY                fffff8800169e490	ndis!ndisDummyIrpHandler
[16] IRP_MJ_POWER                       fffff88001652c60	ndis!ndisPowerDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff88001672ee0	ndis!ndisWMIDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff8800169e490	ndis!ndisDummyIrpHandler
[19] IRP_MJ_QUERY_QUOTA                 fffff8800169e490	ndis!ndisDummyIrpHandler
[1a] IRP_MJ_SET_QUOTA                   fffff8800169e490	ndis!ndisDummyIrpHandler
[1b] IRP_MJ_PNP                         fffff880016bc560	ndis!ndisPnPDispatch
}}}

Here's a 4.3.26 example:

{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040715-17799-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0023dc32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02dcfc32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`042d4500?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: symsrv*symsrv.dll*c:\extracts\ms debuggger\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c890
Debug session time: Mon Apr  6 20:24:15.313 2015 (UTC - 7:00)
System Uptime: 12 days 4:51:38.831
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8009aa6060, fffff800042d4518, fffffa800d2fdd60}

Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetAdp.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetAdp.sys
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009aa6060, Physical Device Object of the stack
Arg3: fffff800042d4518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800d2fdd60, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88005279000 VBoxNetAdp

IRP_ADDRESS: fffffa800d2fdd60

DEVICE_OBJECT: fffffa800c321050

DRIVER_OBJECT: fffffa800aa7ae70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF800042DAFB0

STACK_TEXT:  
fffff800`042d44c8 fffff800`02cedb92 : 00000000`0000009f 00000000`00000003 fffffa80`09aa6060 fffff800`042d4518 : nt!KeBugCheckEx
fffff800`042d44d0 fffff800`02c88cfc : fffff800`042d4600 fffff800`042d4600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`042d4570 fffff800`02c88b96 : fffff800`02e2f140 00000000`04073b69 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`042d45e0 fffff800`02c88a7e : 00000996`bb12dbac fffff800`042d4c58 00000000`04073b69 fffff800`02dfcfa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`042d4c30 fffff800`02c88867 : 0000029d`89aab1c1 0000029d`04073b69 0000029d`89aab16a 00000000`00000069 : nt!KiTimerExpiration+0x1be
fffff800`042d4cd0 fffff800`02c74bca : fffff800`02df9e80 fffff800`02e07cc0 00000000`00000000 fffff880`012234c0 : nt!KiRetireDpcList+0x277
fffff800`042d4d80 00000000`00000000 : fffff800`042d5000 fffff800`042cf000 fffff800`042d4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetAdp
start             end                 module name
fffff880`05279000 fffff880`052a1000   VBoxNetAdp T (no symbols)           
    Loaded symbol image file: VBoxNetAdp.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetAdp.sys
    Image name: VBoxNetAdp.sys
    Timestamp:        Mon Mar 16 09:35:44 2015 (55070660)
    CheckSum:         00030F13
    ImageSize:        00028000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa800d2fdd60 1
Irp is active with 3 stacks 2 is current (= 0xfffffa800d2fde78)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800d2fdd80
ThreadListEntry.Blink = fffffa800d2fdd80
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800d2fddd8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa800de5fd68
Tail.Overlay.ListEntry.Blink = fffff80002e2ed20
Tail.Overlay.CurrentStackLocation = fffffa800d2fde78
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 fffffa800c321050 00000000 fffff80002ecb210-fffffa800d27ba50 Success Error Cancel pending
	       \Driver\VBoxNetAdp	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800d27ba50    

			Args: 00000000 00000000 00000000 00000000
0: kd> !devobj fffffa800c321050 f
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800c321050) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c321020
 \Driver\VBoxNetAdp DriverObject fffffa800aa7ae70
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa800c3211a0 DevObjExt fffffa800c3228e0 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) fffffa8009aa6060 \Driver\PnpManager
Device queue is not busy.
0: kd> !drvobj fffffa800aa7ae70 f
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
fffff80002e2f1d0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa800aa7ae70) is for:
 \Driver\VBoxNetAdp
Driver Extension List: (id , addr)

Device Object list:
fffffa800c81f4d0: Could not read device object


DriverEntry:   fffff8800527e0e0	VBoxNetAdp
DriverStartIo: 00000000	
DriverUnload:  fffff880017c04a0	ndis!ndisMUnload
AddDevice:     00000000	

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88001716920	ndis!ndisCreateIrpHandler
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff880017ac490	ndis!ndisDummyIrpHandler
[02] IRP_MJ_CLOSE                       fffff88001716160	ndis!ndisCloseIrpHandler
[03] IRP_MJ_READ                        fffff880017ac490	ndis!ndisDummyIrpHandler
[04] IRP_MJ_WRITE                       fffff880017ac490	ndis!ndisDummyIrpHandler
[05] IRP_MJ_QUERY_INFORMATION           fffff880017ac490	ndis!ndisDummyIrpHandler
[06] IRP_MJ_SET_INFORMATION             fffff880017ac490	ndis!ndisDummyIrpHandler
[07] IRP_MJ_QUERY_EA                    fffff880017ac490	ndis!ndisDummyIrpHandler
[08] IRP_MJ_SET_EA                      fffff880017ac490	ndis!ndisDummyIrpHandler
[09] IRP_MJ_FLUSH_BUFFERS               fffff880017ac490	ndis!ndisDummyIrpHandler
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff880017ac490	ndis!ndisDummyIrpHandler
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff880017ac490	ndis!ndisDummyIrpHandler
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff880017ac490	ndis!ndisDummyIrpHandler
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff880017ac490	ndis!ndisDummyIrpHandler
[0e] IRP_MJ_DEVICE_CONTROL              fffff880017ac020	ndis!ndisDeviceControlIrpHandler
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff880017ac490	ndis!ndisDummyIrpHandler
[10] IRP_MJ_SHUTDOWN                    fffff880017ac490	ndis!ndisDummyIrpHandler
[11] IRP_MJ_LOCK_CONTROL                fffff880017ac490	ndis!ndisDummyIrpHandler
[12] IRP_MJ_CLEANUP                     fffff880017ac490	ndis!ndisDummyIrpHandler
[13] IRP_MJ_CREATE_MAILSLOT             fffff880017ac490	ndis!ndisDummyIrpHandler
[14] IRP_MJ_QUERY_SECURITY              fffff880017ac490	ndis!ndisDummyIrpHandler
[15] IRP_MJ_SET_SECURITY                fffff880017ac490	ndis!ndisDummyIrpHandler
[16] IRP_MJ_POWER                       fffff88001760c60	ndis!ndisPowerDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff88001780ee0	ndis!ndisWMIDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff880017ac490	ndis!ndisDummyIrpHandler
[19] IRP_MJ_QUERY_QUOTA                 fffff880017ac490	ndis!ndisDummyIrpHandler
[1a] IRP_MJ_SET_QUOTA                   fffff880017ac490	ndis!ndisDummyIrpHandler
[1b] IRP_MJ_PNP                         fffff880017ca560	ndis!ndisPnPDispatch
}}}

I've experienced 8 similar crashes since March 3/25 using different versions of VirtualBox.  It would seem that if you need to reproduce this error somewhat reliably, my machine can do it.",ohm
5816,Reserve the guest OS taskbar space on the host OS desktop in seamless mode,Windows,,2009-12-21T08:23:27Z,2010-02-23T13:58:13Z,2010-02-23T13:58:13Z,"I think this will be useful for those who want the guest to work seamless with the host OS.

In the seamless mode, When a host application is maximized, it will cover the guest OS taskbar. If I want to use guest application, I have to minimize the host application to make the guest taskbar show up. So there will be a lot of unnecessary mouse clicks and movement, if I have to do much copy/paste work between guest and host.

Now, I walk around this problem using the HSI(Hawkeye ShellInit), a small tool that can create any number of margins on the screen that maximized windows won't cover.

I think this can be easily implimented in the Virtualbox. The guest additions gets the guest's taskbar position and width, then sends this imformation to the vboxmanager. The vboxmanager performs the same function in seamless mode like what the HSI will do. ",kidault
1397,Feature request: Overcommitting of memory (swap in/out),other,VirtualBox 1.5.6,2008-04-08T13:32:45Z,2016-08-22T16:35:36Z,2016-08-22T16:35:36Z,"I always get HostMemoryLow e.g. Knoppix 5.2. VMware and Microsoft Virtual PC work on this PC (IBM Thinkpad T40, 512 Mb RAM). I have enclosed the Logfile. How can I help?",IuK
1752,Software Installation not passed Windows Logo testing,other,VirtualBox 1.6.2,2008-06-20T18:34:53Z,2010-10-05T22:06:06Z,2010-10-05T22:06:06Z,"During installation a dialog box appears warning that:

""The software you are installing has not passed the Windows Logo testing to verify its compatibility with Windows XP.  (Tell me why this is important)

Continuing your installation of this software may impair or destabilize the correct operation of your system either immediately or in the future.  Microsoft strongly recommends that you stop this installation now and contact the software vendor for software that has passed Windows Logo testing""

Some users may take Microsoft's strong advice and not install VirtualBox.",Jerry Waldorf
2097,Minimize to task bar on key,Windows,VirtualBox 2.0.0,2008-09-05T14:38:20Z,2015-08-06T20:26:22Z,2015-08-06T20:26:22Z,"Feature Request: Add key to go from Full Screen to minimized (hidden in task bar). Switching back to V.B. shall enter Full Screen again.
",A20_user
2152,"Feature Request: allow ""move"" option when changing Snapshots Folder",Windows,VirtualBox 2.0.0,2008-09-08T09:29:27Z,2010-08-17T09:45:43Z,2010-08-17T09:45:43Z,"I would like the VirtualBox GUI to offer to *move* any existing snapshots, if I change the Snapshots Folder (in the ""Advanced"" tab of the General settings).  Currently, I get the following error message instead:

""The snapshot folder of a machine with snapshots cannot be changed (please discard all snapshots first).""
",Kevin Roth
2107,Feature request: Predefined absolute time for Guest,Windows,VirtualBox 2.0.0,2008-09-05T22:03:12Z,2009-02-10T23:08:26Z,2009-02-10T23:08:26Z,Please add an option to set Guest time to a fixed value at startup. This is a feature for repeatable software tests.,A20_user
2098,MaxGuestResolution per machine,Windows,VirtualBox 2.0.0,2008-09-05T14:40:26Z,2008-09-08T07:28:43Z,2008-09-08T07:28:43Z,"Feature request: ""VBoxManage setextradata global GUI/MaxGuestResolution ..."" shall be a per-machine setting.
",A20_user
2389,mount.vboxfs does not allow context= option,Linux,VirtualBox 2.0.2,2008-10-07T16:36:55Z,2009-01-21T09:07:47Z,2009-01-21T09:07:47Z,"Mounting a shared folder in a Fedora 9 linux guest, I receive SELinux denials when I try to copy files into the shared folder.  I received advice to attempt the mount using a ''context= option''.

According to the mount manpage, the ''context='' option should be supported on all filesystems...  So I guess this ticket is an RFE.

Cheers,
 Christian",Christian Iseli
2570,Seamless mode with Vista host doesn't work correctly with Sidebar turned on,Windows,VirtualBox 2.0.4,2008-11-05T20:24:35Z,2009-05-04T16:34:53Z,2009-05-04T16:34:53Z,"Using a Vista host with the Sidebar enabled, a Windows XP guest in seamless mode isn't cropped properly.  All window cropping is shifted to the left 2 pixels, such that a windows shows 2 pixels of the background on the left and is missing 2 pixels of the border on the right.

The problem disappears when the Sidebar is closed.",Chris Thompson
3045,Feature Request: Control HOST os resolution in fullscreen mode (for res switching),Windows,VirtualBox 2.1.0,2009-01-15T12:05:14Z,2009-10-29T19:35:02Z,2009-10-29T19:35:02Z,"Id like to see a feature that allows virtual box to control the physical monitor on resolution switching 

for example
  you launch gameA.exe and it needs to run in fullscreen 800x600 on the GUEST os but the HOST os is 1600x1600 (right now it just shows as a little square in the middle of the screen with big borders), it would be really nice if VirtualBox could change the HOST display to the required resolution the guest os is at. (this would probably be needed for windows only and when in fullscreen mode, i think X11 doesn't change res's as much) 

so far other software such as microsoft virtual pc 2007 (in their options it has a pulldown that says ""use guest os resolution"", ""use host's resolution"" ..etc)

vmware , and parallels has a option, VirtualBox is such great software this feature missing is a giant let down for me, it has speed, hardware support, lightweight, it just cant control the host's resolution. :\

dont confuse this with ctrl+g (since that just ups the virtualbox to the host's current resolution (what i need is the host's resolution to match the currnet guest os resolution so basically its reversed ;) ) 

",hyakki
3351,Normalise or repair the XML data models,other,VirtualBox 2.1.2,2009-02-16T14:19:01Z,2011-06-23T00:16:25Z,2011-06-23T00:16:25Z,"Currently the VBox metadata models are denormalised in that data elements are duplicated between the central ''!VirtualBox.xml'' registry and the various machine.xml files.  The VBox application does not enforce proper transactional integrity between these various definition files and so various program errors can cause them to get out of sync.  A result of this is that VBox will then refuse to load the VM and the users are unable to recover the contents of any snapshotted HDs with understanding the XML schemas and manually patching up the XML files — not something that the average use is capable of doing.  Hence certain classes of VBox error can result in major data loss for most users.  There is sufficient volume of posts on the forum related to this issue to support the conclusion that this is a real problem.

As far as I can see there are three possible approaches to remove this product vulnerability:
 * '''Renormalise the data models'''.  For example the ''<!MediaRegistry><!HardDisks>'' tree would only contain HDs that are not allocated to VMs.  The complete set of ''<!HardDisks>'' could be obtained by enumerating this tree plus the ''<!HardDisks>'' in each attached machine.  (This node would replace the existing ''<!HardDiskAttachments>'' node).  Such an approach would also mean that a VM is now a self-contained entity that can be exported or imported (a frequent user request).  Yes this would require addition integrity checks to walk the VMs XML files when adding or removing HDs, but this is hardly a frequent occurrence.  This is my recommended option.
 * '''Provide a repair too'''.  This would walk the various XML files, identify inconsistencies and have a set of rules for when to recommend recovery and when to ask the user for a choice.
 * '''Move the meta data to a proper DB'''.  The obvious one to use here is SQLlite: simple, free, and able to handle the transactional issues.  Under this scenario the Machine schema would only be used for importing and exporting machines.
This metadata is critical to the protecting the user content maintained within the various VMs, yet there are no transactional, journalling or recovery mechanisms provided to ensure the integrity of this metadata.  This is unacceptable in product of VBox's maturity.",Terry Ellison
3461,Settings saved in wrong place (WinXP),other,VirtualBox 2.1.4,2009-03-01T14:48:20Z,2010-07-11T00:08:07Z,2010-07-11T00:08:07Z,"Hi, 

Currently Virtualbox save its settings here:[[BR]]
{{{%userprofile%\.VirtualBox}}}

Unfortunately, this is the wrong place under Windows XP. Applications are supposed to store their settings, etc. in {{{%appdata%}}}.

So it should be this way:[[BR]]
{{{%appdata%\.VirtualBox}}}

And, by the way, on a Windows system it's a bit unusual to use folder names with a leading dot (okay, I am a bit fussy now).

Therefore, to be even more Windows-like, it should be:[[BR]]
{{{%appdata%\VirtualBox}}}
",David
3493,Pass the Tablet PC Pen Flicks from the host to the guest,Windows,VirtualBox 2.1.4,2009-03-04T12:59:25Z,2009-03-04T12:59:25Z,2009-03-04T12:59:25Z,"Pass the Tablet PC Pen Flicks from the host to the guest

1- Install the Virtual Box on Windows Vista 32 or 64 bit
2- Connect a wacom babmo tablet with pen and install the drivers
3- Open the vista control panel, and enable all pen flicks.
4- Install Windows Xp or Vista on a virtual machine, and install the additions.
5- Do (Copy) or (Paste) or (Undo) with the pen on the virtual machine

Results:
Vista will report that the pen flick is successful, but nothing will happen in the virtual machine

Expected Results:
Please just pass the flick command to the guest OS, I am not asking for full pen support, the current mode is very good, just pass the pen flicks to the guest.
",GT
3484,"Using shared folders, if the underlying shared resource becomes unavailable, you cannot remove it from its previously assigned VBOXSVR mapping.",Windows,VirtualBox 2.1.4,2009-03-03T12:33:36Z,2009-03-03T12:33:36Z,2009-03-03T12:33:36Z,"Share a resource permanently, read-only, say E:\mp3 -> mp3.  This will show up in the guest OS as \VBOXSVR\mp3.  Then change the drive letter or make the resource generally unavailable (e.g. no E: drive).  Then try to go in to shared folders and remove it - this will appear to work successfully.  But if you go into the guest OS and browse, \VBOXSVR\mp3 will still be there!  Nothing you do within Vbox will make that change - rebooting, logging out as different user, etc.

I've attached virtual machine config files as well.

WORKAROUND:
* Shut down the guest OS
* Go to MachineDisks and find the guest OS's .xml file.
* Find section SharedFolders/SharedFolder which corresponds to share you're trying to remove.
* Change or remove the entry to be correct.
* Restart guest OS virtual machine.
* Vbox appears to just remove the entry you modified in the .xml file regardless of whether you set it to a valid value or not.
* Re-add the changed resource path (if you want to change it).

",cboyd
3654,Bridged Networking does not find any adapters,other,VirtualBox 2.2.0,2009-04-08T17:08:02Z,2015-06-10T20:15:06Z,2015-06-10T20:15:06Z,"When configuring a guest in version 2.2.0 under Windows Vista (I have x64, some others have reported with x32), under the bridged network configuration, the only selection for ""Bridged Network Adapter"" that I can choose is ""Not selected.""  This means that I cannot configure the network to work in bridged mode.  This has been reported on the forum: [http://forums.virtualbox.org/viewtopic.php?f=6&t=16202&start=0].",brigad@rpi.edu
4087,Multimedia keys not passed through to guest,Linux,VirtualBox 2.2.2,2009-05-24T09:58:47Z,2022-07-15T10:43:12Z,2022-07-15T10:43:12Z,"I have a Cherry eVolution STREAM keyboard. The following buttons are not passed through to the guest when pressed:

volume down
mute
volume up
previous track
play/pause
next track

At least, according to xev. They work in the host just fine.

The host is Vista Home Basic x64. The guest is Debian using Linux 2.6.26.",Sam Morris
4088,Noticeable audio latency,Linux,VirtualBox 2.2.2,2009-05-24T10:00:58Z,2016-10-22T15:52:58Z,2016-10-22T15:52:58Z,"There is a noticeable delay between when the guest operating system starts to play a sound, and when it actually becomes audible. Perhaps in the range of 100-200 ms--just a guess though, I'm not sure how to time it.

The host is Vista Home Basic x64 and the guest is Debian running Linux 2.6.26.",Sam Morris
3972,OS/2 guest cannot write to floppy disk,other,VirtualBox 2.2.2,2009-05-08T23:25:39Z,2016-08-13T20:25:48Z,2016-08-13T20:25:48Z,"I am using a Vista x64 SP2 host, and OS/2 ACP2 guest.
When I mount the floppy drive in the guest, I can read files from the floppy just fine. But I can't do any writes. All writes (such as COPY, DEL, etc) result in a SYS0039 ""The A: device is not ready"".

The floppy drive works fine in the host, and I am able to do those same operations in the host OS to the same floppy disk just fine (if I unmount the floppy from the guest, of course).
",Julien Pierre
3974,OS/2 guest is limited to 1024x768x16777216 resolution,other,VirtualBox 2.2.2,2009-05-08T23:53:12Z,2016-06-17T14:22:16Z,2016-06-17T14:22:16Z,"I have installed OS/2 ACP2 as a guest, and the virtual box OS/2 additions.
The maximum resolution I can select is 1024x768 in 24 bits. This is not much, especially if one wants to open many windows and use the VM for development. I have two monitors on my Vista host, a 24"" at 1920x1200, and a 30"" at 2560x1600 . I can use the full screen with my other guests (Solaris, Opensolaris, Win7). But with the OS/2 guest, I can only use a small portion of the screen. This is really limiting.

Even MS virtual PC supports a higher resolution (1600x1200) in the OS/2 guest. Unfortunately I can't use both Virtual PC and Virtual Box at the same time - it results in BSODs on the host. I have to choose one or the other.

While I realize the OS/2 guest will never have dynamic resolution support like the other hosts, I really wish you could offer some higher fixed resolutions for the guest, at least standard resolutions like 1280x1024, 1600x1200, 1920x1200, even if you don't go all the way to 2560x1600 .
",Julien Pierre
3866,Host-only interface interferes with the current adapter,other,VirtualBox 2.2.2,2009-04-29T03:21:22Z,2015-05-22T10:11:14Z,2015-05-22T10:11:14Z,"When the host-only interface is installed, it '''suddenly''' screws up the connection for the physical adapter. The adapter says it is identifying the network when it is connected to it already.",Frank
4057,ER: Simpler way of accessing Windows host printer from Ubuntu guest,Linux,VirtualBox 2.2.2,2009-05-20T08:47:09Z,2009-05-20T09:05:57Z,2009-05-20T09:05:57Z,"
I am a non-technical user of VirtualBox 2.2.2 so I can run Linux programs on a Ubuntu guest for purposes of writing third-party user guides in FrameMaker on Windows XP SP3. I would like to remain a non-technical user and therefore propose that Guest Additions for all guest OSes incorporates a virtual printer that can access one or more real network/local/usb/parallel/serial printers on the host OS.

This could be a configuration option in the xVM VirtualBox GUI that allows the user to map guest printers to real printers, however then may be attached to the host.

I am trying to access my Epson CX6900F on Windows XP SP3 from an Ubuntu 9.04 Jaunty Jackalope using CUPS and Samba but without success. (I told you I was non-technical.)

I have shared a folder on Windows to try and access it from Samba but although it scans for shared folders can't find it.  Same for shared printer with CUPS.",Hedley Finger
4358,Break signal on serial port is not delivered to the port in vm,Windows,VirtualBox 2.2.4,2009-07-02T15:30:13Z,2011-07-25T14:25:03Z,2011-07-25T14:25:03Z,"On the host machine, I run an application that listens to COM port and reacts when the port sends Break signal. To the port I connect a device capable of sending Break signal, and the application reacts as programmed.

In Windows v.m. I specify COM port mapped to the real port on the host machine. Then I run the same application in the virtual machine and have the device send break signal. But the application in v.m. does not see it.

Break signal is described at 
http://support.microsoft.com/kb/119506

its implementation in Visual Basic at 
http://msdn.microsoft.com/en-us/library/aa259405(VS.60).aspx

I can provide the sample program demonstrating this, if needed.


",vadimrapp
4754,Suggest a new function to install the VDI file to a real physical hardrive,Linux,VirtualBox 3.0.0,2009-08-12T00:49:45Z,2010-08-19T20:00:45Z,2010-08-19T20:00:45Z,"Hi, all VBox developers,
I am a 1-year VBox user, fanny about this application.
Thank you all for the masterpiece.

Currently, I have been running Ubuntu(a kind of Linux, as guest OS here) on VBox on Windows(as host OS here) for 1 year and love the Ubuntu OS very much. 
However, how could I put the Ubuntu to a physical hardisk?
That means, how could I write the VDI file to a real phycial hardisk, in which way Ubuntu is on a real and physical machine? 
Is there such a functionality in VBox of next version?

Thanks and waiting. ",jack
5477,Mini toolbar option in GUI is confusing and inconsistent with Shared Clipboard option,other,VirtualBox 3.0.10,2009-11-16T16:28:10Z,2011-08-18T05:36:42Z,2011-08-18T05:36:42Z,"Hi,
using VirtualBox 3.0.10 on Windows XP host. On General section on Advanced tab there are two settings: ""Shared Clipboard"" and ""Mini Toolbar"". Both of them are solving same type of problem, but there are solved very differently using GUI options, which can be very confusing, specially for new user.

I suggest to implement ""Mini ToolBar"" option like ""Shared Clipboard"" option and that is create drop down menu with three options: ""Disable"", ""Show At Top Of Screen"" and ""Show At Bottom of Screen"".

This kind of solving the same type of problem would make GUI tool more user friendly especially for new users.
Regards",grof
5349,traffic get answered on the wrong VLAN,Linux,VirtualBox 3.0.10,2009-10-30T18:44:54Z,2009-10-30T18:44:54Z,2009-10-30T18:44:54Z,"debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

second debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

you will notice on the tcpdump trace that requests are received in VLAN 400/VLAN4 (this is QinQ) but the response is sent on VLAN 4 which is not even configured on the box.

tcpdump [[BR]]

tcpdump -i eth2[[BR]]

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode[[BR]]

listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes[[BR]]

15:33:47.584076 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:47.614299 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:48.566620 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:48.566983 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:49.549445 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]
[[BR]]
[[BR]]


setup:[[BR]]

apt-get install vlan[[BR]]

modprobe 8021q[[BR]]

vconfig add eth3 400[[BR]]

ifconfig eth3.400 up[[BR]]

vconfig add eth3.400 4[[BR]]

ifconfig eth3.400.4 up[[BR]]


",erik
5515,Builtin DHCP server does not pick up setting update once started,Linux,VirtualBox 3.0.12,2009-11-20T10:25:21Z,2020-09-10T08:52:41Z,2020-09-10T08:52:41Z,"I have several hosts that I want to connect with each other without access to the outside world. So all hosts use host-only networking. One of the hosts provides PXE and DHCP, so I went to File -> Preferences -> Network and edited the settings for the host-only networking. In the tab of the DHCP Server I disabled the DHCP server. Then I started my management server (fixed IP address in the proper range), configured DHCP with a range outside the default range for host-only and started one of the client hosts. PXE went well and the OS was installed. When the client host requested an IP-address, it was served with an address from the builtin DHCP server although I disabled this server. Stopping all clients and restarting VirtualBox did not solve this. After a reboot of the host system, the DHCP server was truly disabled and the client was served with an address from my management server.",SiemKorteweg
5598,ReactOS not listed under OS,Windows,VirtualBox 3.0.12,2009-11-30T09:57:45Z,2017-12-08T15:30:40Z,2017-12-08T15:30:40Z,"Dear VirtualBox support,
I test ReactOS with VirtualBox, it works ver well, it's even listed in the OS matrix, but it isn't available as an OS in VirtualBox itself, could you please add it?
Best regards.

Gabriel.",gabriel
5568,unable to perform some svn operations on shared folders from guest,Linux,VirtualBox 3.0.12,2009-11-26T06:32:34Z,2016-02-01T21:02:56Z,2016-02-01T21:02:56Z,"Host: Windows Vista


Guest: Gentoo


Description:

In the development, I need to use some collaboration system whose gui client in windows sucks. So I plan to share the project direcotries with my guest gentoo and then use the command line client in unix instead.[[BR]]
However, because the client depends on the result of 'svn status' and my netbeans uses its own SCM instead of the native one, I have to do this manually, which fails.[[BR]]
This is the error message when I perform some svn operation like 'svn add':
{{{
svn: Can't move '.svn/tmp/entries' to '.svn/entries': Operation not permitted
}}}
This will never happen if the underlying file system is local since I care little about anything inside the .svn directory. I try to chmod it 777 and find that somehow its permission will get ""reverted"" before svn starts its job.[[BR]]
The shared folders are mounted manually with default options. I can do whatever I wish but not with svn, which sounds weird. I hope this does help.[[BR]]
BTW, vbox rocks!",Marvin
5587,"USB device is reported as ""unknown device"" in Windows Guest on Windows Host",Windows,VirtualBox 3.0.12,2009-11-29T03:15:16Z,2015-11-06T11:06:32Z,2015-11-06T11:06:32Z,"The problem appears related to the slash contained in the device serial number. My guess is that the conversion into a # brokens the guest address. 

Using ""VBoxManage.exe list usbhost"":
{{{
UUID:               d398cf2d-92ee-44bc-aa8e-6ccef37494eb[[BR]]
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       '''GNU/GPL2'''
Address:            {eb781aaf-9c70-4523-a5df-642a87eca567}\0000
Current State:      Busy
}}}
is reported at the guest as:
{{{
UUID:               fd66cabb-4b08-4a90-a877-468e438c50b4
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       GNU/GPL2
Address:            \?\usb#vid_80ee&pid_cafe'''#gnu#gpl2#'''{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State:      Captured
}}}
The guest os see the device as ""unknown device"" with PID and VID to 0. ",Egon
4605,Ubuntu Linux guest audio output slow and distorted,Linux,VirtualBox 3.0.2,2009-07-22T21:13:53Z,2020-04-22T17:03:35Z,2020-04-22T17:03:35Z,"There's some discussion in community forums related to this, but it doesn't go very far.  Couldn't find any similar report in Bugtracker.  Sorry if I overlooked.

This is an Ubuntu Linux 9.0.4 guest in Virtualbox 3.0.2 r49928 on a Vista SP1 host, a Presario C751 notebook.  Following initial installation of the guest, sound playback works well.  Only after shutting down the VM completely and then restarting will sound playback slow down with a commensurate lowering of pitch as though the clock is running slow.  Sound distortion such as ""chirping"" and stuttering may be evident as well.  The problem is temporarily repaired by reinstalling the Guest Additions and rebooting the VM (reboot only, don't shut it down!).  Having done that, audio playback is restored to normal and will remain normal between reboots of the VM.  Only after the VM is shut down will the problem recur.  The same problem occurred in V 2.2.4 r47978.  FWIW Video output seems to be affected as well.

A Windows XP SP3 guest does not seem to exhibit the same problem.

Using a VM for multimedia apps is silly, but what's amazing is how well it works when it works.  It's not the way to go, but even if you don't, Ubuntu, for example, makes sounds like the drumbeat figure when GDM is ready for login, the Ubuntu ""theme"" as GNOME comes up and other sounds such as error notifications and the like and it is irritating for them to be slow, off pitch and distorted.  More importantly, the fact that it sometimes works and sometimes doesn't implies an underlying problem that may be more significant.

If I can, I will dissect the Guest Additions installation and try to determine what seems to ""fix"" the problem.",Larry Shurr
4626,PPPoE fails over bridged HP8510w 4965AG WLAN card,Windows,VirtualBox 3.0.2,2009-07-26T10:28:40Z,2018-11-08T23:11:59Z,2018-11-08T23:11:59Z,"I have a problem where I have a host machine, an HP8510w laptop with an intel 4965AG WLAN card. I am running Vista 64 Ultimate (same problem with Win 7 64 RTM) with a guest machine running Windows XP Sp3. The most important aspects of this setup is that the guest machine is set to be bridged to my WLAN card (Intel 4965AG). I am using static IP's with a router.

After the Guest OS is installed, I have configured an IP address. I can ping the router from the Host OS and I can also ping the router from the Guest OS. All other aspects of networking seem to be working. (I do not use DHCP purely because of my network setup but I feel this is unimportant).

I have several PPPoE accounts and a router that is in bridge mode. When I try to initiate a PPPoE connection in the Guest OS (WinXP), PADI packets leave the guest machine, go through the bridged network, reach the router. The router then sends a PADO response which can be seen on the Host OS and is also passed on to the Guest OS.

Unfortunately, the Guest OS is ignoring these packets as the target MAC address does not seem to be for the Guest OS (Which is understandable, but surely the bridging driver/service installed on the Host OS NIC is supposed to correct this?)

This seems to be a problem with the bridging driver/service for VirtualBox. This may not be of any concern to you, but the problem also exists in VMware Workstation. This is not a problem for Microsoft Virtual Machine though.

I have discovered a slight workaround. If I set the MAC address of the virtual network card in the guest to the same MAC address of the Host OS WLAN card, the PADO packets are relayed and it now works. Unfortunately, this causes other problems with Linux Guest's trying to use the same workaround and I cannot use this solution permanently.

I have attached the Vbox.log, as well as two wireshark captures from both the host and the guest machine.",Kinnoken
4656,USB device is busy with a previous request,Linux,VirtualBox 3.0.2,2009-07-30T12:38:29Z,2017-09-27T15:32:17Z,2017-09-27T15:32:17Z,"Windows XP host and Fedora 11 guest. After a crash while transferring a huge amount of files between the pen drive and the Fedora guest, the pen drive becomes unavailable. When clicking Devices -> USB Devices -> Device Name this message is shown:

""Failed to attach the USB device xxx to the virtual machine Fedora 11
USB device xxx with UUID yyy is busy with a previous request. Please try again later.

Details:

Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDevice
Interface: 
IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: 
IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}
""

Forum discussion topic:

http://forums.virtualbox.org/viewtopic.php?f=6&t=20744&start=0#p89540",Clodoaldo Pinto Neto
4862,"Files in shared folder which open in mode ""w+b""(Linux guest) could not be read(Protocol Error)",Linux,VirtualBox 3.0.4,2009-08-27T02:25:21Z,2017-02-25T16:48:42Z,2017-02-25T16:48:42Z,"I am using a python programe(ZODB) to read file's content in shared folder.But I got a [IOError]Protocl Error when I run the programe.And I check out the source,found that ZODB open this file in ""w+b"" mode.I write a very simple test programme(also python),and got the same problem.Here is the source:
{{{
#Test programme
f = open(""Data.fs"",mode=""w+b"")
f.read(10)#got error here
}}}
Data.fs is the file in shared folder.I also test in mode ""r+b"",it's ok for both write and read.",Yao
4682,"Remove ""Create Quick Launch Icon"" from installer on Windows 7 and above",other,VirtualBox 3.0.4,2009-08-05T09:31:40Z,2011-03-01T08:52:41Z,2011-03-01T08:52:41Z,"Since ""Quick Launch"" has been removed from Windows 7 and is unlikely to return in future builds of Windows, creating a quick launch icon should not be offered on Windows 7 an above. This is merely a cosmetic issue as this option has no effect on Windows 7 but should be fixed eventually.",Frank Freibuth
4876,A duplicate name exists on the network - Windows Error,Windows,VirtualBox 3.0.4,2009-08-29T19:48:01Z,2011-02-20T22:58:44Z,2011-02-20T22:58:44Z,"VirtualBox Guest has problems with DHCP leases managed by ASUS Wireless Router RT-N11 (host connected by cable).

Guest does the DHCP has grabs an IP address although it is not accessible by the network name, only by IP address.

See images attached.",XoK
4744,Windows host and guest drives should be WHQL certified (Windows logo testing),Windows,VirtualBox 3.0.4,2009-08-10T22:30:43Z,2010-05-28T20:25:00Z,2010-05-28T20:25:00Z,"Just upgraded VB from 3.0.2 to 3.0.4 on Windows XP. Upgrading the guest additions failed with the error that the driver for the VirtualBox Graphics Adapter has not passed Windows Logo testing to verify its compatibility with Windows XP. I've tried uninstalling the previous guest additions and get the same error.

The host is also XP.

The guest is configured with 16MB of video RAM with 3D Acceleration disabled.",John Clayton
4934,Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running,other,VirtualBox 3.0.4,2009-09-09T08:12:04Z,2010-05-24T12:31:28Z,2010-05-24T12:31:28Z,"Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running.

Windows Vista Business 64bit host SP2

I have 3 VLANs on an Intel PRO/1000 MT Desktop Adapter lan card.
I have installed the Intel Proset drivers for the NIC v14.3
They enable me to have each VLAN with its own virtual NIC in the form of for example: Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN2018 (The only way to use VLAN in Windows I know of)
If I start a virtual machine bridged to one of the Virtual VLAN NICs it is OK, everything is working
I can also start more virtual machines bridged to the same Virtual VLAN NIC
But the problem is when I try to start a virtual machine bridged to a different Virtual VLAN NIC,
 while those VMs bridged to first Virtual VLAN NIC are still running.

I get a crash with message: VERR_INTNET_INCOMPATIBLE_TRUNK

I tried Virtual Box version 2.2.4-47978 and also latest beta 3.0.6_BETA1-51790 still the same
The only difference is that 2.2.4 locks up hard after a couple of VLAN crashes and I need to reboot my host.

For example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
start VM3 bridged to VLAN2 - CRASH!!!

Other example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
stop VM1 and VM2
start VM3 bridged to VLAN2 - OK
",Boris
4763,Cross-PC Clipboard Data Exposure Using Remote Desktop into Guest,Windows,VirtualBox 3.0.4,2009-08-12T22:24:34Z,2010-04-13T12:51:35Z,2010-04-13T12:51:35Z,"I discovered what I would consider a data security exposure (at worst) or (at best) an undesirable function of clipboard copy/paste. I have an XP guest (running on a Vista host, but I don't think the host platform matters). Let's call the XP guest GUEST1 and the Vista host HOST1. Often, using another plain standalone XP PC (not running VirtualBox) -- a separate physical PC on the same network that we'll call PC1 -- I will use Windows Remote Desktop from PC1 to access GUEST1 remotely. If I copy text in the Remote Desktop session from PC1, the next paste operation on HOST1 results in pasting the data that was copied from the Remote Desktop session on PC1 (obviously by way of GUEST1).

The data copied to the clipboard should have remained only on the physical PC on which is was copied, in this case PC1 which isn't even running VirtualBox.

This becomes a problem when a separate user on another computer is remotely accessing a guest. This is actually how I discovered the problem as undesirable data was appearing in my host clipboard while someone else was remotely accessing my guest. They could be copying sensitive data, which should not appear on the host clipboard.

This is an easy scenario to recreate on demand. I have verified that this scenario happens in 3.0.4 and as far back as 3.0.0, possibly earlier as I have been having unexpected data appear in my host clipboard for some time.",Christopher Makris
5104,VirtualBox taskbar item flashing for no reason (or reason not apparent),other,VirtualBox 3.0.6,2009-10-02T15:18:07Z,2019-06-21T08:02:39Z,2019-06-21T08:02:39Z,"The guest isn't doing anything, no CPU or disk activity on Windows XPsp3 or Ubuntu Guests with a Windows XPsp3 host but the actual window for that guest starts flashing in my taskbar, given enough time all of the running windows are flashing and it's just plain irritating :-p.

I open the window to expect some important message and nothing. I'm not sure what's causing it to flash or what it's altering my attention to but eventually it gets to me and I have to open it just to stop it.

",Chris
4956,Installer fails with error 1603,Windows,VirtualBox 3.0.6,2009-09-11T16:49:56Z,2015-06-05T09:14:31Z,2015-06-05T09:14:31Z,"Trying to install version 3.0.6 on Windows Vista.
After all the confirmation the installer starts. But after seconds the scrollbare runs back and an error is showed:

Virtual Box Installer
Installation of MSI failed
Error: 1603

",Nagi
4961,Mouse wheel scrolling broken in Ubuntu 32 bit guest / Windows 7 host since 3.06,Linux,VirtualBox 3.0.6,2009-09-12T08:47:08Z,2009-10-06T21:50:56Z,2009-10-06T21:50:56Z,"Subject says it all really - since upgrading to 3.06 I can no longer use the mouse wheel to scroll in an Ubuntu guest.

Ceri",carlill
5122,Can't access shared folder without login on Windows 2003,Windows,VirtualBox 3.0.6,2009-10-05T12:47:20Z,2009-10-05T12:47:20Z,2009-10-05T12:47:20Z,"Try to access shared folder from autorun service (not with !LocalSystem account but a User account) using net command or UNC but doesn't work until someone login and must maintain login for the access to work.

Issue mentioned in thread:
http://forums.virtualbox.org/viewtopic.php?f=2&t=22032
",Cplaisstw
5076,Keyboard go crazy (miss map) after screen turn off and come back,Linux,VirtualBox 3.0.6,2009-09-25T01:35:08Z,2009-09-25T08:20:58Z,2009-09-25T08:20:58Z,"I just install the latest Virtualbox yesterday and i observed a very strange behavior. Below is the details description:

Virtualbox version: 3.0.6
Host: Windows 7 Pro RTM
Guest: Ubuntu 9.04
using seamless mode
Setting on Windows 7 to turn off the screen after 5 min (not sleep)

- Basically the problem is causing the host keyboard catching to go crazy. 
- Seem like the window key (special key) is lock up, so no matter what key i pressed, even is a single key (such as ""y"") but in the host window it seem like (window key + y).
- I try using VMware unity, it did not seem to have this problem. So i guess it is a bug. Has this bug being reported?",ntyonline
5064,"Mouse I-pointer and crosshair pointer disappears when using Guest Additions (Vista host, WinXP guest)",Windows,VirtualBox 3.0.6,2009-09-23T13:48:47Z,2009-09-23T13:48:47Z,2009-09-23T13:48:47Z,"I'm using Windows Vista as my host and Windows XP as my guest. When I'm using VirtualBox Guest Additions and mouse pointer integration is enabled, the regular mouse pointer appears ok, but when I move my mouse within the guest to a textbox, or to a window which is supposed to change into a crosshair pointer, the mouse pointer disappears on those areas. When I move out of the affected areas, the regular mouse pointer appears. The other mouse pointers, like the hand pointer when selecting a hyperlink, and the hourglass pointers appear fine.

When I disable the mouse pointer integration, all pointers are working perfectly. However, I'd like to have the mouse pointer integration enabled as I would have difficulty moving from an application in my host and an application running in the guest (I have to hit Right-Ctrl every time.)

Using the same VirtualBox version on a Linux (Ubuntu Jaunty) host and the same Windows XP guest, I did not experience this problem.

",Jake Catayoc
5252,Intel vt-d/AMD IOMMU support,other,VirtualBox 3.0.8,2009-10-19T07:29:51Z,2012-05-20T13:58:21Z,2012-05-20T13:58:21Z,"I want to use the pci-e inside the guest os to accelerate the directx and opengl but virtualbox still not support it
and I found that intel vt-d can use the host pci-e in parallel workstatio 4.0 

Hope to support this in future version.",vizio
8991,Virtualbox breaks virtual machines if the host dies unexpectedly,Linux,VirtualBox 3.0.8,2011-05-30T19:50:14Z,2011-05-30T19:50:14Z,2011-05-30T19:50:14Z,"If a virtual machine is running and the host shuts down unexpectedly from processor overheating, BSoD or power failure, about 50% of the time, it breaks the VM.
It breaks the actual settings file and not the HD image.
Sometimes it shows
----------------------------------------------------------------------------
Could not load the settings file 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml'.
Premature end of data in tag VirtualBox line 3.
Location: 'C:\Users\XXXX\.VirtualBox\Machines\Debian\Debian.xml', line 77 (3), column 5.
Result Code: 
VBOX_E_XML_ERROR (0x80BB000A)
Component: 
VirtualBox
Interface: 
IVirtualBox {3f4ab53a-199b-4526-a91a-93ff62e456b8}
---------------------------------------------------------------------------
And sometimes it hangs for no apparent reason when trying to start of modify the VM.
I can create a new VM with similar settings and reattach the disk image and it works fine but this is an annoyance. The VMs seem excessively fragile.
BTW I just realized I am using a very old version.

",smeezekitty
5308,vrdp with resistive touchscreen tablet pc,Windows,VirtualBox 3.0.8,2009-10-28T14:10:43Z,2009-12-01T17:59:01Z,2009-12-01T17:59:01Z,"Hello,
I just dug this out of the forums, realizing that after all this time; I've had it in the wrong spot.

I just bought a tablet (slate) WinCE pc with a 10"" resistive touch screen. I can connect to virtualbox with vrdp and it looks great, and the response times are great, but I have one issue. With the touchscreen, I have to touch twice to click (once to move the mouse to the desired location, again to click) or hold it for like a second. This makes double clicking impossible. Although, I can use the hard navigation buttons just fine. Using the Microsoft's RDP on the guest works perfect, so I am believed to it bieng virtualbox.

I am hoping to use the tablet for interacting with MS PowerPoint that is being displayed fullscreen on a projector simultaneously. It doesn't matter if mouse integration is enabled or not.

I have:
Host: win7 x64
--CPU: i7 920
--Memory: 6 Gb 
Network: Host - ethernet - wireless router - wifi (802.11g w/ excellent signal) - tablet
Guest: Win XP Pro Sp 2 tablet edition
--VB version: 3.0.8; additions: installed
--mouse integration: on and off
tablet: viewsonic v210 WinCE 4.2
--RDC v5.1 settings:
----Display: 256 color (lowered to see if it would help, didnt)
----Local resources: Sound: leave at remote; local dev: none checked
----Experience: Performance: Custom (none clicked, to test, didnt help)


there is no crash, so i dont believe a log file is needed.",silverhawk_184
5732,Many executables refuse to run fom Shared Folders,Windows,VirtualBox 3.1.0,2009-12-11T22:30:13Z,2019-12-27T16:03:57Z,2019-12-27T16:03:57Z,"About 50% of all Windows executables refuse to run from Shared Folders (vboxsf).

The same executable work perfectly from mounted SMB shares.

Host: Windows XP, Core 2 Q6600, VBox 3.1.0

Guest: Windows 7, 64-bit.

-Technologov, 12.12.2009.",Technologov
5652,Bridge network driver breaks host network DHCP,other,VirtualBox 3.1.0,2009-12-03T05:04:16Z,2009-12-03T05:06:41Z,2009-12-03T05:06:41Z,"Installing VirtualBox with the bridge network driver installed prevents the host machine from getting DHCP responses.  However, this issue only comes up after I reboot the host computer.  Here are the steps:

1.  Install VirtualBox.  Install completes successfully.  VMs run properly and can access the network.  Host networking works properly.  I can release my DHCP lease and acquire a new one successfully.

2.  Reboot the host computer.  Host is now unable to get DHCP responses and thus the IPv4 stack is not configured properly.  Interestingly, IPv6 is working properly.  The host is able to automatically configure its IPv6 address.

3.  Uninstall VirtualBox.  As soon as VB is uninstalled, the host gets the DHCP response and IPv4 works again.

I've had this issue since VB 3.0.10 at least.  I did not have the issue in 3.0.2.  I didn't install any versions between them.

Host is running Windows 7 Ultimate 64-bit.  It is an upgrade from Vista Ultimate 64-bit.  I had the same issue in Vista as well.  Several guests including Gentoo Linux and FreeBSD.  Although it doesn't appear to be a guest issue.

If I don't install the Bridge Network driver, I don't see the DHCP problem.  I did have Juniper Networks VPN installed.  I un-installed it, but it didn't help the problem.  I don't know if the un-install left any lingering drivers behind though.

I see from the DHCP server logs that the server is getting the DHCP query and is sending a response.  But the Windows box is clearly not getting the response.  Including 'ipconfig' output.",Ryan Moore
5828,Unable to restore VM's saved state,Windows,VirtualBox 3.1.2,2009-12-23T15:30:06Z,2016-05-18T08:10:31Z,2016-05-18T08:10:31Z,"Information duplicated from this forum post: [http://forums.virtualbox.org/viewtopic.php?f=6&t=26019&p=116632#p116632].

With 3.1.2 and snapshots taken since installing 3.1.2, I get the following when restoring from a saved state:

    00:00:06.170 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
    00:00:06.419 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_REC_TERM_CRC)} aWarning=false, preserve=false
    00:00:06.420 Power up failed (vrc=VERR_SSM_INTEGRITY_REC_TERM_CRC, rc=E_FAIL (0X80004005))


When discarding saved state information, I'm able to start the machine without issue. Restored to earlier snapshot and am able to save and restore states without issue.

I'm seeing this on two different XP VMs. Have not tried to take a new snapshot of my Ubuntu VM yet, but did notice that when attempting to take a snapshot of one of my XP VMs that was powered off, the VBoxGUI crashed.",Wipeout
6057,[feature-request] Installer: warn users for incompatible drivers on Windows host,other,VirtualBox 3.1.2,2010-01-22T10:11:14Z,2013-08-21T20:53:02Z,2013-08-21T20:53:02Z,"
I see there are some instances where vboxdrv or vboxnetflt drivers are incompatible with currently installed 3rd party drivers on Windows Host platform.

It would be better, especially for newbie users, if we detect such incompatibilities in our installer, and warn users.

Here is the known list: (and perhaps a few more that I overlook)

#3752 DNS protocol problem with Vista hosts => check Shrew Soft Lightweight filter rules

#5519 vboxnetflt: fatal BSOD installation on Marvell Server NIC

#3370 VBoxNetFlt: Conflict with the Trend Micro Anti-Virus driver

#3724 Host crash: vboxdrv crashes, when run together with coLinux

Other incompatible software:

-decndis.sys caused the crash on one user. decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX (reported by Huihong Luo of VMlite)

-Microsoft VirtualPC

-Microsoft Hyper-V

The same issues applies to Linux-host installer too, but since installers are platform-specific, it deserves a separate wish.

-Technologov, 22.1.2010",Technologov
2928,Make time sync time function of the Guest Additions optional,Windows,VirtualBox 3.1.2,2008-12-30T20:08:44Z,2010-06-11T08:26:34Z,2010-06-11T08:26:34Z,"I don't want the time of the guest OS auto-synced by the Guest Additions, but still wish to use other features of it.

Could this function be made OPTIONAL?",helehele
6093,Deleting a snapshot when the underlying vdi files are readonly,Windows,VirtualBox 3.1.2,2010-01-29T14:53:58Z,2010-01-29T14:55:37Z,2010-01-29T14:55:37Z,"If you make a VDI file for a snapshot on disk read only to protect it against unexpected modification and then try and delete a snapshot which results in merging on the read only VDI, the snapshot dissapears from the UI but it fails to complete since the file is read only. You can't try again though since the snapshot has gone from the UI.

I.e.

A  <--Read only
|-B  <-- Read only
  |-C

Then delete snapshot B, when it tries to merge to give you A->C it'll fail, however the UI shows B missing now and you end up having to delete all snapshots and reverting back to the base disk.

If the merge operation fails then the snapshots in the UI should be left untouched.",Robert Garfoot
6314,Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER) on restoring from saved state,Windows,VirtualBox 3.1.4,2010-03-02T16:46:05Z,2019-04-15T08:45:31Z,2019-04-15T08:45:31Z,"On restoring machines from a saved state, I regularly get the error:

Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER)

This occurs after the progress bar for the restore has reached 100%. It does not happen every time I try and restore a machine, but once it does happen, it will happen every time I try and restore that particular machine until I discard the saved state. Therefore, I suspect the problem is occurring while saving the state.

Both host and guest are Windows 7 64-bit. I have yet to experience this on other guest operating systems, but I have not used saved state on other guests as much as the Windows 7 ones, so that may be pure chance.


",Ravenous Bugblatter Beast
6236,"USB device ""cannot start"" after installation",Windows,VirtualBox 3.1.4,2010-02-18T14:27:48Z,2017-03-31T14:31:13Z,2017-03-31T14:31:13Z,"Host:
  - Windows 7 Professional

Client:
  - Windows XP SP3 Professional

Synopsis: 

USB smart card reader (ACS ACR80) gets recognized in client, but when the driver installation finishes, Windows XP reports the following error:

""The device cannot start. (Code 10)""

I tried rebooting both host and client, then disabling EHCI (USB 2.0) but it made no difference.

In general, USB devices handling in VirtualBox is very tricky and far for perfect. I believe this aspect of the functionality requires far more attention in the future releases.

I like how elegant USB handling is in VMware Player, but I still prefer VirtualBox for many other reasons.
",Dragan Obrenovic
6358,Add official support for running as a service,other,VirtualBox 3.1.4,2010-03-11T11:28:42Z,2012-02-27T16:31:41Z,2012-02-27T16:31:41Z,"Hi
In my opinion the only reason that a lot of users (including me) cant really get virtualbox to work as they want is because of lack of running VB as a service( the very same thing that Virtual Server for microsoft has ). we really need to be able to run VMs before logging in and shutting them down automatically when the system is shutting down. of course they are some tricks around already but they are all really messy and have a lot of issues. i think adding this ability could make a lot of users happy and make the virtual box the best virtualization software ever.",Hamy
6178,[feature-request] Installer: Please introduce internal checksum,other,VirtualBox 3.1.4,2010-02-12T23:36:09Z,2010-02-15T15:05:21Z,2010-02-15T15:05:21Z,"Some users, including me, experience bad downloads from time to time... which results in broken VBox installation.

Please introduce internal checksum, so installer won't proceed if it was damaged during download or by virus.

I had this problem on Windows hosts; Not sure if this is applicable to other hosts...

Similar issue: Bug #6177

-Technologov, 13.2.2010",Technologov
6579,Cannot get a bridged network connection on guest OSes via a WPA2 wireless network with MSCHAPv2/PEAP authentication,other,VirtualBox 3.1.6,2010-04-22T21:58:37Z,2020-01-28T17:49:10Z,2020-01-28T17:49:10Z,"I have WinXP SP3 as a host OS.  I have used XP SP3 and Ubuntu 9.10 as guest OSes.  The problem appears to happen when I am conencted to a WPA2 wireless network with PEAP/MSCHAPv2 authentication.  The guest OSes do not get an IP address.  On the Windows guest, I get a private IP.

When I try this with networks with no PEAP/MSCHAPv2 authentication, this problem doesn't happen as I am able to get IP addresses for both guest OSes.

There was also a discussion on the VB forums where I discussed this:  [http://forums.virtualbox.org/viewtopic.php?f=6&t=30093]

Please advise.  Thanks.",prefection9791
6510,Timed Default Option When Close Is Detected,Windows,VirtualBox 3.1.6,2010-04-08T17:18:59Z,2014-01-02T22:22:20Z,2014-01-02T22:22:20Z,"Currently, when VirtualBox detects a close request (i.e. the system sends one or the the clicks on the close button) it brings up the Close Virtual Machine dialog box and waits for a response.  It would be useful to have the ability to select one of the three options as a timed default.  IOW, if the user didn't respond within n seconds VirtualBox would execute the default selection.

This would provide a way to gracefully close a VM when the host initiated a logoff or a shutdown while the user was not at the machine.
",Stewart Berman
6547,"Cancelling ""Add host-only network"" causes ""Unknown device"" to be created.",other,VirtualBox 3.1.6,2010-04-18T12:06:27Z,2010-04-19T10:08:34Z,2010-04-19T10:08:34Z,"How to duplicate:

 * Click File->Preferences...
 * Select Network page
 * Click the ""Add host-only network"" button
 * When the ""Hardware Installation"" dialog for ""!VirtualBox Host-Only Ethernet Adaptor"" appears, click the ""STOP Installation"" button.
 * If you then look at the Windows Device Manager, under Network Adaptors, there is an ""Unknown device"" entry that cannot be uninstalled.
 * When Windows is rebooted, it starts the ""Found New Hardware Wizard"" for the unknown device called ""Net"".  It keeps doing this every time Windows is rebooted.

!VirtualBox should really detect that the installation of the network driver was stopped by the user, and clean-up the Unknown device.

Tested on Windows XP SP3 (32-bit) host.

A related ticket is #4257.",gonk23
6829,"Network Adapter dialog allows to select Bridged Adapter, that is not installed, but actually doesn't set this setting",Linux,VirtualBox 3.2.0,2010-05-28T14:18:53Z,2010-05-28T14:18:53Z,2010-05-28T14:18:53Z,"I have VirtualBox already installed. But it was installed without VirtualBox Networking. I tried to change network settings of the virtual machine by clicking on the icon in the bottom of the window. The next dialog offed me to select Bridged Adapter (though it is not installed). Then I press Enter and it allows me to select this adapter. But when I press the icon once again, adapter is not attached.",r75a7
6815,Dual Monitors in full screen doesn't focus when dropping windows into other screen,Windows,VirtualBox 3.2.0,2010-05-26T14:24:41Z,2010-05-26T14:24:41Z,2010-05-26T14:24:41Z,"When in Full Screen mode and Guest OS having 2 Virtual Monitors, moving 1 window to another screen requires an additional click to have the focus on what should already have a focus (i.e. to drag the window back to the other monitor, I'd need another click to focus the ""window/screen/monitor"" then I can click+drag. For completeness, I think this is a ""minor"" fault.  Fixing this will make it as seamless as a real dual monitor setup!",danf84
7756,Occasional Hang when saving machine state - data loss,other,VirtualBox 3.2.10,2010-11-23T12:14:02Z,2019-07-16T01:27:55Z,2019-07-16T01:27:55Z,"Hi there.

Occasionally Virtualbox fails to save the machine and hangs on 100% on the ""... Saving the execution state of the virtual machine""

I am forced to kill the VirtualBox.exe process. This unfortunately corrupts the attached virtual disk and often leads to any work done during that session to be lost.

Host Windows XP SP2",Nazar
4890,"Linux guest, ""mv -f file1 file2"" fails on shared folder without write permissions on file2 (Windows hosts)",Linux,VirtualBox 3.2.10,2009-09-01T12:28:38Z,2017-02-07T21:35:02Z,2017-02-07T21:35:02Z,"Test case:

touch file1 file2
chmod a-w file2
mv -f file1 file2

On the guest disk, there is no message whatsoever and file2 is replaced by file1. This is the behavior I expect.


On a shared folder pointing to a directory on the host's local hard disk drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': Operation not permitted


When the shared folder is pointing to a network drive, I get this error from the mv command and file1 remains:

mv: cannot move `file1' to `file2': File exists

",David
7736,SATA disks not found after reboot into linux (ICH9 only),Linux,VirtualBox 3.2.10,2010-11-19T10:25:07Z,2015-01-07T22:26:38Z,2015-01-07T22:26:38Z,"Situation:
 * I have a IDE hdd with a linux installation on it, as well as grub.
 * I have a IDE cdrom with an image of windows XP on it.
 * I have a SATA hdd with windows XP on it, or nothing

I want to boot the linux OS, which will determine if the windows XP partition is available and has booted correctly. If this is the case, a grub-reboot is issued to boot into windows XP once, otherwise the image is restored onto the HDD.
If I reboot from windows XP, the linux OS should do the above again.

On an actual machine, the procedure works without a hitch.

However after a reboot from windows XP to linux (Start | Shut Down... | Restart) the linux suddenly can't find the SATA disks.
dmesg has the following lines:
{{{
[    6.166426] ata1.00: qc timeout (cmd 0xec)
[    6.166426] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    6.516437] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   16.517619] ata1.00: qc timeout (cmd 0xec)
[   16.517619] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   16.517619] ata1: limiting SATA link speed to 1.5 Gbps
[   16.866406] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   46.866424] ata1.00: qc timeout (cmd 0xec)
[   46.866424] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   47.216399] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   47.566424] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   52.566425] ata2.00: qc timeout (cmd 0xec)
[   52.566425] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   52.916425] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   62.916398] ata2.00: qc timeout (cmd 0xec)
[   62.916398] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   62.916398] ata2: limiting SATA link speed to 1.5 Gbps
[   63.266424] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   93.266437] ata2.00: qc timeout (cmd 0xec)
[   93.266437] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   93.616439] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
}}}
Attached is the full vbox.log and the full dmesg as I have it.",Mike Musterd
7761,additions install on Xen kernel,Linux,VirtualBox 3.2.10,2010-11-24T21:35:36Z,2010-11-24T21:35:36Z,2010-11-24T21:35:36Z,"Apparently, Linux Guest Additions are not working on Xen kernels. Unfortunately, I did not know about this limitation, because the Additions installer appeared to install OK. Sure, it installed OK, but should it even try to install?",Luci S
7646,Keyboard and mouseclick disabled at windows host with 'view login sceen at resume',other,VirtualBox 3.2.10,2010-10-25T08:56:34Z,2010-10-25T08:56:58Z,2010-10-25T08:56:58Z,"If I use VirtualBox without the Guest drivers installed, I am experiencing a problem when I leave the VBox window focused and then don't use my computer for longer than 10 minutes, the time I've set before the screensaver activates. Because I've set the computer to prompt me to log in again, it shows up the login screen. But except moving my mouse around, I can't do anything; Ctrl+Alt+Del, pressing the power button shortly, nothing works and my only option is to press and hold the power button...
For some reason the log isn't available via Ctrl+L, but I think the problem is clear; when the login screen appears, VirtualBox is still stealing my keyboard and mouse clicks. Best solution for this in my opinion would be that VBox checks whether the user is still logged in each few seconds, or that the keyboard focus stops when the screensaver at the host becomes active.",Vbug
7891,VBox doens't handle the user account correctly on Windows Hosts,other,VirtualBox 3.2.12,2010-12-23T10:37:26Z,2012-01-10T23:47:17Z,2012-01-10T23:47:17Z,"Host : Windows 7 Pro 64 bits

Context : VBox is called by a PowerShell script. At development time, this script is run by me, manually. At production time, this script is run by a scheduled task or through an ASP.Net web interface.

I wrote a little PowerShell script to illustrate the defect:

{{{
""Windows 1: $([Environment]::UserDomainName)\$([Environment]::UserName)"" | Out-File ""out.txt""
""Windows 2: $([Security.Principal.WindowsIdentity]::GetCurrent().Name)"" | Out-File ""out.txt"" -Append

$vBox = New-Object -ComObject VirtualBox.VirtualBox
""VirtualBox: $($vBox.HomeFolder)"" | Out-File ""out.txt"" -Append
}}}

If the script is run manually by me, the result is:
{{{
Windows 1: <my domain>\robot
Windows 2: <my domain>\robot
VirtualBox: C:\Users\robot/.VirtualBox
}}}

To me, this is the CORRECT result.

If the script is called through the computer ASP.Net web interface, the result is:
{{{
Windows 1: <my domain>\robot
Windows 2: <my domain>\robot
VirtualBox: C:\Windows\system32\config\systemprofile/.VirtualBox
}}}

Here, the ASP.Net engine is setup with impersonation to enforce the user with the ""robot"", as shown with the 2 first lines, this works, so the VBox result is WRONG.

If the script is run through a scheduled task, the result is:
{{{
Windows 1: <my domain>\Robot
Windows 2: <my domain>\Robot
VirtualBox: 
}}}

Here again, the scheduled tasks enforces the user account to ""robot"", so here again, the VBox result is also WRONG.

I've found a tricky workaround to run from the web interface by backuping/copying VBox files from/to the robot/systemprofile accounts, so yes, really tricky.

For the scheduled task, as VBox returns nothing, I have no solution, until to hope to see this defect fixed.

Thanks.",Romuald Tisserand
7843,"VBox host-only network is reported as ""Unidentified Network"" and Public on Windows7 hosts",other,VirtualBox 3.2.12,2010-12-14T01:28:54Z,2010-12-14T01:28:54Z,2010-12-14T01:28:54Z,"I am configuring virtual machines that are using the host-only network interface to connect to the host machine.

My host OS is Windows 7 and its firewall operates by classifying which network adapters and networks are public vs. work/home.  Based on this classification, the firewall determines which interfaces allow service connections (e.g. cifs, http, etc.) and which interfaces do not.

The host-only network interface cannot be modified to change the network name nor network access type in the Windows ""Network and Sharing Center""  If I click on the network type (Work, home, public) of any other adapter, a dialog comes up that allows me to change the type and name.  If I click on the bench of the vbox host-only iface, then I get an immutable dialog that shows me a read-only textfield and no capability to change the network type.

Please fix this.  I do not want to install 3rd party firewall software, nor do I want to needlessly expose my box to public-network elements when I need VM guests to connect to my host.  A host-only network is arguably more ""private"" than a ""public network""",Perry
7791,"If disk images are on a shared storage(eg. samba), clients crashes if there is networking error.",other,VirtualBox 3.2.12,2010-12-04T16:37:19Z,2010-12-06T15:51:50Z,2010-12-06T15:51:50Z,"I keep all disk images in a samba share, and sometimes, If there is network problem, The guests fail constantly, Even if the share which contains disk images offline and go back within in a second, The guest fails(both windows and linux) still. Asked in #vbox channel, And finally the conclusion might be:

00:13 < lacqui> But honestly, the issue is that VBox is attempting to access a file that it assumes is constantly available
00:13 < lacqui> When there are network issues, that may no longer be the case.
00:13 < lacqui> VBox has the file open constantly.
00:13 < lacqui> I beleive that file pointers may be lost (on the OS level); I don't know if there is an application-level method of bypassing that
00:14 < xinming> Since the samba share returns again really soon, So I believe there may be a work around to detect this, and re-open the file.

Possible to fix this?
Or if this won't be fixed, Is there a way to prevent this situation please?

Thanks!
",yiyihu
7036,"""Check for update"" turned on, automatic vm start, when update available, access blocked",Windows,VirtualBox 3.2.2,2010-06-21T15:10:59Z,2010-10-17T23:27:46Z,2010-10-17T23:27:46Z,"Hi,

a very strange ""error"". Situation: 

- automatic checking for updates once a week is turned on
- vm is started automatically from batch with vboxmanage StartVM
- vm was restoring from Saved State, vm restored correctly
- VirtualBox update occurred

All started well, and there was a modal dialog notifying that there is an update, but wherever I tried to click, on OK button in dialog or inside the vm, Windows produce a sound ""you can't click there"". The vm was also not visible in Alt+Tab list.

The only way to was to force Save State with ControlVM.

",vlatko
6917,Feature request: Prevent guest resolution auto adjust,other,VirtualBox 3.2.2,2010-06-07T08:16:38Z,2010-06-07T08:16:38Z,2010-06-07T08:16:38Z,"Hello,
I'm using VBox Windows XP.
Coming out of full screen mode, the guest window is automatically adjusted to the guest's resolution.
Can this behavior be disabled?

For clarity, here is a detailed example:
I have a screen resolution of 1680x1050.
I set the resolution inside the guest to 1680x1050 (so that I can enjoy my full screen real estate when in full screen mode).
I resize the guest window to 100x100 pixels.
I go to full screen mode.
I come out of full screen mode.
=> The guest window doesn't retrieve its size of 100x100! Rather, VBox is trying to stretch it all over the screen to set its size to 1680x1050.
So, I have to resize it back to 100x100, manually.

Yes, if I enable Host+G, it will go back to 100x100 automatically when I come out of full screen mode, but it will also *change the guest resolution* (an even worse problem, because when I go into full screen mode again, all windows sizes and desktop icon positions in the guest are messed up)!

I hope this is clear. I need the guest resolution to never be touched AND the guest window to retrieve its previous size automatically when coming out of full screen mode (with scroll bars, if needed).

Also, a button to go to full screen mode would be nice, instead of having to navigate menus.

Regards.",ExpertNoob
7040,"Windows 7 host, VBox 3.2.4 cannot do bridged networking",Windows,VirtualBox 3.2.4,2010-06-21T23:21:05Z,2015-05-19T17:18:58Z,2015-05-19T17:18:58Z,"Upgraded from 3.1.4 to 3.2.4 on a Windows 7 Ultimate 64-bit host

Existing VMs would not start (E_FAIL). Checking the settings highlighted a problem with the network adapter.

The VMs all use bridged networking. The dropdown for the host network adapter to bridge was empty, and nothing could be selected.

Tried creating a new VM in 3.2.4, same problem - can't set network adapter to bridged networking, because I can't select a host adapter to bridge.

Downgrade to 3.1.8 - everything works as before.
",Mike Benson
7174,OS/2 Warp 4 Colors are wrong at 16 million setting,other,VirtualBox 3.2.6,2010-07-15T00:41:30Z,2016-01-18T16:16:17Z,2016-01-18T16:16:17Z,"Guest additions are working. When setting the resolution to 16 million colors, red and blue are reversed. Everything that is supposed to be blue, is red. Everything that is supposed to be red, is blue. Colors are right when using lower settings. ",Ron Schnatzmeyer
7260,VBoxTray.exe high CPU usage in RDP session,Windows,VirtualBox 3.2.6,2010-08-02T13:52:01Z,2016-01-04T12:49:43Z,2016-01-04T12:49:43Z,"Hi

version: 3.2.6
host: Windows Vista 32-bit
guest: Windows 2003 Server 32-bit (guest additions installed)

When connecting guest OS through Windows RDP (I mean not VirtualBox RDP) VBoxTray.exe loads CPU up to 100%. After killing the VBoxTray.exe process it's OK.

Regards, Almir",nalmir
7094,VirtualBox kills network connectivity if VLAN tagging enabled on Realtek NIC,other,VirtualBox 3.2.6,2010-06-30T23:46:16Z,2015-10-15T07:56:42Z,2015-10-15T07:56:42Z,"If VLAN tagging is enabled on the Realtek network card of a system with VirtualBox installed, and the ""VirtualBox Bridged Network Driver"" is bound to that network card (the default behavior), no network access is possible.  The only remedy is to either disable VLAN tagging or unbind the ""VirtualBox Bridged Network Driver"" and reboot the system.  The former is no remedy, because we use VLAN tagging (to the desktop) in our environment.  The latter remedy obviously means no network access for VirtualBox.  It would be nice if this issue could be fixed, as Microsoft HyperV does not suffer from this problem, and I'd much rather use VirtualBox.
{{{
Steps to reproduce:

1. Install the appropriate full Realtek NIC driver from http://www.realtek.com
/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
2. Install VirtualBox on a system with a ""Realtek PCIe GBE Family Controller""
3. Open the Network Connection Control Panel
4. Right-click ""local Area Connection"" and choose ""Properties""
5. Click Configure
6. Click Advanced
7. Under the ""Propery:"" list, select ""Priority & VLAN"" then, under the ""Value:"" list, select ""Priority & VLAN Enabled""
8. Click Start --> All Programs --> Realtek --> Diagnostic Utility --> Realtek Ethernet Diagnostic Utility
9. Select ""Realtek PCIe GBE Family Controller"" from the list on the left
10 Click ""VLAN"" (from the middle column)
11. Click ""Add"" and enter a VLAN ID (for a VLAN that actually exists on your network) and press <ENTER>
12. Confirm adding of the VLAN and close the Realtek utility
13. Check to see if you still have network connectivity.  If you do, reboot.
14. You should not longer have network connectivity.
15. Open ""local Area Connection Properties""
16. Uncheck ""VirtualBox Bridged Network Driver"" and click ""OK"".  Reboot
17. Now you should have network connectivity.

This problem is happening on a system with the following characteristics;

- Windows 7 64-bit
- Realtek Realtek PCIe Gigabit Etherenet NIC
- Virtual Box 3.2.x
}}}",viro
7211,Captured mouse pointer is not released with Right-Control keypress on Windows when Canadian Multilingual Standard keyboard layout is active,other,VirtualBox 3.2.6,2010-07-20T19:34:15Z,2015-08-27T16:01:32Z,2015-08-27T16:01:32Z,"Captured mouse pointer is not released with Right-Control keypress on Windows when Canadian Multilingual Standard keyboard layout is active

Reproduction steps:
 1. Use Windows control panel Regional Settings applet to add 'Canadian Multilingual Standard' keyboard layout and make it the default
 2. Start !VirtualBox
 3. Start a !VirtualBox guest OS which doesn't have Guess Additions installed
 4. Click in the guest window, observe mouse is captured
 5. Press Right-Control, observe that mouse is not released and remains captured.
",Jon TURNEY
7083,character encoding munged in CLI on Windows,other,VirtualBox 3.2.6,2010-06-27T13:41:42Z,2010-06-27T18:11:58Z,2010-06-27T18:11:58Z,"I must admit that I don't know if VirtualBox is to blame or Windows 7. I have an otherwise US English installation of Windows, but if I set the language in VirtualBox to French, for example, and create a virtual machine, it will name certain things in French. For example, the storage controller is called ""Contrôleur IDE"". However, when I use the VBoxManage showvminfo command it shows as ""Contr¶leur IDE"" (the o with a circumflex gets replaced by a paragraph mark). I have not tried to use the storageattach command yet with this improperly named/displayed controller name, but I suspect I would run into trouble. And, other than me guessing what the name is supposed to be because I know the language well enough, there does not seem to be a way to verify what the name is. If I named it something else more obscure using this apparently incompatible character encoding, I'd have no way to display what it is actually stored as. 

Also, descriptions or snapshot names are displayed wrong. The é (e with acute accent) is replaced by a ú (u with acute accent). This happens in both cmd.exe and powershell interfaces.

I wish everyone would just use UTF, but apparently someone here is not and doesn't realize that the other guy is not. I suspect Windows is to blame, but I'm not sure. In the graphical user interface, comments and names continue to appear correctly as I typed them or as they were automatically created if I switch from French to English. However, certain things like the name of the storage controller are not displayed in the GUI.

-Example-

.\VBoxManage showvminfo browse

Storage Controller Name (0):            Contr¶leur IDE

.\VBoxManage showvminfo WS2003R2-sctltest1

Storage Controller Name (0):            IDE Controller",$roman
7492,Need a progress indicator during Snapshot creation,Linux,VirtualBox 3.2.8,2010-09-17T14:38:51Z,2016-08-12T12:39:25Z,2016-08-12T12:39:25Z,"For a large VM with 5GB RAM, I tried making a snapshot of a live VM. The snapshot did not finish before 10 minutes and I could not wait any longer, so I canceled the snapshot (breaking my VM, see separate bug report http://www.virtualbox.org/ticket/6877).

I had no way of knowing when the snapshot would finish. Maybe it would have taken another few seconds... I don't know.

A progress indicator for snapshot making would be very helpful.
",BobO
7443,Guest Addition brakes mouse: instant scrolling instead of pointer movement,Windows,VirtualBox 3.2.8,2010-09-07T15:18:40Z,2015-06-04T19:15:50Z,2015-06-04T19:15:50Z,"Host OS: Win7HomeBasic

Guest OS: WinXP SP3

VBox version: 3.2.8

PC(Notebook): Samsung R519

After installation of the Guest Additions touchpad (and usb-mouse too) does not work properly in guest OS: any application that have scrollbars (tested on notepad, MS Office 2007, MS Paint) do constant scrolling down to the bottom of the document when touchpad is used or mouse is moved. The direction of the mouse's movement does not influence on the applications behaviour. It just scrolls down. Installation of the official touchpad drivers into guest OS does not help. The pointer does not react on any movement after the driver installation.
The mouse (and touchpad) worked fine before Guest Additons installation. Uninstallation makes mouse work back as well.
",zolotov
7546,Print Screen does not work on Windows XP if Virtual Box has Focus,other,VirtualBox 3.2.8,2010-10-07T16:20:37Z,2010-10-07T16:20:37Z,2010-10-07T16:20:37Z,"1. Open up Virtual Box and Paint on Windows XP.
2. Start up a virtual machine in Virtual Box.
3. Select the title bar for the virtual machine (so that it is the active window). You should not be in the VM's content area, but the VM should be the active window.
4. Press Print-Screen.
5. Go to paint and try to paste.
6. It fails.
7. Arrange the windows so that both Virtual Box and Paint are visible.
8. Make paint the active window (by clicking on its title bar).
9. Press printscreen.
10. This time it works. It should have worked at step 6 so steps 7-10 are a workaround.",davidVisitor
7476,2D Video Acceleration Error Message Should detect platform first,Linux,VirtualBox 3.2.8,2010-09-14T21:32:22Z,2010-09-15T06:53:51Z,2010-09-15T06:53:51Z,"'''Host:''' Windows XP SP3.[[BR]]
'''Guest:''' Debian Linux

'''Problem:'''  When selecting 2D Video Acceleration, the error message presentation priority is non-helpful.

'''Steps To Reproduce'''
 1.  Start !VirtualBox.
 2.  For your Debian Linux image, click Settings.
 3.  Click Display.
 4.  Set the amount of video memory to 16MB.[[BR]]
 ->  No message is displayed in the lower information pane.
 5.  Click Enable 2D Video Acceleration.[[BR]]
 ->  A message in the lower information pane appears stating that ""On the Display page, you have assigned less than 20MB of video memory which is the minimum amount required for HD Video to be played efficiently.""
 6.  Increase the amount of video memory to 20MB.[[BR]]
 ->  A message appears in the lower information pane stating that ""On the Display page, you have 2D Video Acceleration enabled.  As 2D Video Acceleration is supported for Windows guests only, this feature will be disabled.""

'''Expected behavior:'''  I would expect the system to warn me about how the option is only valid for certain guest operating systems first in priority, and then warn me about the HD video problem.  Thus, I would expect the Windows support for guests only message to appear instead of the HD Video warning.

'''Actual behavior:'''  One has to adjust video memory before discovering that the 2D Video Acceleration option isn't supported for non-Windows hosts.",Jon Polfer
7361,Windows XP UNC Benutzername und Passwort läst sich nicht über Ordner suchen hinzufügen,Windows,VirtualBox 3.2.8,2010-08-21T14:38:55Z,2010-08-21T14:38:55Z,2010-08-21T14:38:55Z,"Auf einem Windows XP Host, kann man bei einem ""Durchuschen""(Ordner suchen)-Dialog(Fenster) auch einen Netzwerkort angeben. Das ist UNC. Normalerweise dann, bei einem Datenzugrif auf diesen Ort, fordert dann Windows XP die Zugangsdaten per Fenster auf, ein zu geben. Jedoch wird bei dem ""Durchsuchen""-Dialog bei Virtual Box nur der Path-String ausgelesen und als lokale Adresse behandelt. Somit erkennt Windows nicht, dass es nötig ist, ein Fenster zu erstellen um die Zugangsdaten (Benutzername, passwort) eingeben zu können.

Jedoch könnte man die Funktion von Virtual Box umschreiben. So dass man da bei dem Fenster ""Gemeinsame Ordner"" gleich die Zugangsdaten mit angeben kann und diese dann entsprechend der Paramter-Syntax mit einer UNC-Connection Funktion übernommen werden.

So mit würde folgender Leistungs-Belastener Schritt nicht mehr nötig:

1. Netzlaufwerk zur Netzwerkquelle auf dem Host erstellen (net use).

2. Erstelltes Netzlaufwerk von Punkt 1, als Quelle bei den Gemeinsamen Ordnern (Virtual Box) eintragen.

3. Netzlaufwerk im Gast-Betriebsystem (Virtual Box Computer) erstellen (net use).",Ines
7972,Cannot install extension pack -- VERR_ACCESS_DENIED,other,VirtualBox 4.0.0,2011-01-02T01:03:11Z,2018-01-26T21:25:44Z,2018-01-26T21:25:44Z,"''Note: I have not attached a session log file as attempting to install an extension pack, predictably, does not appear to generate anything in the session log for a VM.  I have attempted the installation both without and with VMs running.''

I installed !VirtualBox 4.0.0 onto Windows 7 Professional and attempted to install the extension pack: '''Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack'''
The attempt failed with:
  The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED('G:\PROGRA~3\Oracle\VIRTUA~1/ExtensionPacks/Oracle_VM_VirtualBox_Extension_pack-_-inst-4100' -> 'G:\PROGRA~3\Oracle\VIRTUA~1/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack')

''a screencap of the error dialog is attached.'' (''NOTE: My boot drive (C:) is a small solid-state drive so I have the user account directories on my G: drive and install most software there as well.'')

As the error suggests ""access denied"" and the host is Windows 7, I immediately suspected UAC, however, I am not so sure of that now.  I searched the forums for anyone else experiencing the error -- I did find someone else and their error appeared to be identical to mine but, in their case, they have VBox loaded on a Windows XP host, so UAC seems an unlikely contributor.

I did verify that it seems to be actually creating the temporary directory (I did this by opening the !ExtensionPacks subdirectory in Windows Explorer and visually watching it as I attempted the installation -- a new folder appeared briefly then disappeared again followed immediately by the appearance of the error dialog).

I have verified that the MD5 checksum for the extension pack matches the one published on your website.  I can also open that file using 7-zip and it appears reasonable in format and content (as best as I can tell).

I tried installing the extension pack in as many ways as I could imagine: doubleclicking on the file itself; adding it using the preferences dialog in !VirtualBox Manager; running !VirtualBox manager both as an administrator and as a non-elevated administrative user; installing from an elevated command prompt using VBoxManage.exe; etc.  In each case the results were exactly the same.  I even tried rebooting my machine and then running the scenarios again.

Since it was suggesting an access problem, and knowing that Windows 7 has some restrictions on making modifications to the ""Program Files"" directory and subdirectories ( I am not sure exactly what those restrictions are but I know that in some cases things wind up in a virtual directory instead of the intended target) I tried a long shot and deleted the !ExtensionPacks directory then replaced it with a symbolic link to a directory I created in G:\Users\Public which had full access by the special user ""!EveryOne"" so there should not have been any access problems so far as I know -- the results were exactly the same as before so I reversed my changes.

I have checked the Windows Logs in the event viewer -- there are no application errors, system errors, nor security audit failures, corresponding to the failed installation.

I am pretty well tapped out of other ideas of things to try as workarounds.  If there is any other information you need please let me know.  Thanks in advance for any assistance you can provide in resolving this.



",Leslie Noland
8195,Shared folder error with long filename after snapshot restore,Windows,VirtualBox 4.0.0,2011-01-27T07:06:28Z,2017-02-28T13:18:45Z,2017-02-28T13:18:45Z,"- Snapshot created during running (WinXP) gast

- Snapshot restored (with vboxmanage startvm)

- Create an ordner on shared folders with more than 8 characters --> failes

- Access on files with more than 8 charcters in filenames failes

- Sometimes after a while (I don't know why and after which action), it is possible to access some longer filenames

- For Example:

  - Start Windows Explorer an try to create an (default) ordner.

  - It will be create ""ordn"" only, instead ""Neuer Ordner"".

- Hint:

  - An other program tell, the shared folder support only 8 standard characters.
",vbdevtest
7919,VM VirtualBox Manager GUI crash when deleting snapshot,Linux,VirtualBox 4.0.0,2010-12-27T13:54:39Z,2016-08-26T10:56:07Z,2016-08-26T10:56:07Z,"Host: Win7 x64[[BR]]
Guest: SLES 10 SP3 x64 w/o GA[[BR]]

Manager GUI crashes when trying to delete (merge) snapshot for running machine.[[BR]]
It is reproducible on new machine.[[BR]]
If snapshot has saved state it loses it before crash.
That VM and other ones are not affected and are running.",Alil
7968,Protocol error with junctions in shared directory,Linux,VirtualBox 4.0.0,2010-12-31T15:17:31Z,2016-03-21T16:14:42Z,2016-03-21T16:14:42Z,"Host: Win XP Pro SP3 32bit[[BR]]
Guest: Ubuntu 10.04 32bit

In a shared directory on the Windows host I have created junctions (aka ""reparse points"") to other directories. When using guest additions 3.2.12 these are treated as regular directories and the contents of the linked directory is shown.

With guest additions 4.0.0 (both versions tried in the same VM in VB 4.0.0) when I try to ""cd"" into one of the junctions, I get an error like
""bash: cd: Junction: Protocol error"" where ""Junction"" is the name of the junction.

",Michael Butscher
8038,Symbolic links in shared folders,Linux,VirtualBox 4.0.0,2011-01-08T19:37:48Z,2012-08-21T09:45:45Z,2012-08-21T09:45:45Z,"
Hi all !

Virtualbox 4.0.0
windows host, linux guest.

If I made with windows a simlink from folder c:\Documents to d:\shared_folder\documents... under linux this symlink doesn't works... is not accessible ( red color 0 byte )... linux can't access to c:\Documents.
In the past releases this kind of symlink worked.

For testing windows simlinks I used mklink from cmd line and a specific ( awesome ) program like Link Shell Extension (http://schinagl.priv.at/nt/hardlinkshel ... ml#contact ) that allow making different kinds of links... but nothing working...",Quaid
7895,multimon fullscreen mode is broken in 4.x,Windows,VirtualBox 4.0.0,2010-12-23T18:07:34Z,2011-07-31T11:15:48Z,2011-07-31T11:15:48Z,"Hello. Im using virtualbox 3.x without this problem at all.
I have 2 monitors running in dualview mode (so i have two separated desktops). First desktop is primary.

Virtualbox Manager GUI running on first monitor and guest VM running on second monitor.
now if i press <host>+F combination (goto fullscreen) my guest VM is switched to primary monitor! if i press <host>+F again, it will go away to second monitor.

I expect to see fullscreen mode on second monitor (that is working flawless in 3.x builds)
",ddn
8048,Restless Guest window's preview,other,VirtualBox 4.0.0,2011-01-10T06:18:14Z,2011-01-27T06:17:17Z,2011-01-27T06:17:17Z,"I noticed that the preview gets continuously updated while a VM is running,
which can be quite useless and CPU consuming.

I saw the preview can be disabled, but doing so involves loosing the possibility of seeing the last screen of a saved VM in the VirtualBox Manager.

I searched the manual looking for a way to '''have the preview updated only when closing down a VM''', but I did not find anything.",marcox
8011,VBoxManage/GUI does not detect VMs started by another user,Windows,VirtualBox 4.0.0,2011-01-05T17:02:28Z,2011-01-06T15:58:46Z,2011-01-06T15:58:46Z,"If a VM is started by the Windows Local System account (for example, if started by ""VBoxVMService""), then neither VBoxManage nor the GUI when executed by a regular user or administrator will show the VM as running. The status of a VM should be machine global and visible to all users.
",DavidN
9147,"After upgrading to 4.0.10 from 4.0.8 on windows 7 host network connection is permenantly lost, icon replaced by vurtualbox adapter icon",Linux,VirtualBox 4.0.10,2011-07-02T15:11:58Z,2011-07-15T11:50:15Z,2011-07-15T11:50:15Z,Running Windows 7 on a Toshiba L755D latop with 6GB of RAM.  Upgraded from 4.0.8 to 4.0.10.  After the install could not connect to the internet from windows (via wireless).  The standard wireless network icon in the systems tray was replaced by an icon which was reported as virtualbox adapter.  Opened networking settings to try and connect manually to the wireless but the virtualbox adapter could not be removed or disabled and the normal wireless connection was disabled and would not re-enable.  Uninstalled 4.0.10 and regressed to 4.0.8.,setheridge
9344,Snaphot deletion status window,other,VirtualBox 4.0.12,2011-07-29T15:54:47Z,2011-07-29T15:54:47Z,2011-07-29T15:54:47Z,"When you delete a snapshot, VB helpfully puts up a status window titled:
{{{
Machine: Deleting snapshot 'earlier':
}}}
Unfortunately the contents is:
{{{
Merging differencing image '{gah-internal-uid}'
}}}
Apart from the UID being fairly useless to the average user, it is also something that is not shown in the GUI itself, as the GUI only lists snapshot names.  So the average user has no idea what the UID is, or what it relates to.  The status window should use the snapshot name or some such.  

For example, if the snapshot following is called 'later', then:
{{{
Merging into snapshot 'later'
}}}
and if there is no later snapshot, then:
{{{
Merging into current state
}}}
",simon marshall
9211,Mouse pointer not correctly showed on guest when using multiple displays.,Windows,VirtualBox 4.0.12,2011-07-16T02:18:34Z,2011-07-16T02:18:34Z,2011-07-16T02:18:34Z,"When using multiple displays on host system - in this case, Windows 7 Professional - on a guest system running Windows XP the mouse pointer is not correctly mapped. In other words, you can't reach all window with one ""normal"" mouse pass: sometimes, multiple mouse passes have to be done with some speed to get the other side of the guest window.

This problem only occurs on Windows - only tested on XP. On a linux distro, it doesn't happen.

Solution: Place the guest window on the top left corner of the main display - if extended and the left one is the main one.

I'm available to provide more information on this issue.",haZard0us
10598,--timesync-set-on-restore syncs time up to 10 seconds after snapshot restore,Linux,VirtualBox 4.0.16,2012-05-24T13:44:54Z,2012-05-25T13:35:49Z,2012-05-25T13:35:49Z,"I have a Linux guest(additions 4.0.16) and a Windows host(vbox 4.0.16). The guest service is started via:
{{{
/usr/sbin/vboxguest-service -f -vvvvv --disable-vminfo --disable-cpuhotplug --disable-vmstats --disable-automount --disable-memballoon --timesync-set-threshold 1000 --timesync-set-on-restore 1
}}}

If I restore a snapshot of this machine, even one that is 7 days old, the time is not synced on restore.
~10 seconds (timesync-interval?) after resuming the VM, the vboxguest-service outputs ""The VM session ID changed, forcing resync."" and time is actually synced.

This causes trouble when working with certificates that are generated after taking the snapshot, so for some use cases this is really annoying.",insecure
8311,SATA AHCI Errors: READ FPDMA QUEUED,Linux,VirtualBox 4.0.2,2011-02-09T15:53:00Z,2021-08-23T04:41:22Z,2021-08-23T04:41:22Z,"My guest OS hangs periodically with a harddrive command error followed by an attempt to reset the HD (reproduced with Ubuntu and !ArcLinux). This issue does not occur in the host OS (Windows 7), only in the Guest OS.

Environment:

 * Ubuntu running in a Virtual Box 4.0.2 running on Windows 7 64bit.
 * Asus G53JW Laptop
 * Intel X25 SSD HD

Log excerpts:
{{{
Jan 17 14:48:32 vm kernel: [ 1513.120252] ata3: hard resetting link
Jan 17 14:48:33 vm kernel: [ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus
123 SControl 300)
Jan 17 14:48:33 vm kernel: [ 1513.471232] ata3.00: configured for UDMA/133
Jan 17 14:48:33 vm kernel: [ 1513.471241] ata3.00: device reported invalid CHS
sector 0
Jan 17 14:48:33 vm kernel: [ 1513.471255] ata3: EH complete
}}}
{{{
[ 1513.120200] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
[ 1513.120210] ata3.00: failed command: READ FPDMA QUEUED
[ 1513.120222] ata3.00: cmd 60/08:00:30:66:4c/00:00:00:00:00/40 tag 0 ncq 4096
in
[ 1513.120224]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4
(timeout)
[ 1513.120230] ata3.00: status: { DRDY }
[ 1513.120252] ata3: hard resetting link
[ 1513.470345] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1513.471232] ata3.00: configured for UDMA/133
[ 1513.471241] ata3.00: device reported invalid CHS sector 0
[ 1513.471255] ata3: EH complete
}}}",andornaut
8242,VRDP shows black screen on connection,Windows,VirtualBox 4.0.2,2011-02-01T22:13:40Z,2019-06-22T17:49:53Z,2019-06-22T17:49:53Z,"Windows XP 64 bit SP2 host, Windows XP 32 bit SP3 guest.

When I connect to a headless session via the Windows remote desktop client and the Virtualbox VRDP server, the display will be solid black. If no user is logged in. a blinking white cursor will display. If I start typing, the input fields and buttons of the login dialog will display with everything else remaining black. If I log in, the display will come up normally.

If there is a user logged in, clicking the mouse will cause a small square of the display to show. In this case, disconnecting and reconnecting will usually result in the display coming up correctly.",Russ Lehman
8324,Windows Host shutdown -any guests running stop windows from shuting down correctly,Windows,VirtualBox 4.0.2,2011-02-11T11:29:53Z,2017-09-13T19:46:44Z,2017-09-13T19:46:44Z,"Is there a way to improve the shutdown of guests on a windows host which is performing a shutdown / reboot.

the only way to reboot a windows host (ie for windows updates) is to use vboxtray which detects the reboot and auto-saves state of the guests...

I'm running 2 guests on a windows server which I can only get to remotely... as soon as I issue a restart (or windows udpates do) it kills my remote connection but the server is left hanging there as it cannot shutdown the guest's running on it. I end up having to get someone to manually click close / force reboot etc,etc to get the host server to shutdown / reboot.

the server can reboot / shutdown automatically for various resaons such as a UPS shutting the server down after a power cut...

as I say vboxtray manages to just about get round this by auto-save state but surely virtualbox host or guest apps could do with a settings that detects host shutdown (whether guest is in GUI or headless mode) and does a save state as a default and helps the windows host do a clean shutdown / reboot???


I have this problem on all version of VB since I started using it on 3.2.6 and I've tried it on different HOST machines - win xp pro, win 7 biz, server 2003 64bit.

Without vboxtray we wouldn't have a get round solution, which sort of works but I find that vboxtray sometimes closes on the tray so can fall over too sometimes.

can this be added as a feature request for windows hosts please

many thanks",Jimbo
8275,3D accelerated OpenGL 1.5 occlusion query support missing,Windows,VirtualBox 4.0.2,2011-02-05T03:14:20Z,2015-02-14T07:36:26Z,2015-02-14T07:36:26Z,"Host: Windows 7 Ultimate 64-bit
Guest: Windows XP Professional SP3 32-bit
3D acceleration: Enabled

The Windows XP guest reports the OpenGL version as ""2.1 Chromium 1.9"".
However not all OpenGL features up until OpenGL 2.1 are supported.
The following OpenGL 1.5 functions are missing: glBeginQuery, glDeleteQueries, glEndQuery, glGenQueries, glGetQueryObjectiv, glGetQueryObjectuiv, glGetQueryiv, glIsQuery. This means that OpenGL programs that expect full OpenGL 2.1 support may crash if it uses the OpenGL version string to determine whether or not it can use OpenGL 1.5 occlusion queries.

Attached is output from glewinfo which lists extensions that are present/missing.",Jonathan Liu
8477,Cannot use Windows clipboard when connected to host and guest via RDP,Windows,VirtualBox 4.0.2,2011-03-02T16:42:46Z,2011-03-02T16:54:48Z,2011-03-02T16:54:48Z,"Configuration:

Laptop:  Windows XP
Virtualbox Host: Windows 2003 Standard
Virtualbox Guest: Windows 2003 Standard

If I am connected to both the Virtualbox Host and Virtualbox Guest via RDP the clipboard fails to work.  Also it looks like it locks up the local application that I am copying from. 

For example If I copy something from either Excel or notepad and I want to past it into notepad on the VirtualBox host or any Windows Virtualbox Guest, the paste will not work and the source app will be locked until I either disconnect either the RDP connection to the VirtualBox Host or VirtualBox Guest.

If a RDP connection is open to only the VBOX Guest or VBOX Host it works fine.
",Shawn McCloskey
8282,Mini Toolbar/Quickbar unavailable if fullscreen changed to other host screen,Linux,VirtualBox 4.0.2,2011-02-05T22:51:59Z,2011-02-05T22:51:59Z,2011-02-05T22:51:59Z,"I am using 4.0.2 on Windows Vista host. (guest should be irrelevant, but is linux in case)

My host has 2 Monitors.
The guest has one Monitor, and runs fullscreen.

The mini-toolbar appears on the bottom of the screen.

If I switch (vie mini-toolbar ""view"" / ""virtual screen"" / ""use host screen x"" to the other host screen, then the mini toolbar will no longer appear, if the mouse is moved to the bottom-middle position.

Switching temporarily to window mode, and back to fullscreen fixes the issue (as a work around) until the next host-monitor switch",Martin
8148,Guest pre-boot check cycle of .vmdks with raw disks does not detect mismatch in drive geometry,other,VirtualBox 4.0.2,2011-01-22T15:39:56Z,2011-01-22T15:39:56Z,2011-01-22T15:39:56Z,"Hi! :)

I asked a question about this on the forums (http://forums.virtualbox.org/viewtopic.php?f=6&t=38285&start=0), and then did some testing to try to satisfy my concerns.

Issue at hand: If I have set up my VBox guest on a Windows host to access disks using raw device .vmdks, what will happen when I add a new controller, change BIOS drive order, remove a drive, or similar, which would cause Windows' \.\PhysicalDriveX links to point to physical devices different to what has been described in the .vmdks. E.g. that a 2TB physical disk is referenced to by a .vmdk describing the geometries of the 1TB disk that used to be at that PhysicalDriveX path.

<Copy/paste from my post in the forums>
First test:
I picked out two .vmdks, one pointing at a 1TB drive, the other pointing at a 2TB drive. I then switched them around, i.e. renamed them.

The ""Storage"" list in the main manager window did not pick up on this change. It still listed the ""old"" settings, i.e. the sizes for the previously corresponding \.\PhysicalDrive targets. However, upon booting, the OS report I/O errors on the drives in question.

This suggests that VB kept the geometry info from when the drives were attached, but read in the new \.\PhysicalDrive paths. Not good. Had I set up md and zfs already, I'm guessing this would not have been good for my data.

Second test:
I edited the two .vmdks to switch around physical drives.

Again, there's no update in sizes in the ""Storage"" list, and again, booting results in ""Buffer I/O error"" messages in logs and TTYs. No warning from VB.
</Copy/paste from my post in the forums>

With these raw disk .vmdks, VBox is spending quite a bit of time doing its checks before booting a VM the first time. I believe this time should also be spent comparing the geometries registered in the .vmdk with the actual, current, geometries of each drive, and when finding a mismatch either aborting (seems sane) the process with an error, or at least warning the user and blocking the boot until the user has determined what to do.

The way it works now, a broken power line to a drive could cause complete reordering of a list of drives upon reboot (possibly initiated automatically by the BIOS subsequent to a crash on behalf of the failing drive). If the VM is set to automatically boot, and ignores the discrepancies in geometries, you might find yourself starting RAID systems or ZFS pools on drives that have bad geometries and will I/O error out on everything, possibly causing severe data corruption.
",Daniel Smedegaard Buus
8147,Adding devices to virtual SCSI controller will use reserved port 7,Linux,VirtualBox 4.0.2,2011-01-22T15:21:28Z,2011-01-22T15:26:00Z,2011-01-22T15:26:00Z,"Hi! Fantastic work on VBox, thank you so much! I think the V4 is better than VMware :)

If this guy is right - http://forums.virtualbox.org/viewtopic.php?f=1&t=38319&start=0 - i.e. that the SCSI port 7 is reserved for the host adapter ID (or something more accurate, not a SCSI-savvy guy myself), then there's a bug in the interface when adding devices to the virtual SCSI controller. It will automatically assign the new device to port 7 when ports 0 thru 6 are already occupied, and you end up with missing devices in your OS (at least in my Ubuntu OS ;)",Daniel Smedegaard Buus
8698,VirtualBox Host-Only Network Adapter prevents multicast traffic,other,VirtualBox 4.0.4,2011-04-07T21:12:06Z,2020-06-28T14:04:55Z,2020-06-28T14:04:55Z,"After installing Oracle VirtualBox and VirtualBox installing the ""VirtualBox Host-Only Network"" on my Windows 7 64-bit machine, I am no longer able to receive multicast streams on the host machine. This problem occurs even when VirtualBox is not running.

To get around this issue, I have to go into Network Connections everytime I want to stream from a multicast source and disable the VirtualBox Host-Only Network adapter. I then have to remember to reenable it everytime I wish to use VirtualBox.",Michael Irigoyen
8564,WiFi network adapter,Windows,VirtualBox 4.0.4,2011-03-14T23:26:21Z,2014-08-15T23:28:14Z,2014-08-15T23:28:14Z,"Currently there are only wired network adapters available. A wireless adapter should be available too.

Some WiFi networks need a certificate to gain access. This certificate may (sometimes) only be installed IF a WiFi network is present and active on the (guest) server.

To allow for the VM guest to gain full access to a certificate controlled WiFi network, even thou the VM host does not, the VM guests need a network adapter of type WiFi.

",dum
8649,[feature-request] VBox Windows Installer should check for python version,other,VirtualBox 4.0.4,2011-03-29T06:57:13Z,2011-11-08T02:02:44Z,2011-11-08T02:02:44Z,"Host: Windows (all), VBox 4.0.4

VBox currently installs python bindings even on buggy python modules. (python 2.5.1 and pywin32 v213)

1. in ""vboxshell.py"" terminal colors on Windows Vista/7 must be disabled by default, and it is a known python bug, checking for python version fixes garbage on those platforms

2. We must check for pywin32 version. v213 is known to be broken. This fixes VBox bug #8605

We should refuse to install python bindings (gray out this option, or gives warning message), if python modules are old.

-Technologov, 29.3.2011.",Technologov
8606,Files remain installed and locked by Windows after uninstall or upgrade,other,VirtualBox 4.0.4,2011-03-21T20:32:27Z,2011-05-17T18:24:20Z,2011-05-17T18:24:20Z,"Upon upgrading from v4.0.2 to 4.0.4 I was unable to launch any VMs. I discovered that vboxdrv.sys, vboxnetadp.sys and vboxusbmon.sys were still from v4.0.2 and one of them was locked. Upon rebooting the machine and manually removing the files I was able to install 4.0.4 successfully.",Patrick Headley
8360,"when using existing ubuntu as a guest, vbox replaces xorg.conf",Linux,VirtualBox 4.0.4,2011-02-17T23:23:52Z,2011-04-13T13:39:34Z,2011-04-13T13:39:34Z,"I have a win7/ubuntu10.10 dual-boot. I installed virtualbox on win7 (host)
I followed these instructions http://chaits.accosted.net/?p=54 and created an instance out of an existing linux partition.
after I installed vb additions and extension, everything worked great in virtualbox. when i tried to boot into linux, the windows manager didn't lunch. xorg.conf was overwritten. 

Currently I have to sitch xorg.conf file manually if i want a graphical interface. 
i documented my experience [http://kirilligum.wordpress.com/2011/02/17/run-existing-linux-ubuntu-10-10-partition-in-virtualbox-under-host-windows-7-system-on-thinkpad-x201t/ here].",kirill
8597,"When connect to windows server guest by use Terminal Services, the VBoxTray.exe use half of my CPU",Windows,VirtualBox 4.0.4,2011-03-20T15:34:24Z,2011-03-20T15:34:24Z,2011-03-20T15:34:24Z,"Hi

I think I find a bug here:

I was try Windows Server 2003 SP2 on VirtualBox 4.0.4, and install the Terminal Services, and set the network to be Bridged.

Now when I connect the Windows Server by use Remote Desktop Connection, VBoxTray.exe will use half of my CPU.",vibbow
8551,DOS applications dosn't work with VBox Guest Additions shared folders,Windows,VirtualBox 4.0.4,2011-03-13T00:38:18Z,2011-03-13T00:38:18Z,2011-03-13T00:38:18Z,"Hello,

There is a problem with DOS applications working on folders shared through VBox Guest Additions.

The test configuration is:
  Host:  Win XP, 32-bit /problem also confirmed on Win7 64-bit host/

  Guest: Win XP, 32-bit

  Shared folder: 'D:\' on host shared as 'D'; Drive F: on the guest is mapped to \vboxsvr\D;
  
Problem: A DOS application running on the guest cannot find any file residing on a shared folder. The standard DOS FindFirst function call (INT 21/AH=4E) always fails despite there is files matching to the search criteria. For example FindFirst(""F:\Temp\*.*"") always got error is 0x12 (NO MORE FILES), but there are files in F:\Temp. Furthermore if you call GetExtendedError (INT 21/AH=59h) afterwards it reports error 0xEA which looks meaningless and unrelated to the error returned by FindFirst.

The problem occurs only if you are searching for files on a shares through VirtualBox Guest Additions. It's working correctly with classic SMB network shares.

I tested FindFirst for files on a network drive (e.g. drive 'G:' mapped to a network share) and it works. But if you map G: to \vboxsvr\some-shared-folder then you always got error as described above.

Another test by running 4DOS command shell on the guest shows similar behaviour (4DOS is a popular 16-bit DOS shell like COMMAND.COM). If you type ""dir F:\*.*"", where F: is mapped to \vboxsvr\some-shared-folder you see empty directory listing.

Described problem also appears also on a different machine with Windows 7, 64-bit host.",Dimitar Nanev
8485,Differencing disk created from multiattach base disk is marked as auto-reset,Windows,VirtualBox 4.0.4,2011-03-03T18:48:31Z,2011-03-03T19:08:39Z,2011-03-03T19:08:39Z,"According to the [http://www.virtualbox.org/manual/ch05.html#hdimagewrites VirtualBox] docs:
  ''Technically, a ""multiattach"" image behaves identically to an ""immutable"" image '''except the differencing image is not reset every time the machine starts'''.''

This doesn't appear to be the case.

I created a VM with a dynamically sized disk, installed Win7, sysprepped the VM and shut it down. I released the HDD and used '''VBOXMANAGE MODIFYHD ... -TYPE MULTIATTACH''' to mark this HDD as immutable and that children should not auto-reset.

I then created a new VM, using the base HD which created a differencing disk for its own data.

Using '''VBOXMANAGE SHOWHDINFO ...''', I examined the new VM's differencing disk and saw that it claims auto-reset is on.

I booted the new machine, completed the OOBE (Out Of Box Experience) and modified the desktop wallpaper. I shut down the VM and then rebooted it and was sent straight back to the OOBE again.

VirtualBox is a great product, but its poor handling of differencing disks, requiring users to delve around in the command-line tools to configure even the most rudumentary differencing scenarios, is, in my opinion, VirtualBox' biggest weakness, especially when compared to Hyper-V and VMWare.

PLEASE fix this bug and consider improving VirtualBox' GUI for handling differencing disks.",bitcrazed
8426,Unable to lock down VBOX COM using DCOMCNFG,Linux,VirtualBox 4.0.4,2011-02-24T19:59:23Z,2011-02-24T19:59:23Z,2011-02-24T19:59:23Z,"I need to install VirtualBox in an environment that permits only a special user (vboxuser) to control virtual box.[[BR]]
[[BR]]
The problem is that on Windows XP, locking down VirtualBox is not working (could be a windows bug), any user can launch with VBOXSVC and then have complete control over VirtualBox (if the set VBOX_USER_HOME properly). Windows 7 works fine (UAC on and off).[[BR]]
[[BR]]
[[BR]]
Here are the steps to lock down the COM service:[[BR]]
1- Install virtualbox under any admin user[[BR]]
2- Create a new user (vboxuser), make it an admin.[[BR]]
3- Login to vboxuser and start DCOMCNFG as admin[[BR]]
4- Select Component Services --> Computers --> My Computer --> DCOM Config[[BR]]
5- Locate VirtualBox then right click on open Properties[[BR]]
6- Select Security Tab[[BR]]
7- Change Launch/Activation to SYSTEM and vboxuser (local launch and activation)[[BR]]
8- Change Access to SELF,SYSTEM and vboxuser (local access)[[BR]]
9- Change Configuration to SYSTEM, vboxuser (full control)[[BR]]
10- Click OK and make sure that virtualbox.exe can start under vboxuser[[BR]]
11- logoff from vboxuser and then log back in to your user.[[BR]]
12- Start virtual box, and it starts! That is the problem.[[BR]]
[[BR]]
On Windows 7 you would get an error (Access Denied) and it would only work if I use runas /user:vboxuser virtualbox.exe.[[BR]]
[[BR]]
The problem happens only on Windows XP SP3 x86 (I haven't tested any x64 versions)[[BR]]
[[BR]]
I tested another COM service, and the permissions seem to work on Windows XP.[[BR]]
Please let me know if you have any questions[[BR]]
[[BR]]
I was able to reproduce this problem using VBOX 4.0.4 and VBOX-OSE 3.2.18 (self compiled/installed)",rbhkamal
8404,"window backup (wbadmin) restore error ""Cannot enumerate files"" if guestadditions installed.",Windows,VirtualBox 4.0.4,2011-02-22T20:00:27Z,2011-02-22T20:00:27Z,2011-02-22T20:00:27Z,"Guest Windows 2008 Server (32bit) as DC role. Guest edition 4.0.2 installed, 4.0.4 running. 

Perform windows full vss backup, with windows backup to attached disk.

Boot into DSRM and attempt a system state restore.

wbadmin start systemstaterecovery -version:xxxx -backuptarget:E: -authsysvol

Errors with ""cannot enumerate file""

If the guest edition is removed, a restore can be made.

Comments on the net suggest that this might be due to the path names of the vboxservice in the registry. However a brief examination of the service keys did not show anything unusual to my eye.



",John Huttley
8393,A way to define key-combinations which always are passed to the Host OS,Windows,VirtualBox 4.0.4,2011-02-21T18:37:36Z,2011-02-21T18:37:36Z,2011-02-21T18:37:36Z,"I commonly run certain utilities in my host OS which are useful whether I'm in the guest OS or not. I would like to be able to set up ""pass through shortcuts"" which always get passed to the Host.

For example the NextAction task list manager always activates with Windows+Z but I run it on my host machine. I would like to be able to set up virtual box so the guest machine does not capture Windows+Z.",George Mauer
8761,Silent failure to delete files on Shared Folders,Linux,VirtualBox 4.0.6,2011-04-21T22:50:42Z,2021-07-21T08:05:07Z,2021-07-21T08:05:07Z,"When running bonnie++ bechmark on Linux guest (Fedora 14) in a shared folder under Windows XP host, the benchmark fails due to ""directory not empty"" at the end. 

The benchmark creates thousands of small files, and then deletes them. The problem is that after all deletions are done (and no error is reported), the benchmark directory is not empty.

Running the same benchmark on the same guest, but on a Linux native folder (VDI disk), the benchmark runs OK. No files left over.

VirtualBox 4.0.6 (the problem also occurred on VirtualBox 4.0.4, I just hadn't reported it yet, sorry)[[BR]]
Host: Windows XP Professional SP3[[BR]]
Guest: Fedora 14 kernel 2.6.35.11-83.fc14.i686[[BR]]
bonnie++-1.96-1.fc13.i686

Terminal session:

{{{
# cd /media/sf_some_shared_folder
# bonnie++ -u root -n 3 -s 0
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
# ls
Bonnie.1733
# ls Bonnie.1733/ | wc -l
1106
# for i in `seq 1 5`; do bonnie++ -u root -n 3 -s 0; done
Using uid:0, gid:0.
Create files in sequential order...done.
Stat files in sequential order...done.
Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty
Cleaning up test directory after error.
...[snip, cut 4x repeated output]...
# for dir in `ls -d Bonnie*`; do \
    echo -n ""files left over in $dir: ""; \
    ls $dir | wc -l; done
files left over in Bonnie.1733: 1106
files left over in Bonnie.1743: 1111
files left over in Bonnie.1744: 1102
files left over in Bonnie.1745: 1102
files left over in Bonnie.1746: 1102
files left over in Bonnie.1747: 1108
# rm -rf Bonnie.*
# ls
}}}

Notes:[[BR]]
- bonnie++ option [-n 3] creates 3 * 1024 files[[BR]]
- The command [rm -rf Bonnie.*] successfully deletes all left over files. That said, as stated above the benchmark runs OK on native Linux guest disk instead of shared folder, so it seems the problem is not in bonnie++ code.[[BR]]
- There's no error / no message appearing at VBox.log for the running VM right before, during or after the benchmark. See attached file VBox-20110421-1939.log.


// BTM3505 (self reference, please ignore)
",Edmar (Macrovita)
8760,VMDK: VERR_SHARING_VIOLATION,Linux,VirtualBox 4.0.6,2011-04-21T21:06:37Z,2019-03-03T04:57:10Z,2019-03-03T04:57:10Z,"When running in an administrator command line and attempting to create virtual drives from raw disks under a windows 7 host, vboxmanage fails with this error message.  I was previously able to use these commands to mount my ubuntu partition under virtualbox on a windows XP host.  

Regards,
Alaric

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands listpartition
s -rawdisk \.\PhysicalDrive0
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
5       0x83  0   /2  /1   29  /254/63           235          126
6       0x82  30  /1  /1   333 /254/63          2384       482013
7       0x83  334 /1  /1   1023/254/63         18119      5365773
8       0x83  1023/254/63  1023/254/63         17406     42475520
2       0x07  1023/254/63  1023/254/63        114470     78124095

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands createrawvmdk
 -filename ""c:\Users\alaric\mydrive.vmdk"" -rawdisk \.\PhysicalDrive0 -partition
s 5,6,7,8
VBoxManage.exe: error: VMDK: could not open raw partition file '\.\PhysicalDriv
e0'
VBoxManage.exe: error: Error code VERR_SHARING_VIOLATION at D:\tinderbox\win-4.0
\src\VBox\Storage\VMDK.cpp(3762) in function vmdkCreateRawImage
VBoxManage.exe: error: Cannot create the raw disk VMDK: VERR_SHARING_VIOLATION
VBoxManage.exe: error: The raw disk vmdk file was not created
",Alaric
8796,Host-only adapter interface lost it's manual configured ipv4 address,Windows,VirtualBox 4.0.6,2011-04-26T23:01:51Z,2017-01-06T04:00:56Z,2017-01-06T04:00:56Z,"I have a host-only interface created by 2.x long time ago. After installation of 4.0.6, I find I have to re-configure the ip address of host-only interface after every reboot.
The ip address is manually configured by vbox manager gui, and then I add gateway and dns server in the ipv4 properties。 After reboot，the configuration in the ipv4 properties seems not changed, but in the vbox manager gui, the ip address will be something like ""169.254.4.67"", and the ipconfig.exe command will show the same address.",kidault
8893,FATAL: Int13_diskette_function: read error,other,VirtualBox 4.0.6,2011-05-15T00:24:22Z,2011-08-12T09:18:42Z,2011-08-12T09:18:42Z,"Win7Pro w/8GB mobo is Gigabyte 870A-UD3, CPU is AMD Phenom II X6 1075T.  Guests are MS-DOS 6.2 and MS-DOS 6.22.  Multiple error situations.  Both guests crash with error message:  FATAL: Int13_diskette_function: read error.  Same happens with USB Floppy drive.

I've replaced the internal Diskette drive but get the same results.  I can't operate these guests without diskette support.

Please help.",Bill Peavy
8855,"Windows XP netcard doesnt work with ""VirtualBox Bridged network driver"" enabled",other,VirtualBox 4.0.6,2011-05-06T05:29:01Z,2011-05-10T02:24:05Z,2011-05-10T02:24:05Z,"after upgrade version 4.0.4 to 4.0.6 get troubles with networking of Host system (Windows XP SP2).
after booting up a systyem local (physical) netcard properties fields ""IP"", ""netmask"" & ""gateway"" showed empty strings, inspite of ""tcp/ip properties"" are configured as ""manual"". changing properties of netcard didnt help (changes even didnt ""appended"" successfully). only turning ""VirtualBox Bridged network driver"" to ""disabled"" state allowed successful conection to local network (& internet).

",GG
8849,Feature Request: Snapshot Immutable Images and Enhanced Branching,Windows,VirtualBox 4.0.6,2011-05-04T22:23:10Z,2011-05-05T06:39:38Z,2011-05-05T06:39:38Z,"Snapshots:
Snapshots in VMware 7 have a number of advantages: 
They have automatic snapshots every few days + ability to create new VM from snapshots (aka differencing-immutable images).

Another enhancement of the snapshot system would be; having the ability to branch out from many saved states and from the current one. An example of what I am talking about:
 [[Image(http://s.techairlines.com/wp-content/uploads/2009/09/VMware-Snapshots.png)]]

It would be very useful. Thanks for considering.",DNS
8848,Feature Request: Ability to map VDI to Windows and use them as a harddrive,Windows,VirtualBox 4.0.6,2011-05-04T22:12:35Z,2011-05-04T22:40:54Z,2011-05-04T22:40:54Z,"Ability to map vdi to windows and use them as a harddrive storage directly. Windows doesn't have easy way loop-mount facility. This will require writing Windows-host SCSI driver to make it work. Possible, but hard.",DNS
8828,Back button in program installer doesn't work,other,VirtualBox 4.0.6,2011-05-03T05:17:22Z,2011-05-03T05:17:22Z,2011-05-03T05:17:22Z,"This is while installing the software on WINDOWS (not sure about other systems) When you get to the last screen on ""Oracle VM VirtualBox 4.0.6 Setup"", the back button does nothing.",Jimmy
8970,Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION),Windows,VirtualBox 4.0.8,2011-05-26T16:21:51Z,2020-04-20T18:13:29Z,2020-04-20T18:13:29Z,"Failed to load unit 'pgm' (VERR_SSM_INTEGRITY_DECOMPRESSION)

occurs in v4.08

have a virtual world that is frozen in time with virtualbox guest additions service disabled in vw.  when a restore is done, this error now appears.  used to be able to freeze time on vb machine a few versions back without problems and save its state then restore etc.  unable to do this now without getting an error on the restore state.  very problematic. seems like there's some new check that flags the vw when the date is out of sync possibly and its keeping the vw from being restored.

thank you,
art",art
9036,"kernel WARNING ""sysfs: cannot create duplicate filename /devices/virtual/bdi/vboxsf-$SHARENAME""",Linux,VirtualBox 4.0.8,2011-06-06T19:12:45Z,2011-10-19T18:15:16Z,2011-10-19T18:15:16Z,"The following kernel messages are regularly logged since upgrading to 4.0. They appear harmless.

{{{
Jun  6 20:00:41 wintermute kernel: [   18.074041] ------------[ cut here ]------------
Jun  6 20:00:41 wintermute kernel: [   18.074048] WARNING: at /build/buildd-linux-2.6_2.6.39-1+b1-amd64-h9EWBu
/linux-2.6-2.6.39/debian/build/source_amd64_none/fs/sysfs/dir.c:455 sysfs_add_one+0x86/0x98()
Jun  6 20:00:41 wintermute kernel: [   18.074051] Hardware name: VirtualBox
Jun  6 20:00:41 wintermute kernel: [   18.074052] sysfs: cannot create duplicate filename 
'/devices/virtual/bdi/vboxsf-vmshare'
Jun  6 20:00:41 wintermute kernel: [   18.074054] Modules linked in: bridge stp bnep rfcomm bluetooth rfkill binfmt_misc 
ppdev lp sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod joydev snd_intel8x0 snd_ac97_codec ac97_bus 
snd_pcm snd_seq snd_timer snd_seq_device pcspkr snd processor soundcore psmouse ac thermal_sys power_supply button 
serio_raw parport_pc parport snd_page_alloc evdev fuse vboxsf(O) vboxguest(O) loop autofs4 ext4 mbcache jbd2 crc16 
nbd usbhid hid sg sd_mod sr_mod cdrom crc_t10dif ohci_hcd ahci libahci libata ehci_hcd virtio_net scsi_mod usbcore 
virtio_pci virtio_ring virtio [last unloaded: scsi_wait_scan]
Jun  6 20:00:41 wintermute kernel: [   18.074089] Pid: 1226, comm: mount.vboxsf Tainted: G           O 2.6.39-1-amd64 #1
Jun  6 20:00:41 wintermute kernel: [   18.074091] Call Trace:
Jun  6 20:00:41 wintermute kernel: [   18.074097]  [<ffffffff810458b4>] ? warn_slowpath_common+0x78/0x8c
Jun  6 20:00:41 wintermute kernel: [   18.074100]  [<ffffffff81045966>] ? warn_slowpath_fmt+0x45/0x4a
Jun  6 20:00:41 wintermute kernel: [   18.074102]  [<ffffffff8114f8aa>] ? sysfs_add_one+0x86/0x98
Jun  6 20:00:41 wintermute kernel: [   18.074105]  [<ffffffff811500cd>] ? create_dir+0x67/0x9f
Jun  6 20:00:41 wintermute kernel: [   18.074108]  [<ffffffff81150196>] ? sysfs_create_dir+0x91/0xa5
Jun  6 20:00:41 wintermute kernel: [   18.074112]  [<ffffffff811a34fc>] ? kobject_add_internal+0xc8/0x181
Jun  6 20:00:41 wintermute kernel: [   18.074114]  [<ffffffff811a3745>] ? kobject_add+0x66/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074118]  [<ffffffff81331dc0>] ? mutex_lock+0xd/0x33
Jun  6 20:00:41 wintermute kernel: [   18.074120]  [<ffffffff811a3376>] ? kobject_get+0x12/0x17
Jun  6 20:00:41 wintermute kernel: [   18.074124]  [<ffffffff81242cfa>] ? device_add+0xcf/0x5d7
Jun  6 20:00:41 wintermute kernel: [   18.074127]  [<ffffffff8124329f>] ? device_create_vargs+0x8b/0xbc
Jun  6 20:00:41 wintermute kernel: [   18.074131]  [<ffffffff810cbb0f>] ? bdi_register+0x5a/0x183
Jun  6 20:00:41 wintermute kernel: [   18.074133]  [<ffffffff810cb794>] ? bdi_init+0x12b/0x157
Jun  6 20:00:41 wintermute kernel: [   18.074137]  [<ffffffff8110d9c1>] ? inode_sb_list_add+0x10/0x4b
Jun  6 20:00:41 wintermute kernel: [   18.074141]  [<ffffffffa01914fc>] ? sf_read_super_26+0x44f/0x514 [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074144]  [<ffffffff811a2788>] ? ida_get_new_above+0x196/0x1b7
Jun  6 20:00:41 wintermute kernel: [   18.074147]  [<ffffffff811a2bb3>] ? idr_pre_get+0x57/0x6b
Jun  6 20:00:41 wintermute kernel: [   18.074151]  [<ffffffff810fd06a>] ? unlock_super+0x21/0x21
Jun  6 20:00:41 wintermute kernel: [   18.074154]  [<ffffffff810fd0b8>] ? set_anon_super+0x4e/0xe1
Jun  6 20:00:41 wintermute kernel: [   18.074157]  [<ffffffff810fdf6a>] ? sget+0x35d/0x372
Jun  6 20:00:41 wintermute kernel: [   18.074160]  [<ffffffffa01910ad>] ? sf_glob_free+0x2a/0x2a [vboxsf]
Jun  6 20:00:41 wintermute kernel: [   18.074163]  [<ffffffff810fe05c>] ? mount_nodev+0x45/0x79
Jun  6 20:00:41 wintermute kernel: [   18.074165]  [<ffffffff810fdb2f>] ? mount_fs+0x6c/0x14a
Jun  6 20:00:41 wintermute kernel: [   18.074168]  [<ffffffff81112ce9>] ? vfs_kern_mount+0x61/0x97
Jun  6 20:00:41 wintermute kernel: [   18.074171]  [<ffffffff81112d7e>] ? do_kern_mount+0x49/0xd6
Jun  6 20:00:41 wintermute kernel: [   18.074173]  [<ffffffff81113533>] ? do_mount+0x728/0x792
Jun  6 20:00:41 wintermute kernel: [   18.074176]  [<ffffffff810e6260>] ? alloc_pages_current+0xa7/0xca
Jun  6 20:00:41 wintermute kernel: [   18.074179]  [<ffffffff81113625>] ? sys_mount+0x88/0xc3
Jun  6 20:00:41 wintermute kernel: [   18.074182]  [<ffffffff81338c12>] ? system_call_fastpath+0x16/0x1b
Jun  6 20:00:41 wintermute kernel: [   18.074184] ---[ end trace 8683823577cfa94a ]---
Jun  6 20:00:41 wintermute kernel: [   18.074186] kobject_add_internal failed for vboxsf-vmshare with -EEXIST, don't try to 
register things with the same name in the same directory.
}}}

This may be a duplicate of #8056, but for me the shared folders work fine, whereas in that bug the user cannot mount them.

Guest is Linux 2.6.32 through 2.6.39.",Sam Morris
9026,Keyboard problem on guest systems in w7 host,Linux,VirtualBox 4.0.8,2011-06-05T18:02:39Z,2011-06-10T04:53:11Z,2011-06-10T04:53:11Z,"I'm running VirtualBox 4.0.8 on 64-bit Windows 7 Home Premium with the latest updates.

After upgrading to 4.0.8: in both WinXP and Ubuntu 10.10 guests, which have worked for months, I find that characters typed on the keyboard produce random or sequential numbers. Holding the key down continually produces different numbers.

Holding down the ""Windows key"" while typing produces normal, correct results.

I attempted to go back to previous VirtualBox versions by downloading and installing old releases.  Going back as far as 3.2.1.2 did not fix the problem.  I suspect that this is because I haven't removed the defective software component and it is still being used by the older version I've installed.

I notice that there are other reports of this problem this week in the forum for Windows-hosted VirtualBox users, but no solutions. ",davidsmith
9031,Add option to handle URLs in guest on host,Windows,VirtualBox 4.0.8,2011-06-06T14:33:33Z,2011-06-06T14:33:33Z,2011-06-06T14:33:33Z,"It would be really useful if Guest Additions could (optionally?) add a handler for URLs that would pass them through to the host.

My use case is Outlook running on a Win7 Guest.  I'd prefer if links in Outlook opened on my Host instead of in the Guest. Others at my work have a similar use case, as well as [http://superuser.com/questions/140234/is-there-a-way-to-redirect-a-click-on-a-url-in-a-virtualbox-guest-to-open-in-th others] outside my work.

Ciao!",Christian Höltje
9358,Mouse pointer offset when shown as arrow. Position ok if line-pointer (text-mode),Windows,VirtualBox 4.1.0,2011-08-01T20:02:26Z,2011-08-11T05:09:41Z,2011-08-11T05:09:41Z,"A display in Vbox shows Text and buttons in the top and a table with several lines and columns below.
As soon as the mousepointer crosses the border from the screen-top to the table it offsets by 1.5 lines of the table vertically and about the same amount horizontal.
If the mouse pointer goes across a field of the table which has text-contents, i.e. the mouse pointer changes to a line pointer to select text it adjusts perfectly to the text.
This problem has shown up after installing Vbox 4.1 with extension pack 4.1 and guest additions 4.1. Everything was working fine with 4.0.12",Ulrich
9385,"""Create a snapshot of the current state"" is not remembered when restoring snapshots",other,VirtualBox 4.1.0,2011-08-05T18:17:26Z,2011-08-05T18:17:26Z,2011-08-05T18:17:26Z,"Not using the English version so terminology may be slightly off.

Starting with 4.1.0 when you try to restore an snapshot and the current state is modified, the GUI asks if you want to snapshot the current state. But that checkbox is always marked by default and doesn't remember when you uncheck it, so you have to uncheck it every time.

Other checkboxes, such as the one about restoring the last snapshot when you force-power-down a machine, do remember their state.",jmausr
10436,"Virtual Box install fails (rollback, MSI code 1603) on Windows 7 64 host",Windows,VirtualBox 4.1.12,2012-04-13T17:57:17Z,2015-10-15T13:42:19Z,2015-10-15T13:42:19Z,"I have read the posts, howtos and such and still cannot determine why my install is failing (rollback initiated during install) MSI error code 1603. 

Host: Windows 7 64 bit

Tried command line install without USB drivers. Still fails.

The only driver log created was setupapi.app.log. It and the install log are attached.

Any help would be greatly appreciated.",bobheck
10771,VirtualBox Extension Pack installation failed exit code 128 E_FAIL (0x80004005),other,VirtualBox 4.1.18,2012-07-19T09:57:35Z,2021-06-19T14:31:42Z,2021-06-19T14:31:42Z,"Problem happens in a fresh install VirtualBox 4.1.8-75467 on host Microsoft Windows Server 2003 Standard R2 with Service Pack 2 64-bit with No antivirus installed.

Failed to install the Extension Pack 

The installer failed with exit code 128: .

Result Code: E_FAIL (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}


VirtualBox (XP)COM Server 4.1.18 r78361 win.amd64 (Jun  5 2012 15:58:59) release log
00:00:00.031 main     Log opened 2012-07-18T17:03:02.358332400Z
00:00:00.031 main     OS Product: Windows 2003
00:00:00.031 main     OS Release: 5.2.3790
00:00:00.031 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031 main     Process ID: 2236
00:00:00.031 main     Package type: WINDOWS_64BITS_GENERIC
00:00:01.063          VDInit finished
00:00:28.234 ExtPackInst ExtPack: Executing 'C:\Program Files\Oracle\VirtualBox/VBoxExtPackHelperApp.exe' '--display-info-hack' 'hwnd=0x210122''install' '--base-dir' 'C:\Program Files\Oracle\VirtualBox/ExtensionPacks' '--cert-dir' 'C:\Program Files\Oracle\VirtualBox/ExtPackCertificates' '--name' 'Oracle VM VirtualBox Extension Pack' '--tarball' 'D:/Software/Virtualbox/Oracle_VM_VirtualBox_Extension_Pack-4.1.18-78361.vbox-extpack' '--sha-256' '1c8cf8d67d9adf75fd02d529c03ee2f960ec4be08970fd8030ba7912ef1e3198'
00:00:28.234 ExtPackInst ExtPack: enmReason=1 iStatus=128 stderr=''
00:00:28.234 ExtPackInst ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={The installer failed with exit code 128: }, preserve=false
00:00:45.656 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={The object is not ready}, preserve=false


I made many test (all as user Administrator):

1. Uninstall program Oracle VM VirtualBox
2. Delete folder .VirtualBox in Documents and Settings/Administrator
3. Verify Oracle folder not exist anymore in Program Files
4. Install VirtualBox version X
5. Install the extension pack version X
6. Same messages error as above

This made for X = All available version 4 (4.1.4-74291, 4.1.6-74713, 4.1.8-75467, 4.1.10-76836, 4.1.12-77245, 4.1.14-77440, 4.1.16-78094, 4.1.18-78361). No one works fine.

Another problem I suppose related is that for every above Virtualbox version the command: ""vboxmanage extpack cleanup"" returns

VBoxManage.exe: error: The installer failed with exit code 128:
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ExtPackManager, interface IExtPackManager, callee IUnknown
Context: ""Cleanup()"" at line 1148 of file VBoxManageMisc.cpp
",davipena
10844,Failed to attach the USB device to virtual machine,Linux,VirtualBox 4.1.18,2012-08-21T03:59:31Z,2020-01-10T14:18:26Z,2020-01-10T14:18:26Z,"64bit Windows 7 host, various 32 and 64 bit Linux guest distributions, 4.1.18r78361 extensions package installed.

Cannot get USB device to be recognized by guest (check via lsusb). Sometimes, selecting the device in the Devices->USB Devices menu just has no effect (entry doesn't get checked), and sometimes I get the following:


Failed to attach the USB device Yubico Yubikey II [0224] to the virtual machine pws-deb6.

USB device 'Yubico Yubico Yubikey II' with UUID {3c66074d-0580-47fd-921e-81da094dd391} is busy with a previous request. Please try again later.

Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
---

Notes:
- Other USB devices can be successfully attached.
- Playing with the USB filter settings has no effect.
- On another 64bit Windows 7 host, running the same versions of VirtualBox and guest, the same (physical) device is successfully passed through to the guest. (Unfortunately, I need this working on the machine that fails...).

Please advise.

P.S. The device vendor has offered to provide assistance, including device samples.",Rony Shapiro
10754,Running xperf -on latency -stackwalk profile doesn't capture CPU Sampling data in Windows 8,Windows,VirtualBox 4.1.18,2012-07-13T07:00:04Z,2019-04-09T15:49:32Z,2019-04-09T15:49:32Z,"When I run xperf -on latency -stackwalk profile in Windows 8 it doesn't capture CPU Sampling data (http://msdn.microsoft.com/en-us/library/ff191014.aspx, http://blogs.msdn.com/b/pigscanfly/archive/2009/08/06/stack-walking-in-xperf.aspx )

I've asked Microsoft and they told my that VirtualBox reports CPU h/w counters but then in fact not supporting them.",Andre.Ziegler
10759,Can't kill Virtualbox.exe process,Linux,VirtualBox 4.1.18,2012-07-13T20:31:09Z,2016-02-23T02:41:25Z,2016-02-23T02:41:25Z,"Windows 7 64 bit Host.
Ubuntu 11.10. OS will lock when running certain programs and the virtualbox.exe process will keep running at 25% cpu. Can't kill it in the command line or in task Manager. Only option is to reboot the host Windows 7. ",speedkills20
10764,VirtualBox 4.1.18r78361 prevents Windows 7 host from sleeping/entering standby,Linux,VirtualBox 4.1.18,2012-07-15T17:20:19Z,2015-11-17T06:22:45Z,2015-11-17T06:22:45Z,"While VirtualBox is running, my Windows 7 host OS will not enter standby/sleep after the time of inactivity specified in my Windows power scheme has elapsed.  When I close VirtualBox, Windows sleeps after the time specified in the power scheme.  This problem started after I upgraded to 4.1.18r78361.  This is very inconvenient because I like to keep my guest OS running, so I have to remember to put my host computer into standby whenever I leave the computer or it will needlessly stay on.",bgx90
9639,v4.1.2 and previous: amplified OpenGL mouse movements,Windows,VirtualBox 4.1.2,2011-09-23T12:15:21Z,2022-01-04T21:25:37Z,2022-01-04T21:25:37Z,"Host:
System   -- Dell E6510: 8GB, 1.7GHz Core i7 Q720; Win7 Pro SP1 x64
Graphics -- Nvidia NVS 3100M; Forceware v270.61
Mouse -- Microsoft USB IntelliMouse Optical; IntelliPoint v8.20.409.0
VirtualBox v4.1.2

Guests:
Win7 Ultimate SP1 x64 with Guest Additions installed
Win8 Developer Preview x64 with NO Guest Additions installed


Symptoms:

When running the OpenGL program Celestia v1.6.1
which is available at http://sourceforge.net/projects/celestia/files/ 
dragging the mouse in its window with either or both mouse buttons held 
down seems to cause the application to receive many more mouse evemts
than it should or to receive unrealistically large mouse motion values.

When the LMB is dragged, the selected object should move the same amount
of distance that the mouse is dragged. Instead it ""leaps off the screen""

When the RMB is dragged, the selected object should rotate smoothly.
Instead it rotates by unpredictably large amounts.

When both buttons are held down simultaneously, the selected object
should move at a moderate speed toward or away from the viewpoint.
Instead it immediately becomes extremely close or invisibly distant.

Exactly the same symptoms are seen when running Celestia in both guests
and whether or not 2D or 3D graphics acceleration is enabled.

These symptoms are not seen when running on the host.

I am attaching a zip file containing VirtualBox logs recorded while 
running Celestia under Win8.
",Selden Ball
9559,Winsat fails with TSC Frequency,Windows,VirtualBox 4.1.2,2011-09-05T12:26:08Z,2021-07-09T09:34:33Z,2021-07-09T09:34:33Z,"I can not get WinSat to run (Windows System Assessment Tool)

Pretty much every test receives this result:

>winsat formal
> Running the Formal Assessment
Error: Cannot Measure Time Stamp Counter (TSC) Frequency

>winsat cpu
Windows System Assessment Tool
Error: Cannot Measure Time Stamp Counter (TSC) Frequency

The Host machine is a Dell 6510 laptop with i7 q720 win7 x64.
The Guest is win7 x32.
Both are at SP1 and have current windows updates.


I've had no luck running winsat on any version 4 it did run on version 3 except for graphic.

I believe this same issue also leads to long guest OS pauses (for 30 - 90 second) where no activity in the guest happens and then it resumes to normal operations.

I have current guest additions installed,




",steve richards
9586,Seamless Mode cuts out Drop-Down boxes where options are not inside Window/Dialog,Windows,VirtualBox 4.1.2,2011-09-11T14:43:52Z,2015-05-05T18:22:42Z,2015-05-05T18:22:42Z,"If you drop-down a combo boc and the list of options full-out of the active window in Seamless Mode, you cannot see them. I have upgraded from 3.1.8 to 4.1.2 and never saw this issue in 3.1.8. The guest PC is a clean build of Windows XP with 4.1.2 tools installed.

See picture which shows the issue.",stewaj03
9541,VirtualBox GUI does not support Windows 7 Jump Lists for recent machines.,other,VirtualBox 4.1.2,2011-08-31T12:57:41Z,2011-08-31T12:57:41Z,2011-08-31T12:57:41Z,"Following on from a 2010 forum post http://forums.virtualbox.org/viewtopic.php?f=8&t=28017, this ticket is for the implementation of Windows 7 jumplists. 
As suggested in the forum posting, implementing a SHAddToRecentDocs call (from Shlobj.h) when Virtual Machines are started (or opened) on Windows XP and above should allow basic jumplist functionality.",Adam
9472,"Minor regression in past several versions - ""Help...About Virtualbox..."" flashes off-screen before it can be read",Linux,VirtualBox 4.1.2,2011-08-20T07:18:49Z,2011-08-20T07:18:49Z,2011-08-20T07:18:49Z,"Windows 7 x64 SP1 host:

Help...About Virtualbox...

Version box materializes momentarily, then vanishes before it is possible to read it.

Since this may include your copyrights, you should be more concerned about this than I am.",Bob Kosch
9450,Restore snapshot improvements,Windows,VirtualBox 4.1.2,2011-08-17T10:13:57Z,2011-08-17T10:13:57Z,2011-08-17T10:13:57Z,"1. When double clicking a snapshot, this should mean: Restore this snapshot.
Similar to (but easier than) clicking on the snapshot and select the restore button.

2. When current state hasn't changed and you restore the nearest snapshot, there's no need to display the confirmation dialog. Nothing gets deleted and the operation is totally reversible (simply by restoring the previous snapshot again).

3. The message that comes up, when you restore a snapshot and current has changed only asks if you want to create a snapshot of current state, but not why I would want that/what happens if I do.
The text should clarify that I can create a branched snapshot tree, something like:
'...... by checking the checkbox below to create a branched snapshot tree; if you don't....'

4. That checkbox should be OFF by default! Normally when restoring a snapshot, you really want to delete the current state.

5. Documentation shows an image with branched snapshots, but not a word about how you create a branched snapshot tree. Please add some text about that.",Poul Bak
9448,Don't show mouse pointer in fullscreen,Windows,VirtualBox 4.1.2,2011-08-17T06:49:57Z,2011-08-17T07:52:18Z,2011-08-17T07:52:18Z,"Don't show mouse pointer in fullscreen for windows host.
Thanks Gabee.",Gabee
10851,VM config file lost after host power off,other,VirtualBox 4.1.20,2012-08-22T08:52:36Z,2018-03-07T08:09:42Z,2018-03-07T08:09:42Z,"VBox: 4.1.16 (and 4.1.20)

Host: Windows 7 x64 (and other Windows)

When shutting down host, (after Windows update, or sudden power off) in some cases VBox does delete the *.vbox meta-data file, and the VM becomes ""inaccessible"" state. In some cases the file becomes corrupted and zero-bytes, and there are no *.vbox-tmp and no *.vbox-prev files to recover from.

Workaround: copy [VM].vbox-tmp or [VM].vbox-prev as [VM].vbox can restore the VM in most cases. (something new users can't do)

Recommended real fix: VBoxSVC must write down a history of transactions into the VM folder, per VM, [VM].vbox-transactions file, which should list all changes to the *.vbox file meta-data in a patch/diff format, and then, when VM becomes ""inaccessible"", VBoxSVC must attempt to recover the file until last transaction automatically, plus will allow manual recover and debug.

NOTE: This bug is an old one, and AFAIK happens once every several weeks since v4.0.0 (but rarely) - still losing VM is *really* bad.

Log attached.

-Technologov, 2012-08-22.",Technologov
10999,extended error 234 when trying to list directory,Windows,VirtualBox 4.1.22,2012-09-28T12:27:24Z,2016-10-16T20:04:08Z,2016-10-16T20:04:08Z,"Running host windows 7 64 bit
running guest win xp 32 bit, dos program foxprox doing a command prompt from within the program and a dir of a mapped drive or shared vbox folder

extended error 234 and no directory listing",itguru2
9786,USB devices freeze VM instances and VB main window under certain conditions,Windows,VirtualBox 4.1.4,2011-10-19T12:33:29Z,2019-06-28T19:44:54Z,2019-06-28T19:44:54Z,"In one certain instance I have found that any tested usb Headsets will freeze the VM and the VirtualBox windows. Since the latest upgrade when connecting a USB headset (I have tried 3), upon opening any program that would use the headset the VM will freeze. It will also make the main VirtualBox windw freeze to where you cannot shut down that VM or open new ones. I have tried with a soft phone, voice recognition and sound recorder. All produce the same effect.
1. open a Windows VM on a Windows host
2. attach a USB headset
3. start Windows sound recorder
next clicking on anything shaould freeze the VM indefinitely
This was tested with Win 7 Ult. X64 host and Win 7 Pro X64 guest",Mark S Klopf
9717,Unable to restore from state saved with memory balloon active,Windows,VirtualBox 4.1.4,2011-10-07T15:24:08Z,2018-07-18T15:19:40Z,2018-07-18T15:19:40Z,"Steps to reproduce:

 1. Create a VM, install an operating system that supports the VirtualBox Guest Additions (Windows, Linux)
 2. Install Guest Additions, Reboot guest
 3. VBoxManage controlvm [vnname] [balloon size][[BR]]
   (any balloon size grater than zero causes the issue)
 4. Save the VM state
 5. Attempt to start the VM

Error message is Failed to load unit 'pgm' (VERR_SSM_LOADED_TOO_LITTLE).",cb1
9688,Private host network problem => Fixed in SVN,Linux,VirtualBox 4.1.4,2011-10-04T13:44:08Z,2016-07-01T09:26:13Z,2016-07-01T09:26:13Z,"Since I have pass to the last version 4.1.4 I have a problem :

The Private host network function for the partage in network don't work.

This functionnaly don't work since i have restart the computer.

I use Windows 7 and a VM with ubuntu 10.10.

I have solve my problem with re-install the version 4.0.12.

Sorry for my english.

Regards.",alex57
9776,When using pause the gray out effect isn' working when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu,other,VirtualBox 4.1.4,2011-10-17T13:07:28Z,2012-02-12T03:57:18Z,2012-02-12T03:57:18Z,"When using pause the gray out effect isn' working when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu

VirtualBox 4.1.4 

Guest Additions 4.1.4 installed 

Ubuntu 11.04 Up-to-date no extra packages other than the guest additions from the guest additions .iso installed.
 
ATI Mobility Radeon HD 5470 (Driver version 11.9) 

Windows 7 Home Premium 64-bit Intel VT-x enabled Core i3 proccessor (4 cores cores reported, I think it's 2 hyperthreaded to 4)
 
1 GB ram allocated to guest 2 CPU Guest SMP 8GB .vdi 
",temp4746
9808,Cannot delete snapshot due to hidden differencing image,other,VirtualBox 4.1.4,2011-10-25T08:40:44Z,2011-12-08T12:20:07Z,2011-12-08T12:20:07Z,"Fairly regularly, I find that when I try to delete a snapshot, the VBM (VBox Manager) reports that it cannot because there is more than one child hard disk.  However, the VBM does not show any indication of its existence in the snapshot hierarchy.  I can only see the extra disk in the VMM (VMedia Manager), where I can delete it and then successfully delete the snapshot from the VBM.

However, that the VBM and VMM disagree about the disk/differencing hierarchy must be a bug, right?

In all of the situations where this has occurred, I have done nothing more complex than periodically create snapshots and periodically delete them.  The disks are not shared across machines and I've not cloned any machines.  Unfortunately, it's not reproducible, it just occasionally happens.  I've come across this problem on 2 different hosts with 4.1.4.  I think I've seen it in earlier versions too.",simon marshall
9846,Virtualbox 4.1.4r74291 - shared folders disappear and reappear randomly between reboots,Windows,VirtualBox 4.1.4,2011-11-02T17:22:48Z,2011-11-02T17:22:48Z,2011-11-02T17:22:48Z,"Virtualbox 4.1.4r74291 - shared folder to drive letter mappings disappear and reappear randomly between reboots.
They always show up in the VM's Settings --> Shared Folders section, no problem displaying or editing them.   But, when you start the VM, sometimes they show in Windows Explorer as mapped drive letters, sometimes they don't.   They are always accesible when referenced as UNC paths, i.e. \vboxsrv\sharedfolder, but they are not always accesible as drive letters.",Pedro Serrano
9806,VirtualBox Manager does not update Machine status when the VM is started in a different desktop (sysinternals),Windows,VirtualBox 4.1.4,2011-10-25T02:21:01Z,2011-10-25T02:21:01Z,2011-10-25T02:21:01Z,"I use SysInternals desktops on Windows 7 64, which gives Windows four desktops.  I nominally run VMM on desktop 1 and VMs on each of the other three desktops.  All works fine, except for the VM status does not get updated on the VMM running in desktop 1.  

This has led to corrupted VM Linux filesystems due to executing a VM management task while the VM was in a state that normally would not allow the task to be executed.  

If the VMM is run in the same desktop as the VM, then the status gets updated.

WORKAROUND: verify that the VM is shutdown before performing any management tasks in the VMM.
",george lawton
4753,ost-only network adapters settings change after reinstall,other,VirtualBox 4.1.4,2009-08-11T15:32:38Z,2011-10-21T05:30:43Z,2011-10-21T05:30:43Z,"Every time I reinstall (mostly when updating to a new version) VirtualBox, my host-only network adapter settings are changed... I found out about this when the internet in the guests stopped working. The first time it took me a while to discover that the problem was on the changed settings, I never though they would be different for any reason.

The host-only settings for each adapter has two tabs, ""Adapter"" and ""DHCP Server"".

Since I have the DHCP Server disabled, I don't know if it happens to those settings. But for the Adapter, I change the IP and Network Mask to match my needs and every time I update (last time was 3.0.2 -> 3.0.4), those settings are reset to the default values and because of that, my network connection stops working in the guests because it can't find the Adapter IP I specified.

Don't you agree that any settings for custom configurations shouldn't be changed when the user re-installs or upgrades to a new version? I mean, I changed the settings for a reason, I'm not expecting them to change unless I explicitly change them.",Nazgulled
9792,Parent VM Still reports being parent of deleted VMs,other,VirtualBox 4.1.4,2011-10-20T13:12:42Z,2011-10-20T13:22:50Z,2011-10-20T13:22:50Z,"In Virtualbox 4.1.4 GUI if you have a VM that is a parent of a linked clone and you delete that linked clone it will still say ""Linked Base for [VM Name]""


",Jeremy
9777,"The display panel in Ubuntu only shows the current resolution and 800x600, 640-480 - need better way to set specific resolutions",Linux,VirtualBox 4.1.4,2011-10-17T13:09:03Z,2011-10-17T17:02:53Z,2011-10-17T17:02:53Z,"The display panel in Ubuntu only shows the current resolution and 800x600, 640-480, there is no way to set a specific resolution other than that.
Maybe adding a dialog to set a specific resolution using the resizing ability of the guest additions will offer a simple solution for this. (there needs to be a GUI for this not only VBOXManage display hints)",temp4746
9774,2.The preview in the VirtualBox main window shows a black screen when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu,Linux,VirtualBox 4.1.4,2011-10-17T13:05:24Z,2011-10-17T13:05:24Z,2011-10-17T13:05:24Z,"The preview in the VirtualBox main window shows a black screen when running a 3D accelerated desktop (3D acceleration on) like Unity in Ubuntu

VirtualBox 4.1.4 

Guest Additions 4.1.4 installed 

Ubuntu 11.04 Up-to-date no extra packages other than the guest additions from the guest additions .iso installed.
 
ATI Mobility Radeon HD 5470 (Driver version 11.9) 

Windows 7 Home Premium 64-bit Intel VT-x enabled Core i3 proccessor (4 cores cores reported, I think it's 2 hyperthreaded to 4)
 
1 GB ram allocated to guest 2 CPU Guest SMP 8GB .vdi 
",temp4746
9744,Cancelling out of VM creation deletes entire mount point / junction,other,VirtualBox 4.1.4,2011-10-13T02:23:54Z,2011-10-13T11:05:56Z,2011-10-13T11:05:56Z,"On a Windows 7 64bit host, I have VirtualBox installed on Drive C:.
My VM ""library"" is a partition mounted via D:\Virtual.
If I start to create a new VM and cancel at any point beyond the ""VM Name and OS Type"" dialog, the mount point ""D:\Virtual"" will be destroyed.
The data on the partition remains intact and the mount point can be recreated.",Mike
9715,Change GUI to ask for merge or snapshot when gracefully shutting down a guest,Windows,VirtualBox 4.1.4,2011-10-07T11:44:15Z,2011-10-07T11:44:15Z,2011-10-07T11:44:15Z,"One nice feature of Virtual PC 2007 is that when you gracefully shut down a guest (only Windows), it displays a pop up box asking if you want to merge changes or discard them.

This feature would be nice in Virtual Box as it's a (slight) pain to shutdown the machine, then go to the console and delete a snapshot to merge the images.  Virtual Box, on gracefully shutdown of a guest, could display a pop up box asking if you want to 1) Snapshot 2) Discard Changes (Revert to last snapshot), or 3) Merge changes into last snapshot.  Note:  This would be for shutdown of the guest, not a restart of the guest.",Chris
9706,Big minimizing machine in Full Screen dual monitor mode,Linux,VirtualBox 4.1.4,2011-10-06T19:28:34Z,2011-10-06T19:28:34Z,2011-10-06T19:28:34Z,"I'm running Windows 7 Professional 64 bit as the host and Ubuntu 11.04 as the guest.

The dual monitor mode works much better in this release than in the previous release (the previous release frequently locked-up or froze when running Ubuntu 11.04).   However, there is still one more kink to work out.

When in full screen mode running dual monitors, if I click the minimize button on the VM tab with the VirtualBox controls for the machine, it only minimizes the primary monitor window and leaves the secondary monitor window maximized.  This should be fixed since the auto-resize feature in dual monitor mode in running an Ubuntu guest OS is still a little fragile.  Both windows should minimize when clicking the minimize button from the VirtualBox menu bar.",josiah
9983,Virtualbox doesn't start on Windows 7 x64,other,VirtualBox 4.1.6,2011-12-02T14:26:12Z,2016-02-13T16:48:29Z,2016-02-13T16:48:29Z,"Hello,

If I start VirtualBox GUI and launch Virtual Machine after restart it starts OK, but when I close the virtual machine and VirtualBox GUI. It I try to start VirtualBox GUI to launch some virtual machine, process starts, but no GUI shows. If I look at task manager the process VirtualBox and VBoxSVC are running.

After reading some info on site I added two environment variables VBOX_GUI_DBG_AUTO_SHOW=true, VBOX_GUI_DBG_ENABLED=true, but that doesn't help, when I look in VBoxSVC.log.

I also tried running virtual machine by using VirtualBox --startvm --debug <machine name>, but it doesn't work as well. Same goes if i try to run from VBoxManage. When this happens VBoxManage hangs on every command I try to pass, like listing or starting virtual machines. Hangs like it sits on command line and nothing happens.

In all the cases started application VirtualBox/VBoxManage doesn't consume resources or processor time according to task manager.

I don't know if you use windows events, but there are no warning or error messages in windows event viewer.

I tried downgrading to versions 4.1.4, 4.1.2, 4.1.0. While downgrading I uninstall VirtualBox from ""Programs and Features"" then install the older version. In all installations I also install VirtualBox Extension Packs for the corresponding version I am installing.

I am attaching two VBoxSVC.logs -
First is on hanged VirtualBox.
Second is on last started guest - Which is Windows 2003 R2 server.",Philip Bonev
9860,VirtualBox Bridged Networking Service Is not installed with Virtual Box 4.1.6,Windows,VirtualBox 4.1.6,2011-11-06T02:36:15Z,2015-08-13T16:29:31Z,2015-08-13T16:29:31Z,"I installed VB 4.1.6. Apparently it install fine. I then created a new virtual machine. I changed the networking settings to use ""Bridged Adapter"" in the Attached To list. However the Name list is empty. The dialog would not save the configuration because ""Invalid settings detected"". Same thing with earlier version of Virtual Box. The ""VirtualBox Host-Only Network"" is fine, but the bridged network adapter was not installed.",Fernando Quintero
9926,No virtual system boot with grub2 on mbr for raw disk access to specific partitions,Linux,VirtualBox 4.1.6,2011-11-20T18:53:01Z,2013-04-04T06:48:32Z,2013-04-04T06:48:32Z,"Recent Linux systems, such as Fedora 16, use the newer grub2 boot loader.  The usual grub2 setup places the boot code on the mbr and on the unpartitioned sectors immediately follow the mbr partition.  If a virtual guest Linux system is made using raw parition access to Linux code on a partition(s) separate from the host system partition(s), the grub2 boot code is not accessible unless the whole disk is attached rather than just the partitions containing the guest system.

For example, with a Windows 7 64bit host on partition 3 of disk 0 and Fedora 16 on partitions 5 and 6, and with grub2 installed on the mbr of disk0, VirtualBox will not boot a Fedora 16 x86_64 guest unless the vmdk is created with whole disk access to disk0.  If the vmdk is created with access to only partitions 5 and 6, Fedora does not boot and hangs after the boot code in the mbr is executed.  The code in the sectors following the mbr sector is not reached.  Given that it is dangerous for the virtual system to have direct access to the host operating system code, the grub2 boot code should be accessible when only individual partitions are attached.  For Windows hosts, the -relative option is not available for createrawvmdk so this option cannot be tested as a solution with Windows hosts.
",Leo Pilachowski
10007,Drag and Drop ISO on to CD/DVD Icon,Windows,VirtualBox 4.1.6,2011-12-07T18:46:51Z,2011-12-07T18:46:51Z,2011-12-07T18:46:51Z,"You should be able to drag/drop an .ISO file on to the icon in the statusbar.  I couldn't do that with the release as of today Dec 7, 2011 Using Win7 x64.",dfatvb
10001,Short file names missing from \vboxsvr\share,Windows,VirtualBox 4.1.6,2011-12-07T08:16:23Z,2011-12-07T08:16:23Z,2011-12-07T08:16:23Z,"short file names are missing via shared folders whether the drive is mapped or the unc is used.  for example: 

dir \vboxsvr\share /x 

should list short file names along with the name, but the short file names are missing.  this is causing problems with 16 bit utilities including source code builds that have to use the short name.
",dfatvb
9992,"Close button for ""already latest version"" window does not work",other,VirtualBox 4.1.6,2011-12-05T15:11:43Z,2011-12-05T15:11:43Z,2011-12-05T15:11:43Z,"The built-in close button for the ""you are already running the latest version"" window does not work. Nothing happens when I press the button. See attached screenshot.

The OK button works just fine (closes the window).",Oskar
9913,Windows XP Guest application causes hang of VirtualBox Guest & Windows 7 Host,Windows,VirtualBox 4.1.6,2011-11-17T08:32:28Z,2011-11-17T15:27:55Z,2011-11-17T15:27:55Z,"I am running Virtualbox 4.0.10 successfully with a Window 7 host and a Windows XP guest.

Any version of Virutalbox newer than the above suffers the following issue:

When starting an application on the guest called ""Cisco IP Communicator v7.0.5.4"" the guest hangs and does not respond and also the Virtualbox.exe process running on the host hits a constant 25% of CPU (which is one full CPU as I have a quad core system) and cannot be terminated via windows task manager, also of course Virtualbox GUI on the host also fails to respond - the only way to recover from this situation is to reboot the host.

I have tried things like trying a different networking adapter rather than PCnet FAST III, disabling the VTx, nested paging options, switching back to 1 CPU for the guest but it always causes this hang.

Attached are logs from a successful run of the guest on 4.0.10 obviously as it hangs I cannot attach from when a newer version suffers the hang.

I have held off logging a bug until now as I was hoping newer versions may resolve the issue but the fault is still present.",starfire
10081,"Updating damages existing ""pinned"" shortcuts",other,VirtualBox 4.1.8,2011-12-24T21:47:27Z,2017-07-28T12:35:00Z,2017-07-28T12:35:00Z,"When you pin the shortcut to VirtualBox to the Start Menu or Taskbar in Windows 7, and then update VirtualBox (Min to Min[4.1.0 to 4.1.2], or Major to Major[3.x to 4.x]) the shortcut appears to be deleted, leaving a broken pinned shortcut that needs to be deleted, and then recreated.

No other software I have pinned appears to have this problem when performing updates.

Has happened with every version of VirtualBox I've had installed, starting around 3.1.8, possibly earlier.

Expected behavior should let existing shortcuts, pinned and otherwise, should still be functional after simple updates.",kookyman
10309,USB is busy with a previous request [E_INVALIDARG (0x80070057)],Windows,VirtualBox 4.1.8,2012-03-06T19:03:54Z,2017-03-08T09:03:23Z,2017-03-08T09:03:23Z,"Hi,
I still have problems with connecting my USB device on this Win7-64bit host to a WinXP SP3 guest in 4.1.8 with usb_extension 4.1.8 and guest additions 4.1.8.

Connecting some usb flash drives succeeds but connecting my USB-to-CAN - device from peak-systems ([http://goo.gl/MSxX1 more info]) is not working. In earlier versions I got a message when starting the guest like ""Virtualbox USB is installing..."" and after the next complete restart of my computer the device was working. But now I don't get the windows tray message ""Virtualbox USB is installing..."" and if I want to connect my usb device while vm is running I get the error

{{{
Das USB-Gerät VER1:PEAK    
VER2:02.8.01        
DAT :06.05.2004
TIME:09:35:37
                             ... [1C11] konnte nicht an die virtuelle Maschine Windows XP gebunden werden.

USB device 'VER1:PEAK    

VER2:02.8.01        

DAT :06.05.2004

TIME:09:35:37

                             ...' with UUID {2fb58d0c-81b4-4505-9984-a67bfc272a87} is busy with a previous request. Please try again later.

Fehlercode:E_INVALIDARG (0x80070057)
Komponente:HostUSBDevice
Interface:IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee:IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
}}}

USB-filters are set correctly, as already mentioned other usb mass storages are working. On my host this peak usb device is running with latest drivers and all seems to work.

I've been searching already for some hours in google and had a look at [https://www.virtualbox.org/ticket/3033 #3033] and [https://www.virtualbox.org/ticket/5343 #5343] and [https://forums.virtualbox.org/viewtopic.php?f=5&t=31926 Forums] but nothing solved it until now.

Is there a way to find a solution? I don't want to reinstall earlier versions...
Is there a problem to disconnect the device from host because it's busy?

Thanks for your help",Jacky Ryan
10317,Windows 8 Host: No network adapters after resume from sleep,other,VirtualBox 4.1.8,2012-03-12T06:14:51Z,2017-01-26T05:07:15Z,2017-01-26T05:07:15Z,"I am running Oracle VirtualBox 4.1.8 r75467 on a Thinkpad T510.  When I put my computer to sleep, the only way to get functioning NIC's on my host after resume is to go into device manager, uninstall the NIC and then scan for hardware changes to re-install the NIC.  I disabled the VirtualBox Bridged Network Driver on each NIC and I no longer have this problem.",Andrew
10057,clipboard integration not working for headless guest,other,VirtualBox 4.1.8,2011-12-21T04:40:54Z,2016-10-10T21:37:11Z,2016-10-10T21:37:11Z,"I'm using v4.1.8, but I've noticed the problem with earlier versions, at least since 4.1.4.

I have a 64-bit Windows 7 host and both Windows XP and Linux VMs. The VMs are configured for bidirectional clipboards and those work as expected when the VMs are run from the VirtualBox GUI interface: I can copy text in a guest and paste it in the host and vice versa. When I run the same VMs using ""VBoxManage startvm <vm name> --headless"" and connect to them via the Windows RDP client, text copied in the guest not only is not available in the host's clipboard, it's not even available in the guest's.

The attached VBox.log shows clipboard-related errors from a headless Windows XP guest. The content copied during the logged session was text from a text editor (Notepad++) on the guest.",Evan Burkitt
10563,guest addition functions degrade with guest runtime,Linux,VirtualBox 4.1.8,2012-05-14T21:26:15Z,2015-10-26T14:22:30Z,2015-10-26T14:22:30Z,"Hi!

Sorry, but this is going to be a bit vague and probably hard to reproduce, but has happened to me various times, so I guess it is a bug.

I'm running VirtualBox 4.1.8 on Win7 (64 bit). I know this isn't he current version, but I cannot update the setup now and the release notes of newer versions don't indicate a fix to my problem.

Guest OS is Ubuntu 11.4, but I had the same problems with previous versions of Ubuntu too. There's one shared folder (""Temp"") in the VM mounted via fstab:

{{{
Temp		/media/Temp	vboxsf	rw,uid=1000,gid=1000	0	0
}}}


Right after starting the VM almost everything works (bidirectional clipboard, access to files in the shared folder). But even then only root may write to the shared folder, normal users get

{{{
cp: cannot create regular file `/media/Temp/foo': Permission denied
}}}

To keep my working state I take a snapshot from time to time and reset the VM to the last snapshot instead of a shutdown. So the VM runtime is can get quite long (several weeks or month).

After some time clipboard sharing stops to work completely - guest and host use seperate clipboards.

Later the shared folder also degrades and I cannot write files inside the host anymore, even as root I get an error stating that a file of the same name already exists although it doesn't.

A restart of the VM fixes all the strange effects .. for a while. It seems the restart also fixes at least the shared folder issues of a loaded snapshot too!?
",PinkyBrain
10121,Guru Meditation (HostMemoryLow) when low memory,Windows,VirtualBox 4.1.8,2012-01-02T17:09:48Z,2015-06-26T14:10:12Z,2015-06-26T14:10:12Z,"I've resumed a virtual machine, but memory low. Expected result is a Paused VM state, but the VirtualBox simple crashed with guru mediation. 
(First occurence was founded in unofficial test build 4.1.7, see comment #9 of ticket #7929
",wacher
10343,"Provide emulated hardware devices for video camera, scanners and video capture",Linux,VirtualBox 4.1.8,2012-03-17T16:47:54Z,2012-04-04T21:02:27Z,2012-04-04T21:02:27Z,"Virtualbox should add a virtual emulated device that a guest OS can use inside the VM to access video input and output devices and imaging devices such as scanners and video cameras, and capture cards, virtualbox would use the  application API of the host OSs to access the hardware through the Host OS driver, the application API for accessing the hardware drivers used by the  host OS as the backend for emulated devices provided to the guest OS. 

This is already what virtualbox does for sound cards, video cards, and network interfaces.

This in many cases is better than attempting to use the USB pass through. USB pass through does not work well when multiple OSs including many VMs need to share the device. Very rarely does pass through work right. It is just asking for trouble to occur to have many different drivers trying to directly cntrol the device. 

This is why it is best to only have one driver directly talk to the device, the Host OS driver, and then provide emulated devices inside the VMs that use the Host OS driver as a backend. The guest Os then only needs to load the driver for the device that virtualbox emulates. Virtualbox should choose to emulate a brand and model of each type of hardware that is particularly common and widely supported by many OSs.

What I suggest is have virtualbox emulate some hardware devices, like a scanner, USB web cam and a happauge video capture card. The emulation would then use the Host OSs application driver APIs as a backend and provide a virtual device in the VM for every real device accessible via the application driver APIs. Guest OSs would load the driver for the scanner, video capture card and camera device that would talk to the emulated hardware device. 

This would provide much smoother operation than  the horrid and buggy USB pass through. This is already done with video cards, network adapters and so on. ",David
10252,Switch to fullscreen with VBoxManage,Linux,VirtualBox 4.1.8,2012-02-14T16:52:49Z,2012-02-14T16:52:49Z,2012-02-14T16:52:49Z,"It would be of great value to us to be able to use VBoxManage controlvm to switch the VM window between the different display modes, such as scale, fullscreen and so on via VBoxManage. This would be a very important and valuable feature. Also, it would be valuable to as well allow auto resize to be turned on and off via VBoxManage. These would be extremely valuable and important features to us. Thank you very much, it is greatly appreciated.",David
10242,Need a way to prune snapshot tree,Windows,VirtualBox 4.1.8,2012-02-10T20:02:44Z,2012-02-10T20:02:44Z,2012-02-10T20:02:44Z,"Note: This is ''not'' another complaint about ""Delete Snapshot"". I propose a new feature, regardless of what the snapshot operations are named.

When I have a tree of snapshots, I sometimes want to remove a branch, abandoning the snapshot states, deleting their differencing images and other new disks. I just want part of the machine's state zapped, just as if I had never created it in first place.

Other than hacking XML files, the only way to do this is documented here: 
[http://srackham.wordpress.com/2010/06/18/deleting-virtualbox-snapshots/ Convoluted Pruning Method] (Warning: contains an irrelevant gripe about the name of ""Delete Snapshot"".)


There are some design issues that I've thought of:

- Should the operation be on the parent snapshot (i.e, prune all children)? Or, should it be on the topmost snapshot to be removed?

- What if Current State is one of the decendents? Disallow or offer to restore to one of the snapshots that will remaing?

- There can be only one root snapshot. It necessarily has Current State as a decendent. And with all the snapshots being removed, it would seem appropriate to make the Current State the same as the the root snapshot and then remove all the snapshot. Again, just as if I had never created the root snapshot.

- I'm not looking for a one-click ""nuke it"" operation. As with the other snapshot operations, careful, informative UI design will help users be sure that they are doing the right thing and offer appropriate options or followup actions (e.g., delete disks or keep).
",TomB
10241,Display the Current State node as the first child of its parent,Windows,VirtualBox 4.1.8,2012-02-10T15:17:20Z,2012-02-10T15:17:20Z,2012-02-10T15:17:20Z,"In the GUI's display of snapshots for a machine, the Current State node is often lost within the tree of snapshots. I would like to more easily see which snapshot is its parent. Making it the first child would be one way (whether by a preference setting or otherwise). 

Yes, it could be argued that once the current state has changed (thereby begun serving its purpose), it is the youngest state and therefore should be the last child of the snapshot parent. However, the fact that it has snapshots as siblings is irrelevant to its relationship to its parent and the ultimate purpose of restoring to that snapshot in the first place.",TomB
10182,Auto capture keyboard shortcut host key not displayed in warning info,Linux,VirtualBox 4.1.8,2012-01-19T16:18:39Z,2012-01-19T16:21:46Z,2012-01-19T16:21:46Z,"When I start VirtualBox I get 'auto capture keyboard' warning where it should be displayed keyboard shortcut, but in my case there is no key displayed.

I use Windows-menu key as host key, key is between right <Atlt> and right <Ctrl> key.",grof
10175,auto mount shared folders immediately and not just after reboot,Linux,VirtualBox 4.1.8,2012-01-16T21:27:12Z,2012-01-16T21:27:12Z,2012-01-16T21:27:12Z,"When creating a shared folder and setting auto mount it will be mounted after reboot.
It will be helpful if the folder will be mounted immediately without requiring a reboot as well.

Tested on ubuntu 11.10 guest under win7 host.

Thanks",pablop
10958,Windows guest does not recognized Broadcom 5880 smart card reader,Windows,VirtualBox 4.2.0,2012-09-18T15:28:16Z,2017-12-12T06:27:22Z,2017-12-12T06:27:22Z,"I have a Dell Latitude E6520 with a built in Broadcom 5880 smart card reader that refuses to work inside my Windows Guest OS. Some relevant notes:
* the 5880 reader works fine on my host system. 
* if I plug in an external USB smart card reader (SCR3310), that works fine inside the guest OS
* the built in 5880 reader works fine in a guest if I use VMware.

Virtual box will allow me to connect the 5880 from the USB devices menu. It then indicates a lot of flashing red/green lights on the USB icon, but my smart card software inside the guest (ActivClient) does not recognize that a reader is present. Inserting/removing the card has no effect.

My configuration:
* Windows 7 64-bit Professional on the host, 8GB RAM
* Windows 2008 R2 64-bit as the guest, 3.5GB RAM

I just updated to VirtualBox 4.2 but have tried this on a bunch of previous 4.0 and 4.1 versions. I was hoping this would eventually be fixed. My googling through the community indicates that others have had this problem and it has never been solved.

Any idea how to make this work or whether it will be fixed?
",armillz
10955,APC UPS Driver and VirtualBox issue,Linux,VirtualBox 4.2.0,2012-09-18T00:14:30Z,2014-12-19T16:51:46Z,2014-12-19T16:51:46Z,"Hi,

My host is Windows 7 64 bits Ultimate Edition with latest service pack and hotfixes. My processor is an Intel i7 950 4 cores @ 3.07 Ghz. My board is the GigaByte X58A-UD3R. While two days, I had a big problem : VirtualBox GUI was no longer starting. After investigation, I discovered that it was due to my recent installation of PowerChute Personnal Edition v. 3.0.2. It contains a driver named ""APC UPS"". After I disabled it, VirtualBox was working. But I need this driver because Microsoft's default ""HID UPS Battery"" driver makes my computer sleep has soon as it is on the battery. I have review every power options, even made a reset, nothing can explain why Windows goes to sleep immediatly. But when using PowerChute, evering is fine, but VirtualBox is not working. I have tried to reactivate the driver after starting VirtualBox, but it hangs like VirtualBox when the driver is enabled. I hope I give you enough details.",sickle
10996,Parallel port interrupts can not be used,other,VirtualBox 4.2.0,2012-09-26T06:11:10Z,2012-09-26T14:00:40Z,2012-09-26T14:00:40Z,"I have tested software that uses (and requires) a parallel port interrupt to communicate with hardware. The software is never able to detect the interrupt while running in a Windows guest. The software will run fine in a Windows host (XP or 7).

",jmb
10986,Wrong mtime on shared folders,Linux,VirtualBox 4.2.0,2012-09-22T17:45:52Z,2012-09-24T12:07:45Z,2012-09-24T12:07:45Z,"Linux ""vboxsf"" shared folder system does not set correct modification time. It only happens then file is written with some data.
attachment contains repro code (gcc testts.c ; ./a.out)
",ajax16384
11663,Host-only adapter slows down DNS resolution tremendously,other,VirtualBox 4.2.10,2013-04-01T20:32:55Z,2015-08-13T16:45:38Z,2015-08-13T16:45:38Z,"I have tried VB 4.2.10 and 4.1.24 with the same result.

I recently compiled libcurl myself for a custom client. DNS resolution was awefully slow, around 5 to 10 seconds. After a [http://curl.haxx.se/mail/lib-2013-04/0007.html post] to the mailing list. I have figured out that when I disable the Host-only adapter, resolution screams again.

With host-only disabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0    606      0 --:--:-- --:--:-- --:--:--   631
Name lookup time: 0.016000 s
Connect time: 0.187000 s
Pretransfer time: 0.016000 s
start transfer time: 0.188000 s
Total time: 0.407000 s
}}}

With host-only enabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0     47      0  0:00:05  0:00:05 --:--:--    57
Name lookup time: 4.844000 s
Connect time: 0.188000 s
Pretransfer time: 0.000000 s
start transfer time: 0.187000 s
Total time: 5.219000 s
}}}

There must be something intercepting and blocking DNS resolution for some reason.

I am on Windows XP SP3, compiled libcurl 7.29.0 with mingw/gcc 4.7.2.",Michael-O
11640,"vboxsf does not support noatime,nodiratime,discard options",Linux,VirtualBox 4.2.10,2013-03-25T01:30:53Z,2013-03-25T01:30:53Z,2013-03-25T01:30:53Z,"When using a mount (/etc/fstab), for example as follows:

ssd /ssd vboxsf noatime,nodiratime,discard 0 0

And trying to mount, you get:

[roel@localhost /]$ sudo mount -a
unknown mount option `noatime'

Removing the options one by one shows it does not support any:

unknown mount option `nodiratime'
unknown mount option `discard'

Yet, using 'defaults', i.e.:

ssd /ssd vboxsf defaults 0 0

Works fine.

This is very significant, as it does not allow for mounting a SSD with SSD recommended options (noatime,nodiratime,discard).",RoelV
11758,"""Take Screenshot"" just makes black PNG ==> Fixed in SVN",Linux,VirtualBox 4.2.12,2013-04-26T15:04:10Z,2019-02-08T12:32:17Z,2019-02-08T12:32:17Z,"If I hit '''Take Screenshot''', all I get is a black PNG. I've attached the PNG. I've also attached a user-generated screenshot, created from hitting PrtScn while VirtualBox does not have the focus (and later cropped with GIMP).

System state:
* guest is Ubuntu 13.04, fresh install
* Guest Additions installed, has been rebooted
* host is Windows 8 x64

If you look at the manually-taken screenshot, you'll notice a problem with z-order on the windows: even though Chromium is below gedit, Chromoium's '''chrome web store''' content is displaying above gedit. I'm filing a separate issue with Ubuntu over this, but that should not affect VirtualBox's ability to take a screenshot, as it really should just be slicing off a copy of the final rendered output.",Aren Cambre
11712,Install Makes Windows 8 Host Boot Fail,other,VirtualBox 4.2.12,2013-04-15T00:12:55Z,2015-04-09T12:31:56Z,2015-04-09T12:31:56Z,"This is bug: When I run the Virtualbox 4.2.12 install with its default settings, Windows will not finish booting on the next start up. I'll leave it try to boot for a while, kill the power, start it up and repeat until the Windows 8 auto recovery kicks in. Windows 8 will do a system restore t the point just before installing Virtualbox. Virtualbox will no longer be installed and the system will reboot  and operate normally. I ran the whole install Virtualbox, system repair cycle several times to confirm nothing else I did was tied to the problem. I eventually installed Virtualbox by not installing anything that looked like it was related to networking. With that install configuration Windows booted properly several times. I ran several clients in Virtualbox and they all were able to connect to the internet.

Machine Information: I am running Windows 8 x64 as my host. It is not an upgrade. I did a fresh install from CD, though I have since installed numerous other items. The laptop runs an AMD A8-4500, has 16 GB of RAM, and a sizable SSD. Because I develop for windows phone, I have hyper-v enabled and it has several network adapters setup. I use Virtualbox because hyper-v is inadequate for some things, so I have to have them both concurrently. I had previously used them concurrently without issue, but then I kept running into wireless networking issues (no internet access over WI-FI) definitively caused by Virtualbox somehow. As such I had no choice but to uninstall Virtualbox (though Windows seemed not to remove all of the settings related to Virtualbox's network adapter) and to start using hyper-v in its place.  Hyper-v was inadequate in some regards, so I installed Virtualbox 4.2.12 and got the above bug.

If I can help fix this issue or provide any useful information, even if it means retesting that whole mess installing nightly builds or anything else, please let me know as I am more than happy to help! I can be contacted directly if needed at [reportedbyname] {A T} [gmail address]",jmessenger235
11900,Windows host cannot see / follow symlinks in shared folder from Linux guest,Linux,VirtualBox 4.2.12,2013-06-25T15:36:49Z,2014-04-24T11:14:35Z,2014-04-24T11:14:35Z,"I'm running an ubuntu guest on a windows 7 host. I have shared folders setup and working via a Vagrant file. My shared folder has a bunch of development files in it created using the Ubuntu guest, nearly all of which I can access from the windows host. 

{{{
$ ls -lah                              
total 13                                                                                  
drwxrwxrwx 1 vagrant vagrant 4096 Jun 25 14:06 ./                                         
drwxrwxrwx 1 vagrant vagrant 8192 Jun 24 19:49 ../                                        
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:51 brunch -> ../brunch/bin/brunch*            
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 cake -> ../coffee-script/bin/cake*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 cleancss -> ../clean-css/bin/cleancss*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:49 coffee -> ../coffee-script/bin/coffee*     
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 express -> ../express/bin/express*         
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 grunt -> ../grunt-cli/bin/grunt*           
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 jade -> ../jade/bin/jade*                  
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 nodemailer -> ../nodemailer/bin/nodemailer*
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 stylus -> ../stylus/bin/stylus*            
-rwxrwxrwx 1 vagrant vagrant   20 Jun 25 14:04 test*                                      
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:02 test2 -> test*                             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 25 14:05 test3 -> ../brunch/bin/brunch*             
lrwxrwxrwx 1 vagrant vagrant    0 Jun 24 19:50 uglifyjs -> ../uglify-js/bin/uglifyjs*     
vagrant@mwalters:~/development/clp-web/node_modules/.bin$                                                                                                 
}}}

What's shown above (ls -lah run on Ubuntu guest) - 

1. 'test' file, created on Ubuntu guest is visible on Windows 7 host
2. 'test2' symlink to 'test', created on Ubuntu guest is visible on Windows 7 host
3. 'test3' symlink to file in another directory, created on Ubuntu guest is *not* visible on Windows 7 host (nor are any of the others which follow the same pattern). 

{{{
$ ls -lah                                                                  
ls: brunch: No such file or directory                                      
ls: cake: No such file or directory                                        
ls: cleancss: No such file or directory                                    
ls: coffee: No such file or directory                                      
ls: express: No such file or directory                                     
ls: grunt: No such file or directory                                       
ls: jade: No such file or directory                                        
ls: nodemailer: No such file or directory                                  
ls: stylus: No such file or directory                                      
ls: test3: No such file or directory                                       
ls: uglifyjs: No such file or directory                                    
total 7.0k                                                                 
drwxr-xr-x   15 mwalters Administ     4.0k Jun 25 10:06 ./                 
drwxr-xr-x   37 mwalters Administ     8.0k Jun 24 15:50 ../                
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test*              
-rwxr-xr-x    1 mwalters Administ       20 Jun 25 10:04 test2*                                                                             
}}}

What's shown above (ls -lah run on Windows 7 host) - 

Notice none of the files are recognized as symlinks. test2 is a symlink to test and all of the other files, including test3, are symlinks to files in other directories. None of them are registering or followable from the Windows host. 

Here is a copy of my Vagrant file: 

{{{
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(""2"") do |config|
  config.vm.box = ""precise32""
  config.vm.box_url = ""removed to allow me to post""

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  config.vm.network :forwarded_port, guest: 9983, host: 9983

  config.vm.hostname = ""#{ENV['USERNAME']}.dev""

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network :private_network, ip: ""192.168.33.10""

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  config.vm.synced_folder ""../../"", ""/home/vagrant/development""


  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
    vb.customize [""modifyvm"", :id, ""--cpus"", ""8""]
    vb.customize [""modifyvm"", :id, ""--memory"", ""12288"", ""--ioapic"", ""on""]
    vb.customize ['storagectl', :id, '--name', 'SATA Controller', '--hostiocache', 'on' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development', '1' ]
    vb.customize ['setextradata', :id, 'VBoxInternal2/SharedFoldersEnableSymlinksCreate/home/vagrant/development/*', '1' ]
    vb.customize [""modifyvm"", :id, ""--natdnshostresolver1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--natdnsproxy1"", ""on""]
  end

config.vm.provision :puppet do |puppet|
    puppet.manifests_path = ""manifests""
    puppet.manifest_file  = ""init.pp""
  end
end
}}}

Additional info here: https://forums.virtualbox.org/viewtopic.php?f=6&t=56097&p=259861#p259861",mateodelnorte
11876,should change char to wide character in VBoxStub.cpp,all,VirtualBox 4.2.12,2013-06-18T07:54:47Z,2013-06-18T07:54:47Z,2013-06-18T07:54:47Z,"
If a user name is not english(such as East Asia Lang.-Korean, Japanese..), current stub code can not extracts msi and cab file.

or one of way is

do not use user's temp folder. (like C:\TEMP_VIRTUALBOX) but it is not good way.

",Woof
11860,error starting VM in batch when the path to VM have Unicode characters,all,VirtualBox 4.2.12,2013-06-13T04:57:57Z,2013-06-13T07:02:18Z,2013-06-13T07:02:18Z,"When I start <<VirtualBox.exe --startvm ""path_to_VM"">> it works only if path_to_VM doesn't have some Unicode characters (specific to a language, like the u with 2 dots above from Munchen).
It shows an error message saying that the VM was not found and it displays the path with those Unicode characters doubled into some strange ones.
If I start <<VBoxManage.exe  --startvm ""path_to_VM""/UUID>> or <<VirtualBox.exe --startvm UUID>> it works with any combination.
But I prefer using <<VirtualBox.exe --startvm ""path_to_VM"">> so could you please fix it...?
Thank you.

Regards, Cosmin",Cosmin
11846,Setting the medium description not implemented,all,VirtualBox 4.2.12,2013-06-06T11:17:12Z,2013-06-07T13:56:08Z,2013-06-07T13:56:08Z,"Setup
Host: Core i5 3gen (quad core), 16GB RAM, Windows 8 Pro 64 bits.
Guest: 4 cores, 4GB RAM, 2 alread, no OS installed.

I created a disk and attached to a VM with vboxmanage. While the attaching was successful, it gave me some errors:

C:\Users\luka\Desktop>vboxmanage createhd --filename ""E:\asm\asm-vol00.vdi"" --size 20480 --variant Fixed
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Disk image created. UUID: 706f7563-882f-4da2-91c5-3a593dcd957a

C:\Users\luka\Desktop>vboxmanage storageattach ""RAC n1"" --storagectl SATA --port 2 --type hdd --medium ""E:\asm\asm-vol00.vdi"" --mtype shareable --comment ""Disco para ASM""
VBoxManage.exe: error: Method Medium::put_Description is not implemented
VBoxManage.exe: error: Details: code E_NOTIMPL (0x80004001), component Medium, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Description)(bstrComment.raw())"" at line 685 of file VBoxManageStorageController.cpp",chesterman
11889,OpenGL Warning,Windows,VirtualBox 4.2.14,2013-06-22T10:50:43Z,2016-10-20T17:16:30Z,2016-10-20T17:16:30Z,"{{{
OpenGL Warning: State tracker is being re-initialized..

OpenGL Warning: Assertion failed: g_pAvailableContexts[ctx->id] == ctx, file D:\tinderbox\add-4.2\src\VBox\GuestHost\OpenGL\state_tracker\state_init.c, line 346
}}}

P.S. Nothing was listed in VBox.log",nothx
12048,No OpenGL Support for Windows 8,Windows,VirtualBox 4.2.16,2013-08-23T13:46:44Z,2018-09-29T13:25:25Z,2018-09-29T13:25:25Z,"Host: Windows 7 64 bit
Guest: Windows 8 32 bit
Problem: No opengl GL support.

I'm trying to get accelerated opengl in my Windows 8 guest. All I get is the Microsoft Software OpenGL 1.1 driver. 

Additional Info:
- guest additions installed and selected the D3D support during installation
- 3D hardware acceleration enabled in the VM settings
- Direct 3D 9 acceleration works

To make sure it's not a problem with my host I installed Windows 7 32 bit as a guest. In this virtual machine the OpenGL Adapter of the host seems to be passed through to the guest.

I will attach a log for the windows 8 guest where OpenGL is not working.",muhkuh
11976,long paths  (>260chars) cannot be created using a host:win + guest:linux setup,Linux,VirtualBox 4.2.16,2013-07-19T17:23:19Z,2018-02-23T21:23:47Z,2018-02-23T21:23:47Z,"From https://github.com/mitchellh/vagrant/issues/1953 and https://github.com/isaacs/npm/issues/3670, VirtualBox on windows cannot generate paths longer than ~260 characters on windows, despite windows supposing UNC paths to allow for ~32k character paths. This means that using things like Vagrant, with a project that uses node/npm, is blocked by VirtualBox because node module dependencies (but also just any deeply nested software project being tested in a virtualbox VM) end up having paths that are longer than the standard 260 character limit.

Somewhere, VirtualBox is not communicating the correct error from host to guest OS; it would be extremely useful if this was solved somehow (allowing UNC paths by default? perhaps something else altogether)",Urrich
11980,guest additions should write system time to RTC after adjusting it,Linux,VirtualBox 4.2.16,2013-07-22T13:13:14Z,2016-03-11T12:45:48Z,2016-03-11T12:45:48Z,"When booting a Linux distribution using systemd, the system time is not automatically written to the RTC during shutdown. For further information & rationale, see <http://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html>.

As a result, booting my system under VirtualBox results in the following:

{{{
Jul 22 03:46:06 wintermute kernel: rtc_cmos rtc_cmos: setting system clock to 2013-07-22 02:46:03 UTC (1374461163)
...
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: Superblock last write time is in the future.
Jul 22 03:46:07 wintermute systemd-fsck[443]: (by less than a day, probably due to the hardware clock being incorrectly set).  FIXED.
Jul 22 03:46:07 wintermute systemd-fsck[443]: /dev/sdb1: clean, 340335/39321600 files, 138917904/157286139 blocks
...
Jul 22 03:46:08 wintermute systemd[1]: Started LSB: VirtualBox Linux Additions.
Jul 22 13:57:43 wintermute systemd[1]: Time has been changed
}}}

After boot, we can observe the RTC is still wrong:

{{{
$ date
Mon 22 Jul 14:10:15 BST 2013

# hwclock -r
Mon 22 Jul 2013 03:58:44 BST  -0.070616 seconds
}}}

After the guest editions have set the system clock from the host clock, they should set the hardware clock to match. That is, perform the equivalent of `hwclock --systohc`.",Sam Morris
12064,Suddenly no VM's will start - all give a RPC_S_SERVER_UNAVAILABLE error at 0%,all,VirtualBox 4.2.16,2013-09-03T14:11:55Z,2015-07-06T19:51:53Z,2015-07-06T19:51:53Z,"I was in the process of creating a new machine, and it wouldn't start (more in a bit) - I then tried to start up a few old, reliable machines, and got the same behavior.  The only change was that on startup a new version was mentioned; I installed it and saw this behavior.  After some web research I went back to version 4.2.12, and still see the same problem - but this may have to do with having installed the 4.2.16 version and then, perhaps, and incomplete removal.  I suppose technically this applies to both versions, as the problem shows up in both.

When I try to start any machine, I see a small popup, ""Starting virtual machine..."" and ""0%"" - that never changes.  My host OS is Windows 7 Ultimate; I have to kill the process for that machine manually.  When I do, I get a popup from Virtualbox; the detailed error message is:
Result Code: 
  RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
  Component: 
  ProgressProxy
  Interface: 
  IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Web searching shows this, or something like it, was a problem years ago, but apparently fixed.  I found current ticket #10747 that looks similar.

The VM I was trying to start as the main test case is a Windows 98 machine, fairly vanilla.  I certainly haven't changed any of its attributes (e.g., hardware acceleration options) since it last ran.

I have 17 VM's, all of some level of importance; it would not be a minor effort to recreate them, even if that helped.  I tried to create a new Windows 2000 machine from scratch and had the same problem, that is the exact same hang and detailed error message.

I'm willing to invest some time to help fix it, if any testing I can do on this end might help.",Bryan Bentz
11995,Saving Ubuntu guest in full-screen mode causes guest X session hang when resuming. Windows 8 host.,Linux,VirtualBox 4.2.16,2013-07-27T04:41:12Z,2015-02-11T23:24:07Z,2015-02-11T23:24:07Z,"Host is Windows 8 64-bit, guest is Ubuntu 13.04 64 bit.

Everything works fine including saving state & restoring when the guest is in a normal window.  But if the guest is saved while in full-screen mode, then when the guest is restored it is unresponsive, cursors do not flash, etc.

However the ""hung"" guest does respond to Host-F1 and switches to a VT where you can log and kill the X server, after which normal operation resumes.

So saving or restoring in full-screen-mode breaks something related to sending events to the guest X server.

HOW TO REPRODUCE:


{{{
Start Ubuntu guest
Go to full screen (Host-F)
Put cursor at bottom of screen to get vbox menu, then
Machine->Close-Save Machine State
}}}


Restart the saved VM.  It hangs.

(to recover: Host-F1, log in as root and kill the X server process)

I'll attach two log files (one from the session which ended with a save while in full-screen mode), the other from the restarted VM with the hung X server.",Jim Avera
12063,Using Windows 8.1 RTM and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems,Windows,VirtualBox 4.2.16,2013-09-03T07:29:07Z,2014-11-29T22:11:23Z,2014-11-29T22:11:23Z,"Using Windows 8.1 RTM single language (English, activated with serial provided with PC) and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems. The display becomes dim and HDD spins down (on notebook) but the power led is on and coolers continue to work.
Changing drivers for network cards, video, motherboard, etc doesn't help.
Reinstalling Virtualbox with bridge networking switched off (NAT is on) helps to completely resolve the issue.
Devices used: HP envy 4 touchsmart, Acer iconia tab w700.",Immunologist
12162,Serial Port output slows down VM,Linux,VirtualBox 4.2.18,2013-10-06T13:53:10Z,2019-09-18T22:57:01Z,2019-09-18T22:57:01Z,"I have a linux VM, with a kernel command-line saying console=ttyS0,115200 

With no serial port enabled, or a disconnected serial port, there are no problems. As soon as I redirect the serial port to a local file, the guest slows down significantly.

Booting the same guest using VMware Player (with the serial port also redirected to a file) does not show such a large performance penalty.

Alternatively, is there a faster solution to get /dev/console output onto a file on the host?",AxelFontaine
12168,Oracle Virtualbox manager has stopped working,Linux,VirtualBox 4.2.18,2013-10-08T05:27:51Z,2018-02-04T11:03:41Z,2018-02-04T11:03:41Z,"I have the following scenario:

VirtualBox 4.2.18
Host: Windows 7 Enterprise 64-bit 6GB RAM
Guest: Oracle Linux Release 6.4 32bit 2GB RAM

Virtualbox stopped working twice:
1. After press Reboot button when installation progress had been finished
2. After press Finish button in the last step(Kdump) of configuration process..

I have checked similar threads who had posted the same error at the same stage but there was no resolution or response provided and hence I am creating this ticket.

Thanks,
Nayagam",Nayak
12087,VirtualBox.exe fails to run,all,VirtualBox 4.2.18,2013-09-09T11:42:00Z,2016-09-28T10:54:18Z,2016-09-28T10:54:18Z,"VirtualBox.exe failed with the message:[[BR]]
Callee RC: E_NOINTERFACE (0x80004002)[[BR]]

VBoxSVC.log reports:[[BR]]
Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false[[BR]]

Running as administrator -> no error[[BR]]

Previous version (4.2.16) does not have this issue.",yefkov
13625,Can't start virtualBox,Linux,VirtualBox 4.2.18,2014-11-19T16:41:16Z,2014-11-20T16:25:38Z,2014-11-20T16:25:38Z,"Échec de l'ouverture de session pour la machine virtuelle Linux Mint 17.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Code d'erreur : E_FAIL (0x80004005)
Composant : Console
Interface : IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}

",EricG
11096,No Host-Only Network Adapter after upgrading from 4.2.0 to 4.2.2,all,VirtualBox 4.2.2,2012-10-21T01:05:49Z,2012-10-21T03:25:17Z,2012-10-21T03:25:17Z,"
There appears to be a flaw in the Windows installer script, probably custom actions.

Upgrading from 4.2.0 to 4.2.2 on a Windows 7 x64 SP1 host produces the following:

""--Error Renaming Connection-- Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.""

The msi logs indicate the installation was 'sucessful'. However in addition to the 'Proxy' issue already reported, the Host-only Networks section of VirtualBox Settings is completely blank.
",Bob Kosch
14557,with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile,all,VirtualBox 4.2.32,2015-09-08T15:50:40Z,2015-09-08T15:54:29Z,2015-09-08T15:54:29Z,with windows 7 hosts in a windows domain virtualbox saves some info in roaming profile which then break vms when logging into another pc on same domain,clive darra
11133,On a Windows 8 host VM microphone does not work in an XP guest,Windows,VirtualBox 4.2.4,2012-10-27T18:17:10Z,2015-04-03T06:00:37Z,2015-04-03T06:00:37Z,"Host: Windows 8 64, MB ASUS M2N68 AM-PLUS integrated audio
Guest: Windows XP, ICH AC97

The guest sees the microphone, but does not react when I am speaking into it.

The same VM works on Windows 7 host.",Andrey Gerasimenko
11183,Nonexistent host networking interface,Windows,VirtualBox 4.2.4,2012-11-09T11:15:50Z,2015-02-23T08:06:03Z,2015-02-23T08:06:03Z,"The following error message is displayed when restoring a VM from a Saved state:


{{{
Failed to open a session for the virtual machine [VM NAME].

Nonexistent host networking interface, name 'Atheros AR8131 PCI-E Gigabit Ethernet Controller (NDIS 6.20) #2' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
}}}


This occurs when the following is performed:

1. VM is running fine, and in Bridged networking mode connected to the LAN network interface. This interface is connected to a wireless router
2. The VM state is saved
3. Host is put to sleep
4. Wireless router is unplugged
5. Host is woken up
6. A different network device, in this case a network hub is plugged into the LAN
7. The VM is started again, and the error appears

The workaround is to delete the savestate and start the VM again.

For interest, the VM is Windows 2012 with 8GB RAM, 2 CPUs and apart from Shared Folders there is nothing fancy configured.

This behaviour does occur for all OSs and configurations.

I would assume this has something to do with when a network interface is disabled and enabled again, it adds ""#2"", ""#3"" next to it. Note, though that no setting in the Host (in Windows 7) shows that the network interface has been renamed, this appears to be the internal NIC name.",georgeby
11329,SDK - IGuestSession - (conceptual) bug with CopyTo/From(),Windows,VirtualBox 4.2.4,2012-12-25T01:44:17Z,2015-02-03T17:14:39Z,2015-02-03T17:14:39Z,"There seems to be a (conceptual) bug with the IGuestSession::CopyTo() and CopyFrom(). The internal code is relying on a 30 seconds timeout for the whole copy operation to finish (because it's counting on some vbox_cat internal process spawn within the Guest). Obviously that fixed timeout is not realistic for large files such as 500MB-1GB long. Not to mention that the host file may not be really on the physical host itself, but located somewhere on the network.

I get into the same issue when I'm using the equivalent VBoxManage command.",smihaila
11231,Recursive copyto does not create folders and fall if it not exists on destination VM,Windows,VirtualBox 4.2.4,2012-11-23T13:03:05Z,2014-10-27T18:54:22Z,2014-10-27T18:54:22Z,"I want to recursively copy files to a VM. But when copying occurs directory, an error occurs.
In version 4.1.18 ""--recursive"" worked. But there were unexpected interruption when transferring files.

{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" guestcontrol ""VM"" copyto ""c:\\AutoTest\\"" ""c:\\Test\\"" --username ""Administrator"" --password ""***"" --verbose --recursive

Copying from host to guest ...
Directory ""c:\\Test\"" already exists
Source: C:\\AutoTest\
Processing host directory: C:\\AutoTest
File: Exchange.exe
Directory ""c:\\Test\"" already exists
Copying ""C:\\AutoTest/Exchange.exe"" to ""c:\\Test\Exchange.exe"" ...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
File: ExchangeConfiguration.exe
Copying ""C:\\AutoTest/ExchangeConfiguration.exe"" to ""c:\\Test\ExchangeConfiguration.exe"" ...
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Directory: icons
Processing host directory: C:\\AutoTest/icons
File: about.png
VBoxManage.exe: error: Unable to retrieve requested information.
VBoxManage.exe: error: Error processing ""C:\\AutoTest"", rc=VERR_GENERAL_FAILURE
}}}

{{{
01:07:04.784606 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={57eb82a8-822b-42c1-9d1c-5c54bc3d3250} aComponent={GuestSession} aText={Unable to retrieve requested information}, preserve=false
}}}",angelx
11137,BIOS call int13h cannot access more than 4 HDDs on the SATA or SCSI controller.,all,VirtualBox 4.2.4,2012-10-28T13:06:25Z,2014-04-06T21:32:35Z,2014-04-06T21:32:35Z,"When I set up 6 HDDs on SATA controller, BIOS in VirtualBox does not recognize last 2 HDDs. If the last 2 HDDs are connected to SCSI controller, i.e. 4 HDDs on SATA and 2 HDDs on SCSI, all the 6 HDDs can be accessed via int13h.

Similarly, more than 4 HDDs on SCSI and SAS controller cannot be accessed by int13.

This causes boot failure problem of linux in software RAID5 partition with 6 HDDs.

The ""User Manual"" says VirtualBox supports 4 HDDs to IDE, 30 HDDs to SATA, 15 HDDs to SCSI and 8 HDDs to SAS controller. Since real PC BIOS can access all the HDDs connected to SCSI controller as usual, this is a bug of VirtualBox BIOS, I believe.

This problem is also in version 4.2.2 and 4.2.0, and maybe older version.
",Yano
11517,VBoxSDL error before launching VM,all,VirtualBox 4.2.6,2013-02-23T11:11:45Z,2019-12-15T12:32:47Z,2019-12-15T12:32:47Z,"In version 4.2.6 under Windows 7 SP1 x64, when trying to start a VM using VBoxSDL, I get the following error (regardless of the VM) :
{{{
SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
[[BR]]
It also happens from a freshly created VM :

{{{
C:\Program Files\Oracle\VirtualBox>vboxmanage createvm --name test --ostype Debian_64 --register
Virtual machine 'test' is created and registered.
UUID: 2cbfe35a-fd26-44e3-90a3-9a6e31f406f3
Settings file: 'D:\VMs\VirtualBox\test\test.vbox'

C:\Program Files\Oracle\VirtualBox>vboxsdl --startvm test
Oracle VM VirtualBox SDL GUI version 4.2.6
(C) 2005-2012 Oracle Corporation
All rights reserved.

SDL Error: 'DirectInputDevice::SetDataFormat: Invalid parameters'
}}}
No VBox.log is generated and nothing appears in the VBoxSVC.log.",Max D
11375,Running Virtualbox causes high CPU usage in Elan Touchpad drivers,all,VirtualBox 4.2.6,2013-01-09T23:24:08Z,2017-05-16T18:05:57Z,2017-05-16T18:05:57Z,"Seeing high cpu usage on etdctrl.exe on Win 8 64bit host when any VM is started. Process must be killed manually and restarted to regain touchpad features. 

etdctrl.exe is part of the Elan Touchpad driver suite.

Host is on Win 8 64bit, Acer Aspire S7-391. ",tmk
11496,Vboxmanage and host-only interfaces,all,VirtualBox 4.2.6,2013-02-16T08:28:58Z,2017-03-12T09:28:34Z,2017-03-12T09:28:34Z,"Original findings and history can be found here -> https://forums.virtualbox.org/viewtopic.php?f=6&t=54119
[[BR]]

Under Windows, when trying to use host-only adapter commands on vboxmanage, they fail intermittently and return this:
{{{
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

Taken from the forum post :
{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       192.168.74.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       172.17.101.143
NetworkMask:     255.255.0.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

{{{
c:\Program Files\Oracle\VirtualBox>Vboxmanage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            a5f0012b-7729-4d31-8d4a-744f67e13797
DHCP:            Disabled
IPAddress:       192.168.123.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:dc5b:cdf6:ea70:c8a2
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:94:7b
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101.143 --netmask 255.255.0.0

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

c:\Program Files\Oracle\VirtualBox>ipconfig

Windows IP Configuration
--snip--
Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::dc5b:cdf6:ea70:c8a2%25
   IPv4 Address. . . . . . . . . . . : 172.17.101.143
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
--snip--
}}}

Again, this problem is very intermittent.

4.2.4 & 4.2.6 currently broken.",Max D
11338,OS/2 VBOXSERVICE.EXE 4.2.6 not working,other,VirtualBox 4.2.6,2012-12-28T23:46:59Z,2013-03-27T23:13:02Z,2013-03-27T23:13:02Z,The guest additions for os/2 appear to be updated for 4.2.6 however they are not mentioned in the changelog.  When using VBOXSERVICE.EXE in os/2 (4.2.6 r82870 Dec 19 2012 15:02:33) my os/2 guest crashes with a TRAP 000d error.  I reverted VBOXSERVICE to 4.2.2 (r81494 Oct 18) and the guest is working again.,walter380
11514,Time sync: incorrect host time,Linux,VirtualBox 4.2.6,2013-02-22T13:49:40Z,2013-02-26T15:01:24Z,2013-02-26T15:01:24Z,"I have noticed that I do not get the time set correctly on my virtuals machines. They do sync but are always behind the host's time (which is set per ntp correctly) and funnily the times between several VMs running on the same host vary.

When I started to dig for the reason I started VBoxService with -vvv and saw that the Host time displayed there was not the actual time of the host (i.e. the windows machine on which the VMs are running).

I expected the time shown in the log as ""Host:"" would be the host time, e.g:
{{{
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z
}}}
Unfortunately it differs from the hosts time. Even more suspicious: it differs differently on various VMs of the same host.
Could this be the reason why time sync does not work correctly?

Below more debug output.

{{{
root@orpdm-03:~#  /usr/sbin/VBoxService -f -vvv --enable-timesync --timesync-interval 1000
VBoxService 4.2.4 r81684 (verbosity: 3) linux.amd64 (Oct 26 2012 19:49:17) release log
00:00:00.002083 main     Log opened 2013-02-22T13:37:48.290070000Z
00:00:00.002159 main     OS Product: Linux
00:00:00.002180 main     OS Release: 3.2.0-37-generic
00:00:00.002199 main     OS Version: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002388 main     OS Service Pack: #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013
00:00:00.002412 main     Executable: /opt/VBoxGuestAdditions-4.2.4/sbin/VBoxService
00:00:00.002415 main     Process ID: 31071
00:00:00.002418 main     Package type: LINUX_64BITS_GENERIC
00:00:00.002608 main     4.2.4 r81684 started. Verbose level = 3
00:00:00.002766 main     Initializing services ...
00:00:00.003517 main     Service client ID: 0x24
00:00:00.003767 main     VMInfo: Property Service Client ID: 0x25
00:00:00.003810 main     VBoxServiceBalloonInit
00:00:00.003847 main     MemBalloon: VbglR3MemBalloonRefresh failed with VERR_PERMISSION_DENIED
00:00:00.003942 main     Service 'memballoon' was disabled because of missing functionality
00:00:00.003965 main     VBoxServiceVMStatsInit
00:00:00.004058 main     VBoxStatsInit: New statistics interval 0 seconds
00:00:00.004102 main     VBoxServiceAutoMountInit
00:00:00.004353 main     VBoxServiceAutoMountInit: Service Client ID: 0x26
00:00:00.004393 main     Starting services ...
00:00:00.004414 main     Starting service     'control' ...
00:00:00.004706 control  Waiting for host msg ...
00:00:00.004831 main     Starting service     'timesync' ...
00:00:00.005097 main     Starting service     'vminfo' ...
00:00:00.005246 timesync VBoxServiceTimeSyncWorker: Host:    2013-02-22T13:39:47.465000000Z    (MinAdjust: 100 ms)
00:00:00.005341 vminfo   Writing guest property ""/VirtualBox/GuestInfo/OS/Product"" = ""Linux""
00:00:00.005413 timesync VBoxServiceTimeSyncWorker: Guest: - 2013-02-22T13:37:48.293063000Z => 119 171 937 000 ns drift
00:00:00.005509 timesync VBoxServiceTimeSyncAdjust: adjtime by 119 171 937 000 ns
}}}",Markus
11497,"When starting on user login in windows in fullscreen mode, vb loses focus",Linux,VirtualBox 4.2.6,2013-02-16T15:00:00Z,2013-02-16T15:00:00Z,2013-02-16T15:00:00Z,"I have set up virtualbox to start up when the Windows user logins, By setting up the virtualbox command line tool to be run in a script on Windows user login, to start virtualbox on start up from a script when the windows user logs in. I wish for it to be started in fullscreen mode so the Windows UI is not visible at all, including the Windows taskbar covered up.

The problem is, after virtualbox starts when the user logs in, the Windows taskbar appears at the top of the screen even though virtualbox is in fullscreeen mode, and virtualbox loses focus. Virtualbox needs to add a stayontop option for use from the virtualbox command line tool to tell virtualbox to stay on top and regain focus if virtualbox happens to lose focus and make sure the windows taskbar stays covered up.

I also request a ""screenmode"" vboxclient option for specifying display mode to use, such as ""fullscreen"", when the vboxclient virtualbox command line program is used, to assure that virtualbox is started in fullscreen mode, by supplying this fullscreen option to vboxclient, when started from with vboxclient from my startup script. ",David
11397,Clipboard stops working,Linux,VirtualBox 4.2.6,2013-01-16T17:05:09Z,2013-01-16T18:17:25Z,2013-01-16T18:17:25Z,"The clipboard stops working completely (not just host<->guest, but on the guest itself) when a remote desktop session is established with the guest.

The clipboard on the guest can be brought back to life if the 'Shared Clipboard' is 'disabled' on the 'Devices' menu.

I am also remote-desktop'ed into the host when this problem occurs.",cruvis
11330,SDK - IGuestSession - enhance guest process management functions,Windows,VirtualBox 4.2.6,2012-12-25T01:52:08Z,2012-12-25T01:52:08Z,2012-12-25T01:52:08Z,"Hi,

I'm working on a custom-made test automation framework and I was having high hopes with VirtualBox for my VM-based automation needs.
I'd like to see IGuestSession interface augmented with methods such as:

-Get list of ALL guess processes, not only those explicitly created through IGuestSession::CreateProcess()

-Bind/attach to an EXISTING guest process (not previously created via IGuestSession) and get an IProcess object wrapper around it, in order to be able to sync on it (i.e. wait for termination)

Considering how powerful the level of VirtualBox automation is currently (at least for windows guests - i.e. things like auto-logon, process execution, file injection/copying), tt would be a real pity not to have a 1st-class, built-in solution for more complete process management.

By having such support, we wouldn't have to rely on activating network support on the windows guest OS and mess with Microsoft Process/Debug diagnostics API and SMB/RPC calls (i.e. see Process.GetProcesses(string machineAddress) method in .NET Framework).",smihaila
11313,Can't assign guest audio to dedicated sound device on Host,all,VirtualBox 4.2.6,2012-12-20T22:40:02Z,2012-12-20T22:40:02Z,2012-12-20T22:40:02Z,"I would like to assign all audio from a Guest into a specific audio device so that my kids can listen to audio on the Guest while I work on the host or other guests. I am using Windows 7 64-bit as Host.

The simplest solution would be to allow the guest audio to be directed to a specific audio device. This is possible using windows APIs, but in absence of choosing a device, VirtualBox sends all audio to ""Default Device"", which is then the same as all other Guests, as well as the Host. Therefore, all audio is mixed into 1 stream, which prevents isolation.",random_luser
11589,Don't create a desktop shortcut by default,all,VirtualBox 4.2.8,2013-03-13T19:10:55Z,2015-10-21T13:03:30Z,2015-10-21T13:03:30Z,"Please note that Microsoft specifically mentions this point in the Windows Customer Experience Guidelines for developers:

QUOTE BEGIN
If you do only one thing...
Don't abuse the desktop—keep users in control. If your target users are likely to use your program frequently, provide an option during setup to put a shortcut on the desktop, unselected by default.
QUOTE END

http://msdn.microsoft.com/en-us/library/windows/desktop/aa511450.aspx

While you're at it, remove the quick launch shortcut default as well.",gencha
12933,unable to save machine state in case of host reboot/shutdown event,all,VirtualBox 4.3.10,2014-04-10T17:04:46Z,2016-04-25T13:20:37Z,2016-04-25T13:20:37Z,"Host: Windows 7 SP1 x64[[br]]

When a shutdown/reboot event is issued on the host OS, the VirtualBox frontend presents, to the user, the Close VM window, allowing the user to save or properly shutdown the guest. But saving the VM state isn't possible, because the VirtualBox COM service (VBoxSVC) exits immediately. The user is only able to shut down or power off the VM. When choosing to save the state, the user encounters this error:[[br]]

{{{
Failed to save the state of the virtual machine .

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
}}}",Mihai Hanor
14049,VirtualBox NAT implementation tcp keep-alive problem,Linux,VirtualBox 4.3.10,2015-04-14T21:59:14Z,2015-04-15T13:25:24Z,2015-04-15T13:25:24Z,"Guests behind VirtualBox NAT have problem using TCP keepalive.
When connection with remote is lost (i.e. even host OS reports no connection), VirtualBox NAT implementation continues to reply to guest OS keepalive requests, hence guest cannot detect TCP connection loss.[[BR]]

Encountered on:
Host OS: Windows 7 Professional 64
VirtualBox 4.3.10
Guest OS: Ubuntu 12.04 32

The same problem was reported by two users on the forum: https://forums.virtualbox.org/viewtopic.php?f=7&t=52384
",Aegis
12910,respect host-only settings on update / upgrade,Linux,VirtualBox 4.3.10,2014-04-04T08:22:32Z,2015-02-20T12:51:47Z,2015-02-20T12:51:47Z,"Every time I updated / upgraded my VBox installation my Host-only Adapter settings are changed. I have to reconfigure my settings all the time. This is very annoying, because the problem exists for years.",kirsche40
13028,Vertical scrollbar scrolls very slow with mouse-wheel,Windows,VirtualBox 4.3.10,2014-05-14T00:11:37Z,2014-05-15T12:34:56Z,2014-05-15T12:34:56Z,The 'Auto-resize guest display' is disabled. The guest screen size is set to 1280*1024 while the host screen size is 1366*768. At this time the vertical scrollbar displays but it scrolls very slow with mouse-wheel. It will be better if the scroll speed can be adjusted and mouse-wheel work outside the vertical scrollbar a bit.,abelli
13108,Guest mouse cursor range limited without guest additions installed,all,VirtualBox 4.3.12,2014-06-08T21:50:38Z,2018-12-11T13:28:24Z,2018-12-11T13:28:24Z,"When using a guest OS without VirtualBox Guest Additions installed, the guest mouse cursor can only be moved within a part of the guest desktop.  Before the guest mouse cursor reaches the edge of the desktop, the cursor suddenly jumps outside the guest window and appears on the host OS desktop.

The problem happens in version 4.3.12 and 4.2.24 as well as previous versions.  The specific host OS is Windows 7 Professional SP1 and the guest OS is Windows XP SP3 (without guest additions).   The same problem happens for other guest operating systems without guest additions installed.

The display resolution on the host OS is higher than that of the guest OS.  The host OS resolution is 1680 x 1050.  The guest OS resolution is 1024 x 768.

It appears that the mouse becomes un-captured when the (invisible) host cursor position moves outside the guest window.  The cursor in the guest moves slower than in the host, so the guest cursor has not reached the edge of the guest desktop.  Either the mouse should remain captured, or the mouse position in the host should be converted to the correct guest position based on the different screen resolutions.

The problem also happens in full screen mode.  The guest display uses only a portion of the host screen, and the guest mouse cursor stops moving when the (invisible) host cursor moves outside the guest portion of the screen.  The host mouse cursor reappears before the guest cursor has moved to the edge of the guest desktop.

This problem makes VirtualBox very difficult to use with boot CDs or operating systems not supported by guest additions.  In some very old versions of VirtualBox (3.x) this problem did not occur.  I frequently use VirtualBox to test boot CDs that I have created for backup, partitioning and encryption software.",ErikW
13163,Clipboard errors,Windows,VirtualBox 4.3.12,2014-07-03T12:28:21Z,2017-07-07T17:09:11Z,2017-07-07T17:09:11Z,"Hi, all. I posted my experience with clipboard problems in the Forum as follows:
Hi, we have several troubles with a COM Add In using VSTO technics. What happens: The COM Add In does more then one clipboard operation in one thread (using the copy-paste-commands of the application). It works fine, except if: Virtual Box is running (on the host System where the Add In runs), with Windows Guest System and installed Virtual Box Extensions and with at least one user. Then we get clipboard errors, which show, that after a copy command the clipboard is empty or contains invalid data for the paste command. These errors don't occur, if there is no user on the guest machine or if there is a user, but the Virtual Box extensions are not installed. We feel there is a big bug in the Virtual Box extensions handling the clipboard.
This error occurs only with Virtual Box (not with MS Virtual PC nor with VM Ware nor with TeamViewer Virtualization) and only with at least one user logged on to the guest and only with installed VB Extensions on the guest. 
The shared clipboard in the General Settings is turned off! I don't believe that the error occurs in our MS Office Solutions with VSTO COM Add Ins (I got the error in other add ins, too: clipboard empty or invalid data) because of the mentioned circumstances.",EP
13083,Always On Top option for guest window in Windows host,BSD,VirtualBox 4.3.12,2014-06-01T12:06:03Z,2016-04-22T13:11:50Z,2016-04-22T13:11:50Z,Would you be so kind and make Always On Top option for guest window of Windows host? Thank you in advance.,MikhailRokhin
15275,No host-only adapter,other,VirtualBox 4.3.12,2016-03-26T06:37:27Z,2016-03-26T06:37:27Z,2016-03-26T06:37:27Z,"I have upgraded from windows7 to windows10 and my host-only adapter disappaered in Windows and virtualbox. 
I use virtualbox 4.3.12
",louis14
14241,Brackets in group name of VirtualBox Manager causes erratic behavior.,Windows,VirtualBox 4.3.12,2015-07-04T19:44:06Z,2015-07-04T19:44:06Z,2015-07-04T19:44:06Z,"This is to report that including brackets ""("" and "")"" in group names causes erratic behavior; 

When creating groups named ""Base Machines (Stage 0)"" or ""Base Machines (Stage 1)"" cause the groups to show up collapsed and moved to the bottom when the VirtualBox Manager is (re)started (Windows).

Taking out the brackets immediately solved the problem. The VirtualBox Manager seems to have a problem with brackets in group names. Possibly other characters cause similary issues.

I am currently stuck at v4.3.12 due to issue (#13841), but I've seen this behavior up to v4.3.28 (inclusive).",Hans Vledder
13149,VirtualBox installation on Windows 8.1 with InstantGo issues,all,VirtualBox 4.3.12,2014-06-27T21:01:19Z,2015-06-05T19:31:52Z,2015-06-05T19:31:52Z,"When you install Oracle VirtualBox x64 (latest version) on a Surface Pro 3 that supports InstantGo, when the computer goes to sleep, most of the time when the computer awakes, the base Surface wireless device won't load on the host system. I've been able to reproduce the problem by doing a factory reset on my Surface Pro 3 and installing it. The problem manifests itself immediately after the VirtualBox installation. This is a major problem, because without the wireless driver, the computer can no longer connect to the Internet or access network resources on both the host system and guest OS.",JHumenik
13663,Repeat installation without reboots in between does not work.,Windows,VirtualBox 4.3.12,2014-12-01T10:55:34Z,2015-02-16T10:54:38Z,2015-02-16T10:54:38Z,"*Steps to reproduce*
1. Download VBox 4.3.12 (x64 in my case). 
2. Install the setup. 
3. Uninstall the setup. A dialog prompts for reboot. Select 'No'.
4. Again install the same setup. 
5. Upon complete installation, a reboot prompt appears. Select 'Yes' this time. 
6. Upon reboot, try to start a VM (simple windows 7 installation .vdi)

*Observation*
VM does not start. 
Kernel driver missing error is shown. ",praseo
13187,VirtualBox 4.3.14 can't start VMs on certain Windows hosts,other,VirtualBox 4.3.14,2014-07-16T11:22:16Z,2018-12-30T10:39:56Z,2018-12-30T10:39:56Z,"Both new and existing VMs cannot be started with VirtualBox 4.3.14 under Win 8.1 x64. Double-clicking on a stopped VM in the GUI gives a popup containing CLI arguments and a message that it failed. Vagrant is broken too. Restarting the system does not fix the issue. Uninstalling and reinstalling 4.3.14 does not fix the issue.

The only fix is to uninstall and reinstall 4.3.12.",AxelFontaine
13235,Shutdown hangs in OS/2 guest,other,VirtualBox 4.3.14,2014-07-24T05:43:48Z,2015-07-15T01:59:27Z,2015-07-15T01:59:27Z,"Hi/2.

Since 4.2.x, shutdown hangs in OS/2 guest.

I'm using OS/2 Warp 4.52, W4_104a kernel, and installed guest addition.",KO Myung-Hun
13234,Key repeating does not work in OS/2 guest,other,VirtualBox 4.3.14,2014-07-24T05:40:52Z,2015-07-10T11:58:12Z,2015-07-10T11:58:12Z,"Hi/2.

Since 4.2.x, key repeating does not work in OS/2 guest.

How to reproduce,

    1. press a key
    2. press other key without releasing a previous key
    3. release a previous key

Then, a previous key is repeated, but a current key isn't repeated. Only first input is processed.

That is, if I press 'a' and press 'b' later, you can see the following.

    aaaaaab

'b' is not repeated.

I'm using OS/2 Warp 4.52, W4_104a kernel, and installed guest addition.",KO Myung-Hun
13304,"Generic GL Renderer used, leading to crash when accessing 3D functionality.",Linux,VirtualBox 4.3.14,2014-08-20T09:50:53Z,2014-11-26T14:40:11Z,2014-11-26T14:40:11Z,"Host : Windows 8.1pro 64, i7 Haswell with integrated 4600HD Graphics. Latest Intel HD driver 10.18.10.3621.

Guest : Ubuntu 14.04 LTS 64bit, guest additions 4.3.14

Virtual Box 4.3.14r95030 does not recognize Intels OpenGL driver, but falls back to Microsoft generic GDI. 
Linux is booting, when trying to login, crashes with Exception 0xc000094 at 0x2370aeff (unknown software exception). 
Working when disabling 3D support in VBox.

Logfile shows generic MS GDI driver
00:00:30.456612 OpenGL Info: Render SPU: GL_VENDOR:   Microsoft Corporation
00:00:30.456629 OpenGL Info: Render SPU: GL_RENDERER: GDI Generic
00:00:30.456633 OpenGL Info: Render SPU: GL_VERSION:  1.1.0

Using VBox 4.3.12, OpenGL from Intel is being recognized and system is working :
00:00:27.446361 OpenGL Info: Render SPU: GL_VENDOR: Intel
00:00:27.446378 OpenGL Info: Render SPU: GL_RENDERER: Intel(R) HD Graphics 4600
00:00:27.446381 OpenGL Info: Render SPU: GL_VERSION: 4.2.0 - Build 10.18.10.3621

(I am not using RDP oder two graphics adapters or similar). ",Bueffel
13341,Chipset and problems,Linux,VirtualBox 4.3.14,2014-09-03T12:51:28Z,2014-11-24T12:30:55Z,2014-11-24T12:30:55Z,"Host  - Windows 2003 Std (32 bit)
Guest - Oracle Linux 6.5 (64 bit)

VirtualBox-4.3.14-95030-Win and VirtualBox-4.3.15-95713

If Chipset set to '''PIIX3''':[[br]]

The network is working properly.

# cat /proc/cpuinfo 
> processor	: 0[[br]]
> vendor_id	: GenuineIntel[[br]]
> cpu family	: 6[[br]]
> model		: 23[[br]]
> model name	: Intel(R) Xeon(R) CPU L5420  @ 2.50GHz[[br]]
> stepping	: 6[[br]]
> microcode	: 0x60b[[br]]
>> cpu MHz	: 0.000[[br]]
> cache size	: 6144 KB[[br]]
> physical id	: 0[[br]]
> siblings	: 4[[br]]
> core id		: 0[[br]]
> cpu cores	: 4[[br]]
> apicid		: 0[[br]]
> initial apicid	: 0[[br]]
> fpu		: yes[[br]]
> fpu_exception	: yes[[br]]
> cpuid level	: 5[[br]]
> wp		: yes[[br]]
> flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl pni ssse3 lahf_lm[[br]]
> bogomips	: 4571.13[[br]]
> clflush size	: 64[[br]]
> cache_alignment	: 64[[br]]
> address sizes	: 38 bits physical, 48 bits virtual[[br]]
> power management:[[br]]

[[br]]
[[br]]
If Chipset set to '''ICH9''':[[br]]

# cat /proc/cpuinfo[[br]]
...[[br]]
cpu MHz  : '''2394.048'''[[br]]
...[[br]]

Network interface not work (on guest network interface is up, but there is no network traffic)[[br]]
eth0 - RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)",PepeN
13267,more video ram please,Windows,VirtualBox 4.3.14,2014-08-07T02:13:23Z,2014-08-07T02:13:23Z,2014-08-07T02:13:23Z,"some games need more vram to load texture, please change vram setting options to unlimited by host can uses free ram, thanks",CML
13263,RTPathUserHome lookup fails when using API in a windows service,all,VirtualBox 4.3.14,2014-08-06T11:16:18Z,2014-08-06T11:16:18Z,2014-08-06T11:16:18Z,"RTPathUserHome uses environment variables to determine the user home directory. When accessing the API from a windows service the lookup for the user home directory fails.

Probably a solution would be to use SHGetFolderPathW for the lookup.

http://stackoverflow.com/questions/9542611/how-to-get-the-current-users-home-directory-in-windows",hakito
13491,HostAudioNotResponding,Windows,VirtualBox 4.3.16,2014-10-10T15:38:25Z,2015-03-24T15:19:02Z,2015-03-24T15:19:02Z,"The warning message appears at Vm's start/restore. 
Audio not transmitted from Guest to Host. Guest does not report any issue.
I've never had such a problem before (since 4.1 at least). 
!!! Reverted back to 4.3.12 works OK again !!!.

",BugRep0rt3r
13455,Windows 8.1 guest - black screen,Windows,VirtualBox 4.3.16,2014-10-01T18:24:38Z,2014-12-12T16:03:24Z,2014-12-12T16:03:24Z,"On host with Windows 7 64bit and Intel 4600 HD video, guest with  windows 8.1 32bit has black screen after enabling 3d support.

3d Support enabled
last video driver from intel is installed

In log is see that GL_Vendor is recognised as Microsoft GDI Generic",RMarauder
13432,Frequent BSOD's on Windows guests since 4.3.x,Windows,VirtualBox 4.3.16,2014-09-24T22:46:10Z,2014-11-25T22:46:21Z,2014-11-25T22:46:21Z,"I've been running everything from 4.3.10 to 4.3.15 and I'm getting constant bluescreens in Windows 7 guests. They are fresh instals as well as older guests. The timing seems to be random, but always within a few minutes. When I can catch the BSOD information, it's regarding ""REFERENCE_BY_POINTER"". The bugcheck is 0x00000018.

At first I thought it was a memory issue, but it occurs even when there is very little memory load on the host.  Host is XP SP3, Intel Core2Duo, 2.93Ghz, 3GB Ram.  I ran a full memory diagnostic which found no problems.

I've done some experimenting, and I can recreate this issue even with barely any memory load on the host. I rolled back to one of the earlier versions that I knew had worked, 4.2.6, and I cannot recreate a single crash, even with an intentionally heavy memory load on the host. I tried several other 4.2.x builds and stopped at 4.2.16. (Newer builds lead to the well-known security issues that also affect the latest 4.3.x branch).  On all of these 4.2.x builds, I just can't get a crash to happen, no matter how hard I try.

Because this didn't happen at all until I upgrade to 4.3.x, I tend to think there's a regression of some kind in 4.3.x.  If anyone is so kind as to take a look at this, I am more than happy to provide additional logs, testing, or information.  

Thanks for reading!",mjdbb1
13440,can't share folders after yum update,Linux,VirtualBox 4.3.16,2014-09-27T03:48:08Z,2014-10-22T16:51:21Z,2014-10-22T16:51:21Z,"Running windows 7 host w/fedora 20 guest.  Setup shared folders and they worked fine for a long time, then they stopped working recently.  When trying to mount the folders, get the error ""/sbin/mount.vboxsf: mounting failed with the error: No such device""  Tried all online suggestions and no luck.  

Eventually narrowed it down to working with fresh Fedora 20 install but the error occurs after a ""yum update"".  

So if I have a VM that's been updated and boot from ""Fedora with Linux 3.11.10-301.fc20.x86_64"", it works fine.  But if booting with the latest, ""Fedora 3.16.3-200.fc20.x86_64) 20 (Heisenbug)"" the shared folders don't work",virtualsomething
13523,After snapshot VM won't start.,Windows,VirtualBox 4.3.16,2014-10-17T14:29:27Z,2014-10-17T15:53:31Z,2014-10-17T15:53:31Z,"I made a snapshot of the virtual machine it would not start anymore the result I get is:
No error info:

Result Code: 
E_FAIL (0x80004005)
Component: 
ProgressProxy
Interface: 
IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
",ditproz
13417,Shortcut doesn't start VM window in the foreground,Windows,VirtualBox 4.3.16,2014-09-19T17:55:39Z,2014-10-14T19:38:21Z,2014-10-14T19:38:21Z,"I'm running Windows XP SP3 as guest OS in a Windows 7 Ultimate 64-bit host. I've created a shortcut to the VM using the feature in VirtualBox Manager.

When starting the VM using the shortcut, the VM window is not brought to the foreground. Although it will appear on top of the desktop (if the shortcut is on the desktop), it will not have focus until you click in it or switch to it using Alt-Tab.

However, the VM window is brought to the foreground when started from VirtualBox Manager.

This seems to be a side effect of the recent Windows hardening changes, but I'm not sure.",bogdan
13507,Overwrite the MAC address of other virtual miniport adapter after wake up from sleep,all,VirtualBox 4.3.16,2014-10-14T07:29:28Z,2014-10-14T07:29:28Z,2014-10-14T07:29:28Z,"I have installed VirtualBox and an IPsec client SW on Windows7 host system. The client uses its own virtual miniport adapter. On this adapter is enabled the ""VirtualBox Bridged Networking Driver"" service.

The MAC address of client adapter:
 
before going sleep: 02:00:00:00:01:00 
after wake up:      08:00:27:00:70:1D

VirtualBox does overwrite the MAC address of foreign adapters!",Beat O
13443,Tooltips in VBox window (not in the guest) make it crash.,all,VirtualBox 4.3.16,2014-09-28T10:34:02Z,2014-10-13T20:56:06Z,2014-10-13T20:56:06Z,"Hi there,

This is the second time I'm encountering problems / crashes with VBox.

First time was with... 4.3.14 ! Now this is with 4.3.16...

Bugs encountered in 4.3.14 have been solved so I could update from 4.3.12, but this time, I'm encountering a new one (not blocking but disturbing).

VM started, in the VBox window or on the Mini Toolbar (depending on if I'm in fullscreen or not), I just can't make tooltips appear : when I put the cursor on a button, after the tooltip delay (1s), the guest windows crashes (and make it ""Aborted"" in the VMs list). I'm getting a 0x0000000 crash with ""memory can't be written"" (see attached files)

This happens on all my VMs (Linux / Windows guests)

Thanks for your help",marebul
13433,For pyTivo with Python 2.7.8 the network traffic is being modified somehow on the Host,Windows,VirtualBox 4.3.16,2014-09-25T03:43:57Z,2014-10-11T19:01:30Z,2014-10-11T19:01:30Z,"I've been using pyTivo and VirtualBox on the same host for a long time. It worked fine until I upgraded from 4.3.12 to 4.3.16. There were no errors produced, but my TiVo could not access pyTivo. I downgraded back to 4.3.12 and pyTivo started working again. Not really sure what log files I could produce to demonstrate the problem. I do not see any errors in any of the Windows log files and pyTivo shows no problems. I can only surmise that it is some sort of networking issue. However I can still access the web address for the program, http://pytivohost:9032, from another computer. Only my TiVo cannot access it.

I'm running Windows 7 Home Premium 64-bit with 16GB of RAM. Not particularly relevant, but my guests are also Windows 7 64-bit. The problem exists whether any guests are running or not.",Steven Wilson
13500,Windows VirtualBox Process Priority support,all,VirtualBox 4.3.18,2014-10-12T18:15:07Z,2021-06-08T23:57:02Z,2021-06-08T23:57:02Z,"BOINC runs CPU-instensive tasks (sometimes VirtualBox CPU-intensive tasks), typically at idle priority, but sometimes at below normal priority. The intent is to not interfere with the user's computing experience.

Before the hardened security that was added to VirtualBox for Windows (using VirtualBox 4.3.12 or prior), BOINC could easily manage/set/increase/decrease the process priorities as needed.

After the hardened security was added to VirtualBox for Windows (using VirtualBox 4.3.14+), the process priorities can no-longer be controlled. They run at Normal, with no way to change them (that I know of). This ends up degrading the user experience. I'm considering this a defect, since the hardened security changes broke something that was previously working great.

Please add some way to control the priorities of the VM processes that get instantiated -- Preferably available in the VirtualBox Manager UI, but for BOINC's purposes, VBoxManage command line parameters would work too I believe.

Thanks,
Jacob Klein",Jacob Klein
13580,The Instruction at 0x... referenced memory at 0x... The memory could not be read,Linux,VirtualBox 4.3.18,2014-10-31T15:11:02Z,2016-12-12T17:22:47Z,2016-12-12T17:22:47Z,"As of version 4.3.16 and 4.3.18 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
",Frank Breitling
14054,Non-stereo (surround) audio,Windows,VirtualBox 4.3.18,2015-04-17T04:06:02Z,2016-08-23T12:37:19Z,2016-08-23T12:37:19Z,"I require non-stereo/surround audio to work correctly in virtualbox so I can test the behaviour of applications on multiple OSs. Currently if the guest audio is set to anything other than stereo, the resulting audio is corrupt and only ever plays out the L and R speakers.",Paul17041993
13582,3D fails in Ubuntu 14.10 Guest,Linux,VirtualBox 4.3.18,2014-10-31T16:43:31Z,2015-07-31T09:27:01Z,2015-07-31T09:27:01Z,"This may be related to bug [https://www.virtualbox.org/ticket/12941 ] but is with the newer release of ubuntu and verified on the latest virtualbox 4.3.18 release and a variety of guest additions (including latest 4.3.19 test).

vboxvideo fails to load either via compiz or in tests using `/usr/lib/nux/unity_support_test`, giving the following error:

{{{
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

This means that ubuntu falls back to llvmpipe rendering, so uses 100%+ CPU continuously. 
This is with a Window 8.1 host, ubuntu 14.10 guest (clean install from latest ubuntu ISO)",markh
14242,3D Accelerate Grayed Out (Can't disable after moving VM),Linux,VirtualBox 4.3.18,2015-07-04T23:28:40Z,2015-07-04T23:28:40Z,2015-07-04T23:28:40Z,"I recently set up a new system and decided to migrate my VM to the new host. The new host doesn't support 3D acceleration so I was unable to start the VM.

Unfortunately, because VirtualBox detected that my host doesn't support 3D acceleration, it disabled the ""3D Acceleration"" checkbox in the VM's settings. It was disabled, yet still checked.

The workaround is just to use the commandline:
vboxmanage modifyvm MY_VM_NAME --accelerate3d off

If VBox is taking the time to check for host capabilities and updating the UI appropriately, it should also remove the 3D acceleration checkbox and notify the user about the incompatibility.

I'll also note that this was in 4.3.18 since that's what's in the Debian package repository. I migrated the VM from a Windows host using 4.3.28 that supports 3D virtualization so I wasn't able to verify whether this is an issue in the latest release.",sraboy
13622,BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) on host machine immediately after powering on guest machine,Windows,VirtualBox 4.3.18,2014-11-18T22:29:28Z,2015-06-25T13:51:57Z,2015-06-25T13:51:57Z,"Hello.

I get BSOD (SYSTEM_SERVICE_EXCEPTION 0x0000003b) immediately on host machine after powering on guest machine. 

I have searched the forums and did not find anything corresponding to my problem.

Host: Windows 7 SP1 x64
Guest: Windows 2012",Anton Lisnenko
13526,Memory leak with 3D acceleration with Ubuntu lens,Linux,VirtualBox 4.3.18,2014-10-17T15:24:42Z,2015-06-20T00:47:09Z,2015-06-20T00:47:09Z,"I have a Windows 7 host and Ubuntu 14.04 guest. If I enable 3D acceleration, there is a huge memory leak (about 100 MB per second) when the Ubuntu main system menu (Unity lens) is open. It is apparently related to the blurring effect, since there is no leak if I disable 3D acceleration and Ubuntu just shows a plain colour background. 

The strangest thing is that I can see the memory being eaten away in my host's performance monitor, but the guest's performance monitor doesn't show any problem and the memory use is stable there. I hope this can be a clue as to where the problem lies.

I can work with 3D disabled but the system is totally unusable with it enabled, since the memory leak is so severe.

I attach a log file",rgargente
13620,Inconsistent screen redraw when scrolling in Chromium,Linux,VirtualBox 4.3.18,2014-11-18T13:55:08Z,2015-04-20T08:57:20Z,2015-04-20T08:57:20Z,"When I scroll in Chromium, I get inconsistent screen redraws.

Attached is a PNG that demonstrates the problem. In that case, I scrolled up some. Notice how the banner image shows three times.

Occasionally, when I switch between tabs, portions of both tabs will be interleaved in horizontal stripes.

I can usually fix an inconsistent screen redraw if I take the Chromium window and move it around.

This seems to have started with a 14.04 guest when I upgraded VirtualBox and the guest extensions in September or October. I cannot remember the exact timeline. I installed a fresh copy of 14.10 yesterday (that's where the PNG comes from), and the same problem is happening.

I have 3D acceleration enabled and 128MB video memory. Host is Windows 8.1 x64.

I've also attached console warnings that appear when starting Chromium from the terminal window.",Aren Cambre
13574,VirtualBox keeps resizing the guest to 1 screen,Linux,VirtualBox 4.3.18,2014-10-30T11:15:06Z,2014-12-18T19:39:20Z,2014-12-18T19:39:20Z,"Since updating to VB 4.3.16 and 4.3.18 from 4.3.12 it is impossible to resize the guest operating system to more than 1 screen.

I run Windows 7 and I have 3 screens and I have enabled Auto-Resize Guest Display.

It is possible to drag the bottom right corner of the guest window, but as soon as it is released there are some flickering and the window is resized to be as width as 1 screen.
The guest OS display is internally of the size I resized to, but there is a horizontal scrollbar.

The guest OS is Fedora 19 fully updated.

Guest OS additions are installed.

As soon as I downgradeto 4.3.12 the problem goes away and it is 100% reproducible with 4.3.16 and 4.3.18. I have never tried 4.3.14.

I have a NVIDIA NVS 310 card.

Some other users have reported it here

https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",mariolino
13629,VM SUP startup log creation,all,VirtualBox 4.3.18,2014-11-20T16:30:45Z,2014-11-20T16:30:45Z,2014-11-20T16:30:45Z,"VirtualBox creates VM shortcuts without adding the --sup-startup-log command line parameter. A VM receives the --sup-startup-log parameter only when it is started from the VirtualBox Manager. Most users will not be aware of this and they will provide whatever log resides in the VM folder. Maybe it should be better to use a per VM property, that defaults to enabled. An example of such a situation can be found [[https://www.virtualbox.org/ticket/13295#comment:20|here]].",Mihai Hanor
13611,Cannot get rid of 2nd monitor window,Windows,VirtualBox 4.3.18,2014-11-12T17:44:05Z,2014-11-14T13:31:57Z,2014-11-14T13:31:57Z,"Never set VB to use 2 monitors for a VM, but somehow after a Windows update occurred in the VM, guessing this was the point at which it first appeared. I have 2 VB displays coming up for a VM.  I have tried to set VB to use only 1 display, however, the Win OS still comes up on the 2nd display thus never allowing me to sign in to the OS.  I have also tried changing the monitor under windows settings to show the desktop on the primary display 1, vs the second but the OS will not allow me to make the change. I did not initiated the change on the OS or through VB and cannot get ride of it.  Also, VB shows the primary display as being corrupted in the preview window.

Please see attached screen shots.  Need to get the VM back and Win OS to using only 1 display.

Thank you
Art",ArtZ
13557,Virtualbox 4.3.18 disable logging,Linux,VirtualBox 4.3.18,2014-10-27T08:52:34Z,2014-11-14T11:41:47Z,2014-11-14T11:41:47Z,"I have set system user variables:
{{{
VBOX_RELEASE_LOG_DEST=nofile
VBOXSVC_RELEASE_LOG_DEST=nofile
VBOX_GUI_SELECTORWINDOW_RELEASE_LOG_DEST=nofile
}}}

But one file still appears. ""VBoxStartup.log"" under `\VirtualBox VMs\(Machine name)\Logs`. How can I disable all log files?",karlsson
13598,Error al iniciar máquina,Windows,VirtualBox 4.3.18,2014-11-07T02:49:12Z,2014-11-10T14:16:25Z,2014-11-10T14:16:25Z,"Fallo al abrir una sesión para la máquina virtual PC_WindowsXPSP3.

The virtual machine 'PC_WindowsXPSP3' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'N:\EquiposVM\PC_WindowsXPSP3\Logs\VBoxStartup.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: Machine
Interfaz: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}",seterymco
13571,64bit guest on 64bit Windows 8.1 running bootcamp on a macbook air,Windows,VirtualBox 4.3.18,2014-10-29T21:04:08Z,2014-11-03T14:43:00Z,2014-11-03T14:43:00Z,"I have just installed Virtual Box 4.3.18r96516, on a Macbook Air running Windows 8.1 in bootcamp. Right after the installation completed, I installed Windows Server 2012R2 64bit on a new virtual machine - this worked perfectly and I also installed an SQL server 2012 afterwards. Now a few hours later after sleeping the computer I get this error: ""VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot."". I tried rebooting into OS X and back again, but that didn't work either (same error).
In task manager->performance it says Virtualization Enabled, and from a bit of research I can gather that virtualization should be enabled as default on all macs.",Skovby
13539,Can't Resize guest to span monitors,all,VirtualBox 4.3.18,2014-10-21T16:55:35Z,2014-10-21T16:55:35Z,2014-10-21T16:55:35Z,"Running Windows 7 amd64 
Previously in version 4.3.12 and earlier, I could move a guest so it spanned monitors I have 4 of them. And the guest would resize the desktop.

Now since 4.3.14 (or) 4.3.16.. I can move a windowed guest so it crosses multiple monitors. But when I try to resize it. It snaps to one monitor window and fits itself inside the monitor still in windowed mode.

Since my monitors are pretty low res 1440x900 being able to expand my guests makes it much more useful.

I see this using Ubuntu 14.4 as a guest as well as Win XP as a guest.

I did upgrade everything to 4.3.18 and added the additions to the host and the guests.

",Remowylliams
13528,Windows 10 Tech preview - Reboot at Guest Additions installation with 3D disabled,Windows,VirtualBox 4.3.18,2014-10-18T20:30:40Z,2014-10-20T16:51:39Z,2014-10-20T16:51:39Z,"Instead of showing a specific error, the Virtual machine crash/reboot if  I try to install guest addition 4.3.18.r96516 .  I just activated 2D+3D graphic options of the vm and now the installation complete successfully

",FrankBT
13531,"VBoxManage ""c:\"" argument handling",all,VirtualBox 4.3.18,2014-10-20T14:04:36Z,2014-10-20T14:04:36Z,2014-10-20T14:04:36Z,"on the Microsoft Windows host I run 'cmd' and enter:[[BR]]
cd %programfiles%[[BR]]
cd Oracle[[BR]]
cd VirtualBox[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
[[BR]]
The quotes are straight. In[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
this is displayed as:[[BR]]
c:\[[BR]]
in the textbox. There is no icon to the left side of the text.[[BR]]
[[BR]]
[[BR]]
In the file[[BR]]
%userprofile%\.VirtualBox\VirtualBox.xml[[BR]]
it is stored as:[[BR]]
<SystemProperties defaultMachineFolder=""c:&quot;"" ...[[BR]]
[[BR]]
[[BR]]
[[BR]]
This will lead to:[[BR]]
a) wrong folders being used.[[BR]]
New virtual machines created with VirtualBox.exe will be stored in[[BR]]
""%userprofile%\%VBOXNAME%\""[[BR]]
instead of[[BR]]
""c:\%VBOXNAME%\""[[BR]]
[[BR]]
The snapshot folder of the virtual machine is wrong as well.[[BR]]
[[BR]]
[[BR]]
b) errors if you programmatically create a virtual machine.[[BR]]
If you set the machinefolder:[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
[[BR]]
The VM creation/registration command :[[BR]]
VBoxManage createvm --name ""%VBOXNAME%"" --ostype Windows7 --register[[BR]]
[[BR]]
will fail with the error message:[[BR]]
VBoxManage.exe: error: Invalid machine settings file name 'C:\Users\user\""\VB-USER\VB-USER.vbox' (VERR_INVALID_NAME)[[BR]]
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component Machine, interface IMachine, callee IUnknown[[BR]]
VBoxManage.exe: error: Context: ""CreateMachine(bstrSettingsFile.raw(), bstrName.raw(), ComSafeArrayAsInParam(groups), bstrOsTypeId.raw(), createFlags.raw(), machine.asOutParam())"" at line 275 of file VBoxManageMisc.cpp[[BR]]
[[BR]]
[[BR]]
Note: the problem applies to the following parameters as well:[[BR]]
VBoxManage createvm --basefolder[[BR]]
VBoxManage modifyvm --snapshotfolder[[BR]]
[[BR]]
[[BR]]
For example, if you run[[BR]]
VBoxManage setproperty machinefolder ""c:\""[[BR]]
and[[BR]]
VBoxManage createvm --basefolder ""c:\""[[BR]]
The settings file will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%.vbox[[BR]]
The Snapshot folder will be stored in:[[BR]]
%userprofile%\%VBOXNAME%\%VBOXNAME%\Snapshots[[BR]]
[[BR]]
I leave out the example of the snapshotfolder.[[BR]]
[[BR]]
[[BR]]
The workaround I found is instead of[[BR]]
""c:\""[[BR]]
use[[BR]]
{{{
""c:\\""
}}}
OR[[BR]]
{{{
c:\
}}}
as argument to machinefolder/basefolder/snapshotfolder parameter.[[BR]]
[[BR]]
In ""%userprofile%\.VirtualBox\VirtualBox.xml""[[BR]]
{{{
""c:\\""
}}}
is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
c:\ is stored as[[BR]]
<SystemProperties defaultMachineFolder=""c:\""[[BR]]
[[BR]]
Either workaround will display a folder icon in[[BR]]
VirtualBox -- File -- Preferences... -- General -- Default Machine Folder[[BR]]
[[BR]]
[[BR]]
[[BR]]
[[BR]]
Note:[[BR]]
on Fedora 20 x86_64 you can use ""/"" as a machine folder without problem.[[BR]]
I had to start VirtualBox with root-permissions to work with this, though.[[BR]]",Sobek
13513,vBox USB redirection not working for remotefx redirected USB devices,all,VirtualBox 4.3.18,2014-10-14T22:35:19Z,2014-10-14T22:35:19Z,2014-10-14T22:35:19Z,"Environment:  VirtualBox on Windows 7 x64 (The Windows Host is actually a Guest on a Hyper-V, Server 2012 R2)

The Windows 7 is connected via Remote Desktop while being attached with some USB devices via RemoteFx USB redirection. VirtualBox is unable to detect these USBs, thus the Nested guests are not able to use USB attached to their Host. It is possible that VirtualBox could support such ""uncommon"" configuration? 

Blow shows a snapshot (devicemanager.jpg) from the ""Device Manager"" to illustrate the hardware topology while RemoteFx USB redirection is in effect.",ganboing
13572,GUI to remember whether Details or Snapshots were showing,all,VirtualBox 4.3.18,2014-10-30T01:11:53Z,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"Could the VirtualBox Manager GUI (VirtualBox.exe on a Windows host) please remember between runs whether I had the Details or the Snapshots view in the right pane. 

I create, delete, restore snapshots a lot, but don't look at or modify (once the VM is set up) the VM details much. So almost every time I run the VirtualBox Manager GUI I click the Snapshots button (top right corner), because the GUI always starts showing Details. It would be very handy if the GUI would simply preserve the current view between runs, as it preserves many other GUI state details.",m6477
12369,NAT Network -  DHCP problem: no DNS,Windows,VirtualBox 4.3.2,2013-11-17T23:47:23Z,2014-12-02T12:33:10Z,2014-12-02T12:33:10Z,"Postby petardo » 17. Nov 2013, 03:20
I am using the ""NAT NETWORK"" Network Adapter.
I have found a DHCP SERVER problem:
IF
- DHCP SERVER is enabled in the file / preferences / network / nat network section,
- and NAT NETWORK is selected as natwork adapter for the guest
==> NO DNS values get forwarded to the guest",petardo
12403,Feature Request - Mount VDI as Windows Drive,other,VirtualBox 4.3.2,2013-11-28T10:40:53Z,2013-11-28T10:40:53Z,2013-11-28T10:40:53Z,It would be of great use if VB can provide a way to mount VDI directly in Windows as disk drives and let me defrag it without need to boot into guest OS.,Edward Yang
13659,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it",all,VirtualBox 4.3.20,2014-11-29T15:14:44Z,2019-12-07T17:39:42Z,2019-12-07T17:39:42Z,"Hardened protection incorrectly get name of injected signed (!) dll and can't verify signature, so rejecting it.

VirtualBox since 4.3.14 (all builds, including 4.3.20/4.3.21 - the most updated) are incompatible with Outpost Firewall Pro v6.7.x and others, that used ""WL_HOOK.DLL"" module to inject to all processes to get some information in RING3 (usermode).

WL_HOOK.DLL is digitally signed (!) (I can attach this file, if needed), and must be allowed even by hardened rules. But VirtualBox incorrectly recognize a path to it. There is a bug in VirtualBox getting/parsing path information in some cases of modules inject or other (probably, is because of special inject technics, that used). Please see a VBoxStartup.log:

{{{
...
e4.11ec: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\WINDOWS\system32\imm32.dll [lacks WinVerifyTrust]
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=76290000 'E:\WINDOWS\system32\IMM32.DLL'
e4.11ec: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║)
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║: None of the 1 path(s) have a trust anchor.: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║
e4.11ec: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewallц╜ОцХоц╝атБжцб┤тБетА▒цЕ░цб┤чМитАйцЕицХ╢цДачРачХ▓чС│цДацНоц╜ит╣▓тА║фСЬчЩецНйх▒ецЕИцС▓цедцн│ц╡Дц╜ЦчХмцХнх▒│цбРчН╣цНйц▒бц╡Дц╜ЦчХмцХнх▒│ц▒ВцНпхЩлц▒пц╡╡уНехБЬц╜▓чЙзц╡бфШац▒йчНеф╜ЬчС╡ц╜░чС│фШачЙйчЭец▒бюЩмш║╜щЧжюЪоъВ╝шЗвюЪжыТбшЗвюКеыЖАшЧжюЪ░ыТбш│зюКиъжАшЧжюЪиыЪХшУжюЮаъВРщЧзюЮ▓ыОСшУжюЪаъ║Ны╖жюКиыК╣шГв┬║
e4.11ec: Error (rc=0):
e4.11ec: supR3HardenedMonitor_LdrLoadDll: rejecting 'e:\progra~1\outpos~1\wl_hook.dll': rcNt=0xc0000190
e4.11ec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'e:\progra~1\outpos~1\wl_hook.dll'
...
}}}

Please see a lot of garbage (binary garbage like ""ц╜ОцХоц╝атБжцб┤тБетА▒цЕ░ц"" and so on) after ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall"" string, instead of normal dll name path.

The real path to wl_hook.dll is E:\Program Files\Outpost Firewall Pro\wl_hook.dll

So it must be like: ""\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume3\Program Files\Outpost Firewall\wl_hook.dll""

But you had incorrectly get/parsed data. It seems like buffer contain a garbarge or like string's ending-zero is missed or something, so you are reading garbage memory.

After you are got that garbarge-containing-path you a providing it to a system function WinVerifyTrust to check digital signature of this ""file"". But path is invalid (garbaged/damaged), so Windows function cannot find the file and check digital signature and returns an error.

After getting this error, you are REJECTING to load this .dll.

And after that, we have a problems to use VM. Because Outpost Firewall cannot read information about process without this R3-dll injected to VM's process, so it can't get correct ProcessName and can't allow/create_rule to any network or other activity from VM, so it is UNUSABLE.

Please fix path retreiving/parsing or this inject method allowing and allow WL_HOOK.DLL (digitally signed) to inject to your process.",John Dan
13669,Virtual Box 4.3.20 stuck on creating process for virtual machine,Windows,VirtualBox 4.3.20,2014-12-04T07:15:16Z,2019-03-14T16:03:24Z,2019-03-14T16:03:24Z,"Hi,
I have updated my Version from 4.3.12 to 4.3.20. since then I can´t start the VM. I stuck in creating process in Virtual Machines.
As Antivir I am using Symantec. 
My Host is Windows 7 64 bit Enterprise and the VM is a Win 7 32-bit
",cyberoner1
13697,4.3.20 doesn't start virtual machines any more (supHardenedWinVerifyProcess failed),Windows,VirtualBox 4.3.20,2014-12-18T07:23:20Z,2017-09-25T14:30:00Z,2017-09-25T14:30:00Z,"Hi,
yesterday I upgraded from 4.3.12 to 4.3.20 r96997 and every virtual machine on my Win7-32bit SP1 Enterprise Host hangs on startup with this messages (see screenshots):

Error in supR3HardNtChildPurify:
supHardenedWinVerifyProcess failed with
VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc=-5673)

I executed KB3024777-x86.exe to remove KB3004394 but it doesn't seem to do anything. In system control, programs, ""installed updates"" I can't find KB3004394.

[[Image(http://abload.de/img/1jgahq.png)]]
[[Image(http://abload.de/img/2hpbct.png)]]

It would be great to get some help on this issue!
If you need any further information about it I'll provide it:-)
Thanks in advance.",JackyRyan
13648,VirtualBox 4.3.20 Could Not Initialize GLX,Linux,VirtualBox 4.3.20,2014-11-27T01:15:36Z,2016-01-22T08:37:28Z,2016-01-22T08:37:28Z,"After upgrading from VirtualBox 4.3.12 to 4.3.20, attempting to run a QML application results in the error: ""Could not initialize GLX"". There appears to be a problem with OpenGL in the guest extensions.

------------
System Info:

{{{
Host:
Windows 7 Professional 64-bit SP1
AMD Phenom II N950 Quad-Core
ATI Mobility Radeon HD5650

VirtualBox v4.3.20 r96997
Extension Pack v4.3.20 r96996

Guest:
Xubuntu
lsb_release: Ubuntu 14.04.1 LTS
uname: Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Relevant Packages:
mesa-common-dev
libgl1-mesa-dev
libglu1-mesa-dev
}}}


-------
Output:

{{{
$ qmlscene test.qml --resize-to-root
libGL error: pci id for fd 10: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
Could not initialize GLX
Aborted (core dumped)
}}}


------------
Sample Code:

{{{
import QtQuick 2.2
 
Rectangle {
  width: 640
  height: 480
  color: 'black'
}

}}}

------------
Qt Download:
http://www.qt.io/download-open-source/",amclain
13749,Host Screen numbers are reversed in full screen mode,Windows,VirtualBox 4.3.20,2015-01-10T06:01:39Z,2015-11-21T09:06:25Z,2015-11-21T09:06:25Z,"I have two identical monitors. When I run a VM (with a single virtual monitor) in full screen mode, I can use Mini Toolbar, View->Virtual Screen 1 to move the VM from one monitor to the other. However the monitor number is wrong - when I select Host Screen 1 (the left monitor), it puts the VM on monitor 2 (on the right), and vice-versa. I've checked the host machine display properties (including ""Identify"") and verified that host monitor 1 is on the left and 2 is on the right.

It used to work correctly, however I recently swapped the two physical monitors, ie left to right and right to left, and so far as I can tell that's when the problem with virtual box started.

At the time I swapped the monitors, I was doing some fault finding, so the host PC was switched on/off a few times with various combinations of one or both monitors disconnected, primary monitor being one or the other, swapping cables between monitors etc. (Virtual Box was not run at any time during this.) The problem turned out to be a physical/optical defect in one monitor - which was originally my primary monitor (number 1, on the left), so that monitor is now my secondary (number 2, on the right). (Swapping them back is not an option.) After I finished, I went to Windows Control Panel and ensured that monitor 1 (eg as shown by the ""Identify"" button) is on the left and is my main display, and the monitor 2 on the right is the secondary - it had changed during the process of testing. The port on the video card that's used for the left monitor hasn't changed - only the monitors have swapped places.

The host machine appears to correctly identify the monitors, but now Virtual Box puts the full-screen VM on the opposite monitor to what the mini toolbar menu item says.

The problem is not user-specific. I can replicate it with a different user on the same host PC.

Uninstalling/reinstalling VirtualBox does not fix the problem.

I've tried assorted combinations of disconnecting one or other of the monitors, restarting the machine etc, to see if that will fix it, but it doesn't make any difference.

I even reverted to a (Windows Backup and Restore) system image taken before the monitors were swapped, and that didn't fix the problem either.

It's as if VirtualBox's ""host screen 1"" is tied to the original physical monitor 1, rather than the logical monitor 1 (ie as Windows identifies it after swapping them).

Technical details:

Host is Windows 7 Ultimate, SP1, 64-bit. (The problem appears to be independent of the guest OS - I can replicate it with Windows and Ubuntu guests, and no guest OS at all, just the VM BIOS on a newly created VM with no software installed.)

The monitors are both Dell 2209WA.

Video card is AMD Radeon HD 6670.
",m6477
13705,"Windows 7 Host and Linux guest, BSOD on host",Linux,VirtualBox 4.3.20,2014-12-20T05:41:09Z,2015-10-05T22:30:45Z,2015-10-05T22:30:45Z,"I ran 4.3.12 for quite awhile.  After I jumped to 4.3.20, I am now getting BSOD every now and then.  I've done a memory scan, just to be sure I don't have failing RAM.  Anything else I can do to get more information?

I'm not sure if the windows event viewer files are useful or not, but I'm attaching them.",Trent
13771,Crash When Entering Seamless/Fullscreen Mode,all,VirtualBox 4.3.20,2015-01-20T21:32:49Z,2015-08-21T02:31:11Z,2015-08-21T02:31:11Z,"VirtualBox v4.3.20/4.3.21 crashes when I enter Fullscreen or Seamless mode. The guest OS will run perfectly in a regular window, but once you try to switch to one of those two modes it crashes after about a second or two. It doesn't matter what the guest is (Windows or Linux) and I have the guest add-ons installed in both of them. I'm running Windows 7 64 as my host OS. I have 20 GB of RAM and an Intel Core i7, so power isn't a problem. The crash is repeatable, even across versions and clean installs. I wiped out my VMs and my settings, then booted a LiveCD and the same error happened.

Here's the actual error: '''The Instruction at 0x00000000 referenced memory at 0x00000000. The memory couldn't be written. Click OK to terminate the program.'''
",BrandonGolway
13748,Java8 GUI Apps not working in Linux guest,Linux,VirtualBox 4.3.20,2015-01-08T07:55:52Z,2015-08-17T11:24:07Z,2015-08-17T11:24:07Z,"My Host is Windows 7 Enterprise Build 7601 SP1
My Guest is Suse Enterprise Linux Server 11 SP3 with GuestAdditions.

I installed jdk8u25 and eclipse STS Version 3.6.3.RELEASE Build 201411281415 Platform Eclipse Luna SR1 (4.4.1)
and when i try to start eclipse i get following error message:

{{{
ES2 Prism: Error – reported GLX version = 1.2
GLX version 1.3 or higher is required
}}}

This seems to be caused by the eclipse internal webbrowser.

And the problem seems to be that the glx version provided by the virtual box's graphic card driver is just too old.

The only way i was able to solve the issue was to downgrade java to jdk7u71.",mmoossen
13686,VirtualBox + Actual Windows Manager = crash,Windows,VirtualBox 4.3.20,2014-12-12T14:14:03Z,2015-07-07T12:02:14Z,2015-07-07T12:02:14Z,"Hello,

I recently installed the Actual Windows Manager application (demo available here: http://www.actualtools.com/windowmanager/) to manage my multiple screens.

I noticed that, when this application is installed, all my virtual machines crashes when I try to open them. After 5 seconds, the virtual machine window freezes, and it's not possible to make any action. I noticed that the virtual machine continues to work on the application main interface (the virtual machine is still updated inside the screenshot control), but the virtual machine display window stops to work, and I have no alternative but to kill it.

When this happens, my machines take the Aborted status, and I cannot do nothing to resolve that. If I try to start my machine again, it restarts normally, but after 5 seconds, the problem returns. All my virtual machines are affected by this issue. If I uninstall the Active Windows Manager, all becomes normal.

I'm working on Windows 7 professional 64bit.

Regards",jeanmilost
13676,Guest windows is squeezed to small size if user32.dll has been altered on a host,all,VirtualBox 4.3.20,2014-12-07T22:22:47Z,2015-04-18T09:30:31Z,2015-04-18T09:30:31Z,"If user32.dll has been altered on a host (some software installation) and is not signed anymore, since 4.3.16 (or 4.3.14) all guests start with a window squeezed to a smallest possible size. VMs start and run normally, just the window always auto-resize to a smallest size. Not happening with 4.3.12 version.

related error in the logs:
00:00:01.122572 supR3HardenedErrorV: supR3HardenedScreenImage/Imports: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=32 \Device\HarddiskVolume7\Windows\System32\user32.dll

discussion on the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=63634",wroot
14018,Shared Clipboard stops working,Windows,VirtualBox 4.3.20,2015-04-02T00:16:04Z,2015-04-02T00:16:04Z,2015-04-02T00:16:04Z,"Host: Windows 7 x64

Step 1: Start guest with guest additions, bi-directional clipboard (in my case, linux mint)

clipboard works both ways, as it should.

Step 2: Start another guest without guest additions, clipboard sharing disabled (in my case, windows 10 preview)

clipboard does not share in 2nd guest, as intended; however, clipboard no longer is shared in the 1st guest now, either direction.",whoami
13763,Problem with setextradata GUI/Seamless on,Windows,VirtualBox 4.3.20,2015-01-15T13:51:36Z,2015-03-30T16:09:06Z,2015-03-30T16:09:06Z,"Hello.
I develop on c#.
I'm trying to start VirtualBox VM to SeamlessMode via VBoxManage.exe in command line under Windows 7/8/8.1 host. The problem is that it works, but not all the time. If the host computer is powerful then the success rate of starting VM in seamless mode is about 90%. If the host machine is slow then the success rate drops to 50%.
Please see the attached snippet (VM starting in seamless mode) 
	restoreSnapshot();[[BR]]setSeamlessMode();[[BR]]runVM(); 

	public static void restoreSnapshot()
	{
			Process VBoxManage = new Process();
    			VBoxManage.StartInfo.CreateNoWindow = true;
	    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    			VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    			VBoxManage.StartInfo.Arguments = ""snapshot VM restore Snap1"";
	    		VBoxManage.StartInfo.UseShellExecute = false;
	    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    			VBoxManage.Start();[[BR]]String line = """";
		        while (!VBoxManage.StandardOutput.EndOfStream)
		        {	        
		            line = VBoxManage.StandardOutput.ReadToEnd();	            
		        }
	        	VBoxManage.Dispose();
	}

	public static void setSeamlessMode()
	{
		
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
    		VBoxManage.StartInfo.Arguments = ""setextradata VM GUI/Seamless on"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;	        
    		VBoxManage.Start();[[BR]]String line = """";
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
	        VBoxManage.Dispose();
	        
	}

	public static void runVM()
	{            
		Process VBoxManage = new Process();
    		VBoxManage.StartInfo.CreateNoWindow = true;
    		VBoxManage.StartInfo.FileName = VBoxManageEXE;
    		VBoxManage.StartInfo.WorkingDirectory = VBoxPath;
            	VBoxManage.StartInfo.Arguments = ""--nologo startvm VM -type GUI"";
    		VBoxManage.StartInfo.UseShellExecute = false;
    		VBoxManage.StartInfo.RedirectStandardOutput = true;
    		VBoxManage.Start();            
	        String line = """";[[BR]]
	        while (!VBoxManage.StandardOutput.EndOfStream)
	        {
	            line = VBoxManage.StandardOutput.ReadToEnd();	            
	        }
                VBoxManage.Dispose();            
        }",batyr
13713,VirtualBox fails to create bridged or host-only network adapter on some Win7 desktops - Error FAIL (0x80004005),all,VirtualBox 4.3.20,2014-12-23T16:09:02Z,2015-03-25T14:34:59Z,2015-03-25T14:34:59Z,"Detected in:  VirtualBox-4.3.20-96997-Win.exe

On some of our Win7 desktops with Broadcomm gigabit 57xx ethernet adapter, When installing or configuring VirtualBox, it returns error FAIL x8004005 and fails to create the virtual ""host-only"" and/or bridged network adapter.  Switching to NAT also fails with a similar network-related error (cannot find network adapter for PXE boot or similar). 

This error is occurring only on some (~10%) of our Qa desktops, but all have identical hardware and configurations running similar recent Win 7 builds. 

Note that this error was also occurring also under Vbox 3.18 and VBox 3.16, for these same desktops, and is similar to many open defects already logged with oracle. 

We have tried install/uninstall numerous versions of Virtual Box, as local and domain Admin, with AVG antivirus disabled, as well as uninstall + manual registry and driver-file cleaning as per FAQs, + system restores, and nothing fixes it. For these affected desktops, Vbox is unable to work.

Note that this error is very similar to open issue logged with Oracle, on which there is no resolution, but it seems very suspicious that it's working for most of QA and RnD, except for those recent windows builds.

Scenario 1: 
------------------
On install, or subsequently from :
 ==> Vbox/File/Preferences/Network/Host-Only/ ==> try to create a new ""host-only"" adapter:
Result Code: E_FAIL (0x80004005)
- In Device manager, every time this is attempted, we get a new ""unknown"" network device.
- Manual device driver update fails (see attached screenshot)
 
Scenario 2:
-----------------
On any guest image
==> Settingas/Network==> select ""Bridged"" network adapter ==> save and start guest VM:
Result Code:  E_FAIL (0x80004005)
Component: 
Console
Interface: 
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}


Similar issues logged @ Virtual Box:
--------------------------------------------
   * https://www.virtualbox.org/ticket/13690
   * https://www.virtualbox.org/ticket/13681
   * https://www.virtualbox.org/ticket/13654
   * https://www.virtualbox.org/ticket/13481

See attached vbox ""setupapi"" log files and screenshots
--------------------------------------------",mkorning
13733,VBoxNetFlt.sys v4.3.20 BSOD “DRIVER_POWER_STATE_FAILURE” when hibernate/shutdown WIN7,all,VirtualBox 4.3.20,2015-01-05T09:01:24Z,2015-03-01T11:01:59Z,2015-03-01T11:01:59Z,"I randomly (but often) get a BSOD ({{{DRIVER_POWER_STATE_FAILURE}}}) when I hibernate or shutdown my laptop (Windows 7 Home Premium).

I first get a black screen during about 10 minutes then I get the following BSOD.

I already got this issue randomly with previous versions of VirtualBox and I thought it was fixed when reinstalling a new version…

analyze -v output:
{{{
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005572700, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800feaa0a0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88010200000 VBoxNetFlt

IRP_ADDRESS: fffffa800feaa0a0

DEVICE_OBJECT: fffffa8007771050

DRIVER_OBJECT: fffffa8007756e70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0354c8d2 : 00000000`0000009f 00000000`00000003 fffffa80`05572700 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034e785c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`034e76f6 : fffffa80`0e88fc58 fffffa80`0e88fc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034e75de : 000001b6`a883467f fffff800`00b9cc58 00000000`00b847c0 fffff800`0365ba88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034e73c7 : 00000060`dc5662c2 00000060`00b847c0 00000060`dc56620f 00000000`000000c0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d48ca : fffff800`03657e80 fffff800`03665cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetFlt
start             end                 module name
fffff880`10200000 fffff880`1022b000   VBoxNetFlt T (no symbols)           
    Loaded symbol image file: VBoxNetFlt.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
    Image name: VBoxNetFlt.sys
    Timestamp:        Mon Nov 24 12:06:09 2014 (54731121)
    CheckSum:         000271EA
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
}}}
",lorcan
13851,Linked clone not created in group subdirectory,other,VirtualBox 4.3.20,2015-02-18T01:14:24Z,2015-02-18T01:14:24Z,2015-02-18T01:14:24Z,"I have several VMs in a group.
I create a linked clone of one of the VMs in the group.
The linked clone VM appears in the group in the VirtualBox Manager GUI, but the directory containing the new VM does not appear in the group subdirectory, as I would expect it to.

Eg given virtual machines in groups (named ""Beta A testing"", ""Beta B testing""), with both groups and directory listing like this:
{{{
\---Virtual machines
    +---Beta A testing
    |   +---Version 10.1 SP2 updated to SP3 Beta A
    |   +---Version 10.1 SP3 Beta A
    |   +---XP Version 10.1 SP2 updated to SP3
    |   \---XP Version 10.1 SP3
    +---Beta B testing
    |   +---SP2 updated to SP3 beta B
    |   +---SP3 beta B
    |   +---XP SP2 updated to SP3 beta B
    |   \---XP SP3 beta B
    +---Build
    +---Version 10.1 SP1
    +---Version 10.1 SP2
    \---Windows 7
}}}
I made a linked clone of ""SP3 beta B"", called SFX-23779. The new directory SFX-23779 (containing the logs and snapshops for the new VM) appeared under ""Virtual machines"", whereas I expected it to appear under ""Beta B testing"" for consistency with the other grouped VMs.",m6477
13774,"OpenGL, Direct3d screenshot making error",Windows,VirtualBox 4.3.20,2015-01-21T15:29:25Z,2015-02-05T09:00:05Z,2015-02-05T09:00:05Z,"Like it is listed here:
https://www.virtualbox.org/ticket/10794
and here:
https://www.virtualbox.org/ticket/10800

In both cases the screenshot making is not working in the inteded way, I can see through the active window which have the 3d application in the screenshot.
The 3d content is completely transparent.
Integrated Intel HD video card on a T520 notebook, with only 3D DirectX enabled on the guest. (Win7 Enterprise X64 host, Win7 Ultimate X64 guest) Latest patch on everything: drivers, OS, VBox on both machines.
On guest VBoxWindowsAdditions-amd64.exe was also installed from this: http://download.virtualbox.org/virtualbox/4.3.20/VBoxGuestAdditions_4.3.20.iso

Host 8GB RAM, 2 display

Guest RAM 2048MB, VRAM 256MB, 1 display, I/O APIC enabled, PIIX3, 1 core, VT-x enabled, memory virtualization enabled, 2-way shared clipboard enabled

Please do not mark it obsolete, since it is a live bug in the latest version.
I will gladly give more info if needed.",xzvf
13808,VM window should stay maximized when moving to a screen with a different resolution,Windows,VirtualBox 4.3.20,2015-02-03T21:32:50Z,2015-02-04T13:51:56Z,2015-02-04T13:51:56Z,"VirtualBox: 4.3.20 r96997

Host: Windows 8.1 Enterprise 64-bit

Guest: Windows 7 Enterprise 64-bit

Problem:  I am running VirtualBox on a laptop with a secondary monitor connected via a display-port to VGA adapter coming out of the laptop and VGA in on the monitor.  The resolution of the laptop is 3200x1800 and the resolution of the secondary monitor is 1680x1050.  When I move the guest machine from the laptop screen to the secondary monitor I expect the VirtualBox window to resize to the new resolution but it does not. All other applications do this.  This is a bit confusing to explain but bear with me here...

Example:
I start Virtualbox and start my guest machine.  These windows are on my laptop screen and maximized, so running at 3200x1800.  I move the guest machine window over to my secondary monitor but the window does not resize.  I believe the window is still running at 3200X1800 instead of resizing to 1680x1050 when moved.  This is causing issues because the guest machine is pretty much unusable as everything is at a very high resolution but running on a monitor that does not have that resolution.  I can adjust the window or the resolution of the guest machine, but nothing changes.  The window still is running at 3200x1800 thus causing the guest machine to appear very tiny.",gregv
13798,Junctions to host,Windows,VirtualBox 4.3.20,2015-01-29T09:42:36Z,2015-01-29T09:42:36Z,2015-01-29T09:42:36Z,"Hello

I don't know if it is a bug or a technical restriction.
I tried to make a link (junction) to a folder from win 8.1 (guest) to my windows 7 (host).
My idea was, instead to add a drive to an UNC Path (\\vboxsrv\hostshare), I make a link to this folder.
But when I access to this folder (double click in explorer), folling message appears (see attachment).

What do you this?
Should this work or isn't possible to do this?

Thanks",Michael
13779,vobxsf breaks on long paths (> 260) with Windows host,Linux,VirtualBox 4.3.20,2015-01-22T21:00:44Z,2015-01-22T21:00:44Z,2015-01-22T21:00:44Z,"Linux guest (Ubuntu 14.10), Windows (8.1) host.

When using shared folders, if the path length of a file is greater than 260, the file doesn't appear correctly in the guest. Note that the problem appears to be related to the path length in the host (Windows), rather than the path length in the mounted filesystem in the guest.

Here is an example of the problem:

{{{

$ ls -l
ls: cannot access 22-20131023143021.zip: No such file or directory
ls: cannot access properties.xml: No such file or directory
total 4
?????????? ? ?   ?      ?            ? 22-20131023143021.zip
-rwxr-xr-x 1 abc abc 3819 Jan 20 10:26 content.txt
?????????? ? ?   ?      ?            ? properties.xml

}}}

In the host, the length of the path (in the host fs) of context.txt is 258. It is readable in the guest (Linux). The other two files have a path length > 260 and are not accessible
",__cc__
13758,Win7-64 install fro SCCM image,Windows,VirtualBox 4.3.20,2015-01-14T14:35:23Z,2015-01-14T14:35:23Z,2015-01-14T14:35:23Z,"new VM WIn7Ent64. install always fails after loading boot image from SCCM.
pls. see attached log.",Papika
13704,No Window Decorations in Zorin 9 after Guest Additions - VirtualBox 4.3.20,Linux,VirtualBox 4.3.20,2014-12-20T05:00:26Z,2015-01-13T02:43:15Z,2015-01-13T02:43:15Z,"After Installing Zorin 9 32 bit core (3D Acceleration Enabled) I installed VirtualBox Guest Addtions as follows:

In Termainal ran:

sudo apt-get install build-essential linux-headers-$(uname -r) dkms

Then from VirtualBox Menu selected Devices - Insert Guest Additions CD image... And ran it.
After I rebooted all Window Decorations were missing (Minimize Maximize/Restore and Close buttons) I tried everything in Zorin but found that it happened after I installed Guest Additions from VirtualBox.

The only fix was to install Guest Additions from terminal in Zorin using the following:

sudo apt-get update

sudo apt-get install virtualbox-guest-x11

and choose Y to overwrite

I rebooted and my Window Decorations Were Back.

I think the problem is with 4.3.20 Guest Addtions CD image",FutureAlex
13736,Function Keys in VirtualBox are inactive,Windows,VirtualBox 4.3.20,2015-01-05T13:45:38Z,2015-01-05T14:09:20Z,2015-01-05T14:09:20Z,"Hallo
My PC is ASUS ZenBook with OS:Win7 Prof (Host).
I have Installed  WM VirtualBox 4.3.20 with Extension package.
My Guest OS is Win98.
In my Application I need the function keys F1 to F12.
I have try all possible, I also search in the community FAQ but without
success. The proposition I have found there are without success. activate
What I have to do for activating the F1 to F12 ??
Thank You in advance
Anton
",akurka
13732,Direct3D on Intel GMA X3000 hangs VM and manager GUI,Windows,VirtualBox 4.3.20,2015-01-05T03:51:50Z,2015-01-05T03:51:50Z,2015-01-05T03:51:50Z,"Guest: XPSP3 32-bit[[br]]
Host:  XPSP3 32-bit[[br]]
Video core: Intel GMA X3000 (G965 Express Chipset Family)

Easiest way to repro is run DxDiag in guest (obviously install and enable 3D acceleration first). VM and manager GUI hang and have to be killed but host seems unscathed.

VBox log and DxDiag.txt from host attached. The log is possibly truncated by my having to kill the process (or maybe it flushes after each line, I don't know).",hugh2
13731,High CPU load when smooth-scrolling,Linux,VirtualBox 4.3.20,2015-01-04T02:26:32Z,2015-01-04T02:26:32Z,2015-01-04T02:26:32Z,"I have noticed that when smooth-scrolling in either Firefox or Chrome, either by continuously running the mouse wheel, or by mid-click to activate auto-scroll and then moving the cursor slightly to slowly start scrolling, I get very high CPU load. At usual reading pace I can often get 70-80% CPU, slightly less when I scroll slower. This surprises me, since scrolling really shouldn't be a CPU intensive task! Under the Windows host, smooth scrolling never takes any CPU at all. Also, the Linux guest feels a bit more sluggish when scrolling compared to the Windows host. I am running Compiz, and 3D is generally working well (if using the 3D-box desktop, and it rotates nicely).

It is a bit of a bother, since this significantly reduces battery time: When just browsing the web, I scroll while reading, and this usually loads the CPU high enough to spin up the fan. Obviously, all that heat is a battery drain!

I am using a dual-boot Windows 8.1 and Windows 7 host with an Ubuntu 14.04 LTS guest on an ASUS 550JV laptop (Core I7-4700HQ, 16GB RAM and nVidia GT-750M). I have seen this on Virtualbox 4.3.12 (with guest additions 4.3.14) and on 4.3.20 (with guest additions 4.3.20). Virtualbox has one core and 6GB RAM. 3D in general is working well, as mentioned.",00prometheus
13723,Gnome 3 window decoration issue on Debian guest with 3D acceleration enabled,Linux,VirtualBox 4.3.20,2014-12-30T17:19:05Z,2015-01-01T07:13:31Z,2015-01-01T07:13:31Z,"I searched for an already opened ticket: I found
ticket:12320
ticket:12746
ticket:12941
that seem similar, but in my case there is no guest crash, actually just some X server problems.

Host:
{{{
Windows 8.1
16GB RAM
NVIDIA GTX 860M (dedicated GPU)
Intel HD 4600 (integrated GPU)
VirtualBox 4.3.20r96997
}}}
Guest:
{{{
Debian 8 (testing) quite fresh installation
3D acceleration enabled
}}}

Issue:
It looks everything work fine....but after some using of Totem video player, window decoration crashes (see the attached screenshot): for example

1. If I select menu->properties during video playback, its window is not visible because video rectangle remain ""on top"", while the properties window lies correctly above the title bar.
2. If I open and close several video files, suddenly window decoration crashes. Buttons are not drawn (even the date and the clock) and there are white or gray rectangles in their place. If I restart gnome 3 (alt+F2 then ""r""), some buttons are still not clickable, i.e. poweroff button, some other are missing (I suppose it is a gnome 3 behaviour after video capabilities have been switched from 3D to 2D). I have to reboot from a terminal (TTY).

Xorg logs are clean, while virtualbox guest logs show GuestAdditions errors: (full log is attached)
{{{
00:07:49.644926 Guest Additions capability report: (0x5 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:07:50.050200 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
00:07:50.050224 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
00:07:50.050288 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400
00:07:50.050301 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid..
00:08:00.952341 Guest Additions capability report: (0x1 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:08:00.956122 Guest Log: VBoxGuestCommonIOCtl: HGCM_CALL: Invalid handle. u32Client=13
00:08:00.956161 Guest Log: VBoxGuestCommonIOCtl: HGCM_CALL: Invalid handle. u32Client=13
}}}",debianized
13721,Machine Shared Folders and Repeatable Serial Numbers (Win),Linux,VirtualBox 4.3.20,2014-12-28T22:47:15Z,2014-12-28T22:47:15Z,2014-12-28T22:47:15Z,"Ubuntu 14.04.01 LTS With VBox 4.3.20

A windows Guest program (MediaMonkey) makes use of the ""Serial Number"" scheme assigned to drives in windows to build the database of files.  After reboot, the Serial Number reported to the Guest changes, causing issues for the Guest program to link up the mapped drive to it's database representing it.

This seems to be new behaviour when I upgraded to 4.3.20, prior to this the serial numbers would not change.  May I suggest that the serial number reported to the Guest OS be calculated from the host's Path so that it remains constant as long as the host's path configuration is constant?",longj
13710,Error code 5 with install windows 7,Windows,VirtualBox 4.3.20,2014-12-23T07:54:44Z,2014-12-23T07:54:44Z,2014-12-23T07:54:44Z,"Hi,

When I want install Windows 7 on VM, I have ""code error 5"".

This probleme come from the BIOS (old BIOS make this with Windows 7 CD bootable).
It's possible to update BIOS of VM in Virtual Box? 
Or propose a choice

Best regards",Olivier69
13675,Crash due to windowed screen spanning monitors,Windows,VirtualBox 4.3.20,2014-12-07T09:48:09Z,2014-12-07T09:48:09Z,2014-12-07T09:48:09Z,"4.3.2 I can stretch the display across multiple monitors with no issues. The display shrinks back to the main display when the system hibernates but can just be resized on wake-up.
All releases after this do not function this way, resulting in BSOD crash.
4.3.20 I can't even stretch the window beyond the main display.

There is a memory.dmp of 350mb created before I rolled back but it may not be complete as I usually just close the VM down and start over.
LMK if a full dump is of any use and I'll reinstall an interim release and replicate the crash.",akaAlso
13664,Guest additions failed after upgrading to 4.3.20 on ubuntu 14.04.1 LTS guest / W7 host,Linux,VirtualBox 4.3.20,2014-12-02T13:40:44Z,2014-12-05T11:58:22Z,2014-12-05T11:58:22Z,"I upgraded my host to 4.3.20 and also the additions into all my existing and running 4.3.18 VM's.
I didn't see anything special during the upgrade.
I noticed the cut/paste with the host not working on a desktop install.
I got to the boot.log and noticed the additions failed (modprobe vboxguest failed).
I noticed stange characters in voboxadd-install.log at the end of the make statement.
Seem to me something went wrong here !
",micwic
13633,Unable to delete snapshot - Hard disk 'Disk location' has more than one child hard disk (3),Windows,VirtualBox 4.3.20,2014-11-21T20:45:49Z,2014-11-21T20:45:49Z,2014-11-21T20:45:49Z,"Hi,

I am trying to delete snapshot on VM but getting error message - Hard disk 'Disk location' has more than one child hard disk (3)

VM Version - 4.3.20 r96996
OS - Windows 7
OS on VM- windows server2003

Details about the error:
Failed to delete the snapshot Snapshot 1 of the virtual machine XXXXXXXXXXXXX.

Hard disk 'H:\infor.vdi' has more than one child hard disk (3).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Please take a look.
",Mahi
13884,Keys repeat in guest VM (Windows 7 Pro 32 bit OS),other,VirtualBox 4.3.22,2015-02-23T15:02:57Z,2020-04-13T08:19:51Z,2020-04-13T08:19:51Z,"Periodically the keys will repeat in the VirtualBox guest OS. I am running 4.3.22 r98236 with VirtualBox guest additions and the extension pack for the same version.

This has been happening for many months. I was following a discussion in https://forums.virtualbox.org/viewtopic.php?f=8&t=55373&sid=5dede60332149c70efbe3c8be4fcfd97&p=313722#p313722 but it was suggested to open a ticket for the issue.

The problem does not occur on the host, only the guest. I just had the issue occur  at 2/23/2015 9:40 AM, tried to check the vbox.log but did not see anything that I could relate to the problem. I have attached the logs. The 



",kjoyce
13889,VirtualBox Bridged Networking Driver error,other,VirtualBox 4.3.22,2015-02-24T17:13:50Z,2017-02-24T06:32:40Z,2017-02-24T06:32:40Z,"Hi all!

If use Intel mainbord ethernet adapter and like setting VLAN - installed and ENABLED VirtualBox Bridged Networking Driver -, beyond possibility enabled status on for lan adapter.

If disabled VirtualBox Bridged Networking Driver in LAN adapter properties, work anyone.

(guest not running)",Lacus
13847,vpnc no response from target after upgrade to 4.3.20 and 4.3.22,Linux,VirtualBox 4.3.22,2015-02-17T14:20:10Z,2015-08-30T23:54:57Z,2015-08-30T23:54:57Z,"Host is Win7, Guest is OEL6.  Have been using vpnc to connect to Cisco VPN for several years.  After upgrade of VirtualBox from 4.3.12 to 4.3.20 it stopped working with ""vpnc: no response from target"". Restarting guest and host did not help. Downgrading to VirtualBox 4.3.12 resolved the issue. Tried upgrading to VirtualBox 4.3.20 again, just in case a driver got hosed during first attempt, but it did not work.  Reverted back to 4.3.12 and having been running that for months now.

Today I tried upgrading to VirtualBox 4.3.22, hoping the issue would be fixed, but it still doesn't work.  I tried the same reboot guest and host after upgrade but no luck.  Reverted back to 4.3.12 and it works fine now.",Dave Musci
13828,Drag-and-drop not working in either direction,Linux,VirtualBox 4.3.22,2015-02-13T14:28:32Z,2015-08-28T07:26:12Z,2015-08-28T07:26:12Z,"Host: Windows 7, all latest updates
Guest: XUbuntu 14.04.1, all latest updates

Drag-and-drop does not work in either direction.  I have tried changing the menu option to enable it only in one direction, as well as bidirectional, but nothing works.

I've checked the manual, and it says drag-and-drop should work for a Windows host and Linux guest.  But in this case it doesn't.

Shared folders do work, so that's my workaround for the moment.  (Although there's another bug for shared folders to report separately.)

The clipboard does work for copying text in both directions.  It does not let me copy files in either direction.  It's not clear from the manual whether it should, but I have to assume it's text-only.  (This is a shame, when VMware Player does it fairly seamlessly.)",gbartlett
13841,Oracle Vbox crashes on full screen,Linux,VirtualBox 4.3.22,2015-02-16T15:22:58Z,2015-06-29T05:41:28Z,2015-06-29T05:41:28Z,"While trying to view in full screen Vbox crashes with error ""the instruction at 0x000000000 referenced memory at 0x000000000. The memory could not be written."" ",ddfedora21
14173,Starting a Virtual Machine in Jenkins via batch script causes immediate crash and result in aborted state,Windows,VirtualBox 4.3.22,2015-06-03T23:29:33Z,2015-06-03T23:29:33Z,2015-06-03T23:29:33Z,"== Symptom ==
Whenever I try and start a VM from the Execute Windows Batch Command inside a freestyle Jenkins job, my VM immediately crashes.

== Details ==
Trying to execute a batch script inside a Jenkins job that starts a Virtual Machine via a batch script will immediately crash and go to the aborted state.

However, the same exact batch script can be ran by the host machine with the same variable and parameters perfectly fine manually. 

Also another workaround is to have the Virtual Box GUI interface open and running and the VM will seem to start.

Is this a permissions issue?

== Steps to be able to duplicate the bug ==
1. Have an instance of Jenkins running on the host machine.
2. Create a freestyle Job that will allow you to execute Windows batch scripts
3. Then create a batch script as such 

{{{
cd ""C:\Program Files\Oracle\VirtualBox""
VBoxManage.exe ""Name_OF_VM""
}}}

4. save and build the job
5. Observer that it starts up but then immediately crashes and goes to the abort state.

== Versions Affected ==

 * Windows 8.1 64-bit (Host and Guest)
 * Version 4.3.22

== Workaround ==
Please see Details for any workarounds at the moment.

",MTaylor
13862,"Sound not working 4.3.22 windows xp guest, windows 8.1 host",Windows,VirtualBox 4.3.22,2015-02-19T22:59:07Z,2015-03-09T05:49:43Z,2015-03-09T05:49:43Z,"HI many others also reported on forum that sound that was working has stopped in newer version.  I tried reinstalling drivers, installing downloaded driver, reinstalling guest additions, installing K-lite codec pack, checking all volume controls not muted.  Also uninstalled, rebooted and reinstalled host sound drivers. 
In meantime will be downgrading to older 4.3.20 where was working sound. Host sound works well through speakers. Please fix soon as prefer to use current version.",Astrogirl
13879,Seamless mode tri-head hosts,Linux,VirtualBox 4.3.22,2015-02-22T11:32:48Z,2015-02-22T11:32:48Z,2015-02-22T11:32:48Z,"Hi,

When using seamless mode with 3 monitors, only 2 monitors are displayed. The main monitor does not display guest windows (and taskbar); but we see them on the preview and we can drag them over the ""not displayed monitor"".

Screenshot attached

All is working fine on dual-screen and in normal mode

Test with 4.3.22 and build 98406",MPoil
13875,Uninstaller doesnt remove all drivers,other,VirtualBox 4.3.22,2015-02-21T11:30:57Z,2015-02-21T11:30:57Z,2015-02-21T11:30:57Z,"Hello,

The VirtualBox uninstaller on Windows does not remove the following drivers even after multiple reboots:

VirtualBox Host-Only Ethernet Adapter: 
\SystemRoot\system32\DRIVERS\VBoxNetAdp.sys

VirtualBox Bridged Networking Service: 
\SystemRoot\system32\DRIVERS\VBoxNetFlt.sys

This has the added effect of showing these devices to end-users when calling GetAdaptersAddresses and specifying the GAA_FLAG_INCLUDE_ALL_INTERFACES flag.

The uninstaller should add these drivers to the PendingFileRenameOperations registry key allowing Windows to remove them on system restart.",dmex04
13861,Feature Suggestion: usb and other devices controlling of connections admin permissions,Windows,VirtualBox 4.3.22,2015-02-19T22:51:48Z,2015-02-19T22:51:48Z,2015-02-19T22:51:48Z,"There should be a way to at least hide (as in VMware player)
or preferably disable the usb connections or restrict for 
non admin users, 
the connecting and disconnecting of specific usb and other devices
shared with the host so kids/non admin users can't randomly connect
and disconnect devices. 
One example is the mouse/keyboard -if disconnected instability in host also.
Or if loading a VDI for virtualbox off the external usb
hard drive you don't want this accidentally disconnected from the host, 
as you may have data loss and crash VM.

I am new to using virtual box and have yet to use the usb filters -not sure how this works.",Astrogirl
13853,SDK: Java via webservice: IMachine.setGroups causes IMachine.deleteConfig to work wrongly,all,VirtualBox 4.3.22,2015-02-18T09:30:44Z,2015-02-18T09:30:44Z,2015-02-18T09:30:44Z,"Setting:
Using a java application to access webservice from SDK to control virtual box.

Problem: IMachine.deleteConf does not delete files when machine is in a group other than ""/""

Use case:
- Create clones
- Add clones to group ""/Clones"" (and only this group)
- Verify: Files of clone were created in subfolder ""/Clones/Name_of_clone
- Delete clones using 'deleteConf' does NOT delete files and does not fail! Documentation does not mention anything related to that

Workaround
- Before deleting, change group back to ""/"". delteConf works as expected

",andresluzern
13843,MSCOM Java Binding - Breakage,all,VirtualBox 4.3.22,2015-02-16T16:26:17Z,2015-02-17T21:09:03Z,2015-02-17T21:09:03Z,"MSCOM Java bindings are currently unusable as they fail on any method not returning a String.[[BR]]
[[BR]]
Test code[[BR]]

{{{
public class MsComTest {
   
   public static void main(String[] args) {
      VirtualBoxManager mgr = VirtualBoxManager.createInstance(null);
      try {
         mgr.getVBox().getRevision();
      } finally {
         mgr.cleanup();
      }
   }
   
}
}}}
",Max D
13840,Trailing spaces in VM names are not handled consistently when grouping,all,VirtualBox 4.3.22,2015-02-16T01:56:59Z,2015-02-16T01:56:59Z,2015-02-16T01:56:59Z,"1. Create 3 new VMs ""test1"", ""test2"", ""test3 "". The VM names do not include the quotation marks, but test 3 has a trailing space in its name.
2. Select all three new VMs and create a new group for them.

The VMs all appear in the group in the Virtual Box Manager GUI, but when I look at the directories where the data is stored, I see that test1 and test2 have been moved into a subdirectory named ""new group"", but test3_ (directory name has underscore instead of space) has not been moved into the subdirectory - it remains in its original parent directory
",m6477
13832,VirtualBox 4.3.22 Breaks Physical Network Card Config,Linux,VirtualBox 4.3.22,2015-02-13T18:11:52Z,2015-02-13T18:11:52Z,2015-02-13T18:11:52Z,"

I'm having the same problem with VirtualBox 4.3.22 for Windows on Windows 7 Pro 64 Bit patched as of today. After virtual box install it disabled eth0 (first NIC) and I have no networking at all. From the command line it looks like the bridged network is being assigned to the physcial interface and that breaks connectivity.

I had to log in as Admin and disable and reenable both interfaces for it to sort of work. Not it keeps putting the card off line and online. Not sure how this bug reared its ugly head so often but it has.
",evit
13922,Cant install openvpn when virtualbox is installed. Windows10 x64 build9926,all,VirtualBox 4.3.24,2015-03-04T22:52:03Z,2016-06-03T14:50:06Z,2016-06-03T14:50:06Z,"Hi, on windows 10 i cant install openvpn only when virtual box is already insalled. It stuck on tap-installer. Without virtualbox install goes fine.",bullet92
13933,VirtualBox 4.3.24 Could Not Initialize GLX,Linux,VirtualBox 4.3.24,2015-03-06T18:14:56Z,2016-02-26T11:11:23Z,2016-02-26T11:11:23Z,"I've a problem with running qmlscene from Qt. The program aborts with message: 'Could Not Initialize GLX'. The program runs fine when '3D acceleration' is switched off in the vm settings.

{{{
Host:
Windows 7 x64
Radeon R7 250

Guest:
Linux arch-vm 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux

VirtualBox:
4.3.24

}}}

{{{
qmlscene
libGL error: pci id for fd 10: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
OpenGL Warning: glXGetFBConfigAttrib for 0000000001acf250, failed to get XVisualInfo
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000001acf250
OpenGL Warning: Retry with 0x8002 returned 0 visuals
Could not initialize GLX
Aborted (core dumped)
}}}

I've compiled the Qt with debug symbols and got the following backtrace from qmlscene. 

{{{
#0  0x00007ffff4d494b7 in raise () from /usr/lib/libc.so.6
#1  0x00007ffff4d4a88a in abort () from /usr/lib/libc.so.6
#2  0x00007ffff5e38460 in qt_message_fatal (context=..., message=...) at /home/wojtek/banana-pro/qt5/qtbase/src/corelib/global/qlogging.cpp:1422
#3  0x00007ffff5e34e00 in QMessageLogger::fatal (this=0x7fffffffd3b0, msg=0x7fffee5e64c1 ""Could not initialize GLX"") at /home/wojtek/banana-pro/qt5/qtbase/src/corelib/global/qlogging.cpp:643
#4  0x00007fffee590d75 in createDummyWindow (dpy=0x4296d0, config=0x5e50f0, screenNumber=0, rootWin=373) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:103
#5  0x00007fffee591d3e in QGLXContext::init (this=0x454090, screen=0x438cc0, share=0x0) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:294
#6  0x00007fffee59113f in QGLXContext::QGLXContext (this=0x454090, screen=0x438cc0, format=..., share=0x0, nativeHandle=...)
    at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qglxintegration.cpp:170
#7  0x00007fffee55b083 in QXcbIntegration::createPlatformOpenGLContext (this=0x41d470, context=0x44d270) at /home/wojtek/banana-pro/qt5/qtbase/src/plugins/platforms/xcb/qxcbintegration.cpp:254
#8  0x00007ffff6ae00fc in QOpenGLContext::create (this=0x44d270) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qopenglcontext.cpp:597
#9  0x00007ffff6a959ed in QGuiApplicationPrivate::init (this=0x41a000) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:1295
#10 0x00007ffff6a92c6f in QGuiApplication::QGuiApplication (this=0x7fffffffda00, p=...) at /home/wojtek/banana-pro/qt5/qtbase/src/gui/kernel/qguiapplication.cpp:561
#11 0x00007ffff71c7193 in QApplication::QApplication (this=0x7fffffffda00, argc=@0x7fffffffd8ec: 1, argv=0x7fffffffe008, _internal=328706)
    at /home/wojtek/banana-pro/qt5/qtbase/src/widgets/kernel/qapplication.cpp:562
#12 0x0000000000405427 in main (argc=1, argv=0x7fffffffe008) at /home/wojtek/banana-pro/qt5/qtdeclarative/tools/qmlscene/main.cpp:412
}}}

The problem seems to be in the following part of code (qglxintegration.cpp:103):

{{{
XVisualInfo *visualInfo = glXGetVisualFromFBConfig(dpy, config);
if (!visualInfo)
   qFatal(""Could not initialize GLX"");
}}}

I think the contents of the dpy are:

{{{
{ext_data = 0x0, free_funcs = 0x42aa00, fd = 3, conn_checker = 0, proto_major_version = 11, proto_minor_version = 0, vendor = 0x428890 ""The X.Org Foundation"", resource_base = 41943040, 
  resource_mask = 2097151, resource_id = 0, resource_shift = 0, resource_alloc = 0x7ffff42a5590 <_XAllocID>, byte_order = 0, bitmap_unit = 32, bitmap_pad = 32, bitmap_bit_order = 0, nformats = 7, 
  pixmap_format = 0x42aa50, vnumber = 11, release = 11701000, head = 0x0, tail = 0x0, qlen = 0, last_request_read = 395, request = 395, last_req = 0x7ffff45a39c0 """", buffer = 0x430a50 ""\217"", 
  bufptr = 0x430a50 ""\217"", bufmax = 0x434a50 """", max_request_size = 65535, db = 0x0, synchandler = 0x0, display_name = 0x428ad0 "":0"", default_screen = 0, nscreens = 1, screens = 0x42ab00, motion_buffer = 256, 
  flags = 0, min_keycode = 8, max_keycode = 255, keysyms = 0x0, modifiermap = 0x0, keysyms_per_keycode = 0, 
  xdefaults = 0x436720 ""Xft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintmedium\nXft.rgba:\tnone\n"", scratch_buffer = 0x0, scratch_length = 0, ext_number = 7, ext_procs = 0x4541a0, 
  event_vec = {0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a70d0 <_XWireToEvent> <repeats 33 times>, 0x7ffff45b1ec0, 
    0x7ffff42a7090 <_XUnknownWireEvent> <repeats 30 times>, 0x7fffee313190 <repeats 17 times>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42fb9c0, 
    0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff0d3d1b0, 
    0x7ffff42a7090 <_XUnknownWireEvent> <repeats 12 times>, 0x7ffff5b1fc50 <repeats 17 times>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 
    0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>, 0x7ffff42a7090 <_XUnknownWireEvent>}, wire_vec = {0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x0 <repeats 33 times>, 0x7ffff45b1e40, 0x7ffff42a70c0 <_XUnknownNativeEvent> <repeats 30 times>, 0x7fffee30e8c0 <repeats 17 times>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff0d3d0e0, 0x7ffff42a70c0 <_XUnknownNativeEvent> <repeats 12 times>, 
    0x7ffff5b1fc40 <repeats 17 times>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 
    0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>, 0x7ffff42a70c0 <_XUnknownNativeEvent>}, lock_meaning = 0, lock = 0x428b50, async_handlers = 0x0, bigreq_size = 4194303, 
  lock_fns = 0x4287d0, idlist_alloc = 0x7ffff42a55e0 <_XAllocIDs>, key_bindings = 0x0, cursor_font = 0, atoms = 0x0, mode_switch = 0, num_lock = 0, context_db = 0x0, error_vec = 0x0, cms = {defaultCCCs = 0x0, 
    clientCmaps = 0x0, perVisualIntensityMaps = 0x0}, im_filters = 0x0, qfree = 0x0, next_event_serial_num = 1, flushes = 0x0, im_fd_info = 0x0, im_fd_length = 0, conn_watchers = 0x0, watcher_count = 0, 
  filedes = 0x42a9d0 ""\003"", savedsynchandler = 0x0, resource_max = 2097146, xcmisc_opcode = 0, xkb_info = 0x436780, trans_conn = 0x0, xcb = 0x428730, next_cookie = 0, generic_event_vec = {0x0, 0x0, 0x0, 
    0x7fffee314260, 0x0 <repeats 124 times>}, generic_event_copy_vec = {0x0, 0x0, 0x0, 0x7fffee312670, 0x0 <repeats 124 times>}, cookiejar = 0x0}
}}}

I still have to figure out how to get contents of config variable as gdb gives me <incomplete type> when I try to print it.

Please let me know if I can further help. I'd really like to see this problem fixed.",bvr
13946,Unable to Use USB devices on Virtual box,Linux,VirtualBox 4.3.24,2015-03-09T15:09:41Z,2015-12-22T15:33:02Z,2015-12-22T15:33:02Z,"We are using Virtual Box 4.3.24 and inside we are using Ubuntu 14.
and also in my Local machine windows 7 we are using McAfee DLP 9.3.

* we raised a ticket with McAfee regarding this and they are saying it must be a problem with virtual Box.

when we uninstall DLP USB works fine in Virtual box. ",sathi
13939,Errort when pressing right mouse buttion in CD/DVD device selection dialog,all,VirtualBox 4.3.24,2015-03-07T23:44:49Z,2015-05-18T13:11:02Z,2015-05-18T13:11:02Z,"When the CD/DVD Device selection dialog is shown and you press the right mouse button to bring up a popup menu the guest aborts with a C++ runtime error.

Host Windows Server 2003 x64 / Windows XP64

Also occurs with latest test build. 

Other than the termination dialog window no error in event log or elsewhere can be found.

FRG",frg
13937,Windows 10 TP network bridge causes major fault,all,VirtualBox 4.3.24,2015-03-07T19:11:33Z,2015-04-02T09:32:55Z,2015-04-02T09:32:55Z,"This is similar to ticket number 13912. When VB is installed in the latest beta of Windows 10 technical preview, the host machine halts upon restart. The only thing working is the mouse, nothing else works.

The computer works fine if the network cards are disabled in Windows, but this leaves end users unable to access any network.",dhrida
13942,Failed to start the virtual machine when seemingly unreachable,Windows,VirtualBox 4.3.24,2015-03-09T06:39:51Z,2015-03-23T11:28:17Z,2015-03-23T11:28:17Z,"I as a system connected to the virtual media used images located on a network drive.
In the case where the network drive is not available, the virtual system can not start.
  It would be better to just give a message about the unavailability of the resource, not to block the program.",and_kors
13953,WinXP guest machines do not start after the update to version 4.3.24 & host system reboott,Windows,VirtualBox 4.3.24,2015-03-13T20:58:08Z,2015-03-22T12:52:20Z,2015-03-22T12:52:20Z,"After the update to version 4.3.24 from 4.2.18 I was able to run a win XP guest machine but after the host (Win 7 Home Premium x64, AMD, Acer Aspire) reboot it has been possible no longer. I tried to turn off PC Tools 7 firewall, antivirus AVG 2015 and Iobit Advanced Care 8.1 but without a success. I am enclosing screenshots and the VM guest machine logs. Could you look at the issue?

The error messages are:
""Error relaunching VirtualBox VM process: 5
Command line: '...--starttvm...--no-starttvm-errormsgbox...""

""The virtual machine '...' has terminated unexpectedly during startup with exit code 1(0x1)...
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {...}""
",Kola Wisarionowicz
13958,GUI does not indicate corrupt/missing save file in an obvious way,all,VirtualBox 4.3.24,2015-03-16T14:15:52Z,2015-03-16T14:20:14Z,2015-03-16T14:20:14Z,"I have a windows 8.1 x64 host running 4.3.24 which cannot start a Windows 7 Enterprise x64 guest with saved state after rebooting the host OS. Something appears to have removed or corrupted the save-state file, but the GUI does not indicate this in an obvious way (it does appear in the log, however).

More desirable behavior would be a ""Save file is missing or corrupt. Restart VM?"" dialog. Instead, I get this, which is also symptomatic of a large number of other (more complex) failures:

{{{
Failed to open a session for the virtual machine CDW Win7.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}
}}}

The Log:

{{{
VirtualBox VM 4.3.24 r98716 win.amd64 (Mar  2 2015 14:18:45) release log
00:00:03.174146 Log opened 2015-03-16T13:53:05.920532400Z
00:00:03.174149 Build Type: release
00:00:03.174155 OS Product: Windows 8.1
00:00:03.174157 OS Release: 6.3.9600
00:00:03.174158 OS Service Pack: 
00:00:03.258341 DMI Product Name: 20246
00:00:03.262022 DMI Product Version: Lenovo IdeaPad Yoga 11S
00:00:03.262030 Host RAM: 8071MB total, 5351MB available
00:00:03.262033 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:03.262034 Process ID: 4556
00:00:03.262035 Package type: WINDOWS_64BITS_GENERIC
00:00:03.262679 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={VM cannot start because the saved state file 'C:\Users\P\VirtualBox VMs\CDW Win7\Snapshots\2015-03-14T16-48-25-963707000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false
00:00:03.263825 UIMediumEnumerator: Medium-enumeration finished!
00:00:03.264472 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 640x480
00:00:03.268691 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 1 as 640x480
}}}
",kc0tfb
13949,All guests fail to start,Linux,VirtualBox 4.3.24,2015-03-10T13:54:37Z,2015-03-16T08:24:39Z,2015-03-16T08:24:39Z,"All guests fail to start at virtualbox 4.3.24


The virtual machine 'bioLinux' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\libindo\VirtualBox VMs\bioLinux\Logs\VBoxStartup.log'.

Code erorr: E_FAIL (0x80004005)
Компонент: Machine
Интерфейс: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

",buratin
13931,Excessive processor use,Linux,VirtualBox 4.3.24,2015-03-06T13:17:07Z,2015-03-10T09:47:37Z,2015-03-10T09:47:37Z,"Since 4.3.22 or so I noticed that after a while VBox is starting to use a lot of processor power. Everything is OK when it starts but after few hours its 90-100% of one thread and some minor-medium use on other threads (35%-40% of total processor time, i7 4770K, 4 cores 8 threads).

Host is Windows 8.1
Guest is 64bit Ubuntu 14.04

It was initially installed under 4.3.20 and there was no problem. It only appeared recently.",randomwhitetrash
13928,Change of behavior of Host Only Network,Linux,VirtualBox 4.3.24,2015-03-06T10:52:19Z,2015-03-06T10:52:19Z,2015-03-06T10:52:19Z,From version 4.3.22 you have added a value for *NdisDeviceType register entry. A value for that entry as NDIS_DEVICE_TYPE_ENDPOINT implies that Windows ignores the endpoint device when it identifies networks. I was using a virtual linux firewall connected to the bridged interface to create a network with different OS including the access to internet from the host. After this change in 4.3.22 Windows does not detect the virtual network and there is no connection from most windows applications.,luisds
13925,file timestamp not preserved on tar-extracted files in shared folders on linux guest windows host,Linux,VirtualBox 4.3.24,2015-03-05T17:36:29Z,2015-03-05T17:36:29Z,2015-03-05T17:36:29Z,"There is a strange behavior, that files extracted from TAR package within shared folders on Linux guest/Windows host, does not preserve file timestamp stored in a tarball. The files' timestamp get converted to the extraction time.

I've searched through Virtualbox issues, and saw another ticket regarding timestamp in shared folders, #6473, but that was solved years ago, and does not apply to this particular issue.

Issue is easily reproducable:
- configuration: Windows 7 Host, Linux (Debian, no GUI) Guest
- using tar command from a Linux Guest shell, create a TAR of an older ""test file"", so the timestamp would be evident,
- delete the ""test file""
- extract the ""test file"" from a tar archive
- the timestamp will be wrong, as tar preserves timestamp by default
- to confirm we can do the same procedure within another Linux Guest folder, other than the shared folder, and the timestamp will be preserved.

Here's code sample, presuming we have a file.pdf test file, within /var/www/shared folder, which is a shared folder, both Linux guest and Windows 7 host can see:

{{{
cd /var/www/shared
ls -la
> -rwxrwxrwx 1 root root 11654 Jan 23 08:16 file.pdf
tar -c -f test.tar file.pdf
rm file.pdf
tar -x -f test.tar
ls -la
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 file.pdf
> -rwxrwxrwx 1 root root 11654 Mar 5 17:30 test.tar
}}}

I would kindly ask anyone to answer if there is a solution to this problem, or is there anything we can do to preserve original timestamps at tar extraction process within shared folders, so we don't need to extract files in a separate folders and move the files back, as we need those timestamps.

We have both, current Virtualbox and current Guest Additions installed.",sargac
13912,Windows 10(host) and virtual box,all,VirtualBox 4.3.24,2015-03-03T05:06:52Z,2015-03-04T22:41:18Z,2015-03-04T22:41:18Z,Host pc-surface pro (i5) causing black screen after install of virtual box.,Bluwolf024
13913,Start a VM at boot time on a Windows host,all,VirtualBox 4.3.24,2015-03-03T09:59:19Z,2015-03-03T15:36:38Z,2015-03-03T15:36:38Z,"Can a VM be started at boot time on a Windows host? 
Documentation (see page https://www.virtualbox.org/manual/ch09.html#autostart ) 
say it is possibile on other hosts (Linux, Solaris, ...).
Does it mean it is not possible on Windows hosts?
If so, can this limitation be inserted in documentation?
If not, can the documentation include instructions to start a guest VM at boot time?

  ",Marius Roma
14102,Kubuntu 15.04 Guest: 3D acceleration broken,Linux,VirtualBox 4.3.26,2015-05-08T16:01:54Z,2019-01-16T08:05:02Z,2019-01-16T08:05:02Z,"3d support is unavailable for every KDE5 (Plasma) based Linux distro on Windows Host. Reference
https://forums.virtualbox.org/viewtopic.php?f=3&t=67589&p=320394#p320394
https://forums.virtualbox.org/viewtopic.php?f=6&t=64452

If 3D acceleration is enabled, KDEs login screen appears normally, one can login. After logging in, the Desktop appears, everything seems to be normal. BUT:

1.) Right clicking somewhere at the desktop doesn't bring up the context menu
2.) Clicking the ""KDE"" Menu: the KDE Menu appears, but the Control Bar disappears completely
3.) When starting an application in KDE Menu (which can still be opened with Alt+F1), the application seems to start, but no application window appears
4.) Trying to get out of KDE and switch to a console TTY (STRG+ALT+F1) just switches to a smaller screen but in this KDEs background image remains.
==> So the Desktop is completely unusable, it isn't even possible to get a terminal window, so one even can't examine ""glxinfo"" or some logs...

It looks like the KDE Background lays in front of everything, similar to an ""z-axis 9999""...

After disabling 3D acceleration the Desktops behaves absolutly normal but not with the performance it could have...

My System is this:

Host:
Windows 7 Pro 64Bit
Latest VirtualBox 4.3.26, Extension Pack for 4.3.26 installed

Guest:
Kubuntu 15.04, all current patches installed
GuestAdditions from iso shipped with VirtualBox 4.3.26",sac
17652,Error message,other,VirtualBox 4.3.26,2018-03-30T16:37:24Z,2018-04-19T20:24:34Z,2018-04-19T20:24:34Z,"Trying to run a program called WISEPC 2015 which is supposed to run on VirtualBox, and I get an error message. I have attached the log file and image.

""A critical error has occurred while running the VM and the machine execution has been stopped""

""Unable to allocate and unlock memory. The VM has been paused. Please close applications to free up memory or close the VM.",Carman
13998,Windows 8 - VirtualBox Disables Wireless Display Support,other,VirtualBox 4.3.26,2015-03-27T14:31:59Z,2016-02-29T07:26:12Z,2016-02-29T07:26:12Z,"See https://forums.virtualbox.org/viewtopic.php?f=2&t=66827

I found this out after struggling with my Microsoft Wireless Display Adapter no longer being detected in Windows 8. It didn't matter which machine I used - my Surface or my Laptop. I came across an article that suggested I remove VirtualBox, and voila - ""Connect to a wireless display"" came back. I want to keep using VirtualBox, but I also need WiDi for teaching. Hey Oracle, would you fix this, or suggest a setting I can disable so I can have my wireless display while using your software, please?
",Auri A. Rahimzadeh
14007,Cannot Insert Linked Cloned Into Group,other,VirtualBox 4.3.26,2015-03-29T20:05:41Z,2016-01-22T17:50:21Z,2016-01-22T17:50:21Z,"== Failed Scenario ==
Inserted a Base VM into a new Group[[BR]]
Created a snapshot while VM is off[[BR]]
Cloned the snapshot into a new Linked Clone[[BR]]
The linked clone appears on /VBOX main folder, and not under the Group folder[[BR]]
[[BR]]
Extra: Moving out of the group in Vbox UI and in again, or to another group and back, keeps it in the Main Vbox folder


== Workaround ==
Before cloning base VM, move it out of any group to main Vbox folder[[BR]]
Clone base VM[[BR]]
Move Base and Clone VMs into the group",Zvika Dror Zend
13967,NatNetwork limits mtu,Linux,VirtualBox 4.3.26,2015-03-18T13:43:20Z,2016-01-05T16:20:19Z,2016-01-05T16:20:19Z,"I have 4.3.26 in win7 running.

My guests are linux (redhat 5,4 5.10, opensuse 13.2, ...)

All are connected to a virtualbox NatNetwork

Inside the guests an openvpn client is started and i see, that huge packets that the openvpn client sents will be dropped. I investigated further and found out, that the highest Packet size leaving the host is 1295 bytes long.

",RobbySherwood
14070,Virtualbox all guest operating system crashed,all,VirtualBox 4.3.26,2015-04-22T13:11:58Z,2015-09-19T04:30:29Z,2015-09-19T04:30:29Z,"Hi!

My Virtualbox version 4.3.26.98988
My config: Asroc H55M-LE, Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, 8GB RAM Windows 8.1 Professional 64 bit, ATI RADEON HD 5570

If running guest computer, a few seconds freeze. The same problem 32 or 64 bit.

The work is still in version 4.0.26.

(pasted log file removed)",agostonl119
14109,VBoxSVC lingering after VBoxWebSrv,all,VirtualBox 4.3.26,2015-05-12T08:56:39Z,2015-06-23T13:51:58Z,2015-06-23T13:51:58Z,"'''Context'''[[BR]]
Windows 8.1 64 bits
VirtualBox 4.3.26

'''Scenario'''[[BR]]
Without any VirtualBox process already running, start VBoxWebSrv in a prompt in verbose mode, wait for it to start, wait another 2 sec, then press Ctrl+C to quit.
In the Task Manager or via cygwin ps -W, check how long VBoxSVC will remain running before auto shutdown.

'''Issue'''[[BR]]
VBoxSVC remains running for about 6 min then auto exit

'''Expected behaviour'''[[BR]]
VBoxSVC remains running 5-10 sec then auto exit, like when VirtualBox.exe or VBoxManage are run.

'''Detection command in cygwin'''

{{{
while true; do sleep 1; isStarted=1; isFinished=0; while [ $isStarted -ne 0 ]; do sleep 0.5; ps -W | grep -qi vboxsvc; isStarted=$?; done; echo ""VBoxSVC started""; startTime=$(date ""+%s""); while [ $isFinished -eq 0 ]; do sleep 0.5; ps -W | grep -iq vboxsvc; isFinished=$?; done; echo ""VBoxSVC finished""; endTime=$(date ""+%s""); runTime=$(($endTime-$startTime)); echo ""VBoxSVC ran for $runTime seconds""; done;
}}}


'''VBoxSVC average runtime as per the command above'''[[BR]]
367 sec

'''Extra info'''[[BR]]
Behaviour is also visible on Win 7.[[BR]]
Logs & memory dump of lingering VBoxSVC can be found at https://kamax.io/vbox/vboxsvc-lingering_with_vboxwebsrv.zip",Max D
13962,"VBoxClient: Failed to set graphics capability, rc=VERR_NOT_SUPPORTED",Linux,VirtualBox 4.3.26,2015-03-16T23:23:10Z,2015-05-19T09:30:15Z,2015-05-19T09:30:15Z,"Host is Windows 7 Pro 64-bit; guest is openSUSE 13.2 32-bit. Previously functioning correctly with this host and this VM. VM display is no longer using custom dimensions, but preset 4:3-aspect dimensions seem to work. Upon logging in to account in guest OS, I receive the following two errors:

* vBoxClient: Failed to set graphics capability, rc=VERR_NOT_SUPPORTED
* vBoxClient: Initialising service: VERR_NOT_SUPPORTED

The background on this is that I was running VirtualBox 4.3.20 (I think) until this morning. After being prompted about a new version (4.3.24) I decided to upgrade, including updating the Guest Additions. (Oops.) If I remember right, this problem appeared on the first boot after the Guest Additions upgrade. I then tried 4.3.25 (not seeing that .26 was already available), with the matching(?) Guest Additions, and the behavior was the same. I then installed 4.3.26 and the matching Guest Additions, and the behavior is still the same.

While I can use preset sizes, they are all 4:3 and are either significantly smaller than what I want to use or are too large vertically, imposing scrolling (not ideal).

I'm assuming the 'component' is 'guest additions' but I'm not sure that's correct.",Crenel
14127,No bridged network adapter is currently selected,other,VirtualBox 4.3.26,2015-05-17T02:22:10Z,2015-05-17T06:51:23Z,2015-05-17T06:51:23Z,"Windows 7, 64 bit., VirtualBox 4.3.26.

When adding a bridged network adapter to any virtual machine while running virtual box as normal user, the selection for network interfaces is empty. It also states: ""No bridged network adapter is currently selected"":

[[Image(bridge-empty.png)]]

When I run VirtualBox as admin, it works as expected.

The VirtualBox networking driver is setup and installed properly and is enabled for all network interfaces. Example shown here:

[[Image(vbox_driver_interface.png)]]

I found some references to exactly this kind of issue but it seems that the problem is something different in my case because all the workarounds did not work, including:

* Reinstallation of VirtualBox, rebooting, ...
* Delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config, reboot, re-install VirtualBox
* Set a higher value to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters (I Use 0x20), reboot, reinstall etc.

",divB
14120,unable to startvm with high priority on windows,Linux,VirtualBox 4.3.26,2015-05-15T14:39:58Z,2015-05-15T14:39:58Z,2015-05-15T14:39:58Z,"Reference forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=67715#p320669

I recently upgraded to 4.3.26 and now I'm unable to run my batch file that launched my VM with high priority because it seems that there are now 3 different processes that end up getting run. The parent process has the high priority but the actual VM does not which makes it slow. Here is the batch file, not much to it. Anyone found a workaround for this, or should I report it as a bug? 

Batch File contents:
start ""name"" /high ""C:\Program Files\Oracle\VirtualBox\VirtualBox.exe"" --comment name --startvm 1941c965-3dc5-4326-85ae-4400ea58b90d

Things that I've tried without any success:
- running the batch file as admin
- setting VirtualBox.exe to always run as Admin",p1234
14093,AltGr issue on Windows 8.1 and Windows 7 with Czech keyboard layout,Linux,VirtualBox 4.3.26,2015-05-04T10:52:51Z,2015-05-15T13:18:34Z,2015-05-15T13:18:34Z,"This is weird issue, as I am not able to reproduce it alltime, but I know, after several hours of running guest it results in this weird issue.

Host: MS Windows 8.1 (64 bit) or Windows 7 (64 bit).
Guest: Debian Wheezy (64 bit) or Debian Jessie (64 bit).
Guests addons installed from Debian's contrib repository.

AltGr-a (~) is not working, when host keyboard layout is Czech, but works if keyboard layout is English USA. All other AltGr combinations (I use) work fine.

I have already investigated it using {{{xev}}}, I can see keystroke {{{ISO_Level3_Shift}}}, but no {{{a}}} keystroke, but for example AltGr-q (\) I can see both keystrokes.

Auto capture is disabled. When auto capture is enabled it works as expected, but it is not handy for me.

I see similar fixed issue #13216.

Offtopic: Is it possible to create Extension Pack, that will not capture several key combinations, so for example ctrl-alt-(anything) will not be captured even if auto capture feature is enabled?",xdml
14110,GUI anomalies on VHD display Windows 8.1,other,VirtualBox 4.3.26,2015-05-12T10:01:42Z,2015-05-12T10:01:42Z,2015-05-12T10:01:42Z,Some of the list items in the Vbox GUI are malformed @ 3200x1800 resolution on a 16:9 monitor of Dell XPS13 (2015),Wille
14097,I can not connect the drive to Virtualbox.,Windows,VirtualBox 4.3.26,2015-05-06T09:23:52Z,2015-05-06T13:08:09Z,2015-05-06T13:08:09Z,"Не удалось открыть файл виртуального жёсткого диска E:\arut-minimal.vdi.

After transferring from one resource to another error occurred.

Could not get the storage format of the medium 'E:\arut-minimal.vdi' (VERR_NOT_SUPPORTED).
{{{
Код ошибки: VBOX_E_IPRT_ERROR (0x80BB0005)
Компонент: Medium
Интерфейс: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Вызванный интерфейс: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Код ошибки метода: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}
I tried using vboxmanage for repair.
{{{
c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -dry-run -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbo
x\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)

c:\Program Files\Oracle\VirtualBox>vboxmanage internalcommands repairhd -format VDI e:\clients\arut-minimal.vdi
VBoxManage.exe: error: VDI: invalid pre-header in 'e:\clients\arut-minimal.vdi'
VBoxManage.exe: error: Error code VERR_VD_IMAGE_REPAIR_IMPOSSIBLE at F:\tinderbox\win-4.3\src\VBox\Storage\VDI.cpp(3039) in function int __cdecl vdiRepair(const char *,struct VDINTERFACE *,struct VDINTERFACE *,unsigned int)
}}}",Speltor
14092,Ufter upgrade from 4.1.12 to 4.3.26 stops to run VM from PhysicalDrive,all,VirtualBox 4.3.26,2015-05-02T08:38:16Z,2015-05-02T08:38:16Z,2015-05-02T08:38:16Z,"subj

I had working system, ufter upgrade that stopping to work. No config is changed. Logs and configurations attached",KES
14079,The Application failed to initialize properly (0xc000007b),Windows,VirtualBox 4.3.26,2015-04-27T07:34:28Z,2015-04-27T07:35:35Z,2015-04-27T07:35:35Z,"i recently updated the virtualbox from 4.3.18 to 4.3.26
and suddenly i cannot start the virtualbox, error show the application failed to initialized properly (0xc000007b)
how can i repair this, i already use the sfc /scannow on command prompt, uninstall the .net framework (2.0, 3.0, 3.5)
fyi my OS was windows xp SP3 and before the update my virtualbox was running smoothly.
",Handi
14072,Win 8 host.  Cannot change Linux guest priority using Windows taskmgr.exe,Linux,VirtualBox 4.3.26,2015-04-22T19:11:30Z,2015-04-22T19:11:30Z,2015-04-22T19:11:30Z,"I am running Windows 8.1 using VBox 4.3.26 and a couple of Fedora 21 based Linux guests on a 4 core i7 computer with 16 GB of memory.  I would like to be able to set priority or change affinities of the Linux guests but I receive a message from Windows that access is denied.
I tried running taskmgr from an administrative command prompt without success.  Note that I am a Windows administrator as well.
I am able to set priorities or change affinities for other Windows processes but not for the Linux guests.  I even ran Tails, an ISO based TOR Linux implementation, guest as well and could not change its priorities or affinities either. 
To be clear I want to change the Windows priorities for the Linux guests and not priorities inside the Linux guest.  Likewise I want to limit a 2 core guest to certain cores on my i7.
",TKVbox
14044,Crash Virtualbox on Windows 8.1,all,VirtualBox 4.3.26,2015-04-11T17:42:10Z,2015-04-21T18:43:49Z,2015-04-21T18:43:49Z,"Hello. 

Virtualbox Crash when i use file explore (in import application, import vdi...). 

Virtualbox end to tun. I use virtualbox 4.3..26.

Regards",bernalau
14066,CopyTo subcommand complains Source Folder does not exist,Windows,VirtualBox 4.3.26,2015-04-21T14:44:09Z,2015-04-21T14:44:09Z,2015-04-21T14:44:09Z,"VirtualBox Version : 4.3.26 r98988
Host Machine : Windows7 x64 Bit
Guest Machine : Windows7 x64 Bit

Expected Result
=================
valid source Folder from Host gets copied to valid Guest Host recursively

Command
=========
VBoxManage.exe guestcontrol  ""PerfTest_Windows7x64_1-"" copyto F:\VMBOX-Stuff\d\  D:\  --username admin --password  pass, --recursive --verbose


Actual Result
=============
Opening guest session as user 'admin' ...
Waiting for guest session to start ...
Guest session (ID 1) has been started
Copying from host to guest ...
Directory ""D:\"" already exists
Source: F:\VMBOX-Stuff\dummyFolder
Closing guest session ...
VBoxManage.exe: error: Warning: Source ""F:\VMBOX-Stuff\dummyFolder"" does not exist, skipping!

However for a File from the same folder gets successfulyl copied

arg : [VBoxManage.exe, guestcontrol, ""PerfTest_Windows7x64_1-"", copyto, F:\VMBOX-Stuff\dummyFolder\abc.txt, D:\abc.txt, --username, admin, --password, pass, --recursive, --verbose]

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Opening guest session as user 'xpadmin' ...
Waiting for guest session to start ...
Guest session (ID 1) has been started
Copying from host to guest ...
Directory ""D:\"" already exists
Source: F:\VMBOX-Stuff\dummyFolder\abc.txt
Copying ""F:\VMBOX-Stuff\dummyFolder\abc.txt"" to ""D:\abc.txt"" ...
Closing guest session ...

",vazudew
14060,Mouse disappears when over active window when typing in WinXP Guest,Windows,VirtualBox 4.3.26,2015-04-20T15:44:58Z,2015-04-20T15:44:58Z,2015-04-20T15:44:58Z,"Using a windows 7 pro host running virtualbox 4.3.26 running a windows xp guest os in fullscreen mode. Due to an antiquated management system, resolution on the monitor being used for virtualbox is 800x600, though I don't think this matters. To replicate the problem, open notepad (or any program really), position the mouse over the notepad window and start typing. the mouse dissapears until you move it. Now move the mouse outside the notepad window and type - the mouse remains visible the entire time. I've reproduced on multiple computers, hosts, guests, and monitors. To me this is trivial, but to several users this is major as they ""lose"" the mouse and have to ""refind"" it all day long.",Keebs
14050,Bugcheck (BSOD) 0x0000009f (0x00000003) on wakeup with InstantGo,Windows,VirtualBox 4.3.26,2015-04-15T19:43:46Z,2015-04-15T19:43:46Z,2015-04-15T19:43:46Z,"Hi, 
After installing the latest stable x86 version on a Z3735 tablet with Windows 8.1,
I experience recurring bluescreens/reboots when the machine is trying to wake up. Since this Atom class CPU is setup with InstantGo/Connected standby, I suspect that this may be the root cause.

The bugcheck and event log entries point to a problem reinitializing the virtual network adapter on wakeup.

I tried uninstalling Virtualbox and after that,the crashes did not appear anymore.

Device: Pipo W5
CPU: Intel Z3735
RAM: 2 GB
OS: Windows 8.1 x86

",andersl
14042,VBoxNetFlt crashing windows 7 on resume,Linux,VirtualBox 4.3.26,2015-04-10T14:58:45Z,2015-04-13T09:36:10Z,2015-04-13T09:36:10Z,"My system started bugchecking after I installed virtualbox 4.3.26 r98988 on my Windows 7 SP1 Enterprise system (64 bit).  The first one happened when I awoke the machine after putting it into sleep mode with my vm running.  After that, I made sure to shut down the vm before going into sleep mode but that doesn't prevent the crash.

Please find the crash dump analysis below.  Note that while the analyzer is blaming the multi-process NT kernel, the faulting module is VBoxNetFlt.  That indicates the filter driver is not handling the power state change correctly.
{{{
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\Debug\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.22948.amd64fre.win7sp1_ldr.150202-1521
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a3890
Debug session time: Thu Apr  9 16:19:23.133 2015 (UTC - 6:00)
System Uptime: 2 days 7:16:36.599
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800d99d980, fffff800047063d8, fffffa80134bee10}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxNetFlt.sys - 
Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800d99d980, Physical Device Object of the stack
Arg3: fffff800047063d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa80134bee10, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88000dc6000 VBoxNetFlt

IRP_ADDRESS: fffffa80134bee10

DEVICE_OBJECT: fffffa8011208050

DRIVER_OBJECT: fffffa8013c3c5d0

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF8000470CFB0

STACK_TEXT:  
fffff800`04706388 fffff800`02f448e2 : 00000000`0000009f 00000000`00000003 fffffa80`0d99d980 fffff800`047063d8 : nt!KeBugCheckEx
fffff800`04706390 fffff800`02edeb3c : fffff800`047064c0 fffff800`047064c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x336b0
fffff800`04706430 fffff800`02ede9d6 : fffff800`03086140 00000000`00c2a48e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`047064a0 fffff800`02ede8be : 000001cf`53374f3b fffff800`04706b18 00000000`00c2a48e fffff800`03054448 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04706af0 fffff800`02ede6a7 : 00000079`dd9484c1 00000079`00c2a48e 00000079`dd9484d7 00000000`0000008e : nt!KiTimerExpiration+0x1be
fffff800`04706b90 fffff800`02ecbb8a : fffff800`03050e80 fffff800`0305ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04706c40 00000000`00000000 : fffff800`04707000 fffff800`04701000 fffff800`04706c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------
}}}",microwheels
14037,Error starting virtual machine after upgrading to 4.3.26 The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  E_FAIL (0x80004005),all,VirtualBox 4.3.26,2015-04-09T07:23:28Z,2015-04-09T07:23:28Z,2015-04-09T07:23:28Z,"Hello, since I upgraded to 4.3.26 (but I tried even using 4.3.27), when I start a VM I got the following error:

Apertura di una sessione per la Macchina Virtuale Vista non riuscita.

The virtual machine 'Vista' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Daniela\VirtualBox VMs\Vista\Logs\VBoxStartup.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: Machine
Interfaccia: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

This is the host machine:
Microsoft Windows 7 Professional 
6.1.7601 Service Pack 1 build 7601
SAMSUNG ELECTRONICS CO., LTD.
X86-based PC
x64 Family 6 Model 58 Stepping 9 GenuineIntel ~2400 Mhz

Please, see the attached file for startup log

Best regards",shinnai
13968,Can't drag to select text in Google Chrome on Linux Guest,Linux,VirtualBox 4.3.26,2015-03-18T15:57:25Z,2015-03-30T23:33:32Z,2015-03-30T23:33:32Z,"I am unable to drag to select text in Google Chrome on a Linux Guest.

There is currently a thread on chromium at code.google.com for this.  A common factor is when running in VirtualBox - https://code.google.com/p/chromium/issues/detail?id=456222 .  Note: Their title for the bug is missleading and they are lumping the above description into that same bug report.

By drag to select text I mean: mouse down on some text, drag mouse to highlight some text, then mouse up.

I can drag to select text in Firefox with no problems.

My setup:
Host OS: Windows 8.1 Pro,
VirtualBox:  4.3.26 r98988 with Guest additions installed,
Virtual Machine OS: XUbuntu 14.04 last updated 3/17/2015,
Chrome: 41.0.2272.89 (64-bit)

On the code.google.com report, people have seen the issue with host OS of Mac OS X.  One report mentioned downgrading chrome fixed it.  Another mentioned uninstalling Guest Additions fixed it.",Scott H
14145,Virtualbox installer does not ask for admin rights (UAC) automatically,other,VirtualBox 4.3.28,2015-05-22T19:35:36Z,2016-11-22T23:16:27Z,2016-11-22T23:16:27Z,"Summary:

Since Virtualbox needs to install drivers, it always needs admin privileges. An installer can be compiled to require this, and many programs that need such privileges are (e.g. Networx, made by SoftPerfect).

Virtualbox is not. If a user has UAC at its default setting (enabled, one notch down from the top), as most people do, then at least in a Vbox upgrade scenario one must remember to run the installer ""as admin.""  If this isn't done, then the installation will still look like it worked, but Virtualbox's system drivers will likely not be installed (if you look at the drivers after the reboot -- e.g. vboxdrv.sys, vboxusb.sys, vboxusbmon.sys, etc -- they will not have been updated).

Proposal:

Virtualbox be made to force elevation upon a normal double click, thereby guaranteeing that this will not be a problem for the forgetful.

Note: I have not provided a log since this problem is one that's visible before setup begins to do anything more than show its initial screen. Also, this isn't specific to any particular version. It's been like this for any version for Windows that I can remember up through the current version.",rseiler
14208,Virtualbox crashes when undocking,Windows,VirtualBox 4.3.28,2015-06-17T10:00:07Z,2016-11-11T10:23:05Z,2016-11-11T10:23:05Z,"Hi,

I am using a docking station and most of the time (I would say 80%) virtual box crashes when I undock.

I am using VB version 4.3.28 r100309 under windows 7 enterprise SP1.

After having investigated a little bit this seems to happen when 2D acceleration is enabled (never tried with 3D) 

I attached the logs in case it can help to investigate.",thedavix
14236,Qt5 developed app not displaying correctly in Linux Cinnamon desktop guest,Linux,VirtualBox 4.3.28,2015-07-03T15:53:00Z,2016-06-22T10:27:20Z,2016-06-22T10:27:20Z,"Qt5 developed app doesn't display correctly using Cinnamon desktop in VirtualBox

I have an app I've developed in Qt 5.3.1 that doesn't display data in output text boxes when using the Linux Cinnamon desktop in VirtualBox with 3D acceleration enabled in the display settings for the virtual machine. 

It does this when using the Cinnamon desktop in any Linux Distro (I've tried Cinnamon with Linux Mint, Ubuntu and Debian). The regular Unity desktop in Ubuntu and the Xfce desktops in both Linux Mint and Debian have no problem. Just Cinnamon. 

I don't know if this is a Cinnamon, VirtualBox or Qt problem. Months ago I registered a bug with the Cinnamon folks but I never saw a fix, or that the problem was replicated anywhere. If I disable 3D acceleration for any of the Cinnamon virtual machines in VirtualBox the problem doesn't happen.

I'm posting here because maybe some Qt developers have seen similar problems with Cinnamon in either VirtualBox, or a native Linux machine.

The app is called Lottery Analyzer Expert QL: it can be downloaded at http://tcesoftware.webs.com, follow the link to Linux Downloads. 

It's free. My main versions are Windows, but I have both a 32 bit and 64 bit version for Linux developed in Qt 5.3.1. I hope the link I posted is OK. It's a free application, though not open source (because of the nature of the subject). 

It does various analyses on the Powerball and Mega Millions lottery games. I developed the programs out of curiosity of how to do it, and offering them for free for all the very useful free software I've used over the years. 

Again, I hope posting the link is OK. I just want someone to try my program and see if they can replicate the problem in any environment. 

Just double click on either Lottery_32 (32 bit) or Lottery_64 (64 bit) in the folder created by downloading and unzipping the tar.gz. Then choose one of the analyze buttons or ""drawn"" buttons after entering the number of draws to sort. If it runs correctly data will fill the text boxes for the game chosen to sort the totals of. The problem will show if the text boxes are empty except for the last row.

Any comments or replies would be welcome. Thanks in advance for any.",te7
14155,Double-click-hold doesn't work,Windows,VirtualBox 4.3.28,2015-05-27T09:23:52Z,2016-05-06T18:33:33Z,2016-05-06T18:33:33Z,"I had VBox 4.3.24 and updated to 4.3.28. Since then, holding the mouse button on a double-click doesn't work on my Windows guests. This method of text selection is available on several applications (like Notepad++ and most IDEs) to extend the selection on a word-by-word basis.

This doesn't seem to be a Guest Additions problem since I tried another VM with an older version of Guest Additions and I had the same problem.
",Constantine Dokolas
15089,Unable to setup base OS using virtual box,Linux,VirtualBox 4.3.28,2016-01-28T23:40:50Z,2016-02-10T08:50:11Z,2016-02-10T08:50:11Z,"Hi Team,

I tried Oracle Virtual Box 5.12 and 4.2.28 but unable to start the ubuntu VM.
Seeing below error every time. I got my system reimaged with client Windows 7
{{{
00:00:01.107602          VDInit finished
00:00:01.107602          Loading settings file ""C:\Users\a371216\.docker\machine\machines\default\default\default.vbox"" with version ""1.14-windows""
00:00:01.107602          Loading settings file ""C:\Users\a371216\VirtualBox VMs\manualUbuntu64\manualUbuntu64.vbox"" with version ""1.14-windows""
00:01:42.302389          ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={3295e6ce-b051-47b2-9514-2c588bfe7554} aComponent={ExtPackManager} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false
00:01:42.349395          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480cf695-2d8d-4256-9c7c-cce4184fa048} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
}}}",naveenlekhwar
14185,ICH AC97 Guest cannot record its own audio,Windows,VirtualBox 4.3.28,2015-06-09T03:00:21Z,2015-11-19T01:29:53Z,2015-11-19T01:29:53Z,"ICH AC97, select stereo mix and the guest never receives it's own audio for recording.

Windows 2000 pro guest, Windows 8.1 pro x64 host.",Paul17041993
14240,Oracle Linux 6.6 wont start on init 5 after install guest additions,Linux,VirtualBox 4.3.28,2015-07-04T14:12:51Z,2015-07-20T18:41:04Z,2015-07-20T18:41:04Z,"Recently we upgrade our Oracle Linux 6.4 to Oracle Linux 6.6. Upgrade was fine. We were able to connect with no issues on Linux guest.

Then we try to upgrade the guest additions, in order to use mouse integration. Guest additions was installed successfully. Then we reboot the Linux guest. After this, we are not able anymore to use GUI to start the Linux. We are able to change the init to 3 and start the Linux, but when we use init 5, the Linux just hangs. If we deinstall the guest addition, then we can install Linux in GUI mode.

We are using Windows7 as host, and Oracle Linux 6.6 as guest. Running latest Virtual Box version, 4.3.28 r 100389. We did not find nothing in messages and dmesg output.",Antonio Cesar Rosa
14212,(ipv6) multicast NS are not delivered to the guest,Linux,VirtualBox 4.3.28,2015-06-19T11:56:51Z,2015-07-16T13:48:05Z,2015-07-16T13:48:05Z,"It seems that the guest doesn't receive (ipv6) multicast neighbor
solicitations from the router.",Maarten Hoes
14210,VERR_INTERNAL_ERROR_3 when loading custom device plugin,Windows,VirtualBox 4.3.28,2015-06-18T14:32:22Z,2015-07-13T11:15:57Z,2015-07-13T11:15:57Z,"Hi folks, I use a custom virtual PCI device plugin. Unfortunately, even though I've signed it with a code-signing key from GoDaddy, VirtualBox 4.3.28 refuses to load my DLL. It gives the following error..

{{{
00:00:03.302562 VMSetError: F:\tinderbox\win-4.3\src\VBox\VMM\VMMR3\PDMLdr.cpp(307) int __cdecl pdmR3LoadR3U(struct UVM *,const char *,const char *); rc=VERR_INTERNAL_ERROR_3
00:00:03.302569 VMSetError: Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll
00:00:03.429194 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Unable to load R3 module C:\VMs\custom_device.dll (custom_device): : \Device\HarddiskVolume2\VMs\custom_device.dll (VERR_INTERNAL_ERROR_3)}, preserve=false
00:00:03.475155 Power up failed (vrc=VERR_INTERNAL_ERROR_3, rc=E_FAIL (0X80004005))
}}}

I've had a look at the source code for VBox and unfortunately this error is returned in many different situations. To make matters worse the pdmR3LoadR3U function obliterates the original error string which makes it impossible to discover the root cause. All you get is ""Unable to load R3 module"", which is about as useful as a chocolate teapot.

Given that the same DLL works with older versions of VBox (prior to the hardening update) and that the DllMain is never called, I have to assume that this error is related to signature verification issues. However, every tool I've tried tells me that my DLL is signed correctly and that the certificate chain is OK.",Kaloth
14215,(Windows 7) Guru Meditation -226 (VERR_INTERNAL_ERROR_2),Windows,VirtualBox 4.3.28,2015-06-21T10:01:44Z,2015-07-06T00:56:59Z,2015-07-06T00:56:59Z,I was trying to install Visual Studio Community 2015 RC on Win7 x64 guest and during component selection got Guru Meditation. No Guru Meditation on the second try.,tico-tico
14230,VirtualBox ISession get_Console returns S_OK but IConsole ptr is NULL,Linux,VirtualBox 4.3.28,2015-06-29T15:52:54Z,2015-06-29T15:52:54Z,2015-06-29T15:52:54Z,"Hi,

I am running into a strange thing here. My (pseudo) code (see below) works fine on Windows 7 SP1 / 64bit with 64bit VirtualBox and 64bit app binary.
But when I compile the stuff not as x64 but Win32 (32bit binary on SysWOW64), the app crashes because get_Session returns S_OK but the delivered pointer IConsole * is NULL !!!
Is this a bug or is it not possible to run a Win32 binary on Win7/64 with VirtualBox/64? I thought that it should be completely transparent using Microsoft COM?
Here is the pseudo code:

{{{
BSTR machineName = SysAllocString(L""VMName"");
IMachine *pMachine = NULL;
if (FAILED(pVBOX->FindMachine(machineName,&pMachine)))
{//do error stuff}
if (FAILED(pMachine->LockMachine(pVBOXSession,LockType_Write)))
{//do error stuff}
pMachine->Release, pMachine = NULL;
if (FAILED(pVBOXSession->get_Machine(&pMachine))) // get mutable one
{// do error stuff}
IConsole *pConsole = NULL;
if (FAILED(pVBOXSession->get_Console(&pConsole)))
{// do error stuff }
}}}

[...]
At this position, pConsole is NULL on Win32 (SysWOW64) and not NULL on Win64 (x64).
Any ideas?

Thank you.




",vboxcomapijunkie
14197,can not install bridged interfaces on W7-64 Pro,other,VirtualBox 4.3.28,2015-06-16T00:53:20Z,2015-06-28T00:38:11Z,2015-06-28T00:38:11Z,"Documented in this thread:

https://forums.virtualbox.org/viewtopic.php?f=6&t=68293&sid=bf442681877c87e603508a1aa2a0fb11

Hi there....readers digest. Dell replaced my M4800 laptop due to many different issues. The original is dual quad core intel core i7-4800MQ @ 2.7 Ghz, 8gb ram, 512mb hybrid drive, dual video processors Intel HD4600 and nVidia. Intel is default. Intel I217-LM ethernet adapter. Virtualbox installed normally but never got to run anything yet. 

new laptop is still a M4800 dual quad core I7-4810MQ @ 2.8 Ghz, 32gb ram, 512MB SSD + 512MB SATA drive. NVidia Quadro  K1100M is the other graphics processor. Same ethernet adapter.

I've attached a log from a failed attempt to install full product.

I need the bridged adapter.

Please help. If you need anything else, please let me know.

Thanks leon

",Leon Zetekoff
14200,USB not detected when VBox running,all,VirtualBox 4.3.28,2015-06-16T11:11:42Z,2015-06-22T18:49:08Z,2015-06-22T18:49:08Z,I have a Canon IX8000 series USB printer connected directly to my PC. If I run VBox the printer is reported offline and cannot be accessed. As soon as I close VB the printer starts working again,MarkT
14213,NAT networking stops responding blocks all I/O on that interface for Ubuntu/Debian x64 guests,Linux,VirtualBox 4.3.28,2015-06-19T18:21:50Z,2015-06-19T23:06:42Z,2015-06-19T23:06:42Z,"= Summary =
I can reproduce almost 100% this fault, which seems to affect Virtualbox versions 4.3.x in both Windows 8.1 and Windows 10 using ubuntu 14.04.2 or debian Jessie guests.

I attached a script, which pings a well known site once a second that you can run to show the precise moment at which networking stops responding. You may use this script or any tool you like for this. For the purposes of the bug description I will assume you are using the embedded script.

= Repro steps to detect fault =

1. Make sure you have a standard NAT based single interface ubuntu guest running.
2. Log-in to guest.
3. Install either google chrome (triggers fault immediately) or chromium-browser (ubuntu) or chromium (debian jessie) which trigger very often but not 100% of the time. Install google-chrome using the following snippet:

{{{
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - 
echo ""deb http://dl.google.com/linux/chrome/deb/ stable main"" | sudo tee /etc/apt/sources.list.d/google-chrome.list
sudo apt-get -yqq update
sudo apt-get install -yqq google-chrome-stable
}}}


4. Start embedded script to monitor network, access.
{{{
Expected result: It should be possible to ping well known address, the
 result should be something along these lines:
...
1 packets transmitted, 1 received, 0% packet loss, time 0ms
...
}}}

5. Start chromium browser from UI and try to access google.com or any address.

{{{
Result: Scripts start showing that network access is broken. Lines like
the following one show in script after a small delay where everything is
frozen:
...
1 packets transmitted, 0 received, 100% packet loss, time 0ms
...

Result 2: Virtualbox process in Windows becomes unresponsive and unstable,
cannot be easily stopped, may turn windows blank as hung processes show.

}}}
 
{{{
Expected result: Network access should work normally, no disruptions.
}}}

= Script to trigger fault =

For repro steps I used:
{{{
./net_tester.sh -x
}}}

{{{
$ cat net_tester.sh 
#!/bin/bash

function usage()
{

  cat <<eof

Usage: $(basename $0) [-x] [-h] [output log file]

The purpose of this script is to check network reliability of Virtualbox

Options:

-x, --external  Uses the google DNS to ping instead of NAT gateway address.
-h, --help      This message.

eof
  exit 1
}

#
# Change the following line to the address of the NAT gateway.
#
ping_address=10.0.0.2
out_file=out.log

while [ ""$1"" != """" ]
do
  case ""$1"" in
  -h|--help) usage ;;
  -x|--external) ping_address=8.8.8.8 ;;
  *) out_file=$1 ;;
  esac
  shift
done

while :
do
  date
  ping -c 1 ${ping_address}
  sleep 1
done | tee ${out_file}

}}}

",Coffee_fan
14138,Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf',all,VirtualBox 4.3.28,2015-05-19T18:16:23Z,2015-06-18T18:24:59Z,2015-06-18T18:24:59Z,"I get this error installing on Windows 8.1:


{{{
DIFXAPP: INFO:   VBoxUSBMon.inf: checking signature with catalog 'C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.cat' ...
DIFXAPP: ERROR:  Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf' ('C:\Program Files\Oracle\VirtualBox\drivers\USB\filter\VBoxUSBMon.inf'). (Error code 0x800B0003: The form specified for the subject is not one supported or known by the specified trust provider.)

}}}

",Mark Richman
14207,VBoxManage unregistervm --delete performs only a partial deletion if media file is locked by other process,Linux,VirtualBox 4.3.28,2015-06-17T09:12:07Z,2015-06-17T09:12:07Z,2015-06-17T09:12:07Z,"Trying to produce an automatic provisioning script to build VM's on demand and encountering this issue when the machine get above a few GB in size.

Process calls the vboxmanage export command and then immediately calls the unregistervm --delete command to remove the VM leaving just the export file.

However if the VM is above a few GB in size the lock is not released on the media in time resulting in:

{{{
BoxManage.exe: error: Medium 'C:\Users\scobarn\VirtualBox VMs\My_VM\My_VM.vdi' is locked for reading by another task
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium
VBoxManage.exe: error: Context: ""int __cdecl handleUnregisterVM(struct HandlerArg *)"" at line 166 of file VBoxManageMisc.cpp
}}}

Subsequent delete commands fail due to the vboxmanage unregister command executing just the unregistration part but leaves all files and directories behind requiring manual cleanup.

{{{
VBoxManage.exe: error: Could not find a registered machine named 'My_VM'
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: ""FindMachine(Bstr(VMName).raw(), machine.asOutParam())"" at line 154 of file VBoxManageMisc.cpp
}}}

Shouldn't vboxmanage unregister --delete be an all or nothing command and if an error occurs perform none of the steps instead of just removing the registration and leaving all files behind to cause issues without manual cleanup?",sbarnden
14206,"glPixelStorei(GL_UNPACK_ALIGNMENT,1) does not work",Windows,VirtualBox 4.3.28,2015-06-17T03:07:02Z,2015-06-17T03:07:02Z,2015-06-17T03:07:02Z,"This following code:

glPixelStorei(GL_UNPACK_ALIGNMENT,1);
glTexImage2D(GL_TEXTURE_2D,0,GL_ALPHA8,width,height,0,GL_ALPHA,GL_UNSIGNED_BYTE,pixels);

Will work properly with a packed texture only if width is a multiple of 4. If for example width is 41 and the texture is packed (so each row is 41 bytes wide with 0 empty bytes between rows) then diagonal lines will appear in the texture. However the same code works properly outside of virtualbox on every machine/driver combination tested.",sarladudu
14196,Install fails with fatal error but no other message,all,VirtualBox 4.3.28,2015-06-15T21:30:47Z,2015-06-16T17:31:04Z,2015-06-16T17:31:04Z,"It gets most of the way through the install then it rolls back and says there was a fatal error. But, it never says what the error was. I've collected an msiexe /lx install log that I'm attaching. It's the only info I have right now. I'm running Windows 7 as the host.",Gungwald
14180,when trying to open sagemath in oracle vm virtual box in windows 8.1 64 bit Blue screen of death happening,Linux,VirtualBox 4.3.28,2015-06-07T17:57:00Z,2015-06-08T14:12:35Z,2015-06-08T14:12:35Z,"Installation of Oracle VM Virtual Box and importing the sage ova file in it was not a problem. But when I started the sage machine Blue Screen of Death (DRIVER_VERIFIER_DETECTED_VIOLATION) happened. Otherwise my machine works fine. I was using Sage-6.7 ova file and Virtual Box 4.3.28.100309-win in a windows 8.1 64 bit machine. The problem persists for 4.3.12.93733-Win version also. For my machine OS, drivers BIOS everything is up to date. Hard disk health is good. No issue of Virus or malware. I have not installed the guest additions.More than 100 GB space is available in machine. Any help will be appreciated.",amritendu
14178,Host Crash reproducible,all,VirtualBox 4.3.28,2015-06-05T15:33:32Z,2015-06-08T12:40:51Z,2015-06-08T12:40:51Z,"Hi, i finally add it as a BUG here AFTER following all advices ( IRC, testing, reproducing failure, compaing results, check forums, etc. );

[ Sorry for sounding washy, im a bit tired now of all that crap, hopefully you are not and can take a deep look in it ]

Definition of the Bug as far as i can describe:

[HOST-SYSTEM]

[Soft-Ware:OS]

The Host Operating Systems i can reproduce these bugs on ( so far )are:

a) Windows NT 6.3.1 x86 U1 [ Windows 8.1 ( Embedded / Enterprise )Update 1 32-Bit ] NVHD

b) Windows NT 6.1.2 x86 [ Windows 7 ( Embedded Standard / Enterprise ) ] Service Pack 2 32-Bit ] NVHD

[Soft-Ware:VBOX]

VirtualBox 4.3.28 r100309 with ext-pack same version

[same effect/other symptoms in]

VirtualBox 4.3.29 r100811 with ext-pack from released version r100309 AND extpack for testing version [r100811]

HINT: Any version before is running ( not fine, but running )!


[Hard-Ware]

[A:AMD]
- Dell Optiplex 740
- CPU: AMD-Athlon X2 2.7GHz ( AMD-VX )
- NIC:
- onboard lan Marvell yukon GBit
- Wifi 54g D-link (PCI) originally; was exchanged with a firewire-pci
- 100mbit lan(pci with pxe-bios)

SND:
- onboard realtek ac 97

VGA:
- onboard nvidia ? ( unused)
- Ati v5700 Fire-GL (pci-express 16x)

HDD:
- 4x Seagate Barracuda ES 750GB 15k (non-raid use on onboard SATA AHCI )

ODD:
- external LG DVD+-RW whatever USB2
USB:
- 4 RootHubs ( 3 in use ) USB 2

[B:Intel]
- FS Esprimo

CPU:
- Pentium D 945 Presler ( VT-X)

HDD:
- 1x Samsung 160GB ( internal SATA AHCI )
- 1x IDE changeable rack
- 1x ide smart card/Compactflash-boot/SDHC/MS

VGA:
- Intel 945G (EE)

SND:
- onboard intel HD

ODD:
- none

HINT: These machines are in amounts up to 50 available, were in seldom use and bought from local energy provider as sorted-out and should be used in future for kindergarten-network as experimental stations; they are already checked and stress-tested and i interchanged systems with the given setup just to ensure it is not a single-machine that is faulty. Btw.: all these machines ran in energy efficient lowest modes all their lifetime just used for some bureaucracy, so even if cpu-ram-gpu-stresstest weren't reliable, they function normally in any other case ( before and after reproducing the given failure of vbox )


What is the problem ?


In my webchat IRC with MichalN in the #vbox channel i had kind brainstorm of possibilities, because i wouldn't report a bug without further investigations. Whatever, the problem to report a bug is, i can get NO MINIDUMP at all, independent of settings, because due to bugs in the given version, from a given OS in native VHD-Boot there are issues which in most cases, do not lead to a dump. believe me i tried all options. That is why i asked at vbox-channel for possible workarounds, like special logging-modes for vbox or possibilities to sandbox vbox, so the host-system can't crush and can be investigated. Nonen option so far given.

The problem in its symptomatic:

When running 64-Bit guests the host system crushes almost immediately!
Linux live systems run. ( at least in the release version ) in the testing-version they crush also immediately and with a bsod clock_watchdog_timeout for some millisecs of the host - followed by immediate restart and no dump at all ); at least in testing version vbox comes so far to log the usual vm-init inside. in the release version it never got so far.

Tested systems:
- 64-bit guest on 32-bit host is the problem;
- i counterchecked 32-bit ones also

- Fedora
- 17
- 19
- 21
( Workstation, Server, Live, DVD , CD, Netinstall )

- Ubuntu
- all LTS versions plus vivid (15.04) and winy (15.10)

- Windows
- any you can think of

- Debian
- Jessie ( 8 )
- Wheezy ( 7.1 and 7.6 )
- did i forget some, maybe ...

okay to get some more specific things:


side-problem NIC

as MichalN mentioned, due to change from wifi to onboard lan i checked that ones too, it makes a difference in time it takes until crash, but nevertheless changes nothing at all; so forget about it; right now in this moment i am running the stable-version 4.2.30 r100415 with winy werewolf (15.10) besides this ticket-creation without a problem with full install and stress-test inside 64 bit vm on the A-Host, the AMD-one, with all options given and any hardware acceleration and all hardware on the host enabled, soi can say -- It is NOT a HW-problem and not even a host-problem i would say.

I know it is problematic without a dump at all; however let me go on with that:

i tested any old version i could find in my libraries and which i regularly used on all my machines, especially on the given ones.
Btw. i just checked if it is dependent of the generation/featuresets by checking on m HP Elitebooks, too and on a panasonic toughbook; It is not; That ones were Core-duo Core2-Duo Turion X2 i5; Where was I, ah yes: Old versions

Old versions of VBOX tested so far:

- 3.2.8
- 4.0.8-71778
- 4.1.12
- 4.1.14-77440
- 4.1.22-80657
- 4.2.0-80737
- 4.2 ( 4.2.16 + 4.2.4[r81684] )
- 4.3 ( 4.3.6[r91406] + 4.3.8[92456] )
... these ones are counterchecked on linux hosts as well, which have not at all any problem with the 64guests on 32hosts (whereas the mentioned systems above that were used as guests i have also available as hosts )
plus the actual

release:

- 4.3.28-100309

testing:
- 4.3.29-100811

and the actual stable:

- 4.2.30-100415


Here is what i came to as a definitive reproducable point:

When using the actual release or testing:

-ONLY Linux-live systems based on debian run at all;
- UNTIL fully installed, the CRASH follows right after logging in the created user-account first-time.

- Windows-64-Guests ( Setup OR OVA OR prepared vhd's dism/firadisk/grub4dos) crash immediately.

- Linux-64-Guests crash right in the moment a user account is logged in in a graphical system

- Fedora-based linuxes are critically slow

- debian-based run acceptable up to perfect

- ovas with virtualization features in it are crushing in the same manner, comparable to Fedora 21 Workstation, which is the fastest crusher of all tested systems(IMMEDIATE-RIGHT-NOW-TOTAL-RESTART-OF-HOST)

Okay that was long enough - i am tired and have no concentration anymore, please see this as a possibility to make something of it; i am available for further test-scenarios, BUT DO NOT FORGET: the given HOST-OSs can not produce a dump.

I saved the chat-log of my chat with MichalN if it helps and am willed to help out. added also 2 screenshots just for a prove of stable is running ubuntu winy and a short device overview.

Give me reproducable test-case and i follow to my best; If necessary i can make a video of the crash and the none existance of the dump if you wish to. In case you do not believe.
I have visual studio available if it helps and am able to install a set of progs to help narrow the problem, because these ones are not really production systems at the moment. Only thing is you have to explain what it is for if i dont know and i might double check for resulting contents, because i run some more networks chained where these machines are appended to.

To be precise: i am willed to spend my time to check on the HOST-A ( the AMD ) as the Intel-Machines go out for setup and deliverance for a while for other projects.

The other systems are my personal ones and i am not willed to make crucial tests on them anymore as long as crazy shutdowns are not handled.

So whatever: I hope you have an idea of an idea of an idea of what might could eventually maybe happen here and feel able to give some straight questions.

Thanks for your interest.

PAETH CLAUDIUSRAPHAEL
S466531257BOSS

P.s.:

By the way, if you think that it is not necessary to give compatibility to these OLD machines then i need you to tell that clearly and unmisleading and ALSO clarify the tech-specs of your products for the given case. If instead you accept that these kind of machines are right now even in industry-leading nations like germany still in use by MANY private AND business users and organizations, especially those who teach and take care of our children then PLEASE do me and maybe others the chance to make it usable. Your decision. I just ask to be precise about this issue.",PAETH CLAUDIUSRAPHAEL
14169,vboxsf: files with illegal (:) characters truncated on host's NTFS shared folder / results in data loss,Linux,VirtualBox 4.3.28,2015-06-03T06:50:04Z,2015-06-03T06:50:04Z,2015-06-03T06:50:04Z,"Moving a file from a Linux guest filesystem that is tolerant of e.g. the colon character (:) in a filename, to a Windows-hosted NTFS filesystem using vboxsf results in truncation ('''DATA LOSS''') and odd naming behavior.

== Steps to reproduce: ==

1. Create a file on a Linux filesystem in a guest; e.g.
{{{
# dd if=/dev/random of='/tmp/1mega:byte' bs=1M count=1
}}}

2. Mount NTFS shared folder:
{{{
# mount -t vboxsf SHARE /mnt
}}}

3. Move file to vboxsf shared filesystem
{{{
# mv '/tmp/1mega:byte' /mnt
}}}

== RESULT: ==
a file in /mnt of zero size and truncated filename

{{{
# du /mnt/1mega
0       /mnt/1mega

# du '/tmp/1mega:byte'
du: cannot access '/tmp/1mega:byte': no such file or directory
}}}

== EXPECTED RESULT: ==
An error that does not result in the truncation of the /tmp/1mega:byte file in the above example OR a renaming of the file in /mnt, along with preservation of the contents of the file.",baitisj
14165,Virtual machine loses hard drive when settings are changed.,Windows,VirtualBox 4.3.28,2015-06-02T14:21:26Z,2015-06-02T15:35:30Z,2015-06-02T15:35:30Z,"This problem is described at length in the forum at this link:
http://forums.virtualbox.org/viewtopic.php?f=6&t=68147&p=323314&e=323314

After shutting down the guest OS and changing its settings using VirtualBox Manager the virtual machine loses its DVD and/or HDD configuration.
The message: FATAL: Could not read from the boot medium! System halted.

is displayed and it not possible to recover the disk. (Things tried restoring the original .vbox and .vbox-prev files, running VBoxManage internalcommands sethduuid etc. )

This problem is not present in VirtualBox 4.3.20.",eqh
14164,Problem with installing VirtualBox on Windows 7,other,VirtualBox 4.3.28,2015-06-02T08:04:01Z,2015-06-02T08:04:01Z,2015-06-02T08:04:01Z,"When I run the installer on my maschine (Windows 7 Enterprise), the installer seams to do what it is supposed to do. But when I afterwards try to start VirtualBox, the main windows of the programm is shown and almost immediately, it crushes down.
Please find the picture with the error screen and also the error text cutted out into a text file attached.
Solution for the problem is the following procedure:
The installer created a folder named "".VirtualBox"" under my user folder here on windows. As I compared some other installations from other maschines, in my new installation was one file missing named ""vbox-ssl-cacertificate.crt"". After adding this particular file to that folder, VirtualBox was able do run again.
Question: What is the problem for the installer that it fails to create this file during the installation routine?
I even ran the installation routine as admin and it didn't make any difference.
",Jonas Bassl
14158,Memory Leak on Windows 7 Host VBox  4.3.28 r100309. Host Mem 45%-90% in 3 Hrs.,Linux,VirtualBox 4.3.28,2015-05-29T17:47:50Z,2015-05-29T17:47:50Z,2015-05-29T17:47:50Z,"Vbox Details
 Version 4.3.28
 Guest Additions 4.3.28.iso
 Operating System: Ubuntu 14.04
 System:
  Base Memory: 3GB
  Processors: 4
  Execution Cap: 95%
  Acceleration: VT-x/AMD-V, Nested Paging, PAE/NX
 Display:
  Video Memory 64 MB
  Screens: 2
  Acceleration: 3D

Host Details:
 Operating System: Windows 7
 RAM: 8GB
 Processors: 8
 
After starting the Virtual Machine VirtualBox.exe Memory(Private Working Set) rises to about 416,416 K. Within 3 hours of working inside the VM It will rise to roughly 2,000,000 K at which point the host alerts me to low memory. If I don't restart the VM eventually it will completely freeze and crash.

Typical Programs running in VM
Firefox
Sublime-Text-2
Terminal
Libre Office Writer/Spreadsheet
File Manager

In the host VirtualBox is typically the only program I'm running. I was wondering if maybe not having Admin permissions on the account I'm using is causing a problem? Although I did give VirtualBox all the rights an admin account has. 
",dduke22
14157,Removing snapshot fails and leave VM in unbootable state,Linux,VirtualBox 4.3.28,2015-05-28T11:24:14Z,2015-05-28T11:24:14Z,2015-05-28T11:24:14Z,"The VM had 2 snapshots and was running. I started the removal of the
first snapshot from the GUI.  This removal aborted with an error, and the running VM was somehow stopped (or killed).
Unfortunately, I don't have the error message any longer.

The bigger problem is that the VM was not bootable any longer; I think this is the error message in VBox.log.2:
{{{
00:00:04.189066 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false
}}}

The next attempt to start the VM resulted in an error messag that a required snapshot file was missing (in VBox.1.log):
{{{
00:00:02.948345 AIOMgr: Endpoint for file 'C:\Users\voelkerb\VirtualBox VMs\opensuse13.2\os13.2.vdi' (flags 000c0781) created successfully
00:00:02.983231 VMSetError: F:\tinderbox\win-4.3\src\VBox\Storage\VD.cpp(6370) int __cdecl VDOpen(struct VBOXHDD *,const char *,const char *,unsigned int,struct VDINTERFACE *); rc=VERR_FILE_NOT_FOUND
}}}

Creating a new snapshot in order to preserve the current state failed
with the same message.

The only way out was to revert to the last snapshot - without taking
a snapshot of the current state and thus loosing the work until that
last snapshot. ;-(

After that, the machine was still not bootable, but the media manager
complained about 2 missing differencing images.
After removing that, the VM could be started again, yet some work was
lost.

I experienced the same already 2-3 times in the past.

Host: Windows 7, guest: openSUSE-13.2",berny
14152,restoring my snapshot made web pages cannot connect to mysql,Linux,VirtualBox 4.3.28,2015-05-25T20:24:18Z,2015-05-26T12:52:01Z,2015-05-26T12:52:01Z,"Restoring snapshot made my webpages connection to Ubuntu guest cannot connect to Ubuntu guest mysql anymore

",virtualguys
14141,vb guest additions corrupts win 10 guest,Windows,VirtualBox 4.3.28,2015-05-21T03:28:12Z,2015-05-22T10:06:54Z,2015-05-22T10:06:54Z,"when attempting to load vb guest additions on a windows 10 64 bit guest with a windows 8.1 64 bit host vitalization enabled guest initially loads fine insert guest additions CD within guest then attempt to run CD clicking through with default settings guest additions will start to load drivers until it gets to the WDDM video driver can take up to a minute to Begin to load this driver then the screen will began to pixalate and artifact and then the screen will go blank and show a black screen with a white or grey box in the middle then VM will freeze the only way to exit is by red X attempts to restart will show widows loading screen then show blank screen again you are forced to force close only fix is to restore to previous snap shot a use VM without guest additions installed
this problem has existed in all versions of virtual box since window 10 tech preview was initially released",bugger
14115,4.3.28 installation failed,other,VirtualBox 4.3.28,2015-05-14T19:55:06Z,2015-05-21T09:05:49Z,2015-05-21T09:05:49Z,"Hi,
I tried to install 4.3.28 but I had a bluescreen during installation saying DPC_WATCHDOG_VIOLATION.
I tried after to install the 4.3.26 again and it failed.
I tried to do all sorts of fix found on your forums but nothing worked.
I link to this bug report a log of the last installation I tried",Josk
14123,X11 additions: no EDID detection any more,X11,VirtualBox 4.3.28,2015-05-16T14:25:16Z,2015-05-18T12:54:34Z,2015-05-18T12:54:34Z,"With release 4.3.28 the X11 additions have rendered EDID detection dysfunctional. As a result, Xorg comes up with the default resolution of 1024x768 instead of sizing according to the (virtual) screen size.

Attached is a unified diff of Xorg.0.log, comparing 4.3.26 and 4.3.28 guest additions. xorg.conf is identical.",hmo
14130,Creating a VB on Windows 7-32bit for Windows 8-32bit,Windows,VirtualBox 4.3.28,2015-05-17T18:39:55Z,2015-05-18T06:33:45Z,2015-05-18T06:33:45Z,"Tried to run a VB Windows 8.1 (32 bit) on my Windows 7.  

Encountered the following errors:

1.  Failed to create the VirtualBox COM object.
    The application will now terminate.
    Callee RC: E_INVALIDARG (0x80070057)

2.  Failed to open a session for the virtual machine Windows 8.
    The virtual machine 'Windows 8' has terminated unexpectedly during 
    startup with exit code 1 (0x1).  More details may be available in   
    'C:\Users\c3p0i\VirtualBox VMs\Windows 8\Logs\VBoxStartup.log'.

    Result Code: E_FAIL (0x80004005)
    Component: Machine
    Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I have attached the *.log with this ticket.

Thanks and Regards.",c3p0i
14121,VirtualBox 4.3.28 auf Windows Server 2012 Datacenter - kein VM-Start mehr nach Windows-Updates,Windows,VirtualBox 4.3.28,2015-05-15T14:53:50Z,2015-05-15T15:27:10Z,2015-05-15T15:27:10Z,"I have updated VirtualBox from 4.3.20 to 4.3.26 and later to 4.3.28.
The operating system is Windows Server 2012 Datacenter (German).
When I install all current Windows updates, my
VM (Windows Server 2008 R2 German with all Windows updates) does
not start.

The error after installing VirtualBox 4.3.28 is:
Die Anweisung in 0xe3ff0ab1 verweist auf Speicher 0x041af0bd. Der
Vorgang read konnte nicht im Speicher durchgeführt werden.
Klicken Sie auf ""OK"", um das Programm zu beenden.

",clearth
14322,BSOD on Windows 7 upon hibernating while VirtualBox is open,Linux,VirtualBox 4.3.30,2015-07-24T14:06:23Z,2015-09-02T21:52:59Z,2015-09-02T21:52:59Z,"I have a recurring problem where I get a blue screen of death when I hibernate my computer while I have VirtualBox open. I'm running Windows 7 64-bit with a xubuntu on Ubuntu 14.04 (trusty) guest. I'm also using version 4.3.30 of virtualbox and version 4.3.24 of the guest additions. My BSOD provided the following information: the error was a DRIVER_IRQL_NOT_LESS_OR_EQUAL, and was attributed to VBoxNetFlt.sys. I ran WinDbg on the MEMORY.DMP (full dump, not minidump) and got the following info:

{{{
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
    Machine Name:
    Kernel base = 0xfffff800`0300f000 PsLoadedModuleList = 0xfffff800`03253890
    Debug session time: Fri Apr 10 15:50:18.376 2015 (UTC - 4:00)
    System Uptime: 3 days 14:35:58.020
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    
    Loading unloaded module list
    ................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {112337, 2, 0, fffff80003076615}
    
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
    Probably caused by : avgidsdrivera.sys ( avgidsdrivera+10634 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000112337, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80003076615, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  0000000000112337 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KiInsertQueueApc+69
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800bffb710 -- (.trap 0xfffff8800bffb710)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff80003341a58 rbx=0000000000000000 rcx=000000000011232f
    rdx=fffffa800a6373e0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003076615 rsp=fffff8800bffb8a0 rbp=fffff880009e8180
     r8=0000000000000001  r9=000000000011231f r10=fffff880009e8c01
    r11=fffffa800fd26b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!KiInsertQueueApc+0x69:
    fffff800`03076615 488b4108        mov     rax,qword ptr [rcx+8] ds:00000000`00112337=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003083469 to fffff80003083ec0
    
    STACK_TEXT:  
    fffff880`0bffb5c8 fffff800`03083469 : 00000000`0000000a 00000000`00112337 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0bffb5d0 fffff800`030820e0 : fffff880`0bffb738 fffff800`03083153 ffffffff`8000297c fffffa80`105c1060 : nt!KiBugCheckDispatch+0x69
    fffff880`0bffb710 fffff800`03076615 : fffff880`00000001 fffffa80`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`0bffb8a0 fffff800`030656b0 : fffffa80`105c1060 00000000`00000000 00000000`00000078 fffffa80`0a6373d0 : nt!KiInsertQueueApc+0x69
    fffff880`0bffb8d0 fffff880`04c10634 : 00000000`00000000 00000000`778e7ac0 00000000`00000078 00000000`000007ff : nt!KeInsertQueueApc+0x80
    fffff880`0bffb930 fffff880`04c107b4 : 00000000`0000ed04 fffff880`04c3cf50 ffffffff`8000397c fffffa80`1769b6c0 : avgidsdrivera+0x10634
    fffff880`0bffba10 fffff880`04c10866 : ffffffff`8000397c fffffa80`1769b6c0 fffffa80`168f6520 00000000`000007ff : avgidsdrivera+0x107b4
    fffff880`0bffbac0 fffff880`04c2925c : 00000000`00000001 fffff880`0bffbba8 fffffa80`0fd26b50 fffff880`0bffbba8 : avgidsdrivera+0x10866
    fffff880`0bffbb10 fffff800`0337cb43 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`0fd26b50 : avgidsdrivera+0x2925c
    fffff880`0bffbb40 fffff800`0308da95 : fffff800`03338b00 fffff800`0322b201 fffffa80`0fd26b00 fffffa80`00000000 : nt!IopProcessWorkItem+0x23
    fffff880`0bffbb70 fffff800`03322b8a : fffffa80`105029d0 fffffa80`0fd26b50 00000000`00000080 fffffa80`0698eb30 : nt!ExpWorkerThread+0x111
    fffff880`0bffbc00 fffff800`030758e6 : fffff880`03365180 fffffa80`0fd26b50 fffffa80`06d40290 00000000`07fa1011 : nt!PspSystemThreadStartup+0x5a
    fffff880`0bffbc40 00000000`00000000 : fffff880`0bffc000 fffff880`0bff6000 fffff880`0bffb8a0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    avgidsdrivera+10634
    fffff880`04c10634 84c0            test    al,al
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  avgidsdrivera+10634
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: avgidsdrivera
    
    IMAGE_NAME:  avgidsdrivera.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55128c2a
    
    FAILURE_BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    BUCKET_ID:  X64_0xA_avgidsdrivera+10634
    
    Followup: MachineOwner
    ---------
}}}

Please provide any assistance you can on determining the cause of and solution to this problem.",Anomaly13
14513,OpenGL error with 3D acceleration enable with black screen,Linux,VirtualBox 4.3.30,2015-08-27T20:58:30Z,2015-08-27T20:58:30Z,2015-08-27T20:58:30Z,"Hi,

I'm running Ubuntu 14.04 lts trusty 64 bit on 4.3.30 r101610 on Win 7 host 64 bit.
I'm getting too many OpenGL warning and my rendering screen is going black. I'm
running gazebo robotic simulator. However if I do not use hardware acceleration then everything work fine and there are no warning. But then by simulation run very slow.
I've done almost everything regarding this issue as this is not new. I've installed the VBoxGuestAddition_4.3.30.iso. Before installing the guest addition the 3d hardware acceleration work fine and I do not get openGL warning. However I'm not able to go to fullscreen.
I've also installed latest virtual box extension pack.

Please share any suggestion.",AmitUbu
14352,Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057),Windows,VirtualBox 4.3.30,2015-07-30T21:43:49Z,2015-07-30T21:43:49Z,2015-07-30T21:43:49Z,"After an upgrde from 4.3.12 to 4.3.30, I get the 'Failed to create the VirtualBox COM object. The application will now terminate. Callee RC: E_INVALIDARG (0x80070057)' error. this error has prevented me from upgrading from 4.3.12 to any later version.",dinsdale
17288,Crash while installing DirectX 9.0c on Windows 98,Windows,VirtualBox 4.3.36,2017-11-18T06:06:38Z,2017-11-18T11:24:32Z,2017-11-18T11:24:32Z,"While following forum instructions https://forums.virtualbox.org/viewtopic.php?f=2&t=59559

The critical error guru box showed up and suggested I submit this ticket.

My virtualbox version is actual 4.3.40 r110317. On that note, this new ticket form has the version list all out of order, could that be sorted?

The host system is Windows 7 64-bit",Brrwrist
15076,Wifi connections goes off,Linux,VirtualBox 4.3.36,2016-01-25T18:15:47Z,2016-01-25T21:47:43Z,2016-01-25T21:47:43Z,"If I leave my virtual machine in saved state and turn off my pc and then turn it on after sometime my host os looses wifi connection  ,it shows limited .The only workaround is to switch on the vm ,turn it off and then restart the pc .

This doesn't happen if I turn off the vm instead of leaving it in the saved state
",rishabh
12646,XP Guest GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6 => Fixed in SVN,Windows,VirtualBox 4.3.4,2014-01-27T17:56:46Z,2020-07-11T19:27:22Z,2020-07-11T19:27:22Z,"When running 16 bit Apps in XP, there is an occasional GPF in WIN87EM.DLL at 0001:02C9 or 0001:02C6.  Same app sometimes works OK.
For me, this problem did not exist through many version of VB through 4.2.18 and started with 4.3.4.

The only web research I have was from a VMWare post that may or may not apply here (quoted from cwsault original post):

""There are a few applications which may fail with this error when executed in a VM. The problem is that the library tries to read the instruction bytes of the last FPU instruction executed based on the code segment and instruction pointer saved in the FPU environment. Unfortunately, the code segment saved in the FPU environment may be NULL.

When we switch between the virtual machine monitor and the host operating system, we use the primitive hardware instructions to save and restore the FPU state. These instructions were not really designed for an environment that mixes 32-bit and 64-bit execution. When the instructions are executed in 64-bit mode, they don't keep track of the code segment, since segments have little meaning in 64-bit mode. The virtual machine monitor, which saves and restores the FPU state for the guest VM, executes in 64-bit mode. Hence, the FPU code segment is lost.

Fortunately, there is a workaround for this issue. If you add the following option to your configuration file, we will make sure that the FPU code segment is properly saved and restored when switching between the virtual machine monitor and the host operating system (at some small performance penalty):
    
monitor_control.enable_rigorous_fpu_save_restore = TRUE""
",SteveDeveloper
12459,Host-only adapter interface resets IP address back to default.,Windows,VirtualBox 4.3.4,2013-12-09T15:16:51Z,2016-02-10T13:49:02Z,2016-02-10T13:49:02Z,"There is an old defect #8796 that describes this same problem for an older version of Virtual Box.  I don't want this issue to get lost under an old defect so I've created this new one since this was not an issue with the last 2 versions prior to 4.3.4.

Starting with my upgrade to v4.3.4, every couple of days I have to reset my host-only adapter's interface IP back to my user configured one of 192.168.56.1.  It keeps resetting to 169.254.x.x, but only after a few days and I have not been able to identify any trigger.

Windows 7-64-bit with a hosted Windows 2008 R2 server.  The previous version did not have this problem so hopefully this will help to identify the cause.

The reset of the DHCP settings for the host-only adapter remains intact, it's only the interface's IP address.
",GCPeters
12487,Disable ICH9 Chipset for NetWare Guests,other,VirtualBox 4.3.4,2013-12-15T07:20:21Z,2013-12-15T07:20:21Z,2013-12-15T07:20:21Z,"After a fair bit of experimentation, confusion, and trial/error, I have determined that using the ICH9 chipset on a variety of NetWare guests just leads to many issues, one of which is extremely subtle.

For example, if running a NetWare 4.2 SP9 guest (PIIX3 chipset), IPX-only, NDS 6.21, and you try to install an NW5.1SP8/NW6.0SP5 guest into the existing tree, also IPX-only, but using the ICH9 chipset, then the second guest cannot see the first over IPX.  I even ran a packet capture and the two were definitely talking to each other during the initial setup, but once you try to install the second guest into the first's tree, they stop and IPX just breaks down.  Setting the second guest back to PIIX3 chipset solves this problem.

So I think the best thing to do is to just disable the chipset field in the guest properties if the chosen guest type is ""Other/NetWare"" so people who try this in the future don't go through the same punishment.",kumba
12440,"Option to capture USB for whole VB run, or even globally",all,VirtualBox 4.3.4,2013-12-04T18:45:18Z,2013-12-04T18:45:18Z,2013-12-04T18:45:18Z,"Running on Windows, it seems USB capturing works on a per-VM invocation basis. You start the VM, insert the USB device, and it's captured until the VM exits. This means that multiple runs of the VM require removing and reinserting the USB device every time.

It would be useful to have an option to capture USB for the whole VirtualBox session, rather than a single VM run. 

Possibly, even a system-global capture would be useful, where the USB filter parameters would be stored by the host USB capture driver and acted upon even before VB runs. In such a case, the VB GUI (or maybe a property sheet for the USB capture driver) could have a ""release capture"" option. 

A system-global capture would prove useful in scenarios where a USB device is there exclusively for VM usage. A system-global capture would mean no removal/reinsertion at all.
",emu1
12570,VM window appears off screen; not accessible,Linux,VirtualBox 4.3.6,2014-01-03T15:11:01Z,2020-11-14T10:18:07Z,2020-11-14T10:18:07Z,"Virtual box remembers guest window location and uses it at next start-up for a VM.  This is a good thing.  However, what it doesn't do is confirm upon start-up that the remembered location is still valid and will display the window off screen and not viewable.  Worse, it does not respond to the typical Windows move commands in order to move the window back into viewable space.  This leads to not being able to correct the condition and the user is stuck with a window they cannot access.

Specifics:
At home, I have an additional monitor that is positioned vertically above my laptop screen and is oriented that way in Windows ""Screen Resolution"" where one identifies monitors and their relative locations.  At the office, I have three external monitors, all side-by-side, and do not use the laptop screen.

I had worked at home and placed the VM window in the ""top"" monitor in scaled mode.  I shut down the guest and then shut-down the host laptop in that condition and went to the office.  There, I started the host laptop, opened VirtualBox, and started the guest.  Initially, the guest window came up in my main monitor.  I then switched it to scaled mode and the window disappeared.  Attempts to move it via the Windows Move option from the System menu was not successful.

I ended up having to go into ""Screen Resolution"" and orienting my monitors to place one of them ""above"" my main monitor -- thus replicating the condition under which the scaled guest window last appeared.  Doing this, I was able to then access the guest window and drag it ""down"" to the main monitor.  I then reverted the monitor orientation to side-by-side and moved the guest window to the monitor on the side.

Certainly not an insurmountable issue but until I thought about trying the re-orienting of my monitors, I was really stuck.",RodBarnes
12680,Unable to restore saved state after sleeping host,Windows,VirtualBox 4.3.6,2014-02-08T19:31:03Z,2020-02-28T11:06:37Z,2020-02-28T11:06:37Z,"Windows 7 x64 host, Windows 7 x64 guest, VirtualBox 4.3.6 r91406

If I save the state of the guest, and then put the host PC to sleep, when I wake it back up and attempt to resume the guest, I get:

Failed to open a session for the virtual machine Win7.
Failed to load unit 'pgm'
(Verr_SSM_INTEGRITY_REC_TERM_CRC).

The details are:

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

If I shut down the host and reboot, I can then resume the guest from it's saved state.

This is repeatable every time.  I saw another ticket from months (years?) ago with the same issue; it's how I knew to reboot in order to be able to resume the saved state.",Kiran Otter
12708,USB-Dongle with Vendor-ID 0000 cannot be attached,Windows,VirtualBox 4.3.6,2014-02-16T22:59:27Z,2018-04-26T18:51:38Z,2018-04-26T18:51:38Z,"I have to connect a USB-Licence-Dongle with Vendor-ID 0000 and Product-ID 9999 to a virtual machine (Windows 7/64 Professional).

This fails with:

{{{
Assertion failed: [mData.vendorId] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-client\USBDeviceImpl.cpp' (62) in long __cdecl OUSBDevice::init(struct IUSBDevice *).

Please contact the product vendor!.

Fehlercode:E_FAIL (0x80004005)
Komponente:OUSBDevice
Interface:IUSBDevice {f8967b0b-4483-400f-92b5-8b675d98a85b}
}}}

Having a look at this Code-Line shows
{{{
ComAssertRet(mData.vendorId, E_INVALIDARG);
}}}

It seems there is no reason for failing here besides the fact, that 0000 is not an allowed vendor-id. At least VMware Workstation 10 can handle this. Don't tell me to contact the Vendor, I have to work with what I get, and what I get has Vendor-ID 0000.
",RainerHohn
12564,Unable to drag/drop ISO on cd icon on status bar,other,VirtualBox 4.3.6,2014-01-03T01:05:58Z,2017-06-16T07:18:32Z,2017-06-16T07:18:32Z,"I know I do this in virtual pc (drag/drop ISO on the CD icon) and thought I was doing it in VirtualBox as well, but the latest update doesn't allow me to do that (vmware doesn't allow it which is why I don't use it much).

Can you bring drag/drop of .ISO back (or add it if it wasn't there before).  It's really a very big time saver.

",dfatvb
12738,OpenGL windows are always on top of everything else in linux guest,Linux,VirtualBox 4.3.8,2014-02-26T15:32:52Z,2017-11-09T13:00:22Z,2017-11-09T13:00:22Z,"System:
Host = windows 7 home premium
Guest = ubuntu 12.04 LTS

Virtualbox versions 
4.3.6r91406
4.3.8r92456

Hardware: AMD, INTEL, 32 and 64 bit, nvidia ati amd chromium

OpenGL windows from any application are always topmost, that is they are always on top of everything else.
In applications such as Blender, FreeCad etc drop down menus disappear behind the opengl window which is the main frame of the application. This makes it very difficult to use the program.
All opengl features seem to work.
I have reproduced this on at least 3 completely different hardware systems. 32 bit and 64 bit
When you run glxgears and drag the application to another location on the screen the application window moves with the cursor but the opengl window doesn't move until the mouse button is released.
Also all screenshots come out black, probably due to reversed window layering.
This must be a virtualbox bug as none of this behaviour occurs in Ubuntu 12.04 LTS when run natively. 
There are no errors reported nothing noted in any logs.
I've been trying to find a solution to this for almost 2 years.
There are a lot of similar bug reports which all claim it is fixed. Yet all I need to do is install virtualbox on any windows machine then install Ubuntu 12.04 LTS, install guest additions and I have the same problem. All other 3d acceleration works fine it's just the opengl window layering. 
Compiz cube works.
I think I started using virtualbox at version 4.2 and have always had this problem.
Running identical Ubuntu 12.04 LTS installations, one natively the other in a virtualbox on a windows 7 host on the same hardware platform. The native installation has no issues. The virtualbox guest installation always has this issue with opengl windows.
Please help...",solaris235
12813,Mini toolbar activation area is too big,Windows,VirtualBox 4.3.8,2014-03-12T09:24:31Z,2017-05-09T14:32:48Z,2017-05-09T14:32:48Z,"In fullscreen mode mini toolbar gets activated too early. It hinders when operation with task bar in the bottom of screen.
Older versions of VirtualBox had activation area at the very bottom of screen so it did not interfere with task bar of guest OS.
Hosts: Windows 7, Windows 8.1
Guest: Windows XP",denZXabc
12860,"Linux guest aborts in VRDP, OpenGL mural warning",Linux,VirtualBox 4.3.8,2014-03-25T01:18:02Z,2015-02-26T11:51:28Z,2015-02-26T11:51:28Z,As of 4.3.8 my Fedora 20 guest (Windows 8.1 host) is aborting when I launch Komodo IDE within the VRDP connection. If I launch Komodo with the VM running directly it does not abort. VBox.log attached.,Citryphus
12819,Host fails to read NTFS folder which is mounted to some partition,Linux,VirtualBox 4.3.8,2014-03-13T18:14:42Z,2015-01-27T08:14:56Z,2015-01-27T08:14:56Z,"Steps to reproduce:
* On Windows host, mount some partition (USB drive in my case) to NTFS folder, (say, to `C:\shared\usb`)
* Create new shared folder, ""shared"" = ""C:\shared"".
* Mount the folder in Linux guest.

Result:
* When listing the directory, ""usb"" is shown as symlink.
* When trying to `cd /mnt/shared/usb` the following error occurs:
{{{
-bash: cd: /mnt/shared/usb: Protocol error
}}}
",dmak
12780,VBoxSVC.exe crashes on Windows with VBox 4.3.8 when setting VBOX_USER_HOME,other,VirtualBox 4.3.8,2014-03-05T10:29:38Z,2014-07-01T08:45:29Z,2014-07-01T08:45:29Z,"Unable to set a dedicated different VBOX home path. Virtual Box COM Server is unable to work with new settings.

{{{
C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" --version
4.3.8r92456

C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" list systemproperties
API version:                     4_3
Minimum guest RAM size:          4 Megabytes
Maximum guest RAM size:          2097152 Megabytes
Minimum video RAM size:          1 Megabytes
Maximum video RAM size:          256 Megabytes
Maximum guest monitor count:     64
Minimum guest CPU count:         1
Maximum guest CPU count:         32
Virtual disk limit (info):       2199022206976 Bytes
Maximum Serial Port count:       2
Maximum Parallel Port count:     2
Maximum Boot Position:           4
Maximum PIIX3 Network Adapter count:   8
Maximum ICH9 Network Adapter count:   36
Maximum PIIX3 IDE Controllers:   1
Maximum ICH9 IDE Controllers:    1
Maximum IDE Port count:          2
Maximum Devices per IDE Port:    2
Maximum PIIX3 SATA Controllers:  1
Maximum ICH9 SATA Controllers:   8
Maximum SATA Port count:         30
Maximum Devices per SATA Port:   1
Maximum PIIX3 SCSI Controllers:  1
Maximum ICH9 SCSI Controllers:   8
Maximum SCSI Port count:         16
Maximum Devices per SCSI Port:   1
Maximum SAS PIIX3 Controllers:   1
Maximum SAS ICH9 Controllers:    8
Maximum SAS Port count:          8
Maximum Devices per SAS Port:    1
Maximum PIIX3 Floppy Controllers:1
Maximum ICH9 Floppy Controllers: 1
Maximum Floppy Port count:       1
Maximum Devices per Floppy Port: 2
Default machine folder:          C:\Users\dyle\VirtualBox VMs
Exclusive HW virtualization use: off
Default hard disk format:        VDI
VRDE auth library:               VBoxAuth
Webservice auth. library:        VBoxAuth
Remote desktop ExtPack:
Log history count:               3
Default frontend:
Autostart database path:
Default Guest Additions ISO:     C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso

C:\Users\dyle>del .VirtualBox
Möchten Sie ""C:\Users\dyle\.VirtualBox\*"" löschen (J/N)? j

C:\Users\dyle>set VBOX_USER_HOME=""C:\Users\dyle\AppData\Local\Temp""

C:\Users\dyle>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" list systemproperties
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

I've deleted the ~/.VirtualBox folder in between to start with a new fresh instance.

For us this is a project killer, as I'm unable to work with a dedicated VBox machine and environment path not located at the standard user paths. This sets our project at risk.",dyle71
14374,Network adapters not working after host returns from sleep Win 7 host Linux Mint 17.2 guest,Linux,VirtualBox 5.0.0,2015-08-02T17:02:25Z,2021-09-09T03:59:02Z,2021-09-09T03:59:02Z,"Host is Dell E7440 laptop running Windows 7 SP1 Enterprise 64 bit. VirtualBox version 5.0.0 r101573. Wireless NIC is Intel Dual Band AC 7260 as a bridged adapter virtualized as Intel PRO 1000 MT desktop. Guest is ""Linux Mint 17.2 Rafaela built on Ubuntu 14.04.2 LTS Trusty Tahr and kernel is 3.13.0-37-generic. The guest additions have been installed

Issue started appearing after the 5.0 update recently. After my host has returned from sleep my network connection is lost on my guest until i completely shutdown. I have tried switching the host adapter to other adapters. Disconnecting and reconnecting the cable in Devices>Network Settings. I have also tried just rebooting. The VM has to be completely powered off and back on for the adapter to work again. The network connection icon in the task bar stays discontented the entire time. No error message is given at any time.",Johnny Kilo
14291,Lots of error entries in VBoxSVC.log,other,VirtualBox 5.0.0,2015-07-17T09:50:44Z,2020-09-08T05:33:38Z,2020-09-08T05:33:38Z,"Looking into VBoxSVC.log I find lots of error entries.

When starting the VM Virtualbox Manager GUI, the first entries appear (time stamps 00:00:00 in attached file)

Then, related to time stamps beginning with 00:18:59 I executed the following commands, that are embedded in a script:
{{{
vboxmanage createvm --name AMHS-Tester --groups ""/AMHS-CentOS-Eval"" --ostype RedHat_64 --register --basefolder ""E:\VMs\Eval-Testsuite\AMHS-CentOS-Eval\VMs""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --memory 3072 --boot1 dvd --boot2 disk --boot3 none --cpus 8 --vram 12 --audio pulse --usb on --usbehci on
vboxmanage createhd --filename ""E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester"" --size 16384 --format VMDK --variant Split2G
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name IDE-Controller --add ide
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 0 --type dvddrive --medium ""E:\VMs\Eval-Testsuite\AMHSTESTER.iso""
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl IDE-Controller --port 0 --device 1 --type dvddrive --medium ""C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso""
vboxmanage storagectl 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name SATA-Controller --add sata --portcount 1
vboxmanage storageattach 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --storagectl SATA-Controller --port 0 --type hdd --medium ""E:\VMs\Eval-Testsuite\VMs\AMHS-CentOS-Eval\AMHS-Tester\AMHS-Tester.vmdk""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic1 hostonly --hostonlyadapter1 ""VirtualBox Host-Only Ethernet Adapter #2""
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nic2 natnetwork --nat-network2 NatAMHS
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --nicpromisc2 allow-all
vboxmanage sharedfolder add 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --name work --hostpath ""E:\VMs\Eval-Testsuite\work"" --automount
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --clipboard bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --draganddrop bidirectional
vboxmanage modifyvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --vcpfile ""E:\VMs\Eval-Testsuite\work\AMHS-Tester.webm"" --vcpwidth 1920 --vcpheight 1200
vboxmanage startvm 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c
}}}
And finally, starting at time stamp 00:18:59 the script checked the VM every five seconds using:
{{{
vboxmanage showvminfo 5cb950aa-86e4-4f31-8a2b-9d0b580e3e4c --machinereadable
}}}
The UUID is of course that of the newly created VM in the first command.
",Reiner Brodbeck
14275,Error with USB 3.0 devices on VirtualBox 5.0,all,VirtualBox 5.0.0,2015-07-14T06:11:13Z,2020-08-19T09:10:11Z,2020-08-19T09:10:11Z,"When I try to attach a device (USB 3.0) I got this message:

VirtualBox Error
Failed to attach the USB device Ralink 802.11 n WAN [0101] to the virtual machine ...
Details
USB device 'Ralink 802.11 n WLAN' with UUID ... Is busy with a previous request. Please try again later.


Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDeviceWrap
Interface: 
IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


Then I try changing to USB 2.0, but the error continue.

My HOST is DELL Inspiron 17r i7 with OS Windows 8.1 64 bits with 16 GB RAM, 1 TB HD (400 GB free).

I got the same error using with Existents VMs, one OS Win XP SP3 and  the second with Debian. ",Xopxe
14040,Windows host-only adapter creation fails due to slow background processing,all,VirtualBox 5.0.0,2015-04-10T02:11:16Z,2018-09-03T15:36:47Z,2018-09-03T15:36:47Z,"I was debugging why Xamarin Android Player could not prepare a VM for me and determined the failure to be in the host-only adapter creation, isolating the problem to this:

{{{
C:\Program Files\Oracle\VirtualBox\>VBoxManage.exe hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""int __cdecl handleCreate(struct HandlerArg *,int,int *)"" at line 66 of file VBoxManageHostonly.cpp
}}}

After some time spent in the debugger, I've found the real error to be `CO_E_CLASSSTRING` (Invalid class string), naturally returned by some `CLSIDFromString()` API call. Interestingly enough, the input GUID string contained garbage only.

Further debugging revealed a data race in `VBoxNetCfgWinCreateHostOnlyNetworkInterface()`. By the time `RegQueryValueExW(..., ""NetCfgInstanceId"", ...)` is called, the network device might still not be fully constructed by another process and this registry value might not be present yet. Because the result of this operation is effectively ignored, the program silently continues and the function fails only later due to the GUID being invalid.

A proof from Process Monitor - it took the system ~0.4 seconds more to write the value:
{{{
03:11:01.9426053	VBoxSVC.exe	15024	RegQueryValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	NAME NOT FOUND	Length: 144
03:11:02.3592881	svchost.exe	1140	RegSetValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	SUCCESS	Type: REG_SZ, Length: 78, Data: {F4CCBF3A-4C8B-4FE7-A659-725C3DF52E69}
}}}

Waiting in the debugger for a while before the `RegQueryValueExW()` call helped and I was able to create host-only network adapters fine.

Setting as priority minor because:
* it happened on a pre-release OS (Windows 10 preview build 10052)
* it happened on a pre-release VirtualBox (5.0.0_BETA1 r99371).

On the other hand, I submitted a ticket anyway because:
* the race is still a bug and can possibly crash the program, it might have been working with a little bit of luck only
* it seems the relevant VBox code has not been changed for the current beta
* I hear there was some refactoring done in Windows 10 regarding network adapters, this might show up later for more people",Jiri Hruska
14302,"Keyboard Caps lock, Num lock and Scroll Lock problems with Virtualbox 5.0",Windows,VirtualBox 5.0.0,2015-07-20T07:35:37Z,2018-06-12T00:40:49Z,2018-06-12T00:40:49Z,"Steps to reproduce the problem:
1) With no virtual machines running, activate Caps lock and/or Num lock and/or Scroll lock.
2) Start a virtual machines from saved state.
3) When I reduce the window of the virtual machine or I close it (by saving the state or by shut down the system) the state of Caps lock, Num lock and Scroll lock are deactivated.

Host: Windows 7 x64
Guest tested: Windows Xp SP3: Windows 7 x64 SP1; Windows 8.1 x64",bmn
14296,Failed to create COM object - 0x80040154,other,VirtualBox 5.0.0,2015-07-18T23:42:50Z,2017-11-28T22:25:24Z,2017-11-28T22:25:24Z,"When I try to run a Virtual Machine I get this error:


{{{
Failed to create the VirtualBoxClient COM object.
The application will now terminate.
Details:
Callee RC: 
REGDB_E_CLASSNOTREG (0x80040154)
}}}

After the error the Virtual Machine will not start.
The current virtual machine is a newly created Windows 8.1, but nothing has been installed yet because it won't launch.
Host is Windows 7 x64 and I am running VirtualBox 5.0.0

I've tried repairing my .net with dotNETfx. I have also tried re-registering the VBoxSvc.
I did a full reinstall and deleted the virtual box folders in C:\Users\UserName\

This error was occurring in the most recent stable 4.x version.

I have a forum thread open here:
https://forums.virtualbox.org/viewtopic.php?f=6&t=68992

I will keep trying to fix it on my own, but any help is appreciated.
",Circa
14340,VBoxSVC usb initialization causes host USB device to disconnect,all,VirtualBox 5.0.0,2015-07-28T17:23:00Z,2017-03-27T00:56:53Z,2017-03-27T00:56:53Z,"VirtualBox is causing the (host) SD card reader on my Microsoft Surface Pro 3 to disconnect/crash when VBoxSVC attempts to enumerate / initialize theUSB devices on the host. Any VirtualBox activity that attempts to enumerate the host USB devices (i.e. starting the VirtualBOX GUI, or executing a ""VBoxManage list usbdevices"") appears to cause this problem.

This occurs without any guest VM's running, and without any USB devices being configured for capture by VirtualBox.

I don't know if this is a bug in the Windows SD card driver that's being exposed by VirtualBox, or if it's a bug in VirtualBox itself.

To reproduce:
1. On a Surface Pro 3, mount an SD card
2. Initiate a large file copy to the SD card.
3. While the file copy is underway, execute the ""VBoxManage list usbdevices"" command. (or just start the VirtualBox GUI)

Expected result:
Files continue to copy to the SD card

Actual result:
The SD card volume drops offline. Windows displays a ""destination does not exist"" error. The windows event log shows a ""An error was detected on device \Device\Harddisk2\DR2 during a paging operation."" error.

The only error that I see in VBoxSVC.log file is ""Getting USB descriptor failed with error 31"". 

I have not attached the VBox.log file, as this error occurs without any guest instances running.",Hugh
14348,Video playback freezes in Linux guests with KVM paravirtualization enabled,Linux,VirtualBox 5.0.0,2015-07-30T00:49:30Z,2016-09-15T11:36:18Z,2016-09-15T11:36:18Z,"When KVM paravirtualization is enabled in VirtualBox 5.0.0 Linux guest operating systems fail to playback video. This is apparent with all video tested, including web video using Flash or HTML5. This has been tested on Antergos, Mint 17.2, and Fedora 22. Host Operating systems used to confirm this bug were Windows 8.1 and Windows 10.",Markon101
14421,Copy/paste not (always) working from host to guest,Linux,VirtualBox 5.0.0,2015-08-10T07:41:10Z,2016-08-31T13:31:14Z,2016-08-31T13:31:14Z,"Copy paste sometimes works from host to guest, but then often stops working after a few hours of the VM running. 

Copy paste from guest to host works. ",nopaste
14363,The Instruction at 0x... referenced memory at 0x... The memory could not be read,all,VirtualBox 5.0.0,2015-08-01T10:57:34Z,2016-07-06T17:58:43Z,2016-07-06T17:58:43Z,"As of version 4.3.16 I cannot start my Ubuntu guest on Windows 7 64 Bit.

Instead I receive the Error message:

""Die Anweisung in 0x... verweist auf Speicher 0x.... Der Vorgan read konnte nicht im Speicher durchgeführt werden.""

The English version according to Google should be:

""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""

This is just an update of Ticket #13580 because I cannot update its version number to 5.0.0.",Frank Breitling
14572,Can't recover the IP when USB2Ethernet adapter is removed and reconnected.,Linux,VirtualBox 5.0.0,2015-09-11T04:27:22Z,2016-03-14T16:19:00Z,2016-03-14T16:19:00Z,"= Heading =
IP address not recovered in bridged mode when USB2Ethernet adapter is removed and reconnected.

== Description ==
I'm running VirtualBox-5.0.0-r101573 64bit version on Windows 7 64bit OS, having guest as CentOSv6. The guestos is configured with two network adapters, 1) Host-Only 2) Bridged. When the guestos is booted afresh with the USB2Ethernet adapter connected, the Bridged network obtains the IP properly, But when the USB2Ethernet adapter is removed and reconnected the guestos is unable to fetch the IP and waits indefinitely.

'''Steps to reproduce'''
1. Boot the guestos with USB2Ethernet connected.
2. IP should acquire properly.
3. Remove the USB2Ethernet adapter from the System.
4. Try to restart the network service in the guestos.
5. Unable to fetch the IP and waits indefinitely.

'''Note''': Not tested on other guestos whether the same problem exists or not.",lokesh
14410,"Linux-on-Windows 3D support slow, buggy and generates lots of errors",Linux,VirtualBox 5.0.0,2015-08-06T19:20:44Z,2016-03-04T10:12:28Z,2016-03-04T10:12:28Z,"I'm running a Ubuntu 14.04.3 LTS guest inside VirtualBox 5.0 (with up-to-date additions) on Windows 7 Enterprise (64-bit) host. When 3D acceleration is enabled, screen redraws are slow and often do not refresh blocks of the screen correctly. For example, flipping through a multi-page PDF often results in half of the page not being redrawn. Also, sometimes the terminal (xterm) doesn't redraw when executing a command, giving the illusion that it didn't execute. Moving the window or scrolling will typically restore the contents of the window to what they should be.

Further, when I run the unity_support_test program, I get a lot of OpenGL warnings. In particular:

{{{
$ /usr/lib/nux/unity_support_test -p
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string:   Humper
OpenGL renderer string: Chromium
OpenGL version string:  2.1 Chromium 1.9

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yes

Unity 3D supported:       yes
}}}

As you can see, it thinks 3D acceleration works, and it's using the Chromium driver, but could not load the vboxvideo driver and as a result, the 3D accelerated behavior is flaky at best (per the description above).

The workaround has been to disable 3D acceleration and switch to a non-Unity desktop (for speed).",memoryhole
14424,Shared folder seems to cache old file content for the guest after editing host files,Linux,VirtualBox 5.0.0,2015-08-10T13:39:45Z,2015-12-08T17:42:12Z,2015-12-08T17:42:12Z,"I have VirtualBox 5.0.0 running on a Windows 7 SP1 x64 host, with an Ubuntu MATE 15.04 Linux as guest.

To exchange script files in development, I mounted a share manually to a shared folder (""sudo mount -t vboxsf {sharename} {targetname}"", because I did not know where to look for the auto-mounted share), where I copied files to in the hosting Windows, and copied files out of the share into a local directory in the guest Linux.

I found that the script files contained some bugs, which I fixed using Windows tools I have more experience with, which reduced the size of some files (e.g. converting CRLF line breaks to LF only, and deleting some text content).

Then I copied the files with the same name and location in the guest Linux out of the share and into the local directory again, overwriting the old versions of these files. So I thought. But I had to discover that the scripts still contained the buggy parts. And on top, the size was now reduced to the new file size, means, a part of the last script line was truncated now.

The only reliable way to edit the files inside the guest Linux was to empty the files, save with 0 bytes, close, re-open (in gedit or similar fork), then copy the text in a Windows text editor in the host, and paste the text into the Linux text editor via shared clipboard in the guest.",LigH
14428,win 10 host and VB from 5.0 to latest test build = NO bridge networking,Windows,VirtualBox 5.0.0,2015-08-11T13:44:44Z,2015-12-02T08:43:13Z,2015-12-02T08:43:13Z,"hi!

win 10 64 bit host , upgrade from win 8.1,
win xp guest

no way to set network -bridge-

hope someone will be able to find a workaround as for the 
issue of the no sound:
https://www.virtualbox.org/ticket/14361#comment:21

cheers",giusi
14435,ERROR In SupR3HardenedWinResSpawn,all,VirtualBox 5.0.0,2015-08-13T13:52:28Z,2015-11-21T22:09:45Z,2015-11-21T22:09:45Z,"OS Win7 x32 Ultimate.
Bitdefender Antivirus Free Edition 1.0.21.1099.
VirtualBox - 5.0.0-101573 (similar errors appeared with version 4.3.14)
When I run the guest appears this window:
""ERROR In SupR3HardenedWinResSpawn""
After removal of the antivirus VBox starts as expected.",digitadropper@…
14398,webcam on Lenovo T550 with CentOS 7.1 guest,Linux,VirtualBox 5.0.0,2015-08-05T18:53:20Z,2015-11-04T15:32:51Z,2015-11-04T15:32:51Z,"Hi.

I'm running VirtualBox 5.0.0 under Win7 on a Lenovo T550 laptop. 
My guest O/S is CentOS 7.1.
On the Win7 system, the integrated laptop webcam works perfectly.
If I export the webcam to the Linux guest O/S (ie. in the ""Devices"" menu, under Webcams, ""Integrated Camera"" is selected.), then the guest O/S sees the webcam as well (uvcvideo, 04ca:703c).
In the guest O/S, if I start ""cheese"" (a tool to take pictures and video from the webcam), I should see a live preview of the webcam input.  The light on the camera does go on and stays on, but rather than displaying the live preview, I get the first frame that cheese saw when it was started.  That frame doesn't change.  I can click ""take picture"" over and over but it will capture the identical frame.
If I change the video resolution in cheese, then the frame changes one more time.

I tried on an older VirtualBox version 4.3.18, and the problem is identical.
I tried with CentOS 6, under both VirtualBox versions 4.3 and 5.0 (with proper guest extensions), and had the same problem.
I tried with a Lenovo T540p laptop (previous generation of this laptop), and the live preview in cheese worked on both 4.3 and 5.0.

It's important to note that the problem is not explicit to just ""cheese"".  For example, if I visit the following URL in Firefox:

http://mdn-samples.mozilla.org/s/webrtc-capturestill/

This is a WebRTC demo.  In the left box, I should see a live preview of my webcam.  I get the same problem (1 frame).  The same demo works properly on the underlying Linux box, and from the T540p laptop.

I installed a CentOS 7.1 system from scratch with no vbox, and the camera works fine with cheese (and demo above).
I installed VirtualBox 5 on this CentOS 7.1 system, and then installed the same VM that was having the cheese problem, and the video passes through perfectly as well!
I would guess this means that the issue is in the Windows Extension pack.

I'm really really anxious to resolve this issue soon because I really need it for later this month.  If there's any help that I can provide, please let me know.

Jason.",kangaroo
14268,Implementing VMDK relative raw disk partitions on Windows,all,VirtualBox 5.0.0,2015-07-13T14:15:02Z,2015-10-13T13:39:01Z,2015-10-13T13:39:01Z,"This bug serves to track progress of implementing the -relative option for the '''VBoxManage internalcommands createrawvmdk -filename ... -rawdisk ... -partitions ...''' command on Windows hosts.

See [https://www.virtualbox.org/manual/ch09.html#rawdisk section 9.9.1] of the docs regarding using physical partitions as a Virtual Drive for a VM. The -relative option for the above command was only available on Linux hosts.",regedit
14436,Host screen saver do not start on VirtualBox 5,Windows,VirtualBox 5.0.0,2015-08-14T00:30:12Z,2015-09-10T16:20:44Z,2015-09-10T16:20:44Z,"When there is a virtual machine running and the relative window is active, the screen saver of the Host, when the time is elapsed, starts but terminates immediately.
Tested on VirtualBox v5.0 and v5.0.2
Host tested: Win 7 x64 Professional SP1
Guests tested: Win 7 x64 Ultimate SP1 and Windows XP x86 SP3
",bmn
14479,Virtual box hangs/crashes on VM rename,other,VirtualBox 5.0.0,2015-08-20T23:38:06Z,2015-09-08T11:42:05Z,2015-09-08T11:42:05Z,"1) Make a new VM, called ""test""
2) Right-click VM > settings
3) Change name to be ""test (a:b)""
4) OK

An error will occur. On confirming the dialog, Virtual box will hang",RoelV
14517,Menubar disappears in fullscreen mode when 3D acceleration is activated in VM settings,Windows,VirtualBox 5.0.0,2015-08-29T13:32:13Z,2015-08-29T13:32:13Z,2015-08-29T13:32:13Z,"Hello,[[BR]]

I think that I found a bug:[[BR]]

I have a VM running with guest OS Windows 8.1 on a Windows 10 host (both 64bit). The problem that occurs is that the menubar disappears in fullscreen mode when I click into the VM (e.g. on the desktop or a window of the VM). If I click on the host desktop on my second screen after this, the menubar will appear again. However, if I click into the guest again the menubar will disappear again. The problem only occurs when I have activated 3D acceleration in the VM settings. 2D acceleration doesn't cause that problem.[[BR]]

If you need more information you can feel free to contact me.",JKLs
14403,Symlinks are created incorrectly on shared directories,Linux,VirtualBox 5.0.0,2015-08-06T08:59:44Z,2015-08-26T08:04:54Z,2015-08-26T08:04:54Z,"I have a trusted environment for development and I have activated symlink support for shared folders as desribed here: https://www.virtualbox.org/ticket/10085

This solution worked great so far, however since VirtualBox 5 (in combination with Win 10 host), the creation is incorrect.

If I create a symlink on a shared folder with the command

{{{
ln -s /media/sf_data/file.js /media/sf_data/test.js
}}}

The symlink is created but using readlink, I can see that the created path is incorrect:

{{{
\media\sf_data\test.js
}}}

The backslash should be replaced by a slash.

If I create a symlink outside the shared folder, everything is correct. Also if I create a symlink pointing to a file in a shared folder. However if I create a symlink within a shared folder to a file outside the shared folder, the bug exists.",MathiasB
14377,No Network-Adapters found after Windows 10 Installation,Windows,VirtualBox 5.0.0,2015-08-03T10:06:39Z,2015-08-15T10:06:52Z,2015-08-15T10:06:52Z,After Installation of Windows 10 pro upgrade from Windows 7 pro no networkadapters are selectable under the VMs properties Network->Networkbridge and also under Network->Host-only Adapter. The same bug was found after new installation of VirtualBox. ,arcor.de
14261,Bridge network,Linux,VirtualBox 5.0.0,2015-07-11T09:53:19Z,2015-08-15T01:28:49Z,2015-08-15T01:28:49Z,"Since my upgrade to Virtual Box 5, I have 2 issues :

1/ My Bridged Network does not work anymore, I had to switch to NAT",daredevil
14385,Guest  Ubuntu 15.04 (64 bit) crashes on Host Windows 7 AND 10 (each 64bit) after upgrading to VB v5.0 unless nested paging left OFF,Linux,VirtualBox 5.0.0,2015-08-04T09:03:59Z,2015-08-14T09:17:52Z,2015-08-14T09:17:52Z,"I upgraded to VirtualBox 5.0.0-101573 three weeks ago, from VirtualBox v4.3.30.
Today I also tried Testbuild 5.0.1-101908.

With the new versions 5.0.X I cannot use my Ubuntu 15.04 (64 bit) VM anymore, unless I turn nested paging off. When it is turned on Ubuntu crashes and restarts when I try to access the VM.
I tried it on both Windows 7 and Windows 10 Host (each 64 bit).

For now, I reverted to VirtualBox v4.3.30 which runs it fine.

It looks like it is the same error as #14262 and #14263, although Guest/Host are the opposite.",Aweman
14395,"vbox 5 host firewall blocks bridged networking, used to work in 4.3.20",Windows,VirtualBox 5.0.0,2015-08-05T14:37:58Z,2015-08-09T06:33:20Z,2015-08-09T06:33:20Z,"I migrated from vbox 4.3.20 on a w7/64 host to vbox 5 & later to 5.01

I run Bitdefender Internet security on my host

VM's (w7) that used to work with bridged networking under vbox 4.3.20 no longer can access internet. Disabling the Bitdefender host firewall solves the issue. accessing local web resources on the intranet such as a NAS management webpage does work. So it looks like the new network adapter of 5.x is causing the issue

NAT does work with the host firewall enabled.",Frank Bevers
14399,Background VMs are halted when Host is shuting down,all,VirtualBox 5.0.0,2015-08-05T20:30:19Z,2015-08-05T20:30:19Z,2015-08-05T20:30:19Z,"I see the great feature in VirtualBox 5!!! Its posibility to run virtual machines in background. Its very cool and must have feature.
But!! When i shutdown my windows host machine it halts all background virtual machines. It is not funny. Why halt it? It is better to susspend it by default. Isn't it?

So great tool. Great new features. But fix this ""little bug"" please.",artkor
14387,Application Error when Plugging/Unplugging HDMI for second display,Linux,VirtualBox 5.0.0,2015-08-04T13:10:09Z,2015-08-04T13:10:09Z,2015-08-04T13:10:09Z,"When unplugging/plugging in HDMI cable for second display on my laptop, I receive dialog ""VirtualBox.exe - Application Error"", ""The instruction at 0x80165d4a referenced memory at 0x00000018.  The memory could not be read.""

I am running a Windows 8.1 host, with Ubuntu 14.04 as the guest.",cmo
14274,BSoD in VBoxNetLwf with d1,other,VirtualBox 5.0.0,2015-07-14T06:07:13Z,2015-07-31T11:58:40Z,2015-07-31T11:58:40Z,"'''Version:'''[[BR]]

VirtualBox 5.0.0-101573[[BR]]

'''Network Adapters:'''[[BR]]

RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC[[BR]]

VirtualBox Host-Only Ethernet Adapter[[BR]]

'''Minidump'''[[BR]]
{{{
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880079c2007, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880042ab2a4, address which referenced memory

Debugging Details:
------------------

DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\nsiproxy.sys - file not found
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys - OK
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys found
DBGENG:  C:\Windows\System32\drivers\nsiproxy.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\mssmbios.sys - file not found
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys - OK
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys found
DBGENG:  C:\Windows\System32\drivers\mssmbios.sys - Mapped image memory
SYMSRV:  mssmbios.pdb from http://msdl.microsoft.com/download/symbols: 50755 bytes - copied         
DBGHELP: mssmbios - public symbols  
         f:\localsymbols\mssmbios.pdb\9ECFB21A2AD64292AB8AF8AB1B194C2E1\mssmbios.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetLwf.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetLwf.sys - Mapped image memory
SYMSRV:  f:\localsymbols\VBoxNetLwf.pdb\7E00272F27A1406CADE9A553C591E1CB1\VBoxNetLwf.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/VBoxNetLwf.pdb/7E00272F27A1406CADE9A553C591E1CB1/VBoxNetLwf.pdb not found
DBGHELP: VBoxNetLwf.pdb - file not found
DBGHELP: F:\tinderbox\win-rel\out\win.amd64\release\obj\VBoxNetLwf\VBoxNetLwf.pdb - file not found
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxNetLwf.sys - 
DBGHELP: VBoxNetLwf - export symbols
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetAdp6.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetAdp6.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ndis.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ndis.sys - OK
DBGHELP: C:\Windows\System32\drivers\ndis.sys found
DBGENG:  C:\Windows\System32\drivers\ndis.sys - Mapped image memory
SYMSRV:  ndis.pdb from http://msdl.microsoft.com/download/symbols: 420783 bytes - copied         
DBGHELP: ndis - public symbols  
         f:\localsymbols\ndis.pdb\7F2704456B8949D6BD0D97D90F00DB912\ndis.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Rt64win7.sys - file not found
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys - OK
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys found
DBGENG:  C:\Windows\System32\drivers\Rt64win7.sys - Mapped image memory
SYMSRV:  f:\localsymbols\rt64win7.pdb\CA0B16D985A346649CC5D6735331FF111\rt64win7.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/rt64win7.pdb/CA0B16D985A346649CC5D6735331FF111/rt64win7.pdb not found
DBGHELP: rt64win7.pdb - file not found
DBGHELP: d:\svn\ndis_6\driver\src\src\sysw7x64\objfre_win7_amd64\amd64\rt64win7.pdb - file not found
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
DBGHELP: Rt64win7 - no symbols loaded
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\TDI.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\tdi.sys - OK
DBGHELP: C:\Windows\System32\drivers\tdi.sys found
DBGENG:  C:\Windows\System32\drivers\tdi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\afd.sys - file not found
DBGHELP: C:\Windows\System32\drivers\afd.sys - OK
DBGHELP: C:\Windows\System32\drivers\afd.sys found
DBGENG:  C:\Windows\System32\drivers\afd.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\WDFLDR.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys - OK
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys found
DBGENG:  C:\Windows\System32\drivers\WdfLdr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ACPI.sys - file not found
DBGHELP: C:\Windows\System32\drivers\acpi.sys - OK
DBGHELP: C:\Windows\System32\drivers\acpi.sys found
DBGENG:  C:\Windows\System32\drivers\acpi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\tcpip.sys - file not found
DBGHELP: C:\Windows\System32\drivers\tcpip.sys - OK
DBGHELP: C:\Windows\System32\drivers\tcpip.sys found
DBGENG:  C:\Windows\System32\drivers\tcpip.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\vga.sys - file not found
DBGHELP: C:\Windows\System32\drivers\vga.sys - OK
DBGHELP: C:\Windows\System32\drivers\vga.sys found
DBGENG:  C:\Windows\System32\drivers\vga.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VIDEOPRT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\videoprt.sys - OK
DBGHELP: C:\Windows\System32\drivers\videoprt.sys found
DBGENG:  C:\Windows\System32\drivers\videoprt.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\HIDPARSE.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\hidparse.sys - OK
DBGHELP: C:\Windows\System32\drivers\hidparse.sys found
DBGENG:  C:\Windows\System32\drivers\hidparse.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbccgp.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys found
DBGENG:  C:\Windows\System32\drivers\usbccgp.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbehci.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbehci.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbehci.sys found
DBGENG:  C:\Windows\System32\drivers\usbehci.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\USBPORT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\usbport.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbport.sys found
DBGENG:  C:\Windows\System32\drivers\usbport.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\umbus.sys - file not found
DBGHELP: C:\Windows\System32\drivers\umbus.sys - OK
DBGHELP: C:\Windows\System32\drivers\umbus.sys found
DBGENG:  C:\Windows\System32\drivers\umbus.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbhub.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbhub.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbhub.sys found
DBGENG:  C:\Windows\System32\drivers\usbhub.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\watchdog.sys - file not found
DBGHELP: C:\Windows\System32\drivers\watchdog.sys - OK
DBGHELP: C:\Windows\System32\drivers\watchdog.sys found
DBGENG:  C:\Windows\System32\drivers\watchdog.sys - Mapped image memory
DBGHELP: C:\Windows\System32\win32k.sys - OK
DBGENG:  C:\Windows\System32\win32k.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\srv.sys - file not found
DBGHELP: C:\Windows\System32\drivers\srv.sys - OK
DBGHELP: C:\Windows\System32\drivers\srv.sys found
DBGENG:  C:\Windows\System32\drivers\srv.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\fltmgr.sys - file not found
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys - OK
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys found
DBGENG:  C:\Windows\System32\drivers\fltMgr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Ntfs.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ntfs.sys - OK
DBGHELP: C:\Windows\System32\drivers\ntfs.sys found
DBGENG:  C:\Windows\System32\drivers\ntfs.sys - Mapped image memory

READ_ADDRESS:  fffff880079c2007 

CURRENT_IRQL:  2

FAULTING_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880079c1460 -- (.trap 0xfffff880079c1460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880042ab2a4
rdx=fffff880079c2006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880042ab2a4 rsp=fffff880079c15f0 rbp=fffff880042be4d8
 r8=0000000000000000  r9=fffff880042a8000 r10=0000000000000000
r11=fffff880079c1610 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
VBoxNetLwf+0x32a4:
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1] ds:4256:fffff880`079c2007=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7fe69 to fffff80002c808c0

STACK_TEXT:  
fffff880`079c1318 fffff800`02c7fe69 : 00000000`0000000a fffff880`079c2007 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`079c1320 fffff800`02c7eae0 : fffff880`03572180 fffffa80`12a47b50 00000000`00000206 fffffa80`1c73f7a0 : nt!KiBugCheckDispatch+0x69
fffff880`079c1460 fffff880`042ab2a4 : fffffa80`1e81af50 00000000`000007ff fffffa80`1e81af50 fffffa80`1c73f670 : nt!KiPageFault+0x260
fffff880`079c15f0 fffff880`042ab72e : fffffa80`1ca55740 00000000`00000000 fffff880`042be4d8 fffffa80`1dbbb0e0 : VBoxNetLwf+0x32a4
fffff880`079c1690 fffff880`042abb78 : 00000000`00000000 00000000`00000000 fffffa80`1ca55740 fffff880`00000000 : VBoxNetLwf+0x372e
fffff880`079c1700 fffff880`01aac0a7 : 00000000`00000000 fffffa80`1c3491a0 00000000`00000000 00000000`00000000 : VBoxNetLwf+0x3b78
fffff880`079c1780 fffff880`05846cf4 : fffffa80`1c6ad000 fffffa80`1c6ad000 00000000`00000000 fffffa80`1c73f670 : ndis! ?? ::FNODOBFM::`string'+0xcd8f
fffff880`079c17d0 fffff880`058319c4 : fffffa80`1c349100 fffff880`05832c01 fffff880`0000000a fffff880`079c1a60 : Rt64win7+0x1bcf4
fffff880`079c19f0 fffff880`01b14542 : fffff880`00000000 fffffa80`1c3491a0 fffffa80`1c3491a0 fffffa80`00000000 : Rt64win7+0x69c4
fffff880`079c1a60 fffff880`01a9d56d : 00000000`00000002 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis!ndisMiniportDpc+0xe2
fffff880`079c1ad0 fffff880`01ac3b7d : 00000000`00000002 00000000`00000002 00000000`00000000 fffffa80`1ca4ed78 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd
fffff880`079c1b70 fffff800`02f1a456 : 00000000`27c49c63 fffffa80`3fae6b50 00000000`00000080 fffffa80`3fae6b50 : ndis!ndisReceiveWorkerThread+0x1bd
fffff880`079c1c00 fffff800`02c722c6 : fffff880`03500180 fffffa80`3fae6b50 fffffa80`1d67f6c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`079c1c40 00000000`00000000 : fffff880`079c2000 fffff880`079bc000 fffff880`079c18c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  VBoxNetLwf+32a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxNetLwf

IMAGE_NAME:  VBoxNetLwf.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  559e4840

FAILURE_BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

Followup: MachineOwner
---------
}}}",bookevg
14354,"Simple Feature request: Please Change the ""Input"" Menue",other,VirtualBox 5.0.0,2015-07-31T08:32:15Z,2015-07-31T08:35:30Z,2015-07-31T08:35:30Z,"Hello

I have a german installation, therefore I try to translate the menue names...

The Window of a virtual machine has a menue:
File - Machine - View (or Display) - Input - Devices - Help

The ""Input"" Menue is unnecessarily nested and therefore the handling is (unnecessarily) intricate:

Input
 +- Keyboard
 |  +- Keyboard Configuration
 |  +- ----------------------
 |  +- Send Ctrl-Alt-Del
 |  +- Send Ctrl-Break
 |  +- Send Insert
 +- ----------------------
 +- Mouse-Pointer Integration


Because this Menue does not have many items, could your please change it for an easier and better usability to this Layout:

Input
 +- Keyboard Configuration
 +- Send Ctrl-Alt-Del
 +- Send Ctrl-Break
 +- Send Insert
 +- ----------------------
 +- Mouse-Pointer Integration

Thanks a lot in advance,
kind regards,
Tom",Tom P
14289,Drag and drop failing from vm to host,Windows,VirtualBox 5.0.0,2015-07-17T05:58:56Z,2015-07-28T09:31:39Z,2015-07-28T09:31:39Z,"With latest Virtualbox 5.0 r101573 and updated guest additions, Host Win7, Guest XP, I'm able to drop files from host to vm but not the opposite.

I get a ""Drag and drop error from guest (VERR_INVALID_PARAMETER)."" followed by VBOX_E_IPRT_ERROR (0x80BB0005), component GuestWrap, interface IGuest {13a11514-402e-022e-6180-c3944de3f9c8}
",ctrl
14330,Guest OS still show black sreen when it startup,Windows,VirtualBox 5.0.0,2015-07-27T02:15:37Z,2015-07-27T02:15:37Z,2015-07-27T02:15:37Z,"Guest OS is windows 8.1 x64 or windows 10 x64.
When guest os startup ,after windows splash screen,it is still show a black screen when 3D acceleration is enabled.I have to force to close the guest OS.When 3D acceleration disabled it works fine.

",binary
14313,Windows resizes to the smallest size,Windows,VirtualBox 5.0.0,2015-07-21T18:42:40Z,2015-07-21T18:42:40Z,2015-07-21T18:42:40Z,"Virtual machine starts in the tiny winndow (smallest possible size). With guest additions installed and without them.

If the auto adjust option is on and trying to resize with the mouse the window is blinking and right after the mouse buttom is up the window resizes to the smallest size again.

But with fully expanded window and in the full screen everything works correct.

As I suppose VirtualBox fails o detect curent guest screen size and sets the smallest windows size every time exept full screen and expanded cases.

Tested with:[[BR]]
VirtualBox 5.0 (4.3.38, 4.3.30) tested with (and without) guest addition of corresponding versions[[BR]] 
Host Windows 7 (latest updates) fresh install [[BR]]
Guest Windows 7 (latest updates)[[BR]]
Intel hd graphics 4600 drivers 10.18.14.4222[[BR]]",Lester
14299,GUI should disable snapshot delete on running VM,Linux,VirtualBox 5.0.0,2015-07-19T12:52:52Z,2015-07-20T21:12:01Z,2015-07-20T21:12:01Z,"This has happened a couple of times to me. I go to delete a snapshot, not realizing the VM is already running. I get an error. Thereafter, even with the VM stopped, I cannot delete any of its snapshots. Simplest fix I would recommend: disable GUI controls for deleting snapshots on running VMs.",Dale Visser
14832,Unable to use Host-Only adapters on Windows 10 Threshold 2,all,VirtualBox 5.0.10,2015-11-16T01:38:09Z,2020-10-30T19:55:25Z,2020-10-30T19:55:25Z,"I installed the new Windows 10 update ""threshold 2"" via Windows Update, and VirtualBox is no longer able to use Host Only adapters.  While it creates them, changes their IPs, and deletes them with no trouble, the following error message comes up when I try to run any VM with a Host Only interface attached:

{{{
Failed to open a session for the virtual machine Ubuntu Test.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

This worked with no trouble before the Windows Update, and all other adapter types still work perfectly.

I originally had this issue with VirtualBox 5.0.1, so I uninstalled that one and installed 5.0.10, and I still have the issue.

Log file attached.",kohenkatz
14823,Error messages on a Windows 7 shutdown when VirtualBox is still open,other,VirtualBox 5.0.10,2015-11-13T19:53:35Z,2019-11-12T21:48:28Z,2019-11-12T21:48:28Z,"I always get a series of 6 error messages that popup when I try to shutdown my computer when virtualbox is still open.  I don't have to have any VMs open.

To reproduce:
1. Start computer.
2. open virtualbox.
3. shutdown computer.
I get the attached error messages each time.  I have to click OK on each one.

Let me know what you need.  Maybe it's something to do with my specific computer but I figure it out from the error messages.",Wes Manning
14846,VBoxManage Error about Machine XXX is not currently running and Machine XXX is really running in Windows Task Manager,other,VirtualBox 5.0.10,2015-11-19T17:15:54Z,2018-04-05T20:10:43Z,2018-04-05T20:10:43Z,"Hi, I'm trying to launch the command ""vboxmanage controlvm XXX savestate"" (or controlvm XXX poweroff) after to have been executed succesfully, about 15 or 20 minutes before <if you try to reproduce this issue I explain but starting the VM follow by shutting down inmediatly via commands curiosely it works fine..>, the command ""vboxmanage startvm XXX --type headless"" (as well as without headless modifier) from a Scheduled Task of Windows Task Scheduler. I'm involved whith this issue for several days, perhaps two weeks... I've tried all I know about it... It seems to be that transcurred some minutes from starting the machine, she (the machine) disappears from the runnig list machines as I can positively test: just now I have my three-VBoxHeadlexx processes plus one VBoxSVC process running on my Windows 7 x64, and if I run ""vboxmanage list runningvms"" I get no machines running message. So, when I try to run ""vboxmanage controlvm XXX savestate"" manually or through a Scheduled Task, I get a no running machine with that name in the first case, or a 0x01 code in the Windows Task Scheduler saying ""the command-task finished but with warnings"". Thanks for support and best regards.",aZtk-laga
14904,Not possible to create Host Only network,Windows,VirtualBox 5.0.10,2015-12-06T14:53:09Z,2016-06-17T07:23:29Z,2016-06-17T07:23:29Z,"when click on add new receive this error :
Querying NetCfgInstanceId failed (0x00000000).

Result Code: 
E_FAIL (0x80004005)
Component: 
HostNetworkInterfaceWrap
Interface: 
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

This happens on windows 10 build Version 10.0.10586 Build 10586

Without this, cant use 3rd party software like Genymotion (dont launch enymore)",Sergi
15276,copy&paste alter guest opened file,Linux,VirtualBox 5.0.10,2016-03-26T15:40:26Z,2016-03-26T15:40:26Z,2016-03-26T15:40:26Z,"Hi All,

I have problem with the share functionalities. When I open for editing a shared file just on the quest (used VBox shared folder, e.g. code editing) and I continue to work in the host (e.g. browsing on the net) and I using copy-paste, sometimes in the guest my text cursor moved and guest clipboard pasted in that position. So paste event triggered on both machines (different content). This problem sometimes I have just working on the guest e.g. editing not a shared file: paste at the end, continue to typing, scroll up and last pasted text inserted multiple times in the old text. These are very annoying.
I had no time to experiment exact what are the problems or reinstall and reconfigure the guest. I will do..., but first I just wanted to know if anyone had a similar issue and if this issue was 'fixed'.
 
Host: Windows 7
Guest: openSUSE 13.1
Enabled: shared copy&paste, drag&drop, shared folder

Regards,",bandki
14880,Guest Additions donot work on windows 10 host,Windows,VirtualBox 5.0.10,2015-12-01T14:41:32Z,2016-03-11T06:53:57Z,2016-03-11T06:53:57Z,"I am running Windows 7 guest on Windows 10 host. 
Win 7 runs without guest additions but when i install them windows doesn't start and gives this error message
Load library failed with error 1114: A dynamic link library (DLL) initialization routine failed.
If i go to safe mode and uninstall guest additions then windows runs again. I set 3D unchecked in guest settings. and didn't install Direct3D(experimental)when installing Guest additions.",petergemeni
14905,Error In supR3HardNtChildWaitFor,Linux,VirtualBox 5.0.10,2015-12-06T21:10:26Z,2016-02-01T09:27:14Z,2016-02-01T09:27:14Z,"Since last week I've been encountering problem with starting Linux virtual machine. It's now starting about 2 minutes and before start it throws an error (in attachment: error-screenshot.jpg).
I've disabled my Avira antivirus real-time protection but it doesn't help, I hadn't installed any additional software before bug started to appear (only Avira Antivirus had made it's update).",DSProgrammer
15039,"Assertion failed, Please contact the product vendor!",Windows,VirtualBox 5.0.10,2016-01-17T09:15:08Z,2016-01-18T09:20:19Z,2016-01-18T09:20:19Z,"I got the message below.

Additional info: It occurred after I was trying to delete some snapshots and got various error messages like access denied and invalid object state. I do not know if these errors were related. This time also my harddisk was getting full and eventually the machine refused even to show up in the VirtualBox window.

Just for additinal note, the snapshot delete functionality currently quite often fails, even when disk has enough room. The failures look random - same snapshot always fails, but which ones will fail and which ones will not for same virtual machine, is not predictable.

{{{
Assertion failed: [m->state == MediumState_LockedRead] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\MediumImpl.cpp' (4411) in long __cdecl Medium::i_createDiffStorage(class ComObjPtr<class Medium> &,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0074,class MediumLockList *,class ComObjPtr<class Progress> *,bool).
Please contact the product vendor!.


Result Code: 
E_FAIL (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}",levitation
14972,VirtualBox disables ASIO analogue inputs on my MIA MIDI soundcard,Windows,VirtualBox 5.0.10,2015-12-23T13:47:04Z,2015-12-23T13:52:47Z,2015-12-23T13:52:47Z,"I am running Version 5.0.10 r104061 on an ASUS Z87-A motherboard with an Intel i7-4770 CPU and 16GB memory. I also have an Echo Digital Audio Mia Midi PCIe sound card which uses ASIO drivers. I use this as my main soundcard and have disabled the onboard soundcard on my Motherboard.

When I run any guest with sound enabled: Windows Direct Sound, Intel HD Audio, the ASIO analogue virtual inputs are disabled in all my audio programs (DAWs) and replaced with the digital S/PDIF inputs.
If I disable audio in the guest the ASIO ports work correctly.
If I select Windows Direct Sound as input, I can record on the host and still get sound from the guest. However, as I record music, I want the ASIO drivers to be available on the host. 

VB should recognise all the audio hardware on the host and allow me to direct the guest to use the on-board audio hardware on the motherboard 
",MarkT
14939,VM VirtualBox 5.01 on Windows 10 has excessive disk activity when running Debian 7.0.0,Linux,VirtualBox 5.0.10,2015-12-17T14:57:04Z,2015-12-22T02:41:26Z,2015-12-22T02:41:26Z,"Since I have upgraded from 4.2.34 to 5.0.10-104061, the performance
of Debian 7.0.0 (40.0 Gb) has gone down significantly.
Whenever I resume the saved state, there is a lot of disk
activity even when I am doing nothing. The Windows 10 Task Manager
indicates disk activity peaking around 30 Mbytes/sec coming
from the VirtualBox Manager. A lot of disk activity continues while I
am working in a command window in Linux. I have encountered the
same issue with Windows 7 (before I upgraded to Windows 10 recently).

I have tried to regress back to 4.2.34, but I am unable to restart
the saved state of Debian 7. ""Failed to open session for virtual
machine debian 7.0.0. Unsupported version 17 of data unit cpum""

Occasionally when I close the Virtual Machine using save state,
it gets aborted. When I restart the virtual machine, Debian reboots.",seymour
14926,kernel 4.2 incompatible headers structure,Linux,VirtualBox 5.0.10,2015-12-13T01:36:25Z,2015-12-17T08:04:03Z,2015-12-17T08:04:03Z,"virtualbox guest additions (v 5.0.10) claim that can't find headers for current kernel, but install successfully.

In Ubuntu 15.10 amd64.",MikhailRokhin
14930,Excel 2016 can't open file in Windows 10,Windows,VirtualBox 5.0.10,2015-12-14T12:51:22Z,2015-12-14T13:15:05Z,2015-12-14T13:15:05Z,"Hi,

I've an issue when I'm trying to open a file in Excel 2016 from the Explorer under Windows 10 guest. The error says that ""There was a problem sending the command to the program""

Reading different solutions on windows forums I found that if I disable the hardware acceleration graphics in excel, then the file opens normally.

Also it doesn't matter the location of the file. The error happens either if the file is on a local disk(desktop) or shared folder or network mapped folder.

There are some roundabouts where the file opens fine with hardware accelerated graphics enabled:
- If Excel is already open and open a file from the explorer.
- If I open the file form Excel.

The only scenery is opening a file from explorer while the Excel is closed and HW acc graphics is enabled.

setup:
- Guest: Windows 10 pro x64 using hyper-v and graphics acceleration enabled.
- Host: Windows 7 Enterprise x64 @ Intel i5 4300M
- Virtualbox: 5.0.10 r104061 also tested in 5.0.11 r104675.",David Eduardo Cortelezzi
14924,GNU/Linux guest aborts while saving when 3D acceleration is enabled,Linux,VirtualBox 5.0.10,2015-12-12T18:00:46Z,2015-12-12T18:00:46Z,2015-12-12T18:00:46Z,"Virtualized GNU/Linux box (Ubuntu Gnome 15.10) crashes every time when trying to save machine state, only if 3D acceleration is enabled: the progress bar reaches 97%, then the machine status is set to ""Aborted"".

Disabling 3D acceleration makes the problem disappear, while touching any other parameter (including increasing or decreasing guest RAM or video memory) does not seem to have an impact.

I also tried the latest test build (5.0.11-104602 at the time of writing), without success.

All machine details are in the logs attached.
Guest syslog, Xorg.log, and kern.log are also included.

Thanks!",eisenach
14919,Polycom CX600 gets call from Computeraudio when starting VM with ICH AC97 controller,all,VirtualBox 5.0.10,2015-12-11T09:07:52Z,2015-12-11T09:07:52Z,2015-12-11T09:07:52Z,"Since VirtualBox-5.0.2-102096 I have a strange behavior with my Polycom CX600 phone connected via USB to the my host system (Windows 7).

As soon as a VM is started and the VM BIOS is loading, the phone shows me silently a call to ""Computeraudio"". Every real call to my phone then only is knocking on like the phone is busy.

As soon I stop the VM, the ""Computeraudio"" call is interrupted and the phone works again like it should.

In VirtualBox-5.0.0-101573 and older versions everything works fine.

Every Version since VirtualBox-5.0.2-102096 have the same behavior, including the actual version VirtualBox-5.0.10-104061.

I tried a little bit around with some settings and found out that this doesn't happen when the audio controller is not set to ""ICH AC97"". Intel HD Audio and SoundBlaster 16 doesn't produce this behavior, but I get no sound out of my Linux guests with these two audio controllers (especially tested with Knoppix LiveDVD 7.6 for repeatable results).

Another check was what happen when I disconnect the phone USB cable from the host.
When the guest was already started and the phone shows already the ""Computeraudio"" call, the call is interrupted as soon as I disconnect the USB cable. After connecting it again, the phone dosn't show the ""Computeraudio"" call again (until reboot the VM).
When I disconnect the cable before starting the VM and plug it in after the VM was started, no ""Computeraudio"" call is shown. The phone works normally.

Because of this behavior starts before the guest OS is loading, I think this is independent of it. Nevertheless I checked out lsusb but there are no USB devices shown, except the input device and the USB root hubs.

I will attach four log files (for Version 5.0.0 and 5.0.2 one with ICH AC97 and one with Intel HD Audio controller). And if it works, also an picture of the phone screen.

",Andy1971
14911,Black screen with OpenGL only in full-screen mode,Linux,VirtualBox 5.0.10,2015-12-08T14:52:38Z,2015-12-08T14:52:38Z,2015-12-08T14:52:38Z,"When I'm not in full-screen mode, I can run an OpenGL application such as glxgears, and it works fine. In full-screen mode, however, the entire screen will go black except for the contents of the window where 3D rendering is occurring. For example, with glxgears I see only the gears, and the rest of the screen is black.

I'm running Debian ""jessie"" as a guest with VirtualBox 5.0.10 on a Windows 7 SP1 host. Both the guest and the host are 64-bit. I've installed the guest additions for 5.0.10 via the CD image supplied with VirtualBox. 3D acceleration is enabled in the VM settings. (Disabling it makes the problem go away, but then 3D rendering is slow due to no acceleration.) I have version 10.3.2-1 of most of the mesa lib packages, 9.0.0-2 for libglu1-mesa. My graphics card is an NVIDIA Quadro FX 3800, and I have the NVIDIA drivers installed on the host. (Previously I had a Quadro FX 570, and the behavior was exactly the same with that card.) Everything else is working fine in this Linux guest.",abc123
14859,"updeted vbox and guestadd. to version 5, randomly stop working",Windows,VirtualBox 5.0.10,2015-11-23T13:45:37Z,2015-12-05T06:25:34Z,2015-12-05T06:25:34Z,"used firefox, randomly guest stop working, total blocking
note, I also work at host at same time and go to guest short times.
",Mjau
14870,Unable to Accept EULA On XP,Windows,VirtualBox 5.0.10,2015-11-26T21:12:14Z,2015-11-27T08:30:18Z,2015-11-27T08:30:18Z,"When I try to press any F keys, I can't. And because you need to press F8 to accept the XP EULA, I can't do that.",VirtualMan2000
14828,Windows XP resize problem after installing updates and enabling 3D acceleration,Windows,VirtualBox 5.0.10,2015-11-14T11:14:26Z,2015-11-19T14:36:17Z,2015-11-19T14:36:17Z,"There's currently a problem with XP Guest Additions, more specifically with the auto resize function.[[BR]]
If you enable 3D acceleration (or both 2D and 3D), after installing a certain update (I don't know which) the function gets glitched and every time you log in, after few seconds, all the screen goes black and you need to resize the VM window in a smaller size to make the image appear again (or go to fullscreen and exit).[[BR]]
Also, after you do so, if you resize the window in a bigger size, the ""new"" part of the screen appears black. Fullscreen is also affected.[[BR]]
Both XP Pro, XP Pro x64 and even Ice XP (v6) are affected.[[BR]]
In the log I start up the Ice XP VM with 3D acceleration only, wait for the glitch, resize the window and shutdown.",Zacchi4k
14836,Caps-lock cannot be intercepted,Windows,VirtualBox 5.0.10,2015-11-16T16:35:18Z,2015-11-16T16:35:18Z,2015-11-16T16:35:18Z,"I use vim and various vim modes a lot. For this reason, one of the first things I usually do on my host machine is rewire caps-lock to the escape key using AutoHotKey on my host machine.

This worked just fine until the recent update. Every time I would press caps-lock it would be interpreted as an escape everywhere. 

After upgrading to 5.0.10 however, *inside the VM* it interprets caps-lock as both hitting escape *and* hitting caps-lock. This means, that every time I hit it, my vim flips into a bizarre mode where it does unexpected things with every key stroke. It would be one thing if it wasn't interpreted as escape at all but its interpreted as *both*.

So in order to get the intended behavior, I have to hit caps-lock *an even number of times*. However if, I only hit it an odd number of times, things start jumping around all over (because vim in caps lock mode is no fun).

Guest/Host: both on windows 8.1",gmauer
14803,E_FAIL (0x80004005) Critical Error on Windows 10 (Build 1240),Linux,VirtualBox 5.0.10,2015-11-11T10:36:24Z,2015-11-11T10:36:24Z,2015-11-11T10:36:24Z,"I can't run VM session with Comodo Internet Security installed on my PC. (CIS 8.2.0.4703). 


{{{
The virtual machine 'name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\User\VirtualBox VMs\name\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

}}}
",netak
15019,Unable to create Host-Only Network in Windows 10,all,VirtualBox 5.0.12,2016-01-09T14:28:44Z,2018-01-19T22:32:40Z,2018-01-19T22:32:40Z,"I was unable to create host-only network in Windows 10 Home Single Language using {{{VBoxManage hostonlyif create}}} with following output:

{{{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}
",rkurniawan
14978,Error In supR3HardNtChildWaitFor,Linux,VirtualBox 5.0.12,2015-12-26T14:09:49Z,2017-12-22T06:27:04Z,2017-12-22T06:27:04Z,"Hello,
I get this error on startup since 5.0.8 (also on .10 and .12).
Key Host Info:
- Lenovo x250 16GB RAM, 512 SSD
- Host win7 (latest patches some win10 upgrade stuff suppressed)
- guests: debian (but probably irrelevant)
- avira antivir antivirus
- comodo firewall

When I start vbox, after a while I get the following error:
---------------------------
VirtualBox - Error In supR3HardNtChildWaitFor
Timed out after 60001 ms waiting for child request #1 (CloseEvents).
(rc=258)
where: supR3HardNtChildWaitFor
what:  5
Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)
---------------------------

If I do not close it and wait a while (another minute or so) I get it again, and then the guest opens just fine. See this bug description:
https://forums.virtualbox.org/viewtopic.php?t=64111&f=6#p301426 (way back from Oct 2014 and 4.3.18)
...it is essentially this. If I close any of the dialogs, then the guest does not open. Attached are the logs (from 5.0.10, I can recreate with .12 if desired) and a screenshot of the errors. The logs appear normal.

Thanks
Nils
",Nils
16816,8042/BIOS16 keyboard issues,other,VirtualBox 5.0.12,2017-06-06T13:02:08Z,2017-06-06T13:02:08Z,2017-06-06T13:02:08Z,"VB 5.0.12 keyboard for BIOS16 users (DOS etc) is not working good for two main reasons:
 a) modifiers keys (alt, shift, ctrl) are sticky or not detected
 b) spurios keys issued while no one key is pressed

2.
captured video: http://yadi.sk/d/Ibvjeu-03Jsfd7

video description:
i try to enter keys and try to edit the wrong one by pressing shift+cursor to block mark
- shift+cursor is not work, but instead i got
- some entered keys lost
- sometimes shift is switched ON without my will and begun to produce block selection when i enter text
- at last shift state of the DOS program and the shift state of real host keyboard lost sync

3.
i guess VBox 8042 emulated part or BIOS16 is not compatible with AT-386 existing software, 8042 can not be detected or 8042/BIOS16 can not be used by the software as needed

more decription of error is in forum here:
http://forums.virtualbox.org/viewtopic.php?p=394494#p394494

PS:
Advise me to install new version of VBox if only the keybord code in new version of VBox was really rewritten ",dldall
14946,WiFi problem at user logon,all,VirtualBox 5.0.12,2015-12-19T04:48:06Z,2016-03-05T14:18:19Z,2016-03-05T14:18:19Z,"Starting from version 10.0.8, I have a very weird problem with WiFi connection at logon. The connection appears good as normal, but actually it is not and no internet connections can be made.

I have to disconnect and reconnect to get network working. This happens verytime I logon my account - with one exception.

The exception is - Everyday in the morning I power on my computer, it works as normal; but after that during the day, even a cold reboot would not work.

My system is Windows 10 (build 10586).
",Edward Yang
14947,Error message when logging off,all,VirtualBox 5.0.12,2015-12-19T04:53:17Z,2016-03-05T06:16:04Z,2016-03-05T06:16:04Z,"If I have VB running (not VM) and log off, I get the following error:

[https://forums.virtualbox.org/viewtopic.php?f=1&t=74113#p343094]
",Edward Yang
14961,"Windows 10 Guest: ""vboxvideow8"" is stopped on login, screen resolution drops",Windows,VirtualBox 5.0.12,2015-12-22T08:27:47Z,2016-03-04T18:30:52Z,2016-03-04T18:30:52Z,"This is similar to #14957 but it still happens with VirtualBox 5.0.12

When starting the VM, the guest (Windows 10/1511) shows the start sreen in the expected screen resolution.[[BR]]
After clicking on screen to get the login fields (user name and password), the screen resolution drops to 1024*768 - after the login it can be increased somewhat, but the automatic adjustment of the guest does not work.[[BR]]
In the system log is an entry that ""VBoxVideoW8"" does not respond anymore and was deactivated by Windows.
",Feuerfloh
14962,USB devices do not show up in VM,other,VirtualBox 5.0.12,2015-12-22T13:22:00Z,2016-03-01T17:21:14Z,2016-03-01T17:21:14Z,"Host OS: Windows 8.1 x64
VirtualBox 5.0.12

When I try to attach a USB device into VM it seems to get ""stuck"" or locked. When I click Devices->USB->My device (USB flash stick), I see it disappearing in the host OS, but it never appears in the guest OS (checked via dmesg: no messages at all about any new USB attachments). When I open that USB submenu again and hover my device, the tooltip tells that it is now ""Captured"", but there is no checkbox near the device name (which would indicate that the USB device is attached to the guest), and when I run VBoxManage showvminfo, it tells that there are no currently attached USB devices.

If I try to click the same device again, I get the error message that the device ""is busy with a previous request"". If I remove the device physically and reinsert it into another USB port, it appears in the USB menu as a new instance (while the previous one, the ""Captured"", remains there as well). However, clicking this new instance leads to absolutely the same behaviour: the device disappears from the host, never appears in the guest and remains forever locked in the ""Captured"" state.",Konstantin Vlasov
15042,Can't attach USB device Microchip MPLAB Real Ice,Windows,VirtualBox 5.0.12,2016-01-18T09:09:23Z,2016-01-28T16:55:18Z,2016-01-28T16:55:18Z,"Failed to attach Microchip MPLAB Real Ice to the VM Windows XP SP3

USB device 'Microchip Technology, Inc. (www.microchip.com) MPLAB® REAL ICE tm (www.microchip.com)' with UUID {30576387-492f-41fa-862e-c9b593202bde} is busy with a previous request. Please try again later.
Codice 'uscita: 
E_INVALIDARG (0x80070057)
Componente: 
HostUSBDeviceWrap
Interfaccia: 
IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
 ",Attylus76
15044,"WebGL doesn't work, OpenGL shows warnings",Linux,VirtualBox 5.0.12,2016-01-19T21:01:39Z,2016-01-19T21:01:39Z,2016-01-19T21:01:39Z,"Hello all,

I've been trying to use WebGL in a VirtualBox VM. It doesn't work in Firefox and Chrome (and probably others). In general, OpenGL seems to be having issues and is printing alot of warnings and errors.

3D acceleration is turned on. If I turn it off, WebGL works and I don't see all the warnings. But it's unusable. It's very, very slow.

{{{
tperkins@ubu1510vm:~$ firefox
pci id for fd 55: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

The host is Windows 10 64-bit, the guest in Ubuntu 15.10 64-bit. VirtualBox is 5.0.12 (r104815). I also tested a few other guests, and they all had this issue: Ubuntu 15.10 32-bit, Ubuntu 14.04 64-bit, Xubuntu 15.10 64-bit.

Things like `glxgears` are working, but they are showing identical warnings and errors. Hopefully that helps reproduce the issue.

{{{
tperkins@ubu1510vm:~$ glxgears
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
221 frames in 5.0 seconds = 44.191 FPS
289 frames in 5.0 seconds = 57.745 FPS
285 frames in 5.0 seconds = 56.949 FPS
}}}",tprk77
15041,Video not responding,Windows,VirtualBox 5.0.12,2016-01-18T08:53:42Z,2016-01-18T08:53:42Z,2016-01-18T08:53:42Z,"Hello,
I have an Acer Aspire aspire vn7-792g with windows 10.
I have installed virtualbox with windows 7 inside, I have installed guest addition and enabled 2d and 3d video acceleration.
After installing guest addition, my acer has a critical problem on display, if it turns off (power saving), the video does not respond.
I must power off the computer, otherwise my display remains black, even if virtualbox is not running.

",matteo
15026,VB Crashes after creating a machine,Linux,VirtualBox 5.0.12,2016-01-11T15:30:08Z,2016-01-11T15:30:08Z,2016-01-11T15:30:08Z,VB Crashes after creating a machine and on startup if one machine is present. I've reinstalled VB and tried beta builds.,mysi
15013,Symbolic Links,other,VirtualBox 5.0.12,2016-01-06T18:48:19Z,2016-01-10T01:09:00Z,2016-01-10T01:09:00Z,"VirtualBox 5.0.12 is erasing Symbolic Links after installation.

Never thought by simply installing VirtualBox something like this would happen. I don´t have a vbox.log because I just installed it successfully (VBox didn't crash)",Henrique Madson
15017,I get black screen after log out desktop environment.,Linux,VirtualBox 5.0.12,2016-01-09T04:31:46Z,2016-01-09T04:31:46Z,2016-01-09T04:31:46Z,"Host OS: WES7 SP1, OS X 10.11[[BR]]
Guest OS: Arch Linux


Reproduce process:[[BR]]
1) Set ""CustomVideoMode1"" value to ""1280x800x32"".[[BR]]
2) Start VM. Config guest OS to automatic login to virtual console and autostart X at login using xinit according to https://wiki.archlinux.org/index.php/Automatic_login_to_virtual_console and https://wiki.archlinux.org/index.php/Xinitrc#Autostart_X_at_login. [[BR]]
3) Set the value of ""GRUB_GFXMODE"" of /etc/default/grub file to ""1280x800x32"".[[BR]]
4) Run command ""grub-mkconfig -o /boot/grub/grub.cfg"".[[BR]]
5) Poweroff guest OS and start VM again. At the grub selection OS UI, the resolution of VM screen is 1280x800. Before desktop environment start, the information of systemd showing is fine. My desktop environment is Cinnamon or Mate.[[BR]]
6) Log out Cinnamon or Mate back to tty. I get black screen.[[BR]]
6.1) I didn't know what status of VM, so I clicked Close button on the VM title bar. After close dialog showed up, the black screen disappear, the information of tty can be seen.[[BR]]
6.2) I clicked Cancel button of the close dialog. the black screen came back.",SuperDiver
14973,Shared clipboard does not allow to copy files with ctrl-c - ctrl-v,Windows,VirtualBox 5.0.12,2015-12-23T13:51:10Z,2016-01-08T17:13:49Z,2016-01-08T17:13:49Z,"I tried to copy files via cliboard in VMware and it does it easily.
In VirtualBox copying files via clipboard does not work.",i8329
14988,Starting 2nd instance takes too much time,all,VirtualBox 5.0.12,2015-12-29T10:35:43Z,2016-01-08T07:26:42Z,2016-01-08T07:26:42Z,"Starting VB for the first time usually takes only less than 1 second on my computer (Windows 10 with SSD drive). But starting the 2nd instance would always take almost 5 seconds or more. That is not normal.

BTW, this problem has been there for years since I started using VB of 3.x.",Edward Yang
15007,installing virtualbox on windows 10 version 1511 throws VERR_SHARING_VIOLATION,other,VirtualBox 5.0.12,2016-01-05T04:59:25Z,2016-01-05T14:20:07Z,2016-01-05T14:20:07Z,"so yea, just downloaded the latest version of virtualbox, and tried installing it, got the installer to run correctly only to try restarting the installer process from process explorer (due to installer not doing anything at all possibly due to windows issue yet to be discovered or pinpointed) and now upon the thing restarting, it throws that error, and no matter how many times I redownload the installer, it throws this error every time....even if I delete the file from all existance and redownload it, it still throws said error.",mmd123
14971,Dragging from Windows 10 guest to Windows 10 host does not work,Windows,VirtualBox 5.0.12,2015-12-23T13:37:44Z,2016-01-04T12:50:19Z,2016-01-04T12:50:19Z,"Sometimes it works.

Sometimes, when I drag from guest to host nothing happens and when I try to delete the file I dragged, I get error message (see VB-screenshot-1.jpg).",i8329
14966,Dragging folder with several files from host to guest works partially,Windows,VirtualBox 5.0.12,2015-12-22T18:42:29Z,2016-01-04T11:41:16Z,2016-01-04T11:41:16Z,"When I drag folder containing several files from host to guest, VirtualBox copies the folder and one file, while all other files except the first one are not copied.",i8329
14949,Drag and drop inside guest doesn't work after installing Guest Additions,Windows,VirtualBox 5.0.12,2015-12-19T12:29:26Z,2016-01-04T10:52:02Z,2016-01-04T10:52:02Z,"I have been testing Virtualbox for some months and it works really great, very good job guys!
But I have found a strange issue, and can't find a solution here.
Last days I am testing VBox with windows 7 (64bit) embedded guests.
In my latest builds, everything works fine until I install Guest Additions, then drag and drop (in windows explorer and desktop) stops working completely in guest. If I uninstall Guest Additions then it starts working again. 
Also I get some errors trying to run some exe files (mainly installers) from host shares. But if I copy the directory to my desktop or some network share, then the same installers work just fine.
It happens with v. 5.0.10 and also with latest 5.0.12 (with their respective Guest Additions versions), I'll try with older/stabler versions.
I haven't had these problems with Windows 7/8 guests, maybe something related with Windows Embedded. If I install that same image to a real computer, drag and drop works just fine.
Any ideas of what might be happening?
My host has Windows 8.1.
Please see log attached.
You can see the thread I opened in forum here:
https://forums.virtualbox.org/viewtopic.php?f=2&t=75253&p=349185#p349185

Thanks in advance!",ramoncio
14994,Can't enable/disable a Virtual Screen when in full-screen mode,Windows,VirtualBox 5.0.12,2015-12-30T21:39:43Z,2015-12-30T21:39:43Z,2015-12-30T21:39:43Z,"I have a VM with monitor count set to two in Settings > Display. I have two physical monitors.

When I'm not in full-screen mode in the View > Virtual Screen 2 menu I see the Enable command in that menu and can check or uncheck it to enable or disable the second VM screen as desired.

But in full-screen mode when I go to the View > Virtual Screen 2 menu the Enable command is not shown.

Not sure if this is a defect or enhancement.  

Some background: I disabled the second screen about a week ago as this is a laptop and I was traveling with it and today I was back in the office and wanted to enable it again and couldn't figure it out.  I was toggling between ""Use Host Screen 1"" and ""Use Host Screen 2"" trying to get the second screen to show. This is something I don't do often. ",Wes Manning
14974,Windows 10 /Solaris:Linux or Windows Guest,all,VirtualBox 5.0.12,2015-12-24T12:41:32Z,2015-12-24T16:21:13Z,2015-12-24T16:21:13Z,"The guest, whatever version windows, linux or solaris will work for a few weeks then fail, I have to restart the PC change some ethernet adapter property usually I toggle ipv6 enabled and then virtualbox guest starts ok. This cycle repeats

The log that shows the issue seems to reference two c++ files. 

I had put this one the forum, but I placed in the wrong sub-forum, Windows 10 Guest. The moderator suggested this was incorrect and moved to a Solaris guest.
",matdave
14964,Shared clipboard does not work every second time,Windows,VirtualBox 5.0.12,2015-12-22T17:33:25Z,2015-12-22T17:33:25Z,2015-12-22T17:33:25Z,"It starts working after restart. So, I regularly have to start virtual machine and then restart it to get it work. Log attached.",i8329
14948,"""Auto-resize guest display"" feature unstable",Windows,VirtualBox 5.0.12,2015-12-19T08:41:43Z,2015-12-20T09:15:09Z,2015-12-20T09:15:09Z,"I am talking about this feature:
https://ma.ttias.be/auto-resize-screen-size-windows-10-guest-vms-virtualbox/

I am running Windows 10 guest under Windows 10 host.

After I start virtual machine:
Guest display is autoresized, but ""Auto-resize guest display"" checkbox inside top menu bar is disabled (greyed).

After I login to my Windows account on guest system:
""Auto-resize guest display"" checkbox is enabled, but it does not do anything. I would expect that when I uncheck this checkbox guest display would toggle to fixed size and when I check it guest display would toggle to flexible size. However, this does not happen. Guest display does not react to checking/unchecking ""Auto-resize guest display"" checkbox.

If I click on ""Resize to ..."":
Guest display toggles to fixed size, however ""Auto-resize guest display"" checkbox remains checked. So, checkbox does not reflect current state of guest display. Next, to return to flexible size I need to click on checkbox twice: the first click will uncheck checkbox and the second click will check checkbox and return display to flexible size.

For me it would be logical if:
""Auto-resize guest display"" option would move to the same menu with ""Resize to ..."". Then I would have: ""640x480 resolution"", ""800x600 resolution"", ..., ""Auto-resize guest display"". Then only one option can be enabled at the same time. Current situation when I can have ""640x480 resolution"" and ""Auto-resize guest display"" enabled at the same time is against the logic. The screen can't have two different sizes at the same time.

But most important issue is:
After some time ""Auto-resize guest display"" features breaks, guest display toggles back to fixed size and does not react to ""Auto-resize guest display"" checkbox any more. I have to reboot to toggle flexible display size on. This happens occasionally. I suspect that this may happen when host system goes to sleep mode or other kind of waiting mode, but I can't say for sure.",i8329
15060,Can't start virtual machine with bridged interfaces,all,VirtualBox 5.0.14,2016-01-21T12:37:02Z,2022-09-28T19:15:41Z,2022-09-28T19:15:41Z,"When resuming a saved virtual machine, I get the message:

{{{
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

This is on Windows 10.0.10586, but didn't start when upgrading to this version... I've been using Virtualbox fine for the last couple of weeks until this morning.

I did some searching and it seems that others were able to resolve the same issue by enabling the 'VirtualBox NDIS6 Bridged Networking Driver' for their network adapters, but I checked each adapter and it's already enabled for them all.

The virtual machine logs contain:

{{{
00:00:03.187772 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.187821 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187846 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:03.187879 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187883 VMSetError: Failed to attach the network LUN
00:00:03.187893 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:03.190010 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.197890 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.204536 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.211773 GIM: KVM: Resetting MSRs
00:00:03.341518 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:03.341550 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:03.341693 Console: Machine state changed to 'PoweredOff'
00:00:03.352282 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
}}}",Sam Morris
15144,BSOD - Windows 10 host VBoxNetLwf.sys,Windows,VirtualBox 5.0.14,2016-02-12T16:56:54Z,2021-03-31T21:56:18Z,2021-03-31T21:56:18Z,"I have had a handful of intermittent Windows 10 'blue screen of death' host crashes of type PAGE FAULT IN NONPAGED AREA which mention VBoxNetLwf.sys over the last few weeks. This has been observed with multiple minor releases of VirtualBox since version 5.0 and multiple releases of Windows 10 Professional. 

I suspect this may not be a VirtualBox bug and more likely an issue with our security software (Symantec Endpoint Protection) or the host Windows OS (as I only noticed this issue since updating from Win 8.1 Pro). 

Happy to provide any more info that might help, attached a screen grab of the crash. ",kpm
15193,"Errors when I start a virtual machine (Virtual Box Version 5.0.14 r105127, Windows 8 - 64 bit)",all,VirtualBox 5.0.14,2016-03-02T10:40:25Z,2020-07-02T11:48:06Z,2020-07-02T11:48:06Z,"I installed Virtual Box Version 5.0.14 r105127 on Windows 8 - 64 bit

An error dialog appears when I start a virtual machine.
The error message is:


{{{
Failed to open a session for the virtual machine MacOSXYO.

The virtual machine 'MacOSXYO' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\haipv87\VirtualBox VMs\New group\MacOSXYO\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
}}}


The error log is with content:

{{{
f18.940: supR3HardNtViCallWinVerifyTrustCatFile: WinVerifyTrust => 0x0; cat='C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-SKU-Foundation-Package-avcore~31bf3856ad364e35~amd64~~6.2.9200.16384.cat'; file='\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: supR3HardNtViCallWinVerifyTrustCatFile -> 0 (org 22900)
f18.940: supR3HardenedWinVerifyCacheProcessWvtTodos: 0 (was 22900) fWinVerifyTrust=1 for '\Device\HarddiskVolume2\Windows\System32\winmmbase.dll'
f18.940: Fatal error:
f18.940: supR3HardenedMainGetTrustedMain: LoadLibrary ""C:\Program Files\Oracle\VirtualBox/VirtualBox.dll"" failed, rc=1790
618.c3c: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 984 ms, the end);
fb0.f10: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1350 ms, the end);
}}}


I found some people has the similar problem, but all suggestion not work with my case.

Best Reguard.
",haiphungvan
15050,Can not connect USB Stick to VM,Linux,VirtualBox 5.0.14,2016-01-20T10:45:10Z,2020-05-25T18:09:52Z,2020-05-25T18:09:52Z,"How to reproduce:
Starting VM. Plugging in USB Stick. After this the following message appears:

Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",Uti
15174,Fresh install of windows 10 stops responding (repeatable).,Windows,VirtualBox 5.0.14,2016-02-23T19:48:20Z,2019-02-25T17:36:04Z,2019-02-25T17:36:04Z,"Windows 10 guest stops responding after leaving it run in the background.  It may have something to do with how windows 10 sleeps or hibernates.   Maybe something to do with the power settings and how it lets hard disks spin down or other such things.   The screen looks fine (not black).  The mouse doesn't move.  It doesn't respond to Ctrl-Alt-Delete.   It doesn't respond to “Send the shutdown signal”.   Sending the “Power off the machine” does close the box and restarting it doesn't give me the options for safe more like windows 7 did.  

Running on Windows 7 Ultimate Host.",isgdre
15084,Scale Factor Causes Malfunction of USB Multi-Touch Tablet in Debian-Based Linux,Linux,VirtualBox 5.0.14,2016-01-28T06:18:18Z,2017-10-15T18:45:26Z,2017-10-15T18:45:26Z,"I just acquired a Surface Book that has a high resolution touchscreen interface. Enabling the USB Multi-Touch Tablet interface, touches register correctly in the guest only when the Scale Factor is set to 100%.

When the Scale Factor is set to 200%, the upper-left quarter of the screen registers input for the entire render and the other three quarters register nothing at all.

For example, with the Scale Factor set to 200%, I can register a click on the Menu button in the lower-left corner of the screen by tapping on a point just above the center of the left edge of the screen. Tapping directly on the Menu button registers nothing.

It's easy to see this bad behavior as well by running `xinput test 11` and dragging a finger around the screen. With the Scale Factor set to 200%, it's pretty clear where the events register and where they stop registering.

I retested on build 105205 and this hasn't been miraculously fixed. Running LMDE 2 (Mate) or Debian (Gnome), the result is the same.",bazald
15181,Video Capturing broken within guest systems with 3D enabled,Linux,VirtualBox 5.0.14,2016-02-26T16:55:37Z,2016-09-26T14:29:44Z,2016-09-26T14:29:44Z,"NOTE: This refers to capturing video from WITHIN the guest, and does NOT refer to VirtualBox's ""video capture"" capability, which seems to work fine (but with no sound, by design)

I am trying to record (a portion of) my desktop along with my audio into a video file, from the client OS. In the past I've used two different tools to do this, either [http://www.maartenbaert.be/simplescreenrecorder/ SimpleScreenRecorder] (great for recording only a portion of the screen) and [http://www.videolan.org/ VLC] (full-screen only).

With 3D Acceleration DISABLED in the VBox settings, the applications work as expected. For example, simplescreenrecorder can preview and record what is on the screen with no problems. Of course, CPU usage is considerably higher for most simple operations.

With 3D Acceleration ENABLED in the VBox settings, the applications appear to run correctly, with no errors reported in any logs, however the preview and recordings are blank/black. Occasionally (not always reproducible) the recording is of the generic default Unity background/splash screen, with the words Ubuntu 15.10 in the bottom left, even though this is NOT my selected window background.

I'm not sure if this is a bug, per se, or is a configuration issue.

This APPEARS similar to the problem reported [https://forums.virtualbox.org/viewtopic.php?f=3&t=75795&p=352596&hilit=video+recording here], but everything else 3D appears to work OK. For example, glxgears runs fine and gets about 450 FPS. I do not use any specific 3D apps, however the user interface (Unbuntu Unity) has serious performance issues without basic 3D support...

Other than downgrading VirtualBox to lower than 4.3.28 as had been suggested in the linked forum post, is there a configuration that would enable video capture from within the client OS?

Host: Windows 10
Guest: Ubuntu 15.10

{{{
$ uname -r
4.2.0-30-generic
}}}

{{{
$/usr/lib/nux/unity_support_test -p 
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL vendor string:   Humper
OpenGL renderer string: Chromium
OpenGL version string:  2.1 Chromium 1.9

Not software rendered:    yes
Not blacklisted:          yes
GLX fbconfig:             yes
GLX texture from pixmap:  yes
GL npot or rect textures: yes
GL vertex program:        yes
GL fragment program:      yes
GL vertex buffer object:  yes
GL framebuffer object:    yes
GL version is 1.4+:       yes

Unity 3D supported:       yes
}}}

{{{
$ glxinfo
name of display: :0
pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: Chromium
server glx version string: 1.3 Chromium
server glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
client glx vendor string: Chromium
client glx version string: 1.3 Chromium
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
GLX version: 1.3
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, 
    GLX_EXT_texture_from_pixmap, GLX_SGIX_fbconfig
OpenGL vendor string: Humper
OpenGL renderer string: Chromium
OpenGL version string: 2.1 Chromium 1.9
OpenGL shading language version string: 4.40
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, 
    GL_ARB_fragment_shader, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object, 
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shader_objects, 
    GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shadow, 
    GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_compression, GL_ARB_texture_cube_map, 
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine, 
    GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, 
    GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, 
    GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, 
    GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, 
    GL_ATI_texture_mirror_once, GL_CR_bounding_box, GL_CR_cursor_position, 
    GL_CR_head_spu_name, GL_CR_performance_info, GL_CR_print_string, 
    GL_CR_readback_barrier_size, GL_CR_saveframe, GL_CR_server_id_sharing, 
    GL_CR_server_matrix, GL_CR_state_parameter, GL_CR_synchronization, 
    GL_CR_tile_info, GL_CR_tilesort_info, GL_CR_window_size, 
    GL_EXT_blend_color, GL_EXT_blend_equation_separate, 
    GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_compiled_vertex_array, GL_EXT_draw_range_elements, 
    GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_object, 
    GL_EXT_multi_draw_arrays, GL_EXT_secondary_color, GL_EXT_shadow_funcs, 
    GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, 
    GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, 
    GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, 
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
    GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
    GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, 
    GL_IBM_texture_mirrored_repeat, GL_NV_texgen_reflection, 
    GL_SGIS_generate_mipmap, GL_SGIS_texture_edge_clamp
}}}

{{{
$ cat /var/log/Xorg.0.log
[    48.883] 
X.Org X Server 1.17.2
Release Date: 2015-06-16
[    48.883] X Protocol Version 11, Revision 0
[    48.883] Build Operating System: Linux 3.13.0-68-generic x86_64 Ubuntu
[    48.883] Current Operating System: Linux redacted-VBox 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26 UTC 2016 x86_64
[    48.883] Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash
[    48.883] Build Date: 12 November 2015  05:33:29PM
[    48.883] xorg-server 2:1.17.2-1ubuntu9.1 (For technical support please see http://www.ubuntu.com/support) 
[    48.883] Current version of pixman: 0.32.6
[    48.883] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    48.883] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    48.883] (==) Log file: ""/var/log/Xorg.0.log"", Time: Fri Feb 26 08:22:28 2016
[    48.975] (==) Using system config directory ""/usr/share/X11/xorg.conf.d""
[    49.048] (==) No Layout section.  Using the first Screen section.
[    49.048] (==) No screen section available. Using defaults.
[    49.048] (**) |-->Screen ""Default Screen Section"" (0)
[    49.048] (**) |   |-->Monitor ""<default monitor>""
[    49.048] (==) No monitor specified for screen ""Default Screen Section"".
	Using a default monitor configuration.
[    49.048] (==) Automatically adding devices
[    49.048] (==) Automatically enabling devices
[    49.048] (==) Automatically adding GPU devices
[    49.120] (WW) The directory ""/usr/share/fonts/X11/cyrillic"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.120] (WW) The directory ""/usr/share/fonts/X11/100dpi/"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.120] (WW) The directory ""/usr/share/fonts/X11/75dpi/"" does not exist.
[    49.120] 	Entry deleted from font path.
[    49.129] (WW) The directory ""/usr/share/fonts/X11/100dpi"" does not exist.
[    49.129] 	Entry deleted from font path.
[    49.129] (WW) The directory ""/usr/share/fonts/X11/75dpi"" does not exist.
[    49.129] 	Entry deleted from font path.
[    49.129] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[    49.129] (==) ModulePath set to ""/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules""
[    49.129] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    49.137] (II) Loader magic: 0x560d34f1ed40
[    49.137] (II) Module ABI versions:
[    49.137] 	X.Org ANSI C Emulation: 0.4
[    49.137] 	X.Org Video Driver: 19.0
[    49.137] 	X.Org XInput driver : 21.0
[    49.137] 	X.Org Server Extension : 9.0
[    49.138] (II) xfree86: Adding drm device (/dev/dri/card0)
[    49.142] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/134217728
[    49.148] (II) LoadModule: ""glx""
[    49.303] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    49.540] (II) Module glx: vendor=""X.Org Foundation""
[    49.540] 	compiled for 1.17.2, module version = 1.0.0
[    49.540] 	ABI class: X.Org Server Extension, version 9.0
[    49.540] (==) AIGLX enabled
[    49.540] (==) Matched vboxvideo as autoconfigured driver 0
[    49.540] (==) Matched vboxvideo as autoconfigured driver 1
[    49.540] (==) Matched modesetting as autoconfigured driver 2
[    49.540] (==) Matched fbdev as autoconfigured driver 3
[    49.540] (==) Matched vesa as autoconfigured driver 4
[    49.540] (==) Assigned the driver to the xf86ConfigLayout
[    49.540] (II) LoadModule: ""vboxvideo""
[    49.540] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo_drv.so
[    49.557] (II) Module vboxvideo: vendor=""Oracle Corporation""
[    49.557] 	compiled for 1.17.0, module version = 1.0.1
[    49.557] 	Module class: X.Org Video Driver
[    49.557] 	ABI class: X.Org Video Driver, version 19.0
[    49.557] (**) Load address of symbol ""VBOXVIDEO"" is 0x7fdae5a3f340
[    49.557] (II) LoadModule: ""modesetting""
[    49.557] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    49.572] (II) Module modesetting: vendor=""X.Org Foundation""
[    49.572] 	compiled for 1.17.2, module version = 1.17.2
[    49.572] 	Module class: X.Org Video Driver
[    49.572] 	ABI class: X.Org Video Driver, version 19.0
[    49.572] (II) LoadModule: ""fbdev""
[    49.572] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    49.590] (II) Module fbdev: vendor=""X.Org Foundation""
[    49.590] 	compiled for 1.17.1, module version = 0.4.4
[    49.590] 	Module class: X.Org Video Driver
[    49.590] 	ABI class: X.Org Video Driver, version 19.0
[    49.590] (II) LoadModule: ""vesa""
[    49.590] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    49.593] (II) Module vesa: vendor=""X.Org Foundation""
[    49.593] 	compiled for 1.17.1, module version = 2.3.4
[    49.593] 	Module class: X.Org Video Driver
[    49.593] 	ABI class: X.Org Video Driver, version 19.0
[    49.593] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    49.593] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    49.593] (II) FBDEV: driver for framebuffer: fbdev
[    49.593] (II) VESA: driver for VESA chipsets: vesa
[    49.593] (++) using VT number 7

[    49.605] (WW) Falling back to old probe method for modesetting
[    49.605] (WW) Falling back to old probe method for fbdev
[    49.605] (II) Loading sub module ""fbdevhw""
[    49.605] (II) LoadModule: ""fbdevhw""
[    49.605] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    49.607] (II) Module fbdevhw: vendor=""X.Org Foundation""
[    49.607] 	compiled for 1.17.2, module version = 0.0.2
[    49.607] 	ABI class: X.Org Video Driver, version 19.0
[    49.607] (EE) open /dev/fb0: No such file or directory
[    49.607] (WW) Falling back to old probe method for vesa
[    49.607] (II) VBoxVideo(0): VirtualBox guest additions video driver version 5.0.15r105668
[    49.607] (II) Loading sub module ""ramdac""
[    49.607] (II) LoadModule: ""ramdac""
[    49.607] (II) Module ""ramdac"" already built-in
[    49.607] (II) Loading sub module ""fb""
[    49.607] (II) LoadModule: ""fb""
[    49.607] (II) Loading /usr/lib/xorg/modules/libfb.so
[    49.617] (II) Module fb: vendor=""X.Org Foundation""
[    49.617] 	compiled for 1.17.2, module version = 1.0.0
[    49.617] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.617] (II) Loading sub module ""shadowfb""
[    49.617] (II) LoadModule: ""shadowfb""
[    49.636] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[    49.637] (II) Module shadowfb: vendor=""X.Org Foundation""
[    49.637] 	compiled for 1.17.2, module version = 1.0.0
[    49.637] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.637] (II) Loading sub module ""vgahw""
[    49.637] (II) LoadModule: ""vgahw""
[    49.637] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[    49.652] (II) Module vgahw: vendor=""X.Org Foundation""
[    49.652] 	compiled for 1.17.2, module version = 0.1.0
[    49.652] 	ABI class: X.Org Video Driver, version 19.0
[    49.653] (II) Loading sub module ""dri2""
[    49.653] (II) LoadModule: ""dri2""
[    49.653] (II) Module ""dri2"" already built-in
[    49.653] (II) VBoxVideo(0): Creating default Display subsection in Screen section
	""Default Screen Section"" for depth/fbbpp 24/32
[    49.653] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[    49.653] (--) VBoxVideo(0): Virtual size is 32766x32766 (pitch 32766)
[    49.653] (**) VBoxVideo(0):  Built-in mode ""800x600"": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[    49.653] (II) VBoxVideo(0): Modeline ""800x600""x0.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    49.653] (**) VBoxVideo(0):  Built-in mode ""800x600"": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[    49.653] (II) VBoxVideo(0): Modeline ""800x600""x0.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    49.653] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0
[    49.653] (==) VBoxVideo(0): RGB weight 888
[    49.653] (==) VBoxVideo(0): Default visual is TrueColor
[    49.653] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[    49.653] (==) VBoxVideo(0): DPI set to (96, 96)
[    49.653] (II) UnloadModule: ""modesetting""
[    49.653] (II) Unloading modesetting
[    49.653] (II) UnloadModule: ""fbdev""
[    49.653] (II) Unloading fbdev
[    49.653] (II) UnloadSubModule: ""fbdevhw""
[    49.653] (II) Unloading fbdevhw
[    49.653] (II) UnloadModule: ""vesa""
[    49.653] (II) Unloading vesa
[    49.653] (--) Depth 24 pixmap format is 32 bpp
[    50.201] (II) VBoxVideo(0): [DRI2] Setup complete
[    50.201] (II) VBoxVideo(0): [DRI2]   DRI driver: vboxvideo
[    50.221] (II) VBoxVideo(0): Requested monitor count: 1
[    50.221] (II) VBoxVideo(0): Output VGA-0 has no monitor section
[    50.221] (II) VBoxVideo(0): Output VGA-0 has no monitor section
[    50.221] (II) VBoxVideo(0): Printing probed modes for output VGA-0
[    50.221] (II) VBoxVideo(0): Modeline ""1336x790""x60.0   64.09  1336 1338 1340 1342  790 792 794 796 (47.8 kHz Pb)
[    50.222] (II) VBoxVideo(0): Modeline ""2560x1600""x60.0  247.26  2560 2562 2564 2566  1600 1602 1604 1606 (96.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""2560x1440""x60.0  222.63  2560 2562 2564 2566  1440 1442 1444 1446 (86.8 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""2048x1536""x60.0  190.04  2048 2050 2052 2054  1536 1538 1540 1542 (92.5 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1920x1600""x60.0  185.59  1920 1922 1924 1926  1600 1602 1604 1606 (96.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1920x1080""x60.0  125.50  1920 1922 1924 1926  1080 1082 1084 1086 (65.2 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1600x1200""x60.0  116.21  1600 1602 1604 1606  1200 1202 1204 1206 (72.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1680x1050""x60.0  106.82  1680 1682 1684 1686  1050 1052 1054 1056 (63.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1400x1050""x60.0   89.08  1400 1402 1404 1406  1050 1052 1054 1056 (63.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1280x1024""x60.0   79.47  1280 1282 1284 1286  1024 1026 1028 1030 (61.8 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""1024x768""x60.0   47.83  1024 1026 1028 1030  768 770 772 774 (46.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""800x600""x60.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    50.222] (II) VBoxVideo(0): Modeline ""640x480""x60.0   18.84  640 642 644 646  480 482 484 486 (29.2 kHz b)
[    50.222] (II) VBoxVideo(0): Output VGA-0 connected
[    50.222] (II) VBoxVideo(0): Using exact sizes for initial modes
[    50.222] (II) VBoxVideo(0): Output VGA-0 using initial mode 1336x790
[    50.222] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    50.222] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    50.229] (==) VBoxVideo(0): DPMS enabled
[    50.229] (--) RandR disabled
[    50.240] (II) SELinux: Disabled on system
[    50.362] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[    50.362] (II) The file referenced, is *NOT* loaded
[    50.362] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[    50.362] (EE) AIGLX error: vboxvideo does not export required DRI extension
[    50.362] (EE) AIGLX: reverting to software rendering
[    51.108] (II) AIGLX: Loaded and initialized swrast
[    51.108] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    51.109] (II) VBoxVideo(0): Setting screen physical size to 353 x 209
[    51.346] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    51.371] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    51.371] (**) Power Button: Applying InputClass ""evdev keyboard catchall""
[    51.371] (II) LoadModule: ""evdev""
[    51.372] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    51.407] (II) Module evdev: vendor=""X.Org Foundation""
[    51.407] 	compiled for 1.17.1, module version = 2.9.2
[    51.407] 	Module class: X.Org XInput Driver
[    51.407] 	ABI class: X.Org XInput driver, version 21.0
[    51.407] (II) Using input driver 'evdev' for 'Power Button'
[    51.407] (**) Power Button: always reports core events
[    51.407] (**) evdev: Power Button: Device: ""/dev/input/event0""
[    51.407] (--) evdev: Power Button: Vendor 0 Product 0x1
[    51.407] (--) evdev: Power Button: Found keys
[    51.407] (II) evdev: Power Button: Configuring as keyboard
[    51.407] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0""
[    51.407] (II) XINPUT: Adding extended input device ""Power Button"" (type: KEYBOARD, id 6)
[    51.407] (**) Option ""xkb_rules"" ""evdev""
[    51.407] (**) Option ""xkb_model"" ""pc105""
[    51.407] (**) Option ""xkb_layout"" ""us""
[    51.407] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[    51.407] (**) Sleep Button: Applying InputClass ""evdev keyboard catchall""
[    51.407] (II) Using input driver 'evdev' for 'Sleep Button'
[    51.407] (**) Sleep Button: always reports core events
[    51.407] (**) evdev: Sleep Button: Device: ""/dev/input/event1""
[    51.408] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[    51.408] (--) evdev: Sleep Button: Found keys
[    51.408] (II) evdev: Sleep Button: Configuring as keyboard
[    51.408] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input1/event1""
[    51.408] (II) XINPUT: Adding extended input device ""Sleep Button"" (type: KEYBOARD, id 7)
[    51.408] (**) Option ""xkb_rules"" ""evdev""
[    51.408] (**) Option ""xkb_model"" ""pc105""
[    51.408] (**) Option ""xkb_layout"" ""us""
[    51.408] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
[    51.408] (**) Video Bus: Applying InputClass ""evdev keyboard catchall""
[    51.408] (II) Using input driver 'evdev' for 'Video Bus'
[    51.408] (**) Video Bus: always reports core events
[    51.408] (**) evdev: Video Bus: Device: ""/dev/input/event3""
[    51.408] (--) evdev: Video Bus: Vendor 0 Product 0x6
[    51.408] (--) evdev: Video Bus: Found keys
[    51.408] (II) evdev: Video Bus: Configuring as keyboard
[    51.408] (**) Option ""config_info"" ""udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input4/event3""
[    51.408] (II) XINPUT: Adding extended input device ""Video Bus"" (type: KEYBOARD, id 8)
[    51.408] (**) Option ""xkb_rules"" ""evdev""
[    51.408] (**) Option ""xkb_model"" ""pc105""
[    51.409] (**) Option ""xkb_layout"" ""us""
[    51.409] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event5)
[    51.409] (**) VirtualBox mouse integration: Applying InputClass ""evdev pointer catchall""
[    51.409] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[    51.409] (**) VirtualBox mouse integration: always reports core events
[    51.409] (**) evdev: VirtualBox mouse integration: Device: ""/dev/input/event5""
[    51.409] (--) evdev: VirtualBox mouse integration: Vendor 0x80ee Product 0xcafe
[    51.409] (--) evdev: VirtualBox mouse integration: Found 1 mouse buttons
[    51.409] (--) evdev: VirtualBox mouse integration: Found absolute axes
[    51.409] (--) evdev: VirtualBox mouse integration: Found x and y absolute axes
[    51.409] (--) evdev: VirtualBox mouse integration: Found absolute touchscreen
[    51.409] (II) evdev: VirtualBox mouse integration: Configuring as touchscreen
[    51.409] (**) evdev: VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[    51.409] (**) evdev: VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    51.409] (**) Option ""config_info"" ""udev:/sys/devices/pci0000:00/0000:00:04.0/input/input6/event5""
[    51.409] (II) XINPUT: Adding extended input device ""VirtualBox mouse integration"" (type: TOUCHSCREEN, id 9)
[    51.409] (II) evdev: VirtualBox mouse integration: initialized for absolute axes.
[    51.409] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[    51.409] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[    51.410] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[    51.410] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[    51.410] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event2)
[    51.410] (**) AT Translated Set 2 keyboard: Applying InputClass ""evdev keyboard catchall""
[    51.410] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    51.410] (**) AT Translated Set 2 keyboard: always reports core events
[    51.410] (**) evdev: AT Translated Set 2 keyboard: Device: ""/dev/input/event2""
[    51.410] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[    51.410] (--) evdev: AT Translated Set 2 keyboard: Found keys
[    51.410] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[    51.410] (**) Option ""config_info"" ""udev:/sys/devices/platform/i8042/serio0/input/input2/event2""
[    51.410] (II) XINPUT: Adding extended input device ""AT Translated Set 2 keyboard"" (type: KEYBOARD, id 10)
[    51.410] (**) Option ""xkb_rules"" ""evdev""
[    51.410] (**) Option ""xkb_model"" ""pc105""
[    51.410] (**) Option ""xkb_layout"" ""us""
[    51.411] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event4)
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass ""evdev pointer catchall""
[    51.411] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: Device: ""/dev/input/event4""
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Vendor 0x2 Product 0x6
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found relative axes
[    51.411] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[    51.411] (**) evdev: ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    51.411] (**) Option ""config_info"" ""udev:/sys/devices/platform/i8042/serio1/input/input5/event4""
[    51.411] (II) XINPUT: Adding extended input device ""ImExPS/2 Generic Explorer Mouse"" (type: MOUSE, id 11)
[    51.411] (II) evdev: ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[    51.411] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[    51.411] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[    51.411] (II) No input driver specified, ignoring this device.
[    51.411] (II) This device may have been added with another device file.
[   130.365] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   132.502] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   132.512] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   146.475] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
}}}

{{{
$ ls -al /usr/lib/xorg/modules/drivers | grep video
lrwxrwxrwx 1 root root      65 Feb 25 15:26 vboxvideo_drv.so -> /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/vboxvideo_drv_117.so
}}}

{{{
$ ls -al /opt/VBoxGuestAdditions-5.0.15/lib/VBoxGuestAdditions/
total 2096
drwxr-xr-x 2 root root   4096 Feb 23 10:02 .
drwxr-xr-x 3 root root   4096 Feb 23 10:02 ..
-rwxr-xr-x 1 root root   1401 Aug 31 10:12 98vboxadd-xclient
-rwxr-xr-x 1 root root  19152 Feb 23 10:02 mount.vboxsf
-rwxr-xr-x 1 root root 715272 Feb 23 10:02 pam_vbox.so
-rwxr-xr-x 1 root root  15796 Feb 23 10:01 vboxadd
-rwxr-xr-x 1 root root   4535 Feb 23 10:01 vboxadd-service
-rwxr-xr-x 1 root root  22252 Feb 23 10:01 vboxadd-x11
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_13.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_14.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_15.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_16.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_70.so
-rwxr-xr-x 1 root root  15136 Feb 23 10:02 vboxmouse_drv_71.so
-rw-r--r-- 1 root root   9056 Feb 23 10:02 vboxmouse_drv.o
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_110.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_111.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_112.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_113.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_114.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_115.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_116.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_117.so
-rwxr-xr-x 1 root root  61912 Feb 23 10:02 vboxvideo_drv_118.so
-rwxr-xr-x 1 root root  61648 Feb 23 10:02 vboxvideo_drv_13.so
-rwxr-xr-x 1 root root  61648 Feb 23 10:02 vboxvideo_drv_14.so
-rwxr-xr-x 1 root root  65928 Feb 23 10:02 vboxvideo_drv_15.so
-rwxr-xr-x 1 root root  65928 Feb 23 10:02 vboxvideo_drv_16.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_17.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_18.so
-rwxr-xr-x 1 root root  61904 Feb 23 10:02 vboxvideo_drv_19.so
-rwxr-xr-x 1 root root  53184 Feb 23 10:02 vboxvideo_drv_70.so
-rwxr-xr-x 1 root root  53184 Feb 23 10:02 vboxvideo_drv_71.so
-rw-r--r-- 1 root root  61728 Feb 23 10:02 vboxvideo_drv.o
-rwxr-xr-x 1 root root   4509 Aug 20  2015 x11config.sh
}}}



From HOST system, AMD's RADEON SETTINGS app reports the following

{{{

Radeon Settings Version - 2016.0203.1043.19267
Driver Packaging Version - 15.301.1801.1001-160203a-299103E
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1533
Direct3D® Version - 9.14.10.1171
OpenGL® Version - 6.14.10.13417
OpenCL™ Version - 2.0.4.0
AMD Mantle Version - 9.1.10.99
AMD Mantle API Version - Not Available
AMD Audio Driver Version - 10.0.0.2
}}}

VBox.Log and VBoxHardening.Log attached

",Michael
15165,"Leaving Full-Screen Mode resizes guest with ""Auto-resize Guest Display"" off",Windows,VirtualBox 5.0.14,2016-02-22T01:33:49Z,2016-06-24T15:15:27Z,2016-06-24T15:15:27Z,"In older versions (when Auto-resize Guest Display could be toggled with Host+G), this worked fine, but when this shortcut toggle was removed, this bug was introduced.

To reproduce:

1. Leave full-screen mode if necessary.
2. Enable ""Auto-resize Guest Display"".
3. Guest resolution should change to match window.  If not, resize the window.
4. Enter full-screen mode (Host+F).
5. Guest resolution should change to match host resolution.
6. Use Host+Home to disable ""Auto-resize Guest Display"".
7. Exit full-screen mode (Host+F).
8. Notice that the guest resolution changes to match the window, but it should not.
",Marc
15123,Bluescreen when starting Beckhoff TwinCAT PLC with activated VT-x,Windows,VirtualBox 5.0.14,2016-02-07T20:58:29Z,2016-06-18T13:39:06Z,2016-06-18T13:39:06Z,"With the VBox Version 5.0.10 and 5.0.14 the Windows 7 crashes with a bluescreen when the Beckhoff TwinCAT PLC 3.1 is started.
This happens on a 32 Bit Windows as Long as the VT-x Support is activated and allways on a 64 Bit Windows, because the VT-x Support coulkdn't be swithed off.
With VBox 5.0.4 the System doesn't Crash.",OTonn
15198,Virtualbox misses keypress isuued just after capture,Windows,VirtualBox 5.0.14,2016-03-03T19:22:51Z,2016-03-03T19:26:11Z,2016-03-03T19:26:11Z,"Whenever I switch to my guest, either using Alt+tab or just clicking with the mouse inside the guest window, the first and sometimes second keypresses are lost.
This only happens if the keypresses are sent very fast after switching
To reproduce:
Open notepad on guest
Place the mouse cursor inside the notepad window
Host should have focus
Click inside notepad and just as you do that, press 1 2 3 on the keyboard
If you're fast enough, 1 is lost 80-90 % of the time and 2 is lost 50 % of the time
This also happens if you alt+tab from host to the guest

Tested on two different hosts",noir04
15168,DOS batch file crashes on run attempt (Command Prompt Only) w98,other,VirtualBox 5.0.14,2016-02-22T22:17:09Z,2016-02-22T22:17:09Z,2016-02-22T22:17:09Z,"I can successfully boot to Windows 98 or DOS but cannot get a DOS application to run; which is the goal of virtualizing this system.

1) Start Windows 98 VPC
2) Boots to Microsoft Windows 98 Startup Menu
3) (Select) 5. Command prompt only (Enter)
4) C:\>

SO FAR, ALL IS WELL...
5) Type Start (start.bat) and Enter
c:\>start (enter)
6) Crash!

",Big B Creations
15132,Problems getting native resolution on Windows 10,Linux,VirtualBox 5.0.14,2016-02-09T21:24:04Z,2016-02-16T19:06:25Z,2016-02-16T19:06:25Z,"This ticket concerns how to get native resolution in the Virtualbox graphical frontend when running under a Windows 10 host.

By ""native resolution"", I mean a 1-1 mapping between pixels on the display and pixels in the frontend fullscreen window.

My setup is a laptop with a 2736x1824 screen. Connected to this, I have an external monitor with a 2560x1440 resolution.

The behavior I expect from the frontend is that I always get native resolution when I select a scale factor of 100% in the View menu.

The behavior I get is somewhat complicated. It seems like there are two states: I either get native resolution on the laptop monitor or the external monitor. The switch between these two states goes through Windows display settings:

Assume that we have everything working as expected on the laptop display, with native resolution in the Virtualbox frontend.

Now we connect the external monitor and choose to use only that monitor. When we now select fullscreen in the frontend we only get some scrambled rectangles on the screen. However, if we go from a scale factor of 100% to 125%, we get a screen with proper content, but with a high resolution (higher than the display) from the point of view of the guest, scaled down to fit the display.

Going now to Windows display settings, there is a red sentence saying that we need to sign out in order for all apps to adjust to the new scaling (resolution?). Doing that and restarting the guest and the graphical frontend, we now get (for a 100% frontend scale factor) native resolution.

The same thing happens again when going back to the laptop display.

This is clearly a bug since one shouldn't have to save the machine state, sign out and in again, and restart the vm for every monitor switch. I wish there was a way for Virtualbox to ignore the Windows weirdness and simply have a hard mapping between 100% scale factor and native resolution.

I attach a log from a run where I fail to get native resolution on my laptop display (but do get it on the external monitor).",Mikael Djurfeldt
15151,Ubuntu on VirtualBox crashes when laptop goes to hibernate,Linux,VirtualBox 5.0.14,2016-02-15T13:38:42Z,2016-02-15T13:38:42Z,2016-02-15T13:38:42Z,"

I am running VirtualBox 5.0.14 on Windows 10. I am running Ubuntu Desktop (I tried 14.04, 15.10 and 16.04 (pre release)) in my VirtualBox environment. When my laptop goes to hibernate the Ubuntu session crashes with the following error:

http://imgur.com/74PYXBN

In case image is not available, the error is:

    The instruction at 0x00007FF92F74E80B referenced memory at 0x0000000000000014. The memory could not be read.

I installed the latest version of the Guest additions.

Reference to AskUbuntu question: http://askubuntu.com/questions/734867/ubuntu-on-virtualbox-crashes-when-laptop-goes-to-hibernate
",martijnburger
15147,Guest OS cannot see Host in Bridged Mode,Linux,VirtualBox 5.0.14,2016-02-13T05:45:37Z,2016-02-14T10:37:51Z,2016-02-14T10:37:51Z,"I have Windows 10 as a host system and Centos 6 as a guest system.
I am connection to internet by wireless
The issue is that bridged network adapter does not allow automatic ip configuration. So I have setup static ip to connect and the rare thing is the the guest system (centos) can get access to internet, can ping the gateway but cannot ping the host system, but the host system can ping the guest system.
",kecondezo
15141,Virtualbox and Avira,Windows,VirtualBox 5.0.14,2016-02-11T08:37:47Z,2016-02-11T08:37:47Z,2016-02-11T08:37:47Z,"Hi,

I want to report a problem with antiviruses, especially with Avira (that is my case).

VirtualBox (5.0.14 but also previous versions) worked fine until I installed Avira on my host pc (Windows 7 Pro x64).
Then it started to slow down and show this error:

Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap

The error appear also if the antivirus is disabled and creating exceptions in the real time protection doesn't work either.

If I uninstall Avira on my host pc, everything works fine again.
",Baboo85
15136,After upgrade Virtual Box 5.0.14 does not recognise USB Key,Linux,VirtualBox 5.0.14,2016-02-10T09:56:47Z,2016-02-10T09:56:47Z,2016-02-10T09:56:47Z,"I upgraded VB from version 4.3.18 and the USB Key that has been always recognized is not recognized anymore, tested with all of the versions of USB selected. The USB Key is a Kingston Data Travel with 16GB.

Thanks in advance.",PHOTON
15113,VBoxManage controlvm savestate fails on Windows Host,Windows,VirtualBox 5.0.14,2016-02-04T21:27:59Z,2016-02-05T09:41:16Z,2016-02-05T09:41:16Z,"'''Execute:'''[[br]]
{{{VBoxManage controlvm <vmname> savestate}}}

'''Displays:'''[[br]]
{{{VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)}}}[[br]]
{{{VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 101 of file VBoxManageControlVM.cpp}}}

The pause option also displays the same error message. Other options may produce the same error message.
This issue seems to have first appeared in Sept 2015, see https://forums.virtualbox.org/viewtopic.php?f=6&t=70975",Tim T ASP
15111,Unable to create a Virtual machine,Windows,VirtualBox 5.0.14,2016-02-04T10:57:21Z,2016-02-04T10:57:21Z,2016-02-04T10:57:21Z,"I am unable to create a for the first time a Virtual Machine .
After creating a Virtual machine call eWinXP  I click on the Machine and I get the following:
A small appeared  saying “You have the Auto capture”
A second message saying : “Creating process for for virtual machine eWinXP (GUI/QT)...(1/2)” and e progress bar with no Progress activity shown.(after 20 min) and no activity on the CD player.
He Mouse pointer shown the only activity.
I could not stop any running program . The only way I cuold regaing control of the computer is by using the “Task Manager”
The “Task Manager” show hat :
eWinXP (Power Off) and Oracle VM VitualBox  Running.
After closing both task the following ERROR message apeared:
Fail to open a session for virtual machine eWinXP
The VM sessuion was closed
Result Code : E_FAIL (0x8004005)
Component : SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
 a Copy of “VboxHardening” file attached  for your information.

I am using Windows 7 Enterprise on a HP Mini5102
 
Thank you for your help 
Ferruccio       






",Ferruccio
15045,corrections in OSE build,all,VirtualBox 5.0.14,2016-01-20T07:54:54Z,2016-01-30T18:30:29Z,2016-01-30T18:30:29Z,"1. Incorrect check of renamed variable (v4->v5): bug5man_ose.patch
2. Absent implib's: ose_st_ssl_web.patch
3. Incorrect check of non-standard latex place: pdf_ose.patch",yjh
15053,Genymotion Virtual Box Host Adapter not found,Windows,VirtualBox 5.0.14,2016-01-20T18:52:27Z,2016-01-28T10:43:45Z,2016-01-28T10:43:45Z,"Hello, i'm using last version 5.0.14 on Windows XP SP3 togheter with Genymotion. 
I write here because there is a virtualbox error and exactely :
The host network interface with the given name could not be found.

I've tried to delete all interface and when i open genymotion it recreate correctly virtual host adapter...

Thanks for helping",Dario Cdj
15083,Win 7 / Linux Guest - Cannot delete backup file on shared folder.,Linux,VirtualBox 5.0.14,2016-01-27T17:29:59Z,2016-01-27T17:29:59Z,2016-01-27T17:29:59Z,"When a backup~ file is created in a directory within a VirtualBox's shared folder, the program that created the backup~ file cannot remove the file preventing the original file from being saved. Trying to remove the backup~ file manually via 'rm' results in an 'Operation not permitted.' message. The only way to remove the backup~ file is navigating to the directory from the Host system and removing the file that way.",agilis
15079,Seamless mode : taskbar pinned app contextual menu only visible above guest window,Windows,VirtualBox 5.0.14,2016-01-26T13:41:16Z,2016-01-26T13:41:16Z,2016-01-26T13:41:16Z,"In seamless mode, the contextual menus for pinned apps are only painted when above a guest window.",Billy Braga
15059,Virtual box crash when host pc reboots,all,VirtualBox 5.0.14,2016-01-21T11:33:32Z,2016-01-21T14:17:55Z,2016-01-21T14:17:55Z,"tested using 5.0.14 on W7 / 64 , W10 32 & 64 bit.
Start Virtualbox, do not start any vm in virtual box
Reboot the host PC
Virtual box will stop the host pc from booting

The first error being displayed is ""Failed to set the global Virtualbox extra data for key GUI/Toolbar to value {}""

",Frank Bevers
15308,guest does not regain network connectivity if cable unplugged for for 5+ secs,Linux,VirtualBox 5.0.16,2016-04-14T10:49:47Z,2023-02-11T00:27:22Z,2023-02-11T00:27:22Z,"Host = Windows 10 Version 1151 (Build 10586.164)
Guest = CentOS7.2.1511 x86_64 (Kernel 3.10.0-327.el7.x86_64)

VirtualBox VM has 2 adapters
- 1 = Host-only Adapter (VirtualBox Host-Only Ethernet Adapter)
- 2 = Bridged Adapter (Intel Ethernet Connection I219-LM)

Networking functions 100% between the VM and LAN if I power on the VM with the Ethernet cable plugged in to the bridged interface (Intel Ethernet Connection I219-LM). The VM can communicate with my LAN and vice versa.

If I start a ping from within the Linux VM and disconnect the Ethernet cable from the bridged interface (Intel Ethernet Connection I219-LM) and plug it back in within 5 seconds, the ping picks back up where it left off.

If it takes more than 5 seconds for me to plug the cable back in, the ping does not pick back up and I need to shut down the VM and cold boot it in order to restore networking between the VM and LAN. Restarting the guest Linux networking, a VM reboot, or a disable/enable of all Windows' interfaces does not regain network connectivity to the Linux VM. Only a shutdown and cold boot of the VM.

I've tried the various ""Adapter Types"" in VirtualBox to no avail.

I run static IPs in the guest.

Virtual LAN = 192.168.184.0/24
VirtualBox NIC in PC = 192.168.184.1/24
Linux enp0s8 = 192.168.184.2/24 (default gw 192.168.184.1)

Physical LAN = 10.70.0.0/24
Windows physical NIC = 10.70.8.139/16
Linux enp0s17 = 10.70.8.130/16

Note: If I put the PC to sleep (tested up to 5 mins) and wake it back up, pings pick back up. It's just when I disconnect the cable to more than 5 seconds and plug it back in, the pings do not pick back up.",Tim Riley
15271,"USB mouse ""dies"" - pointer still moving but no function",Linux,VirtualBox 5.0.16,2016-03-24T11:21:45Z,2021-08-13T05:38:52Z,2021-08-13T05:38:52Z,"I am using a kubuntu 15.10 64 bit guest on Windows 7 Enterprise SP 1 with Version 5.0.16 r105871.

About every day, the USB mouse kinda dies in the guest - it still works normal on the Windows host and the pointer still moves in the kubuntu guest, but focus follows mouse and clicks don't do anything any more. Keyboard and everything else still works fine.

Logging off from KDE and on again fixes the problem.

In the attached dmesg, there is an issue with IRQ 22 and a stack trace which I am quite sure are related. The relevant VBox.log is also attached.",Torsten Römer
15268,Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10,Windows,VirtualBox 5.0.16,2016-03-23T19:24:19Z,2019-08-04T09:26:22Z,2019-08-04T09:26:22Z,"==== How to Reproduce ====

While trying to restart a VM with a saved state computer turns off and a blue screen shows the 
SYSTEM_SERVICE_EXCEPTION message then it restarts.

==== System Information ====

I am running:
VirtualBox VM 5.0.17 r106155 win.amd64 
Windows 10
DMI Product Name: Dell Precision M3800
Host RAM: 16286MB total, 12942MB available
Package type: WINDOWS_64BITS_GENERIC

==== Enabled Plugins ====
No plugins installed
",Nayz
15217,McAFee Agentblocks virtual machine running,Linux,VirtualBox 5.0.16,2016-03-08T09:27:19Z,2018-02-12T11:15:54Z,2018-02-12T11:15:54Z,"Good Morning, 

I use the Business PDL with O.S. Host Windows 7 Enterprise edition (x64).
In this sistem running McAfee Agent and i '''can't''' uninstall it.
But this block a VirtualBox Process. The VM is extremely important to testing a Engineering Siemens's software on Debian's O.S.

The message error are:

supR3HardNtChildPurify

supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED

Apertura di una sessione per la Macchina Virtuale Debian non riuscita.

The virtual machine 'Debian' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'D:\Bresciani\VM\Debian\Logs\VBoxHardening.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaccia: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

",abresciani@…
15305,Allow Relative Paths for Shared folder,all,VirtualBox 5.0.16,2016-04-12T11:25:16Z,2017-10-21T08:12:00Z,2017-10-21T08:12:00Z,"It is not uncommon for VirtualBox users to keep one or more Virtual Machines on flash drives, or other external storage, so they can have the convenience of their VMs in their pocket.

Such an external drive might have a folder structure like this:

{{{
DevDrive
\-- Virtualbox_Instances
    |-- Ubuntu14.04_Client
    |   |-- Logs
    |   |-- SharedFiles
    |   |-- client.vbox
    |   \-- client.vdi
    \-- Ubuntu14.04_Server
        |-- Logs
        |-- SharedFiles
        |-- server.vbox
        \-- server.vdi
}}}

When attached on Windows, the drive letter assigned to the drive can generally not be predicted, especially across multiple host machines.

Therefore if the user wishes to have the convenience of an [[https://www.virtualbox.org/manual/ch04.html#sf_mount_auto|auto-mounted shared folder via guest additions]], it is not unusual to have to re-define the shared folder whenever they try running their VM on a new host machine.

The logical solution to this problem would be to define the path of the shared folder relative to the VM, but currently relative paths seem to not be allowed.

Specifically, given the above Folder Structure, if the user modifies u14.14_client.vdi to contain:
{{{
<SharedFolders>
  <SharedFolder name=""SharedFiles"" hostPath="".\SharedFiles"" writable=""true"" autoMount=""true""/>
</SharedFolders>
}}}
They will receive this error:

[[Image(https://i.imgur.com/usGTFOq.png)]]

While adding the path as intended will result in something like:
{{{
<SharedFolders>
  <SharedFolder name=""SharedFiles"" hostPath=""F:\Virtualbox_Instances\Ubuntu14.04_Client\SharedFiles"" writable=""true"" autoMount=""true""/>
</SharedFolders>
}}}

But there is no guarantee that this drive will mount as letter `F` when connected on another host machine.

We cannot assume that the user would even have the privileges necessary on the host machine to assign a drive letter, especially since it may already be bound to another drive.


----

It would be really useful if VirtualBox supported relative Paths for Shared Folders. 

The path should be relative to the `.vbox` file itself.

",JohannesMP
16503,VM title cannot contain slashes,all,VirtualBox 5.0.16,2017-02-22T12:04:57Z,2017-03-09T09:24:26Z,2017-03-09T09:24:26Z,"When renaming a virtual machine to a name containing ""/"", an error appears about VM folder not being able to be moved. The slash is a very useful symbol in names and should be supported.",Urmas
15213,Unable to remove device with attached diff images,Windows,VirtualBox 5.0.16,2016-03-07T15:12:29Z,2016-11-16T13:00:51Z,2016-11-16T13:00:51Z,"Receive message box - one or more disk image files are not currently accessible......

Select ""check""

VDI device is not attached to any machine.  Also, rechecked all machines and non are using this vdi in this location.  Attempt to remove it but it says it has 1 child media and object in use.

a) cryptic message as it should really say in plain english what object name its associated with.

b) there are no machines that I currently have using this particular vdi.

c) have similar named vdi located in another directory but not attached to this one here.  Nothing is attached to it.
",ArtZ
15292,"Application Error ""The memory could not be read""",Windows,VirtualBox 5.0.16,2016-04-06T08:42:29Z,2016-09-18T23:05:43Z,2016-09-18T23:05:43Z,"I recently upgraded to 5.0.16 and started to see a crash after some time of actively using a virtual machine. 

I am attaching the log files I found. If there is a way to enable additional log files to be created please let me know. I also enabled the minidumps in Windows but this crash did not seem to generate any sort of dump.",Plazgoth
15350,"Cannot use , (comma) as a shortcut key",Linux,VirtualBox 5.0.16,2016-04-25T16:29:00Z,2016-04-25T16:29:00Z,2016-04-25T16:29:00Z,"Trying to use comma as a shortcut key (In this case for show-menu-bar >>> File - preferences - input - virtual machine - show-menu-bar - HOST+, (comma))

While the comma can be used as a shortcut, it no longer works after restarting VirtualBox and isn't visible in under file-preferences-...

Looking in %user%/.VirtualBox/VirtualBox.xml <ExtraDataItem name=""GUI/Input/MachineShortcuts"" value=""..."">
The keyboard shortcuts are saved in a comma-delimited list, so it just sees the comma as an extra delimiter, and fails to read it.

I worked around this by using < and > as shortcuts, as opposed to , and .

I might get to submitted a code fix, but low priority so I will just log the issue incase someone else is already in that section of code",CraigK
15314,More complete build number in log file.,all,VirtualBox 5.0.16,2016-04-18T10:09:12Z,2016-04-18T10:09:12Z,2016-04-18T10:09:12Z,"Would it be possible to give more precise Windows Host version in the VBox.log file?

Concrete example: VBoxHardening.log quotes a Windows version as 10.0.10586.122, whereas VBox.log quotes it as 10.0.10586.  From what I can gather, 10580.0 was released last November, whereas 10580.122 is the latest bleeding edge insider version released AFTER the current VBox version, so the minor build number is important information for support purposes.

This is an enhancement suggestion not a bug report, hence I'm not including log files.",mpack
15312,Ubuntu doesn't get to desktop when 3D acceleration is enabled,Linux,VirtualBox 5.0.16,2016-04-15T17:20:34Z,2016-04-15T17:20:34Z,2016-04-15T17:20:34Z,"I have guest additions with 3D acceleration enabled.
The client is Ubuntu 14.04 LTS

When launching Ubuntu, I can log in but it doesn't make it all the way through to the full desktop. The OS is basically unusable.",raduzard
15291,Linux Gest - Console black in Full Screen,Linux,VirtualBox 5.0.16,2016-04-04T11:55:38Z,2016-04-04T11:55:38Z,2016-04-04T11:55:38Z,When running Debian (current version 8.3) on a Windows host (Windows 8.1 Pro) in fullscreen switching from Gnome desktop to one of the other ttys (e.g. Hostkey-F1 to get tty1) results in a black screen. Doing the same in window mode (but maximized) does work fine.,jeansen
15237,random BSOD on Win7 x64,Linux,VirtualBox 5.0.16,2016-03-11T17:12:10Z,2016-03-23T03:51:32Z,2016-03-23T03:51:32Z,"Got several random BSOD on my WIN7 Dell Laptop while having Vbox running.


",theetete
15266,VirtualBox 5.0.16 - Windows 10 Host- Bridged Network,Linux,VirtualBox 5.0.16,2016-03-22T21:05:11Z,2016-03-23T02:58:01Z,2016-03-23T02:58:01Z,"Hello,

I have on Windows 10 Host the !VirtualBox 5.0.16 installed and try a Linux Guest with bridged Network.
On Network tab, i can select the bridged network as interface and then the physical network device from windows.
I am try to install a fresh Linux Ubuntu 14.04 LTS Server. This works fine, but the DHCP Service will not found from Linux. After setting up manual IP-addresses it will not be better. The Interface appears in the Linux system but no ping or other communication will work.

The IP-range is correct, the addresses also. Any idea what is the problem and what can i do?

Thanks Sascha",svalcken
15265,Touchscreen and scaling screen does not fit,Windows,VirtualBox 5.0.16,2016-03-22T17:12:31Z,2016-03-22T17:12:31Z,2016-03-22T17:12:31Z,"Hello,
I use Virtualbox Host Windows 10 and Guest Winsows 10 with USB-Multitouch-Pointer.
By Scalingfaktor 100% all works fine. By other Scalingfactor i.e. 150%  the position of the touch-input is wrong on Desktop.
I've tried 5.0.17 -> same Problem.

Scaling display is a very usefull feature at HD-Displays, so please fix the bug :-)

Sorry about my worst english

chriskl

ps: my Hardware is HP Spectre X360 13-4104ng",chriskl
15264,[Request] Add PCI segmentation support on I/O MMU Virtualization,all,VirtualBox 5.0.16,2016-03-22T13:51:08Z,2016-03-22T13:51:08Z,2016-03-22T13:51:08Z,"Current PCI passthrough support up to Bus/Device/Function only.

For example:
'VBoxManage modifyvm ""VM name"" --pciattach bus:device.function'

Request to add PCI segmentation support on I/O MMU Virtualization, such as:
'VBoxManage modifyvm ""VM name"" --pciattach segment,bus:device.function'",alexander3133
15250,No sound in W2012-2008 Server,Windows,VirtualBox 5.0.16,2016-03-17T10:34:50Z,2016-03-18T14:38:57Z,2016-03-18T14:38:57Z,"Sound device is detected, but Audio Output is absent.

For Server version of Windows only. Workstation versions are emulated fine.",MikhailRokhin
15252,Application Error - Sudden crash,other,VirtualBox 5.0.16,2016-03-17T18:28:50Z,2016-03-17T18:28:50Z,2016-03-17T18:28:50Z,"I was using my Ubuntu VM when suddendly VirtualBox crashed with the following Error Message:
- The instruction at 0xdb43b800 referenced memory at 0x00000000. The memory could not be read.

If I try to debug the program, I get the following additional information:
- An unhandled win32 exception occurred in VirtualBox.exe [8948].

Please find attached the logs, although I don't think you will see the crash reason there.

One minute before it crashed, I have detached the SD-Card-Reader. I had a console window open in the Ubuntu guest and the application crashed exactly in the moment where I entered ""exit"" followed by the Enter-Key.",tacarrie
15242,cannot open VirtualBox imported any machine (Windows or Linux),other,VirtualBox 5.0.16,2016-03-13T21:13:22Z,2016-03-14T19:16:32Z,2016-03-14T19:16:32Z,"I want to use VirtualBox on my NetBook ""Aspire One D270"", but I cannot. I tried VirtualBox 5.0.16 either VirtualBox 5.0.0 and also both portable and fix installted. I do not know the reason, hardware? Antivir? Firewall?

Fehlercode:
E_FAIL (0x80004005)
Komponente:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
",Sven_web
15234,"Starting virutalbox causes ctrl, shift, alt and super key to stay pressed",other,VirtualBox 5.0.16,2016-03-11T00:12:59Z,2016-03-11T03:12:30Z,2016-03-11T03:12:30Z,"When starting VirtualBox, before launching any guest whatsoever, Windows starts behaving very peculiar. First, the VirtualBox window does not appear on top of other windows, but instead behind all open windows. Then the keyboard mostly stops working (I can't write anything anywhere, use alt+tab etc), and clicking anywhere there is text (for example a browser) starts marking text and I can't use my scroll wheel for scrolling through web pages. My left mouse button still works, but most right click menus disappear as quickly as they appear. If I try to launch anything (or switch to a running program) in the taskbar this causes a UAC window to appear. This behaviour continues after closing virtualbox, and the only way I've discovered to get rid of it is a complete reboot.

Thinking this seemed like ctrl+shift were pressed I proceeded to log some keys. Using autohotkey I managed to check what happens when I start Virtualbox, and it seems LAlt, LWin, RControl, RShift and F3 all get pressed down (but not up). This also seems to repeat 8 times (with a ~30ms delay in between each iteration).

This problem started happening sporadically for me about a month ago or so, when running my virtual machine (although quite rarely). I could not seem to identify any particular behaviour triggering this at the time. Today I upgraded to VirtualBox 5.0.16 and now the issue somehow turned permanent, and happens every time I launch, and it really renders the host pretty much unusable until next restart.

Although it is very clear that this change happened during my upgrade to 5.0.16, now it happens for more versions. I tried unistalling and reinstalling several times, with the problem remaining, and even tried 5.0.14 and 4.3.36, with the same issue happening on every startup of Virtualbox. I have made sure to turn off any program (including autohotkey) runnning in the background both during installation and running the program.

I run on a 64-bit version of Windows 10, using a swedish keyboard layout. The problem starts happening before any VM launch, but if it's of interest I only have one Ubuntu guest that I use for development sometimes. I can still launch my VM with this behaviour, but I can't seem to be able to use the keyboard in it. I'll attach a VBox.log of that running, in case it is of interest.",rubicus
15207,Guest kubuntu freezes just after dektop completes loading (more often if loading while virtualbox is not in focus),Linux,VirtualBox 5.0.16,2016-03-05T12:47:27Z,2016-03-09T19:22:27Z,2016-03-09T19:22:27Z,"Hello there.

Host='''Win10 x64'''
Guest='''Kubuntu 16.04 x64''' (I had the same issue with 15.10)

It is reproducible on kernel 4.0.X up to '''4.4.4''' at least.

Sometimes, after SDDM login desktop appears and freezes in second. I can move one window in that time or click a button but nothing more: virtual box freezes and closes after 4 or 5 tries. I mean, after click stop button it hangs completely and stops to respond.

I had this issue in 5.0.14, 5.0.15 and now in '''5.0.16'''. I never had such problems with the OS running outside virtual box (I have raw image targetting whole SSD drive)

I didn't find anything interesting in VBox.log, but attached it though.

Oh! And one more thing - if virtualbox window is not minimized and doesn't lose focus during the whole boot procedure, chances to be frozen are decreased. It hangs in >80% of cases when the window loses focus during the boot and ~20% only when it stays focused.",Grief
15216,Guru Meditation after installing FreeDOS,other,VirtualBox 5.0.16,2016-03-07T21:40:29Z,2016-03-08T08:27:22Z,2016-03-08T08:27:22Z,"Hi,

I've just installed the latest version of FreeDOS and get a Guru Meditation error when trying to boot that machine.

",Mastropiero
15351,Oracle VM VirtualBox Manager Crashes on Shutdown,Windows,VirtualBox 5.0.18,2016-04-25T19:53:35Z,2022-04-11T10:31:23Z,2022-04-11T10:31:23Z,"I know there are quite a bit of ticket dealing with Virtualbox crashing during shutdown.  This is not a problem with a guest but with the Oracle VirtualBox Manager.  This has been present since 5.0.0 was released.  I have tested every release since 5.0.0 including 5.0.18.

Host OS:  Windows 7 64bit
Guest OS:  Windows 7 32bit

How to Reproduce

1.  Open Oracle VM VirtualBox Manager, do not start a guest.
2.  Shutdown the Windows 7 Host computer.
3.  This should generate the errors attached.
",cmccarron
16075,"VBox ""draganddrop"" CPU Spike on Ubuntu Guest",Linux,VirtualBox 5.0.18,2016-10-17T19:06:54Z,2018-12-10T11:10:40Z,2018-12-10T11:10:40Z,"Version: 5.0.18_Ubuntur106667
Host: Windows 7 Professional Service Pack 1 64-Bit
Guest: Ubuntu 16.04 LTS 64-Bit

I have a very peculiar issue with VirtualBox. To replicate on my machine:
1) Open Guest to desktop and leave open in one window
2) Open windows explorer and place on top of Guest
3) Drag arbitrary file from window on top of Guest to anywhere outside Guest, ensuring cursor with file moves over any section of Guest.
4) CPU immediately spikes to 100% with the two processes of the name ""/usr/bin/VBoxClient --draganddrop"" using the highest percentages

I've attached my logs to this ticket.",craymichael
15355,Auto-resize guest (Win 8.1 and 10) not working with Guest additions 5.0.18,Windows,VirtualBox 5.0.18,2016-04-26T14:25:49Z,2016-08-24T20:28:57Z,2016-08-24T20:28:57Z,"Auto-resize guest using the Guest additions 5.0.18 does not work in a Win 8.1 and Win 10 VM.
I've verified that:
- Auto-rezie guest display is enabled
- Maximum guest screen size is automatic

What I've done (and did NOT help):
- Downgrading to 5.0.16 from 5.0.18 (and reinstalling the matching GA)
- Reinstalling/upgrading Guest Additions

What I've done (and DID help):
- Downgrading to 5.0.14 (and matching GA)
- Using vBox 5.0.18 with the 5.0.14 GA",Martien Korenblom
15328,usb mouse does not work after migrating to 5.0.18,Linux,VirtualBox 5.0.18,2016-04-21T07:18:46Z,2016-08-03T09:47:26Z,2016-08-03T09:47:26Z,"if I setup guest 5.0.18 addons in linux guest , mouse seems available but no cursor is displayed.
if I remove completely guest kernel modules addons, mouse is working.
if I setup 5.0.16 guest addons and run 5.0.18 host , the mouse does not work , graphic system runs badly.


",sancelot
15341,Unexpected closure of guest when clicking menubar item in fullscreen,Linux,VirtualBox 5.0.18,2016-04-24T05:43:00Z,2016-07-20T07:52:16Z,2016-07-20T07:52:16Z,"About half the time when I click a menu bar item expecting it to open the menu, it closes the guest without any warnings whatsoever.  That is VERY bad.  The typical time I've noticed, I was either trying to open the View menu or the Devices menu.

In many ways, this is a crash--even if vBox thinks it was told to close.  I was unsure of which component to chose.  Someone may need to correct it.

The only guest/host combination this was noted with was Linux for the guest and Windows for the host.  However, I expect this to affect all guests.",Will Pittenger
15318,seamless mode does not work after upgrade to VirtualBox 5.0.18 Oracle VM Guest Additions on Ubuntu Guest,Linux,VirtualBox 5.0.18,2016-04-19T08:28:11Z,2016-05-31T15:40:04Z,2016-05-31T15:40:04Z,"Host ist Win10-64bit and guest is Ubuntu 15.10. The task bar is about 2cm deeper than normal. Staying at the guest additions from xxxx16 works.

Any idea?",beststevie
15391,TTL Expired in Base Machine if 2 VM's runnig,Windows,VirtualBox 5.0.18,2016-05-05T09:16:28Z,2016-05-05T15:21:21Z,2016-05-05T15:21:21Z,"Been using Virtual box for Years, but I have notice a problem lately ( last week). Using !VirtualBox 5.0.18 r106667

Each of my VM's have 2 Interfaces , one set as bridged (IPV4 Static) , one set as NAT (DCHP) . The NAT interface is set as Cable Disconnected to Keep VM from internet unless I specifically need it.

Now down to my problem, my network on my base machine seems to have TTL Expire errors when I ping 8.8.8.8 from base machine while I have 2 VM's running as soon as I pause them or switch them off/suspend them the TTL EXPIRE error disappears. I have tried with and without the network interfaces in the VM enabled. This can be seen by the time the XP Splash screen shows on Second machine rather than once XP is fully running. 


Ping to 8.8.8.8 from Base machine as second VM is started
{{{
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 8.8.8.8: bytes=32 time=33ms TTL=58
Reply from 8.8.8.8: bytes=32 time=30ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
}}}

Routing Tables from Base Machine
{{{
===========================================================================
Interface List
 28...1a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter
 16...2a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 31...0a 00 27 00 00 1f ......VirtualBox Host-Only Ethernet Adapter
 12...d4 be d9 84 d1 0b ......Realtek PCIe GBE Family Controller
  8...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 21...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
 13...b8 76 3f 20 74 c1 ......Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz)
 23...00 ff 99 5b a6 25 ......TAP-Win32 Adapter V9
 43...00 ff ea 7f 81 0e ......TeamViewer VPN Adapter
  3...b8 76 3f 20 74 c2 ......Bluetooth PAN HelpText
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.176     20
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.172     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     172.16.228.0    255.255.255.0         On-link    172.16.228.176    276
     172.16.228.0    255.255.255.0         On-link    172.16.228.172    281
   172.16.228.172  255.255.255.255         On-link    172.16.228.172    281
   172.16.228.176  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.172    281
     192.168.10.0    255.255.255.0         On-link      192.168.10.1    276
     192.168.10.1  255.255.255.255         On-link      192.168.10.1    276
   192.168.10.255  255.255.255.255         On-link      192.168.10.1    276
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    266
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    266
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    266
    192.168.184.0    255.255.255.0         On-link     192.168.184.1    276
    192.168.184.1  255.255.255.255         On-link     192.168.184.1    276
  192.168.184.255  255.255.255.255         On-link     192.168.184.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.56.1    266
        224.0.0.0        240.0.0.0         On-link    172.16.228.176    276
        224.0.0.0        240.0.0.0         On-link    172.16.228.172    281
        224.0.0.0        240.0.0.0         On-link      192.168.10.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.184.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.56.1    266
  255.255.255.255  255.255.255.255         On-link    172.16.228.176    276
  255.255.255.255  255.255.255.255         On-link    172.16.228.172    281
  255.255.255.255  255.255.255.255         On-link      192.168.10.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.184.1    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 31    266 fe80::/64                On-link
 13    281 fe80::/64                On-link
  8    276 fe80::/64                On-link
 21    276 fe80::/64                On-link
 13    281 fe80::558:9d49:604d:8884/128
                                    On-link
 31    266 fe80::5565:d785:2df6:9cb6/128
                                    On-link
  8    276 fe80::88b5:5871:7b28:d87/128
                                    On-link
 21    276 fe80::c9b3:ca08:7e8b:6e66/128
                                    On-link
  1    306 ff00::/8                 On-link
 31    266 ff00::/8                 On-link
 13    281 ff00::/8                 On-link
  8    276 ff00::/8                 On-link
 21    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
}}}


VM Log ATTACHED",mad4x4
15367,Cannot remove 4.3.12 Bridged Network Miniport Driver - Bridget Networ not working,all,VirtualBox 5.0.18,2016-04-28T13:11:53Z,2016-04-28T13:11:53Z,2016-04-28T13:11:53Z,"Hi,
Bridged Network does not work anymore after updating to any 5.x version. There are still remains of the old 4.3.12 driver in the device manager (with exclamation mark) wich I can't ether uninstall or repair. Uninstalling VBox 5.0.18 rebooting, re-installing has no effect. No new drivers were installed. 

I also tried to remove involved keys from the registry, but I could not delete them for whatever reason. I'm running windows 8.1.
",Elsni
15347,RPC_S_SERVER_UNAVAILABLE when logging off host while VirtualBox.exe is running,other,VirtualBox 5.0.18,2016-04-25T13:18:14Z,2016-04-25T13:18:14Z,2016-04-25T13:18:14Z,"Host machine is Windows 7 Ultimate, SP1 64-bit.

1. Start VirtualBox Manager (VirtualBox.exe) - no need to actually start a VM
2. Log off from host machine.
3. VirtualBox Manager then gives the following series of error message boxes:

Failed to set the global VirtualBox extra data for key GUI/Toolbar to value {}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/Statusbar to value {}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/SplitterSizes to value {469,568}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/LastWindowPosition to value {319,152,1041,745}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/DetailsPageBoxes to value {general,system,display,storage,network,sharedFolders,description}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

Failed to set the global VirtualBox extra data for key GUI/LastItemSelected to value {m=FL Pro}.

Callee RC: RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)

At this point the VirtualBox Manager window has disappeared, but Task Manager shows that VBoxSVC.exe and (1 instance of) VirtualBox.exe is still running.

Attached are the log files that existed after:
- the aforementioned error messages
- I used Task Manager to kill the VBoxSVC and VirtualBox (so that WinZip did not complain about trying to read the log files)

This looks like it might be related to https://www.virtualbox.org/ticket/12933",m6477
14461,Raw disk VM gives ahci-0-0 BLKCACHE_IIOERR if block cache turned off on VirtualBox 5.0.1 and later => fixed in SVN/5.0.x,all,VirtualBox 5.0.2,2015-08-17T17:46:41Z,2021-06-27T12:09:02Z,2021-06-27T12:09:02Z,"VirtualBox builds 5.0.2-102096 and 5.0.1-102010 fail to run correctly a full-raw-disk-based virtual machine that 5.0.0-101573 loads correctly. The failure occurs when the ""Use Host I/O Cache"" option (StorageController: useHostIOCache) is off for the controller of the raw VMDK.

This is the case even though VirtualBox is being run as an administrator, which I've found required for it to work with raw disks at all. Maybe something changed about what process accessed the drive?

The machine doesn't die straight away, but immediately after the initrd system loads up - the ""Root: clean"" line of fsck is printed (there are many things that happen just after that, so I don't want to imply it's part of fsck) - it freezes and a message is printed:

----

An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error

----

The log also mentions ""Invalid machine state Paused when checking if the guest entered the ACPI mode"".

----
ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
00:00:10.967017 Console: Machine state changed to 'Stopping'
----
Host is Windows Vista 32-bit, guest is Debian 8.x 64-bit (though I figure it probably doesn't matter so I left the type as 'all'). The controller is the LSI logic, listed as ""AHCI"" in the GUI.

Attached are logs from when the files work, and when they don't, and the vmdk and vbox in question.",Laurence 'GreenReaper' Parry
14484,Host-only adapter fails after sleep-wake transition,Linux,VirtualBox 5.0.2,2015-08-21T22:57:02Z,2018-11-25T15:46:20Z,2018-11-25T15:46:20Z,"In 5.0.2, Window 7 host, Debian 8 guest, the host-only adapter only works after a full restart of host and guest.  Once you put the host to sleep and wake it back up again, the host-only adapter is broken.  Here is what ping from the guest gives:

root@byted> ping 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
From 192.168.56.101 icmp_seq=1 Destination Host Unreachable

where 192.168.56.101 is the guest IP and 192.168.56.1 is the adapter IP.  There is a similar break in ping of guest IP from host.

jpm
 ",Jeff Morgenthaler
14457,cannot ping host <--> VMs after upgrade to VirtualBox 5.0.x with NDIS6 driver,all,VirtualBox 5.0.2,2015-08-16T19:21:34Z,2016-12-13T10:29:47Z,2016-12-13T10:29:47Z,"In reference to this forum post:

https://forums.virtualbox.org/viewtopic.php?f=6&t=69597

after upgrading to VirtualBox 5.0.x I could no longer ping between the host and the VMs (bridged mode), while the VMs could still ping each other, and all (host and VMs) could still ping other computers on the same subnet.  By reverting back to using the NDIS5 driver, all worked properly again, so the issue is related to some bug/defect in the new NDIS6 driver implementation.
",qd01a
15989,Guru Meditation error,Windows,VirtualBox 5.0.2,2016-09-26T09:34:35Z,2016-09-27T20:14:56Z,2016-09-27T20:14:56Z,"Hi. I have built 2 test VMs using virtualbox. But, when I have one VM opened and trying to start another one, it throws me the attached Guru meditation error.

I'm new to virtualbox, so request you to guide me in this regard & solve the issue.


Thanks!",RJD
14546,Can't install VirtualBox on Windows 10,Windows,VirtualBox 5.0.2,2015-09-05T20:27:46Z,2016-02-28T09:08:32Z,2016-02-28T09:08:32Z,"I am not able to install VirtualBox nor 5.0.2 or 5.0.x revision 102467 on my Windows 10 laptop. Previous I updated Windows 8.1 to Windows 10 and all works fine. Now after clean install of Windows 10 i can't use VirtualBox again. I think problem is related to VirtualBox network drivers. I enclose a log file where there is some info:

InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
Installing INF file ""C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf"" ...
Install failed, hr (0x80070005)
VBoxNetCfgWinInstallComponent failed, hr (0x80070005)
Installation failed, rolling back installation set ...
",sal3tra
14524,VisualStudio 2013 Professional on Windows 10,Windows,VirtualBox 5.0.2,2015-08-31T09:12:59Z,2015-10-31T02:15:37Z,2015-10-31T02:15:37Z,"I have Windows 10 installed and Visual Studio 2013 Professional. 
Also the host has Windows 10 installed. 
When my computer goes to sleep and starts-up again the screen size 
of the virtual environment is decreased to 800x600.
Before that screen size it was 1600x860. 
To fix this I can only reboot the virtual environment.

When I used Windows 8.1 and VirtualBox 4.2 this problem did not occured.  ",UserVirtualBox
14699,"Wrong icon for ""Other Linux (64-bit)""",Linux,VirtualBox 5.0.2,2015-10-14T18:54:55Z,2015-10-14T18:54:55Z,2015-10-14T18:54:55Z,"Choose[[BR]]
Type: '''Linux'''[[BR]]
Version: '''Other Linux (64-bit)'''[[BR]]


Icon the same as for '''Other Linux (32-bit)''' without 64 in left top corner.",bmx666
14452,Installing VirtualBox 5.0.2 blocks network on host (Windows 10),other,VirtualBox 5.0.2,2015-08-16T01:57:41Z,2015-09-14T12:59:20Z,2015-09-14T12:59:20Z,"I installed VirtualBox 5.0.2 on my host system which runs Windows 10.

It made my network fail.
The tray icons shows no error but trying to access a website does not work.
Restarting host does not help.

There are no errors in windows device manager. Both my network cards and VirtualBox's show.

Unintalling VirtualBox, immediately makes the network work again.

I have tried this on two computers with fresh windows 10 installs.

Both my computers have an intel network card.
One computer with ""Intel(R) Ethernet Connection (2) I218-V"",
and the other with ""Intel(R) Ethernet Connection I217-V"" (this computer also has a ""Killer e2200 Gigabit Ethernet Controller"").

",spacebug
14523,Windows 98 boot Crashes straight to Guru debugging.,Windows,VirtualBox 5.0.2,2015-08-30T21:59:15Z,2015-09-05T19:33:17Z,2015-09-05T19:33:17Z,"When i load up windows 98 and attempts to load the GUI/System, It crashes stright to Guru debugging. I have the log attached. For the screenshot? Just black. Not the worth if its black. Can you please find out whats going on?",HSF3232
14540,No files for DOS applications in VBox shared folder,Windows,VirtualBox 5.0.2,2015-09-04T09:14:48Z,2015-09-04T09:14:48Z,2015-09-04T09:14:48Z,"A DOS application (Foxpro, XtreeGold) can't read list of files in a shared folder. Windows app can see all files. This problem is properly described in https://www.virtualbox.org/ticket/8551 - but there is no solution.

Host (32 bite): Windows 8, Windows 10
Guest (32 bite): Win XP",DanielR
14539,Extreme screen flashing and guest unusable,Linux,VirtualBox 5.0.2,2015-09-03T17:58:30Z,2015-09-03T18:32:46Z,2015-09-03T18:32:46Z,"While this issue started on Windows 10 and I understand there are[[BR]]
problems there, I have since rebuilt the host machine from scratch[[BR]]
with Windows 8.1 and am still experiencing problems although they have[[BR]]
changed some.
For the history of this issue please see:
https://forums.virtualbox.org/viewtopic.php?f=6&t=69906&p=334049#p334049

Environment
> VirtualBox 5.0.2
> Latest extension pack installed
> Windows 8.1 host
> Ubuntu 14.04 guest

Current problem
1) When starting up the guest the guest window flashes. It is very extreme
2) On some starts when guest starts in full screen mode, the minibar is visible during startup but then is no [[BR]]
longer visible. 
3) The guest periodically becomes unresponsive. [[BR]]
The screen looks perfectly normal but does not respond[[BR]]
to mouse clicks. I have assumed keyboard input as well but to [[BR]]
be completely accurate, I have not tested that. However, it does[[BR]]
seem that the UI has frozen. Nothing within the guest window responds[[BR]]
including the OS bar at the top of the Ubuntu window where you[[BR]]
can shut-down the OS.
4) The screen will be come black
* This is happening in fullscreen and normal view.

I have attached logs
I marked this critical as I'm unable to use my dev environment[[BR]]
and get work done. I understand it may not be critical in your view.
Sincerely,
Karl",kekeke
14537,Linux grsecurity guest kernel will not mount shared folders,Linux,VirtualBox 5.0.2,2015-09-03T15:44:23Z,2015-09-03T15:44:23Z,2015-09-03T15:44:23Z,"My guest is an Arch Linux 64-bit VM running kernel 4.1.6.201508230818-1-grsec (latest from official Arch repos as of this report). Since installing the grsecurity kernel, mount.vboxsf will fail with a Protocol error. The following is logged to dmesg when attempting a mount:

{{{
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-5
VBOXGUEST_IOCTL_HGCM_CALL: 64 Failed. rc=-5.
sf_read_super_aux err=-71
}}}",kballen
14518,Can't install Guest Additions in Windows 10 guest under Windows 8.1,Windows,VirtualBox 5.0.2,2015-08-29T15:44:24Z,2015-09-01T12:50:37Z,2015-09-01T12:50:37Z,"I have never been able to install the Guest Additions ever since I first tried the Technical Preview of Windows 10 and VirtualBox 4.28 or 4.30.  It has always failed when installing the WDDM driver.

This is the case with the current VirtualBox test build 5.0.3r102322 and its Guest Additions 5.0.3.102316.

I attach the machine log and a screen shot of the Guest Additions installation.  As the machine is unusable after the Guest Additions intended installation, I was only able to get its installation log by attaching the virtual disk to another Windows 7 VM.  However, it doesn't show any errors.

I did a machine reset but, on reboot, I still had a blank screen and had to ""power it off"".  I restored the machine to a saved VBox snapshot in order to be able to use it.
",c273
14514,VM freezes during installation of guest,Linux,VirtualBox 5.0.2,2015-08-28T07:09:02Z,2015-08-28T07:09:02Z,2015-08-28T07:09:02Z,"I am trying to install openSUSE 13.2 and in the middle of the installation everything just stalls. I am able to move the mouse around and operate dialog boxes/buttons inside openSUSE but the installation itself completely froze.
Process Explorer confirms it where I/O activity completely stops in the middle of loading files. It never stops in the same spot always. Once it got as far as installing half the applications that come with the OS, most of the time it doesn't even make it to the first one.

On average it's about 10 minutes into the session that this happens. Once it stalls, there is no possible way to terminate the VM. If I manage to close the window, the process will remain in memory (and I cant start the VM again). I cannot even normally restart my host PC. I have to press the button on the computer to force restart. If I try to terminate the VM after the freeze, it interferes with the functioning of my host OS. Some programs I can't open at all such as CMD, other operations will be extremely slow and so on.",Inds
14504,VM VirtualBox crashes on Windows Server 2008 r2,other,VirtualBox 5.0.2,2015-08-27T07:34:29Z,2015-08-27T08:19:42Z,2015-08-27T08:19:42Z,"As soon as I open the application, it crashes with the following information:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	0.0.0.0
  Application Timestamp:	555369a5
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.1.7601.18247
  Fault Module Timestamp:	521eaf24
  Exception Code:	c0000005
  Exception Offset:	000000000005320e
  OS Version:	6.1.7601.2.1.0.274.10
  Locale ID:	7177
  Additional Information 1:	c042
  Additional Information 2:	c042b26446d5b704c80f7a33d8431df8
  Additional Information 3:	d71e
  Additional Information 4:	d71e92005cc3ffc26e9fe64612607c50

Any advise on what it could be? Don't even know where to start! Version 4.3.28-100309.",cverster
14489,My Windows 7 cannot surf the Internet after I upgrade Virtualbox,all,VirtualBox 5.0.2,2015-08-24T05:42:11Z,2015-08-24T05:42:11Z,2015-08-24T05:42:11Z,"I used virtualbox 4.3.30 before. And then I upgrade Virtualbox from 4.3.30 to 5.0.2 and 5.0.0. After I upgrade Virtualbox to those newer versions. I cannot connect any website. Finally, I uninstall newer versions and load back 4.3.30 version. It can connect website successfully.",jackzzkao
14463,Symlinks in shared folders don't work after upgrading to 5.0.2,Linux,VirtualBox 5.0.2,2015-08-17T19:39:47Z,2015-08-20T20:35:47Z,2015-08-20T20:35:47Z,"I'm running CentOS 7 as a guest on a Windows 10 host machine. When using 5.0.0 or the test build, 5.0.1, symlinks work fine but once I upgraded to 5.0.2, they stopped working.

The symlink is relative to 2 directories up and was created in Windows 10 as follows:
mklink /D rpclib ..\..\node-rpclib

I tried downgrading the Guest Additions from 5.0.2 to 5.0.0 and that didn't fix the problem so it seems related to the VirtualBox 5.0.2 program itself since after downgrading to 5.0.0 it went back to working

Here's the VBox.log from 5.0.0: http://gobin.io/mTII
Here's the VBox.log from 5.0.2: http://gobin.io/ZJuK

Let me know if you need any more information.",fastest963
14470,NAT Network failing to provision gateway,Linux,VirtualBox 5.0.2,2015-08-18T18:56:35Z,2015-08-18T21:01:03Z,2015-08-18T21:01:03Z,"Creating a new NAT Network using the GUI WITHOUT DHCP server results in a network with the gateway address at x.y.z.1 however gateway fails to respond to ping and fails to forward traffic upstream.  Stopping and restarting VirtualBox does not resolve gateway non-functionality.

NAT Network created WITH DHCP server responds to ping and forwards traffic upstream.  Removing/disabling the DHCP server does not cause loss of gateway functionality.  Functionality maintained across restart of VirtualBox.",VirtualBryan
14464,dwFileAttributes Incorrectly Reports FILE_ATTRIBUTE_REPARSE_POINT,Windows,VirtualBox 5.0.2,2015-08-17T19:54:27Z,2015-08-17T19:54:27Z,2015-08-17T19:54:27Z,"With a Windows guest running within a Windows host, executing the FindFirstFile Win32 API function on the guest returns the incorrect dwFileAttributes with FILE_ATTRIBUTE_REPARSE_POINT for symlinks on the vboxsf.

With symlinks on Linux & Mac hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to false.

With symlinks on Windows hosts, FILE_ATTRIBUTE_REPARSE_POINT is set to true.

FILE_ATTRIBUTE_REPARSE_POINT should be set to false for all vboxsf files/folders, because being a symlink should only be relevant to the host, and the information should be hidden to the guest.

This is causing us some issues doing PHP development involving symlinked folders, because PHP likes to try and follow the reparse points to convert relative paths to canonical paths.  It attempts to retrieve the reparse point info to conver to the canonical path, then fails.


To reproduce the issue:

On the Windows host, create a folder at c:\test

Create a subdirectory at c:\test\myDir

Create a symlink:

{{{
mklink /D c:\test\myLink c:\test\myDir
}}}

Create a VirtualBox shared folder pointing to c:\test , and mount it to X: within the guest.

Run the attached Python script:

{{{
python find_data.py X:\myLink
}}}

On the Windows host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 1024
Attributes: 1040
}}}

On a Linux/Max host, this outputs:

{{{
Target file is X:\myLink
Found file: myLink
Reparse point: 0
Attributes: 16
}}}",Matt Hopkins
14460,Error starting VM - E_FAIL 0x80004005 SessionMachine,Windows,VirtualBox 5.0.2,2015-08-17T17:23:05Z,2015-08-17T17:30:54Z,2015-08-17T17:30:54Z,"I am getting virtualbox error ""Failed to open a session for the virtual
machine xxxxx.""  The VM session was aborted. See screenshot attachment
for complete error. 

This happens when I start any virtual machine just after launching the
virtualbox manager.  I try the start a second and sometimes third time
and the machine will launch and function normally.  When it shuts down,
I also get an error but everything is being saved inside the machine.

I am running Windows 10 Pro (64-bit) on an HP desktop (I7 processor
with 32gb of memory).  This only started after upgrading to version 5
of virtualbox.  I have tried the original 5.0 version, the 5.01 test
version and am now on 5.02 r102096.  The guest machine doesn't seem
to matter - they all receive the error.  Guests include Windows 10
Enterprise, Windows 2008 R2 server, Windows 7, and Windows 2003 R2
server.

Attached is the screenshot of the error and a clean log (cleared before
starting virtualbox and getting error).",_Dale_
14440,Guest program runing with wrong account,Windows,VirtualBox 5.0.2,2015-08-14T14:21:55Z,2015-08-14T14:21:55Z,2015-08-14T14:21:55Z,"When you start or run any programs on guest it's will run under system account, not specified by ''--username'' one.[[BR]]
This bug occurred by Guest Additions 5.x only.

Thanks. ",EAX
15438,Guest can't access host network after resume from hibernation (hybrid sleep).,Linux,VirtualBox 5.0.20,2016-05-23T13:05:56Z,2022-01-18T05:02:12Z,2022-01-18T05:02:12Z,"Host : Windows Server 2008 R2 SP1.[[BR]]
Guest : 64-bit Arch Linux with kernel 4.5.4-1-ARCH.[[BR]]
Network : Bridged with host network card (VirtualBox NDIS6 Bridged Networking Driver).[[BR]]

After resume from hibernation, guest can't access host network. No ping packets reach host. Rebooting guest doesn't help. Only totally powering off and then turning it on helps and guest can access host again.

Maybe related to bug ticket [https://www.virtualbox.org/ticket/14457]",hotjava1231
15478,VBoxTray.exe using excessive CPU,Windows,VirtualBox 5.0.20,2016-06-05T21:35:17Z,2019-10-03T10:22:20Z,2019-10-03T10:22:20Z,"Windows 10 Host running Widows Guests. Problem started after upgrading to 5.0.18 and installing the GAs. Problem remained after upgrading to 5.0.20.

Symptom is that apps running in the guest get very sluggish. Sometimes slide bars are unresponsive. Menu pull downs always open the first selection. Symptoms appear several minutes after VM is started, but once VBoxTray.exe starts eating the CPU, it does not disappear.

Started thread in forums at: https://forums.virtualbox.org/viewtopic.php?f=2&t=77784

mpack suggested going back to 5.0.16 after just installing 5.0.16 GAs did not fix problem.

Problem does not appear when running 5.0.16 with the 5.0.16 GAs",pansophysr
15403,"Clone Function Errors Out when using ""/"" Character",Windows,VirtualBox 5.0.20,2016-05-10T19:30:18Z,2018-03-16T14:36:16Z,2018-03-16T14:36:16Z,"I am trying to create a cloned VM using the following name in the Clone Disk wizard:

Windows 7 / Visual Studio 15 Preview

This worked in prior builds of VirtualBox.  It doesn't seem to like the ""/"" in the cloned disk's name, and it errors out and won't create it.

When I change the cloned name in the wizard to ""Windows 7 - Visual Studio 15 Preview"" (i.e. replacing the ""/"" with a ""-""), then it works.

Again, I had no problem using this in my clone name in prior builds.  I am using the latest build (i.e. 5.0.20.106931)

Please advise.",Master VB Guru
15417,GUI Artifacts after opening Chrome,Linux,VirtualBox 5.0.20,2016-05-15T00:43:28Z,2017-03-28T14:14:25Z,2017-03-28T14:14:25Z,"Starting from 5.0.16 theres been graphics artifacts which hang the desktop (Gnome 3) on a Ubuntu 14.04 guest with the latest Xenial LTS kernel (4.4) and guest additions installed on a Windows 7 64bit host.

The graphics artifacts effectively start after you open Chome and even restarting Gnome 3 doesnt resolve the artifacts. This partially happened in 5.0.14 but only for a few seconds when you initially open Chrome and then it goes away and is usable. From 5.0.16/20 this pretty much makes the GUI desktop unusable once you open Chrome.
",Julio Lajara
15424,Crash when suspending Win10 (14342) guest,Windows,VirtualBox 5.0.20,2016-05-17T04:51:43Z,2016-08-22T04:44:01Z,2016-08-22T04:44:01Z,"... on a Win8.1 host. Both 64bit.

Screenshot of the Error http://i.imgur.com/OVeyzzg.png",Stanzilla
15492,Some apps not displaying correctly,Linux,VirtualBox 5.0.20,2016-06-09T12:23:26Z,2016-08-18T15:54:26Z,2016-08-18T15:54:26Z,"Hi,

I've just upgraded my Linux Mint host to lastest, and had to re-install the guest additions ( from reading around this probably implies there was a kernel update... ).

However some apps aren't being displayed at all correctly, e.g. Visual Studio Code which just displays as a load of dark grey blocks.
Also the login screen displays small rather than full screen ( but works ).

With some trial and error I've discovered that guest additions 5.0.16 is the last which doesn't show this problem, but 5.0.18 and 5.0.20 both do.",Barrie
15448,Second monitor disappears,Windows,VirtualBox 5.0.20,2016-05-26T14:22:32Z,2016-08-10T14:41:35Z,2016-08-10T14:41:35Z,"I believe this has been raised as a ticket before and has been closed but I still have an issue with this. I run a windows 10 pro 64-bit guest on a windows 10 Home 64-bit host. Often, at least twice in an 8 hour work day, when I minimize the second monitor it disappears from the host taskbar, leaving only the one virtualbox instance for the primary screen on the host taskbar. The second monitor is restored when I hit ctrl + F twice to take virtual box out of full screen and then put it back in full screen mode.",collusion
15404,Windows 10 - Failed to create the host-only adapter,Linux,VirtualBox 5.0.20,2016-05-11T08:55:23Z,2016-07-26T15:19:29Z,2016-07-26T15:19:29Z,"When I'm trying to run my VM using vagrant I'm getting following error:

{{{
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""hostonlyif"", ""create""]

Stderr: 0%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}

System information:
- VirtualBox 5.0.21r107152
- Vagrant 1.8.1
- Windows 10 Enterprise Insider Preview, Build 14342.rs1_release.160506-1708


",josin
15605,Full screen bug,Linux,VirtualBox 5.0.20,2016-07-13T19:10:47Z,2016-07-13T19:10:47Z,2016-07-13T19:10:47Z,"I know there are 2 tickets for this problmen, but still it's an annoying bug. I can't use full screen mode, either I can't uninstall virtual box. 

When I try to unintall it the wizard came up, then it asks that would I install an another software. No mather what I chose it ends in the same way. The files stayed untouched but I still can run the software.",Zoltanka
15590,"Windows guest hangs with AHCI port resets, cannot close VirtualBox instance",Windows,VirtualBox 5.0.20,2016-07-10T14:52:46Z,2016-07-10T14:52:46Z,2016-07-10T14:52:46Z,"Hello,

Recently I encountered a Windows guest that hung itself and would not allow me to stop it when right-clicking the VM->Close->Power off. I am running it in headless mode and I saw the vBoxHeadless.exe process on the host was reporting a constant CPU usage value but was not changing, indicating the process was hung.

There are 6 other guests running on this host, all of which did not hang and continued operating properly.

The guest had been booted at 6/30/16 01:31 and some logging software of mine stopped receiving a ping from the guest around 7/9/16 13:30 (232:57 in logfile). I did not attempt to intervene until 20 hours later (252:29 in logfile). It looks like when the guest host process hung the AHCI controller experienced an issue with port resets.

The host is running Windows Server 2008 R2, the guest is running the same.

The VBox.log file is attached.",lbgaus
15502,Regression: Support for middle mouse button (3rd button),Windows,VirtualBox 5.0.20,2016-06-12T16:44:48Z,2016-06-12T16:44:48Z,2016-06-12T16:44:48Z,"Hello,

I have a 5 button + scroll wheel mouse (Evoluent VerticalMouse 4 USB) and I want to use the middle (3rd) mouse button or scrollwheel as doubleclick in my guest system. Before VirtualBox 5.0 (versions 4.3.x) that was no problem and the middle mouse button was detected.
I use the 3rd party software ""X-Mouse Button Control"" (highrez.co.uk/downloads/XMouseButtonControl.htm) to assign mouse buttons to functions, but in VirtualBox 5.0.x the middle mouse button is only detected as left mouse button. Same goes for the scroll wheel.

The USB filter for the mouse does not work either, besides this is not an option for me because I want to use the mouse in the host and guest system.
Is there a solution?

VirtualBox 5.0.20 r106931 with installed Extension Pack
Host: Windows 7 SP1 64Bit
Guest: Windows 7 SP1 64Bit, also tried with Windows XP SP3 32Bit",Sundowner
15491,opengl change of brightness not possible,Windows,VirtualBox 5.0.20,2016-06-09T08:43:35Z,2016-06-10T07:38:45Z,2016-06-10T07:38:45Z,"We have Quake 3 Demo install on our windows 7 x64 guest. The 3d acceleration is enabled. The screen is too dark and changing the brightness in display settings of game is not working.
The host machine is windows 7 x64 too.",trivalik
15486,Cannot start VirtualBox.exe or VBoxSDL.exe because of ntdll.dll error.,other,VirtualBox 5.0.20,2016-06-07T03:44:18Z,2016-06-07T07:36:43Z,2016-06-07T07:36:43Z,"Basically what title says.
Here is the windows log for this:
{{{
  Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	5.0.21.7750
  Application Timestamp:	57515822
  Fault Module Name:	ntdll.dll
  Fault Module Version:	6.1.7601.23418
  Fault Module Timestamp:	5708a857
  Exception Code:	c0000005
  Exception Offset:	0000000000038600
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	246f
  Additional Information 2:	246f18be415dcbf9dfc6a8b7680358ac
  Additional Information 3:	246f
  Additional Information 4:	246f18be415dcbf9dfc6a8b7680358ac
}}}
The problem is I can't event get the .log file from virtualbox as it crashes too early. I was able to run virtualbox.exe in safe mode, but I'm not sure how it will help me. I've tried ""diagnostic startup"" in msconfig, and virtualbox.exe also crushes. Versions I've tried: 
* VirtualBox-5.0.21-107750-Win
* VirtualBox-5.0.20-106931-Win
* VirtualBox-4.3.38-106717-Win",DanceDance
15473,When started any virtual machine - VirtualBox crashes and pulls the machine down,other,VirtualBox 5.0.20,2016-06-02T06:20:05Z,2016-06-02T07:12:49Z,2016-06-02T07:12:49Z,When started any virtual machine - VirtualBox crashes and pulls the machine down,terrybrn
15470,"VB GUI elements are missing, Windows 10",all,VirtualBox 5.0.20,2016-06-01T04:38:22Z,2016-06-01T04:38:22Z,2016-06-01T04:38:22Z,"As described in the title, I have an issue with the VirtualBox GUI itself in which the dropdown menu is not showing correctly and looks like it's not responding.

My configuration is like this :
1. OS : Windows 10 Home x64
2. CPU : Core i7-5700HQ
3. GPU : Intel Hd Graphics 5600 + GTX960M
4. Screen resolution : 1920x1080
5. DirectX version : 12

You can see the details in these pictures below :
[[Image(http://s33.postimg.org/6sedk6c33/image.png)]]
[[Image(http://s33.postimg.org/lykfb423z/image.png)]]
[[Image(http://s33.postimg.org/ada93egmn/image.png)]]

After the bug happens, if I close VirtualBox it will remain in task manager as shown in this picture :
[[Image(http://s33.postimg.org/ubq45s1bj/image.png)]]

And if I start another VirtualBox, the GUI itself will be not displayed but a new VirtualBox process appears :
[[Image(http://s33.postimg.org/o88jlvb1r/image.png)]]

If I try to create a new VM, I couln't do that because a lot of GUI elements are missing and I can't setup the guest memory size, guest hard disk, etc

I've tried with older version of VB through 5.0.4 and they have exactly same problem in my setup

If you need more data, please let me know.

Thanks!",iede
15468,drag and drop not bidirectional,Linux,VirtualBox 5.0.20,2016-05-31T16:24:29Z,2016-05-31T16:24:29Z,2016-05-31T16:24:29Z,"Hi, I have a Windows 10 Host, with a Ubuntu 15.10 guest, Virtual Box and Guest addition latest version. When I drag and drop files from guest to host no problem, when I do it from host to guest my files go only in /tmp/VirtualBox dropped files and not where I dropped them.
I attached log files, hope it helps.
Thanks",rok
15460,Windows 10 VB Error Drag N Drop Not Working N Others More,Linux,VirtualBox 5.0.20,2016-05-30T13:00:20Z,2016-05-30T13:00:20Z,2016-05-30T13:00:20Z,"I Been Using Virtualbox for a long time, and now because of the venom shitty shit. it broke

Problems that i most have is DRAG AND DROP not working on linux and windows
I Install the Extension and my ZorinOS Broken not working anymore not booting properly. on windows 7 it work fine but i cant drag and drop back then i can i forgot the version but drag and drop is working back then, i use linux.
please fix this problem thanks man.",DogSHlT
15447,Win7 BSOD if DHCP server is On for Host-Only Ethernet Adapter,other,VirtualBox 5.0.20,2016-05-26T13:22:57Z,2016-05-26T13:22:57Z,2016-05-26T13:22:57Z,"Host is Win7 Sp1, guest seems to be irrelevant: Linux 2.6, Ubuntu, Win7 - all fail with BSOD.
The BSOD happens only if I use Host-Only Adapter and check ""DHCP Server -> Enable Server"". Without the DHCP it works.
I've also tried with the legacy driver: VirtualBox-installer.exe -msiparams NETWORKTYPE=NDIS5 - same thing.
Attaching VBox.log and the picture of BSOD, though can't attach minidump because that is not saved for some reason.",wentwog
15442,"Virtualbox doesn't refresh any window, unless you resize it. Can't use any vm at all.",Linux,VirtualBox 5.0.20,2016-05-24T11:01:19Z,2016-05-24T16:35:03Z,2016-05-24T16:35:03Z,"After installing 5.0.18, because 5.0.20 would give a critical error while installing. I tried to load my vm into virtualbox, however, nothing in virtualbox seem to refresh, so when i click on the map to import my vm, it doesn't refresh, i have to resize the window in order to refresh. When i run the vm i get a black screen, while in the preview view of virtual box i see that it works. (using windows 10, virtualization is enabled in bios, 16gb ram, 980m GT video card, should work)",TheCodeKing
15437,"""VBoxManage list runningvms"" does not work with the windows taskplaner",Linux,VirtualBox 5.0.20,2016-05-20T17:05:53Z,2016-05-20T17:05:53Z,2016-05-20T17:05:53Z,"Hello, i set up my system (Windows 6.3.9600) that the guest (Ubuntu) is starting after systemstart under the permissions of the user ""VM-Helper"" If i use the command 'C:\Windows\System32\runas.exe /user:VM-Helper /savecred ""VBoxManage startvm Ubuntu --type headless""' (running in the VB dir) i can see the status in the GUI with the command 'C:\Windows\System32\runas.exe /user:""VM-Helper"" /savecred ""VirtualBox.exe""'.
But if i start the task ""%programfiles%\Oracle\VirtualBox\VBoxManage startvm Ubuntu --type headless"" (running in the VB dir) as VM-Helper the status can't be read out by VirtualBox.exe and VBoxManage.exe list runningvms"".

I was very pleased if you can reconstruct it.
The VM starts in both cases, the permissions/user are/is right (acc. to taskmanager and log). I have tried detours over batch-files ecetera...
If i want to start the VM again over the GUI as VM-Helper with a still running instance, (of course) i'll get the error ""E_FAIL (0x80004005)""",Mike446
15436,Modify description of a running VM from vboxmanage,all,VirtualBox 5.0.20,2016-05-20T16:45:43Z,2016-05-20T16:45:43Z,2016-05-20T16:45:43Z,"I want to modify VM description from vboxmanage. But it fails if VM is running at the time:
vboxmanage.exe modifyvm myVM --description ""new descr of myVM""
vboxmanage.exe: error: The machine 'att9-1034-slave-5' is already locked for a session (or being unlocked)
vboxmanage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
vboxmanage.exe: error: Context: ""LockMachine(a->session, LockType_Write)"" at line 493 of file VBoxManageModifyVM.cpp

At the same time I can change VM description via virtualbox manager GUI.

Please, fix modifyvm (or controlvm) command to make it able change VM description while its running.
",wasapl
15434,Host only adapter is not working after host wake up,Linux,VirtualBox 5.0.20,2016-05-19T17:43:05Z,2016-05-19T17:43:05Z,2016-05-19T17:43:05Z,"hi,

I have configured host only adapter for host-guest communication (Samba). But when host (windows 7) wakes up from sleep, host adapter stops working. I tried few things on guest and host but nothing worked. Please provide some tips...

thanks,
Sai ",Sai
15415,Drag and Drop is not working bith direction,Linux,VirtualBox 5.0.20,2016-05-14T01:25:34Z,2016-05-19T13:17:59Z,2016-05-19T13:17:59Z,"Hi,
Problem 1 - trying to drag from windows desktop any file into a CentOS guest we get a disable icon in the CentOS X11 that forbidden the drop.

Problem 2 - when trying to drag file from CentOS X11 desktop to Windows desktop the transfer start and immediately halts.

host: Win 7 64 bit
Guest: CentOS 6.7 - 64Bit

Attached host & guest logs",hanken
15419,vboxguest: module verification failed: signature and/or required key missing - tainting kernel,Linux,VirtualBox 5.0.20,2016-05-15T13:33:57Z,2016-05-15T13:33:57Z,2016-05-15T13:33:57Z,"I've found the error Message mentioned above in my syslog of an Ubuntu 16.04 X64 Server) , see below.

{{{
May 14 12:00:03 fortuna kernel: [    7.962773] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
May 14 12:00:03 fortuna kernel: [    8.354372] vboxguest: module verification failed: signature and/or required key missing - tainting kernel
May 14 12:00:03 fortuna kernel: [    8.371889] piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
May 14 12:00:03 fortuna kernel: [    8.397995] vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds
May 14 12:00:03 fortuna kernel: [    8.398075] input: Unspecified device as /devices/pci0000:00/0000:00:04.0/input/input6
May 14 12:00:03 fortuna kernel: [    8.410875] vboxguest: misc device minor 55, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
May 14 12:00:03 fortuna kernel: [    8.410879] vboxguest: Successfully loaded version 5.0.20 (interface 0x00010004)
May 14 12:00:03 fortuna kernel: [    8.469950] [drm] Initialized drm 1.1.0 20060810
}}}

So on one hand an error, but on the other hand it works.
I've googled a little and found out that it has to do with Kernel Module signing.
Is there any way to fix this?

See also this thread in the Support Forum:
https://forums.virtualbox.org/viewtopic.php?f=3&t=77687",FranzS
15413,Drag and drop only working to host not the other way,Windows,VirtualBox 5.0.20,2016-05-13T18:39:12Z,2016-05-13T18:46:37Z,2016-05-13T18:46:37Z,"My windows 10 guest does not accept files vie drag and drop only the host does which is also a windows 10 machine.
hope somebody can help me Thx.
log files are attached",DerProGamer2000
15398,USB-devices with the same hardware-ID,Windows,VirtualBox 5.0.20,2016-05-08T07:27:26Z,2016-05-08T07:27:26Z,2016-05-08T07:27:26Z,"All USB-devices with the same hardware-ID (VID/PID) are sent to the guest system, although only one USB-device is selected. Have been tested modems and flash drives.",VitusSumy
15370,Exception Breakpoint,Windows,VirtualBox 5.0.20,2016-04-30T12:22:45Z,2016-05-04T06:54:13Z,2016-05-04T06:54:13Z,"Windows XP guest on a Windows 7 Host
In VirtualBox manager, upon restoring from a save state
I get a Breakpoint exception message (see attached image)
The status of the guest then becomes ""Aborted"".
Upon restoring from this state, the guest boots up correctly.
If I then Save the state of the guest,
then the next time I try to restore it I get this Exception Breakpoint message again.",keuk
15553,USB 1.1 (OHCI) controller stops working after a period of time,Linux,VirtualBox 5.0.22,2016-06-28T14:52:03Z,2017-12-12T10:11:26Z,2017-12-12T10:11:26Z,"I have 2 identical FTDI Quad RS232-HS USB virtual serial port chips connected to a Ubuntu 12.04.5 LTS guest running on Windows host (behaves the same on Win7x64 and Win10x64).
I am using USB 1.1 (OHCI) controller, but the FTDI chips are physically connected to the host via USB2.0 ports.
On VirtualBox 4.3.12 everything works just fine.
On higher versions (I tried 4.3.38, 5.0.22, 5.0.23, 5.1.0 Beta 3) I am able to open the virtual serial ports and read and write data to them for a few minutes (maybe 5) after which the communication stops and no data can be sent nor received.
When monitoring the USB ports on the guest with usbmon+wireshark, I can see no packets being sent or received after it stops working.
This only happens when 2 are connected and open at the same time. One on its own doesn't do it.
When I install the extension pack and use USB3.0 (xHCI), the problem doesn't appear.

I am attaching two logs, one running USB1.1 and one USB2.0 controllers both manifesting the issue.",rp3k
15633,Unable to uninstall VirtualBox,other,VirtualBox 5.0.22,2016-07-18T06:31:49Z,2017-10-31T06:59:46Z,2017-10-31T06:59:46Z,"See screenshot.

""The feature you are trying to use is on a network resource that is unavailable"".",Umanamente
15552,attaching differencing vhd on host makes it unusable on guest,Windows,VirtualBox 5.0.22,2016-06-28T08:18:11Z,2016-08-10T12:28:37Z,2016-08-10T12:28:37Z,"When you attach a differencing VHD on Windows host using diskpart or mmc, there's a chance that VBox will no longer understand the format of that VHD. If guest booted, it will see a corrupted filesystem.

I attach my VHD file on Windows 7 host. It's virtual size is 50G and it has one partition formatted to NTFS. I created a dummy VM in VBox GUI to manage snapshots. Currently, the chain consists of 4 image files. 

I didn't boot the guest until now. When I did, guest chkdsk spew tons of errors. Then I stopped the guest and attached the VHD on host again. chkdsk showed no errors.

I went further and restored the 'good' backup (there's a backup of all the .vhd and .vbox files I made before the guest boot). Marked the volume as readonly using diskpart and compared the contents of the block device using cygwin. They're indeed different!

",lfmeloman
15564,"NO RESPONSE from Escape, Backspace, and other keys with VirtualBox on Windows 10 host",Windows,VirtualBox 5.0.22,2016-07-03T22:07:40Z,2016-07-03T22:07:40Z,2016-07-03T22:07:40Z,"I created a Windows XP-SP3 32-bit guest (extension pack installed) running under VirtualBox 5.0.22 on a 64-bit Windows 10 host.  Everything seemed to work perfectly, except some keys such as backspace and escape, among a few others, exhibited no response.  If I VNC'd into the VM, however, those keys worked fine.  I copied the VM's VDI file onto a 64-bit Windows 7 desktop also running VirtualBox 5.0.22, and all keys worked perfectly.  As such, it seems this may be another issue revolving around Windows 10.  Host and guest were all set to standard U.S. English Keyboard, so this is not an internationalization issue.
",qd01a
15543,install path environment var not set,other,VirtualBox 5.0.22,2016-06-22T14:56:42Z,2016-06-22T15:03:11Z,2016-06-22T15:03:11Z,"The VBOX_MSI_INSTALL_PATH environment variable is not set by the 5.0.22 installer.

Tried uninstalling/re-installing, running as administrator, rebooting. nothing helped

Uninstalling and reverting to the 5.0.20 installer set the env var as expected

Installation was on a brand new Windows 10 machine (build 10586.164)",dansgeo
15540,Can't run Unity Editor due to openGL errors,Linux,VirtualBox 5.0.22,2016-06-21T15:43:03Z,2016-06-22T10:24:09Z,2016-06-22T10:24:09Z,"Not possible to run linux Unity Editor if 3D acceleration is enabled.

Starting Unity Editor fails with following error message in the log:

OpenGL Warning: glXChooseVisual: ignoring attribute 0x22
OpenGL Warning: glXChooseVisual: bad attrib=0x186a1, ignoring
OpenGL Warning: glXChooseVisual: bad attrib=0x186a0, ignoring
No valid fbconfig found
OpenGL Warning: XGetVisualInfo returned 0 visuals for 0000000000000000
OpenGL Warning: glXChooseFBConfig returning NULL, due to attrib=0x2, next=0x20
[0621/173105:ERROR:gl_surface_glx.cc(613)] glXChooseFBConfig failed.

This is Unity Editor 5.3.5f1 (http://download.unity3d.com/download_unity/linux/unity-editor-5.3.5f1+20160525_amd64.deb) running under Ubuntu 16.04.",elmir
15535,Host files with (illegal) colon in filename not visible in shared folder,Linux,VirtualBox 5.0.22,2016-06-20T09:53:47Z,2016-06-20T09:53:47Z,2016-06-20T09:53:47Z,In Windows files are created (through CygWin) having a (illegal) colon in their name. I added this folder as Shared Folder in Virtualbox. All subdirs are visible (not having a colon) but none of the files with the colon are. When the colon is removed from the filename they become visible.,CornePlas
17064,VM setting for all PC users,other,VirtualBox 5.0.24,2017-09-08T13:00:02Z,2017-09-08T13:00:02Z,2017-09-08T13:00:02Z,"we have '''VM Dos''' running on '''host windows'''.[[BR]]

our case is we need all users loged in this pc have this VM with same setting without call our helpdesk to config it.",NorMal PC
15588,USB device passthrough does not work,Windows,VirtualBox 5.0.24,2016-07-10T09:26:02Z,2017-05-02T10:34:01Z,2017-05-02T10:34:01Z,"Hello,

Since a couple of months, I'm having trouble passing through USB devices to virtual machine.
My host operating system is Windows 7 x64 Professional with all the updates and I'm running the latest version of VirtualBox (this happens with all the latest version and since I've had the problem reverting doesn't seem to do anything).

In the VirtualBox log I've found this line, which is added twice every time I try to assign a USB device:

{{{
USBPROXY usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

At the very beginning of each log file I also see the following:

{{{
usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

which I've seen in a lot of log files (not related to this problem) on the internet. I'm not really sure if this is an issue o maybe a mis-initialization.

If I re-try assigning the same USB device a second time I see the following message:

{{{
Connessione del dispositivo USB USB Flash Disk [1100] alla macchina virtuale VmXP_Temp non riuscita.

USB device 'USB Flash Disk' with UUID {a416ea81-cffc-4c89-8ce1-80a66a1aedcd} is busy with a previous request. Please try again later.

Codice 'uscita: E_INVALIDARG (0x80070057)
Componente: HostUSBDeviceWrap
Interfaccia: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

which might mean something is ""stuck"" in VirtualBox and this may not be an host issue.

The host logs don't contain anything suspicious and the guest logs too (it doesn't seem I reach a point in which the guest sees anything).

I didn't try with a Linux guest but I'm pretty sure that won't make any difference.

Thanks,
Filippo",filipposironi
15565,Host adapter showing zero bytes traffic,other,VirtualBox 5.0.24,2016-07-04T08:34:02Z,2017-01-25T09:26:28Z,2017-01-25T09:26:28Z,"On Windows 10 x64, I cannot get Microsoft Edge to connect to Virtual Box on the host adapter no matter what I try. (and I have researched this thoroughly on the web)

While trying to get the above working, I noticed that the host adapter shows 0 bytes of traffic, even though traffic is definitely passing through it.

My assumption is that there is something anomalistic with the host adapter on Windows 10, and I am hoping that it is this that is preventing Edge from accessing my guest OS.

For more info on this topic please see here:

https://forums.virtualbox.org/viewtopic.php?f=6&t=76805&sid=03dc09ac43bda2a553c78e31a5b89232&start=15
",oivey
15558,"VBoxDrvStub error: Unknown image file (NtCreateFile, Unknown Status - 5633)",Linux,VirtualBox 5.0.24,2016-06-29T16:06:49Z,2016-11-23T18:33:51Z,2016-11-23T18:33:51Z,"Host Windows 7 SP 1[[BR]]
McAfee VirusScan Enterprise Workstation, v 8.7.0.570
Ubuntu 14.04 LTE guest

Error dialog ""Error in supR3HardenedWinReSpawn"":
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status - 5633
(0xffffe9ff) (rcNt=0xe986e9ff)
VboxDrvStub error: Unknown image file
\Device\HarddiskVolume2\PROGRA~1\Oracle\VIRTUA~1\VIRTUA~1.EXE at 000000013f740000. (rc=-5633)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_NOT_KNOWN_DLL_OR_EXE (-5633) - Process Verification Failure:
An unknown and unwanted DLL was found loaded into the process.",Liberry Man
15560,Linux guest on Windows 10 host keeps freezing,Linux,VirtualBox 5.0.24,2016-06-30T07:27:56Z,2016-11-15T22:38:46Z,2016-11-15T22:38:46Z,"I have a current Debian testing VM running on a current Windows 10 host.
It started to freeze very frequently with 5.0.22. 5.0.23 r108298 (and subsequently 5.0.24) reduced the frequency of the freezes, but did not quite eliminate them.

I experienced this freeze while running Knoppix 7.6.1 on 5.0.23 r108298 as well.

The kernel started out as a 4.5 version and was upgraded to 4.6 recently (shortly before VBox 5.0.24 was released but after my switch to 5.0.23 r108298).

It seems likely that this ticket is related to #15529, as the freezes started happening with the same release and the ACPI code change revert seems to have helped (reducing the frequency of the freeze from one every couple of minutes to once or twice a day).

The symptoms for the 5.0.24 freeze were:
* While actively working with the VM, it suddenly stopped responding.
* Most of the video was frozen, with the notable exception of an open but not focused tab in Chromium - the ""page is loading"" animation remained functional.
* The VM stopped responding to SSH login attempts.
* The VM stayed this way for about 15 mins, until I forcibly turned it off.
* I tried to see whether exiting fullscreen mode would make a difference - it did not.
* After the freeze, the VM displayed no apparent disk or CPU activity.

Unfortunately, neither my notebook not my keyboard have status indicator leds, so I cannot tell whether a kernel panic occurred.",ancow
16006,virutal machine paused with clonezilla,Linux,VirtualBox 5.0.24,2016-09-30T10:32:21Z,2016-09-30T10:32:21Z,2016-09-30T10:32:21Z,"when i'm trying to clone from a vmdk image to a physical disk, the virtual box pause itself with warning when clonezilla has written the partition table to the new disk and ""informing the OS of partition table changes...""

The I/O cache encountered an error while updating data in medium ""ahci-0-1"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Fehler ID: 
BLKCACHE_IOERR
Dringlichkeit:
Normaler Fehler
",mholzer
15736,Crash in crPackExpandDrawElements () from /usr/lib64/VBoxOGLpackspu.so,Linux,VirtualBox 5.0.24,2016-08-03T11:54:32Z,2016-08-03T11:54:32Z,2016-08-03T11:54:32Z,"1.) Install Qt Creator 4.0.1 under Linux x64[[BR]]
2.) When you start it, it immediately crashes.

Workaround: disable 3D acceleration in Creator with ""qtcreator -noload Welcome -noload QmlDesigner"".

Backtrace:
{{{
#0  0x00007fffd06f2dc8 in crPackExpandDrawElements () from /usr/lib64/VBoxOGLpackspu.so
#1  0x00007fffd05773b5 in ?? () from /usr/lib64/VBoxOGLpackspu.so
#2  0x00007fffe30c7520 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib64/libQt5Quick.so.5
#3  0x00007fffe30c8ccd in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib64/libQt5Quick.so.5
#4  0x00007fffe30cf264 in QSGBatchRenderer::Renderer::render() () from /usr/lib64/libQt5Quick.so.5
#5  0x00007fffe30daa92 in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib64/libQt5Quick.so.5
#6  0x00007fffe30db127 in QSGRenderer::renderScene(unsigned int) () from /usr/lib64/libQt5Quick.so.5
#7  0x00007fffe30e977e in QSGRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib64/libQt5Quick.so.5
#8  0x00007fffe3131529 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib64/libQt5Quick.so.5
#9  0x00007fffe321298b in QQuickRenderControl::render() () from /usr/lib64/libQt5Quick.so.5
#10 0x00007fffd6180267 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5
#11 0x00007fffd61803a5 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5
#12 0x00007ffff6821cb4 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#13 0x00007ffff713ee9b in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#14 0x00007ffff70fbb6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#15 0x00007ffff7102af0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007ffff67f8795 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#17 0x00007ffff684694e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#18 0x00007ffff6846d01 in ?? () from /usr/lib64/libQt5Core.so.5
#19 0x00007ffff2e8ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007ffff2e8bc48 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007ffff2e8bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007ffff684702c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#23 0x00007ffff67f6a6b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#24 0x00007ffff78c263f in Utils::SynchronousProcess::run (this=this@entry=0x7fffffffc720, binary=..., args=...) at synchronousprocess.cpp:403
#25 0x00007fffdfd2fc88 in CMakeProjectManager::CMakeTool::run (this=this@entry=0x118e790, arg=...) at cmaketool.cpp:112
#26 0x00007fffdfd2ffc1 in CMakeProjectManager::CMakeTool::supportedGenerators (this=this@entry=0x118e790) at cmaketool.cpp:136
#27 0x00007fffdfd3d5e4 in CMakeProjectManager::CMakeGeneratorKitInformation::fix (this=0xd77f20, k=0x1449ae0) at cmakekitinformation.cpp:248
#28 0x00007fffe922bab7 in ProjectExplorer::KitManager::addKit (this=this@entry=0x9dfc30, k=0x1449ae0) at kitmanager.cpp:518
#29 0x00007fffe922f1e9 in ProjectExplorer::KitManager::restoreKits (this=0x9dfc30) at kitmanager.cpp:204
#30 0x00007fffe91cfff2 in ProjectExplorer::ProjectExplorerPlugin::delayedInitialize (this=<optimized out>) at projectexplorer.cpp:1518
#31 0x00007ffff7bbe6fa in ExtensionSystem::Internal::PluginSpecPrivate::delayedInitialize (this=0x6baa40) at pluginspec.cpp:1025
#32 0x00007ffff7bbb025 in ExtensionSystem::Internal::PluginManagerPrivate::nextDelayedInitialize (this=0x66e6e0) at pluginmanager.cpp:830
#33 0x00007ffff68207d5 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#34 0x00007ffff682dda2 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5
#35 0x00007ffff6821cb4 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#36 0x00007ffff70fbb6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#37 0x00007ffff7102af0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#38 0x00007ffff67f8795 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#39 0x00007ffff684694e in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5
#40 0x00007ffff6846d01 in ?? () from /usr/lib64/libQt5Core.so.5
#41 0x00007ffff2e8ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#43 0x00007ffff2e8bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#44 0x00007ffff684702c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#45 0x00007ffff67f6a6b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#46 0x00007ffff67fe866 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#47 0x000000000040a0d9 in main (argc=1, argv=<optimized out>) at main.cpp:527

}}}
",bmn
15595,RDP sends scroll wheel events to wrong monitor,Linux,VirtualBox 5.0.24,2016-07-12T16:10:46Z,2016-07-12T16:10:46Z,2016-07-12T16:10:46Z,"Using the RDP with a dual head display mouse scroll wheel events are being sent to the wrong monitor.  When the mouse is on the second monitor, scroll wheel events are sent as if they were on the first monitor which causes a focus change and other bad behaviour.

xev running on the console shows the events correctly as coming from the second display (coordinates 2593,264):


{{{
ButtonRelease event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 684071, (2,107), root:(2593,264),
    state 0x1000, button 5, same_screen YES

}}}

But when using RDP the same events are received as if they are on the first head, instead of the second display:


{{{
ButtonPress event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 796041, (75,120), root:(97,283),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 39, synthetic NO, window 0x4400001,
    root 0x141, subw 0x0, time 796041, (75,120), root:(97,283),
    state 0x1000, button 5, same_screen YES

}}}

The mouse was at 97,283 on the second display, which should have been sent as 2657,283sip.

This problem does not occur with VNC, but is present in 5.0.24 as well as the 5.1 beta and does not seem to depend on window manager or host extension version.

As an additional confusing point, if there is any mouse motion at the same time as the scroll wheel event then the events are sent at the correct coordinates on the second head.",thudson
15592,"Upgrade from 5.0.8 to 5.0.24 causes ""FATAL: no bootable disk found""",Windows,VirtualBox 5.0.24,2016-07-10T22:39:59Z,2016-07-10T22:39:59Z,2016-07-10T22:39:59Z,"In a Windows 7 64bit host, running a guest Windows Standard 2012 virtual machine would not boot with ""no bootable disk found"" error.  Reverted back to 5.0.16, and started working again.  Noticed Storage changed on 5.0.24 from SATA to IDE, suspect this is the cause of the ""no bootable disk found"" error, but did not confirm.",Lula
15562,Imperfect string matching when VBox suggests machine type by its name,all,VirtualBox 5.0.24,2016-07-01T10:45:34Z,2016-07-01T10:45:34Z,2016-07-01T10:45:34Z,"Hi guys,

Looks like there is a small problem with how VBox decides on the type of OS by the name of a new virtual machine.

I entered ''Ubuntu 16.04 (restored)'' as a name for the new VM and noticed that after typing ''restored'' the version of the machine changed from ''Ubuntu'' to ''Red hat''. It seems like the regexp matcher considers ''red'' in ''restored'' as a hint while it should not. The solution is rather simple - not to consider the keywords as hints if the words do not start with them.

Another name I just tried is ''Ubuntu twin''. As in the first case, the suggested type of the OS changes from ''Ubuntu'' to ''Windows'' just after typing ''n'' in ''twin''.",kachkaev
15556,Windows 10 consistent video freeze,Windows,VirtualBox 5.0.24,2016-06-29T10:45:21Z,2016-06-29T10:49:43Z,2016-06-29T10:49:43Z,"Running on Windows 10 guest on a Windows 10 host with VB 5.0.24, updated extensions on the guest.

Under load, the video freezes requiring the VM to be restarted.
This happens constantly and makes the VMs unusable.

Tried to run VM with debug but the console command doesn't show any console.
Attaching the relevant vbox.log.",EPinci
15555,[Feature Request] More Video Memory,Windows,VirtualBox 5.0.24,2016-06-28T22:00:05Z,2016-06-28T22:00:05Z,2016-06-28T22:00:05Z,"Modern graphics cards have 6GB+ video memory, please allow us to use more than 256mb for VMs.",Stanzilla
16053,Multi Monitor: Atypical configurations - mouse desync from window dragging,Windows,VirtualBox 5.0.26,2016-10-10T08:54:32Z,2022-12-22T07:25:35Z,2022-12-22T07:25:35Z,"Host: Windows 10, VBox 5.0.26, 3 monitors

Guest: Windows 10, GA VBox 5.0.27r111132, 3 monitors

Steps to reproduce: In Guest Windows display settings, change monitor order into something atypical or just change order from 1-2-3 to 3-2-1. Or use something atypical like 1-3, then 2 below.

What happens ? You can move Window when dragging but there is no way to move cursor according to guest OS configuration. Basically mouse cursor movement is desynced from window movement (while dragging windows across monitors). This is wrong and a bug.

When Multi monitor is configured in atypical way, like:
{{{
1+3
 2  (below the others)
}}}

-or-

{{{
3-2-1
}}}

Expected behavior: It should behave like host, move cursor where it is allowed to. Move windows where it is allowed to.

-Technologov, 10.10.2016.",Technologov
16463,"""Operation not permitted"" on file in shared folder",Linux,VirtualBox 5.0.26,2017-02-07T21:33:01Z,2017-02-28T19:41:09Z,2017-02-28T19:41:09Z,"* Host: Windows 7 x64
* Guest: Linux CentOS 6.7 x64 ( VirtualBox Guest Additions 5.0.26 r108824 )

If you look at ticket #4890, which is very likely the same underlying issue, the most recent comment is still reporting the issue on 5.1.12

In a vbox shared folder:
{{{
[user@server ~]$ mount | grep vboxsf
sv on /sv type vboxsf (uid=500,gid=500,rw)
[user@server ~]$ sudo touch /sv/a.txt
[user@server ~]$ sudo chmod a-w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
rm: cannot remove `/sv/a.txt': Operation not permitted
[user@server ~]$ sudo chmod a+w /sv/a.txt
[user@server ~]$ sudo rm -f /sv/a.txt
[user@server ~]$
}}}

Not in a vbox shared folder:
{{{
[user@server ~]$ sudo touch /a.txt
[user@server ~]$ sudo chmod a-w /a.txt
[user@server ~]$ sudo rm -f /a.txt
[user@server ~]$
}}}

Possible related tickets:
* https://www.virtualbox.org/ticket/4890
* https://www.virtualbox.org/ticket/5568
* https://www.virtualbox.org/ticket/15083",bompus
16024,Win10 host Ubuntu 16.04 guest random crashes,Linux,VirtualBox 5.0.26,2016-10-04T08:05:56Z,2016-12-07T10:02:03Z,2016-12-07T10:02:03Z,"I am using Ubuntu 16.04 with X on Win10 host. It randomly crashes from time to time. I found a remedy. If I select Other 64bit OS from the settings, it does not crash anymore. Below is the Vbox.log file from a crashed machine (after machine was force shut down).
",yurtesen
16174,HPE Smart Storage Administrator utility lockup error 851,Linux,VirtualBox 5.0.26,2016-11-09T17:01:13Z,2016-11-09T17:01:13Z,2016-11-09T17:01:13Z,"Long time we have curious trouble with virtualbox.
HOST W2012 64 SERVER HP ProLiant ML310e Gen8
When we use smart array gui or utility , this report on Dynamic Smart Array B120i RAID
851 Controller lockup error: Restart the server and run a diagnostic report. Install the latest version of controller firmware. If the condition persists, the controller may need to be replaced or require service 

This error ocurs when virtualbox is run and use direct hardware access with VTx.
Guest os is openSUSE 64 13.1 

Issue not change more as year and last four kernels...

When vbox is off lockup not present, when no hardware direct , too no lockup, but Linux guest system is unstable .

Raid Works ok with or without lockup, but with lockup we cant control raid status. HP utility show nothing in error state.

Dynamic Smart Array B120i RAID controller have latest drv and fw.
Issue tested on 5.0.4 - 5.0.26 i mean next too but not tested now.

Please help.
",mguru
16089,MultiMonitor: Guest mode hints do not accept negative numbers for xOrigin in setModeHint.,Windows,VirtualBox 5.0.26,2016-10-20T12:20:33Z,2016-10-20T12:26:58Z,2016-10-20T12:26:58Z,"The source of the bug is in VBoxHelpers.cpp (hlpResizeRect)
it attempts to maintain monitor order on display resize by comparing the monitor rectangles after the resize and finding intersections between adjacent (according to the previous monitor order) rectangles.

The problem happens if the monitor order changes - for instance, suppose we have 2 monitors - 0 and 1. 
{{{
---------- ---------
|   0    | |   1   |
---------- ---------
}}}
Suppose monitor 0 is 1024x768 starting at 0,0 and monitor 1 is 800x600 starting at 1024,0.
Suppose we call setvideomodehint with monitor 1 being moved to -1024,0 in order to move it to the left of monitor 0. 

What will happen now is that when we look for monitors X-positive adjacent to monitor 0, we'll find monitor 1.
The current code to check whether the monitors now intersect (post potential resize) is: 
(assume iRect=0 and iNextRect=1)
{{{
int delta = paNewRects[iRect].right - paNewRects[iNextRect].left;
}}}
this will result in 1024 (right of monitor 0) - -1024 (new left of monitor 1) = 2048.
next, 
{{{
        if (delta != 0)
        {
            DDCLOG((""XP intersection right %d left %d, diff %d\n"",
                     paNewRects[iRect].right, paNewRects[iNextRect].left,
                     delta));

            paNewRects[iNextRect].left += delta;
            paNewRects[iNextRect].right += delta;
        }
}}}
since delta != 0, we will now move monitor 1 on the x axis by 2048, which will lead to monitor 1 
being in the exact same location before we tried to move it. 
(-1024 + 2048 = 1024)
and we'll end up with the original monitor layout. 


Note the processing of the mode hint event from line 1689 in the log file.
",GilB
16077,"Audio: When undocking a laptop, VirtualBox cannot switch to a different sound output",other,VirtualBox 5.0.26,2016-10-18T13:56:43Z,2016-10-18T13:56:43Z,2016-10-18T13:56:43Z,"Host: Win10, VBox 5.0.26

Guest: Win10, x64

When undocking a laptop from a dock station, I expect VirtualBox to automatically switch to a different audio-out device. For example, WinAmp music player on native host does it correctly.

Sadly, VBox doesn't, which makes it impossible to use Skype or listening audio/video with docking station.

Steps to reproduce:
1. Start any music player or VoIP program in Windows (7 or 10) guest
2. Undock (unplug) laptop from docking station (which includes a separate USB Sound Blaster device)

Expected result:
Music should keep playing with max. 1 second audio drop

Actual result:
Music stops playing completely.

-Technologov, 18.10.2016.",Technologov
16034,Connection lost in guest when restart failed due to lack of memory,Linux,VirtualBox 5.0.26,2016-10-05T14:30:24Z,2016-10-06T12:59:59Z,2016-10-06T12:59:59Z,"Sometimes, at startup, VirtulBox complains about the lack of memory (I didn't write down the exact message) and I have to close the VM and launch it again. Then it works. I don't mean restarting the guest. Just record the state of the machine, close the application and run it again.

This is not a big deal and I assume it is due to a lack of RAM on the host, so nothing VirtualBox can do much about.

The issue is that when I do that, sometimes (maybe each time, I'm not 100% sure this is systematic), I lose the connection.

Rather than restarting the guest, this can be solved by restarting network-manager service:

    systemctl restart network-manager

Not sure what the root-cause is and if VirtualBox is to blame. At least if someone encounters the same issue, a workaround is documented here.

Host: Windows 7
Guest: Linux Debian Jessie

There's nothing specifically related in the VM log.",JerNob
15918,"Bad 3D performance, maybe related to: VERR_BAD_EXE_FORMAT atikmdag.sys",Linux,VirtualBox 5.0.26,2016-09-12T09:10:25Z,2016-09-13T21:52:24Z,2016-09-13T21:52:24Z,"I have had strange 3D performance problems with VirtualBox while everything was working fine with VMWARE.

I reported the issue in the forum first:
https://forums.virtualbox.org/viewtopic.php?f=3&t=79456

Thanks to 'Perryg', he found out a line in the log which shows VirtualBox is broken/faulty clearly.


{{{
    00:00:08.740768 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: rc=VERR_BAD_EXE_FORMAT fImage=1 fProtect=0x5 fAccess=0x2 \Device\HarddiskVolume4\Windows\System32\drivers\atikmdag.sys:
}}}
 

This is not a problem in the file itself because all windows programs which use the GPU work fine and also VMWARE works fine, in addition the problem was with multiple versions of the drivers in different computers. See:
https://community.amd.com/thread/195664

If you read the person's post. He even tried multiple versions of the driver. I have in my laptop the drivers which come with Windows Update and signed properly and function properly. So the file is perfectly fine!

Thanks",yurtesen
15909,No notification of major new releases,Linux,VirtualBox 5.0.26,2016-09-08T13:06:06Z,2016-09-08T13:06:06Z,2016-09-08T13:06:06Z,"VB 5.0.26 was released on July 18, 2016. It wasn't until I browsed virtualbox.org on Sept. 8, 2016 that I learned that there was a major dot release (x.0 to x.1) available that had two maintenance releases after July 18. It appears that the built in upgrade notification is failing to notify when stable dot releases are available (I am assuming that a second maintenance release of a dot release = stable).",Aren Cambre
15712,Mouse Integration and USB 3.0 Controller Problem,Windows,VirtualBox 5.0.26,2016-07-29T12:54:09Z,2016-07-29T12:54:09Z,2016-07-29T12:54:09Z,"Using a Windows 7 64 bit guest and setting USB 3.0 controller.

When running the guest the mouse integration is greyed out and clicking in the guest screen requires to re-capture the mouse, when this is done the mouse pointer will not traverse the whole of the guest screen, making it impossible to use the desktop fully.

I have attached the correct log file this time.
",Solrac42
15640,Existing CPU is not supported?,Windows,VirtualBox 5.0.26,2016-07-18T22:23:48Z,2016-07-19T18:35:12Z,2016-07-19T18:35:12Z,"I tried to update one of my guess Win 7 to Win 10 and it failed saying it was an unsupported cpu (xeon e5405).

Thing is, Win10 upgrade thinks the CPU is fine on the host computer witch is the same CPU (see screen shoots supplied in zip file with logs)",isgdre
16398,Boot up of Windows 7 VM running on Windows 10 post upgrade to v5.0.32 crashed,Windows,VirtualBox 5.0.32,2017-01-17T19:46:10Z,2017-01-18T16:58:31Z,2017-01-18T16:58:31Z,"Windows 10 Host
Windows 7 Guest
vBox v5.0.32

Post upgrade to VirtualBox v5.0.32 the Windows 7 Guest crashed during boot up.
",n3kfh
14645,Shared Clipboard some time stop working,Windows,VirtualBox 5.0.4,2015-09-29T16:43:14Z,2020-01-27T12:17:44Z,2020-01-27T12:17:44Z,"Sometimes the shared clipboard stops working and I need to reboot the machine or stop and restart VBoxTray.exe.
I do not have details on why it happens so I can not put the steps to reproduce the anomaly.",bmn
14632,Double click not working with precision touchpad -> believed fixed in releases greater than 5.1.24,all,VirtualBox 5.0.4,2015-09-24T16:56:31Z,2018-02-19T15:33:15Z,2018-02-19T15:33:15Z,"Hi! Im using an Acer Aspire Nitro v17 (VN7-791G-76Z8) which has Precision Touchpad (the new touchpad standard which enables to use all Windows 10 gestures). Im using VirtualBox 5.0.4 with 5.0.4 extensions and Windows 10 x64 Home as Host and Windows 7 x86 as guest (the same error happens in Windows x64 as guest). The problem is that when using the touchpad, I cannot use double click in the guest but I have to do 3 clicks instead to get the double click effect (trust me, that extra click annoys me a lot). If I use a standard mouse, there is not problem.",matias-uy
14597,5.0.4 - Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR,Linux,VirtualBox 5.0.4,2015-09-16T06:44:47Z,2015-11-25T16:09:23Z,2015-11-25T16:09:23Z,"I've been using VirtualBox for a while 4.3.18 - 4.3.30 where i have a VM with a live snapshot.
after upgrading to 5.0.4 i've got a problem on my 4.3.30 created VM: ""Guru Meditation - VERR_REM_VIRTUAL_CPU_ERROR""
reverting back 4.3.30 runs the VM fine but not with 5.0.4

Host: Windows 7 x64
guest: Linux based OS

see also: 
[https://forums.virtualbox.org/viewtopic.php?f=6&t=70070]
",talr
14630,Duplicate host-only Interface name on Windows 10,all,VirtualBox 5.0.4,2015-09-24T11:48:15Z,2015-11-20T19:46:16Z,2015-11-20T19:46:16Z,"Hi guys, 

There's an anoying bug on '''Windows 10'''.

When creating host-only interfaces, sometimes, a popup appears saying:
 Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

This blocks the interface creation.

When clicking the ""OK"" button, VBoxManage resume the operation and create an interface with a name like 'VirtualBox Host-Only Ethernet Adapter #X'
Eventualy, VBoxManage command ends, saying:
 Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created
'''Notice that it is not the actual name of the interface.'''

To reproduce the issue, just run {{{VBoxManage.exe hostonlyif create}}} a couple of times.

Tested on Windows 10, with VBox 5.0.4 and latest test build (5.0.5)",srats
14638,VT-x is not available Error while launching Android VM,Linux,VirtualBox 5.0.4,2015-09-25T22:26:28Z,2015-10-02T18:11:26Z,2015-10-02T18:11:26Z,"Hello,

I am experiencing an error anytime I try to run an android Nexus 4 (KitKat) virtual machine. The error details are as following : 


""VT-x is not available (VERR_VMX_NO_VMX).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
"" 

So far what I have read is that this error indicates the computer does not support virtualization when in fact my machine does.
Here are my computer specs:
Asus K55VD Laptop
Intel core i7-3630QM @2.40ghz
8.00gb ddr3 RAM
Samsung 850 EVO SSD",kingjulian
14614,Virtualbox kills keyboard when running on Windows 10,other,VirtualBox 5.0.4,2015-09-21T04:56:50Z,2015-09-29T17:11:19Z,2015-09-29T17:11:19Z,"OS: Windows 10 build 10240
Virtualbox version: 5.0.4-102546 and 5.0.5-102676

Description:

VirtualBox kills my keyboard every time it is run. Note that this happens when VirtualBox is running for some time, even without starting any VM. 

I fresh installed VirtualBox in my new Windows 10 machine (it's a newly built PC with no PS/2 port on the motherboard, so I am using a USB keyboard). Since it's a fresh install the first thing I do is to create a new VM. The keyboard suddenly died out when I attempt to specify where to store the VM files. All LED went off, and pressing the NumLock/CapsLock/ScrollLock keys won't trigger any LED back on. At first I thought it may be the cable of my keyboard got loose. So I checked but found no problem. Unplugging and plugging the keyboard to the same or different USB ports didn't help. Windows even didn't play any sound that indicate a device is being plugged in/unplugged.

I was afraid that it is the motherboard having some issues, but luckily the keyboard came back when I reboot the machine. I tried several times and the result is still the same.

It seems that only the USB keyboard is affected. The mouse still works.

In my experience, keyboard dies after about 1-2 minutes of usage in the stable (5.0.4-102546) build. Using the latest test build (5.0.5-102676). keyboard dies out after about 10 minutes of usage.

I found one similar case in the forum [1]. The op is working on a laptop, while I am working on a desktop.

Not sure if related to the issue, my Windows 10 machine also runs VMWare workstation . 

[1] https://forums.virtualbox.org/viewtopic.php?f=6&t=70081",cytam
14631,Host-only interface IP changes on Windows 10,all,VirtualBox 5.0.4,2015-09-24T12:50:56Z,2015-09-24T12:50:56Z,2015-09-24T12:50:56Z,"When using host only network interfaces on Windows 10, the interface IP address changes and the interface is not working anymore.



'''Reproduction (easy way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Open Windows 10 network settings (Control Panel\Network and Internet\Network Connections)[[BR]]
4 - Notice that the newly created network interfaces uses DHCP configurations instead of manually configured settings.[[BR]]




'''Reproduction (hard way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Create a Linux guest (such as Ubuntu 15.04), and attach it's first network adapter to the host-only interface.[[BR]]
4 - Run the guest (I chose to run in live mode to avoid to install the OS). It usually gets the first ip available, 192.168.56.101 in our case[[BR]]
5 - Ping the host interface from the guest: ping 192.168.56.1[[BR]]
6 - Check the host interface IP: it has changed to 192.168.56.102 and the host-only interface does not work anymore.[[BR]]




Tested on VirtualBox 5.0.4 and latest testing 5.0.5.[[BR]]
Tested with Linux guests (Android, Ubuntu).[[BR]]
Reproduce on Windows 10 host.[[BR]]
Can't reproduce on Linux (Ubuntu, Fedora, Debian), Mac OS (10.8, 10.9 and 10.10), Windows 7 and Windows 8.1 hosts.[[BR]]",srats
14616,Firefox.com Firefox can't completely Download files,Linux,VirtualBox 5.0.4,2015-09-21T13:46:37Z,2015-09-22T15:26:48Z,2015-09-22T15:26:48Z,"I have been running into what appears to be a bug with !VirtualBox.  

Host OS is Windows7 SP1 x64 with the latest updates.
Guest OS is Centos 7.1 x64 with the latest updates. 

When we use Firefox from www.firefox.com,  it freezes when we try to download a file.

Steps to reproduce:

1.  Start Guest OS
2.  Immediately launch Firefox (38.2.1ESR or the latest 40.x release) and try to download a file (In our case, it is a epub file, http://www.cse.yorku.ca/~jr/epub/w/CV.epub)
3.  Firefox should them freeze

If you close the VM and restart the VM, Firefox should be able to download the file. If you reboot the host and retry the steps above you will reproduce the FF download failure. 


If you look a Wireshark trace during the download you actually see the file start to download, but it seems that it isn't getting fully processed/closed/or TCP session closed. 

Google Chrome/wget  doesn't have this issue. It seems to tied to the FF from firefox.com

I am able to reproduce this with !VirtualBox 5.0.2 and 5.0.4. !VirtualBox 4.3.30 doesn't have this issue.

See the attached log and network captures.",paulg.ca
14624,STATUS_OBJECT_NAME_NOT_FOUND,Windows,VirtualBox 5.0.4,2015-09-22T12:15:12Z,2015-09-22T12:15:12Z,2015-09-22T12:15:12Z,"VirtualBox build: 5.0.5-102800-Win

Host: Windows 10
Guest: any VM (Windows XP, Ubuntu, CentOS)

Message error:
""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)Make sure the kernel module has been loaded successfully.
where: supR3HardenedWinReSpawn
what:  3
VERR_OPEN_FAILED (-101) - File/Device open failed.
Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.""

Driver verifier disabled for :
vboxnetadp6.sys
vboxnetlwf.sys
vboxusbmon.sys

I can boot any VM with the driver verifier disabled for all drivers, not when only disabled for the oracle drivers above.

Wich  others drivers must get out  of Driver Verifier ?

",Leonardo Lira
14569,Full screen flicker Linux guests,Linux,VirtualBox 5.0.4,2015-09-10T14:12:23Z,2015-09-21T07:58:46Z,2015-09-21T07:58:46Z,"Hello.

I installed VirtualBox 5.0.4 and have tried to install various distributions (Ubuntu 14.04 and Debian 8). In all, after installing the ""guest additions"" when I put the screen in ""full screen"" mode gives me small black image flashes. For example when you open the Control Panel Ubuntu or run a program. If I'm in windowed mode it works perfectly.

I have the following equipment:

Windows 8.1
FX8350
32 GB of RAM
GTX 760
2560x1440 resolution monitor

However on my laptop which has exactly the same software works perfectly full screen. The laptop has the following features:

Windows 8.1
Intel i7 4700-HQ
16 GB of RAM
GTX 750m
1920x1080 resolution monitor

I tried to change the resolution of the desktop PC to 1920x1080 and also happens.

P.D. Sorry for the translation

Thanks",bysurferox11
14603,"Installation fails on Windows 7 trying to access ""quick launch"" folder",other,VirtualBox 5.0.4,2015-09-16T23:55:50Z,2015-09-16T23:55:50Z,2015-09-16T23:55:50Z,"Our company employs a domain policy to direct each user's ""Application Data"" folder to a network share. Attempting to install VirtualBox 5.0.4 fails when attempting to access the ""Microsoft/Internet Explorer/Quick Launch"" sub-folder of ""Application Data"" because it resets network connections (thereby cutting off access to network shares) prior to accessing that folder. Upon failing to access the quick launch folder the installation fails (giving the user no option to continue even though the problem is minor) and rolls back the installation, leaving the existing host-only ethernet adapter drivers in a corrupted state.

I have tried the following steps to work around this problem:

1. Tell the installer not to add VirtualBox to the quick launch or start menu. (The installer ignores the user's request and still tries to access the quick launch folder)
2. Tell the installer not to install the network device drivers. (The installer resets network connections even though this is unnecessary)

Possible solutions to fix this problem:

1. Add VirtualBox to the Quick Launch and Start Menu (if the user requests it) *before* resetting network connections; or
2. After installing the network device drivers, ensure that network connections are properly re-established before attempting to access the Quick Launch and Start Menu folders; or
3. Give the user the option of continuing with the installation even if adding VirtualBox to the Quick Launch and Start Menu folders fails.

The same problem occurs when attempting to upgrade to version 4.3.30. I would really like to upgrade to a more recent version of VirtualBox (I'm stuck on 4.3.26) but I can't because I simply can't install any newer version.
",srgerg
14582,Hostonlyif not fully initialized after create returns successful,other,VirtualBox 5.0.4,2015-09-13T18:31:40Z,2015-09-14T04:14:39Z,2015-09-14T04:14:39Z,"When creating a new hostonlyif it appears that the adapter is not fully initialized when create returns success

Host OS - Windows 10 Build 10240
Virtual 5.0.4 - release and 5.0.5 102614

Example (note the garbage netmask returned)

{{{
vboxmanage hostonlyif create && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            336f5edf-a838-43a1-a55f-7955e605ee59
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     15.0.0.0
IPV6Address:     fe80:0000:0000:0000:384b:5e06:3257:bdb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

Here's the same example with ipconfig

{{{
vboxmanage hostonlyif create && ipconfig
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Windows IP Configuration

Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::8d8e:d529:1359:8373%22
   Default Gateway . . . . . . . . . :

}}}

If we wait ~5 seconds after creation and use list hostonlyifs we get the correct information

{{{
vboxmanage hostonlyif create && timeout 5 && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Waiting for 0 seconds, press a key to continue ...
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            c0b80be6-b9d2-499e-855b-b7043f26eec5
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:a541:cd37:5679:1f0c
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

This is big problem for tools like docker-machine,etc.
",ronwilliams
14566,E_FAIL (0x80004005) MediumWrap.cpp[2245],all,VirtualBox 5.0.4,2015-09-10T08:02:14Z,2015-09-11T07:59:48Z,2015-09-11T07:59:48Z,"Ever since the upgrade to VirtualBox 5 I'm unable to add/modify storage controllers or optical drivers.
Either VirtualBox crashes or quits silently. Error is still present even with 5.0.4.2546.",wpa1160
14560,Regression - networking broken after upgrade to 5.0.0 and also subsequent updates,all,VirtualBox 5.0.4,2015-09-09T09:18:54Z,2015-09-10T19:01:26Z,2015-09-10T19:01:26Z,"This worked with 4.3.x, but the problem started with upgrade to 5.0.0 from 4.3.28, but continues with every minor update - after installation, start-up of every virtual machine reports:

  Cannot connect to the network interface '\DEVICE\{C5EF3C32-2A5B-4649-B646-5A5D3A3BB319}'. The virtual network card will appear to work but the guest will not be able to connect. Please choose a different network in the network settings.

The problem is with !VirtualBox Host-Only Ethernet Adapter.

I tried to restart computer after update, but still the same problem.

Removing and re-adding !VirtualBox Host-Only Ethernet Adapter from !VirtualBox menu does not help.

The Device Manager with ""Show hidden devices"" option enabled shows that ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" has exclamation mark with detail ""This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"".

Please note that I am using 192.168.150.0/24 network for !VirtualBox Host-Only adapter (IP 192.168.150.2, mask 255.255.255.0, DHCP 192.168.150.3, dynamic address from 192.168.150.100 to 192.168.150.199), because ''the default address 192.168.56.0/24 is my regular network''.

When I uninstall and install !VirtualBox, the ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" device still reports the same problem. I need to uninstall !VirtualBox first, reboot and install !VirtualBox afterwards in order to get the networking up-and-running again (after changing the IP and DHCP of the Host-Only adapter from !VirtualBox menu).

This is reproducible with every update, starting from 5.0.0.

I am using Windows 7.

Do you need more info from me?",oldium
14561,Failed to open a session for the VM (0x80004005  Component:  MachineWrap),Linux,VirtualBox 5.0.4,2015-09-09T11:14:15Z,2015-09-09T11:29:06Z,2015-09-09T11:29:06Z,I have a problem. Not start a new VM,SergeyO
14559,"GUI: ""Ungroup"" fails",Linux,VirtualBox 5.0.4,2015-09-09T08:31:38Z,2015-09-09T08:31:38Z,2015-09-09T08:31:38Z,"I created a group with the same name as the only single VM in it, ""oS-TW"", using the ""Group"" feature new in 5.0.  When trying the ""Ungroup"" function, I get the following error:

{{{
Failed to save the settings of the virtual machine oS-TW to C:\Users\voelkerb\VirtualBox VMs\oS-TW\oS-TW\oS-TW.vbox.

Could not rename the directory 'C:\Users\voelkerb\VirtualBox VMs\oS-TW\oS-TW' to 'C:\Users\voelkerb\VirtualBox VMs\oS-TW' to save the settings file (VERR_ALREADY_EXISTS).

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
}}}

The VBox.log remains untouched during this, thus not attached.",berny
17415,VirtualBox - Error In supR3HardenedWinReSpawn when the starting the VM,Windows,VirtualBox 5.0.40,2018-01-03T16:40:43Z,2018-01-03T18:38:49Z,2018-01-03T18:38:49Z,"I am using VirtualBox 5.0.40 and I have created a VM which has Windows XPMode configured.
When I am starting the VM, I am getting the below exception pop up with the error message:

VirtualBox - Error In supR3HardenedWinReSpawn

(rc=-5640)

Please try reinstalling VirtualBox.

where: supR3HardenedWinReSpawn 
what: 1 VERR_SUP_VP_THREAD_NOT_ALONE
(-5640) - Process Verification Failure: 
The process has more than one thread.

When I click the OK, it brings another exception pop up with the below error message:

VirtualBox - Error

Failed to open a session for the virtual machine 'My Guest Machine'

Details
The virtual machine 'My Guest Machine' has terminated unexpectedly during startup with exit code 1(0x1).
More details may be available in 'C:\Users\myuser\VirtualBox VMs\My Guest Machine\Logs\VBoxHardening.log'. 

I clicked OK to close the window.

But when I start the VM again, it launches successfully with out any error.
But at times when I start again after the above mentioned error, it is not launching and give the same error.
This behavior is inconsistent.

Could you please suggest me any possible fix to avoid this error?",PbuHCL
16992,Linux filesystem through share folder will be data crash,Linux,VirtualBox 5.0.40,2017-08-08T18:53:35Z,2017-08-10T20:44:24Z,2017-08-10T20:44:24Z,"Host Windows 7, Phy 16 GB RAM[[br]]
Guest Linux Centos 6.8, Virtual 3 GB RAM[[br]]
/share is share folder on Windows NTFS.[[br]]
[[br]]
Reproduce command:[[br]]
*---------- Start[[br]]
dd if=/dev/zero of=/share/tmp_fs bs=1M count=300[[br]]
mkreiserfs -f /share/tmp_fs[[br]]
mount -o loop /share/tmp_fs ~/x[[br]]
touch ~/x/mark (or copy anything to there)[[br]]
umount ~/x[[br]]
*---------- End[[br]]
[[br]]
Now, if you re-mount tmp_fs, you will found nothing in filesystem, and if you fsck on it, it will show filesystem broken.[[br]]
[[br]]
On 5.0.28, all thing are fine[[br]]
On 5.0.40 and above 5.1.x (Note: I don't try on 5.0.30 - 5.0.38), you will catch the bug.[[br]]
",C-MIKE
14727,"With Windows 10 host, VirtualBox guest window jumps between monitors",Linux,VirtualBox 5.0.6,2015-10-21T13:25:08Z,2016-11-29T14:00:32Z,2016-11-29T14:00:32Z,"With a Windows 10 x64 host using multiple monitors, the VirtualBox guest window now jumps between monitors. When it jumps, it always jumps from monitor 2 (extended desktop) to monitor 1 (main desktop). It jumps under these circumstances:
* resizing guest window, especially when the mouse cursor is close to the screen edge
* when guest window changes from text only mode to GUI mode (guest is Ubuntu 15.10, so it starts in text mode upon boot and switches back to text mode for a several seconds at the end of a shut down)
* when moving guest window while mouse is close to screen edge

I am aware of Windows's Aero Snap feature, starting with Windows 7, where dragging windows to the edge of the monitor causes the windows to be maximized or positioned differently. I am not activating this feature. Also:
1. this feature does not cause windows to jump between monitors
1. this feature did not cause problems with VirtialBox when using Windows 7, 8, or 8.1 as a host
1. no other program on my PC exhibits this behvaior

This happens despite the fact that I clean installed Windows 10 and VirtualBox twice. This has happened with all versions of VirtualBox that came out since about a month after Windows 10 RTM was released.

I normally have VirtualBox close to maximized in my monitor 2. By close to maximized, I mean I have about a 10-20 pixel margin around all sides of the guest OS window. That means I am having to drag the guest OS window extents near to but not at the monitor edge.

I am actually on VirtualBox 5.0.8. That was not available as an option in the '''Version''' dropdown.

(#12209 could be related, but I don't think it's the same.)",Aren Cambre
14703,shared folders not mounting,Linux,VirtualBox 5.0.6,2015-10-15T07:10:04Z,2016-03-17T13:39:08Z,2016-03-17T13:39:08Z,"I can't see any shared folders on a debian (jessie) guest, win7 host. The shared folders are set up correctly, This is 5.0.6, with the guest additions rebuilt. This used to work on 5.0.0, not sure if the change to 5.0.6 caused it, or something else (debian update).

error is /sbin/mount.vboxsf: mounting failed with the error: No such device

sudo modprobe -a vboxguest vboxsf vboxvideo
solves it - is that a bug in the guest additions or the OS?

This post pointed me in the right direction:
http://stackoverflow.com/questions/28328775/virtualbox-mount-vboxsf-mounting-failed-with-the-error-no-such-device
Thanks
Nils",Nils
14728,Virtualbox crash when closing laptop lid,other,VirtualBox 5.0.6,2015-10-21T14:27:39Z,2016-01-25T16:51:46Z,2016-01-25T16:51:46Z,"I have been able to get the person who has this issue to work around it.

One of our guys has an issue where if you close his laptop lid with virtualbox running it crashes and the vm goes into aborted state.

Via our helpdesk:-

""The instruction at 0x69866f99 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program""

Does not go away when disabling 3d accelleration

",lotsofjam
14778,Multi-monitor setup - screens swapped,Windows,VirtualBox 5.0.6,2015-11-03T11:14:53Z,2015-12-02T14:13:48Z,2015-12-02T14:13:48Z,"Win7 host, WinXP guest, 2-monitors setup (laptop & external monitor), seamless mode.

After upgrading to VBox 5, it seems that VBox perceives monitor1 as monitor 2 and monitor2 as monitor1. Upon guest startup, 1 window opens at first and XP starts booting. After a while, when switching to graphical environment (during the XP boot process, just before the login screen appears) a 2nd window appears and the XP boot progress is shown in that window (the 2nd instead of the 1st). After that, the guest OS seems to treat the 2nd VBox window as the 1st screen and vice-versa. I enabled the mini-toolbar and set the 1st virtual screen to use host screen 1 but instead it used host screen 2. If VS1 is set to HS2, it works as intended but then if the guest is shut down, the external monitor is plugged-out and the guest is restarted, nothing is shown because in the laptop's monitor, the 2nd VS is supposed to be shown.

The ""Display"" of the guest shows as monitor #1 the laptop monitor and as #2 the external (i can tell from the different resolutions), however the contents of monitor 1 are shown in #2 and vice-versa.

Everything worked normally in VBox4 from which i upgraded the host and guest installations.",Wand
14705,Windows XP SP3: Internet Explorer 8 embeding Windows Media Player 11 crashes when navigating away of webpage or on exit,Windows,VirtualBox 5.0.6,2015-10-15T10:03:57Z,2015-11-10T13:14:03Z,2015-11-10T13:14:03Z,"I am using a TV Online application that makes use Internet Explorer engine to fetch content and Windows Media Player to render the decoded Sopcast streams. The problem is that I can't switch Sopcast channels. The whole application crashes as soon as I browse away from currently playing SopCast stream and also if I close the application while a SopCast stream is playing. This application requires 3D acceleration for SopCast streams to work otherwise you'd experience black screen with audio only, but no crash. 

VMWare is unaffected but I dislike it due to poor performance. 

Applications involved:
-Cool TV Online application: http://www.cool-tv.net/help-tv.html
-Internet Explorer 8
-Windows Media Player 11

Optional software (doesn't affect this issue, removes ads from Cool TV Online application):
-Java Runtime
-nxfilter: http://www.nxfilter.org   ",pal1000
14719,OpenGL Warnings,Linux,VirtualBox 5.0.6,2015-10-19T17:54:29Z,2015-10-26T09:15:47Z,2015-10-26T09:15:47Z,"Hi,
I think this is a recurring problem with the OpenGL, but none of the previous tickets have a concrete answer.
I have installed VirtualBox 5.0.6 with VirtualBoxAdditions, and when I use two molecular visualization programs that require 3D acceleration I get an OpenGL Error.

VMD
{{{
libGL error: pci id for fd 5: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

Pymol
{{{
libGL error: pci id for fd 4: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
}}}

",cb99
14726,Remove option for Quick Launch shortcut from installer,other,VirtualBox 5.0.6,2015-10-21T12:51:23Z,2015-10-21T13:01:43Z,2015-10-21T13:01:43Z,"There should not be an option for a Quick Launch shortcut in the Windows installer. This feature was deprecated 6.5 years ago with the launch of Windows 7; then it took a settings change to bring it back. With Windows 10, it takes a registry hack to bring back this feature.",Aren Cambre
14709,VBoxManage (Windows) doesn't accept paths with spaces using quotation marks,all,VirtualBox 5.0.6,2015-10-17T01:44:29Z,2015-10-17T01:44:29Z,2015-10-17T01:44:29Z,"I need to resize a disk urgently and cannot due to this stupid bug. Can't rename folders and vdi filename to have no spaces as that causes a different error.  eg.

VBoxManage modifyhd ""Windows 10 (64-bit).vdi"" --resize 40960
returns
Syntax error: Invalid parameter '10'
",Ross
14704,Windows special folders mount as read only when shared,Linux,VirtualBox 5.0.6,2015-10-15T08:46:37Z,2015-10-15T08:46:37Z,2015-10-15T08:46:37Z,"Windows uses the 'read only' attribute for folders to indicate that the folder is a special folder such as 'Downloads', 'Documents, 'Pictures', 'Videos' and 'Music'.  Consequently this attribute is not intended to indicate that the folder is actually read only or that files should not be able to be created within it (https://support.microsoft.com/en-gb/kb/326549).  Unfortunately Virtual Box does not respect this behavior when mounting a shared folder that contains such folders.

An example of this problem is that if the 'Downloads' special folder is moved to the root directory of drive 'D:' and then drive 'D:' is shared with an Ubuntu client, then it will be impossible to create files or folders within the 'Downloads' folder from within the Ubuntu client. Nor will it be possible to change the permissions from within the Ubuntu client.

There is a workaround (https://forums.virtualbox.org/viewtopic.php?f=3&t=46541), which involves removing the read only attribute from within Windows using the command line 'attrib' command (Explorer does not permit the read only attribute to be removed from folders).

This is not an ideal solution as it removes some of the special folder behavior within Windows.  Ideally, VirtualBox should respect the normal Windows behavior of the read only attribute and ignore it.  This should be a very simple matter to fix.
",TrevorW
14688,BSOD on Windows 10 with pagefusion on,Windows,VirtualBox 5.0.6,2015-10-09T21:18:36Z,2015-10-09T21:18:36Z,2015-10-09T21:18:36Z,"I always have a BSOD on my Windows 10 Home host when starting a Windows Server 2012 guest with pagefusion on

",mvendramin
14676,NDIS6 Network Driver breaking Local Area Connection on Sleep Resume,all,VirtualBox 5.0.6,2015-10-06T19:31:42Z,2015-10-07T03:11:35Z,2015-10-07T03:11:35Z,"There appears to be a problem with the NDIS6 driver handling power state changes. 

Since updating to VirtualBox 5.0.x, my Local Area Connection reports ""Network cable unplugged"" after waking up from sleep. 

This issues does NOT occur if i uncheck the VirtualBox NDIS6 Bridged Network Driver on the connection. 

Workaround 1: Disable the Virutalbox VirtualBox NDIS6 Bridged Network Driver on the connection

Workaround 2: disable and re-enable the interface every resume. 
 
Workaround 3: Configure the Network Adapter Hardware power management to disable ""Allow this computer to turn off this device to save power."" 

Disabling power management on the interface not only prevents the issue from occuring, but also returns it to service after a sleep/resume cycle without having to disable and re-enable the interace. 


I think this issues could be related to some other host<->guest networking problems commonly reported which I also run into. 

My Hardware: Dell Precision M4800. Intel Ethernet Connection I217-LM. Driver version 12.12.50.7205. Connected via docking station. 

I'm trying to find a way to get into debugging the driver, but could use some guidance. 
",GabeF
14657,"guest audio choppy, video lags and windows screen flickers",Windows,VirtualBox 5.0.6,2015-10-02T21:10:36Z,2015-10-06T03:52:48Z,2015-10-06T03:52:48Z,"Host: Win7 64bit, intel i7-930 processor, VirtualBox-5.0.6-103037-Win
Guest: Win8.1 64Bit with VirtualBox_Extension_Pack-5.0.6-103037

Would also like to refer to:

issue #14633, that describes also the audio problem, but may have a different cause.

issue #4088, latency fixes (Windows hosts only; bug ), fixed in the release



To reproduce this: enable 2d/3d video acceleration for the guest, using an usb mouse

Steps to reproduce:[[BR]]

-start the guest[[BR]]-logon, during logon process the screen flickers[[BR]]
-lauch IE, again sometimes the screen flickers during startup of IE[[BR]]
-goto to youtube and start a music video.[[BR]]


-if you don't use the mouse, the sound and video are almost perfect

-hover the mouse above the playing video area[[BR]]
-rapidly move the mouse from left to right/up/down within the video rectangle
a) the sound will become ""choppy"",
b) the video seems also to lag a little


In the previous version (5.0.4) audio was constantly choppy (even without moving the mouse),
as if you put the volume control to high, like to much voltage on a speaker.[[BR]]

In the previous version (5.0.4) the video was constantly lagging, showing blocks, seems to stop some milleseconds 

After installing 5.0.6, the sound and video performs better but it's not solved.

If I disable 2d/3d video acceleration, audio is back to normal, no video lags and no screen flikkering. (don't see a benefit for enabling video acceleration)

Enabling video acceleration and using the usb mouse together seems to cause the problem.

May be both have an issue.

Attached logs and the description might lead to a solution?
",L.
14815,USB redirection software and VirtualBox,all,VirtualBox 5.0.8,2015-11-13T07:56:59Z,2015-11-13T07:56:59Z,2015-11-13T07:56:59Z,"Description of the problem is on the forum:

https://forums.virtualbox.org/viewtopic.php?f=6&t=74487",bartekbb1976
14791,bridged network error on windows 10,Windows,VirtualBox 5.0.8,2015-11-05T08:22:08Z,2015-11-05T08:22:08Z,2015-11-05T08:22:08Z,"I installed VirtualBox 5.08 on windows 10 pro which run in a windows domain. Current user had admin rights.
A host-only adapter could be installed.
When trying to use bridged or host-only networking, the VM(windows 2008 r2 server) refused to start. NAT was ok.
After many tries I activated the local Administrator, logged in locally and the VM started fine with bridged networking.
From now I could start the VM also as domain user.
Maybe this description helps fixing this issue. 
",miro25
14780,"Windows host, multiple monitors, 1 virtual screen, fullscreen not working correctly",all,VirtualBox 5.0.8,2015-11-03T15:29:01Z,2015-11-03T15:29:01Z,2015-11-03T15:29:01Z,"My setup is roughly this:
- Windows 7 as host.
- 3 real monitors: 1680x1050, 1920x1200 (main), 1280x1024, in that order from left to right.
- VirtualBox version 5.0.8, same effect with 4.3.30 and 5.0.6.

I have several clients installed, Linux Mint, Ubuntu, Windows 7, Windows 8, Windows 10, and I have this problem under all of them. The clients are all configured to have one display. As long as the client is windowed (both floating and maximized) everything works fine. 

When i switch to fullscreen (Host-F), the client gets the wrong display resolution. What i would expect to see is it beeing maximized on my main monitor (the same where the client window is at that time) and have its resolution (1920x1200) (*1). But what happens is that the resolution is set to 4880x1200 in Windows (1680+1920+1280) and 784x1200 in Linux (seems to be 4880 mod 4096) (*2). The vertical pixel count seems to be ok with 1200 (it takes either the maximum of the pixels of the current displays, or it's the height of the main display). To be more exact, the clients left margin is where my left margin is on the main screen, the screen extends to the right, some of it beeing on the right monitor, some of it invisible, but it looks like it exists. I can't move the mouse there, but that might be because the host blocks mouse movement. When i maximize progams inside the client, they seem to behave as if there is just one screen with the resolution of 4880x1200 (*3)

One other issue (no problem for me, but it might be for others), is that when the window of the client is on another of my monitors (either in a window or maximized), the fullscreen always goes so the exact same place, that is, it starts on my main monitor and extends to the right from there. I would expect that i could run a client in fullscreen on one of my side monitors somehow, like if the window is on that screen at the time i press Host-F. There might be another way to do this, but i haven't looked into this much, since it's pointless without fixing the first problem.

There might be some configuration option i overlooked, but i doubt it. My guess is, the virtual box host retrieves the wrong pixel count for the display to send to the client when going fullscreen. It should only take the pixels of the one monitor where it is going fullscreen, but instead takes the total pixels of the display area.

To clear up a few things:
- I have installed client additions on all clients, version matching the host.
- I tested it with only one monitor connected, everything works fine and as expected in this case.
- I have not tested other hosts for this effect. I can only guess that the Windows version on the host (7, 8.1 or 10) does not affect this problem, but it might be that a Linux host does not have this.
- I googled about this issue, and i checked the already existing bug reports, i didn't find anything describing this exact problem.
- ""Host-F"" is the keyboard shortcut for fullscreen, in my case right-ctrl-F. I use this terminology since it's called like that in the documentation as well. The described effect is the same when i use the menu entry for fullscreen. I have not tried remapping the host key, but i can't imagine this changing anything about the issue.
- I have not tried to swap the order of monitors around (especially having a monitor with less height as main monitor), but i had a similar effect with only 2 monitors. I doubt trying different monitor configurations will give any more insight to this problem, and if so, it has to be done by a developer/tester who is more familiar with virtualbox in that area.

Notes:
- (*1) I check what the client ""sees"" as its resolution with something like rightclick and ""screen resolution"" in Windows, and xdpyinfo in Linux
- (*2) I tested this in Linux before, when i had only 2 monitors connected (1680+1920) and then the resolution in Linux was 3600.
- (*3) It's hard to explain why it looks like this, it would be much easier for someone else to just try it. For example, when i maximize firefox, the middle of the windows is about 2440 pixels (half of 4880) away from the left margin (of my main monitor), which appears towards the right on my left monitor. It implies the total screen area goes beyond the right edge of that monitor.",waldemar
14767,VirtualBox 5.0.8 causes Wireless Networks to Disappear,other,VirtualBox 5.0.8,2015-10-30T11:18:18Z,2015-10-30T11:28:25Z,2015-10-30T11:28:25Z,"I installed VirtualBox 5.0.8 under Windows 10 Professional (x64), upgrading my system from 5.0.6.

Now, when I reboot, there is a red ""X"" in my wireless network connections on the login screen.  

When I login to my local desktop (Administrator account or user account with admin privileges) and click the Network Settings icon in the system tray, I get the message that there are no wireless networks.

I have to wait 2-3 minutes before they appear.  Once they do, then Windows 10 connects to them.  Sometimes it takes longer than 2-3 minutes.

I restored my machine to a Windows 10 image I had created prior to installing VirtualBox 5.0.8 and the problem has gone away.
",Master VB Guru
14761,Clipboard behavior: Pasting clipboard from paused VM causes destination host app freeze,all,VirtualBox 5.0.8,2015-10-28T20:17:58Z,2015-10-28T20:17:58Z,2015-10-28T20:17:58Z,"1. Clipboard Direction: Guest to Host
2. Copy any text from guest OS
3. Pause the guest
4. Paste into any application running on host, or another guest (e.g. notepad)

Now, the application of destination freezes until the source of VM is resumed.


This behavior might not incorrect. but I think this scenario should be handled in some way, instead of freezing target app.",ddixuike
14737,Error When starting Windows 1.01 (VINF_EM_TRIPLE_FAULT),Windows,VirtualBox 5.0.8,2015-10-24T08:35:46Z,2015-10-28T14:29:34Z,2015-10-28T14:29:34Z,"When i try to start the VM it goes to the boot screen and MS-DOS EXCUTIVE and then crashes(Works fine on VBOX4)
",po
14751,USB flash driver not working on Windows 7,Windows,VirtualBox 5.0.8,2015-10-26T18:33:05Z,2015-10-26T18:33:05Z,2015-10-26T18:33:05Z,"USB flash driver attach to Windows 7 guest does not work, but working in Windows XP guest.",Steely Wing
14750,Windows 7 Guest crashes with 3D acceleration turned on,Windows,VirtualBox 5.0.8,2015-10-26T14:33:29Z,2015-10-26T14:36:34Z,2015-10-26T14:36:34Z,"Since VirtualBox 5.0 all my Windows 7 guests crash if 3D acceleration is turned on. The guest machine boots up, but when I try to login, the ""VirtualBox.exe"" causes an access violation.
I'm running VirtualBox on a Windows 8.1 host.",Feuerfloh
15649,Can no longer switch screens using mini toolbar,Windows,VirtualBox 5.1.0,2016-07-20T14:19:07Z,2022-08-22T13:55:20Z,2022-08-22T13:55:20Z,"I just upgraded to v5.1 and can no longer switch screens using the mini-toolbar command '''View | Virtual Screen 1 | Use Host Screen X'''. I am running the VM in full screen mode. When I choose ""Use Host Screen 2"" nothing happens. No errors.

I can switch out of full screen mode, I can drag the VM to my second monitor and reenter full screen mode. But moving the VM to another monitor via. the mini toolbar menu no longer works for me.

Windows 8.1 host with multiple monitors

Windows 7 VM, with a single monitor

",s23ayers
15603,VirtualBox 5.1 3D acceleration issues,Linux,VirtualBox 5.1.0,2016-07-13T15:15:46Z,2017-02-04T15:34:10Z,2017-02-04T15:34:10Z,"When 3D acceleration is enabled, several odd things happen.  By the way, VB 5.0.24 did not have any of these issues.

* Sometimes only a small rectangle of the screen will redraw after boot with VB set to a normal window.  It's about the size rectangle as the boot windows.
* The VB mini toolbar and dialogs are hidden in full-screen.
* Can't display full-screen on display 1 when display 2 is primary.  It just ignores the menu setting.
* The non full-screen window randomly shifts to my primary monitor on restart.

With or without 3D enabled, and when the VM is set to auto-login, the Ubuntu launcher is randomly invisible at boot time until I click in the VB window, and it immediately appears.  Clicking does not consistently make the launcher appear with 3D enabled.

Host: Windows 10 Home, NVIDIA GTX 650 Ti 368.69
Client: Ubuntu 16.04 with VB guest additions 5.1
",John JJ
15618,"5.1 and Windows XP machine crashes (raw mode, VERR_REM_VIRTUAL_CPU_ERROR Guru)",Windows,VirtualBox 5.1.0,2016-07-14T18:40:56Z,2016-09-23T22:00:33Z,2016-09-23T22:00:33Z,"Just upgraded to 5.1 from 5.0.24 - and Windows XP machine crashes every time you try to load. The saved session crashed. The fresh boot crashed. I can do a Windows Safe boot (and loaded the new utilities there), but a regular boot still crashes.",Trolleyfan
15656,"mouse disappears in virtualbox, linux installation menu",Linux,VirtualBox 5.1.0,2016-07-21T15:48:18Z,2016-07-21T15:48:18Z,2016-07-21T15:48:18Z,"First of all, Sorry for my bad English!

my mouse disappears in virtualbox, to be exact in the linux installation menu. I can't choose any of the option system. I mean I can't choose ""Install, or anything"" I've a laptop, I tried to use USB mouse, but it didn't work. I used the insert guest additions, and turned off/on the 3D acceleration. both isn't working. I changed my Pointing device, from USB Multi-Touch tablet to USB Tablet. 

Can anyone help me please? What should I do?",Hisham
15631,Virtual machine list accessibility issues,all,VirtualBox 5.1.0,2016-07-17T19:42:30Z,2016-07-17T19:42:30Z,2016-07-17T19:42:30Z,"When navigating in the vm list with NVDA, it's not read as every other list, it's not read at all, or some other controls are read. It's not as critical, but it's a nuisance when you have more vms.",tyrylu
16296,Left half portion of the guest's widescreen desktop becomes unresponsive to left mouse button clicks,Linux,VirtualBox 5.1.10,2016-12-16T14:35:44Z,2022-11-30T22:57:40Z,2022-11-30T22:57:40Z,"I am not sure what causes this or how to manually reproduce this behavior; otherwise, I would have reported this issue a long time ago.  Almost every day (and after no particular amount of up-time), the left half of my Linux desktop becomes unresponsive to left mouse button clicks.  Left-mouse button clicks do continue to work on the right half portion of the screen.  Actually, it is not the entire left-half portion of the screen that is affected; more like approximately the left two/fifths (left 40%) portion of the entire screen.

This problem is very annoying because smaller windows running in the affected portion of the screen cannot be interacted with or dragged over to the responsive side of the screen.

When this problem occurs, nothing I have tried so far (e.g. restarting the window manager) will correct it.  I am forced to close out (as best as I can) all the running applications in the Linux guest and then reboot the guest OS.

I have no idea what is causing this.  A faulty screensaver timeout process?  Your guess is as good as mine.

Some specific details of my setup:

* Guest OS: 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
* Guest window manager: Openbox 3.5.2
* Host OS: Windows 7 Enterprise 64-bit
* Host configuration: dual identical DELL P2414H widescreen monitors (1920x1080 resolution); VirtualBox is running as a maximized window on my right-side monitor

I believe that this strange behavior has been happening as far back as version 5.0.20 of Virtual Box.",Tony DeFusco
16221,After upgrading to 5.1.10 Network interface is not working enp0s3: Detected Tx Unit Hang,Linux,VirtualBox 5.1.10,2016-11-23T15:56:25Z,2020-09-08T16:49:04Z,2020-09-08T16:49:04Z,"After upgrading to virtualbox 5.1.10  Network interface is not working after boot unless its manually reset after boot.Downgrading to virtualbox 5.1.8 fixes the problem.However, upgrading to 5.1.11 is mostly working but not 100% of the time. During the testing it didn't work a few times.
Linux arch 4.8.10-1-ARCH guest on windows 10 Host. 

journalctl -b
kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang",vdv
16220,Improper font scaling in VB Manager,other,VirtualBox 5.1.10,2016-11-23T14:44:51Z,2019-04-30T13:38:53Z,2019-04-30T13:38:53Z,"I am running Windows 10 Professional on a Surface Pro 4. The VirtualBox Manager window has improper font scaling on my main display, a ""normal"" DPI external monitor. See attached image '''VirtualBox Manager on external monitor.png'''. If I drag the window to the Surface Pro 4's internal window, it looks worse; see '''VirtualBox Manager on Surface Pro 4 monitor.png'''.

BACKGROUND: In my current configuration, the Surface Pro 4 boots with its Surface Dock attached. It boots into a situation where an external, 1920x1080 monitor is the primary monitor; the built-in monitor is a secondary monitor. (It always boots this way if the Surface Dock is connected per my intentional configuration of Windows's display settings.) All applications, except VirtualBox, have fonts scaled properly for this normal resolution, main monitor.

This may relate to #9864, an old ticket.",Aren Cambre
16259,Cannot start VMs due to VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED,all,VirtualBox 5.1.10,2016-12-02T17:35:00Z,2017-04-10T07:02:31Z,2017-04-10T07:02:31Z,"On some windows hosts VirtualBox will not start VMs with DigitalGuardian installed. An error message box with ""VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED ... supR3HardNtChildPurify what:5"" appears. This has been reproduced on both a Windows 7 and 2K8R2 systems but not all Win7 and 2K8R2 machines. This is system configuration depended. I have a windows 7 machine where I uninstalled DG but left our driver in place and it still failed. I then copied an MS driver, vms3cat.sys, into dgmaster.sys rebooted and it still failed. I believe there is a logic error in the code that replaces suspect virtual memory.

I have a 2K8R2 VM that reproduces the issue.
",Stevel
16229,Blue screen of the death when you change to Bridged Adapter,Windows,VirtualBox 5.1.10,2016-11-25T08:41:01Z,2017-02-11T08:36:03Z,2017-02-11T08:36:03Z,"All worked fine before update of my network driver. (I updated by KillerSuite_1.1.65.1752_Win7_Win81_Win10).

But after update, when I share internet using Bridge, blue screen of the death for host machine is appeared. If i don't have connection to the internet on host machine (Wi-Fi/Ethernet), all are working fine, but after connection all crash too.   

version of Vbox is 5.1.10 r112026 (Qt5.6.2)
Both(host and guest) have windows 10

Could you please tell, is it problem of Vbox or my driver? What is the best way to resolve it? Rollback driver\create ticket for them or is it Vbox problem? ",AlekseiG
16291,Guest SuSe 13.2 freezes on Host Windows 7 when more than 1 processor (core2 quad) is assigned,Linux,VirtualBox 5.1.10,2016-12-15T09:51:04Z,2017-01-06T10:27:29Z,2017-01-06T10:27:29Z,"This issue is similar to that in [https://www.virtualbox.org/ticket/7619 ticket 7619]. However, the issue occurs with a recent VirtualBox version.

When more than 1 processor is assigned to the Guest (Open SuSe 13.2, XFCE Desktop) it freezes after some time and does not react anymore (commonly after below 1 hour). VirtualBox itself still runs. Pausing the VM or Saving it to the Disk (and resuming) works fine but the Guest is still frozen. The Host is Windows 7 SP1.

When I assign 1 processor it works fine (I worked for 2 month with this 1-processor-setup and experienced some performance problems recently, which is way I came back testing a >1 processor setup. But this is not the topic of this ticket).

3D acceleration is not enabled. The issue seems to be correlating with the usage of Mozilla Firefox and/or Thunderbird - but not exclusively. The freezes occured also without Firefox running (but less ofter). 

The host computer has a Core2 Quad Q9400 Processor. It does not support hyper-threading. I could assign up 8 cores in the settings dialog. I mention this because I found some discussion on whether cores or virtual processes are assigned. Idependent whether the processor supports hyper-threading or not, there should be only 4 cores available.

Currently, I am using VirtualBox v5.1.10 but the issue occured also in v5.1.6 and v5.1.8.

Since the number of Core2 processors is declining this issue probably has a quite low priority.",neumannd
16305,Can't start session for virtual machine,all,VirtualBox 5.1.10,2016-12-19T06:53:30Z,2017-01-03T09:08:43Z,2017-01-03T09:08:43Z,"I've got an error: 

'''Can't start session for virtual machine'''. 

The virtual machine 'MS DOS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VirtualBox VMs\Machines\MS DOS\Logs\VBoxHardening.log'.

Erro code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}



Host - win 7, 64bit. Guest - any vmachine (tried msdos, win xp, win 7, ubuntu and got the same error).

BUT if I start the machine in the background session and then click show (or start background session with interface) - everything works!

Tested on 5.1.10, 5.1.8, 5.1.0 and test build (5.1.11). Seems like an issue with all 5.1.x versions.

Note that 5.0.x works fine on my host.",coldshine
16272,VirtualBox crashes out when attempting to boot Windows Me,Windows,VirtualBox 5.1.10,2016-12-06T23:03:07Z,2016-12-23T04:53:07Z,2016-12-23T04:53:07Z,"When attempting to use Windows Me on one of my machines, VirtualBox crashes out with the message (from Windows host):

VirtualBox.exe - Application Error
The instruction at 0x758BA614 referenced memory at 0x000C000C. The memory could not be written.
Click on OK to terminate the program
Click on CANCEL to debug the program

The result is quite predictable. It happens when I attempt to boot a Windows Me floppy. I can use a Windows 95 floppy to get the VM started, and so install Me from source files, but the resulting hard disk crashes out with the same error.

I’m using VirtualBox 5.1.10 in Windows 10 on an Acer Extensa 5635Z laptop, with a T4200 processor (32-bit, no VT-x) and 2Mb RAM.
The problem does not happen on my other machine, which has a Core i5 (2500) processor amd 16Gb RAM.

I have managed to pin down the problem on the floppy to the disk boot sector, and the particular block of 54 bytes starting at offset 0x8D.
",dlharper
16222,"dragndrop file fails (Windows 10 host, Ubuntu 64bit guest)",Linux,VirtualBox 5.1.10,2016-11-24T03:05:15Z,2016-12-22T09:26:59Z,2016-12-22T09:26:59Z,"As per instructions, logs enclosed!",robertbaruch
16282,Win7: Cannot start a virtual box machine,other,VirtualBox 5.1.10,2016-12-12T10:56:06Z,2016-12-20T15:38:57Z,2016-12-20T15:38:57Z,"Cannot start a virtual box machine (configured for Windows 10) in Window 7 - it worked, but now it causes BSOD - APC_INDEX_MISMATCH (probably after Windows update).

The very same problem when I created a new (empty) virtual machine.

(Computer DELL Optiplex. I was using VirtualBox 5.0.x, but update for 5.1.10 did not solve the issue.)",hrondra
16302,memory usaly error on ubuntu-16.04.1-desktop-amd64,Linux,VirtualBox 5.1.10,2016-12-17T15:18:18Z,2016-12-20T12:29:13Z,2016-12-20T12:29:13Z,"1. run WarZone2100
2. Инструкция по адресу 0х0000000058383А30 обратилась к памяти по адресу 0x0000000000000008. Память не может быть read. ""OK"" — завершение приложения

p.s. https://yadi.sk/i/cDluGr-q33qgq8",fix27
16307,sda_hda_intel 0000:00:05: CORB reset ...,Linux,VirtualBox 5.1.10,2016-12-19T06:57:27Z,2016-12-19T11:25:07Z,2016-12-19T11:25:07Z,"Any version VB 5 - 5.1.11r112223. Host Windows, Guest Linux. I it see at everyone loadings of Debian 8.4, 8.5 (Xu 15-17,Lu 16,U 16). 

The text sda_hda_intel 0000:00:05: CORB reset ... appears only if to use Intel HD Adio in the VB settings.

Why I use Intel HD Audio? I have two sound cards. One built-in the motherboard, second external. They have characteristics: 8-32bit 192kHz.

AC-97 (Audio Codec '97) ""AC'97 defines a high-quality, 16- or 20-bit audio architecture with surround sound support for the PC. AC'97 supports a 96 kHz sampling rate at 20-bit stereo resolution and a 48 kHz sampling rate at 20-bit stereo resolution for multichannel recording and playback. AC97 defines a maximum of 6 channels of analog audio output"" 

If load time speed is very fast this text can be not seen. The sound works without visible problems for Guest.",q34er6ty7
16285,Crash disconecting host monitor while saving state,Windows,VirtualBox 5.1.10,2016-12-13T19:16:33Z,2016-12-13T19:16:33Z,2016-12-13T19:16:33Z,"While I was saving the state of a VM in fullscreen mode, I disconnected a host monitor (physically, by unplugging the video cable). The VM process crashed with the following error (translated):
 Application Error : The instruction at 0x00000000775C4756 referenced the memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.

After that, the VM in the VBox Manager resulted in an ""Interrupted"" status.

Here are some useful details:
* The host screens '''before''' unplugging were:
 1. Notebook native monitor
 2. HDMI external monitor, with fullscreen VM
 3. MiniDP external monitor, ''main host screen''
* The host screen '''after''' unplugging were:
 1. Notebook native monitor, ''main host screen''
 2. HDMI external monitor, with fullscreen VM
* Of course the host screen configurations before and after unplugging are as expected, including the fact that the main host screen switched from the screen no. 3 to the no. 1
* All 3 monitors have the same resolution, 1920x1024
* The VM has 2 guest screens, but only 1 was enabled
* The VBox Manager was open but '''did not''' crash, i.e. only the VM process crashed",FstTesla
16262,shared folder not write-able for non-root users for special windows folders,Linux,VirtualBox 5.1.10,2016-12-03T16:01:53Z,2016-12-05T08:13:01Z,2016-12-05T08:13:01Z,"I would like to mount the Windows ''Downloads'' directory as a shared folder, but the mounted folder is not writable to regular users. Yet the root user can still write to it.

Played all mount options but to no avail: the permissions of all files and sub-folders in the mounted folder are correctly set, and the issue is about the permission bits of the mount point itself. Tried to mount a sub-folder in the ''Downloads'', then the permission bit is correct.

{{{
    C:\Users\opensrc\Downloads     -> Downloads: dr-xr-xr-x
    C:\Users\opensrc\Downloads\Sub -> Subfolder: drwxr-xr-x
}}}

Wonder why the ''Downloads'' folder is treated differently.
",opensrc
16250,Display resolution capped at 1024x768,Linux,VirtualBox 5.1.10,2016-11-30T22:58:53Z,2016-12-01T17:28:20Z,2016-12-01T17:28:20Z,Just installed 5.1.10 r112026 Qt5.6.2 and tried to get Lubuntu running on a Win 7/64 workstation with dual 1920x1080 displays. Tried setting everything in sight including preferences but the Lubuntu VM still shows a capped display size. Similar to bugs: 15997  15788  15310,stkvbox
16235,latest Guest Additions crash linux guests after installation and rebooting the guest,Linux,VirtualBox 5.1.10,2016-11-26T18:44:03Z,2016-11-28T11:20:17Z,2016-11-28T11:20:17Z,"I've find out that the new version of guest extensions crashes down newder debian derivates as elementary os and deepin. I can't confirm this for ubuntu but at least for these too. 

T reproduce 

Download an iso  at deepin.org or elementary.io
install the system on windows at usual 
update the system with sudo apt -y full-upgrade
install guest additions from the iso image delivered with virtualbox as root or with sudo
reboot the guest

The expected result is virtual box on windows will hang up and not respond anymore

",horvan
16227,USB M-Audio fast track ultra device not working,Windows,VirtualBox 5.1.10,2016-11-24T17:07:29Z,2016-11-24T17:07:29Z,2016-11-24T17:07:29Z,"After reading several forums I managed to have my guest (windows 7 home) recognising my audio device.
I installed the appropriate M-Audio drivers with no errors.

However, if I try to play any sound the device basically freezes the program which is attempting to use it and seemed to play like a microsecond of music every several seconds. This also happens if I directly try to test it from windows (the green bars indicating the volume in output move incredibly slowly).",epifab
16226,vbox file is missing after adding port-forwarding config while guest is running and later guest shutdown,Linux,VirtualBox 5.1.10,2016-11-24T12:33:46Z,2016-11-24T12:39:23Z,2016-11-24T12:39:23Z,"Steps to reproduce this problem:

- Create a Linux guest (without installing guest tools).
- Create a snapshot of this guest.
- Fully clone the guest (not linked), not including any snapshot (last state only).
- Run the clone guest.
- Add some port-forwarding configurations while guest is running and save.
- Do ""shutdown -h -t 0"" on the guest.
- It's not previsible how many guest restarts could led .vbox file to be deleted. I had the same problem even with just restarting VirtualBox manager itself or rebooting the host.

Additional info:

Host: Windows 10 Pro Anniversary 64-bits (Hyper-V disabled via ""bcdedit /set hypervisorlaunchtype off"").
Guest: Ubuntu Server 16.04 LTS x64, cloned from another guest.",calamann
16218,"Win10 host Ubuntu 16.04 guest, graphics problems",Linux,VirtualBox 5.1.10,2016-11-23T10:09:57Z,2016-11-23T10:09:57Z,2016-11-23T10:09:57Z,"I have over the last couple of months set up several Ubuntu 16.04 guest and noticed a pattern of problems over all the version 5.X's of VirtualBox:

It seems to be generally slow at times. Sometimes 10-15 seconds to start up until one gets to login. After logging in another 10-15 seconds before the machine becomes fully available, i.e the app icon bar shows.

When using the front end of the OS (i.e. opening, closing or minimising windows), the machine becomes sluggish but not always. when checking processes running ""Compiz"" will typically be using a lot of CPU, e.g. 70-100% for some time, after which it drops and the OS front end becomes responsive/accessible again.

If one enables 3D Acceleration it sometimes help, but may have other consequences such as the Chromium browser just displaying large rectangular, black or white areas with no menu or anything else displayed. The front end of other running applications also becomes either sluggish or non-responsive.

I have also seen problems with videos, sometimes there sometimes not. Sometimes the sound may be out of sync with the picture. But the problems are intermittent. 

So, in general it seems that graphics is not handled properly by VirtualBox and/or Ubuntu 16.04 itself, possibly a combination of the two. Since VirtualBox are handling the graphics in the form of special drivers, the solution probably has to come from VirtualBox.

",Orionsg
16215,Crash while installing Avast,Windows,VirtualBox 5.1.10,2016-11-23T05:37:36Z,2016-11-23T05:37:36Z,2016-11-23T05:37:36Z,"Host OS = XP Prof 32 bit V 2002 SP3 on 800GB partition. 1GB (of 2) ram
Guest OS = Windows 7 Prof 32 bit SP1 30 GB on 50GB partition (7 GB free).  1GB (of 2) ram
Guest originally restored from Macrium image.
When installing Avast anti-virus (free version) I get a ""guru meditation"" before it completes.
Tried with normal and immutable guests, and with a similar Vista guest
Gets to about 99% (going by the progress bar)
",jchrisj
16338,USB Root Hub Shows Yellow Exclamation Mark in Device Manager,Windows,VirtualBox 5.1.12,2016-12-30T08:47:44Z,2021-12-09T16:58:17Z,2021-12-09T16:58:17Z,"Environment:
    ASMedia USB 3.0 extended host controller with the '''vendor driver'''.[[BR]]Operating system is Windows.

Steps:
    1. Open VM VirtualBox and create virtual machine (Type is Microsoft Windows).
    2. Open Device Manager and disable ASMedia USB Host Controller.
    3. Enable ASMedia USB Host Controller.
    4. USB Root Hub shows yellow exclamation mark.
    5. Device Manager displays the following message in the USB Root Hub Properties dialog box, on the General tab, in the Device Status text box:[[BR]]Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)[[BR]]The driver could not be loaded because a previous version of the driver is still in memory.",Gary_Chen
16350,VERR_SSM_LOADED_TOO_MUCH when restoring snapshot,Windows,VirtualBox 5.1.12,2017-01-03T14:07:04Z,2020-08-18T14:23:48Z,2020-08-18T14:23:48Z,"I cannot resume VM state from existing snapshot, getting following error:

Failed to load unit 'vga' (VERR_SSM_LOADED_TOO_MUCH).


E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Host: Windows10
Guest: Windows10

",mammoth
16318,Not Signed with the Build Certificate error after installing 5.1.12 r112440,Windows,VirtualBox 5.1.12,2016-12-23T08:55:56Z,2020-05-07T22:15:45Z,2020-05-07T22:15:45Z,"I have just installed !VirtualBox 5.1.12 !r112440 on a Windows host running Windows 10 Professional, and when trying to run a VB image for the first time I get this error:

''!VirtualBox - Error In supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\!VirtualBox\!VirtualBox.exe (rc=-5657)
Make sure the kernel module has been loaded successfully.''

VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT (-5657) - The image is required to be signed with the same certificate as the rest of !VirtualBox.

Previous to installing this version, all !VirtualBox images have worked perfectly fine, with the only change to my machine between last night and this morning being that I've installed the new version of !VirtualBox.",Shaun Collier
16382,Win10: VBoxSVC hangs when thunderbolt-to-USB is disconnected (PC undocked),Linux,VirtualBox 5.1.12,2017-01-12T18:52:03Z,2020-02-11T20:59:09Z,2020-02-11T20:59:09Z,"USB ports on the HP ZBook Dock with Thunderbolt 3 is unresponsive after undocking/docking when VirtualBox is running.

Hardware: HP ZBook Studio G3 with HP ZBook Dock with Thunderbolt 3

'''To reproduce :'''
1. Start the Oracle VM VirtualBox.
2. Start the Ubuntu VM . 
3. Undock - Unplug the Thunderbolt cable. (ie. disconnect laptop from dock ...)
4. Re-dock - Plug the Thunderbolt cable.
5. The Thunderbolt dock USB ports are non-responsive.

'''Observations:'''
Something in VirtualBox seems to ""block the system from clearing the instance of the USB root hub driver from memory on the Thunderbolt disconnect"".

After the problem has occurred (ie. USB ports on dock is unresponsive), closing all programs, attempting to reboot Windows, the following Window message appears:

""VirtualBox Interface  Has active connections.""

Aborting the Windows reboot and checking ""Task Manager"" shows that the VBoxSVC.exe process is still active.

Manually killing the VBoxSVC.exe process seems to restore the Thunderbolt dock's USB ports.


This may be related to: Ticket #16338 USB Root Hub Shows Yellow Exclamation Mark in Device Manager

Forum thread:
https://forums.virtualbox.org/viewtopic.php?f=6&t=81228&hilit=Thunderbolt&sid=af360a89332f31d27ba3fc2bf64e502e&start=15

",vscheng
16419,"Transmit pauses still happen, not on Linux guests but on Windows host",Windows,VirtualBox 5.1.12,2017-01-24T04:48:19Z,2018-03-22T02:52:05Z,2018-03-22T02:52:05Z,"Despite claim that bug #16221 has been fixed, that fix was at best partial. True, the send side pauses happen far less often than in version 5.1.10, but they still happen. They happen on Windows 10 host and on an interface that has no guests bound to it. I'm going to attach log from a guest, because it may have important information about the host, but this issue really applies to the host and not a guest.
",Rafcio
16361,Windows XP guest keeps crashing in recent releases,Windows,VirtualBox 5.1.12,2017-01-06T05:08:15Z,2018-03-22T02:34:05Z,2018-03-22T02:34:05Z,"I can't tell exactly when this started, but the XP guest was very stable in versions 4.3 and 5.0 (at least the early ones). The guest keeps crashing now at random intervals, so the regression could have been introduced with version 5.1. I didn't upgrade to version 5.1 from 5.0 right away as there were audio issues initially, and when the audio was ""fixed"" the 5.1.x version was already ""broken"" for that XP client. That XP client heavily uses network adapter, but I'm not sure if that's a contributing factor or not. The host is Windows 10 version 1607.

BTW, this is not related to this issue, but I want to mention this for clarity. Bug #16221 did not concern Linux client only. I had major issues with transmit pauses (between few seconds to few minutes) on Windows 10 host. So the bug affected Windows also and also host network interface. It seems to be fixed now, so I'm not going to open a new ticket unless I notice a troubling network interface behavior, but the comment that bug #16221 was concerning Linux only (wrong) client (wrong again) troubles me that there could be things not fixed correctly. Like I said, no issue with pausing after upgrading to 5.1.12.
",Rafcio
17624,Files containing only zeroes gets modified after restart,Linux,VirtualBox 5.1.12,2018-03-16T16:49:37Z,2018-03-16T16:49:37Z,2018-03-16T16:49:37Z,"Hi,

I would like to report that files containing only zeroes, gets modified after turning the virtual machine off and on.

Before the restart:
{{{
piotrek@sue:~> dd if=/dev/zero of=zeroes_1GB bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,678558 s, 1,6 GB/s
piotrek@sue:~> cmp /dev/zero zeroes_1GB
cmp: EOF on zeroes_1GB
}}}

After the restart:
{{{
piotrek@sue:~> cmp /dev/zero zeroes_1GB
/dev/zero zeroes_1GB differ: byte 647411201, line 1
}}}

The place of the first difference seems to be pretty much random. This can be illustrated by another example.

Before the restart:
{{{
piotrek@sue:~> for i in {1..10}; do dd if=/dev/zero of=zeroes_1GB_$i bs=1M count=1024; done
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,62127 s, 1,7 GB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 1,80431 s, 595 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,4662 s, 310 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,16451 s, 339 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,0117 s, 357 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,51445 s, 306 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 2,57957 s, 416 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 6,12661 s, 175 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 7,04536 s, 152 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 5,41265 s, 198 MB/s

piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
cmp: EOF on zeroes_1GB_1
cmp: EOF on zeroes_1GB_2
cmp: EOF on zeroes_1GB_3
cmp: EOF on zeroes_1GB_4
cmp: EOF on zeroes_1GB_5
cmp: EOF on zeroes_1GB_6
cmp: EOF on zeroes_1GB_7
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

After the restart:
{{{
piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
/dev/zero zeroes_1GB_1 differ: byte 794570753, line 1
/dev/zero zeroes_1GB_2 differ: byte 242036737, line 1
/dev/zero zeroes_1GB_3 differ: byte 184365057, line 1
/dev/zero zeroes_1GB_4 differ: byte 10874881, line 1
/dev/zero zeroes_1GB_5 differ: byte 460075009, line 1
/dev/zero zeroes_1GB_6 differ: byte 48693249, line 1
/dev/zero zeroes_1GB_7 differ: byte 101187585, line 1
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

When I cat one of the files, I recognize the content that is normally on my disk (for example xml requests that I store).

VirtualBox version: 5.1.12 r112440 (Qt5.6.2)

Host: Windows 7

Guest: OpenSuse 42.2

Linux kernel version: 4.4.104-18.44-default

Laptop: Dell Precision 3510

Screenshots of applicable virtual machine settings attached.

Best regards,

Piotr",PeterC
16811,VBox 5.1.12.12440 immediately crashes - Win10 x64 Home,Linux,VirtualBox 5.1.12,2017-06-04T20:04:30Z,2017-06-05T14:25:59Z,2017-06-05T14:25:59Z,"I cannot run VirtualBox 5.1.12.12440 x64. It crashes immediately when launced. I can't confirm, but I suspect the recent Windows 10 Creators update maybe did something to harm VBox, only becuase VBox worked fine until that Windows update was applied to my computer.

I've attached a crash dump of the most recent launch. I've also attached the most recent logs.",Malchore
16492,WebEx screen sharing with Windows 10 host causes guest to crash and out of memory error.,Linux,VirtualBox 5.1.12,2017-02-16T22:35:02Z,2017-04-07T11:48:20Z,2017-04-07T11:48:20Z,"When sharing a screen with Cisco WebEx while running a VirtualBox guest, the guest eventually crashes.  The host (Windows 10) complains about running low on memory, and the screen (or both screens) flicker or go blank.  Sometimes the host is usable after this but oftentimes it must be rebooted to become functional again.

The issue appears to be related to 3D acceleration.  When 2D/3D acceleration is disabled for the Linux guest, the issue goes away.

See:  https://forums.virtualbox.org/viewtopic.php?f=6&t=79382&p=385575#p385575

Host:  Windows 10 Enterprise 64 bit (Intel i5, 12 GB RAM)
Guest: Linux Mint 17 32 bit

Thx........",rbc
16365,Error after clean Install VirtualBox 5.1.12 on Windows 7 64 bit.,all,VirtualBox 5.1.12,2017-01-07T20:40:35Z,2017-03-17T10:14:38Z,2017-03-17T10:14:38Z,"Hello, I'm on Windows 7 64 bit.

After try to upgrade VirtualBox from 5.0.x to 5.1.12, I received following error:

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_INVALIDVALUE.

Error Code: 
REGDB_E_INVALIDVALUE (0x80040153)
Component: 
VirtualBoxClientWrap
Interface: 
IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

No one of any version the last stable or the previous one is not working, after install I received same errors. 

Tried to clean registry manually and via software, reinstalled any component of Virtualbox, no one was not help. ",aidjek
16322,Allow specifying a VHD diff file location when cloning,Windows,VirtualBox 5.1.12,2016-12-23T17:21:29Z,2017-03-16T13:19:38Z,2017-03-16T13:19:38Z,"When cloning, I expected to be able to specify the destination folder when using the diff method, just like you can when creating a new machine and creating a new disk.",Will Power
16383,cannot ping but can ssh and http,Linux,VirtualBox 5.1.12,2017-01-13T06:12:33Z,2017-01-20T02:17:57Z,2017-01-20T02:17:57Z,"Host: Windows 10
Guest: Centos 5
Network: NAT

Why: cannot ping in guest, but can http or ssh.

Debug: 
 1. Use tcpdump in guest and host, will see icmp request is sent to host and host resent this packet to the target, but after got icmp reply, host will try to resent reply to 10.96.1.19, then return ""unreachable network""
 1. Try to capture virtual machine packet by(there is only lo0 and eth0 interface in my guest):
{{{
VBoxManage.exe modifyvm ""redhat32"" --nictrace1 on --nictracefile1 c:\Users\xxxx\netlog.pcap
}}}
 But nothing is logged.
",JacksonZheng
16339,"The State of the VM has changed from RUNNING to ' GURU_MEDITATION '. Error ""(VERR_PATM_IPE_TRAP_IN_PATCH_CODE)""",Windows,VirtualBox 5.1.12,2016-12-30T11:50:25Z,2017-01-18T10:13:27Z,2017-01-18T10:13:27Z,"Gentlemen/Ladies,

Good morning.

I have a 32-bit Windows Vista Home Basic operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 2.00 GB. In this machine I created a virtual machine with the Windows 7 Home Premium 32-bit operating system (guest), with Service Pack 1 installed, as well as all the updates for this system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the ""!VirtualBox-5.1.2-108956-Win.exe"" version, since I have been updating !VirtualBox with each release version until I get the version ""!VirtualBox-5.1.12-112440-Win.exe"" . I noticed that the error messages were intencificated from the ante-penultimate version. The virtual machine was in ""Save State"" by the ""!VirtualBox-5.1.10-112026-Win.exe"" version, when I upgraded to the ""!VirtualBox-5.1.12-112440-Win.exe"" version. And several times this week, I entered the ""Machine / Close / Save State"" menu. Saving the state of the machine so I could continue my work from where I left off. In the last two days after starting the machine to continue my work in the state where I stopped, there were some errors, but I would close everything and then start the process again and the virtual machine would go up normally. Before Yesterday after this procedure, I worked normally and when restarting Virtual Machine, a screen appeared informing that the virtual machine suffered serious failures and suggested to me that I pressed the ""Ok"" button to leave the virtual machine and to contact the community !VirtualBox to get help with the problem. Referring to the ""VBox.log"" and ""VBox.png"" files in the ""C: \ Users \ Administrator \ !VirtualBox VMs \ Logs"" directory. Editing the file ""VBox.log"" I extract the following text below:
{{{
Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
04: 57: 53.186726 Console: Machine state changed to 'GuruMeditation'
04: 57: 53.480547

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!
04: 57: 53.480551 !!
04: 57: 53.480552 !! VCPU0: Guru Meditation -1432 (VERR_PATM_IPE_TRAP_IN_PATCH_CODE)
}}}
I will forward you these and the other log files contained in this
folder.

Note: In the virtual machine I made the Microsoft SQL Server 2014 Service Pack 1 Express Downloads, all the Microsoft SQL Server 2014 SP1 Feature Packs files, and the IIS 10 Express download and installation, after that I rebooted the machine and then the error already described appeared. I wonder If this virtual machine is compromised because of these errors and if has how to recover it?",MFS68
16335,"VirtualBox automatically forces shut down of guest before displaying ""new version available"" dialog",Linux,VirtualBox 5.1.12,2016-12-29T19:02:50Z,2017-01-18T10:09:19Z,2017-01-18T10:09:19Z,"VirtualBox version 5.x (any since 5.0) forces a shutdown of a running guest process to display a dialog stating that there is a new version available.

Steps to reproduce:
1. Install and run a guest operating system (Fedora Linux 23/24/25 in this case(s)).
2. Leave the guest operating system running on the host (Win10 in this case) for many weeks without issue.
3. When a new version of VirtualBox is released, the guest is automatically forced to shut down, and then the VirtualBox GUI displays a notice dialog box stating ""VirtualBox - Information: A new version of VirtualBox is has been released!...."".

Expected behavior:
Don't shut down my running guest operating system to display a simple informational dialog.

Notes:
This has happened to me on various VirtualBox versions 5.0.x and 5.1.x for over 10 months now.  VirtualBox guest tools are installed and are always updated with the host update.  Although I list a Windows 10 host and Fedora guest above, I have had the same exact issue happen on a Fedora 23/24 host and Windows 7 guest, with the same 5.x series of VirtualBox (I did run version VirtualBox 4.x on that combination for a while, however I never experienced this issue).

",gats
16392,BSOD SYSTEM_SERVICE_EXCEPTION on Windows 10,Linux,VirtualBox 5.1.12,2017-01-16T13:31:29Z,2017-01-16T13:48:12Z,2017-01-16T13:48:12Z,"I use a VM from MongoDB University course M310.
When I run the VM I get BSOD.",enabokov
16388,Guest CPU utilization pegged at 100% making the guest unusable,Windows,VirtualBox 5.1.12,2017-01-15T22:28:42Z,2017-01-15T22:28:42Z,2017-01-15T22:28:42Z,"Pretty much any activity in the guest pegs the guest CPU utilization at 100% for extended periods of time (for example client booting takes half an hour or more) during which the client is unusable. This affects Windows 7 and 10 clients, but Windows XP and OS/2 clients seem to be unaffected.
This has been introduced by either host upgrade from Windows 7 to version 10, or in VBox version 5.0 or 5.1. Last time a Windows 7 client was working correctly was on Windows 7 host and VBox version 4.3.x. Like I mentioned, multiple clients are affected, all are either Windows 7 or 10, both 32 and 64 bit.
",Rafcio
16371,After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch,Windows,VirtualBox 5.1.12,2017-01-10T17:13:23Z,2017-01-12T16:15:58Z,2017-01-12T16:15:58Z,"After Updating to Windows 10 Enterprise Insider Build 15002 VirtualBox 5.1.12 Won't Launch, below is the error I am receiving. I uninstalled and reinstalled Virtual Box, as well as tried starting in Win 8 Compatibility mode. Let me know if you need any other info.
{{{
Log Name:      Application
Source:        Application Error
Date:          1/10/2017 11:07:04 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CAT-670ZH72.catapultsystems.com
Description:
Faulting application name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Faulting module name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Exception code: 0xc0000005
Fault offset: 0x0000000000013a1d
Faulting process id: 0x2470
Faulting application start time: 0x01d26b63f72f8901
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: e55f15cb-c698-496e-8288-7f3763f5933a
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""Application Error"" />
    <EventID Qualifiers=""0"">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2017-01-10T17:07:04.074275800Z"" />
    <EventRecordID>496</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CAT-670ZH72.catapultsystems.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>VirtualBox.exe</Data>
    <Data>5.1.12.12440</Data>
    <Data>58594e7b</Data>
    <Data>c0000005</Data>
    <Data>0000000000013a1d</Data>
    <Data>2470</Data>
    <Data>01d26b63f72f8901</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data>
    <Data>e55f15cb-c698-496e-8288-7f3763f5933a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
}}}",Bobbyw87
16374,"Problem with usb flash disk: host = W10, guest=W7 and XP",Windows,VirtualBox 5.1.12,2017-01-10T18:11:26Z,2017-01-11T19:32:01Z,2017-01-11T19:32:01Z,"I use win 10 64 bit laptop and virtualbox  5.1.12. When I use VM with W7 or XP: USB flash disk work randomly. Most of the time : doesn't work. When I catch usb device on VM, it disappear on host , doesn't appear on guest and usb device disappear of the list of USB device. You have to disconnect USB flash disk to have it on host.
All VM I use, work very well with host:W7 32b.
I have reinstall lot of time: virtualbox, extension pack and addition guests.
Bests regards.
",galexis
16369,Configuring VirtualBox OSE to build with OpenSSL 1.1.0 on Windows,all,VirtualBox 5.1.12,2017-01-10T11:03:57Z,2017-01-11T09:21:04Z,2017-01-11T09:21:04Z,"Currently it is not possible to configure VBox OSE to compile with OpenSSL 1.1.0 libraries on Windows.
The configure.vbs script fails:


{{{
Checking for openssl...
error: Can't locate openssl. Please consult the configure.log and the build requirements.
}}}

The problem is that with OpenSSL 1.1.0 the libraries are now called libcrypto.lib and libssl.lib. However configure.vbs is still looking for libeay32.lib and ssleay32.lib.",IndyJones
16367,"When you start the VM that is in the ""Save State"", i receive the error message ""Failed to look for handy pages; rc = VERR_NO_MEMORY"".",Windows,VirtualBox 5.1.12,2017-01-08T19:35:44Z,2017-01-09T08:31:07Z,2017-01-09T08:31:07Z,"Ladies and Gentlemen,

Good Morning.

I have a machine with the Windows Vista Home Basic 32-bit operating system (host) with Service Pack 2 installed, as well as all the updates for this system. The computer has an Intel Pentium (R) Dual CPU T2370 of 1.73Ghz, with RAM of 2.00 GB, in this machine. I created a virtual machine with the Windows 7 Home Premium 32-bit (guest) operating system, with Service Pack 1 installed, as well as all the updates for that system. The computer has Intel Pentium (R) Dual CPU T2370 and 1.73Ghz, with RAM of 1.22 GB. The virtual machine was created using the version ""VirtualBox-5.1.2-108956-Win.exe"", since then I have updated VirtualBox with every release version, until the version ""VirtualBox-5.1.12-112440-Win.exe "". The virtual machine was in ""Save State"" in the ""VirtualBox-5.1.12-112440-Win.exe"" version. When I started Virtual Machine again with the following error message:

00: 00: 47.280263 PGM: Failed to look for handy pages; Rc = VERR_NO_MEMORY rcAlloc = VINF_SUCCESS rcSeed = VINF_SUCCESS cHandyPages = 0x8
00: 00: 47.280287 cAllPages = 0x5624d cPrivatePages = 0x4adb7 cSharedPages = 0x0 cZeroPages = 0xb46d",MFS68
16364,SYSTEM_SERVICE_EXCEPTION BSD in Windows 10 x64 guest on Windows 7 x64 host,Windows,VirtualBox 5.1.12,2017-01-07T19:23:27Z,2017-01-07T19:23:27Z,2017-01-07T19:23:27Z,"I'm getting a SYSTEM_SERVICE_EXCEPTION blue screen in Windows Pro 10 x64 guest on Windows 7 x64 host after I've updated VB to ver. 5.1.8. Until then (in ver. 5.1.6) everything was working just fine. Back then I couldn't find a ticket or a topic about a similar issue and I thought will be fixed in the next changes but it didn't. I've updated VB to the latest 5.1.12 version and I'm having the same issue. I've tried to reinstall the Windows 10 guest but the process crashes at some point with the same blue screen error.

I have 2 other VB machines running without issues with the latest VB 5.1.12 (Windows ThinPC x86 and Windows 7 Ultimate x64 same as the host OS).

HOST: Notebook HP Pavilion DV7-1005TX (with Virtualization Support enabled in Bios), Windows 7 Ultimate x64, 8 Gb RAM, video Nvidia 9600M GT on 17 inch display, Bitdefender Antivirus Free Edition.

GUEST: Windows 10 Pro x64 (September 2015)

I'm not an IT professional or expert (just a mechanical engineer). I usually don't change anything that is working, unless it's a critical update available. I never tried to boost, overclock, tune-up or anything beyond my limits as a simple regular Windows PC user.

Thank you.",Mike Skywalker
16358,USB MSD device BBB (bulk only) transfer fails due to CBW/CSW tag mismatch,other,VirtualBox 5.1.12,2017-01-05T15:11:23Z,2017-01-07T15:46:29Z,2017-01-07T15:46:29Z,"Host is Windows 7, guest is OS/2 (eComStation, latest of everything).
I am using this set of USB drivers in the guest:
http://hobbes.nmsu.edu/download/pub/incoming/usbdrv213.zip

I have an ""Alcor Micro Corp."" USB stick (vendor id: 0x58F, product id:0x6387).
If I connect that device to the guest it is properly detected as a USB 2.0 device and I can access it in the guest. However, if I start some lengthy operation like a chkdsk.exe on the device, I eventually get a mismatch of the tag word in the sent out CBW block and the subsequently received CSW block (I have detected this by enabling tracing for USBMSD.ADD in OS/2 and looking at the trace output). At the point of failure, the CSW tag is off by 1 from the tag transferred in the corresponding CBW and it is equal to the CBW and CSW of the last (successful) transmission (as can be expected). If the tag is out of sync the USBMSD.ADD driver issues a MSD reset command and subsequently clears the input and output bulk pipes which of course is reported back to the OS as a transfer failure.

If I use the very same device under a native OS/2 installation with the very same set of USB drivers, I can successfully run the chkdsk.
To me it looks like that on a large number of BBB transfers (where I cannot give a hard and fast value for ""large""), that the USB virtualization eventually gets out of sync.

Let me know if you need any Virtualbox logs.




",lerdmann
16349,"Linux host, Windows 10 guest: USB headset functions intermittently with Skype",Windows,VirtualBox 5.1.12,2017-01-03T13:13:02Z,2017-01-03T13:13:02Z,2017-01-03T13:13:02Z,"My system is the following.
Hardware: Lenovo ThinkPad T460
OS: Linux host (kernel 4.8.15, distribution Fedora 25) with Windows 10 guest
VirtualBox: 5.1.12 with extension packs on both ends of the same version
Additional hardware: Logitech USB headset H650e connected via xHCI USB 3.0 controller
Additional software: Skype 7.3.80.105 under Windows 10 guest

Symptoms
- during an audio call via Skype, the microphone of the USB headset will cease to function
- the Skype connection bars turn red and a warning appears that no microphone is connected
- the behaviour sometimes corrects itself but can not be predicted and is hard to reproduce

My VBox.log is attached.",aljperso
16343,Guest screen corruption with 3D enabled unless mini-toolbar enabled,Linux,VirtualBox 5.1.12,2017-01-01T08:50:41Z,2017-01-01T08:50:41Z,2017-01-01T08:50:41Z,"Seems likely this is actually a host problem, given the toolbar's impact.

VirtualBox 5.1.12 (also tested with 5.1.10 and 5.0.30, same results).
W7SP1 x64 host 8GB, Ubuntu MATE 14.04 x64 guest (kernel 3.13.0-106, X 1.15.1), GA, 2GB.
Host graphics: Radeon 7950 running 16.12.1 drivers.

In a fullscreen VM with 3D acceleration enabled, running glxgears (or even just glxinfo) blacks out the entire screen, and regions outside the glx-invoking window don't redraw until damaged. With no changes to host or guest, enabling ""Show in Fullscreen"" for the mini-toolbar makes the display behave correctly. Very bizarre. :)

I also completely uninstalled VirtualBox and reinstalled 5.1.12, no difference.

The guest WM is Marco (Metacity, effectively) and the behavior is the same whether that's running with or without compositing.

Q: Should I duplicate the logfiles in this ticket, or are the copies in the forum enough?
",arQon
16332,Guest Windows 10 displays black desktop on second screen,Windows,VirtualBox 5.1.12,2016-12-28T07:27:35Z,2016-12-28T07:27:35Z,2016-12-28T07:27:35Z,"My Virtualbox is installed in laptop, OS is windows 10, I also install a guest windows 10 to do some other tasks. I have a second screen connected to laptop and the guest windows 10 is displayed on second screen. 

If I don't shutdown/save the guest windows 10 then unplug in the second screen and then plugin second screen again:

1. The guest windows 10 will display a black desktop after I run mstsc on guest windows(even I closed mstsc). If I press Windows key on keyboard, Start menu and taskbar can be displayed on guest, but the desktop is still black. After the Start Menu and taskbar is hidden, all desktop is black again. To show the desktop, I write a bat file to restart explorer.exe, press Windows key + R to run the bat file, then the desktop can be displayed.

2. The virtualbox min bar will be displayed on first screen of laptop

My VirtualBox version is 5.1.12r112440(Qt5.6.2)
Host and Guest are latest Windows 10
Extention is installed on host, guest additional is install on guest and 3D support is open",Peak Zhang
16321,Failure when trying to do a second clone from one machine,Windows,VirtualBox 5.1.12,2016-12-23T17:18:55Z,2016-12-23T17:18:55Z,2016-12-23T17:18:55Z,"I need to make a total of 5 clones from a VHD, all with their own diff drive. See [http://koussilicious.blogspot.ca/2016/12/70-462-training-kit-setup-preparation.html]; these instructions are for Hyper-V but I thought it would work in VirtualBox.

I was able to successfully clone once. But when I did the second, I got this message:

Failed to create a snapshot of the virtual machine 2012R2Parent.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\Will\VirtualBox VMs\2012R2Parent\Snapshots\{a0565d45-af1f-44d6-809a-904e04b32f85}.vhd' does not match UUID {98edf193-685e-4931-8a08-66942b857091} of its parent medium stored in the media registry ('C:\Users\Will\.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

So in thinking it was that you could not have multiple clones, I tried a clone of a clone. The UI allowed this, but when clicking Create, I got a similar message. When trying to do this a second time to get the error details, the clone on a clone was disabled.

One thing to note is that, as soon as the above happened, the parent VHD was hopelessly corrupted, requiring the VM to be deleted and the VHD to also be deleted.",Will Power
16316,Kubuntu guest rendering errors with 3D acceleration enabled,Linux,VirtualBox 5.1.12,2016-12-22T14:15:09Z,2016-12-22T14:15:09Z,2016-12-22T14:15:09Z,"I'm running a Kubuntu 16.10 (64-bit) guest on VBox 5.1.12, host OS Windows 10 64-bit. As long as 3D acceleration is disabled, everything is fine. After enabling 3D acceleration the KDE toolbar disappears, and there are some artifacts on the screen.

Guest additions were installed",ErnstH
16313,drag and drop in virtualbox 5.1.12 fail in Centos 7.3,Linux,VirtualBox 5.1.12,2016-12-22T08:36:14Z,2016-12-22T09:27:30Z,2016-12-22T09:27:30Z,"When you log in Centos 7.3, after some times trying to drag and drop some file between guest and host systems a file repetively, this will not run ever again. Process will not run never again until you logoff from the system and login in it again.
Bidirectional mode are selected for drag and drop option.
It seem run only a few times, should be about three or four times until drag and drop crash it. Generally the process crash when you drag files at guest client, for example from windows to linux, having a virtual Centos 7.3 machine. The host machine is a windows 10 with the anniversary edition update included.",anruvel
16489,Cannot set VM icon,Windows,VirtualBox 5.1.14,2017-02-16T16:37:34Z,2018-12-24T17:02:42Z,2018-12-24T17:02:42Z,"While reading the manual I came across the vboxmanage command 'vboxmanage modifyvm VMNAME --iconfile'
According to the manual you can change the icon for the VM. I could not find anything else in the manual to emailed the iconfile specs (file type/resolution).
I tried to run the command and gave it the absolute path to a 128x128 .png file but the icon for the VM did not change. 
Is there more information for the --iconfile command? ",fletch
16515,DxgiOutputDuplication::AcquireNextFrame() does not work after Windows 10 1607 update,Windows,VirtualBox 5.1.14,2017-02-27T01:42:15Z,2018-09-26T12:57:59Z,2018-09-26T12:57:59Z,"I used to think this has been broken by VirtualBox update. But I have tried several versions, none of them work after Windows 10 1607 update. This API returns correct value, but the frame is just empty.
The API works well before 1607 update, but it also works well on several regular PCs. So it looks like something is wrong in VirtualBox driver or at least an incompatible behavior.

I have tried only on Windows host, I cannot tell whether it also stops working on other hosts.

You can try a MSDN sample at https://code.msdn.microsoft.com/windowsdesktop/Desktop-Duplication-Sample-da4c696a.

On VirtualBox instance https://drive.google.com/open?id=0B0OFNI4uoZGRNzdkSkZVcUdqOEk
On Thinkpad X1 forth generation https://drive.google.com/open?id=0B0OFNI4uoZGRdTFfbzctSml1RXc",Hzj_jie
16454,VERR_ACCESS_DENIED when using raw disk on Windows 10 host,Linux,VirtualBox 5.1.14,2017-02-04T18:51:58Z,2018-06-19T09:32:03Z,2018-06-19T09:32:03Z,"I created an Ubuntu 16.10 x86_64 VM and attach added raw disk to it which is an internal SATA hard drive (not the system one). I followed the procedure described in the manual for Windows hosts and successfully created a raw disk with VBoxManage.

However, during installation of the gust Ubuntu system as soon as it attempted to modify the disk the VM was paused with the following error:

The I/O cache encountered an error while updating data in medium ""ahci-0-0"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Error ID: 
BLKCACHE_IOERR
Severity: 
Non-Fatal Error

despite that I was running VirtualBox as admin.
",szx
16449,Flashing ROM on USB device fails,Linux,VirtualBox 5.1.14,2017-02-03T22:55:21Z,2017-12-12T10:11:07Z,2017-12-12T10:11:07Z,"I'm working with a custom device so there isn't an obvious way to reproduce the problem. When we flash the ROM on our custom USB device from Linux as a guest of Windows using VirtualBox, the process fails at the beginning of the process. One thing of note is that our device uses a different device ID when it's waiting to be flashed and when it is operating normally. This required 2 USB Device Filters to be added to VirtualBox. Thus process works on VMWare and on native Linux.
",capellsk
16472,Default VirtualBox configuration in MSI,Windows,VirtualBox 5.1.14,2017-02-09T12:00:23Z,2017-10-20T16:34:55Z,2017-10-20T16:34:55Z,"I need to preconfigure some global defaults for my users.

These are
- GUI/SuppressMessages=all
- GUI/UpdateDate=never
- defaultMachineFolder=""D:\Virtual Machines""

Updates are controlled via AD with MSI deployment. Can you add this as registry keys to the MSI setup, please? I explicitly need a way to set GLOBAL settings that are enforced to all users.",vboxuser4
16448,VBoxHardening issue (AV software),Linux,VirtualBox 5.1.14,2017-02-03T20:17:44Z,2017-10-04T09:15:23Z,2017-10-04T09:15:23Z,"Windows 7 Enterprise SP1
Virtual Box 5.1.10 was working fine until company pushed an update to my workstation.

I think the issue is related to Cylance Protect as that software seems to have been updated the day VB broke.
It's also possible kernel32.dll was updated by a windows update.

Error starting ALL VMs..

The virtual machine 'DeleteMe' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\MyProfile\VirtualBox VMs\DeleteMe\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}


The workstation/host has Cylance Protect and Symantec Endpoint Protection enabled (and I can't disable them to test).

I tried test builds.

5.1.10 original had the issue.
5.1.14 - same issue
5.1.15 - test build same issue.
5.1.51 - dev build same issue

",gingleby
16459,Cannot change Virtual Screen from Host screen 1 to 2 in Fullscreen mode,Windows,VirtualBox 5.1.14,2017-02-07T08:29:04Z,2017-09-28T04:06:13Z,2017-09-28T04:06:13Z,"Host: Windows 10 Pro x64 with 2 monitors

Guest: Windows 7 Pro x64

When in Full-screen mode, I used to be able to change from monitor 1 to monitor 2 and vice versa by going to View > Virtual Screen 1 > Use Host Screen 1/Use Host Screen 2. 

I believe since v5.1.12, I have to complete the previous step, exit reenter the Full-screen mode to switch the guest display to the other monitor.",Anh Le
16529,Linux guest additions update creates spurious initramfs copies,Linux,VirtualBox 5.1.14,2017-03-03T00:05:53Z,2017-06-25T15:13:43Z,2017-06-25T15:13:43Z,"With a Win7-X64 host and a CentOS7 guest, I've been seeing a problem for several months where everytime I tried to update the Guest Additions, more than a dozen old initramfs versions would get created, overflowing /boot. The Guest Additions update would only complete after I removed the earliest initramfs versions to make more room. Note that there are not old kernel versions on this system; only the 2 most recent kernels and a recovery are present.

After several attempts, I finally tracked this down to multiple old guest additions subdirectories under /opt. These were empty; apparently the old additions had been properly removed but the empty directories had been left around and this was confusing the guest additions update process. Removing these empty directories cured the problem.",JMHOGM
16457,Some menu categories in Linux guest OSes no longer populate,Linux,VirtualBox 5.1.14,2017-02-06T17:20:49Z,2017-04-21T14:43:31Z,2017-04-21T14:43:31Z,"Beginning with VirtualBox 5.1.14 r112924 and VirtualBox's corresponding Linux guest additions, certain menu categories in Linux Mint 18.1 Cinnamon and Chapeau Linux 24 guest OSes no longer populate. Specifically:

In Linux Mint 18.1 x64 Cinnamon, the following menu categories don't populate (i.e., are empty when selected):

* All Applications
* Accessories
* Administration
* Preferences
* Places

In Chapeau Linux, clicking on the ""All"" subpanel of Gnome 3.2's Activities > Applications panel causes all of the application icons to quickly flash onscreen and then disappear. The ""Frequent"" subpanel populates normally.

In Chapeau Linux with the Application Finder utility installed, the following menu categories in the Applications menu (which replaces the native Activities menu) don't populate:

* Accessories
* Utilities

If Application Finder itself is launched, all categories populate correctly.

Additional background:

* I'm running a Windows 7 x64 host.

* This problem did not occur with previous versions of VirtualBox. It began with the upgrade to VirtualBox 5.1.14 r112924 and installation of VirtualBox's corresponding Linux guest additions.

* This problem still does not occur in Linux Mint 18 ""Sarah"" Cinnamon.

* This problem does not occur with Linux Mint 18.1's own version of guest additions. (Unfortunately, Linux Mint's additions don't seem to support hardware rendering.)

* Because this bug prevents or hinders access to many applications, utilities, and settings via the GUI, I consider it major.",PierrePotame
16531,VirtualBox has issue With my Windows 10 Build 15046,Windows,VirtualBox 5.1.14,2017-03-03T09:13:41Z,2017-04-08T12:42:43Z,2017-04-08T12:42:43Z,"Hello

I have Windows 10 Build 15046 Installed in my Host, I also Installed VirtualBox. but When I started The Virtual Machine, It only show Windows 10 boot screen and VirtualBox BIOS initial screen, and It only Preview can Display Desktop, And the virtual machine window cannot display Windows 10 Guest desktop.

My Host: Windows 10 Build 15046

My Guest Windows 10 (1607)

Hope The issues will be resolved soon.

Thank you

-htjywf2008",htjywf2008
16577,VirtualBox Networking causing BSOD,Windows,VirtualBox 5.1.14,2017-03-18T10:38:03Z,2017-04-06T11:26:54Z,2017-04-06T11:26:54Z,"After installation of VirtualBox I see very often BSOD with error message DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by nwifi.sys. This actualle makes the computer more or less useless.

I have found out that installing VirtualBox without networking solves the problem (restored backup of computer to point without any virtualbox installed and retried. Also did it again and installed with networking and BSOD is back on first reboot).

Host Dell XPS13, Windows 10 Pro 64bit build 10586.839. It's not affected bu guest OS as the BSOD shows up just by installing VirtualBox so there is some driver issue in the host OS/VirtualBox",TurboJens
16406,Display bugs on HiDPI Windows hosts with two displays,all,VirtualBox 5.1.14,2017-01-19T18:45:16Z,2017-03-27T15:47:08Z,2017-03-27T15:47:08Z,"I'm running VirtualBox on a Windows machine which has two screens: one HiDPI with 200% scaling enabled, and the second one using 100% scaling.

When I launch VirtualBox Manager, it launches with 200% scaling (which is correct), but when I drag VirtualBox Manager window to my second display, it doesn't rescale correctly (see attached screenshots).

What's worse, VM window doesn't scale at all when dragged to the second screen.

This bug was introduced in 5.1.0 release.",VasilyA
16554,"VirtualBox on Windows 10 leaks hostonlyifs, turning them into bridgedifs which cannot be removed",Linux,VirtualBox 5.1.14,2017-03-12T09:34:39Z,2017-03-12T09:34:39Z,2017-03-12T09:34:39Z,"It has happened twice now on my machine. The first time I lost hostonlyif 1 through 5 after an Vbox upgrade - searched a while for a solution, but gave up and created new ones ""VirtualBox Host-Only Ethernet Adapter #6"" through #12. That was more than 6 months ago.

Last week I noticed that my host only interfaces were gone again. Not sure on which upgrade, but I was on a 5.0 version. Upgraded to the latest, and some cleanup and reboots, and the problem is still there. Did not try an uninstall and reinstall because that didn't help the last time.

The current state is as follows:

I can create and delete host only interfaces, but the starting number is ""VirtualBox Host-Only Ethernet Adapter #13""
""VBoxManage.exe list -l bridgedifs"" returns a list with all my lost host only interfaces - but I cannot find a command to delete the bridged interfaces.
I can find these in the windows registry by searching the GUID, and also by name in Computer/HKEY_LOCAL_MACHINE/SYSTEM/Setup/Upgrade/NetworkDriveBackup/Control/Class but hesitate to mess with the registry manually, because there are too many references to clean up by hand. Searched for a powershell utility that could clean and free them up, but didn't find one.
Looking for help. Partial output of ""VBoxManage.exe list -l bridgedifs"" looks like this - as you can see by the name they used to all be host only ifs:

PS C:\WINDOWS\system32> VBoxManage.exe list -l bridgedifs

Name: VirtualBox Host-Only Ethernet Adapter #8 GUID: ef9a148d-dbbd-4eac-a072-bae5f0aae49b DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #8

Name: VirtualBox Host-Only Ethernet Adapter #3 GUID: 873d770d-328c-4af6-a0e8-900433a03cf6 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

Name: Microsoft Virtual WiFi Miniport Adapter GUID: a35fb3ad-bb85-4bfc-b9c1-05ce81d512cb DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-Microsoft Virtual WiFi Miniport Adapter

Name: VirtualBox Host-Only Ethernet Adapter #10 GUID: 1e88234f-d548-4b03-a2c2-b7c73f1016b1 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #10

Name: VirtualBox Host-Only Ethernet Adapter #6 GUID: fed303cd-386b-4f60-8419-1c71b53fa90a DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #6

Name: VirtualBox Host-Only Ethernet Adapter #2 GUID: f6d1349b-82f4-4ce2-ae42-e7fb19f7fdf4 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

",rezroo
16442,Could not install Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924,other,VirtualBox 5.1.14,2017-02-02T16:58:46Z,2017-03-09T15:28:40Z,2017-03-09T15:28:40Z,"Hello,

on a Windows 10 machine, trying to open Oracle_VM_VirtualBox_Extension_Pack-5.1.14-112924 results in 

This application failed to start because it could not find or load the qt platform plugin ""windows"" in """".
Reinstalling the application may fix this problem.

VBox 5.1.14 - latest version is installed and running properly.
Tried repairing VBox but no change in the problem.

What can I do ? 

Thanks
E. Gimissis
MSc ICSD
MCP",elrod68
16519,Network bandwidth limit in GUI,all,VirtualBox 5.1.14,2017-02-27T15:21:43Z,2017-03-09T15:17:34Z,2017-03-09T15:17:34Z,It would be good if one could adjust the network speed or limitation easily in the GUI. The detour via the VBoxManager is very cumbersome.(https://www.virtualbox.org/manual/ch08.html --> bandwidthctl),LMS23
16537,Hgh screen resoluton on a MS-DOS 6.22/Win 3.1 VM,other,VirtualBox 5.1.14,2017-03-07T18:01:49Z,2017-03-07T21:59:21Z,2017-03-07T21:59:21Z,"Hi all,

Back when I was a kid, oh, about sometime in the mid 90s if you can go back in the ""wayback machine"" with me, I thought 640x480 was all the screen resolution I'd ever need.  My huge CRT displayed Windows 3.1 just fine back then, or so I thought.

Now, flash forward to 2017 and I have a spiffy 27-inch monitor on my computer at work.  This computer hosts a VirtualBox VM running MS-DOS 6.22 and Windows 3.1.  I am needing access to yesteryear for my job (!) because of the software this company maintains for some of its customers who, apparently, like running MS-DOS 6.22 just fine, thank you very much! :-)

So, I spun up a Oracle VM VirtualBox running MS-DOS 6.22 and Windows 3.1 thanks to some handy dandy tutorial and disk-image websites that I found.  Now, however, it will not allow me to change the screen resolution up beyond 640x480, which on my spiffy 27 inch monitor with its 2560x1440 resolution, looks soooo tiny.  Entering scaled mode does not really help, since now everything just is stretched accordingly (i.e., the Program Manager still has a small UI, just stretched and scaled into a bigger window.)

Is there any way I can tune my VM to have a higher screen resolution (i.e., smaller pixels)?  I seem to recall Windows 3.1 being responsive to those settings back in the day, but I can't quite get my head around it.",astrohart
16533,Boot from usb device.,other,VirtualBox 5.1.14,2017-03-04T11:39:58Z,2017-03-04T11:39:58Z,2017-03-04T11:39:58Z,Add boot from usb device.,q34er6ty7
16526,Google Chrome Stable Crashes Linux Guest,Linux,VirtualBox 5.1.14,2017-03-02T16:29:09Z,2017-03-02T16:40:47Z,2017-03-02T16:40:47Z,"I am not sure about the complete steps, but I can reproduce this each, and every time.  I launch Google Chrome (Version 56.0.2924.87 (64-bit)) under Ubuntu GNOME 16.04.2 Guest.  I visit a Cisco Acano URL to join a meeting (such as https://join.<some domain>.com/invited.sf?secret=QtsgKqo7mTqO2O4pOM0ouB&id=77223344).  When I join the meeting, VirtualBox crashes with an error message, such as:

    The instruction at 0xdc7aa4f2 referenced memory at 0x00000028.  The memory could not be read.  Click on OK to terminate the program.

Host:  Windows 7 Professional SP-1
       16GB RAM
       AMD Radeon R7 M360/Intel HD Graphics 520
       Dual Core i7
       Three monitors (laptop + two external)
Guest: Ubuntu GNOME 16.04.2
       8GB RAM
       128MB VRAM
       2 CPU
       2 Monitors
",JayBofMA
16525,Automatically switching to Seamless mode on start does not use full screen area,Linux,VirtualBox 5.1.14,2017-03-02T13:15:31Z,2017-03-02T13:15:31Z,2017-03-02T13:15:31Z,"If my Arch Linux x64 guest (on Win10 x64 host) is closed with seamless mode running, when I restart the guest there's a popup saying to switch back to seamless mode. If I click okay, seamless mode starts but there's a gap at the top from the vbox guest OS menu. I have to ctrl+L and ctrl+L again to get it to recognize the actual display size.",R
16521,no NetworkBridge Mode,all,VirtualBox 5.1.14,2017-02-28T18:40:31Z,2017-02-28T18:40:31Z,2017-02-28T18:40:31Z,"NAT works fine
NetworkBridge Mode dont work.
It gets an IP-Adress, ping works,
but no trafic, no Website loads, div. ...

last things done:
Update from 5.0.32 to 5.1.14rxxxxxx

Machines:
Ubuntu 16.04,
W10pro
W7pro
Xubuntu
Linux Mint Sarah
WinXP-Pro
ipFire
pfSene
",Bardo
16517,Drag and drop not working,Solaris,VirtualBox 5.1.14,2017-02-27T06:59:51Z,2017-02-27T06:59:51Z,2017-02-27T06:59:51Z,"I used to be able to drag and drop using solaris 11.4.2 but lost that when I upgraded to solaris 11.3. 
I am using a windows 7 (host )  and running solaris 13 as a guest on virtual box 5.1.14. 

Extension pack is updated. ",fg2017
16516,HTTPS request before LaunchVMProcess let sound crash in guest,Windows,VirtualBox 5.1.14,2017-02-27T06:49:59Z,2017-02-27T06:49:59Z,2017-02-27T06:49:59Z,"On a Win7 Guest, Host doesn't mind (tested Win 7 and 10), doing 
[[BR]]
{{{
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(""https://www.google.de"");
HttpWebResponse res = (HttpWebResponse)req.GetResponse();
}}}
before
[[BR]]
{{{
VirtualBox.VirtualBox vBox = new VirtualBox.VirtualBox();
IMachine m = vBox.FindMachine(""VM"");
m.LaunchVMProcess(new Session(), ""gui"", """");
}}}
[[BR]]
the sound in the guest system stops working with 
[[BR]][[BR]]
DSound: Starting playback failed with E_ACCESSDENIED
[[BR]][[BR]]
Switching the https to http in above code, everything will work as expected. 
[[BR]][[BR]]
Additionally, starting the VM without a webrequest (from API or VBoxManage), stopping it and letting VBoxSVC not terminate, means starting the guest by above code immediately, then the https request will not interfere with the guest sound.

Thanks in advance.[[BR]]
Kind regard[[BR]]
Ben",Benne
16511,Running VBox prevents notebook from switching into sleeping mode,other,VirtualBox 5.1.14,2017-02-25T09:32:07Z,2017-02-25T12:42:30Z,2017-02-25T12:42:30Z,"Running VBox (any guest) prevents notebook from switching into sleeping mode.

It looks like Windows can't set on pause or VBox fails to catch that signal from OS. May it be very exclusive usage of CPU by VBox?

For e.g., you can start compiling kernel in guest FreeBSD and try to switch notebook into sleeping mode to see it fails to.",MikhailRokhin
16510,Sound volume not working in guest (winxp x32). Host - kubuntu 16.04.2 LTS x64,Linux,VirtualBox 5.1.14,2017-02-25T08:52:43Z,2017-02-25T08:52:43Z,2017-02-25T08:52:43Z,"Sound volume not working in guest (winxp x32). Host - kubuntu 16.04.2 LTS x64
Not work change sound volume (Even if off - really volume is 100%). I tested 5.0.32 and 5.1.14. Not work checkbox to volume off (volume is 100%)

For disable sound in VM - i disable Intel 82801AA sound controller in VM.

I test with last guest addition for winXP. - volume not changed.
Win7 x32 guest - volume work all right (but slight stutters).",unicorp99
16440,"As a guest, must hold keyboard key a second or more",Linux,VirtualBox 5.1.14,2017-02-01T20:49:13Z,2017-02-24T20:12:44Z,2017-02-24T20:12:44Z,"Previously used Control Panel to uninstall VBox 5.0.4 (was installed through MyDesktop)

Uninstalled VBox 5.1.14 which I'm having keyboard issues with (must hold keys for them to be recognized)

Re-downloaded VirtualBox-5.1.14-112924-Win.exe

Installed VBox 5.1.14, used all defaults

Used Start to bring up Oracle VM VirtualBox

Within VBox Manager, clicked on Start (Oracle Linux Server 6.6), replied with password to ""jhoelsch4.dev"" login.  Information had apparently been retained from a previous install of VBox.  So, looks like there are bits of configuration detail, probably retained in the registry.

Three windows are generated:
- Development [Running] - Oracle VM VirtualBox : 1
- Development [Running] - Oracle VM VirtualBox : 2  (contains icons Computer, jhoelsch's Home, Trash, sf_AutoImage, VBOXADDITIONS_5  1.13_112924)
- Development [Running] - Oracle VM VirtualBox : 3 (identical to window 1 above)
When password was entered in window 1, the same keystrokes were echoed in window 3.

Right-click on jhoelsch's Terminal -> Open In Terminal.  This is where keys must be held extra long to be recognized

Notes: 
sf_AutoImage is residual from a shared folder from a prior VBox install.
",John Hoelscher
16507,Windows 10 freezes when using a KVM switch while VirtualBox is running VMs,Linux,VirtualBox 5.1.14,2017-02-23T18:53:48Z,2017-02-23T18:53:48Z,2017-02-23T18:53:48Z,"I have the following problem. I have Windows 10 PC, Virtualbox 5.1.14 r112924 installed, and a Keyboard/Mouse Switch via USB connected to this PC for Mouse and Keyboard.
Using the KVM switch is working perfectly fine with all applications.
BUT when I run a VM in VirtualBox, and then I use the KVM switch to connect to another computer, and switch back to Windows 10, I have no access to that computer anymore. Keyboard and Mouse don't work anymore. I have to hard reboot the Windows 10 computer. This is reproducible every time. The guest OS is always CentOS 7.2.",bati2712
16500,An USB issue only on Linux guest,Linux,VirtualBox 5.1.14,2017-02-21T07:55:44Z,2017-02-22T21:07:35Z,2017-02-22T21:07:35Z,"I try to use a common FTDI based USB UART (virtual serial port) chips on Win7 host and 32 bit Linux guest and it causes serial communication to drop because some received serial data is lost within seconds of usage. FTDI chips use USB 1.1 are known to work reliably on Linux too.

It has repeated at least on VBox 4.3.5, 5.1.10, 5.1.12 and 5.1.14 on two completely different host computers and various 32bit guests also (debial/ubuntu). USB mode setting 1.1, 2.0 and 3.0 have been tested - no difference.

I've tested vmWare Workstation Player on same computer and same guest image, and it WORKED FLAWLESSLY (10hr+ stress test done). Also it works on same computers with Win7 guest. So problem seems to occurs only with Linux guest + virtualbox combo.

I hope this helps!",reTok
16484,Crash during guest OS startup,other,VirtualBox 5.1.14,2017-02-12T18:21:02Z,2017-02-12T18:21:02Z,2017-02-12T18:21:02Z,"VM crashes during guest OS startup: blue screen on Windows 7, kernel panic on Ubuntu
The crashed appeared suddenly: I do not see any changes in guest and host OS.

Guest OS: Windows 7 54 bit, Ubuntu 64 bit
Host OS: Windows 10 64 bit, version 10.0.14393
VitualBox version: 5.1.14, 5.1.15
",airatsa
16471,TinyCore 7.2 boots on VB 5.0.32 but not on 5.1.14,Linux,VirtualBox 5.1.14,2017-02-09T10:41:13Z,2017-02-09T10:41:13Z,2017-02-09T10:41:13Z,"On a first machine: Win10 - VB 5.1.6, TinyCore-7.2.iso boots fine.

On a second machine: Win8 - VB 5.1.14, CorePlus-7.2.iso or TinyCore-7.2.iso fail with:

{{{
Code:  Bad EIP value.
EIP: [<fefa201c>]  SS:ESP 0068:c703bea4
---[ end trace 91cd7754bf702e09 ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

}}}

Full console log attached. The VB log is no more available.

For trial, I uninstalled 5.1.14 and installed 5.0.32, and it worked.",Psam
16467,Unlink of locked file fails on shared folder,Linux,VirtualBox 5.1.14,2017-02-08T16:42:00Z,2017-02-08T16:42:00Z,2017-02-08T16:42:00Z,"I noticed that some programs crash, when working on data in a shared folder. I recorded the file operations with strace and was able to write a small program, that reproduces the error. The attached program basically acquires a lock on a file and then tries to delete it before closing.

To reproduce the error, execute the attached program in a Linux guest, on a Windows host. It prints ""Test failed"" when being executed in a shared folder. When executed outside the shared folder, it prints ""Test passed.""",egooo
16456,"Windows 10: Installation hangs at ""NetLwf will be installed ...""",all,VirtualBox 5.1.14,2017-02-05T21:22:34Z,2017-02-05T21:22:34Z,2017-02-05T21:22:34Z,"I tried to install VirtualBox 5.1.14 on the weekend on my computer (Windows 10 Version 1607).
Unfortunately the installation hangs at a certain point.
The log shows the following information:

{{{
InstallNetLwf: Installing NetLwf
NetLwf is not installed currently
NetLwf will be installed ...
Installing 1 INF files ...
}}}


I used a Windows 10 image to restore my computer and tried the installation several times, but it never worked.

If I performe the installation without the VBoxNetwork-features the installation works.

It would be really great if somebody could help me.
If you need any more logs just tell me.",Rafter
16451,GUI Manager crashes when adding existing vdi file,Windows,VirtualBox 5.1.14,2017-02-04T12:21:09Z,2017-02-04T12:21:09Z,2017-02-04T12:21:09Z,Creating a new Windows guest under Windows 7 Host.  Trying to attach an existing vdi file.  If you click on the + at the bottom of the screen the manager crashes (see attached screen capture).  Luckily if you click on the + at the top of the screen it all works!  Maybe the easiest fix would be to remove the + and - at the bottom of the screen.  ,JimAttrill
16447,Multi-monitor failure with drag & drop enabled,Windows,VirtualBox 5.1.14,2017-02-03T15:18:00Z,2017-02-03T15:18:00Z,2017-02-03T15:18:00Z,"Host and Guest are both Win-7 64-bit.  Bi-directional drag-and-drop is enabled.  Beginning immediately after booting, moving a file from desktop on primary monitor to secondary monitor works fine.  Attempting to drag a file back from secondary monitor to primary causes screen lockup when transitioning across screen boundaries, even before releasing left mouse button.  Clicking start orb brings up menu, which then becomes permanent on screen.  CPU usage indicator looks like it goes to 50%.  Session information shows disk read data continuously climbing.  Inserting ctrl-alt-del brings up full-screen menu.  Process monitor will come up if selected, but response is extremely slow.  Switching users from ctrl-alt-del back to same (only defined user) comes back to black screens.  Logout and then login from ctrl-alt-del menu clears the problem and screens are unlocked until trying to do another d&d from secondary to primary monitor.  Enabling/disabling 2D and 3D acceleration has no effect.  Switching drag-and-drop to host-to-guest solves the problem, while obviously losing guest-to-host functionality.  I have been using a shared folder for years to move files back and forth between host and guest, so this is a very minor inconvenience.  Other than, it took many hours to figure out why my shiny new 64-bit VM was locking up.  I have not found any other reporting of this problem.  Because this is a production machine, I did not test with a test version of VirtualBox.  Please let me know how I can be helpful.",DougL
16434,Cannot resize VM Win7 on Win 10 Host,other,VirtualBox 5.1.14,2017-01-30T08:59:18Z,2017-02-02T22:14:54Z,2017-02-02T22:14:54Z,"Hello
Please give me any advice regarding my problem:
I cannot resize VM Win7 on Win 10 Host.
Plese see attached images.
Thank you
Best regards",movis
16420,Snapshots present but required Machine/@currentSnapshot attribute is missing.,Linux,VirtualBox 5.1.14,2017-01-24T11:29:01Z,2017-01-30T11:58:24Z,2017-01-30T11:58:24Z,"Hello,

since morning I receive this issue when starting directly into Virtualbox.
Yesterday I used my Ubuntu VM, took a snapshot and closed it.

Everything looked fine.

Please tell me a solution.

Thank you.

Regards

Andreas",Haemma
16433,The installer won't work error 2755 and when I can get it installed another problem happens.,Linux,VirtualBox 5.1.14,2017-01-30T04:26:09Z,2017-01-30T04:26:09Z,2017-01-30T04:26:09Z,"The problem when I got virtualbox installed, it would tell me an error that it couldn't acquire the COM object. I have checked to make sore there are no corrupt registry files, I've deleted some of the old virtualbox files on my system, I even deleted the installer folder in windows32, along with deleting and removing virtualbox and reinstalling. I haven't been able to fix this problem, it was all working fine about a month ago and then one day when I decided to use VBox it just stopped working saying that it can't acquire the COM object ",Kingy
16411,Fails to transfer binary values copy/paste clipboard to and from host/guest,Windows,VirtualBox 5.1.14,2017-01-20T12:36:06Z,2017-01-23T13:20:41Z,2017-01-23T13:20:41Z,"Try to copy binary value from Windows registry either at host or guest
 and to paste to guest/host.

Expected - ordinary copy/paste.

While ordinary text is copy/past -ed as expected.
",MikhailRokhin
16547,Full screen mode only displays on 1 screen,Windows,VirtualBox 5.1.16,2017-03-10T05:13:11Z,2022-08-22T13:21:46Z,2022-08-22T13:21:46Z,"I've just upgraded to 5.1.16 hoping this problem will be resolved. When running my guest in full screen, it only displays on one of my screens (Screen 2). Does not matter if I select a different screen under View -> Virtual screen 1 -> Host host screen 1/2

If I plug screen 2 out, then it works, but the moment I plug it in, it goes back to screen 2",Jaques
16543,High CPU load with MP Linux 4.10 guest,Linux,VirtualBox 5.1.16,2017-03-09T09:21:48Z,2018-08-22T07:53:27Z,2018-08-22T07:53:27Z,"When a Linux 32-bit guest is configured with 2 processors and uses the 4.10 kernel, it loads 100% a host processor core.
It doesn't happen with kernel 4.9 and before.
It doesn't happen with a single guest processor.

During boot the message {{{smpboot: do_boot_cpu failed(-1) to wakeup CPU#1}}} appears.",Urmas
17393,failed to open a session Machinewrap E_FAIL 0x80004005,other,VirtualBox 5.1.16,2017-12-23T11:43:15Z,2017-12-25T10:18:49Z,2017-12-25T10:18:49Z,"'''GUEST is UBUNTU,  Host is windos10.
'''   I JUST GOT UPDATED(small update) MY WINDOWS 10(earlier also windos10) HOST. before update of windos10, virtualbox working finely. After update, virtualbox not opening and shows error. failed to open a session Machinewrap E_FAIL 0x80004005. please try to help me in fixing.[[Image()]]",SUPARI
16541,W10 guest crashes on Win8.1 host all the time (ICH9),Windows,VirtualBox 5.1.16,2017-03-09T00:59:24Z,2017-03-16T13:19:47Z,2017-03-16T13:19:47Z,The screen freezes so I can't make out what the bluescreen is.,Stanzilla
16565,5.1.16 Guest Additions render CentOS7 VM unusable,other,VirtualBox 5.1.16,2017-03-15T01:51:52Z,2017-03-15T02:17:56Z,2017-03-15T02:17:56Z,"After upgrading to 5.1.16 from 5.1.12, CentOS 7 fails to boot due to failure to load SELinux Policy.  Attempted (as root) 'yum reinstall selinux-targeted-policy' after GRUB coercion to boot without SELinux loaded.  Also tried (as root) 'touch /.autorelabel'.  Reboot successfully updated SELinux, however subsequent reboots fail on original issue.  
",crowmastr
16553,Virtual Machines running very slowly,Linux,VirtualBox 5.1.16,2017-03-11T13:47:57Z,2017-03-14T09:18:51Z,2017-03-14T09:18:51Z,"Hi there,

Apologies if this turns out to be something trivial, but I hope you can help - I've been running Kali Linux / Metasploitable / Windows XP virtual machines using virtual box with no issues until a couple of weeks ago they all suddenly started going unusably slowly, taking ages to even log in and even then extremely laggy to use.

I'm running windows 10 on a HP Desktop with Dual core 1.9GHz and 8GB RAM

What I've tried:

Allocating more RAM / Vram to the VMs - Kali 2GB / 128MB Video

switching between 64-bit and 32-bit versions (my OS is 64 bit)

Uninstalling Vbox and removing all VMs, then re-installing them.

changing chipset from PIIX 3 to ICH9

enable I/0 APIC has always been checked
Hardware clock in UTC time always checked
Enable PAE/NX always checked
Video - Enable 3D Acceleration checked, 128MB allocated 
Storage controller SATA, AHCI, Port count 1, Use host I/O cache checked
Network adapter enabled, NATNetwork selected

I noticed that in the system settings, the 'acceleration' tab was suddenly 'greyed' out - this definitely wasn't the case previously. After some digging, I realised this was related to VTx acceleration, so I logged into my BIOS, enabled it and the acceleration tab came back - I checked the box, but unfortunately it has made no difference. Paravirtualization interface set to 'Legacy' (as it has been), Enable VTx/AMD-v checked, Enable nested paging checked.

Seems really strange as it was working perfectly well previously, so obviously something has changed... perhaps some windows update has caused problems, I have no idea.

I have the same setup running on other machines in the school I work at - older apple machines with a lower spec than my own, and it works fine on them!

Any assistance you can offer is greatly appreciated - sorry if I haven't provided enough info, please let me know what you need.

Many thanks,

George



",GMullin
16559,Mouse pointer misaligned,Linux,VirtualBox 5.1.16,2017-03-14T08:02:22Z,2017-03-14T09:13:12Z,2017-03-14T09:13:12Z,"Host Windows 7, guest Fedora 25, VirtualBox 5.1.16
Two displays (different resolutions), extended

The mouse pointer is misaligned in several applications. After started Fedora 25, I click Activities in top left corner. The sidebar with activities appears on the left side of the display. At this moment no problems with mouse alignment, i.e. the icon highlights when the mouse hoovers it.

I click 'Show Applications' from the sidebar. The list with applications shows up. Now the mouse is misaligned: the icon that is highlighted is not the one where the mouse pointer is. E.g. when the mouse is in the middle of the display, a icon much further to the right lights up.

I couldn't find a solution for it. Latest updates for the Windows host and Fedora guest are installed.
",peterka
16558,missing menu item to enable/disable virtual screen,Linux,VirtualBox 5.1.16,2017-03-13T17:27:08Z,2017-03-13T17:51:02Z,2017-03-13T17:51:02Z,"While Debian Linux Virtualbox machine running on windows 7 host with 3 screens configured, there is no longer a menu item to enable/disable virtual screens.  Lost the menu item one I messed with toolbar and menu placement configuration. Also, hover over disable toolbar icon shows 3 displays, but right click does not bring up any menu either.  ",smichel
16664,"Graphics: extensive pixelation and discoloration with VirtualBox graphcis driver and Aero enabled; Windows 7, 8.1, 10",Windows,VirtualBox 5.1.18,2017-04-18T14:42:23Z,2019-01-08T13:12:32Z,2019-01-08T13:12:32Z,"I install clean Windows 7/8/1/10 installations.
I then install Guest Additions with the default graphics driver, and restart.
For Windows 7, I manually enable Aero. For Windows 8.1 & 10, this is automatic.
Everything is fine until I start a Windows Installer program, or try to uninstall certain programs.
At this point the display starts to become pixelated and discolored.
Each time I change screens or move the cursor the pixilation becomes worse.

SPECIFICS:
The only way to get rid of the pixilation without restarting the VM is to restore (un-maximize) and maximize the VM display window.
I started noticing this about a month ago.
I tried rolling back the VM additions and graphics drivers to the versions when this wasn't yet a problem, but that does not fix it.
This occurs in Windows 7, 8.1, and 10, in both x86 and x64.
This problem can be avoided by disabling Aero in Windows 7. HOWEVER, disabling Aero transparency does NOT fix Windows 8.1 or 10.
This is not remedied by changing the amount of VM graphics memory, 2D settings, or 3D settings. I tried ALL combinations of enabling and disabling these.
HOST GRAPHICS: NVidia GeForce GTX 970M
HOST OS: Windows 10 x64
LOG: Attached. Starts at VM bootup and ends at first signs of this pixilation.",JMH1
16651,fatal error in recompiler cpu (raw mode),Windows,VirtualBox 5.1.18,2017-04-14T08:34:11Z,2018-04-09T05:48:09Z,2018-04-09T05:48:09Z,"VirtualBox VM 5.1.18 r114002 win.amd64 (Mar 15 2017 16:16:14) 

When I try to reboot a VM that avails worked fine I got this error.
When I use a cone of the same VM all works fine.  ",Giorgio SIlvio
16676,I get an error E_FAIL (0x80004005) when saving the state of my machine,Windows,VirtualBox 5.1.18,2017-04-20T13:47:11Z,2017-04-20T13:47:11Z,2017-04-20T13:47:11Z,"I work on a virtual machine with a lot of things open and I like save the state of my machine instead of turn it off, but a few days ago that I get this error every time and i don't know why it is",rusoLoco22
16656,"after command init 6, generate core dump and duplicate UUID",Linux,VirtualBox 5.1.18,2017-04-15T19:51:50Z,2017-04-18T20:12:40Z,2017-04-18T20:12:40Z,"Hello,
unfortunately I answered yes to upgrade on Virtualbox 5.0.12 hang on create new disk, resolved on 5.1.19 and install it.
Virtualbox 5.1.19 corrupted 6 Guest Machine and install 5.1.51-114298

Now it is not present later, he returned to version 5.0.12 that worked well?
I honestly did not know if the problem is in virtualbox core or in the host machine, with win7.

the problems that I see right now are:
- Duplication of Guest UUID that worked and you can not run the start
- see attach: although, on this generated core dump I found something and I just solved will update

Regards, Massimo",maximilian
16662,SoftICE Doesn't Refresh,Windows,VirtualBox 5.1.18,2017-04-18T11:02:35Z,2017-04-18T11:02:35Z,2017-04-18T11:02:35Z, https://forums.virtualbox.org/viewtopic.php?f=2&t=41499,Tommaso Blarzino
16645,"VirtualBox.dll"" failed, rc=1790",other,VirtualBox 5.1.18,2017-04-10T16:23:33Z,2017-04-13T15:06:28Z,2017-04-13T15:06:28Z,"The virtual machine 'test' has terminated unexpectedly during 
startup with exit code 1 (0x1). More details may be available in 
'C:\Users\David\VirtualBox VMs\test\Logs\VBoxHardening.log'.",David Popple
16641,"Shared Clipboard, drag and drop, and mouse-dragging STOP working in Win XP Guest",Windows,VirtualBox 5.1.18,2017-04-06T21:10:22Z,2017-04-06T21:10:22Z,2017-04-06T21:10:22Z,"I'm hosting in Windows 7 x64
Guest OS: Windows XP 5.1 SP3
I'm using Virtual Box 5.1.18r114002


I repeatedly get the following symptom. I can sometimes fix it by reinstalling the Guest Extensions (v5.1.18)

Mouse Dragging in the Guest OS (Windows XP) stops working. I can't drag Windows Xplorer window
I can't drag or paste files from Host to Guest. (If I copy a file from Host, and right-click in Guest, PASTE is disabled.)

This has been happening for months. Driving me crazy :(


",MrAnalogy
16638,Don't import appliances if there's not enough space on disk,Linux,VirtualBox 5.1.18,2017-04-05T18:50:26Z,2017-04-06T10:26:05Z,2017-04-06T10:26:05Z,"When importing appliances, it is common that the appliance file is smaller than the actual guest disk size.
Given that, if you are importing an appliance and you don't know the guest disk size, you'll get an error after the host disk is full.
Some import operations may take up to a hour, or more, so if you get the error after the import cannot continue, this is a little frustating to see the time you could save.

E.g.: I have a 20GB appliance the allocates more than 100GB. I was trying to import it on a disk with 80GB free. After 40min importing, I got the allocation error.

So, my suggestion is to show the final size for allocated space in the import dialog, or maybe even check the drive that the user is placing the VM disk and give a message like 'You don't have enough space to import that machine here', or something like that.",tgarcia
16605,Network dropouts in guest since Windows 10 update to 1607 version,Windows,VirtualBox 5.1.18,2017-03-24T15:38:35Z,2017-03-31T10:07:18Z,2017-03-31T10:07:18Z,"I got here following situation. I have a Windows 10 x64 guest on the same OS host. Right now I reduced the amount of installed programs in the guest to the minimum to find the culprit. So right now there is an antivirus (latest Nod32), Firefox and MP3 Player (Xmplay) beside the OS itself. I use the last program for Internet radio since XP days, and there were no problem until now, in and outside the VM. 

Since guest update to the 1607 I can see following behavior: after 15 or 20 minutes of the streaming player starts to buffer at 70-80 % spontaneously around once in a minute, which breaks a streaming experience. One still can listen to the radio, but this is a little bit annoying. This problem only occurs if the Firefox also running in the guest. Something, I don’t know what, but probably some advertisement or data refresh, loads a little amount of the data over and over again once in nearly a minute. I got some network bandwidth pictures which explain the network flow better. But the problem isn’t a bandwidth itself – I can run a bandwidth test, which would use the whole bandwidth and still there would be no buffering. The problem is a timing, because as one can see we have something like 6 or 8 KB/s from the stream constantly, but once in a while the browser adds some 18-20 KB/s to it. So after a while there are some de-synchronization in the flow, which causes the buffering.

This only happens in the guest and only if the browser running with some sites open. If one turns the browser off, there is no buffering. Also, this can’t be reproduced running same player and stream on the host, neither with Firefox also opened on the host with some sites in it, or with Firefox running in the guest, causing the same traffic shape on the host. First of all a thought that this was a new issue with a new VB version, but I tested this with following versions (5.0.30 - 36, 5.1.6, 5.1.10, 12, 14, 16, 18) and the picture is always the same. Changing network adapter from 82540EM to paravirtualized also brings no cure. I tested it with following version of the network adapter drivers (virtio-win-0.1.110, 112, 113, 117, 118, 126, 134), but it always looks the same. There were also no such problems as I updated the host first, before the guest. The clean install of the guest OS from the scratch also doesn’t change anything in this case, but installing the previous version of Windows 10 (1511) in the guest solves the problem. I think, that the problem caused by some TCP/IP optimization in the new Windows version, as described [[https://blogs.technet.microsoft.com/networking/2016/07/18/announcing-new-transport-advancements-in-the-anniversary-update-for-windows-10-and-windows-server-2016/|here]], the Initial Congestion Window 10 probably. If this is important – I hear following [[https://rfe04.akacast.akamaistream.net/7/509/437762/v1/ibb.akacast.akamaistream.net/rfe04?download=1|stream]] for example, but I think any other stream should also do the job. I would like to debug the network stack in the guest, but I don’t know how.

VM is running in the NAT mode. I hope that my description of the issue is clear, in spite of so much text.",boxer01
16620,Crash when removing USB device,Linux,VirtualBox 5.1.18,2017-03-29T16:07:08Z,2017-03-29T16:07:08Z,2017-03-29T16:07:08Z,"I have a USB Wi-Fi dongle which I occasionally use from my virtual Linux guest (besides an ordinary Ethernet connection via the Windows host). I got into the habit of removing it virtually (i.e making it invisible to the guest via the VirtualBox pop-up menu → Devices → USB, then unchecking the relevant device) before saving the state of the virtual machine, because if I don’t do that I occasionally get my Linux guest’s system log spammed with error messages when I restore the virtual machine.

In 5.0.32 (and at least a couple of earlier versions) it worked without a hitch, but in 5.1.18 the guest crashes when I do it. Specifically, I get a Windows pop-up (and an entry in Windows application log) with a message like this:
>  VirtualBox.exe - Application Error : The instruction at 0x00007FFD56EA7D70 referenced memory at 0x00000000000000E8. The memory could not be read.

If I do not close the pop-up, the virtual machine crashes soon anyway. In one case, it crashed when I tried to save its state; in another, it crashed as soon as I tried to sync the filesystem in the Linux guest (via the sync command).

As the bug is a deal-breaker to me, I have returned to 5.0.32.

Host: Windows 10 Pro 64-bit[[br]]
Guest: Ubuntu 14.04.5 LTS 64-bit with Guest Additions installed",mgrzegor
16616,The instruction at 0xdbbf26a0 referenced memory at 0x00000018. The memory could not be read.,Windows,VirtualBox 5.1.18,2017-03-28T10:21:12Z,2017-03-28T10:21:12Z,2017-03-28T10:21:12Z,"This happens when Guest VM window is minimized and I double-click it in VirtualBox Manager. Happens every time.

Logs not attached as they appear to be showing the VM running happily and nothing whatsoever is in there to indicate its gone down.",danf84
16615,No USB Device Access with NoMachine v5.2.11 Innstalled,Linux,VirtualBox 5.1.18,2017-03-28T06:23:41Z,2017-03-28T06:25:45Z,2017-03-28T06:25:45Z,"With the current version of NoMachine installed (v5.2.11) it is not possible to pass thorugh USB devices to VirtualBox.
The device lists in available devices, and when selected is removed from the Windows host. 
The VirtualBox status bar indicates that no device is captured and shows no read or write activity.
If you hover over the status of the device, this says the device is captured, but 'lsusb' in a Linux guest does not show the device, only the hub.
Attempting to capture the device results in an error 'E_INVALIDARG' and a message that the device is busy.
Removing the USB device and reinserting leads to multiple copies of the device appearing in the list.
To clear the list, VirtualBox has to be completely restarted.
This appears to be a clash between the USB device handing in NoMachine and VirtualBox.
I was trying to setup some VirtualBox VMs to test the current version of NoMachine.",Karl Foley
16608,Guest LPT error stops VM to start since VM versions 5.1.4 ... 5.1.18,Windows,VirtualBox 5.1.18,2017-03-25T13:34:44Z,2017-03-25T13:34:44Z,2017-03-25T13:34:44Z,"Host Win7Pro 64bit, guest Win XP Pro, on-motherboard LPT. Worked fine until v5.1.2. Starting from v5.1.4 ... v5.1.18 all versions crash during starting guest. LPT initialization error. If downgrading to v5.1.2 (with corresponding extensions)- works fine again.",Lager-Ju
16601,Windows 10 on Surface Book virtualbox install,Linux,VirtualBox 5.1.18,2017-03-24T01:13:41Z,2017-03-24T01:13:41Z,2017-03-24T01:13:41Z,"I have a brand new Microsoft surface pro book with windows 10.  I have the latest update.  I even uninstalled
the software, removed the files off the hard, removed from windows registery
then reinstalled virtualbox.  I downloaded the latest version of Kali Linux
and I get the same problem.  Windows crashes on me and restarts itself
saying it is writing the report.  I even reinstalled windows 10 and then
did a update, downloaded a fresh virtualbox, fresh kali Linux and the system
bombed out again.  Is there anyway we can fix this problem?",henrygh101
16589,Raw mode release assertion,Linux,VirtualBox 5.1.18,2017-03-21T11:05:16Z,2017-03-23T11:00:33Z,2017-03-23T11:00:33Z,"Ubuntu Linux 16.04 server as guest,
Windows 7 as host

Virtualbox version 5.1.18r114002

While updating the Linux kernel (using apt), the following error stopped the virtual machine:

{{{
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0xe555a9ac.

Click OK to terminate the program
Click CANCEL to debug the program
}}}


[[Image(https://i.imgur.com/K0duG4a.png)]]
[[Image(https://i.imgur.com/SRYeDD0.png)]]",Brianetta
16581,Scaled mode: documentation explains different,other,VirtualBox 5.1.18,2017-03-19T11:28:38Z,2017-03-19T11:28:38Z,2017-03-19T11:28:38Z,"Previously, the 'Keep Aspect Ratio' feature was present in scale mode but removed since r59335 due to Qt5 migration.[[BR]]
However, the documentation, in chapter 1.8.5 still explains:


'''The aspect ratio of the guest screen is preserved when resizing the window. To ignore the aspect ratio, press Shift during the resize operation.'''",ddixuike
15665,Mouse pointer graphic is messed up,Solaris,VirtualBox 5.1.2,2016-07-22T15:17:57Z,2021-09-01T17:43:27Z,2021-09-01T17:43:27Z,"Host: Windows 7 Enterprise 64 bit
Guest: Solaris 10

After installing 5.1.2, the graphic for the mouse pointer in my guest OS is messed up. It looks very bizarre. You can kind of see what the pointer should be, but it is heavily obscured by a bunch of dark ""noise"" that surrounds the pointer in a small rectangle. 

I think this only happened when Mouse Integration was enabled. 

Previous to the upgrade, I was using 5.0.16. I have now downgraded to 5.0.26, and the problem is no longer present. I can't imagine anyone who experiences this would consider it acceptable; I know that I won't be using any 5.1 versions unless this can be resolved. ",Gordon M
15845,e1000 Detected Tx Unit Hang,Linux,VirtualBox 5.1.2,2016-08-22T09:48:52Z,2020-12-17T12:22:56Z,2020-12-17T12:22:56Z,"Hi,

My Arch Linux desktop (client) is sometimes hanging, seems like the kernel module is detecting a disconnection:
{{{
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: new request (0 scripts)
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: completed: no scripts
aug 22 11:25:08 virtwin chromium.desktop[1507]: [1507:1530:0822/112508:ERROR:connection_factory_impl.cc(369)] Failed 
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.2914] device (enp0s3): link disconnected (deferring 
aug 22 11:25:38 virtwin kernel: e1000 0000:00:03.0 enp0s3: Reset adapter
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3570] device (enp0s3): link connected
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3571] device (enp0s3): DHCPv4 lease renewal requeste
aug 22 11:25:38 virtwin kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): canceled DHCP transaction, DHC
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): state changed bound -> done
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3760] dhcp4 (enp0s3): activation: beginning transact
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3783] dhcp4 (enp0s3): dhclient started with pid 4117
aug 22 11:25:38 virtwin dhclient[4117]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67
aug 22 11:25:41 virtwin kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                                  Tx Queue             <0>
                                  TDH                  <1>
                                  TDT                  <9>
                                  next_to_use          <9>
                                  next_to_clean        <2>
                                buffer_info[next_to_clean]
                                  time_stamp           <10012adce>
                                  next_to_watch        <2>
                                  jiffies              <10012b100>
                                  next_to_watch.status <0>
}}}
I must admit I do all my work in this virtual machine, but I can't recall to have seen disconnects in Windows (the host).

Guest OS: Arch Linux
Kernel: 4.7.1-1-ARCH",LordChaos
15752,Failed to open a session for the virtual machine,Linux,VirtualBox 5.1.2,2016-08-05T15:42:22Z,2019-01-19T21:31:44Z,2019-01-19T21:31:44Z,"Fresh install of Windows 10.
Fresh install of VB 5.1.2
Created a default Ubuntu x64 VM using Ubuntu 16.04 .iso
When I try to start the VM I get the following error:

''Failed to open a session for the virtual machine Xerus.

The virtual machine 'Xerus' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\brad\VirtualBox VMs\Xerus\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
''

I have created a default Win7 VM and get the same result when trying to start it.
",slattdog
15694,WinXP guest BSOD after start from saved state in 5.1.2,Windows,VirtualBox 5.1.2,2016-07-26T14:26:04Z,2018-02-18T14:49:56Z,2018-02-18T14:49:56Z,After I update from 5.0.26 to 5.1.2 my WinXP guest is BSODing just after start from saved state.,tico-tico
15774,VirtualBox incorrectly counts processors on AMD products,Linux,VirtualBox 5.1.2,2016-08-10T01:37:02Z,2017-09-24T05:21:17Z,2017-09-24T05:21:17Z,"VirtualBox incorrectly counts processors on AMD products.  I have an AMD CPU with 8 physical processors.  This processor has 8 full processor cores.  Evidently, VirtualBox assumes this processor is an Intel product with Hyper-Threading, but this assumption is not correct.
",Kriston
15751,"Windows VM host crashes randomly, when using Ubuntu 16.04 LTS and 3D is enabled",Linux,VirtualBox 5.1.2,2016-08-05T12:26:51Z,2017-01-06T01:54:24Z,2017-01-06T01:54:24Z,"I have an Ubuntu 16.04 freshly installed on my system.
Randomly, the VirtualBox host crashes with the following data:

""Virtualbox.exe - Application Error""

""The instruction at 0xd953b275 referenced memory at 0x00000088.  The memory could not be read"".

After a few reinstalls, and searching different settings I quickly figured-out, disabling the 3D acceleration was responsible.  Disabling it and the random crashes were completely gone.

Tried to downgrade to the lastest build of version 5.0, configuring sw + virtual machine with the right additions, but the exact same (random) error occurs.
Browsing several forums, 1 hint I tried were the graphics drivers.  I installed a few different revisions (Intel HD Graphics), now using version 10.18.14.4414  

But doesn't resolve the issue.

I checked the LOG files, as well the VBoxHardening.log file and when the crash occurs, the following 2 lines appear which i assume may be related ...

Since the Virtualbox host itself crashes, I clearly assume it should be some kind of bug when using the 3D enabled, which is in fact handy in Ubuntu desktop environments (drastically increases performance)...",Smoetje
15699,Issue with Windows Guest Digital License no longer valid,Windows,VirtualBox 5.1.2,2016-07-27T15:18:29Z,2016-11-28T11:30:14Z,2016-11-28T11:30:14Z,"When upgrading Virtual Box from V5.0 platform to V5.1, I have issue with the Digital license being invalid for Window 10 guests. Once the guest additions are installed I get a message that this copy of Windows is not active. When trying out the activation trouble shooter it prompts you to go to the Store to buy another copy.

I have tried both 5.1.0 and 5.1.2.  The Host OS is Windows 10 Pro 64 bit, while the two clients are Windows 10 Pro 32 bit preview versions.",WMurdockJr
15666,VirtualBox 5.1.0 and 5.1.2 fails to import digitally signed appliance (OVA file),Linux,VirtualBox 5.1.2,2016-07-22T19:20:52Z,2016-10-30T21:07:22Z,2016-10-30T21:07:22Z,"When attempting to import appliance from ova file, VBoxMAnage.exe fails with:


{{{
C:\Users\...\Downloads>""C:\Program Files\VirtualBox\VBoxManage.exe"" import <path to OVA file>
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Appliance read failed
VBoxManage.exe: error: Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ApplianceWrap, interface IAppliance
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleImportAppliance(struct HandlerArg *)"" at line 307 of file VBoxManageAppliance.cpp
}}}

Import from GUI ends with error dialog:

{{{
Failed to import appliance <path to OVA file>.

Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed).

Result Code: E_FAIL (0x80004005)
Component: ApplianceWrap
Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}
}}}

There is no relevant information in logs except:

{{{
00:40:08.764715 ApplRead ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={8398f026-4add-4474-5bc3-2f9f2140b23e} aComponent={ApplianceWrap} aText={Certificate path validation failed (VERR_CR_PKIX_SIGNATURE_MISMATCH, EVP_VerifyFinal failed)}, preserve=false aResultDetail=0
}}}


I have seen the same behavior on Windows 7 x64 and Windows 10 x64. On another Windows 7 appliance import finished with information popup stating that certificate cannot be verified. 

The same OVA file can be successfully imported using VirtualBox 5.0.X and software of other vendors. 

Content of ""*.mf"": 

{{{
SHA1(ERA_Appliance-disk1.vmdk)= 44f1d187daa9f6ed129381eec155ece99530bfee
}}}

and content of ""*.cert"":

{{{
SHA1(ERA_Appliance.mf)= 7334b00ada502ae4420c9c01ba5c6baf1809e0539a0ca74da780d00b38c89c8fedc6be81f8d8e2e4626a7e0d1e5c19dae2beaded0abde864584b4b1a8dc80294a42e92960ee40a0065a5dfb06a088b8435690475c14a828256b2137c433f868b0bb284c343e84c55c0bc609ea1269f773cbd24269e98b89a2d98332a0aad49d147f3246d47183ee9bf916a4a0b3a774afa49aa885953e1c4535199c86ac59579d07f02a34a68c466becf471cec3d3de7c46fc859740e3cb7dbc7cf8ece6afecbe2baa4072dbe8e7692e58e8a596f2a76499f7c886ab45281608c22e7e4be47da67800eba89627365febeb40bed86c01b3c1706fffc5685bda2d840c3f1c64169
-----BEGIN CERTIFICATE-----
MIIFTjCCBDagAwIBAgIQHeEN7VQdUec7xIb0kkmINjANBgkqhkiG9w0BAQUFADCB
tDELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL
ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykxMDEuMCwGA1UEAxMl
VmVyaVNpZ24gQ2xhc3MgMyBDb2RlIFNpZ25pbmcgMjAxMCBDQTAeFw0xNjA0MTkw
MDAwMDBaFw0xOTA3MTkyMzU5NTlaMIGvMQswCQYDVQQGEwJTSzERMA8GA1UECBMI
U2xvdmFraWExEzARBgNVBAcTCkJyYXRpc2xhdmExGzAZBgNVBAoUEkVTRVQsIHNw
b2wuIHMgci5vLjE+MDwGA1UECxQ1RGlnaXRhbCBJRCBDbGFzcyAzIC0gTWljcm9z
b2Z0IFNvZnR3YXJlIFZhbGlkYXRpb24gdjIxGzAZBgNVBAMUEkVTRVQsIHNwb2wu
IHMgci5vLjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKW9l/iFn1Y/
BJouXaVLHs6+TlhWgZztdjUWtyuF6FHJaHk8eaU3UbtZJuKzINeg+VLdVCk1O8RN
w2P1XRoDecxb5W2m7rX4sUrBHvYY62G6KDYHxzWYqfCLNkgC8R5gpkKtYHROwg4W
HP0h+OnRBv0ojYoP8q/lNma1pTcABOQVmYVm8Rg7/NaAmqAAquk0n03Y2+y5rfh2
G2FM3xlLzjBocephZeS30ZxkUhm12TnTf9P+0ZB7j0f8V7N9ecZy8NeUaTSWmjkW
czxbwjphePpK9A4xAaca5uoNrvQV4SarnAM1iVJb+zyA/qMRhR78giyfOVQjDGoX
Q2U0XovY/HECAwEAAaOCAV0wggFZMAkGA1UdEwQCMAAwDgYDVR0PAQH/BAQDAgeA
MCsGA1UdHwQkMCIwIKAeoByGGmh0dHA6Ly9zZi5zeW1jYi5jb20vc2YuY3JsMGEG
A1UdIARaMFgwVgYGZ4EMAQQBMEwwIwYIKwYBBQUHAgEWF2h0dHBzOi8vZC5zeW1j
Yi5jb20vY3BzMCUGCCsGAQUFBwICMBkMF2h0dHBzOi8vZC5zeW1jYi5jb20vcnBh
MBMGA1UdJQQMMAoGCCsGAQUFBwMDMFcGCCsGAQUFBwEBBEswSTAfBggrBgEFBQcw
AYYTaHR0cDovL3NmLnN5bWNkLmNvbTAmBggrBgEFBQcwAoYaaHR0cDovL3NmLnN5
bWNiLmNvbS9zZi5jcnQwHwYDVR0jBBgwFoAUz5mp6nsm9EvJjo/X8AUm7+PSp50w
HQYDVR0OBBYEFIKSJNBoZdrPFMTF6cPzFNk4c63aMA0GCSqGSIb3DQEBBQUAA4IB
AQDzz/hCjjc1kc15nqKjnFy/oiRPDhQpM+C5/bputO8q0AE0uUv17DcGuPQgbQsG
7gfDr4x2suxJfxasRBU2OKKWZfpUfuALqIC5oHviD/8UPU3gk8m+LiwgYr13i5sN
ujbBeUaa4WfzrQo+7+GvdfKPw/NpHnmrDSSRadM0AckpyhrLRqMkgVjvIz7t00Yd
AQoBhFvQTaOk/I8iIQqsQcK0qyVbdOJFnO7Wu16XNeSb0TxqFzXCsGoI0qDUCatm
1uDWPzIKL7omFDrKNxxGZhCoJAV4btgZE1Ys6NFWazUa43//lGl11f6pncXv7BQf
sIlwnYi5uqq1MvtD1mV57wWh
-----END CERTIFICATE-----
}}}",koso
15706,VBoxClient pidfile no copy paste on second running image.,Linux,VirtualBox 5.1.2,2016-07-28T08:34:27Z,2016-10-24T13:19:22Z,2016-10-24T13:19:22Z,"The VBoxClient process is making .vboxclient-*.pid files in the users home directory, to prevent from starting it more than ones. But if the users home dir is a nfs shared home dir to multiple virtualbox images the VBoxClient process will see .vboxclient-*.pid files in the users home dir and does not start the VBoxClient in the second virtualbox image. With the result that copy/past is not working on the second image. 

Solution: Don't make the pid files in the users home dir, but in /var/run or elsewhere on the local machine.



",Edwin
15754,Sound duplication in headless mode,Linux,VirtualBox 5.1.2,2016-08-05T18:36:13Z,2016-10-10T21:30:59Z,2016-10-10T21:30:59Z,"When I connect to guest VM which is started in headless mode the sound is played '''both''' on host and on client PCs.
Of course in '''mstsc''' connection option ""Play sound on this PC"" was set.
When I connect with the same connection settings to host PC itself all is fine.",Suncatcher
15696,"The memory could not be ""read""",Windows,VirtualBox 5.1.2,2016-07-27T08:44:06Z,2016-10-09T20:45:37Z,2016-10-09T20:45:37Z,"Hello,
With new 5.1.2 version, I've got this error:

{{{The instruction at ""0xcc47278e"" referenced memory at ""0x00000010"". The memory could not be ""read"".}}}

This occurs only with a specific software (Movicon 11.4) when I start his runtime. But the error is not report in guest side. This crash Guest and error is reported in host.
",DenisFR
15795,The instruction at 0xd756278e referenced memory at 0x00000010. The memory could not be read.,Windows,VirtualBox 5.1.2,2016-08-15T10:54:37Z,2016-10-07T14:32:02Z,2016-10-07T14:32:02Z,"This happened twice now with the exact same message.

I don't recognise having done anything particular - if anything, I was browsing in Windows Explorer to the Downloads folder, from the Tree View.

Guest: Windows 7 SP1 x86.
Host: Windows 7 SP1 x64.
",danf84
15689,Some time the guest crash,Windows,VirtualBox 5.1.2,2016-07-26T01:58:22Z,2016-09-28T21:14:07Z,2016-09-28T21:14:07Z,"Host: Windows 7 x64 professional SP1 with all other updates; 32 GB of RAM; processor Intel I7.

Guest: Windows 7 x64 Ultimate SP1.

Some time the guest crash with a messagebox (image attached).

I attach also VBox.log

",bmn
15744,Version 5.1.2 Machine Wrap Error,all,VirtualBox 5.1.2,2016-08-04T08:22:59Z,2016-08-17T11:09:08Z,2016-08-17T11:09:08Z,"I am currently using version 5.0.26, I have tried upgrading to version 5.1.2 but it never starts, I always get a ""Machine Wrap"" error.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
",Solrac42
15794,Can't install ReactOS,other,VirtualBox 5.1.2,2016-08-15T08:33:05Z,2016-08-15T08:33:05Z,2016-08-15T08:33:05Z,I try to install ReactOS 0.4.1 at VirtualBox 5.1.2 on Windows Thin PC SP1 without success. When I start machineI got error immediately.,luk3Z
15784,Video Mixing Renderer 9 (VMR) DirectShow graph building issue,Windows,VirtualBox 5.1.2,2016-08-12T12:34:03Z,2016-08-12T12:34:03Z,2016-08-12T12:34:03Z,"I've been experimenting with DirectShow video playback in Windows guests (XP, Vista, 7 and 8.1) using GraphStudioNext, and I stumbled on a issue that might be cause by the VirtualBox additions display driver. (The host PC is running Windows 10 x64 and has a Nvidia Geforce GTX 750 Ti graphics card).

If you start GraphStudioNext and drag a video on to it will by default create a graph with the VMR7 and hit play then it will play fine. If you remove the VMR7 filter and then go to Graph -> Insert Video Renderer, you can try out the various other video renderers.

All of these work fine (Video Renderer, VMR7, EVR) except VMR9, which fails to build the graph, reporting a cannot connect pins error. This error is not normal and doesn't occur on non-virtualized versions of Windows.",QuantumSquirrel
15709,mouse does not work anymore when newer VB starts a VM,Windows,VirtualBox 5.1.2,2016-07-29T06:45:17Z,2016-08-11T13:50:02Z,2016-08-11T13:50:02Z,"mouse is frozen when newer VirtualBox (5.024, 5,026, 5.1.2) starts a VM with 4.3.32 everything is fine.
I use a mircosoft touch mouse with.",xdk
15755,Windows 7 64bit Host - VirtualBox 5.1.2 r108956 The network operation failed,Linux,VirtualBox 5.1.2,2016-08-05T20:58:06Z,2016-08-10T07:31:53Z,2016-08-10T07:31:53Z,"Dear community,
VirtualBox 5.1.2 r108956 failed with Windows 7 64bit Host and Ubuntu as Guest.
As reported for other versions of VirtualBox, ""The network operation failed with the following error: During network request: Connection refused"". I followed all recommendations suggested for older versions of virtualbox but any of them fixed the problem.
Because the network is failing I do not have access to internet when I'm using ubuntu, and it is critical for accessing some of my documents/data.
Let me know if I need to report something else, and how I can report them.
Thanks,
Peris",Peris_D
15670,Shared folder is not mounted at VM start,Windows,VirtualBox 5.1.2,2016-07-23T09:22:10Z,2016-08-09T07:12:10Z,2016-08-09T07:12:10Z,"Under Windows 2000, shared folders are not automatically mounted at system start whereas it was the case with virtualbox 5.0.24. Manual mapping is required.",PBT78
15767,"Keyboard capture often escapes to host when using the ""Windows"" key (Windows host, Linux guest)",Linux,VirtualBox 5.1.2,2016-08-08T19:02:54Z,2016-08-08T19:02:54Z,2016-08-08T19:02:54Z,"I'm not quite sure when this started happening, but it happens to me a lot now (VBox 5.1.2).

My guest VM uses xmonad, and I set it so that using Win-1, Win-2, Win-3, switches desktops. Many times, when I am keyboard-captured, and I start switching desktops, one of them will suddenly escape and do stuff in my Windows host...

How to reproduce:
- Run a Linux guest, Windows host.
- Set it so that your keyboard is captured in the guest.
- Start mashing the Windows key with any other key, like 1, 2, 3, Left.

Effect:
- Within a few seconds of mashing, your host's Windows menu will pop-up.

I tested it with three different keyboards and two different machines.",Ptival
16678,Huge font size in VirtualBox GUI,all,VirtualBox 5.1.20,2017-04-21T06:41:31Z,2021-03-09T10:50:37Z,2021-03-09T10:50:37Z,"Host: Windows 10 x64 Build 1607 (""Anniversary Update"").

I installed VirtualBox without incident a few weeks ago and it worked fine (with multiple host system reboots, etc). I started VirtualBox today (5.1.18 from 2017-03-15 - so this was not after an upgrade) and the text in the UI is huge - though the application is still very readable.

I did an upgrade to 5.1.20 just now, and the issue persists.

Attached are some screenshots.

I do run a particular guest VM at 1024x768 with the window ""Scale factor"" set to 125% or 150% - and I note that a very similar issue described in #14151 seems related to the scale-factor setting: https://www.virtualbox.org/ticket/14151 - though I think he's talking about guest font size, not host font size.

I did ",daiplusplus
16710,Error while drag and dropping files,Windows,VirtualBox 5.1.20,2017-04-28T16:33:07Z,2018-08-28T09:22:18Z,2018-08-28T09:22:18Z,"In recent build but also in previous builds I very often came accross this error:

Drag and drop error from guest (VERR_FILE_NOT_FOUND).

Resultaatcode:
VBOX_E_IPRT_ERROR (0x80BB0005)
Component:
GuestWrap
Interface:
IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

drag and dropping files should work seamless without problems, just as in VMware player (concurrent). Why does it not work in Virtualbox. Please solve this mather in a next build.
",HookyPooky
16828,Unknown USB device detected,Linux,VirtualBox 5.1.20,2017-06-13T17:43:23Z,2017-06-14T16:14:45Z,2017-06-14T16:14:45Z,"There is a line in my VBoxSVC.log that says:
00:00:00.546001          USB: Unknown USB device detected (idVendor: 0x8087, idProduct: 0x07da). Please, report the idVendor and idProduct to virtualbox.org.

So, I am reporting it.",RayH
16699,"createHostOnlyNetworkInterface() returning iProgress, iProgress instead of iProgress,IHostNetworkInterface",all,VirtualBox 5.1.20,2017-04-26T11:16:31Z,2017-04-26T11:16:31Z,2017-04-26T11:16:31Z,"Hello everybody. I'm using Virtualbox 5.1.20 on Windows 10 x64. I'm using the python SDK (version 5.1.20) to bind irtualbox functions via XPCOM. Python version in use is the 2.7 32bit.

PROBLEM:
Function createHostOnlyNetworkInterface() returns iProgress twice instead of returning on iProgress and an IHostNetworkInterface.

Have a look at the attached screenshot, which is pretty eloquent.
",Alberto Geniola
16684,VBoxManage.exe extpack command exhausts StdOut buffer,other,VirtualBox 5.1.20,2017-04-21T22:04:06Z,2017-04-24T16:26:10Z,2017-04-24T16:26:10Z,"After having added a license agreement to the extension pack, automating has become quite the challenge. The problem is that the license message hits a 4K limit of the stdout/stderr buffer (which I actually didn't know existed until today).

Consider the following:

%comspec% /C ""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-5.1.20-114628.vbox-extpack 1> %temp%\1.txt 2> %temp%\2.txt

.. which should write the entire license agreement into the %temp%\1.txt file. That does not happen, as the output (and VBoxmanage.exe) halts when hitting a 4K limit. My guess is that the message is sent as one big chunck of data, instead of being flushed each line.

(At first I though that it was my VBS script having trouble, as WScript.Shell actually does a have 4K limit with StdOut / StdErr, but the limit seems to exist in the shell itself)

No .. using --accept-license=xyz.. to circumvent the issues isn't an option (at least I think), as Im automating installation for multiple customers. Please have a look at this strange behavior, and let me know what you think.",Schimkat
16691,UltraNav mice cannot scroll horizontally,Windows,VirtualBox 5.1.20,2017-04-24T15:05:15Z,2017-04-24T15:05:15Z,2017-04-24T15:05:15Z,"On my Lenovo W530 with UltraNav, horizontal scrolling does not work in Windows or Linux VMs (Win10 Host). Horizontal scrolling does work in every other app, including VBox Manager (within Show Log). Trying the different input device types in VM's settings did not resolve the issue. 

The previous solution of adding a few lines to tp4table.dat used to work (https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/tp01_en/thread-id/37809/page/2 and in fact I'm one of the people reporting there that the solution works), but is no longer the case. As a point of difference between the current and previous issue: scrolling in VBox Manager (within Show Log) used to not work unless the tp4table.dat solution was in place. However in the current issue scrolling does work within Show Log of VBox Manager, but horizontal scrolling does not work in Win7 or Linux Guests.

Furthermore, downgrading from 5.1.20 to version 5.0.38 r114632 did not resolve the issue.

Is there any additional information I can provide to request a fix for this?",R
16681,Virtual core XTEST pointer/keyboard inoperative under X11,Linux,VirtualBox 5.1.20,2017-04-21T10:08:53Z,2017-04-21T10:08:53Z,2017-04-21T10:08:53Z,"Guest: Arch Linux LTS 4.9.23-1 x64; also happens on Arch Linux 4.10.10-1
Host: Windows 10 Pro x64, Intel Core i7

Started happening after an update to VirtualBox 5.1.20. Downgrading on guest side to 5.1.18 had no effect. Unrelated to window manager, happened using X11 default as wel.

Found a workaround by adding two configuration files to /etc/X11/xorg.conf.d/ first to define keyboard to use evdev drivers and mouse to use libinput drivers.",gingerale
16819,Mouse Pointer Issue - Constant left click,Windows,VirtualBox 5.1.22,2017-06-07T14:22:52Z,2022-04-16T03:23:16Z,2022-04-16T03:23:16Z,"After running Virtualbox 5.1 for a period of time (time varies) the mouse pointer will end up in a constant left click.  If I hover over anything it will try to open/click. If I open the start menu the first thing hovered over is what gets opened. Restarting the VM will temporarily fix the issue however it consistently recurs. I did not see the problem pre version 5.1.

Host: Windows 7 64bit pro
Guest:Windows 7 64bit pro",surreal_life
16795,"TRIM on SSD not stable with Linux, Windows 10, FreeBSD",all,VirtualBox 5.1.22,2017-05-28T06:59:33Z,2021-08-24T16:07:04Z,2021-08-24T16:07:04Z,"Linux TRIM timeouts sometimes, FreeBSD same, Windows 10 doesn't boot at all

See below and attachments for details:[[BR]]

Linux Fedora 25 latest updates
1. Attach an image:
{{{
VBoxManage storageattach ""Fedora 25"" --storagectl ""SATA"" --port 0 --device 0 --nonrotational on --discard on --medium ""Fedora 25.vdi"" --type hdd
}}}
2. check trim enabled
{{{
hdparm -I /dev/sda | grep TRIM
           *    Data Set Management TRIM supported (limit unknown)
}}}
3. Enable it in the mount options and reboot afterwards
{{{
/dev/mapper/fedora-root /                       ext4    defaults,discard        1 1
}}}
4. run fstrim /
Hangs sometimes with timeouts


FreeBSD 11 latest updates
1. Attach disk as under Linnux
2. Check for TRIM support
{{{
camcontrol identify /dev/ada0 | grep -i trim
Data Set Management (DSM/TRIM) yes
}}}
3. Enable TRIM support on filesystem
{{{
mount | grep -i ufs
/dev/ada0p2 on / (ufs, local, journaled soft-updates)

# Boot into single user mode
tunefs -t enable /dev/ada0p2
tunefs: issue TRIM to the disk set

bash -c 'tunefs -p /dev/ada0p2 2>&1 | grep -i trim'
tunefs: trim: (-t)                                         enabled
}}}",linuxguru
16844,DRIVER_POWER_STATE_FAILURE VirtualBox 5.1.22,other,VirtualBox 5.1.22,2017-06-19T01:54:53Z,2021-05-01T14:19:17Z,2021-05-01T14:19:17Z,"I started receiving a lot of BSODS on my PC after windows clean install. All of them were related to DRIVER_POWER_STATE_FAILURE while PC going to sleep.

I realised then it's connected to VB because it happened only after I used VB. I checked it, started PC, started VB, finished VB, tries to restart PC ==> bsod. I googled for VB + DRIVER_POWER_STATE_FAILURE BSOD and found out that it's quite a common issue.

I attach my dump files. I thinks it can be connected either with asus usb drivers or rapid mode by samsung (but I have another PC with samsung and VB and there are no issued there).

My host is windows 10 pro x64, my guests are windows 7 x86\64, windows 10 pro x86\64.

I would appreciate any help.",toouur
16808,Removed network adapters are still showing in bridged networking,all,VirtualBox 5.1.22,2017-06-03T05:48:24Z,2021-01-13T16:15:05Z,2021-01-13T16:15:05Z,"When I run ""vboxmanage list bridgedifs"", I get a list of adapter that still contains adapters that are not in the system anymore. In my case, I used to have VLANs adapters that were created using the Intel ANS utility. The VLAN were since removed but are still showing in VirtualBox bridged networking. This is annoying.

In the log below, all adapters having a HardwareAddress of 00:00:00:00:00:00 are not in the system anymore but are still listed in all VirtualBox bridged networking list.

I tried removing and reinstalling VB, removing and reinstalling the NDIS6 Bridged Network Driver, nothing works, the old adapters are still showing up in the list. The Windows registry does not contain any references to the GUID of the removed adapters anymore. Why is VB still 

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage list bridgedifs
Name:            Intel(R) Ethernet I210-T1 GbE NIC
GUID:            da04ab21-b3e6-4bad-b6ad-497cfcd15188
DHCP:            Enabled
IPAddress:       192.168.4.170
NetworkMask:     255.255.255.3
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: a0:36:9f:cd:99:ad
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet
GUID:            42ffbcdd-fad9-4a1e-bc7f-de92582df835
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ
GUID:            dbc6c4c8-8e06-4b50-a0ba-b82766724257
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion
GUID:            d59e7f43-fc7f-4830-902a-74881b6354db
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
GUID:            146679e9-63c0-439f-a968-1545520a0e34
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 00:00:00:00:00:00
MediumType:      Ethernet
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
}}}

",viaujoc
16801,Running a Virtual Machine when Windows Hyper-V is enabled should NOT Crash Windows,all,VirtualBox 5.1.22,2017-05-31T03:26:52Z,2020-06-04T16:28:57Z,2020-06-04T16:28:57Z,"VirtualBox can not run on Windows 10 when Hyper-V mode is ACTIVE (ON).  However the existing behaviour is pathological and must be corrected.  

Running a VM when Hyper-V is ON causes the BSOD!



Conditions:

 1. Windows boots with Hyper-V enabled
 2. Start-up VirtualBox Manager GUI
 3. START an existing VM

Outcome:

 1. VM begins to load
 2. The dread Windows BSOD (Blue Screen of Death) appears
 3. Windows dies -- generates crash log, etc.
 4. Windows reboots
 5. NOTE: Hyper-V is still active and must be deactivated manually.


Resolution Sought:

 1. Check for Hyper-V mode is: OFF, at start-up for all VirtualBox tools; especially:
     * VirtualBox Manager GUI and 
     * VM shell  itself

 2. Issue a WARNING pop-up or error message for command line
    Reporting that Hyper-V mode is active and VirtualBox cannot
    run while there is another hypervisor active.  Or some such.

 3. Exit the VirtualMachine (shell) once the Hyper-V Active 
    status is reported.  
      * Thus Avoiding the BSOD


Optional / suggestion:

 * It would be useful for the warning to tell users how to 
   disable/enable Hyper-V as part of the warning message(s).

 * Another helpful feature is for the VirtualBox management 
   GUI to turn Hyper-V off or on from a menu.


Related / supplementary notes:

There seem to be several issues that mention Hyper-V troubles.  Some are real bugs and some look like misunderstandings.

In my opinion no software should cause a system crash-dump when it can be prevented by checking some system configuration attributes.

See also:

 * https://www.virtualbox.org/ticket/16675
 * https://www.virtualbox.org/ticket/15780


",Will
16830,VM Manager does not remember its restored window size,other,VirtualBox 5.1.22,2017-06-15T05:01:10Z,2018-12-07T05:30:57Z,2018-12-07T05:30:57Z,"If the window of VM Manager has been maximized and then restored, VM Manager does not remember its restored window size between restarts.
VirtualBox.xml stores the bounds of maximized window instead of the restored window in ExtraDataItem ""GUI/LastWindowPosition"".",robpats
16818,VirtualBox Drag and drop failure on Windowd 10,Linux,VirtualBox 5.1.22,2017-06-06T20:09:30Z,2018-10-24T09:02:15Z,2018-10-24T09:02:15Z,"VirtualBox Drag and drop failes on Windowd 10 with the following error:

Drag and drop operation from host to guest failed.
Drag and drop error from host (VERR_PATH_NOT_FOUND).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

",Sciex
16753,Pen_Tablet.exe takes more and more memory when VM is on.,Linux,VirtualBox 5.1.22,2017-05-12T17:25:50Z,2018-09-06T19:28:55Z,2018-09-06T19:28:55Z,"Tablet is Wacom CTL-470.[[BR]]
Driver version 5.3.5-3 (newest for this tablet).[[BR]]
Memory leak occurs on host while VM is running and tablet is connected. Process name is Pen_Tablet.exe (Tablet service for consumer driver). The process gains around 20K memory every second.[[BR]]
Host is running Windows 10 build 15063.250 (Creators update).[[BR]]
Guest is Arch Linux.[[BR]]

",snow
17499,"Can't start vmachine, MachineWrap E_FAIL (0x80004005)",Windows,VirtualBox 5.1.22,2018-01-25T13:27:28Z,2018-01-26T10:28:13Z,2018-01-26T10:28:13Z,"Hello there.

I don't know why, but i can't even start v-box machine. It gives me this error:


{{{
The virtual machine 'TESTING' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Admin\VirtualBox VMs\TESTING\Logs\VBoxHardening.log'.

Návratový kód: E_FAIL (0x80004005)
Komponenta: MachineWrap
Rozhraní: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

Log output:

{{{
41c.1af0: Log file opened: 5.1.22r115126 g_hStartupLog=000000000000006c g_uNtVerCombined=0xa03fab00
41c.1af0: \SystemRoot\System32\ntdll.dll:
41c.1af0:     CreationTime:    2018-01-05T15:56:46.395451500Z
41c.1af0:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
41c.1af0:     ChangeTime:      2018-01-06T08:02:19.865353700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1dd100
41c.1af0:     NT Headers:      0xe0
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x6dead514
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1e0000 (1966080)
41c.1af0:     Resource Dir:    0x174000 LB 0x6a1d8
41c.1af0:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.192
41c.1af0:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
41c.1af0:     FileDescription: NT Layer DLL
41c.1af0: \SystemRoot\System32\kernel32.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:04.954227600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.735385400Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0xab868
41c.1af0:     NT Headers:      0xe8
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xc2cf900
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0xae000 (712704)
41c.1af0:     Resource Dir:    0xac000 LB 0x520
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\KernelBase.dll:
41c.1af0:     CreationTime:    2017-09-29T13:41:43.124345500Z
41c.1af0:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
41c.1af0:     ChangeTime:      2018-01-01T19:07:46.829134900Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x266000
41c.1af0:     NT Headers:      0xf0
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0x4736733c
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x266000 (2514944)
41c.1af0:     Resource Dir:    0x245000 LB 0x548
41c.1af0:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: Windows NT BASE API Client DLL
41c.1af0: \SystemRoot\System32\apisetschema.dll:
41c.1af0:     CreationTime:    2017-09-29T13:42:07.095026600Z
41c.1af0:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
41c.1af0:     ChangeTime:      2018-01-08T20:50:10.598880700Z
41c.1af0:     FileAttributes:  0x20
41c.1af0:     Size:            0x1b398
41c.1af0:     NT Headers:      0xc8
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Machine:         0x8664 - amd64
41c.1af0:     Timestamp:       0xf30abf31
41c.1af0:     Image Version:   10.0
41c.1af0:     SizeOfImage:     0x1c000 (114688)
41c.1af0:     Resource Dir:    0x1b000 LB 0x408
41c.1af0:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
41c.1af0:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
41c.1af0:     ProductName:     Microsoft® Windows® Operating System
41c.1af0:     ProductVersion:  10.0.16299.15
41c.1af0:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
41c.1af0:     FileDescription: ApiSet Schema DLL
41c.1af0: supR3HardenedWinFindAdversaries: 0x0
41c.1af0: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: Calling main()
41c.1af0: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
41c.1af0: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
41c.1af0: SUPR3HardenedMain: Respawn #1
41c.1af0: System32:  \Device\HarddiskVolume1\Windows\System32
41c.1af0: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
41c.1af0: KnownDllPath: C:\WINDOWS\System32
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
41c.1af0: supR3HardNtEnableThreadCreation:
41c.1af0: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardenedWinDoReSpawn(1): New child 2d54.35dc [kernel32].
41c.1af0: supR3HardNtChildGatherData: PebBaseAddress=000000000116e000 cbPeb=0x388
41c.1af0: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
41c.1af0: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
41c.1af0: supR3HardenedWinSetupChildInit: Start child.
41c.1af0: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
41c.1af0: supR3HardNtChildPurify: Startup delay kludge #1/0: 263 ms, 16 sleeps
41c.1af0: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
41c.1af0:  *0000000000000000-0000000000e5ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000e60000-0000000000e7ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000e80000-0000000000e98fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000e99000-0000000000e9ffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000ea0000-0000000000f9afff 0x0000/0x0004 0x0020000
41c.1af0:   0000000000f9b000-0000000000f9dfff 0x0104/0x0004 0x0020000
41c.1af0:   0000000000f9e000-0000000000f9ffff 0x0004/0x0004 0x0020000
41c.1af0:  *0000000000fa0000-0000000000fa3fff 0x0002/0x0002 0x0040000
41c.1af0:   0000000000fa4000-0000000000faffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000000fb0000-0000000000fb0fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000000fb1000-0000000000ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *0000000001000000-000000000116dfff 0x0000/0x0004 0x0020000
41c.1af0:   000000000116e000-0000000001170fff 0x0004/0x0004 0x0020000
41c.1af0:   0000000001171000-00000000011fffff 0x0000/0x0004 0x0020000
41c.1af0:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
41c.1af0:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
41c.1af0:   000000007fff0000-00007ff7ed97ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7ed980000-00007ff7ed9a2fff 0x0002/0x0002 0x0040000
41c.1af0:   00007ff7ed9a3000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
41c.1af0:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
41c.1af0:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
41c.1af0:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
41c.1af0: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
41c.1af0: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
41c.1af0: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
41c.1af0: supR3HardNtChildPurify: Done after 417 ms and 0 fixes (loop #0).
2d54.35dc: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2d54.35dc: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
41c.1af0: supR3HardNtEnableThreadCreation:
2d54.35dc: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2d54.35dc: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: System32:  \Device\HarddiskVolume1\Windows\System32
2d54.35dc: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2d54.35dc: KnownDllPath: C:\WINDOWS\System32
2d54.35dc: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2d54.35dc: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2d54.35dc: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2d54.35dc: Registered Dll notification callback with NTDLL.
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2d54.35dc: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2d54.35dc: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
41c.1af0: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2d54.35dc: \SystemRoot\System32\ntdll.dll:
2d54.35dc:     CreationTime:    2018-01-05T15:56:46.395451500Z
2d54.35dc:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2d54.35dc:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1dd100
2d54.35dc:     NT Headers:      0xe0
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x6dead514
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1e0000 (1966080)
2d54.35dc:     Resource Dir:    0x174000 LB 0x6a1d8
2d54.35dc:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.192
2d54.35dc:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: NT Layer DLL
2d54.35dc: \SystemRoot\System32\kernel32.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:04.954227600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0xab868
2d54.35dc:     NT Headers:      0xe8
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xc2cf900
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0xae000 (712704)
2d54.35dc:     Resource Dir:    0xac000 LB 0x520
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\KernelBase.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:41:43.124345500Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2d54.35dc:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x266000
2d54.35dc:     NT Headers:      0xf0
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0x4736733c
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x266000 (2514944)
2d54.35dc:     Resource Dir:    0x245000 LB 0x548
2d54.35dc:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: Windows NT BASE API Client DLL
2d54.35dc: \SystemRoot\System32\apisetschema.dll:
2d54.35dc:     CreationTime:    2017-09-29T13:42:07.095026600Z
2d54.35dc:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2d54.35dc:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2d54.35dc:     FileAttributes:  0x20
2d54.35dc:     Size:            0x1b398
2d54.35dc:     NT Headers:      0xc8
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Machine:         0x8664 - amd64
2d54.35dc:     Timestamp:       0xf30abf31
2d54.35dc:     Image Version:   10.0
2d54.35dc:     SizeOfImage:     0x1c000 (114688)
2d54.35dc:     Resource Dir:    0x1b000 LB 0x408
2d54.35dc:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2d54.35dc:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2d54.35dc:     ProductName:     Microsoft® Windows® Operating System
2d54.35dc:     ProductVersion:  10.0.16299.15
2d54.35dc:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2d54.35dc:     FileDescription: ApiSet Schema DLL
2d54.35dc: supR3HardenedWinFindAdversaries: 0x0
2d54.35dc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: Calling main()
2d54.35dc: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2d54.35dc: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2d54.35dc: SUPR3HardenedMain: Respawn #2
2d54.35dc: supR3HardNtEnableThreadCreation:
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ntdll.dll)
2d54.35dc: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2d54.35dc: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff956000000 'C:\WINDOWS\System32\ntdll.dll'
2d54.35dc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardenedWinDoReSpawn(2): New child 2fb0.1318 [kernel32].
2d54.35dc: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
2d54.35dc: supR3HardNtChildGatherData: PebBaseAddress=00000000010b9000 cbPeb=0x388
2d54.35dc: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ff956000000 uNtDllChildAddr=00007ff956000000
2d54.35dc: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ff9560791d0
2d54.35dc: supR3HardenedWinSetupChildInit: Start child.
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 1 ms.
2d54.35dc: supR3HardNtChildPurify: Startup delay kludge #1/0: 257 ms, 15 sleeps
2d54.35dc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2d54.35dc:  *0000000000000000-0000000000e8ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000e90000-0000000000eaffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000eb0000-0000000000ec8fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000ec9000-0000000000ecffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000ed0000-0000000000fcafff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000000fcb000-0000000000fcdfff 0x0104/0x0004 0x0020000
2d54.35dc:   0000000000fce000-0000000000fcffff 0x0004/0x0004 0x0020000
2d54.35dc:  *0000000000fd0000-0000000000fd3fff 0x0002/0x0002 0x0040000
2d54.35dc:   0000000000fd4000-0000000000fdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000000fe0000-0000000000fe0fff 0x0004/0x0004 0x0020000
2d54.35dc:   0000000000fe1000-0000000000ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *0000000001000000-00000000010b8fff 0x0000/0x0004 0x0020000
2d54.35dc:   00000000010b9000-00000000010bbfff 0x0004/0x0004 0x0020000
2d54.35dc:   00000000010bc000-00000000011fffff 0x0000/0x0004 0x0020000
2d54.35dc:   0000000001200000-000000007ffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2d54.35dc:  *000000007ffe1000-000000007ffeffff 0x0000/0x0002 0x0020000
2d54.35dc:   000000007fff0000-00007ff7edc0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edc10000-00007ff7edc32fff 0x0002/0x0002 0x0040000
2d54.35dc:   00007ff7edc33000-00007ff7edf0ffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff7edf10000-00007ff7edf10fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf11000-00007ff7edf80fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf81000-00007ff7edf81fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edf82000-00007ff7edfc6fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc7000-00007ff7edfc7fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc8000-00007ff7edfc8fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfc9000-00007ff7edfcdfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfce000-00007ff7edfcefff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfcf000-00007ff7edfcffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd0000-00007ff7edfd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7edfd4000-00007ff7ee01bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2d54.35dc:   00007ff7ee01c000-00007ff955ffffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ff956000000-00007ff956000fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956001000-00007ff956112fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956113000-00007ff956158fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956159000-00007ff956160fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956161000-00007ff95616efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff95616f000-00007ff95616ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956170000-00007ff956172fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff956173000-00007ff9561dffff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume1\Windows\System32\ntdll.dll
2d54.35dc:   00007ff9561e0000-00007ffffffdffff 0x0001/0x0000 0x0000000
2d54.35dc:  *00007ffffffe0000-00007ffffffeffff 0x0001/0x0002 0x0020000
2d54.35dc: VirtualBox.exe: timestamp 0x5903619d (rc=VINF_SUCCESS)
2d54.35dc: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2d54.35dc: '\Device\HarddiskVolume1\Windows\System32\ntdll.dll' has no imports
2d54.35dc: supR3HardNtChildPurify: Done after 463 ms and 0 fixes (loop #0).
2fb0.1318: Log file opened: 5.1.22r115126 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03fab00
2fb0.1318: supR3HardenedVmProcessInit: uNtDllAddr=00007ff956000000 g_uNtVerCombined=0xa03fab00
2fb0.1318: ntdll.dll: timestamp 0x6dead514 (rc=VINF_SUCCESS)
2fb0.1318: New simple heap: #1 0000000001300000 LB 0x400000 (for 1966080 allocation)
2d54.35dc: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2d54.35dc: supR3HardNtEnableThreadCreation:
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: System32:  \Device\HarddiskVolume1\Windows\System32
2fb0.1318: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
2fb0.1318: KnownDllPath: C:\WINDOWS\System32
2fb0.1318: supR3HardenedVmProcessInit: Opening vboxdrv...
2fb0.1318: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
2fb0.1318: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
2fb0.1318: Registered Dll notification callback with NTDLL.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\kernel32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\kernel32.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952740000 LB 0x00266000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\KernelBase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\KernelBase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9556d0000 LB 0x000ae000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff9556d0000 'C:\WINDOWS\System32\KERNEL32.DLL'
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff7edf10000 LB 0x0010c000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe [fFlags=0x0]
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe
2fb0.1318: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ff9560791d0 pvNtTerminateThread=00007ff9560a08c0
2d54.35dc: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 452 ms.
2fb0.1318: \SystemRoot\System32\ntdll.dll:
2fb0.1318:     CreationTime:    2018-01-05T15:56:46.395451500Z
2fb0.1318:     LastWriteTime:   2018-01-01T12:48:26.082566200Z
2fb0.1318:     ChangeTime:      2018-01-06T08:02:19.865353700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1dd100
2fb0.1318:     NT Headers:      0xe0
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x6dead514
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1e0000 (1966080)
2fb0.1318:     Resource Dir:    0x174000 LB 0x6a1d8
2fb0.1318:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.192
2fb0.1318:     FileVersion:     10.0.16299.192 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: NT Layer DLL
2fb0.1318: \SystemRoot\System32\kernel32.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:04.954227600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:04.954227600Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.735385400Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0xab868
2fb0.1318:     NT Headers:      0xe8
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xc2cf900
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0xae000 (712704)
2fb0.1318:     Resource Dir:    0xac000 LB 0x520
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0xac0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\KernelBase.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:41:43.124345500Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:41:43.124345500Z
2fb0.1318:     ChangeTime:      2018-01-01T19:07:46.829134900Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x266000
2fb0.1318:     NT Headers:      0xf0
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0x4736733c
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x266000 (2514944)
2fb0.1318:     Resource Dir:    0x245000 LB 0x548
2fb0.1318:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x2450b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: Windows NT BASE API Client DLL
2fb0.1318: \SystemRoot\System32\apisetschema.dll:
2fb0.1318:     CreationTime:    2017-09-29T13:42:07.095026600Z
2fb0.1318:     LastWriteTime:   2017-09-29T13:42:07.095026600Z
2fb0.1318:     ChangeTime:      2018-01-08T20:50:10.598880700Z
2fb0.1318:     FileAttributes:  0x20
2fb0.1318:     Size:            0x1b398
2fb0.1318:     NT Headers:      0xc8
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Machine:         0x8664 - amd64
2fb0.1318:     Timestamp:       0xf30abf31
2fb0.1318:     Image Version:   10.0
2fb0.1318:     SizeOfImage:     0x1c000 (114688)
2fb0.1318:     Resource Dir:    0x1b000 LB 0x408
2fb0.1318:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2fb0.1318:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2fb0.1318:     ProductName:     Microsoft® Windows® Operating System
2fb0.1318:     ProductVersion:  10.0.16299.15
2fb0.1318:     FileVersion:     10.0.16299.15 (WinBuild.160101.0800)
2fb0.1318:     FileDescription: ApiSet Schema DLL
2fb0.1318: supR3HardenedWinFindAdversaries: 0x0
2fb0.1318: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: Calling main()
2fb0.1318: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
2fb0.1318: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64'
2fb0.1318: '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe' has no imports
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe)
2fb0.1318: SUPR3HardenedMain: Final process, opening VBoxDrv...
2fb0.1318: supR3HardenedEarlyCompact: Removed heap 1 (0x00000001300000 LB 0x400000)
2fb0.1318: supR3HardNtEnableThreadCreation:
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff94e950000 LB 0x00005000 C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff94e950000 'C:\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxSupLib.DLL'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msasn1.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'crypt32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\wintrust.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\wintrust.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume1\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #33 'msasn1.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\crypt32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\crypt32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msasn1.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msasn1.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\msvcrt.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\msvcrt.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msasn1.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msasn1.dll' -> '\Device\HarddiskVolume1\Windows\System32\msasn1.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9557b0000 LB 0x0009d000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951c10000 LB 0x00012000 C:\WINDOWS\System32\MSASN1.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff951ed0000 LB 0x000f6000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ucrtbase.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ucrtbase.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9529b0000 LB 0x001ce000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952eb0000 LB 0x0011f000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff954e70000 LB 0x0005b000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\sechost.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\sechost.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff953340000 LB 0x000a1000 C:\WINDOWS\System32\advapi32.dll [fFlags=0x0]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'sechost.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #27 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\advapi32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\advapi32.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff952c20000 LB 0x00058000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-fibers-l1-1-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-synch-l1-2-0'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952740000 'api-ms-win-core-localization-l1-2-1'
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\WINDOWS\system32\Wintrust.dll'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> -626 (\Device\HarddiskVolume1\Windows\System32\bcrypt.dll)
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll: Grown load config (244 to 256 bytes) includes non-zero bytes: 00 00 00 00 60 a9 01 80 01 00 00 00
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\system32\bcrypt.dll' (C:\WINDOWS\system32\bcrypt.dll): rcNt=0xc0000190
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\bcrypt.dll'
2fb0.1318: Warning! Failed to load bcrypt.dll
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'sechost.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'sechost.dll' -> '\Device\HarddiskVolume1\Windows\System32\sechost.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\sechost.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume1\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume1\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\WINTRUST.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff952c20000 'C:\Windows\System32\WINTRUST.DLL'
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\cryptsp.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\cryptsp.dll
2fb0.1318: supR3HardenedDllNotificationCallback: load   00007ff9515d0000 LB 0x00017000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
2fb0.1318: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\rsaenh.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\rsaenh.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume1\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/Imports: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status -626 (0xfffffd8e)) on \Device\HarddiskVolume1\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
2fb0.1318: Error (rc=0):
2fb0.1318: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -626 (0xfffffd8e) fImage=1 fProtect=0x10 fAccess=0xf cHits=2 \Device\HarddiskVolume1\Windows\System32\bcrypt.dll
2fb0.1318: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\system32\rsaenh.dll'
2fb0.1318: supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x8 (<NULL>) on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: Error -22919 in VirtualBox! (enmWhat=1)
2fb0.1318: WinVerifyTrust failed on stub executable: WinVerifyTrust failed with hrc=Unknown Status 0x8 on '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.exe'
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'vboxrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'qt5printsupportvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'qt5openglvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #14 'oleaut32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #15 'winmm.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VirtualBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmm.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmm.dll' -> '\Device\HarddiskVolume1\Windows\System32\winmm.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'msvcrt.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\winmm.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\winmm.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume1\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'combase.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #23 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\oleaut32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\oleaut32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'ole32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'ole32.dll' -> '\Device\HarddiskVolume1\Windows\System32\ole32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #22 'rpcrt4.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #46 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #47 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #48 'combase.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\ole32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\ole32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'shell32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'shell32.dll' -> '\Device\HarddiskVolume1\Windows\System32\shell32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #73 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #75 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\shell32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\shell32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'advapi32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'advapi32.dll' -> '\Device\HarddiskVolume1\Windows\System32\advapi32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume1\Windows\System32\advapi32.dll [lacks WinVerifyTrust]
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'user32.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'user32.dll' -> '\Device\HarddiskVolume1\Windows\System32\user32.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'win32u.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #34 'gdi32.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Windows\System32\user32.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Windows\System32\user32.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5openglvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5openglvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5openglvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5OpenGLVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5printsupportvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5printsupportvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5printsupportvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5widgetsvbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'winspool.drv'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'comdlg32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5PrintSupportVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5widgetsvbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5widgetsvbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5widgetsvbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'qt5guivbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5WidgetsVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5guivbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5guivbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5guivbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'opengl32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'gdi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'qt5corevbox.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5GuiVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'qt5corevbox.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'qt5corevbox.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\qt5corevbox.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'user32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #2 'shell32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ole32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'advapi32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #6 'mpr.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\Qt5CoreVBox.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcr100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcr100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcr100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp100.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp100.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\msvcp100.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'vboxrt.dll'...
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: 'vboxrt.dll' -> '\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\vboxrt.dll' [rcNtRedir=0xc0150008]
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcr100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'msvcp100.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #3 'ws2_32.dll'.
2fb0.1318: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #4 'rpcrt4.dll'.
2fb0.1318: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll)
2fb0.1318: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Users\Admin\Downloads\Portable VBox\Portable-VirtualBox\app64\VBoxRT.dll
2fb0.1318: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'opengl32.dll'...
2f",Toby (:
16878,VERR_SUP_VP_EXE_VS_PROC_NAME_MISMATCH error on Windows 10,Linux,VirtualBox 5.1.22,2017-07-06T02:31:12Z,2018-01-04T11:44:53Z,2018-01-04T11:44:53Z,"Hello

I keep getting the above mentioned error when I start a guest. I remove and reinstall VirtualBox and the error goes away, but after a few days it comes back again (usually after a restart of my PC). I am attaching the screen shot of error box and VBoxHardening log. A shorter error message is below:


{{{
Failed to open a session for the virtual machine Ubuntu-16.04.

The virtual machine 'Ubuntu-16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\arshad.khan\VirtualBox VMs\Ubuntu-16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}


Any help is greatly appreciated.

Thanks
Arshad",arshad01
17387,USB Dongle not recognized correctly,Linux,VirtualBox 5.1.22,2017-12-21T13:56:46Z,2017-12-21T13:56:46Z,2017-12-21T13:56:46Z,"Host: Windows 10 Pro x64
Client: Ubuntu 16 LTS
VirtualBox: 5.1.22r115126 with ExtensionPack

Synopsis:
An USB-Dongle (Dinkey Pro Lite Mini) is plugged in and gets not recognized correctly from the VirtualBox.
I have to disable/enable this ""Human Interface Dongle / USB Input Device"" from the device manager (or replug it) once after starting the VB. This is an issue only with the Windows 10 OS.
The same setup (dongle, VB) on Windows 7 is working perfectly.

Attacments:
logs.zip: Logs from Machine => Show Log...
usbhost1.log: usb host list after virtual box start
usbhost2.log: usb host list disable/enable the specified USB Input Device
01.jpg: Screenshot after virtual box start
02.jpg: Screenshot disable/enable the specified USB Input Device

The correctly attached device name is ""OEM HID Dongle [0106]"". If the Dongle is recognized correctly as OEM HID Dongle the serial number is attached correctly.
",igm
16771,Qubes install ISO fails to run,Linux,VirtualBox 5.1.22,2017-05-19T14:02:06Z,2017-12-18T22:58:20Z,2017-12-18T22:58:20Z,Am attempting to run install Qubes OS from ISO [https://www.qubes-os.org/downloads/] on 64 bit host using 64 bit Virtualbox and 64 bit VM environment. Was able successfully install Qubes on 1 of 3 different hosts: Dell Latitude E5420. Failed on Surface Pro 4. Also failed in Lenovo Think Center.,mutsuura
17370,Unknown USB device detected,Linux,VirtualBox 5.1.22,2017-12-14T10:57:05Z,2017-12-14T21:27:57Z,2017-12-14T21:27:57Z,"00:00:00.054173 USB: Unknown USB device detected (idVendor: 0x096e, idProduct: 0x0007). Please, report the idVendor and idProduct to virtualbox.org.

It's enough for ""report""?",igm
16886,4.x -> 5.x crash,Windows,VirtualBox 5.1.22,2017-07-07T22:32:30Z,2017-11-15T21:27:54Z,2017-11-15T21:27:54Z,"I updated my virtual box from 4.* to 5.*, now my virtual PCs crash when I start them from any snapshot.

P.S. Can't get log from VM.",Mikha Mikhin
16880,USBPROXY Getting USB descriptor failed with error 31,Windows,VirtualBox 5.1.22,2017-07-06T16:30:28Z,2017-11-06T04:07:05Z,2017-11-06T04:07:05Z,"I cannot use the USB extension pack anymore. It was working fine a few weeks ago but now I get this error whenever I try to add a USB device (from the host) to the guest machine:

USBPROXY Getting USB descriptor failed with error 31

The USB device disappears from the host but dooes not appear on the guest. I tried to downgrade to older versions of VirtualBox but it does not work.

The USB devices are working fine on the host.

Both host and guest run Windows 10 X64 Creator Update.",M.
16850,No Connection to Mobile Phone with MTP via USB,Linux,VirtualBox 5.1.22,2017-06-21T17:09:56Z,2017-10-20T07:30:48Z,2017-10-20T07:30:48Z,"
== My configuration: ==

My Host-OS is Windows 8.1 and my VirtualBox is V5.1.22r115126 including its extension pack and installed USB-controller.
  

== The problem: ==

While my Samsung Galaxy Note 4 (SM-N910F) with Android 6.0.1 perfectly connects through USB with MTP to any native installed Mint or Ubuntu Linux OS, it does not connect to any Mint or Ubuntu if it runs virtual under VB. The file browser of the guest system shows the mobile phone but doesn't show any files. It further appears to hang. All other USB devices work well.

The phone is automatically detected as follows:
Name:         SAMSUNG_Android[0400]
Manufacturer: 04e8
Product ID:   6860
Revision no:  0400
Manufacturer: SAMSUNG
Product:      SAMSUNG_Android
Serial No.:   55xxxx7b
Port:         
Remote:       No
 
Special observation:
Two virtual Guest-OS (both MINT) were running. After I tried to connect my mobile phone without success to one Guest-OS, I shut the Guest-OS down and suddenly found that the phone was connected to the remaining Guest-OS as MTP-device and showed all directories and files as it should be and everything worked fine.


== Conclusion: ==

VB has a bug in handling USB MTP devices or certain USB MTP devices (like my Samsung Galaxy Note 4).

I would be grateful if you could provide a solution or if you book and confirm this as a VB bug.

Didi

  
",Didi
16901,Non-driver certificates not handled correctly by hardening (OpenText SOCKS),Linux,VirtualBox 5.1.22,2017-07-14T10:03:31Z,2017-09-15T13:22:10Z,2017-09-15T13:22:10Z,"I had originally raised an issue with OpenText socks that theri DLL was not signed and so did not work with VirtualBox. They have now provided a signed version, but it is not signed with a driver certificate. According to OpenText support VirtualBox is not handling the signing check correctly. Some of my correspondance with OpenText support pasted below.

----------------------------------------------------------------------------
---- From OpenText Support -----

Hello Lars,

In regards to ticket #3056978, I received input from Engineering.  This issue appears to be related to the third party application.

According to Engineering: 
If you used signtool, it would show DLL is properly signed.  Note, using the default option, will show a trust error because the default assumes driver signing and this is a not a driver with signed catalog file.  You need to use /pa argument for the signing to show as valid.  Since you use SigCheck (Sysinternals), you do not need to use any parameters to show the DLL is signed

C:\Users\xx>sigcheck64 ""c:\Program Files\Open Text\SOCKS Client\*"" > C:\xx\sigcheck_socks.14.0.16.txt

(Refer to the output in the attached file.)
 

The root issue is that Virtualbox process will have HumSOCKS.dll injected into its process space (this is simply how SOCKS works on Windows).  On startup it does a complicated self-validation on itself and all loaded DLLs in the main process space.  Essentially the rules force that all DLLs need to be signed properly (or a couple of other exceptions for specific location and owner of file).  It appears that their code fails the same way that signtool does without the /pa flag and ultimately will not start up when we are in their process space because of that.  In one sense this is correct behavior because there's no signed catalog file for us at all but it's definitely unwanted because it should not apply that logic for 3rd party dlls that are not drivers.

This appears to be a long standing issue with VirtualBox - check out https://www.virtualbox.org/ticket/13659.  The corrupted path it starts out as is not a problem for us but the exact same issue with failed trust for a correctly signed DLL is the main issue left.

Regards,
OpenText Support



---- From me to OpenText Support ---
To: support@opentext.com
Subject: Re: FW: OTCS Ticket 3056978 Socks 14:  VirtualBox does not work when SocksClient is installed

Hi, I have tried your recommendation of importing the certificate. I also tried disabling the virus scanner. I also tried importing the intermediate certificate and tried loosening some policy settings, but nothing solves the problem. SHA-256 certificates show up fine in Windows and the patch required for support is installed.   The error I'm getting in the VBoxHardening.log is:

{{{
14a4.1a9c: supHardenedWinVerifyImageByHandle: -> -23021 (\Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll) WinVerifyTrust
14a4.1a9c: Error (rc=0):
14a4.1a9c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll: None of the 1 path(s) have a trust anchor.: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll 
14a4.1a9c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume1\Program Files\Open Text\SOCKS Client\HumSOCKS.dll
14a4.1a9c: Error (rc=0): 
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll' (C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll): rcNt=0xc0000190
14a4.1a9c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll'
}}}",Lars Hupfeldt
16903,Windows 10 crashes on VirtualBox session startup,Linux,VirtualBox 5.1.22,2017-07-14T21:03:03Z,2017-08-17T15:27:49Z,2017-08-17T15:27:49Z,"VirtualBox: 5.1.22
Host: Windows 10
Guest: Kali

Windows 10 crashes when starting Kali - the blue screen shows error IRQL_UNEXPECTED_VALUE.

",caveman14
16900,Guest Additions Will Not Install,Windows,VirtualBox 5.1.22,2017-07-13T15:43:38Z,2017-08-17T15:14:00Z,2017-08-17T15:14:00Z,"Host: Windows 10 (64-bit)
Guest: Windows Server 2012 (64-bit)

Guest Additions will not install on the guest. When trying to install it, I get an error that it cannot execute ""VBoxDrvInst.exe"". I tried everything and nothing fixes it.

I have attached the log file for VM and also 2 screenshots of the error.

Thank you in advance for helping. I really need guest additions.


",pjkim
16981,Inaccessible Virtual Machines,Windows,VirtualBox 5.1.22,2017-08-04T20:12:21Z,2017-08-05T04:05:58Z,2017-08-05T04:05:58Z,"Hi, I have VirtualBox 5.1.22r115126 installed in my C drive. 
I set the Default Machine folder as: X:\Portable Installations\VirtualBox Saved Files. I store my VMs in my X Drive so that I don't lose my VMs when restoring a C drive backup with Macrium Reflect.

I recently restored a Macrium Reflect C Drive backup. Everything was fine and all my VMs were working. These are my VMs:

""Windows 7 64-bit New Install (Nothing Changed)"". As the name suggests this has Windows installed with nothing else on it.
""Windows 7 64-bit - Opera Portable"". This is a linked clone of the above which I then have Opera Portable on.

I had the linked clone running today and I saved a snapshot. I closed VirtualBox and restarted my PC. When I opened VirtualBox, both VMs are ""inaccessible"". It says a differencing image of snapshot ""snapshot name here"" could not be found. Could not find an open hard disk with UUID ""name here"".

How can I find out what caused the problem and how can I fix it?
Is there any reason why I can't have VMs on my X Drive but VirtualBox installed on the C Drive?
",DaveyMames
16893,Windows XP guests hang/freeze during and after setup with choppy audio,Windows,VirtualBox 5.1.22,2017-07-09T21:14:26Z,2017-07-28T06:17:40Z,2017-07-28T06:17:40Z,"The Windows XP guest stops responding and hangs for while and then continues to work normally. After a little time it freezes/hangs again and the cycle continues. The mouse won't move whenever Windows XP freezes. This cycle starts of hangs start during the part of setup that occurs after entering the product key and while getting the dialog for network settings. Additionally, I get cycles of extremely choppy audio that almost sounds like a chainsaw during the ""welcome to microsoft windows"" screen. I haven't experienced any of this behavior with Windows Server 2003 guests so far which is weird given that the two OSes are similar.",Eddy Smith
16906,Unable to start Virtual Machine (exit code 0x01),Windows,VirtualBox 5.1.22,2017-07-17T11:36:00Z,2017-07-25T21:57:34Z,2017-07-25T21:57:34Z,"Dear Virtual Box support,

i have a critical problem on my Windows 10 machine (64bit), without any previous advice all the Virtual Machines installed are unable to start. 
I started and used VM succesfully one day and after restarting my toshiba notebook PC i had this problem.


Here is the error reported when starting a Virtual Machine:

------

Apertura di una sessione per la Macchina Virtuale Win 7 (64-bit) non riuscita.

The virtual machine 'Win 7 (64-bit)' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Virtual Box VM\Win 7 (64-bit)\Logs\VBoxHardening.log'.

Codice 'uscita: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaccia: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

----

The log of the startup are attached to this message .

Please give me some feedback about this issue.

I used VB for many years and this is first time i encouter souch a big problem.

Best regards,
Massimo Cavagni",MC77
16897,NtCreateFile failed: Unknown Status -626,Linux,VirtualBox 5.1.22,2017-07-12T11:53:11Z,2017-07-24T10:01:14Z,2017-07-24T10:01:14Z,"Windows 10 Version 1703 Build 15063.413[[BR]]
Virtual Box Version 5.1.22r115126(Qt5.6.2)

The virtual machine 'AHF' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ~\Logs\VBoxHardening.log'.

{{{
Result Code: E_FAIL (0x80004005)
Component:   MachineWrap
Interface:   IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}",TheChris
16925,virtio-net slower than Intel PRO/1000 Desktop,Linux,VirtualBox 5.1.22,2017-07-20T15:07:13Z,2017-07-24T09:32:36Z,2017-07-24T09:32:36Z,"Confirmed on version 5.1.24.

Host: Windows 10[[BR]]
VM: Debian 9 with Guest Additions

Host-only NIC with Intel PRO/1000 Desktop
 * iperf3 
  * Host => VM : 2.68 Gbps
  * Host <= VM : 1.20 Gbps

Host-only NIC with virtio-net
 * iperf3
  * Host => VM : 2.11 Gbps
  * Host <= VM : 0.96 Gbps",cantonese
16905,Shared folders hangs by configuration,Windows,VirtualBox 5.1.22,2017-07-16T19:14:14Z,2017-07-19T22:32:44Z,2017-07-19T22:32:44Z,"I have windows 10 host with windows 10 guest and when I try to configure the shared folders it hangs always and I have to kill the process.
It is the same where I configure it, in the VM manager (guest turned off) after choosing the folder on the host it hangs, in the virtual machine menu as soon as I try to configure a shared folder it hangs and I can't choose any folder on the host.
I was checking the log file of both (VM manager and virtual machine) but there is exactly nothing. I saw other similar tickets about shared folders hanging, but not really my problem, in my case it freezes during the configuration of the shared folder, and moreover the other tickets have been resolved.",spamme1
16907,"Vbox additions 5.1.22 in CentOS 6 cause display adapter to be ""unknown""",Linux,VirtualBox 5.1.22,2017-07-17T15:29:31Z,2017-07-18T06:02:11Z,2017-07-18T06:02:11Z,"I've just upgraded vbox from 5.0.30 to 5.1.22. One of my guests runs CentOS (6.3). 

After updating the vbox additions in this guest, the first symptom I noticed is that screen resize stopped working (was not reflected in the X server in the guest). I then noticed that the display is recognized as ""unknown"" (not ""vbox""), and all options in ""View -> Virtual Screen 1"" were greyed out. 
All in all, it looked as if the graphics driver piece of the vboxadditions is misbehaving or missing, even though the install went smoothly.

I have downgraded the vbox additions in this guest to 5.0.30 - left the host at 5.1.22 - and lo and behold, everything seems to work fine.

I tried a couple of back-and-forth installs of 5.1.22/5.0.30, and it is 100% reproducible.",doron
16902,P2P connections die quickly under certain circumstances,Windows,VirtualBox 5.1.22,2017-07-14T16:55:53Z,2017-07-15T09:03:45Z,2017-07-15T09:03:45Z,"Conditions to replicate are rather unusual so please cope with me:
- an application using P2P connectivity is let to operate for a few minutes (5 minutes should be more than enough);
- you may close the P2P application when you want to get to the next step. Wherever you close the P2P application and its active connections won't make a difference;
- pause the VM execution for a few minutes (5 minutes should be more than enough);
- when resuming VM try to repeat the first step and witness the connection failure.
TCP connections seam unaffected.
I only tested NAT network.

I reproduced this with [http://www.sopcast.com Sopcast] which is a P2P application.
- Install the latest version (4.2.0) in a Windows VM;
- Visit [http:///www.cooltvi.com cooltvi.com] in Internet Explorer and select a channel;
- Allow the ActiveX to run - this would start the live broadcast which is P2P based. 
Sopcast requires Direct3D9 for video to render. But this is not required to reproduce this issue, it can very well be reproduced with black screen.

I could reproduce with Windows xp/posready 2009, 7, 8.1 and 10 guests.
I tested with AMD PCNET Fast III, Intel PRO 1000 T-Server and MT Desktop, Paravirtualized Network.

I'll post logs if necessary. 
  
 
 
",pal1000
16895,"Host BSOD when starting any VM on Windows 10 host, without Hyper-V",all,VirtualBox 5.1.22,2017-07-10T16:52:16Z,2017-07-10T16:52:16Z,2017-07-10T16:52:16Z,"I have a largely-clean Windows 10 system with VirtualBox installed. When I attempt to start any VM (including a Centos 7.0 box, and a basic DOS VM), Windows 10 BSODs with `SYSTEM_SERVICE_EXCEPTION`, Bug Check Code `0x0000003b`.

I found multiple references to this being a conflict with Windows 10's own Hyper-V Virtualisation, so I have disabled the Hyper-V services and removed the feature from Windows; the BSOD still happens. I have also updated host graphics and audio drivers (just in case). I have tested VirtualBox versions 5.1.22 (last stable), preview 5.1.23, and 5.0.40 (which is known-good in my department).

Attached are the VBox.log, VBoxHardening.log for both the DOS and Centos systems, and a representative minidump. Analysis of the minidump on Superuser.com (https://superuser.com/a/1228520/82337) suggests that VMMR0.r0 has attempted to execute a Privileged Instruction.

I'm not sure if any further diagnostics would be helpful here, but please ask and I will attempt to get them for you.",Chowlett
16864,VBox 5.1.22 Does Not Start VM after Upgrade from Win7 to Win10,Linux,VirtualBox 5.1.22,2017-06-29T22:42:33Z,2017-07-06T14:39:40Z,2017-07-06T14:39:40Z,"VM's created with Manager 5.1.22 r115126 were working in Win7.
Upgraded to Win10 Enterprise, ver 1703, build 15063.0.
VMs will not start.
VMs are Ubuntu Xenial 16.04.
Tried running the repair VM Manager from the VBox installer.  Did not work.

On VM ""Start"", I get 2 popups.  
The 1st popup refers to running a cmd 'sc.exe', the results of which are posted.
The 2nd popup refers to a file that I pasted below.
I could not find a button to attach the file.

COMMAND - SC.EXE
{{{
sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.
}}}",jkAB
16875,VBox 5.1.22 on intel i3 samsung laptiop virtualbox fails to start,Windows,VirtualBox 5.1.22,2017-07-05T16:41:16Z,2017-07-06T14:24:46Z,2017-07-06T14:24:46Z,(pasted log file removed),Robert Fernando
16877,BSoD CLOCK_WATCHDOG_TIMEOUT,Linux,VirtualBox 5.1.22,2017-07-05T17:30:24Z,2017-07-05T17:30:24Z,2017-07-05T17:30:24Z,"Machine Log: https://pastebin.com/raw/zYqqUp1T
Host OS: Windows 10
There is a dmp file from the bluescreen wich shows VBoxDrv.sys
I'm using Homestead (laravel) with vagrant. Maybe that helps.
Hopefully this is not a duplicate

This bsod just happens randomly when doing something in host system
DMP file can be loaded here: http://www49.zippyshare.com/v/1pxcsU2X/file.html
as to big for the attachmnent page.",keving
16867,Windows Aero on Windows Vista & Windows 7 won't working,Windows,VirtualBox 5.1.22,2017-07-02T04:41:09Z,2017-07-02T04:41:09Z,2017-07-02T04:41:09Z,I cannot running Windows Aero on Windows Vista and Windows 7 (except Windows 8.x and Windows 10) on latest version of VirtualBox. Please make changes on display driver to support Windows Aero like a Windows 8+ display driver.,Hanif Shaquille
16861,Safenet Sentinel Driver,Windows,VirtualBox 5.1.22,2017-06-28T08:02:59Z,2017-06-28T08:31:04Z,2017-06-28T08:31:04Z,"Hi,
I am using Safenet Sentinel Drivers (security dongles).
Since Virtual Box V5.0 the driver is no longer usable on my Windows Virtual Box machines (W7 64 bits).
So I used to stay on V4.3.40 version.
Unfortunately, last W10 update forced me to upgrade my Virtual Box version cause V4.3.40 does not work anymore.
Could you make Safenet Sentinel Drivers work again please?
Thanks a lot.
Regards,",Zikbull
16833,Installation of 5.x Prevents Host Machine Networking,other,VirtualBox 5.1.22,2017-06-16T05:34:38Z,2017-06-22T15:47:40Z,2017-06-22T15:47:40Z,"I've used Virtual box for years, once it moved to 5.x I have not been able to use it due to the summary subject.   The physical machine is an i7 with Win7 x64 all the latest updates.  Contains VirtualPC, VMWare Player and VirtualBox.  The 4.3.40 works fine.  The last time I installed 5.1.22, it uninstalled 4.3.40, installed 5.1.22.  Everything worked fine for a couple days (the computer was left running or sleep mode).   On the reboot, the same thing happens, no networking on the host system, no connecting to domain controller, etc..  If you go to the control panel / network and sharing, it just has a circle hourglass going in circles and says ""Identifying..."" for the Connection: Local Area Connection and Access was ""No Network Access"".  So I went to adapter settings, right clicked on the ""VirtualBox Host-Only Network"" and clicked disable.  As soon as that was disabled, the local area network connected and everything was working again.  This is repeatable, last attempt was back in 2016.  Still a problem today.",dfatvb
16849,"virtualbox gust os crashes and disapear when host os ""Display driver stopped responding and has recovered"" error in ...",Windows,VirtualBox 5.1.22,2017-06-20T15:27:23Z,2017-06-20T16:22:39Z,2017-06-20T16:22:39Z,"virtualbox gust os crashes and disapear
when host os ""Display driver stopped responding and has recovered"" error in ...

When the guest os crash occurs:
Power saving function, when the host OS returns from display off.
",0o0o
16832,When running any machine in VirtualBox 5.1.22 Windows bluescreens,all,VirtualBox 5.1.22,2017-06-15T12:41:35Z,2017-06-20T08:54:26Z,2017-06-20T08:54:26Z,When I try and run a machine on VirtualBox Windows bluescreens and shuts down. I'm running Windows 10 Enterprise version 1703 build 15063.413.,Allan Kjær
16842,Remember last view in VM settings,all,VirtualBox 5.1.22,2017-06-18T15:35:15Z,2017-06-18T16:51:44Z,2017-06-18T16:51:44Z,"I currently try different live ISO images. To change the image, in the VM settings I have to select the page ""mass storage"" and the port every time. It would be very nice to have the settings dialog open with the same view as it was when the settings were saved (in this case page ""mass storage"" and the optical drive port).

Of course, other times the requirements could be different, so for different pages the opened tab (for example, page ""network"", tab ""adapter 2"") should also be saved.",bm1n
16789,VM dropped from network because of DHCP problems,Windows,VirtualBox 5.1.22,2017-05-26T20:42:05Z,2017-06-13T15:41:09Z,2017-06-13T15:41:09Z,"I have a VM in the NAT mode. It happened only once last month, but suddenly guest network lost its internet connection. So the card and network was here, but it has this standard 169 IP address and because of this no access to internet. Only the shutdown and start of the guest helped here. As one can see from the log, it looks like VM suddenly got some problems with DHCP in my local network, where my router is a DHCP server, and lost his 10.x.x.x address. Therefore, it got an 169.x.x.x address. Both guest and host are latest Windows 10.",boxer01
16822,Default Machine Folder link removed,all,VirtualBox 5.1.22,2017-06-08T16:40:50Z,2017-06-08T16:40:50Z,2017-06-08T16:40:50Z,"hello


I encountered an unexpected behavior during VM creation/removal through the VirtualBox Manager GUI - done some testing and found the manager sometimes remove the Default Machine Folder configured in File / Preferences / General

''1st case'' - there is no existing VM in the GUI - create a new VM then abort during creation (I usually abort at the memory setting) => the VM folder is gone as is the Default Machine Folder - it's ok, cleaning is always a good idea as there is no existing or created VM in the folder, but I think this is linked with my problem below : the 2nd case

''2nd case'' - the Default Machine Folder is a junction (folder hard link in Windows world) - in that case, even if there is other existing and possibly running VM, removing one VM results in the removed VM folder removal (expected) and Default Machine Folder link removal (unexpected) - no harm as only the link is removed, the true folder and all VM folders inside are still there, its only annoying as I need to recreate the link each time a VM is removed or VM creation is aborted


'''how to reproduce the problem'''[[BR]]
1) create a junction : in command line ""mklink /j C:\Users\(your-username)\Documents\VM D:\{test-folder}""[[BR]]
2) set the Default Machine Folder to C:\Users\(your-username)\Documents\VM[[BR]]
3) create VM test-1[[BR]]
4) check C:\Users\(your-username)\Documents\VM\test-1 exists as well as D:\{test-folder}\test-1[[BR]]
5) start creating VM test-2[[BR]]
6) abort test-2 VM creation => C:\Users\(your-username)\Documents\VM link should be gone


my current configuration involve iSCSI disks mounted as folders, reason for the links - hope I made the reproduce steps as simple and straight as possible

feel free to ask if you need more tests or information


regards[[BR]]
Bruno",!bruno
16821,Virtual Box won't load existing or new VMs,all,VirtualBox 5.1.22,2017-06-08T13:52:02Z,2017-06-08T14:00:52Z,2017-06-08T14:00:52Z,"Hi,

For the last week I've been having an issue where Virtualbox is refusing to load VMs and gives an error whilst creating the process.

It was working perfectly fine and suddenly this problem has started appearing.

Please check attached documents.

I'm running a W7x64 Host.",jdoe3618
16807,Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).,Linux,VirtualBox 5.1.22,2017-06-02T20:37:24Z,2017-06-02T21:07:58Z,2017-06-02T21:07:58Z,"1) Context
Virtual Version : v5.1.22
Host : Windows 10
Guest : Debian v8.7

2) Problem description : 
An error message appears when starting my Guest.

3) Error Message :
Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).
Code d'erreur : 
E_FAIL (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

4) Usefull infos :
I suspect that the problem was appeared when I have updated VirtualBox from v5.1.10 to v5.1.22
The host only network adapter was #2 and now as you can see in screen shots
this is the #3. So I suspect there a ""binding"" problem between #2 (old version of VBox) and #3 (new version of Vbox)
Is there new network devices between v5.1.10 and v5.1.22 ?
Is the default network device for my Host was changed ?

Best Regards",ManWithNoName
16793,Guest machine freeze when network is active,Windows,VirtualBox 5.1.22,2017-05-27T16:37:58Z,2017-05-29T19:26:12Z,2017-05-29T19:26:12Z,"I have a version of VirtualBox 4.3.38 installed on my Debian, runs, and I keep this version !
Why ?
I installed a version 5.3.1 on a Windows Seven machine, version strongly discouraged!
I will join the logs because the guest machine freeze!
Especially when I add the network card from menu Configuration-> NAT network or bridge,
then systematically blocks the FREEZE guest machine!
I keep version 4.3.38.
I join the log!
I have AVG and spyHunter installed on the Windows machine.
I TRY DISABLED SERVICE SPYHUNTER AND AVG THEN FREEZE ALWAYS

J'ai une version de VirtualBox 4.3.38 installé sur ma Debian , fonctionne , et je garde cette version
pourquoi ?
J'ai installé sur une machine Windows Seven la version 5.3.1 , version vivement déconseiller !
Je vous joint les logs car la machine guest freeze !
Surtout quand je rajoute la carte réseau depuis menu Configuration->Reseau NAT ou pont à pount, 
ca freeze  systématiquement , la machine guest FREEZE !
Je garde la version 4.3.38.
Je joint les log !
Product not tested.",Sizy458
16792,Internal network no connectiion between VM's on Windows10 host,Windows,VirtualBox 5.1.22,2017-05-27T15:08:23Z,2017-05-27T19:14:33Z,2017-05-27T19:14:33Z,"I'made 2 VM's both with an WS2012R2.
Connect the network both on Intern netwerk with the name intnet
Switched from both the firewall off.

Adresses

SERVER A
IP adress 10.0.0.10
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

SERVER B
IP adress 10.0.0.12
Subnet mask 255.255.255.0
Default gateway 10.0.0.1

DNS blank

Can ping the machine itself correctly

Problem is 
On the command line prompt using the ping command it gives unreachble 4 time's on both sides.",Fanatic11
16776,use of USB Audio device in guest trap the host on exiting VM,other,VirtualBox 5.1.22,2017-05-21T17:05:21Z,2017-05-21T17:05:21Z,2017-05-21T17:05:21Z,"Host: Windows 7, 32-bit
Guest: OS/2

When I use an USB Audio device (I have not tested any other isochronous
device) in the guest and if I subsequently end the VM,
a trap will happen inside VirtualBox, see attached screenshot.
Ejecting the USB Audio device in the guest before exiting the VM makes
no difference.
Using the very same USB Driver stack under an native OS/2 Installation
does not exhibit any trap.",lerdmann
16758,winxp,other,VirtualBox 5.1.22,2017-05-15T10:17:11Z,2017-05-15T10:29:38Z,2017-05-15T10:29:38Z,Problem run VB,keriks
16738,Cannot Switch Virtualization Off,Linux,VirtualBox 5.1.22,2017-05-08T05:58:12Z,2017-05-08T05:58:12Z,2017-05-08T05:58:12Z,"If a VM has virtualization switched on, but the BIOS of the physical machine has virtualization switched off, it is impossible to switch virtualization off for the VM.  This is because Virtual Box detects the missing virtualization and grays out the ""Acceleration"" tab under the System Settings.  With this tab missing, it is not possible to deselect hardware virtualization.  Further, Virtual Box does not cascade this detection to actually forcing virtualization off for the VM on execution.  This causes the VM to crash as it starts up (because the virtualization is physically not available).  My suggestion is to always allow the acceleration tab to be accessible.  Alternatively, if virtualization is physically not available, just run the VM with the option deselected, even if it is selected under the acceleration tab (in which case, the acceleration tab can remain grayed out if virtualization is off)",Tim Ellis
16722,Crash on changing optical drive assignment,Linux,VirtualBox 5.1.22,2017-05-03T09:40:19Z,2017-05-03T11:22:00Z,2017-05-03T11:22:00Z,"Hi,
right from clean install of 5.1.22, when I prepared initial config of Debian64 VM, I went to properties, wanted to delete IDE controller (optical disk) and use opt drive under existing SATA there, it crashed - and always crashes.",peterg91
16939,"""Text Select"" mouse cursor corrupted when mouse integration is enabled",Windows,VirtualBox 5.1.24,2017-07-24T19:51:34Z,2020-05-12T16:10:16Z,2020-05-12T16:10:16Z,"Host:  Windows 10

Guest:  Windows 7

When mouse integration is disabled, [[http://i.imgur.com/WbeIunC.jpg|it looks normal]]

When mouse integration is enabled, [[http://i.imgur.com/SwNYZfy.jpg|it looks messed-up]]

",dfiugh
18393,USB3 drive not recognized when connected to USB3 port,Linux,VirtualBox 5.1.24,2019-01-30T18:09:24Z,2019-01-30T18:12:30Z,2019-01-30T18:12:30Z,"I have a Windows7 host w/ Debian8 guest on VirtualBox 5.2.8.  WD Elements 2TB disk (https://smile.amazon.com/gp/product/B00D0L5BH8/) and Thinkpad E560 laptop (https://smile.amazon.com/Lenovo-ThinkPad-20EV002JUS-15-6-Inch-Processor/)

The disk connected into any usb3 port on the laptop.  It is recognized and works fine under the Windows host.  Once I connect the disk to the virtualbox guest, windows correctly stops seeing it and the guest shows:

{{{
[ 1786.262759] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 1786.486278] usb 1-2: device descriptor read/64, error 18
[ 1786.775519] usb 1-2: device descriptor read/64, error 18
[ 1787.063049] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[ 1787.247705] usb 1-2: device descriptor read/64, error 18
[ 1787.535498] usb 1-2: device descriptor read/64, error 18
[ 1787.818462] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 1787.835491] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.018588] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[ 1788.035487] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.036814] usb usb1-port2: unable to enumerate USB device
}}}

''virtualbox list usbhost'' when the device '''is not''' connected to the virtualbox guest:
{{{
UUID:               91f87b8b-5c6c-4318-b582-48e82af85f67
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/Super
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0008
Current State:      Busy
}}}

.. and ''virtualbox list usbhost'' when the device '''is''' connected to the virtualbox guest:
{{{
UUID:               d4973955-0c60-418e-bd19-29d060869977
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/High
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0009
Current State:      Unavailable
}}}

the device does not show up in /dev/sd* at all and ''lsusb'' does not show the device

the guest is configured for USB3 in virtualbox settings and the guest does have the usb3 drivers loaded.

when I use a USB2 extension cable between the disk and the laptop, the device works in the virtualbox guest.


see for discussion: https://forums.virtualbox.org/viewtopic.php?f=6&t=82474",jkister
16936,Snapshot Deletion of Encrypted VM always corrupts filesystem,Linux,VirtualBox 5.1.24,2017-07-22T16:27:41Z,2019-01-24T20:23:59Z,2019-01-24T20:23:59Z,"Given this setup:

* Windows 10 Pro Host
* VitrualBox 5.1.22/24
* Ubuntu 16.04 Guest
* VBox Additions Installed
* Guest is encrypted.
* VBox Web Service is running

I wrote a java tool that uses the web service and does the typical thing in creating a VM backup.  This includes taking a snapshot prior to copying the VDI(s) to an archive and then once completed, deletes the snapshot.  This occurs while the VM is running (or off as well).  The duration of the VM running on the snapshot is probably on the order of 20-30 minutes.

I have several VMs I use day to day. 1 is encrypted and the other 1 isn't.  Invariably the deletion of the snapshot on the encrypted VM results in a corrupt and non-bootable system even though the merge back into the parent is 100% successful.  This does not happen on the non-encrypted VM.

As an additional validation of the issue, I removed the encryption from the encrypted VM and I do the same thing with my java tool.  No problems at all and the VM is fine.  I put the encryption back on the VM and get the same original corruption problem.

In addition I run the tool with the encrypted VM off, and I don't see the problem.  All works as expected.

I've run this over 10 times and the same thing happens every time.  My running + encrypted VM always corrupts the filesystem when the Snapshot deletion/merge occurs.

I read another Bug report on the VirtualBox support site that states the same thing (from a few versions back I believe).

Thanks and let me know what else you need.

",declay
16948,Blank Screen (crash?) on update V5.1.22 -> V5.1.24,Windows,VirtualBox 5.1.24,2017-07-26T17:45:25Z,2017-08-03T15:47:01Z,2017-08-03T15:47:01Z,"A few minutes after I updated to V5.1.24 my computer screen suddenly went black.   Ctrl-Alt-Delete did not bring up the Windows 10 blue options screen.  I couldn't get it to respond in any way.  Maybe crashed but without seeing anything I couldn't verify that.  Had to power off.   Tried again and same thing happened within about 10 min.  Had to roll back to V5.1.22.

In the change log I noticed ""GUI: prevent stopped screen updates or black screen on reboot in a multi-screen setup under certain conditions""

FYI: I do have two video cards in this computer.  One on the mother board (not used) and a NVIDIA NVS 315

",isgdre
16946,Windows 7 Home Premium with VirtualBox 5.1.24 64-bit VMs not offered,all,VirtualBox 5.1.24,2017-07-26T13:07:16Z,2017-07-28T12:48:36Z,2017-07-28T12:48:36Z,"Problem:
- When I click New in VirtualBox, no matter which Type I select, there are no 64-bit choices listed in the Version, only 32-bit choices.

This is what I have:
- ASUS laptop
- Windows 7 Home Premium, 64-bit

This is what I did:
- Upgraded to VirtualBox 5.1.24.
- Ran this successfully in an elevated cmd window:
    bcdedit /set hypervisorlaunchtype off
- Enabled VT-d in my BIOS.  I do not see any setting named Virtualization.

Priority is 'blocker', because I cannot install Windows Server 2016.",clairestreb
16950,crashis when adding virtual device to sata controller,all,VirtualBox 5.1.24,2017-07-27T09:32:16Z,2017-07-27T09:32:16Z,2017-07-27T09:32:16Z,"in mashin settings window i opens the storage tab and right click on the controller's item on the list of the devices and select add harddisk or dvd in context menu
next the VirtualBox Manager crashis.",ilyapashuk
17093,Serial I/O troubles between Guest and Host,all,VirtualBox 5.1.26,2017-09-18T08:53:46Z,2023-01-30T04:57:12Z,2023-01-30T04:57:12Z,"I've only personally seen this in a Windows 10 Pro (64-bit) host environment. But some others I've been in touch with seem to have this with other configurations too.

Scenario:

Host running Windows 10 Pro (64-bit) on computer with no physical COM ports (Lenovo T470p laptop). Guest can be ""anything"", but I've tested with FreeDOS, Ubuntu Linux 16/17, and Windows XP. Using NetSerial (http://pcmicro.com/netserial/) to emulate a COM port. NetSerial will behave as a COM port and as a ""modem emulator"" to allow ""ATDTfoo.bar"" to establish a Telnet session to foo.bar.

In VB Guest Config, I set up the serial port as needed. When Guest OS is launched, the results vary. But there seems to be flow control issues between the Guest and the Host. I've been talking to the author of NetSerial and have been testing with beta versions of NetSerial as well. He sets the correct flags for flow control, etc. But somwhere between the Guest and the Host, data is lost or delayed indefinitely.

When booting a Linux Guest in this setup, doing ""dmesg |grep tty"" does reveal that Linux has detected a 16550A UART on COM1, which is good thus far. Opening a Linux terminal emulator (any will do) using /dev/ttyS0, data IS being sent to NetSerial on the Windows Host. Using it's ""monitor"", I can see data being received from the Client terminal emulator. I can also see data being sent FROM NetSerial into the COM port. On the Guest, however, nothing is received.

When booting a FreeDOS Guest in this setup, I get similar results to the above. Data missing. Data delayed. Flow control issues, etc. 

Every application that I have tested with is requesting flow control to be CTS/RTS (hardware) and not XON/XOFF.

In almost exactly the same scenario, if I ""move"" NetSerial so that it runs inside the guest (Windows XP), there is no problem whatsoever. In that case, NetSerial is emulating a COM port and using Windows XP Guest Network to reach the Internet. No data being lost. No flow control issues.

So this is definitely related to the ""bridge"" between the COM port emulator running on the Host side of things.

There's still quite a bit of use left for serial device I/O, so I would expect this to work 100% in a product of VirtualBox's maturity. This problem has been present in at least the past 8-10 releases, and I suspect before that.

This is not a case of misconfiguration.",joho68
20353,Fallo al abrir una sesión para la máquina virtual Windows XP.,Windows,VirtualBox 5.1.26,2021-05-10T01:00:27Z,2021-05-10T01:00:27Z,2021-05-10T01:00:27Z,"Fallo al abrir una sesión para la máquina virtual Windows XP.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Alejandro Salcido\Downloads\virtualbox\Windows XP\Logs\VBoxHardening.log'.

Código Resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

",VASG
16973,"Thunderbolt 3 Docks, VirtualBox needs new behavior model",Linux,VirtualBox 5.1.26,2017-08-02T18:50:58Z,2020-12-02T06:19:52Z,2020-12-02T06:19:52Z,"My specific hardware.
* HP zBook 15 G3 Laptop
  * NIC: Intel Dual Band Wireless-AC 8260
  * NIC: Intel Ethernet connection I219-LM
* HP Elite Thunderbolt 3 Dock
  * NIC: Broadcom NetXtreme Gigabit Ethernet
* Host: Windows 7 Enterprise
  * Selected Bridged Adapter Intel PRO/1000 MT Desktop
* Guest: CentOS 7

**Situation**
* Thunderbolt 3 docking stations extend the PCIe such that new devices may appear when docked and disappear when undocked.
* One specific issue is with the NIC. While docked I use the NIC provided by the docking station.
* When undocked I use the Wireless NIC or the NIC on the motherboard.

**Issue**
* VirtualBox is unable to cope went the NIC in the dock completely disappears after undocking.
  * In Windows Device Manager the NIC does not appear
* It is also does not seem to hand gracefully when a Wireless NIC is disconnected from any network.
  * VirtualBox has no wireless bridge adapter option.

I hope this description is through enough.",J.R.
16978,Windows 10: scan for hardware changes freezes after loading Virtual Box manager,Linux,VirtualBox 5.1.26,2017-08-03T21:53:05Z,2019-09-04T20:44:46Z,2019-09-04T20:44:46Z,"Windows 10 Pro
Virtual Box  5.1.26 r117224 (Qt5.6.2)

Restart windows 10
Open device manager
Action: Scan for Hardware Changes

The scan completes normally

Open the Virtual Box manager (doesn't matter if we run a session)
Close virtual box manager
Open device manager
Action: Scan for Hardware Changes

The scan never seems to complete.  The ""Scanning plug and play compliant hardware..."" dialog stays on screen.

Plugging in a new device (such as a USB device) does nothing.   It is not recognized by Windows.

Something happens to windows when the virtual box application is loaded.

",K1MGY
17076,No sound from any guest OS,all,VirtualBox 5.1.26,2017-09-12T15:48:49Z,2019-02-13T11:16:00Z,2019-02-13T11:16:00Z,I never get any sound from guest OSs.  I have tried many Windows and Linux guests with the same result.  The Host OS is Windows 8.1.  This problem has existed for many versions of VirtualBox,mafw
17032,Drag and Drop doesn't work from host W7 to guest W10,Windows,VirtualBox 5.1.26,2017-08-22T10:23:10Z,2018-08-28T09:24:01Z,2018-08-28T09:24:01Z,"Host W7 Professional 64bit latest SP and patches, guest W10 Professiona 64bit.
Bidirection setting.
Drag form host to guest never work.
Drag from guest to host work, but sometime guest freeze and a reboot of the  guest is necessary.
In attach vbox.log and vboxtray.log.",Bonato Agostino
17074,Windows 10 Pro Host/Win7Pro Guest Mouse/Cursor Issue,Windows,VirtualBox 5.1.26,2017-09-11T14:58:16Z,2018-06-07T06:50:41Z,2018-06-07T06:50:41Z,"I have recently replaced my Host System with a Surfacebook running Win 10 Pro with I7 duo core with 16 gig ram and 1TB SSD. VB is version 5.1.26. Guests are windows 7 Pro and Win 10 Pro. Guest in full screen mode. USB mouse and built in Mouse Pad are being used.

VB works however; when in the guest opening Notepad++ and any other apps with text boxes the mouse cursor disappears, I need to change the Input mouse setting to see the cursor. This is annoying since I've uninstalled VB extensions and reinstalled and it requires the Host hot key to exit the VM Guest.

This only occurs when guest is used on secondary monitors. When on the SurfaceBook main screen no issue.  External monitor(s) are attached via the Docking station, and I've tested with the built Display port and had same results there as well.

But after many tries and testing I found if I increase the Guest screen Fonts to 150% the problem no longer exists. This is not really best solution.",Mudoch
17023,"Win 10 Surface Book and multiple Host screens, cannot start on Screen 3",other,VirtualBox 5.1.26,2017-08-19T22:03:11Z,2018-06-05T13:29:33Z,2018-06-05T13:29:33Z,"I just bought a MS Surface Book laptop it run windows 10 Pro 64bit with Surface Doc. All OS patches and firmware has been updated. I have 16Gig of Ram and 1TB SSD.  WHen I launch a guest I get it to start on Vir screen 1 or 2, it sees Vir screen 3 but I cannot get into full screen on that monitor.  I have repeated this with 2 Windows guests that did run on another PC just hours ago. I've uninstalled Guest additions on the one Guest, Win 10 pro also, and reinstalled. I then goto VBox menu select View, Virtual Screen 1, and select Use Host screen 3, Screen stays stuck to Screen 2.  but the screen is indicated.",Mudoch
17014,Fedora Gnome slow UI performance,Linux,VirtualBox 5.1.26,2017-08-15T10:25:33Z,2018-02-23T10:35:13Z,2018-02-23T10:35:13Z,"I've installed fresh and latest Fedora 26 as a VM and when I'm trying to use it, I'm receiving slow GUI response and overall graphic performance is bad. I've tried to use 3d acceleration as well, so the guest starts normally but when GUI part is loaded and login window appeared it's starts to work so slowly, that it's impossible to do anything.

The guest has 4vcpu's, 128mb of video memory and virtualbox additions installed. I'm using windows 10x64 Enterprise (build 10240) with latest intel video drivers (Intel® Graphics Driver for Windows* [15.33]) and latest virtualbox (Version 5.1.26 r117224 (Qt5.6.2)). I have plenty of RAM and i5-3470.",mate
16998,driver services missing,Windows,VirtualBox 5.1.26,2017-08-11T05:14:01Z,2018-02-23T09:31:58Z,2018-02-23T09:31:58Z,"NtCreateFile(\Devie\VBoxDrvStub)failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 RETRIES) (rc=-101)

Make sure the kernel module has been loaded succfully.
where:supR3HardenedWinReSpawn what:3 VERR_OPEN_FAILED (-101) -file/
Device open failed. Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
",amrtin34
17020,dd on USB drive results in Input/output error,Linux,VirtualBox 5.1.26,2017-08-17T22:04:47Z,2017-12-12T10:11:41Z,2017-12-12T10:11:41Z,"Since version 5.1.22 and probably earlier I cannot write images to my USB SD card adapter anymore. Especially when writing larger images such as 4 GB of Raspbian I see the following error after some minutes:

{{{
debianguest:~$ time sudo dd if=/dev/loop0p2 |pv -s 4300M |sudo dd of=/dev/sdc2
dd: writing to '/dev/sdc2': Input/output error                ] 34% ETA 0:17:38
3068849+0 records in
3068848+0 records out
1571250176 bytes (1.6 GB, 1.5 GiB) copied, 567.657 s, 2.8 MB/s
1.46GiB 0:09:27 [2.64MiB/s] [==========>                      ] 34%            

real    9m27.844s
user    0m5.073s
sys     0m43.153s
}}}

Something with the USB driver seems to be broken on Windows 10 hosts. It used to work correctly with earlier versions.

This is an update of bug #17019 with corrected fields.
",Frank Breitling
17009,Windows XP SP3 VM application error on VirtualBox 5.1.26 on Windows hosts,Windows,VirtualBox 5.1.26,2017-08-13T04:48:38Z,2017-11-22T02:42:41Z,2017-11-22T02:42:41Z,"Windows XP SP3 VM consistently causes application error within 10 minutes from startup on VirtualBox 5.1.26. This error happened on three different Windows host PCs.  Error occurs with VirtualBox 5.1.26 running on Windows 10 64 bit host or on Windows 7 64 bit host.  The error message from a Windows 10 host PC is ""The instruction at 0x00007FFADAF76D43 referenced memory at 0x0000000000000018. The memory count not be read."" (see attached image). Windows 7 host may of had a different instruction address but it still had the ""referenced memory at 0x00000018"" text.  No special action was performed to cause the error. I downgraded to 5.1.24 on a Windows 10 host and the XP VM ran very stable with the error happening only once after days of use. I only tested on Windows hosts and not on Linux hosts.",Nick1
17097,After drag and droping files from guest to host the cpu usage of the guest additions tray application skyrockets without any sense,Windows,VirtualBox 5.1.26,2017-09-19T09:52:31Z,2017-09-19T09:52:31Z,2017-09-19T09:52:31Z,"Sometimes after copy some files per drag and drop from the guest to the host the CPU usage of the guest additions tray application skyrockets without any sense, because the files are copied and it is doing anything else (s. screenshot).
I was looking for the log files of the guest additions tray application, but I couldn't find any.",spamme2
17000,Cumulative update for Windows 10 1703 broke Virtualbox VT-x recognition,Linux,VirtualBox 5.1.26,2017-08-11T12:37:20Z,2017-09-18T19:17:38Z,2017-09-18T19:17:38Z,"On 2017-0809 around 1700EDT I upgraded my laptop with a security update for Windows 10 (https://support.microsoft.com/en-us/help/4034674/windows-10-update-kb4034674) and a security update for Adobe Flash player for windows 10 (https://support.microsoft.com/en-us/help/4034662/security-update-for-adobe-flash-player-aug-08-2017).

The following morning I attempted to power up my VM that has been running without major hiccups since mid July and got the following failure code:

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Online searches revealed that this type of problem has been encountered before.

1. https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios

I tried 
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and rebooted but problem persisted.

2. https://stackoverflow.com/questions/5482223/vt-x-is-not-available-when-i-start-my-virtual-machine

I reduced my VM's memory footprint below 4096 but when I powered it up I got a Win10 BSOD

3. https://forums.virtualbox.org/viewtopic.php?f=6&t=58820

I ran
c:\Program Files\Oracle\VirtualBox>VBoxManage.exe modifyvm CentOS-Adva-Dev --longmode off

without any noticable effect on this problem.

I confirmed my laptop's virtualization support is enabled in the bios settings.

I attempted to create another VM and noticed that my only VM guest types are 32 bit. 

I attempted to run an installation repair to my VirtualBox 5.1.26 installation without any success.

I have not tried:
1. Uninstall and reinstall VirtualBox application on my host - I have no reason to believe that this will resolve the issue

2. Rolling back the Windows security updates - this action probably carries more risk than reward.

",edwaldner
17071,Random memory reading errors on Windows XP VMs,Windows,VirtualBox 5.1.26,2017-09-10T21:40:10Z,2017-09-14T17:15:32Z,2017-09-14T17:15:32Z,"Hello.

When I set a Windows XP VM, it crashes randomly (after setup, when installing Guest additions) with the message ""The instruction at 0x0000... referenced memory at 0x00000... the memory could not be read"".

Tested with 2 different Windows XP ISOs : Same problem
Tested on another Windows computer host : Same problem
Updated the graphics card driver to the latest version : Same problem
Tested with all antivirus softwares uninstalled : Same problem

Both of the hosts OS is Windows 10 Pro v.1703 x64",Kakoussnight
17078,Serial ports,Windows,VirtualBox 5.1.26,2017-09-13T00:48:44Z,2017-09-13T00:48:44Z,2017-09-13T00:48:44Z,Phisical serial port works under host OS and does not work under guest OS (Mode: Host Device). At the same time there is everithing OK in Device Manager of Guest OS (The device is working properly). Once the guest OS being launched the serial port vanishes from Host OS. Host and Guest OSes are Windows 7 SP1. I have checked with different motherboards.,MIke
17069,Virtual Box cannot create Virutal Machine of 64bits OS on Windows10 Creators Edition.,Linux,VirtualBox 5.1.26,2017-09-10T04:50:13Z,2017-09-10T21:42:59Z,2017-09-10T21:42:59Z,"When I installed VirtualBox Ver5.1.26 or Ver5.2.0 Beta2 and tried to create new VM image of CentOS 64bit on Windows 10 64bit Creators Edition, then I could not choose any 64bits OS in each OS Version list of ""Create Virtual Machine"" dialog.

What I configure on Windows 10, can I choose 64bit OS in OS version list of ""Create Virtual Machine"" Dialog box.


 ",pioarai
17054,"Please fix virtualbox causing bsod, thx.",other,VirtualBox 5.1.26,2017-09-05T09:03:42Z,2017-09-10T21:36:41Z,2017-09-10T21:36:41Z,"Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`ef20c000 PsLoadedModuleList = 0xfffff801`ef5585c0
Debug session time: Tue Sep  5 04:45:48.116 2017 (UTC - 4:00)
System Uptime: 1 days 22:23:16.527
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: ffffaa019a9a88b3, Address of the instruction which caused the bugcheck
Arg3: ffffaa0198e3dcc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION}  Privileged instruction.

FAULTING_IP: 
+254d5
ffffaa01`9a9a88b3 0f22e0          mov     cr4,rax

CONTEXT:  ffffaa0198e3dcc0 -- (.cxr 0xffffaa0198e3dcc0)
rax=0000000000000274 rbx=ffffaa019a6a7340 rcx=0000000000000000
rdx=ffffaa019a6a7340 rsi=0000000000000000 rdi=0000000000000000
rip=ffffaa019a9a88b3 rsp=ffffaa0198e3e6b8 rbp=0000000000000000
 r8=0000000000024cc0  r9=ffffaa019a6a7000 r10=fffff80097a26900
r11=ffffc3023a6701e0 r12=0000000000000206 r13=0000000000000012
r14=ffffc3022ca60870 r15=0000000000000030
iopl=0         nv up di pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000006
ffffaa01`9a9a88b3 0f22e0          mov     cr4,rax
Resetting default scope

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  VirtualBox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from ffffaa019a9a8732 to ffffaa019a9a88b3

STACK_TEXT:  
ffffaa01`98e3e6b8 ffffaa01`9a9a8732 : 00000000`00000010 fffff800`97a254d5 00007ff8`25127a78 ffff9409`701900b8 : 0xffffaa01`9a9a88b3
ffffaa01`98e3e6c0 00000000`00000010 : fffff800`97a254d5 00007ff8`25127a78 ffff9409`701900b8 ffffc302`3931ec00 : 0xffffaa01`9a9a8732
ffffaa01`98e3e6c8 fffff800`97a254d5 : 00007ff8`25127a78 ffff9409`701900b8 ffffc302`3931ec00 ffffc302`323d6cc0 : 0x10
ffffaa01`98e3e6d0 00007ff8`25127a78 : ffff9409`701900b8 ffffc302`3931ec00 ffffc302`323d6cc0 ffffaa01`98e3eb00 : VMMR0+0x254d5
ffffaa01`98e3e6d8 ffff9409`701900b8 : ffffc302`3931ec00 ffffc302`323d6cc0 ffffaa01`98e3eb00 00000000`00000000 : 0x7ff8`25127a78
ffffaa01`98e3e6e0 ffffc302`3931ec00 : ffffc302`323d6cc0 ffffaa01`98e3eb00 00000000`00000000 00000000`00000000 : 0xffff9409`701900b8
ffffaa01`98e3e6e8 ffffc302`323d6cc0 : ffffaa01`98e3eb00 00000000`00000000 00000000`00000000 ffffc302`2ee00101 : 0xffffc302`3931ec00
ffffaa01`98e3e6f0 ffffaa01`98e3eb00 : 00000000`00000000 00000000`00000000 ffffc302`2ee00101 ffffaa01`00000000 : 0xffffc302`323d6cc0
ffffaa01`98e3e6f8 00000000`00000000 : 00000000`00000000 ffffc302`2ee00101 ffffaa01`00000000 fffff800`97a983c0 : 0xffffaa01`98e3eb00


MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .cxr 0xffffaa0198e3dcc0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

VirtualBox Graphical User Interface
Version 5.1.26 r117224 (Qt5.6.2)

",bugtracjer
17058,Memory protection exception on booting Ubuntu 16.04 VM,Linux,VirtualBox 5.1.26,2017-09-06T20:21:11Z,2017-09-10T10:55:25Z,2017-09-10T10:55:25Z,"Host OS: Windows 10 64 bit, 
Processor: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (12 CPUs), ~3.5GHz
Memory: 32768MB RAM
Available OS Memory: 32692MB RAM
Page File: 9687MB used, 27869MB available

Guest OS: Ubuntu 16.04.3 amd64 desktop, new installation

Logs: https://www.dropbox.com/sh/mzdf371kdpecwcz/AAAvcNt4NIjOd4FqpqzKyrora/MemoryProtectionException1?dl=0

[[Image(https://www.dropbox.com/sh/mzdf371kdpecwcz/AAALaQqILsIp3klecoRjHd-ia/MemoryProtectionException1/ApplicationError.png?dl=1)]]

Ubuntu guest progresses to grub boot menu, then the VM crashes with memory protection exception during the early phase of Ubuntu startup.

Reproducibility: The problem happens many times in a row. If you restart VirtualBox Manager it seems to go away.

No dump yet. Enabled full dumps, will link that here next time it happens.",fviktor
17065,SEGV with plymouth on Ubuntu GNOME 16.04,Linux,VirtualBox 5.1.26,2017-09-08T14:31:53Z,2017-09-08T14:31:53Z,2017-09-08T14:31:53Z,"When booting into Ubuntu GNOME, most of the boots are causing a SEGV in Plymouth as follows:
{{{
Aug 26 17:03:55 matthias-VirtualBox systemd[1]: Received SIGRTMIN+20 from PID 356 (plymouthd).
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Unit entered failed state.
Aug 26 17:03:57 matthias-VirtualBox systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
}}}

Searching the Internet, I have found the issue: With the installation of the VBox Additions, it seems that the plymouth service needs to be re-configured to use the framebuffer.

After issuing the following command, I got never again a SEGV:
{{{
echo ""FRAMEBUFFER=y"" | sudo tee -a /etc/initramfs-tools/conf.d/splash && sudo update-initramfs -u -k all
}}}


I have found this information here:

https://askubuntu.com/questions/695761/plymouthd-crashes-on-startup-intel-hd-3000-15-10

So a potential solution could be to issue this command (or similar) when installing the guest additions on a Linux guest containing plymouth.",Matthias.Winker
17063,Kernel panic on Other (Android-x86-4.4*) guest,other,VirtualBox 5.1.26,2017-09-08T06:57:07Z,2017-09-08T06:57:07Z,2017-09-08T06:57:07Z,Android-x86-4.4* kernel is producing a kernel panic. A screenshot and the log is provided. ,hwline
16996,Application Error and a crash. The memory could not be read.,Windows,VirtualBox 5.1.26,2017-08-10T10:23:28Z,2017-09-06T08:56:58Z,2017-09-06T08:56:58Z,During vm operation message box appears and VirtualBox.exe crashes.,Mik
17047,"Memory Issue since updated to 5.1.26 - ""Instruction at 0x4336d43 referenced memory at 0x00000018. The memory could not be read.""",Linux,VirtualBox 5.1.26,2017-08-31T06:59:07Z,2017-08-31T06:59:07Z,2017-08-31T06:59:07Z,"Host: Windows 7
Guest: Ubuntu Mate 16.04 LTS

Since I have updated to version 5.1.26, I often get a error message when starting the virtual machine (see attached picture).
After the error message, the virtual machine aborts.
After a few tries it finally starts.",TK87
17046,"host only network lost after resuming from sleep (H: win10, G:winserver2012)",Windows,VirtualBox 5.1.26,2017-08-30T23:51:01Z,2017-08-30T23:51:01Z,2017-08-30T23:51:01Z,"Before host goes to sleep, connection works fine. After resuming from sleep, I can no longer ping the guest from the host (""Request timed out""). Occasionally, stoping vbox, resetting the interface on the windows side, then restarting vbox fixes connectivity. In other times, only a full host restart allowed me to recover.

before sleep: 
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           192.168.214.1
    Subnet Prefix:                        192.168.214.0/24 (mask 255.255.255.0)
    InterfaceMetric:                      25

>vboxmanage list hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            539037ce-b029-4212-858f-1b368320c5e5
DHCP:            Disabled
IPAddress:       192.168.214.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:4571:268b:9d7d:c79b
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:09
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

after resume:
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           169.254.199.155
    Subnet Prefix:                        169.254.0.0/16 (mask 255.255.0.0)
    InterfaceMetric:                      25

(vboxmanage's report is unchanged)",somersby
17026,VBox 5.1.26.117224 crashing guest with error,Windows,VirtualBox 5.1.26,2017-08-20T21:39:39Z,2017-08-20T21:39:39Z,2017-08-20T21:39:39Z,"Hello,
as noted in summary there is some situations with my VirtualBox which often lead to crashing guest.
Host is Windows 7 Ent, X64.
Guest is Windows XP SP3.
Any other info please message me.
Log is attached.
Any help would be appreciated.
",H4rDw4rE
17001,Getting memory Access Violations 5.1.26,Linux,VirtualBox 5.1.26,2017-08-11T13:23:44Z,2017-08-15T18:04:07Z,2017-08-15T18:04:07Z,"Randomly getting Memory Access Violations.  Often at some point during startup, but not always.

I looked in the VBox.log file, but nothing jumped out at me.

Are there other ways to debug this?

The VBox.log is attached.",jhellmers
16989,Snapshots should store differencing disks alongside parent virtual disks,other,VirtualBox 5.1.26,2017-08-07T17:23:26Z,2017-08-15T17:01:59Z,2017-08-15T17:01:59Z,"With a VM with the VDI stored on volume J:\, after creating a snapshot, the differencing VDI is stored under C:\%USERNAME%\VirtualBox VMs\.

The VDI was stored on another volume due to space issues on C:, and the differencing disk ended up using up all space on C: when it should have been on J:",Jessica Hamilton
17016,instruction referenced at 0xe6826d43 referenced memory at 0x00000018 could not be read,Linux,VirtualBox 5.1.26,2017-08-15T16:12:23Z,2017-08-15T16:47:38Z,2017-08-15T16:47:38Z,"windows7 host ubuntu 16.04 guest
moved the vm from a win7 notebook to a win7 workstation
a repeatable crash during vm startup, various instruction address

apparently solved the issue by changing chipset type from PIIX3 to ICH9, all other changes to vm settings had no effect

",devotip
17011,"VBox crashes; Host Win 8.1, Guest Debian Strech; amd64",Linux,VirtualBox 5.1.26,2017-08-13T15:30:16Z,2017-08-15T08:35:23Z,2017-08-15T08:35:23Z,"VBox crashes on my new installation of Debian Stretch amd64 as guest system. My host system is Win 8.1, amd64. The crash happens after the installation of the Virtualbox Guest Additions during booting the guest. It is a permanent fault and happens during every boot.

Appended is the Win error message as image (part of a screen dump).",hwkraus
17005,Inaccurate Translation to Chinese,Windows,VirtualBox 5.1.26,2017-08-12T07:18:07Z,2017-08-12T08:06:21Z,2017-08-12T08:06:21Z,"The label ""Name"" in the ""Network"" of ""Settings"" could be translated into ""接口名称""(""Interface Name"") rather than ""界面名称"".",kx_sun
17002,Machine not running,Windows,VirtualBox 5.1.26,2017-08-11T16:01:10Z,2017-08-12T06:02:35Z,2017-08-12T06:02:35Z,"I loaded VB easily enough, had issues getting Kali Linux loaded and installed on VB but finally had success. However, now when I run the machine I get a blank screen:
 and Kali Linux does not open. Any ideas?",Sailingonu
16985,VB Additions incompatible with RAID driver,Linux,VirtualBox 5.1.26,2017-08-06T12:10:13Z,2017-08-06T12:12:30Z,2017-08-06T12:12:30Z,"When installing a Linux (tested Xubuntu, Kubuntu and OpenSuse) in VirtualBox on a physical partition it hangs up when booting this partition natively '''if''' the machine uses a RAID (ie. Intel Matrix Storage Manager). The last message of boot is ""A start job is running for dev-disk-by\ ... .device""

When installing the Linux natively and then booting it in VirtualBox, it works but the VB-Additions fail to install.

On a normal AHCI-enabled machine, every thik's fine.",msta
16954,"Ubuntu 16.04 VM Win 7 Host; VM worked fine on 5.1.24, crashes on fullscreen in 5.1.26",Linux,VirtualBox 5.1.26,2017-07-28T17:24:04Z,2017-08-03T19:25:17Z,2017-08-03T19:25:17Z,"I normally launch this VM fullscreen. It gave no issues up until v5.1.24. In v5.1.26, it crashes unless I run it in windowed mode.",Dale Visser
16964,Repeatable error copying network file into virtual box,Windows,VirtualBox 5.1.26,2017-07-31T15:31:13Z,2017-07-31T15:58:31Z,2017-07-31T15:58:31Z,"Never had a problem with Virtual Box before. Using Virtual box on a win10 pro computer running an XP Pro virtual O/S. With the latest 5.1.26 I now am unable to copy large files from a network share into the VHD. I am able to copy the files from the shared folder with the Win10 pro box. Attached is the error message.
",Affiance
16963,Repeating Left Mouse Click after Drag&Drop of files into the VM,Windows,VirtualBox 5.1.26,2017-07-31T08:49:38Z,2017-07-31T08:49:38Z,2017-07-31T08:49:38Z,"Now and then it happens, that copying a file into the VM by drag & drop the mechanism does not work. Instead endless repeating mouse clicks are fired that make the running VM unusable.",angelo_kairos
16956,Presonus Mixer does not load the driver properly,Windows,VirtualBox 5.1.26,2017-07-29T01:02:41Z,2017-07-29T01:02:41Z,2017-07-29T01:02:41Z,"I have a software title that we use in the Court Systems, we use mixers to record court proceedings. However, in VB I am unable to get the driver to load completely. I see the driver I see it in the USB settings but my software errors out with ""ASIO driver not loaded""

I have attached a log, as directed. 

E",EmGone
16951,SYSTEM_THREAD_EXCEPTION_NOT_HANDLED with 4K resolution in Win10 guest,Windows,VirtualBox 5.1.26,2017-07-27T19:26:56Z,2017-07-27T19:26:56Z,2017-07-27T19:26:56Z,"I have Win10 1703 (Creators Update) as both the host and the guest. My host computer is connected to a 4K (3840x2160) display which is set at 100% scaling (no HiDPI handling). The guest machine has both 2D and 3D acceleration enabled and virtual GPU RAM size is set all the way up to 256 MiB.

When I install guest additions, it works great at first. But when I maximize the guest window (which sets the guest's screen size at 3840x2055) and attempt to reboot the VM in that state, the guest OS tries to switch to that screen mode (borders of the black screen in guest window expand to the desired size) for a brief moment, but then BSODs with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

The only way to fix this is to select low-res mode from recovery boot options and set some lower resolution so that it gets saved in the registry - rebooting in normal mode works fine afterwards.

So all in all, it seems like the virtual GPU driver crashes if screen size is too big at boot time, even though it can switch to such mode just fine on a fully booted system.",kFYatek
17104,5.1.28 Guest Additions Install fails with gnome-terminal 3.24.2,Linux,VirtualBox 5.1.28,2017-09-21T19:15:08Z,2019-12-21T13:49:49Z,2019-12-21T13:49:49Z,"The installation of guest additions fails with gnome-terminal version do to deprecated commands in install command.


{{{
localhost ~]$ /bin/gnome-terminal --version
GNOME Terminal 3.24.2 Using VTE version 0.48.3 +GNUTLS
}}}




{{{
localhost ~]$ sudo sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/autorun.sh
}}}
 
Here is the command that fails in the shell script:

{{{
+ BINARY='/run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run'
+ exec /bin/gnome-terminal --title 'VirtualBox Guest Additions installation' -x /bin/sh /run/media/djohnson/VBOXADDITIONS_5.1.28_117968/runasroot.sh --has-terminal 'VirtualBox Guest Additions installation' '/bin/sh /run/media/djohnson/VBOXADDITIONS\_5\.1\.28\_117968/VBoxLinuxAdditions\.run --xwin' 'Please try running ""/run/media/djohnson/VBOXADDITIONS_5.1.28_117968/VBoxLinuxAdditions.run"" manually.'
Option “-x” is deprecated and might be removed in a later version of gnome-terminal.
Use “-- ” to terminate the options and put the command line to execute after it.
Option “--title” is deprecated and might be removed in a later version of gnome-terminal.
No protocol specified
Unable to init server: Could not connect: Connection refused
Failed to parse arguments: Cannot open display: 
}}}

",septer012
17183,Ubuntu guest on Windows host not properly shut down,Linux,VirtualBox 5.1.28,2017-10-20T08:56:33Z,2018-02-27T08:03:21Z,2018-02-27T08:03:21Z,"It seems that after installing version 5.1.28, Ubuntu guest (32-bit version 16.04.3 LTS) cannot properly shutdown, and an exception is thrown. State of ubuntu guest is displayed as ""abandoned"" afterwards.",Kanaris
17117,"Host Win7 x64, Guest Win7 x64, microphone not working after upgrade to 5.1.28",Windows,VirtualBox 5.1.28,2017-09-28T16:02:29Z,2017-12-04T16:27:50Z,2017-12-04T16:27:50Z,"Dear support

Host Win7 x64, Guest Win7 x64, Intel HD Audio,  microphone is detected but input is not working any more after upgrade from VB 5.1.26 to  5.1.28 r117968 (headset mic analogue 3.5mm jack). In host or VmWarePlayer machine it works (Win7 - sound recording tool, Skype, Win settings test etc.). Uninstallation of Intel HD audio driver caused automatic installation after restart, but it did not help. After downgrade to 5.1.26 VB refuses to use virtual drive file already used in VB 5.1.28 (inconsistent helper structure). Please try to record sound using Intel HD Audio analogue microphone in fresh Win7 x64 guest in VB 5.1.28.

Thank you
Best regards
Jiri",DevTc
17263,VirtualBox encounters an application error and aborts the guest,Linux,VirtualBox 5.1.28,2017-11-10T15:50:50Z,2017-11-10T15:50:50Z,2017-11-10T15:50:50Z,"On a Windows 7 x64 host and a Linux Mint 18.2 guest using Virtualbox version 5.1.28 r117968.
I find that on my Dell Latitude E7440 occasionally when I edject from my docking station I will get the attached Application error, forcing my guest to abort.

At the time I have not mapped any USB ports though and and the network interface is set to my LAN controller. 

Attached will be the log of the aborted machine and a screenshot of the application error.
",BWhitten
17166,Installing Extension Pack trashes Linux MDM Login options,Linux,VirtualBox 5.1.28,2017-10-15T02:28:38Z,2017-10-31T19:41:42Z,2017-10-31T19:41:42Z,"Windows 10 Pro
AMD Athlon™ II X4 650 Processor 3.20Ghz
nVidia GeForce GTX 750 Ti (GeForce Game Ready Driver 3.87.92)
Microsoft Security Essentials
VirtualBox-5.1.28-117968-Win.exe
Oracle_VM_VirtualBox_Extension_Pack-5.1.28-117968.vbox-extpack

There is something about installing the VirtualBox Extension Pack (5.1.28) that wipes out my MDM Login menu in my Linux Mint 17.2 / XFCE / Wmaker VM.

I updated my Windows 10 Pro machine to VirtualBox-5.1.28-117968-Win.exe and installed Oracle_VM_VirtualBox_Extension_Pack-5.1.28-117968.vbox-extpack in my Linux VM. This trashed my ability to log into any of my desktops other than my original XFCE Desktop.

My MDM Login menu worked as expected under 5.1.22 but exhibited the same problem in earlier extension packs.

This also happened when I tried to upgrade VirtualBox to v5.0.24 - I didn’t report it then. I just assumed a later version (5.1.22) would fix the issue.

------------- Prior Issue ---------------

by BasilRathbone » 17. Oct 2016, 19:14 

I run VirtualBox 5.0.16 under Windows 10 Home Premium. One of my VM's is Linux Mint 17.2. I run multiple desktops under Linux Mint 17.2, XFCE and WMaker, my favorite being Wmaker.

I tried updating VirtualBox to version 5.1.6. Installing 5.1.6 Extensions in my Linux VM trashes my ability to log into any of my desktops other than my original XFCE Desktop. My MDM Login menu works under 5.1.6 until after I run VBoxLinuxAdditions. Something in that installation process trashes MDM.

This also happened when I tried to upgrade VirtualBox to v5.0.24 - I didn’t report it then. I just assumed a later version would fix the issue.

The last version that works properly for me is 5.0.16 running under Windows 10 Home. ",BasilRathbone
17167,Can't install Extensions in WMaker / Linux Mint 17.2,Linux,VirtualBox 5.1.28,2017-10-15T03:10:59Z,2017-10-16T22:27:26Z,2017-10-16T22:27:26Z,"Clicking on ""Insert Guest Additions CD Image"" while running WMaker (0.95.8+20170322) running on Linux Mint 17.2 fails.

VBOXADDITIONS_5.1.28_117968 never shows up under /media/my_name/

Inserting Guest Additions has never worked under any version of WMaker I've ever run.

I can log out of WMaker and log back in under XFCE and install guest additions but that's trashed the MDM Menu and my ability to log back in to WMaker.",BasilRathbone
17164,wireless mouse stopped working,Windows,VirtualBox 5.1.28,2017-10-13T13:57:06Z,2017-10-16T14:58:02Z,2017-10-16T14:58:02Z,"I installed the new 5.1.28 version and it caused my wireless mouse to stop working in BOTH the HOST and the virtual computers.  I tested this with both a wired and wireless mouse and several virtual computers, rebooted several times.  Each time this was the cause of the interference.  This was not present in previous versions of virtualbox and I previously was using 5.0.46.",3_laws
17159,vboxsf file timestamp not set properly,Linux,VirtualBox 5.1.28,2017-10-12T15:40:37Z,2017-10-12T15:40:37Z,2017-10-12T15:40:37Z,"Setting file modification timestamp on a file seated in shared folder does not work properly.

The case description:

{{{
$ df -h .
Filesystem      Size  Used Avail Use% Mounted on
Shared          932G  317G  616G  34% /media/sf_Shared
$ mount -l | grep Shared
Shared on /media/sf_Shared type vboxsf (rw,nodev,relatime)
$ touch -md ""1970-01-01 00:00:00""   test
$ ls -l test
-rwxrwx--- 1 root vboxsf 0 '''Jul 22  2554''' test

}}}

Doing the same on a native fs does work as expected.",Norbert Novotny
17157,100% CPU usage (windows 10 VM) running on WIndows 10 VM,Windows,VirtualBox 5.1.28,2017-10-11T14:44:00Z,2017-10-11T16:55:55Z,2017-10-11T16:55:55Z,"I've recently moved 2 virtual PCs from a windows 10 PC to another windows 10 Pc. They have the same hardware spec. When I run the VM's on the new PC they just run at 100% CPU usage (after login). This did not occur on the other PC. 
I created a new Windows 10 VM and this seems to work with the CPU usage issue.
I have checked various settings on the W10 VM and on the Oracle Virtual Machine settings. They are not 'useable' on the new machine. I did upgrade from VM 5.1.22 to 5.1.28. I need to use the VM's on the new PC - but the CPU issue is stopping any productive use.",RhUkDev
17153,Blue screen when starting Windows 7,Windows,VirtualBox 5.1.28,2017-10-10T11:57:32Z,2017-10-10T17:02:52Z,2017-10-10T17:02:52Z,"Blue screen when starting Windows 7. After 4 or 5 restarts ok. 
When shutting down a report of a serious error appears. Contact support.",stback
17151,Crashes with critical error when trying to start Window 7 32-bit in Windows 7 64-bit,Windows,VirtualBox 5.1.28,2017-10-10T01:06:54Z,2017-10-10T09:13:01Z,2017-10-10T09:13:01Z,"""A critical error has occurred while running the virtual machine and the machine execution has been stopped"" 

Yesterday it ran correctly until now. I tried to start the system and when the Windows logo disappears the message appears.",Francisco Gonzalez
17145,E_FAIL (0x80004005) SessionMachine,Windows,VirtualBox 5.1.28,2017-10-08T13:49:21Z,2017-10-08T13:53:54Z,2017-10-08T13:53:54Z,"Не удалось открыть сессию для виртуальной машины BOT.

The VM session was aborted.

Код ошибки: E_FAIL (0x80004005)
Компонент: SessionMachine
Интерфейс: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

",free0n
17144,Direct3D11.1 crashes,Windows,VirtualBox 5.1.28,2017-10-07T10:38:48Z,2017-10-07T10:38:48Z,2017-10-07T10:38:48Z,"Dear Sirs!

I have a platform:
Host is a Windows 10 Creators Update.
Virutal PC has Windows 8.1 Up to Date.
DirectX applications are crashing in this configuration.
It is possible to create a Direct3D11.1 and its Context.
Releasing the device throws an hardware exception (bad pointer).
I can not use the DXDiag.exe, it crashes also.

[[Image(https://www.kubera.info/ms/2017-10-07.png)]]",kubera
17143,Windows 10 BSOD if Guest OS started,Linux,VirtualBox 5.1.28,2017-10-06T09:47:15Z,2017-10-06T09:47:15Z,2017-10-06T09:47:15Z,"Hello.
If I start guest operation system - I tried FreeBSD, Ubuntu, my laptop got BSOD. Windows 10 Enterpise  1703 (OS Build 15063.384). I made searh about this type of issues - WTx - instructions enabled in BIOS and HYPER-V uninstalled.
",lvesel
17142,Virtual machine crashed while installing IBM Maximo,Windows,VirtualBox 5.1.28,2017-10-05T18:18:29Z,2017-10-06T09:13:04Z,2017-10-06T09:13:04Z,"I'm hoping somebody can help me figure out this problem. I created a Windows 2012 Server as a guest and tried to install IBM Maximo and the VM crashed.  The log and png file are attached.

I am using VirtualBox v5.1.28 on a older Windows 7 system with 32Gb of RAM.",Al Menendez
17138,Changes to VMDK image on USB Storage Not Preserved,other,VirtualBox 5.1.28,2017-10-04T17:52:33Z,2017-10-05T14:06:38Z,2017-10-05T14:06:38Z,"I have a VM with a VMDK file mounted on a USB mass storage device (e:\ drive).  The Guest OS is CentOS 7.3.1611 (32 bit).  I have been using it without issues for about a week.

Yesterday, I modified a few files on the VM and then rebooted the VM --- and the file changes were gone!  I thought maybe user error, but I created a test file in my home directory and rebooted, and the file did NOT persist (as if the disk was a ramdisk, even though it's not).  I tried this several times, with different ways of rebooting (shutdown -r, manually typing sync first, CentOS GUI, etc), with the same result.

I looked through log files but didn't see anything that looked out of the ordinary.

I have a feeling this has to do with USB -- maybe plugging/unplugging other USB devices confused the OS or VirtualBox -- just a guess.  But in any case, there was no warning that my changes were not being saved onto the disk image.

After this testing, I restarted my host PC (Windows 7), and now things appear to be working -- although I have lost some trust with this setup since I don't really know what happened and it caused data loss.",Joe E Clark
17118,virtualbox nataliasmode proxyonly breaks local network connectivity on windows 10,Linux,VirtualBox 5.1.28,2017-09-28T18:09:31Z,2017-10-02T14:42:29Z,2017-10-02T14:42:29Z,"Hi,

I have enabled proxyonly for the nat and now for the entire local network i am unable to access the guest machine in any of the protocols. thoouh it is accessible from the internet.

Thanks,
Vipin",Vipin Jain
17121,BSOD after launching VM,Windows,VirtualBox 5.1.28,2017-09-29T07:38:51Z,2017-10-02T08:11:17Z,2017-10-02T08:11:17Z,"Hello,

Recently I've upgraded VirtualBox from 5.0.20 to 5.1.28 version. Unfortunatelly it caused that after launching VM appears blue screen; it is possible to launch VM in safe mode, but normal mode crashes. I' ve tried to back to my prior version, but it didn't help; reinstall VirtualBox and change VM settings in many different ways also didn't help. Host is Windows 7 64-bit; guest is Windows XP 32-bit. Interestingly I' ve set this host image on other guest, Windows 10 32-bit on VirtualBox 5.1.10 and it run, but on Ubuntu 32-bit and 64-bit not. Please give me a hint what I have to do to solve this issue.",Skywanter
17120,Installation of 5.1 & 5.2 Beta failing for Windows 10 Pro,other,VirtualBox 5.1.28,2017-09-29T00:07:54Z,2017-09-29T02:07:06Z,2017-09-29T02:07:06Z,"In multiple attempts to install on Windows 10 Pro 64 bit v1703 build 15063.608, VirtualBox fails to install. I've tried VirtualBox-5.1.24-117012-Win.exe, VirtualBox-5.1.28-117968-Win.exe, VirtualBox-5.1.29-118065-Win.exe and VirtualBox-5.2.0_BETA2-117563-Win.exe. I've attached a log from running from the command line as an admin using the --logging param. Any help would be appreciated.",ElysiumTacos
17115,X of guest freezes with 3D acceleration enabled,Linux,VirtualBox 5.1.28,2017-09-28T11:11:49Z,2017-09-28T11:11:49Z,2017-09-28T11:11:49Z,"Hello.

I found that X seems to freeze after login to my Ubuntu 16.04 if 3D acceleration is enabled. The screen is not updating, the mouse cursor moves as it should and I can Ctrl+Alt+F1 to a TTY (and back).

If I change screen resolution by pressing Host+F, I get garbage that remains there even if I change the resolution back to full-screen.

I think this might be related to the closed issue #13487 because the symptoms sound similar.

My Ubuntu 16.04 is up to date and so are the guest additions. The host is Windows 10.

Cheers,

Jan",Jan P.
17108,Virtualbox 5.1.28 running under Windows 10 corrupts clipboard copy & paste,Linux,VirtualBox 5.1.28,2017-09-22T16:16:06Z,2017-09-22T16:16:06Z,2017-09-22T16:16:06Z,"Performing Windows cut & paste operations (using Ctrl+c/Ctrl+v) between VirtualBox VM and Windows frequently corrupts Windows clipboard... VirtualBox 5.1.28 r117968, Windows 10 Pro (v1703 OS Build 15063.608), RHEL 6.9 VM.

Once corruption occurs, pasting between Windows applications such as Notepad, Word or Outlook Email exhibit pages of non-printable characters. Eventually Windows 10 mouse clicks used to switch between applications stop working, Windows taskbar crashes (and won't restart), Desktop background goes black, and Windows becomes non-functional without being rebooted. Ctrl+Alt+Delete still functions and Windows Task Manager runs normally. Task Manager allows switching between applications and doing normal Windows shutdown.",Jayb
17107,"Hello, Today I just upgrade my Vbox, and now I can't open the software. Need Help",Windows,VirtualBox 5.1.28,2017-09-22T14:23:00Z,2017-09-22T14:23:00Z,2017-09-22T14:23:00Z,"Fallo al abrir una sesión para la máquina virtual Siemens Win 7 64 bit.

The device helper structure version has changed.

If you have upgraded VirtualBox recently, please make sure you have terminated all VMs and upgraded any extension packs. If this error persists, try re-installing VirtualBox. (VERR_PDM_DEVHLPR3_VERSION_MISMATCH).

Código Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Rocko
17083,Virtualbox Graphics Adapter for Windows 8+ incompatible with Skype For Business 2016,Windows,VirtualBox 5.1.28,2017-09-15T17:24:47Z,2017-09-21T12:46:04Z,2017-09-21T12:46:04Z,,FrankW
17103,Mouse direction locked in opengl programs,Linux,VirtualBox 5.1.28,2017-09-21T04:51:24Z,2017-09-21T04:51:24Z,2017-09-21T04:51:24Z,"Host Win10, Virtual box 5.1.28 with Ubuntu 16.04 installed.
After install the VBoxGuestAdditions, when i start an opengl Application, the mouse lost control, just pointting to the sky.
When I tried to move left/right, the picture just rotate, not looking around.",ffpwserver
17088,Crash when trying to access SMB network shares under evaluated user,Windows,VirtualBox 5.1.28,2017-09-16T06:14:41Z,2017-09-20T08:18:21Z,2017-09-20T08:18:21Z,"Issue came with update 5.1.26 to 5.1.28.

Guest: Windows 10 Pro 1703
Host: Windows 10 Pro 1703 as well as Windows 7

Crash in the guest system only with the evaluated user, so it might be related to the others issues which Windows 5.1.28 guest extensions has with evaluated users. No problem with standard user. 

The crash is that after login for accessing the SMB shares the explorer terminates. Doing this with another file manager (total commander 9.0a), the file manager hangs. No SMB access for the evaluated user possible.",Denis.L
17099,Shared clipboard : bidirectional mode causes host clipboard malfunctions,Linux,VirtualBox 5.1.28,2017-09-19T17:33:33Z,2017-09-19T17:33:33Z,2017-09-19T17:33:33Z,"Windows 10 host
Linux (Ubuntu 16.04) guest

When the Shared Clipboard is set to Bidirectional, the following issues manifest on the Windows 10 host:

* In Excel, copy cell, paste to multiple cells (select range of cells and paste) does not work
* In Office applications, copy/paste of formatted text does not work; only the text is copied

If Shared Clipboard is set to any of the other three options (Disabled, Host to Guest, or Guest to Host) then the problem does not manifest itself and the above functionality works properly.

This is reproducible at will.

I also noticed this issue on a Windows 7 host running a Linux VM.",Studio
17264,Virtualbox 5.1.30 Error,Windows,VirtualBox 5.1.30,2017-11-10T16:19:35Z,2022-04-11T10:30:15Z,2022-04-11T10:30:15Z,"After installing a program in the virtual machine when I reboot the virtual machine I get the following error:

Failed to get a console object from the direct session (RPC_E_DISCONNECTED).


Result Code: 
VBOX_E_VM_ERROR (0x80BB0003)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
",cmccarron
17354,Can't setup Host-Only Network Adapter on Windows 10 Client,Linux,VirtualBox 5.1.30,2017-12-06T18:20:42Z,2018-10-26T04:03:44Z,2018-10-26T04:03:44Z,"Hi,


'''[How to reproduce it]'''
From fresh installation, installation was ok, no errors, the problem began when I tried to setup the missing IP and network mask for the Host-Only Network Adapter, first thing I noticed is that upon setting up the values VBox was resetting the values every time and clean the values up.

-I'm using VirtualBox Version 5.1.30 also tried with 5.2.0 for Windows
-I have Windows 10 Pro running on a Dell Precision, 16GB RAM, 64-bit, core i7 vPro
-I'm trying to host a Linux VM that contains some web application, so I can access them via u.r.l. , this is a RedHat VM

After this I tried a lot of things to make the Host-Only adapter work

- I had 3 VM, I remove 2 of them and test 1 with one
- Remove every single VM and try to set the values
-Try to set the values using TCP/IP v4 properties in the actual Network device on Windows' Network connections
- Uninstall VBox, install a older version (VirtualBox-5.1.30)
- Reinstall VBox using Admin option
- Uninstall VBox, delete completely .VirtualBox folder, reboot the machine, then reinstall VBox as: user and admin
- Delete all the Devices using the GUI and create the device using VBoxManage hostonlyif create

",Diego Resendi
17825,Restoring VM goes from running to Guru Mediation state,Windows,VirtualBox 5.1.30,2018-06-16T03:05:14Z,2018-06-16T14:06:50Z,2018-06-16T14:06:50Z,"I have created saved state and restoring it. It works fine on Windows 10 Host OS where as in Windows 8.1 Host it gives below error [[BR]]
''aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} '''aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}''', preserve=false''

before this line log shows that guest is getting some fatal condition [[BR]]
''00:00:37.170678 GIM: HyperV: Guest indicates a fatal condition! P0=0x7e P1=0xffffffffc000001d P2=0xfffff803462b21ec P3=0xffff9e0187736768 P4=0xffff9e0187735f90
''[[BR]]

System configuration is:[[BR]]

Guest OS: Windows 10 64 bit[[BR]]

Host OS: Windows 8 64 bit[[BR]]


I have attached log for more information. Not sure what is the reason of failure.",Jeet15
17814,Seamless mode & sleep,Windows,VirtualBox 5.1.30,2018-06-11T18:37:51Z,2018-06-11T18:37:51Z,2018-06-11T18:37:51Z,"After wake up in seamless mode, the taskbar is not shown (guest OS is XP).
In addition when I tried to log off the saved state of VM was lost. It is better to do hibernate of shut down when host OS is logging off or shutting down.

",386sx
17230,"When using modifyvm --groups from the command line, the Virtualbox GUI displays the new VM, but grouping does not update until you close and reopen the GUI.",all,VirtualBox 5.1.30,2017-10-31T18:14:21Z,2018-04-06T10:57:00Z,2018-04-06T10:57:00Z,"1) Open VirtualBox Manager

3) .\VBoxManage.exe modifyvm ""vm1"" --groups ""/group1"" 

4) .\VBoxManage.exe modifyvm ""vm2"" --groups ""/group1""

5) Switch to VirtualBox Manager

Result: VirtualBox Manager doesn't show newly created group.

Restart VirtualBox Manager
Result: VirtualBox Manager shows the group and the two VMs are under it.
",oak_leaf
17432,After upgrade 5.1.30 it never worked again,Windows,VirtualBox 5.1.30,2018-01-08T18:48:23Z,2018-01-08T19:03:22Z,2018-01-08T19:03:22Z,"Long time using VirtualBox and after install upgrade 5.1.30 it left working again. I upgrade to 5.2 version and the same result with a different problem. Each time updated Extension Pack, but nothing.",FGGarcia
17270,Scrolling with mouse integration,Linux,VirtualBox 5.1.30,2017-11-13T22:18:29Z,2017-11-30T16:20:57Z,2017-11-30T16:20:57Z,"While using VBox 5.1.30 with Mouse Integration turned on the wheel scroll event is not passed to some windows while moving the mouse. If mouse is stationary the scroll is registered fine. It happens over Chrome, Firefox, GTK windows, but works fine for Java and urxvt windows.

I've already tried it with libinput and evdev on the guest Fedora 26 system. The behavior is the same.

Thank you.

Yaroslav",Yaroslav
17330,Ubuntu 17.10 guest freezes when restoring guest windows,Linux,VirtualBox 5.1.30,2017-11-29T17:04:05Z,2017-11-30T00:08:01Z,2017-11-30T00:08:01Z,"Okay, so this is driving me nuts. Running VB 5.1.30 on a windows 7 host with a Ubuntu 17.10 (desktop) guest OS. 

I installed the guest additions without issue, though I read here https://forums.virtualbox.org/viewtopic.php?f=6&t=85186 that Ubuntu comes with a set of guest additions installed by default that may cause issues, not sure if that's relevant.

Everything works fine (for the most part) but when I enable 3d acceleration (host has a gtx1070) it runs smoothly... until I 'restore' (un-maximize) a window within the guest. 

Then the machine freezes (any actions take 3-10 seconds for a response) and begins consuming as much as 15-17% of my (i7) cpu and even slowly getting the original window to close in the guest does not restore it's usability or reduce it's cpu consumption. 

Disabling 3d acceleration allows the machine to run stably however it's not very smooth comparably, and simulating both my 2560x1440 monitors makes the machine so sluggish it's not usable.

Any hints to why this would be happening and how to fix it would be much appreciated.",DMeganoski
17248,Guest Additions Directory Listing in Windows XP,Windows,VirtualBox 5.1.30,2017-11-06T21:19:25Z,2017-11-06T21:19:25Z,2017-11-06T21:19:25Z,"Windows XP installed in VirtualBox.  
Host Window 7 or Windows 10.  
Directory listing works OK as 'dir' from DOS Prompt or as 'file open' from notepad.  
But for some programs, if directory listing returns 8 or fewer files, OK; but if directory listing returns 9 or more files, nothing.  
An example program with this problem is the old Norton fa.exe command which lists files and attributes (eg, archive, readonly).  
",Roger
17247,i-beam cursor missing / tiny scale (Win guest additions 5.2.1),Windows,VirtualBox 5.1.30,2017-11-06T18:29:09Z,2017-11-06T18:29:09Z,2017-11-06T18:29:09Z,"Windows host (5.2.0) and Windows guest with additions (5.2.1).

With a 4K screen (3840x2160) at 100% scale, the ""Text Select"" (i-beam) cursor is missing (not rendered). When Windows mouse properties / pointers set to a custom cursor (e.g. beam_r.cur) it is really tiny - too small to see properly.

With the host set at 300% scaling, beam_r.cur is the correct size.

[Update after further testing]
c:\windows\cursors - cursors with the small 9KB file size are not scaled properly. Cursors with the > 100KB file size are.

(This affects windows guests. Using these smaller cursor files on the Windows host scales correctly.)",dangr
17234,Cannot Install VirtualBox Extension pack after upgrade,Windows,VirtualBox 5.1.30,2017-11-03T15:06:13Z,2017-11-04T23:33:50Z,2017-11-04T23:33:50Z,"I am running virtualbox on Windows 10. I just upgraded to VirtualBox V5.1.30 r118389. I uninstalled old version of guest edition extension pack and downloaded latest version 

On installing, the following error is reported:

Failed to install the Extension Pack C:/Users/Administrator/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.2.0-118431 (1).vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-11020' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

I had no problem when upgrading to VirtualBox V5.2.26",Tony_UK
17231,Installing Grisoft's AVG into Win 7 SP1,Windows,VirtualBox 5.1.30,2017-10-31T20:00:27Z,2017-10-31T21:01:12Z,2017-10-31T21:01:12Z,Nearly installed (97%) and it stopped with your 'Guru Meditation' screen,Lofty
17187,GPO: automatic update need to be disalbed per machine,other,VirtualBox 5.1.30,2017-10-20T15:35:56Z,2017-10-20T16:20:49Z,2017-10-20T16:20:49Z,"We deploy the MSI file to some developer machines. However it annoys us permanently (every few weeks) about new unimportant version. I know there is a way to disable the warning per user, but this does not help as the software is installed per machine. I cannot change the settings file with a GPO.

We need a registry key or xml config file in app folder or a MSI propery (best) that allows us to disable automatic updates globally.

Always keep in mind that users are not allowed to install or update software.",Marc Bauer
17492,Guest audio playback sound like fast-forward tape.,Windows,VirtualBox 5.1.32,2018-01-22T17:20:43Z,2019-06-08T16:57:06Z,2019-06-08T16:57:06Z,"HOST is Windows 7 64-bit[[br]]GUEST is Windows XP

Additionally, some video playback be affected, too. (most files are MP4, quite few can test.)

Some walkaround I tried:
* Downgrade VBox to 5.1.30[[br]]-> Good, Back to normal.
* Boot same VM Guest in Debian HOST (5.1.32)[[br]]-> Good, Work as expected.",NoNoNo
17614,Sound distortion and disappearance in Windows guest,Windows,VirtualBox 5.1.34,2018-03-10T23:39:02Z,2019-04-21T19:26:35Z,2019-04-21T19:26:35Z,"This is follow-up ticket for some other tickets with this problem, such as #17225 or #17492. So after some issues appeared on the 5.1.32 it now gets even worth. On Windows 8 host / Windows 7 guest combination sound works nearly fine but completely disappears after some minutes. And there is nothing in the logs, everything looks fine here. On Windows 10 host and guest combination I can’t get any sound at all. Everything is kind of here and presented, but if you try to play something in the guest, the playing software got some seconds of hesitation at the first moment and then time starts to run without a sound. At the second try everything starts immediately but also without a sound. Going back to the previous version helps of course.

For socratis: I know that this is 1001 ticket about this, but I file it anyway. Because it is a new version and it’s a new behavior. So now I’m back to the 5.1.30 where I have no problems with sound. And in my case I simply see further declining in this version after we already got some slight problems in 5.1.32. Anyway I like to thank anybody how is working on this problem.",boxer01
17588,KB4056448 cause hardening error,all,VirtualBox 5.1.34,2018-03-05T09:35:46Z,2018-03-20T21:08:14Z,2018-03-20T21:08:14Z,"KB4056448 on Windows Server 2008 x64 SP2 cause hardening error. Same with VBox 5.2.8.
",Victor Abramoff
18082,still doesn't work copying and pasting some words with shift + insert,Linux,VirtualBox 5.1.38,2018-10-25T12:36:28Z,2018-10-25T12:45:57Z,2018-10-25T12:45:57Z,"Hi experts,

I tried that above after installing each GuestAddition at 3 version, but all failed. The version are 5.1.38, 5.1.28, 5.1.24 for windows host.

when input shift + ins, F was displayed only. 
I don't know why it occurred.

My computer is ThinkPad X270 installed Win10 latest patch.

Br,
Tomio

",Tomio
17780,CentOS 7.5 Guest Additions not installing,Linux,VirtualBox 5.1.38,2018-05-21T15:54:38Z,2018-05-21T16:00:44Z,2018-05-21T16:00:44Z,"I had a CentOS 7.4 VM and then I updated it to the latest kernel so that it is now running CentOS 7.5 and my screen won't resize and I can't copy/paste between my Windows Host and my VM. Originally I was on VirtualBox 5.1.32 and I tried reinstalling the guest additions, this didn't work and I couldn't work out what was causing the issue from the VBoxAdd-install.log.

I saw a fix in the latest version of VirtualBox but this didn't fix the issue even after installing the latest guest additions.

Rough Steps to Reproduce:

 - Upgrade CentOS 7.4 VM to CentOS 7.5
 - Install latest guest additions",oletts
15827,Error message when starting VMs: Error In supR3HardenedWinReSpawn,Linux,VirtualBox 5.1.4,2016-08-19T13:34:14Z,2021-07-06T13:05:47Z,2021-07-06T13:05:47Z,"Almost everyday when I start my machine and run Vbox and try to start a vm, a msgbox appears with the following error:


{{{
VirtualBox - Error In supR3HardenedWinReSpawn
(rc=-5640)
Please try reinstalling VirtualBox.
where supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.
}}}

When I click ""ok"", another msgbox appears:

{{{
Failed to open a session for the virtual machine Ubuntu 16.04.

The virtual machine 'Ubuntu 16.04' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\jbassi\VirtualBox VMs\Ubuntu 16.04\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
}}}

This has been happening for month, with current version, last version, tests versions, etc.
The reason I haven't reported this bug until now is because if I try again a few times (two or three) the VM starts up correctly. So I cannot reproduce everytime. In order to reproduce I need to restart the machine. The first time I try after a reboot almost always fails.

Version: Version 5.1.4 r110228 (Qt5.5.1)
Host: Windows 8.1 Enterprise
CPU: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
",asdfafds
15839,Attempting to output audio causes processes in guest to hang,Linux,VirtualBox 5.1.4,2016-08-21T15:37:52Z,2020-08-31T06:50:49Z,2020-08-31T06:50:49Z,"Since upgrading to 5.1.4 audio output in the guest has become unreliable. A process that attempts to play sound freezes. Sometimes, if I kill off all processes trying to play sounds, I can run aplay or speaker-test a couple of times, but a few moments later they still stop working again.

Guest is running 64-bit Linux 4.6.0, host is 64-bit Windows 10 Home. The sound card is ICH AC97.",Sam Morris
15810,VirtualBox Manager has stopped working when adding USB hard disk in Storage,Windows,VirtualBox 5.1.4,2016-08-17T12:19:56Z,2020-01-20T13:43:17Z,2020-01-20T13:43:17Z,"I stumbled upon a bug in the GUI.

To reproduce, go to VM Settings.
1) I start with no controllers in the Storage Tree.
2) Add USB Controller.
3) Right click the new controller -> Add Hard Disk

Crash.

",danf84
15900,Remote Desktop (RDP) into Windows10 (64-bit) Host Crashes Full Screen Guests 5.1.4,Windows,VirtualBox 5.1.4,2016-09-07T15:48:55Z,2018-10-11T16:52:46Z,2018-10-11T16:52:46Z,"I've had multiple full-screen VMs crash twice now upon getting connected to my Windows 10 64-bit host via the standard Windows Remote Desktop client. The sequence of events scenario was similar both times: I'll typically leave a few guests running full-screen in the background, remote into the host while away, reconnect to the local host console upon returning, then remote in again next day. On the 1st remote connection, the full-screen guests that were left running flash the hosts Windows taskbar, and switching to them restores the full-screen display. Upon the 2nd or so remote connection, the full-screen guests that were left running again flash the host's Windows taskbar, and clicking then to switch to them causes them to crash with (latest example):

[Running] - Oracle VM VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x000000005B16C025 referenced memory at 0x000000000D41E000. The memory could not be read.

Host: Windows 10.0.10586 (64-bit), Dell Precision T5500 36GB RAM
Displays: (NVIDIA GeForce GTS 240)
Primary (Dell 2408WFP) 1920x1200
Extended (Samsung TV) 1920x1080
Guests (all configured for a single display):
Windows 10
Windows Vista (2 CPUs)
Windows XP
(not sure about Linux/Mint)

In all cases, the Remote Desktop client is set to start full-screen on 1 display. Not sure if this could be the reason or if it could be caused by the host having two different screens (speculation of course). However, simply connecting to a host should not crash guest VMs.
",CM7
15879,VBoxSVC.exe prevents logoff,all,VirtualBox 5.1.4,2016-09-02T18:16:52Z,2018-04-17T20:31:24Z,2018-04-17T20:31:24Z,"If you kill a running virtualbox.exe process, then VBoxSVC.exe would stay running (as it always did) and would prevent logoff/shutdown saying that it ""Has active connections"". That was never the case at least up to VirtualBox 5.1.0. The way to reproduce:
1) start any VM
2) kill the running virtualbox.exe process 
3) try to logoff. 

I can always reproduce the problem (at least) on a Win7 x64 host.
",mskov
15897,Symfony clearing cache fails when done through shared folder (rmdir fails),Linux,VirtualBox 5.1.4,2016-09-07T03:33:41Z,2018-03-06T15:58:02Z,2018-03-06T15:58:02Z,"I have opened a bug on the Symfony bug tracker (https://github.com/symfony/symfony/issues/19851), however, I believe this is an issue between Linux and Windows with a shared folder.

I am using RHEL7 on the guest machine and windows 8 on the host. The /var/www/ dir is a mount of a shared folder on the windows machine (a Virtual Box share). I have installed Symfony on the guest, so its files are done through the share (I can browse them on the host).

Everything seems to run fine except clearing of cache. This fails saying that there are files in the dir that it is trying to run an rmdir on:
{{{
(Failed to remove directory ""/var/www/html/tut1/var/cache/pro~/twig"": rmdir(/var/www/html/tut1/var/cache/pro~/twig): Directory not empty.)
}}}
Looking in windows, I can see that there are a bunch of files still showing there, however, when I try list (dir, ll and a bunch of other options attempted), it shows no files. Yet if I try to do an rm -R on the dir:
{{{
rm -R /var/www/html/tut1/var/cache/pro~/twig/
}}}
it says that it can't:
{{{
rm: cannot remove ‘/var/www/html/tut1/var/cache/pro~/twig/’: Directory not empty
}}}

If I remount the /var/www/ mount (or reboot the guest), the files all show and I can run the rm command without any issues.

It's like in the Symfony script it is sending the unlink command that is being reported as successful even though on the host the files are not deleted.

I will attach an strace log if that is of any help. The main lines I looked at are copied into the Symfony bug report.

If you want to replicate this, install with a linux guest, windows host and install and run Symfony on it. Browse to a prod page (go to /project-name/web/app.php) and then clear the cache with the following command:
{{{
php bin/console cache:clear --env=prod
}}}
if you then delete the /project-name/var/cashe/pro~ dir and try that command again (or remount the share) it will work.",MicWit
16359,VBOX XML files are not locked by VBOX Manager instances,all,VirtualBox 5.1.4,2017-01-05T15:43:42Z,2017-01-05T15:43:42Z,2017-01-05T15:43:42Z,"We have lost snapshots recently because the .vbox XML files are not locked by the Virtualbox Manager. 

Steps to reproduce:
1. Create a new VM in User1 Windows account.
2. Don't quit from the Virtualbox Manager GUI.
3. Switch to Windows user account User2. 
4. Open the same VM in the Virtualbox Manager.
5. Create a new snapshot (Snapshot 1). 
6. Close the Virtualbox Manager in User2 account, logoff from User2.
7. Switch back to User1.  Snapshot 1 is not listed. 
8. Close the Virtualbox Manager.
9. Start the Virtualbox Manager. Snapshot 1 is not listed. 

Expected result: When the User2 opens the VM in the Virtualbox Manager, it should raise an error that this VM is locked by another user. 

These errors never happen intentionally, so it would be great if the Virtualbox Manager could lock the vbox files.

Sometimes we can recover the snapshots by manually recreating the snapshot entries in the vbox XML file, but this is not optimal.

Thank you for your help",Z6543
16293,memory can't be written,Windows,VirtualBox 5.1.4,2016-12-15T13:50:37Z,2016-12-15T13:50:37Z,2016-12-15T13:50:37Z,"tried to create common folder and got bug with nulls and message ""memory can't be written"".
i remove this version of VBox and install 4.1.4, and now it works
fix this bug in 5.1.4 pls :)",ilyarik
16214,Blocking delay when switching Guest and Host,Linux,VirtualBox 5.1.4,2016-11-22T14:35:14Z,2016-11-22T14:35:14Z,2016-11-22T14:35:14Z,"I have a Ubuntu16.04 Desktop guest on my Windows 7 Host. My VirtualBox version is Version 5.1.4 r110228 (Qt5.5.1) and VirtualBox additions installed on the guest. 

When I switch between my guest window and any other window in the host, everything blocks for 1-2 seconds. It is annoying since when I change the context and type something, the text gets lost and need to re-type again.

Log attached. ",jlausuch
15888,VirtualBox 5.1.0 - 5.1.4 Guest Additions problem in Windows XP Guest,Windows,VirtualBox 5.1.4,2016-09-05T14:35:16Z,2016-10-29T16:35:03Z,2016-10-29T16:35:03Z,"
Host: Windows 8.1  Pro 64 bit, Intel Core i7-4770K, 16 GB RAM 

Guest: Windows XP SP3, 512 MB RAM, all other settings default.


Problem with guest additions in Windows XP


The guest additions worked properly in VirtualBox 5.0.24 and earlier. In all 5.1 versions (5.1.0 - 5.1.4) the following problems are observed: 

•the guest additions icon does not appear in the system tray;  


•seamless mode is disabled and does not switch; 


•mouse wheel does not response.



I also noticed that VBoxTray process gets started but then terminates in approximately a minute after the start and guest additions icon never appears.


This problem pertains in my virtual machine with Windows XP what I used continuously with Virtual Box 5.0.24 without any problems. 


Other guest OS including Windows 7, 8.1 and 10 do not have this problem.

",batyrulan
15901,Copyig files over USB hangs with USB 3 support,Linux,VirtualBox 5.1.4,2016-09-08T05:40:42Z,2016-10-28T13:16:58Z,2016-10-28T13:16:58Z,"Windows 7 host. 

I copied files from my Kubuntu 16.04.1 to an external tablet via adb push. 

The file I copied is roughly 600 MB. The file takes about 3 minutes to copy from Windows, in VirtualBox Linux Guest the file is still stuck copying after 12 hours. 

I started experiencing this problem since USB 3 support was introduced with VirtualBox 5.0. I do not have this problem with USB 2 enabled. 

My USB port is the following:
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller

I had the problem driver version 1.0.4.225 then upgraded to 1.0.10.255, but had the same problem. 

The external device I am copying to is a Texas Instrument Blaze Tablet. 
",nopaste
15838,download extension pack dialog displayed over upgrade extension pack dialog,other,VirtualBox 5.1.4,2016-08-21T12:46:55Z,2016-10-19T20:55:59Z,2016-10-19T20:55:59Z,"Under Win7, i just upgraded from VB 5.0.26 to 5.1.4, without opening VBox after the installation. After the upgrade was completed, i went on the 5.1.4 Extension Pack i had just downloaded, and double-clicked on it. The VBox GUI window was opened. Over it, an info dialog was displayed, saying that an older Extensions version is installed and asking if i wish to upgrade it. Over this dialog, another dialog appeared, informing me that a newer Extensions version exists and asking if i wish to download it. The last dialog was pointless since i was already trying to upgrade the Extensions Pack.",Wand
15814,Virtualbox closes unexpectedly.,Linux,VirtualBox 5.1.4,2016-08-17T23:18:11Z,2016-09-27T12:55:22Z,2016-09-27T12:55:22Z,"100% reproducible on my x86 Win7 host. Open attached VM, then ''vm settings -> Storage -> select any controller -> click on the blue thingy (add new stor. controller) on the window's bottom -> choose optical drive or hard disk''. After that the whole vbox gui closes.",tico-tico
15903,Media not released after a snapshot revert,all,VirtualBox 5.1.4,2016-09-08T07:03:46Z,2016-09-26T07:45:19Z,2016-09-26T07:45:19Z,"If you revert to a snapshot where some media was not attached, it doesn't get released. The way to reproduce:[[BR]]
1) Create a snapshot without any media attached[[BR]]
2) Attach an iso image to the VM [[BR]]
3) Revert to a snapshot[[BR]]
4) The VM doesn't have the iso attached anymore (as expected). But in the ""Virtual media manager"" this iso is still shown as attached and ""release"" of the iso doesn't work.

If you kill VBoxSVC and start ""Virtual media manager"" again, then the iso is shown as ""not attached"" and can be released without problem.",mskov
15915,Image removed by snapshot restore still shown as attached in media manager,all,VirtualBox 5.1.4,2016-09-10T10:14:16Z,2016-09-23T19:04:43Z,2016-09-23T19:04:43Z,"Longstanding bug:

Steps to reproduce:
* select a VM with an empty virtual optical drive,
* create a snapshot of this VM,
* attach some new ISO image to the optical drive,
* restore the snapshot (do not create one for current state),
* check ""Attached to"" status of ISO image in virtual media manager.

Observed:
ISO image is still reported as ""Attached to: ''Name_of_VM''"". As a consequence, ""Remove"" button is disabled.

Expected:
ISO image should be reported as ""''Not Attached''"".

Workaround:
Re-add ISO image, and then remove it manually before restoring the snapshot.
",chrfranke
15898,Add Shared Folder - pasting folder path causes VBox Manager to crash - until navigated to.,all,VirtualBox 5.1.4,2016-09-07T10:29:17Z,2016-09-15T14:13:50Z,2016-09-15T14:13:50Z,"{{{
VirtualBox Manager version 5.1.4.
Windows 10.
}}}

(Up to this time I have never tried to add a Shared Folder. Ie no 
VM has one, and I've never attempted to configure one.)

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Paste a folder path into the Folder Path entry box.
select OK.
VirtualBox Manager crashes.
}}}

This crash was completely repeatable until I approached the task in 
a different way.

{{{
Select a VM.
Select Settings.
Select Shared Folders.
Select '+' to add a new shared folder.
Select the drop-down arrow in the Folder Path entry box.
Navigate to the folder I want to add.
Select it.
Select 'Select Folder'.
All works fine.
}}}

After doing the task once this way it now works entirely 
satisfactorily doing it the first way, ie by pasting in a 
folder name.

So, not as serious a fault as I first thought but smells to 
me like something not initialized if one hits some code first 
by pasting the folder name rather than by navigating to it.

[[br]]
I have reported this on the forum and been advised that it is 
a Qt5 library issue and that I should report it here.

I have no unusual storage devices, it's a conventional Windows
desktop computer.  There is no Bluetooth.
[[br]]
The crash occurred for all the VMs that I tried.  Most are
Windows guests, one is Linux.
[[br]]
Once it works it continues to work.

",Richard Kerry
15876,Some modern application show corrupted graphic in 3D accelerated mode,Linux,VirtualBox 5.1.4,2016-09-02T07:37:41Z,2016-09-14T14:35:37Z,2016-09-14T14:35:37Z,"On an Ubuntu 16.04 guest running in a Windows 7even host some application show complete corrupted graphic (only some black and white random pattern)
Affected application

1) Chrome and Chromium with acceleration enabled
2) Skype for Linux beta (new version)
3) Ubuntu Amazon app

The VB log gets filled by these warnings:

{{{

0:00:59.077839 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.082506 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.116003 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.128856 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.160880 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
00:00:59.193186 OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty.  Currently, this is not supported.
}}}


Several users report the problem with different graphic cards, confirmed with Intel HD graphics and Geforce GTX 980 Ti.
Link to forum thread: [https://forums.virtualbox.org/viewtopic.php?f=3&t=77349]",Menion
15893,Differencing disk for shared immutable disk saved to wrong VM settings file,Windows,VirtualBox 5.1.4,2016-09-06T15:03:25Z,2016-09-06T15:07:30Z,2016-09-06T15:07:30Z,"Sharing an immutable drive across two VMs causes VirtualBox to save the differencing disk configuration in the wrong VM's configuration file. This is causing my scripts to fail when they search for the differencing disk UUID in the configuration.

After creating both VM's, the following appears in VM1's configuration file:

{{{
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{c1487c8e-ab83-41ca-8efa-92e14b36c4dc}"" location=""E:/Golden Images/W2K12.vhd"" format=""VHD"" type=""Immutable"">
          <HardDisk uuid=""{a721fb7e-9bae-4347-9e32-f6e73fab310e}"" location=""Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" format=""VHD""/>
          <HardDisk uuid=""{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}"" location=""E:/Machines/VM2/Snapshots/{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}.vhd"" format=""VHD"" autoReset=""true""/>
        </HardDisk>
      </HardDisks>
    </MediaRegistry>
}}}

No MediaRegistry exists in VM2's configuration file. I expected to see a MediaRegistry in both configuration files, each containing only their specific VM's differencing disk.

I can reproduce the issue with the following commands. To create VM1:
{{{
VBoxManage.exe createvm --name VM1 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM1 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM1 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM1 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM1 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM1 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
VBoxManage.exe modifyhd ""E:\Golden Images\Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" --autoreset off
VBoxManage.exe modifyvm VM1 --nic1 hostonly --hostonlyadapter1 ""VirtualBox Host-Only Ethernet Adapter""
}}}

To create VM 2:
{{{
VBoxManage.exe createvm --name VM2 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM2 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM2 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM2 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM2 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
# This line is redundant, but executed by my scripts to ensure the shared disk is immutable.
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM2 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
}}}

I apologize if this is simply because I'm not using the command line interface correctly.",Joshua Rehm
15883,Slashes are not converted to underscores when a VM is part of a group,all,VirtualBox 5.1.4,2016-09-03T17:45:45Z,2016-09-03T17:45:45Z,2016-09-03T17:45:45Z,"Before placing my VMs into groups, I had no trouble naming my VMs as ""FreeBSD/amd64 stable/10 ZFS"". The XML file was magically saved as ""FreeBSD_amd64 stable_10 ZFS.vbox"" upon initial creation. I was happy, and VBox was happy. I could change the configuration of my VMs; the VMs would still have names like ""FreeBSD/amd64 stable/10 ZFS"", and the XML file would still be named ""FreeBSD_amd64 stable_10 ZFS.vbox"".

Enter the use of groups. Shock and horror ensues!

I can no longer give my VMs names such as ""FreeBSD/amd64 stable/11 BIOS ZFS"". Somehow the magic sanitation of file names is put aside.

Here's an example of a VM currently named ""FreeBSD_amd64 stable_11 BIOS ZFS"", and as appropriate, the XML file is named ""FreeBSD_amd64 stable_11 BIOS ZFS.vbox"". Everyone are happy, except me.

Now, I attempt to change the name of the VM from ""FreeBSD_amd64 stable_11 BIOS ZFS"" to ""FreeBSD/amd64 stable/11 BIOS ZFS"".

VBox makes noises such as ""Failed to save the setting of the virtual machine FreeBSD/amd64 stable/11 BIOS ZFS to D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD_amd64 stable_11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox"".

Details: Could not rename the settings file 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD_amd64 stable_11 BIOS ZFS.vbox' to 'D:\Users\trond\Documents\VirtualBox VMs\FreeBSD\FreeBSD\amd64 stable\11 BIOS ZFS\FreeBSD/amd64 stable/11 BIOS ZFS.vbox' (VERR_PATH_NOT_FOUND).[[BR]]
Result Code: E_FAIL (0x80004005)[[BR]]
Component: SessionMachine[[BR]]
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

Had I refrained from creating groups, none of the above would have happened, and I would not be the one who created this bug report.

A workaround is to stop the VBox GUI, manually edit the XML file, give the VM whatever name I desire, and launch the GUI once more. In the long run, this is not acceptable.",trondfsi
15882,Installer for VBox 5.1.4 doesn't honor non C: locations when creating shortcut,other,VirtualBox 5.1.4,2016-09-03T17:18:27Z,2016-09-03T17:18:27Z,2016-09-03T17:18:27Z,"I install VirtualBox in G:\Program Files\Oracle\VirtualBox, not in the usual location, C:\Program Files\Oracle\VirtualBox. The ""Oracle VM VirtualBox"" shortcut is created to point to the nonexisting C:\Program Files\Oracle\VirtualBox\VirtualBox.exe, not G:\Program Files\Oracle\VirtualBox\VirtualBox.exe as I would prefer. This is new to 5.1.4. Manual intervention is required after installation. Note, this happened when upgrading from 5.1.2. Maybe the bug doesn't happen on a clean install.",trondfsi
15878,LastNormalWindowPosition isn't correctly saved for a maximized window,all,VirtualBox 5.1.4,2016-09-02T18:10:59Z,2016-09-02T18:17:50Z,2016-09-02T18:17:50Z,"Up to VirtualBox 5.1.0 (don't know about 5.1.2), the LastNormalWindowPosition that was saved for a maximized window would contain the coordinates of the window prior to maximization. That is not the case anymore with VirtualBox 5.1.4. 

The way to reproduce:
1) start a vm with guest additions, wait for it to boot
2) resize the window. Let the guest resize as well
3) maximize the window. Let the guest maximize as well
4) save the machine state
5) start the machine from the saved state. It shoule start maximized
6) ""unmaximize"" the window. Expected behavior: window is resized to the same 
size as was in (2). But that doesn't happen (window stays full-screen size, but not maximized anymore).",mskov
15857,Defect: 5.1.4 Shared Folders not showing in Ubuntu Linux Guest from  Win7 Host,Linux,VirtualBox 5.1.4,2016-08-27T07:12:42Z,2016-09-01T13:37:14Z,2016-09-01T13:37:14Z,"After creating a share folder in Ubuntu 16 Guest,
  we cannot see it in Media

2) Same for bi-directionnal copy/paste not working.

",brook245
15864,Windows Host not start with virtualbox 5.1.4,Windows,VirtualBox 5.1.4,2016-08-30T07:20:21Z,2016-09-01T12:10:44Z,2016-09-01T12:10:44Z,"Hi, I have updated to version 5.1.4-110228 but the windows xp host crashes on startup. I attach the logs. The pc has windows 10 pro",Sergio
15870,Parallel port passthrough support - bug in I/O resource scanning,all,VirtualBox 5.1.4,2016-08-30T22:41:16Z,2016-08-30T22:41:16Z,2016-08-30T22:41:16Z,"English is not my mother tongue; please excuse any errors on my part.

In certain circumstances, Virtualbox is unable to detect correct base I/O address of a parallel port. This happens when the parallel port is an add-on card (PCI, PCIe, ExpressCard). The device driver consists of two parts: bus enumerator and the parallel port itself. The first device has assigned all I/O and IRQ, while the LPT port has no resources at all.

There are two functions involved:

drvHostParallelGetWinHostIoPorts(PDRVHOSTPARALLEL pThis)

and

drvHostParallelGetWinHostIoPortsSub(const DEVINST DevInst)

The second function looks for a device and enumerates its I/O resources. As the LPT port lacks of any resources, the function fails. The caller then fails silently, there is no evidence in log files that the passthrough is defunct.

I don't have VS2010 and I cannot make a build environment to test my changes to the code. If I could only create a build environment, I would attempt to make a workaround to let user specify LPT's I/O base (IRQ is not important),
or fix it to make it list bus enumerators and query them for their I/O addresses.",lelekx
15843,"Repeated crashes with ""The memory could not be read""",Windows,VirtualBox 5.1.4,2016-08-22T09:34:26Z,2016-08-25T20:08:49Z,2016-08-25T20:08:49Z,"Virtual Box used to work fine but since I upgraded to 5.1.0 I'm experiencing crashes of the guest system several times a day and I can't see a pattern.
Every time a new version got released I immediately upgraded my system but the crashes still occur.",schnesim
15836,Windows 10 Start button causes taskbar to disappear in Seamless Mode,Windows,VirtualBox 5.1.4,2016-08-20T16:32:42Z,2016-08-20T16:32:42Z,2016-08-20T16:32:42Z,"I have just installed VBox 5.1.4 Windows 10 64 bit Host, Windows 10 64 bit guest.

Prior to the latest update seamless mode did not work at all with Windows 10 guests as reported by others.
https://forums.virtualbox.org/viewtopic.php?f=2&t=78179

After installing 5.1.4 seamless mode appears to work in that entering seamless mode the taskbar appears as expected and the bottom of the screen, and open windows, or windows opened from the taskbar appear to behave properly.

However left clicking on the start button to open the start menu causes the taskbar to disappear, although the user interface bar remains visible. The start menu appears in the preview window of the Virtual Box manager, but not on the desktop. Closing the start menu (insert Ctrl-Alt-Del and start task manager) causes the taskbar to reappear. 

The same behaviour occurs in a 32bit Windows 10 guest. Host Display is 1920x1200

VBox and VBoxHardening Logs attached.  ",wisty
15819,Videos doesn't work,Linux,VirtualBox 5.1.4,2016-08-18T13:16:42Z,2016-08-18T13:16:42Z,2016-08-18T13:16:42Z,"Videos using players(SMPLAY), and video from internet aren't working on VB 5.1.4 and his guest additions.
Sometimes video on internet is running without audio.",Matipare
15812,Human Interface devices are not detected by the Virtual machine,Windows,VirtualBox 5.1.4,2016-08-17T16:25:59Z,2016-08-17T16:53:34Z,2016-08-17T16:53:34Z,"When I connect a Human interface device to my Windows 7 PC it is detected.  When I try to connect it to my Virtual Box machine, it is not detected.  An error appears when I try to pick in the Device menu - Unknown device.
It used to work when the USB settings were set to 2.0 on VB version 5.0.24
I have attached 2 images.
One from my working Win7 PC and one from the Win7 VB that does not work.",skh
16032,VirtualBox not compatible with USBPcap and similar,all,VirtualBox 5.1.6,2016-10-05T12:38:38Z,2019-09-12T00:10:55Z,2019-09-12T00:10:55Z,"Hello,

* Issue:

current versions of VirtualBox are not compatible with USBPcap on Windows (e.g. Windows 8.1 or Windows 10).

* Description

USBPcap provides USB traffic recording functionality by injecting itself into the USB stack (see http://desowin.org/usbpcap/block_diagram.html) in a way currently incompatible with the way VirtualBox does something similar.

* Experienced behavior

Host USB device is unavailable (""busy"") for attachment to Virtual Machine with USBPcap installed and active. USBPcap can be installed as (optional but default) component of WireShark.

* Expected behavior

VirtualBox forwards the USB device in a defined manner, i.e. either with all USB traffic happening inside the VM visible to USBPcap, or with all USB traffic inside the VM circumventing USBPcap

* Why shouldn't this be fixed by USBPcap?

There are multiple software packages providing similar or identical USB sniffing capability in a similar or near identical functionality, addressing this in all of them with special code instead of handling this properly at the virtualization layer (already deeply involving itself with the system) seems odd.",berlincount
16097,3D acceleration no work on Win10 With Intel HD3000,Windows,VirtualBox 5.1.6,2016-10-20T23:59:02Z,2018-12-09T21:21:14Z,2018-12-09T21:21:14Z,"When open a software use 3D like OpenGL or DirectX on guest OS, It go stuck.(even dxdiag.exe)
Host OS is Windows 10 with Intel HD3000 Graphic.
This is a topic from forum following this problem: https://forums.virtualbox.org/viewtopic.php?f=6&t=79820",Yanfeng
15986,Shared clipboard is not working in headless mode,all,VirtualBox 5.1.6,2016-09-25T13:51:34Z,2018-11-13T09:07:10Z,2018-11-13T09:07:10Z,"I've found plenty similar tickets about this issue but they all are related to obsolete versions so I created this one.[[BR]]

Several tickets ([https://www.virtualbox.org/ticket/14964 14964], [https://www.virtualbox.org/ticket/14645 14645] and [https://www.virtualbox.org/ticket/14421 14421]) are ''likely'' to be the same (I don't know this for sure) but there was no mention about headless mode  or VRDP and my tests clearly say this is headless-only bug.
The most appropriate '''recent''' tickets I found were [https://www.virtualbox.org/ticket/11397 11937] and [https://www.virtualbox.org/ticket/10057 10057] (which are still open), but there are much-much older ones ([https://www.virtualbox.org/ticket/11140 11140], [https://www.virtualbox.org/ticket/3794 3794])[[BR]]

I decided to create my own as I don't know exactly is my issue related to any of them so it's up to admins to merge them or leave them as is.[[BR]]

All in all, my bug comprises several symptoms:
1. shared clipboard does not work guest2host direction on Windows and Linux guest.
2. shared clipboard does not work inside Windows guest at all (in Linux guest does)
3. All this is observed only in headless mode (guest is accessed via VRDP).

Host2guest direction works good.
In GUI mode both directions work wonderful.",Suncatcher
15975,VBoxManage always shows host only interfaces as disabled,Linux,VirtualBox 5.1.6,2016-09-22T22:41:20Z,2017-05-29T14:22:50Z,2017-05-29T14:22:50Z,"VBoxManage list --long hostonlyifs

always shows DHCP disabled, even for an enabled, and functioning NIC.",silvermangb
16066,The instruction at 0x... referenced memory at 0x.... The memory could not be read.,Windows,VirtualBox 5.1.6,2016-10-13T08:53:31Z,2017-03-03T18:22:55Z,2017-03-03T18:22:55Z,"Hello, after some weeks ago my virtual machine start crashing many times per day with error:

'''The instruction at 0x00007FFCCB3949F9 referenced memory at 0x0000000001C9196C. The memory could not be read.'''

It happened in old and new version too. As host I use Windows 10 with '''Anniversary update'''. '''Probably problems come after this update'''. Guest operating system is Windows Server 2012 R2.

I tried to create mini dump via instructions on link https://www.virtualbox.org/wiki/Core_dump but it is not working in Windows 10 Anniversary update. I did it via Process Explorer.

Attached Dumps.zip file contains mini dumps from all processes in process tree of problematic VirtualBox.exe process:

{{{
- VBoxSVC.exe (VBoxSVC_Mini.dmp)
  - VirtualBox.exe (VirtualBox1_Mini.dmp)
    - VirtualBox.exe (VirtualBox2_Mini.dmp)
      - VirtualBox.exe (VirtualBox3_Mini.dmp - VM process)
}}}

Thanks for any suggestion/help.",Paul B.
15970,Failed to create the host-only adapter (Windows 7),all,VirtualBox 5.1.6,2016-09-22T13:15:27Z,2017-01-19T21:35:50Z,2017-01-19T21:35:50Z,"I cannot create host-only adapter neither with the command 
{{{
VBoxManage.exe hostonlyif create
}}}
nor from UI. I get error:

{{{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not operate the communication channel (VERR_BROKEN_PIPE)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component VirtualBoxWrap, interface IVirtualBox
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}

When I try to do it from UI I get error message with the text:
{{{
Failed to create the host network interface.

Could not operate the communication channel (VERR_BROKEN_PIPE).

Result Code: E_FAIL (0x80004005)
Component: VirtualBoxWrap
Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
}}}

This doesn't allow me to use Docker so it is blocker for me.

It is reproducable with older 5.0.* versions too. I tried to reinstall VirtualBox, install with ""-msiparams NETWORKTYPE=NDIS5"" parameter, reset driver cache in ""windir%\inf\INFCACHE.1"" without any result.

After error there is new ""Unknown Device"" in Windows Device Manager.

Lines added to setupapi.app.log after failure:
{{{
>>>  [Build Driver List - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:22.977
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
     cpy: Policy is set to make all digital signatures equal.
!    sig: No installed catalogs matching catalog name '' were found that validated the file.
!    sig: Error 1168: Element not found.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x00000057)
!    sig: Error 87: The parameter is incorrect.
!    sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003)
!    sig: Error 0x80092003: An error occurred while reading or writing to a file.
<<<  Section end 2016/09/22 16:00:23.698
<<<  [Exit status: SUCCESS]


>>>  [DIF_REGISTERDEVICE - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.761
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.763
<<<  [Exit status: SUCCESS]


>>>  [DIF_ALLOW_INSTALL - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.763
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.765
<<<  [Exit status: SUCCESS (DI_DO_DEFAULT)]


>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.765
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<ins>
}}}

also (which looks weird) some lines are added to section dated 2015/09/23:
{{{
>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2015/09/23 20:02:36.865
...
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     dvi: Committing file queue...
     flq: CopyFile: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\Temp\OLD1D54.tmp'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_neutral_978f7ab983bb20bd\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq: MoveFile: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq:       to: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
}}}


Please let me know what information may I provide to help to fix this defect or find some workaround.

OS: Windows 7, 64bit, SP1.

I have Aventail VPN installed but it is inactive when I reproduce the problem. 
",Dron007
16096,"with a socks proxy set in gnome, guest OS randomly freeze black screen",Linux,VirtualBox 5.1.6,2016-10-20T19:42:29Z,2016-10-21T06:22:48Z,2016-10-21T06:22:48Z,"Description of problem:
when a socks proxy is set in gnome, in the guets OS, gnome freezes black screen, randomly without halting the system

Version-Release number of selected component (if applicable):
VitualBox 5.1.6 on Windows7 SP1 64
Fedora 24 4.7.6-200.fc24.x86_64
Gnome ver 3.20.4

Please note:
I'm using VitualBox 5.1.6 on Windows7 SP1 64.
I'm inside a VirtualBox VM where Fedora 24 is my Guest OS.
I installed the VirtualBox Guest Additions ver 5.1.7-110797
I configured the KVM acceleration.
I configured the VM network to Bridged Adapter.
I'm using Snort in Fedora. 

How reproducible:
happens randomly 

Steps to Reproduce:
1. Configure a socks proxy in NetworkManager, in the guest OS

Actual results:
Randomly the screen freeze blank, although the system appears not halted but it is not possible to interact with it


Expected results:


Additional info:
unset the sock proxy all run normally",par7133_2
15946,"When upgrading virtualbox, icon is removed from the taskbar and unnecessary desktop shortcut created.",all,VirtualBox 5.1.6,2016-09-16T19:13:50Z,2016-10-19T20:26:39Z,2016-10-19T20:26:39Z,"OS: Windows 10 64-bit, version 1607, build 14393.105.

VirtualBox Version: Both 5.1.4 and 5.1.6.

When upgrading virtualbox, the icon for virtualbox is removed from it's pinned location on the windows taskbar, and a new icon was added to the desktop.

I normally have desktop icons set to not display, but noticed this errata when going through ""This PC"" -> ""Desktop""
",Samuel Flint
16065,Cannot create symlink inside shared folder on Windows host,Linux,VirtualBox 5.1.6,2016-10-12T20:59:18Z,2016-10-18T22:37:51Z,2016-10-18T22:37:51Z,"Symlinks do not work inside a VirtualBox Shared Folder when running on Windows 10 host with a Linux guest (Fedora 24)


{{{
$ mount  | grep vboxsf
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)
home_vagrant_sync on /home/vagrant/sync type vboxsf (rw,nodev,relatime)

$ pwd
/home/vagrant/sync
$ mkdir a
$ ln -s a b
ln: failed to create symbolic link 'b': Protocol error
}}}

Outside shared folder:

{{{
$ cd ..
$ pwd
/home/vagrant
$ mkdir c
$ ln -s c d
$ ls -ld d
lrwxrwxrwx 1 vagrant vagrant 1 Oct 12 20:51 d -> c
}}}

Environment:

{{{
$ uname -a
Linux guest 4.5.7-300.fc24.x86_64 #1 SMP Wed Jun 8 18:12:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ VBoxClient --version
5.1.6r110634

>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" --version
5.1.6r110634
}}}
",g_tirloni
15990,VirtualBox 5.x CLI cannot display snapshot list while VM is running,Linux,VirtualBox 5.1.6,2016-09-26T19:07:28Z,2016-10-11T12:04:53Z,2016-10-11T12:04:53Z,"The following command produces an error when executed while the targeted VM is running:

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe snapshot MyLinuxVM list
}}}

The error is as follows:
{{{
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LockMachine(a->session, LockType_Shared)"" at line 331 of file VBoxManageSnapshot.cpp
}}}

If the command is executed while the VM is stopped (either suspended or powered off) the command is successful.  I do not have any trouble creating snapshots with VBoxManage while the VM is running.

I had this problem in a previous version (5.0.x) and again when I updated to the latest version (5.1.6).",TastyWheat
16003,"Remove the ""Start after installation"" option from Windows installer",other,VirtualBox 5.1.6,2016-09-29T07:16:21Z,2016-10-07T15:30:29Z,2016-10-07T15:30:29Z,"It is becoming increasingly clearer that with Windows installers you have to install !VirtualBox with the ""Run as Administrator"" option after right-clicking on the installer. It is the only way to make sure that the drivers are installed as they should and are not rejected (silently sometimes) by Windows and UAC.

The problem is that if a simple user uses that tool, at the end of the installation when the installer offers to launch !VirtualBox, then !VirtualBox runs under the context not of the user that did the installation, but under the Administrator context. So if a user starts immediately to use !VirtualBox and creates a new VM, that VM won't be there next time the user re-launches !VirtualBox. It's going to be in the Administrator's account!

Solution: remove the ""Start after installation"" option at the end of the installation. The installer finishes and the user launches !VirtualBox under their own user context, as they would do it normally every other day.

PS. It doesn't have to be a simple user, driver installation fails sometimes even with an administrator user, so the ""Run as Administrator"" is becoming mandatory. Simply in that case the issue does not manifest itself.",Socratis
16036,supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED,other,VirtualBox 5.1.6,2016-10-05T18:56:56Z,2016-10-06T12:09:17Z,2016-10-06T12:09:17Z,"Hi, I have downloaded VirtualBox Versión 5.1.6 r110634 (Qt5.5.1) and installed on Windows 10. 

So, I created a new VM, but at start moment, this message appears:

supHardenedWinVerifyProcess failed with VERR_SUP_VP_REPLACE_VIRTUAL_MEMORY_FAILED: (rc=-5673)

Have you any solution?

Thanks.",Facundo
16033,Cannot attach hard drive to VM on 32-bit Windows 7,other,VirtualBox 5.1.6,2016-10-05T13:07:09Z,2016-10-06T10:41:49Z,2016-10-06T10:41:49Z,"In VirtualBox 5.1 it is not possible to attach a hard drive to a newly created VM on 32-bit Windows systems (tested with Win7x86).

Steps to reproduce the problem:

- Create a new virtual machine **without** a hard drive.
- Try to attach a hard drive to the SATA-Controller. Attaching the hard drive doesn't succeed because VirtualBox crashes.",ckossmann
16026,"error reuse physical disk after open ""computer management"" console",Windows,VirtualBox 5.1.6,2016-10-04T16:38:21Z,2016-10-06T09:28:24Z,2016-10-06T09:28:24Z,"If I open ""computer management"" console (in Win 7x64 host), to use the physical disk becomes impossible (io error, write error etc.), guest system becomes unbootable. 
Also to install guest, had to remove pre-existing disk partition. Only then became possible to format it from the guest system.

Is it possible to make a mapped physical drive does not fall off when restart host system?

I used the following command:

cd C:\Program Files\Oracle\VirtualBox

VBoxManage.exe internalcommands createrawvmdk -filename H:\VBoxHDTools\ssd7.vmdk -rawdisk \\.\PhysicalDrive5


",Nick07
16017,Only one CPU usable Windows 10 Hyper-V Bug,Linux,VirtualBox 5.1.6,2016-10-03T09:23:28Z,2016-10-03T09:44:02Z,2016-10-03T09:44:02Z,"Suddenly I couldn't select the amount of cpus to offer to a newly created virtual machine. Even old ones had only one cpu and wouldn't start anymore. 

The issue seems to be related to a Hyper-V Installation on Windows 10 Pro. When you Install Hyper-V for some reason Virtual Box will be broken

Reproduce

1. Instll Virtual Box as usual on Windows 10 Pro
2. Create a Machine with more than 1 Processor
3. Now activate the Hyper-V Feature from the System Settings Programms and 
   Features dialog
4. Wait for Windows to complete tehe setup
5. Try to change the amound of cpus used by your virtual machine in Virtualbox 

The Feature should be grayed out now

So Hyper-V seems to break VirtualBox by now!

You can re enable the processor feature by uninstalling the Hyper-V feature in Windows 10 Pro

I am not sure if Windows 7 is also afected. Needs Teting",horvan
16000,Can't start VM,Windows,VirtualBox 5.1.6,2016-09-28T15:43:23Z,2016-09-28T15:47:54Z,2016-09-28T15:47:54Z,Can't start VM due to hardening complaints of Sophos AV,ak11
15997,Auto-resize Guest Display greyed out,Windows,VirtualBox 5.1.6,2016-09-28T11:25:31Z,2016-09-28T11:25:31Z,2016-09-28T11:25:31Z,"I have installed VirtualBox 5.1.6 on a Windows 10 Pro Host. The Guest System is Windows 7 Ultimate. GuestAdditions installed.

Mouse integration and Drag and Drop works fine but Auto-resize Guest Display is greyed out.

Tentatively I have installed the Guest Additions Testbuild.


Stefan",StefanPreuss
15992,"Win10 Host, Ubuntu 16 guest, seamless mode, Multiple Virtual Windows",Linux,VirtualBox 5.1.6,2016-09-27T15:18:30Z,2016-09-27T15:24:41Z,2016-09-27T15:24:41Z,"I'm running a Windows 10 host with an Ubuntu 16.04 virtual machine. I have been running this in seamless mode which worked well earlier. I'm also running ""Multiple Virtual Windows"" (www.actualtools.com) to switch virtual displays on the host.

With the virtual machine in seamless mode, if I switch to another virtual window and then back, the guest doesn't appear to respond. If I click on something I don't see any result, but if I then switch out of seamless mode, I see that the action was in fact taken, just that the display didn't update.

I went back to the Ubuntu 14.04 VM and get the same problem, so it could be a recent update to VirtualBox or something with Multiple Virtual Windows that caused the issue.

",N8DNX
15991,Ethernet connection hangs on guest,Windows,VirtualBox 5.1.6,2016-09-27T08:34:45Z,2016-09-27T11:26:59Z,2016-09-27T11:26:59Z,"Ethernet connection on guest is hanging periodically.
After disconnection/connection back it starts to work again",leonik
15960,Copying of HTML from windows host to Firefox on a Linux guest doesn't work,Linux,VirtualBox 5.1.6,2016-09-20T16:57:31Z,2016-09-26T07:18:07Z,2016-09-26T07:18:07Z,"I don't know if it is a problem of Firefox or of VirtualBox itself. Copy-pasting HTML works perfectly fine to e.g. Chrome and LibreOffice Writer. But for some reason it doesn't work if pasting is done to Firefox. Though if you copy HTML directly from the linux guest (e.g. from Chrome, Firefox or LibreOffice) and paste to Firefox on the same guest - it works fine. I've also tried to examine the content of X11 clipboard in the guest and ""text/html"" target seems to be perfectly fine (when obtained with some tools like xclip). I've also tried to write the exact content of ""text/html"" provided by VirtualBox in the guest to the X11 clipboard (with ""xclip -t text/html -selection clipboard"") - and if I do that, then pasting works fine as well. It would be really great, if you could confirm that the problem is in the way how Firefox reads the content and not in the way how VirtualBox is providing this content to Firefox - then I would create a bug ticket on the Firefox bug tracker instead. 

Thnx in advance if you decide to investigate this issue.",mskov
15979,vertio-net causes Cisco AnyConnect instablity,Windows,VirtualBox 5.1.6,2016-09-23T18:21:10Z,2016-09-23T18:21:10Z,2016-09-23T18:21:10Z,"I have been running a Windows (8.1 and 10) guest for several years, using AnyConnect from the guest to VPN into our corporate network.  At some point I transitioned to using the virtio-net driver and it worked well for a long time.  

At some point a few months ago the VPN became very unstable.  I would experience random disconnects, especially during periods of constant VPN utilization (screen sharing, large file transfers, etc).  

When it disconnected, it would reconnect, but would not configure the ip stack properly and I could not pass any traffic without disconnecting and reconnecting.  I lived with this for several months and decided to finally take some time to see if I could find a solution.

Ultimately, going to a virtualized Intel PRO/1000 MT Desktop adapter seemed to fix the problems.  For some reason it appears that recent versions of AnyConnect stopped working well with the virtio-net adapter.

I don't know if this would be an AnyConnect, a VirtualBox, or a VirtIO-net issue, and will not be offended if this gets closed immediately.  However I wanted to be sure it was documented somewhere for anyone else who may experience these issues in the future.",J. Fry
15974,python host.create_host_only_network_interface returns bad object,Linux,VirtualBox 5.1.6,2016-09-22T22:21:10Z,2016-09-22T22:46:19Z,2016-09-22T22:46:19Z,"vbmanager = virtualbox.Manager()
vbox      = vbmanager.get_virtualbox()
host      = vbox.host   

hoa,progress = p_host.create_host_only_network_interface()
progress.wait_for_completion(32000)

print hoa.name

The print statement generates an error 

Failed to find attribute name in <virtualbox.library.IHostNetworkInterface object at 0x0000000008FB6898>



However, the interface was created.",silvermangb
15968,Crashing VirtualBox,other,VirtualBox 5.1.6,2016-09-22T12:06:37Z,2016-09-22T12:06:37Z,2016-09-22T12:06:37Z,"When I'm trying to open any Virtual machine I'm having error:
""The virtual machine 'Helper' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Games\VirtualBox\Helper\Logs\VBoxHardening.log'.


Код ошибки: 
E_FAIL (0x80004005)
Компонент: 
MachineWrap
Интерфейс: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}""

Log attached.",DenJed
15941,Error occurs trying to add a machine to be fixed.,all,VirtualBox 5.1.6,2016-09-16T09:35:39Z,2016-09-21T23:58:04Z,2016-09-21T23:58:04Z,"An old machine with an old reference to a DVD image cannot be added as the manager incorrectly tries to ""run"" it before actually adding it in, the machine cannot be fixed if its not already in the manager.",Paul17041993
15957,"GUI of guest Fedora 24 4.7.3-200.fc24.x86_64 freeze ""blank"" on login screen",Linux,VirtualBox 5.1.6,2016-09-19T20:22:45Z,2016-09-21T22:39:03Z,2016-09-21T22:39:03Z,"I'm using VirtualBox version 5.1.6 r110634 on Windows with Fedora 24 4.7.3-200.fc24.x86_64 as guest, both updated to the last patch.

I have the last version of the Guest Additions installed.

And I operate the Guest full screen.

The guest GUI freeze on the login, leaving a blank screen, only the background color is visible, forbidding any action with the mouse or keyboard, apparently.

To refresh the GUI after a mouse or keyboard typing I have to click on the toolbar of the host, to restore the Windows screen.

When I switch back to the guest, the guest screen is updated.

After the login screen all comes back to normality.

",par7133_2
15955,"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag and drop error from guest Drag (VERR_FILE_NOT_FOUND)""",Windows,VirtualBox 5.1.6,2016-09-19T06:13:28Z,2016-09-20T11:56:43Z,2016-09-20T11:56:43Z,"Error occurred when the file from the virtual drag and drop to the host, prompt ""Drag  and drop error from guest Drag (VERR_FILE_NOT_FOUND)  VBOX_E_IPRT_ERROR (0x80BB0005)"".
My operating system: win10_1607.",zhaoyao
15943,Wrong hostonlyif mask,all,VirtualBox 5.1.6,2016-09-16T11:14:02Z,2016-09-16T11:14:02Z,2016-09-16T11:14:02Z,"I'm using VirtualBox as a Vagrant provider and when I specify an netmask of 255.255.255.240, the first vagrant up works fine but on subsequent ups a new interface is generated with automatic ip address.

As I explore the source of the issue I find that at vboxmanage list hostonlyifs the interface with the pretended network has a printed netmask of 255.255.255.'''15'''. This is an issue since that in fact, at network interface settings, the actual network mask is the 255.255.255.240.

I'm suspecting that this issue is leading Vagrant to assume that there's no interface for the pretended network and then it creates a new one and setted to the already existing network which cases VirtualBox to change adapter to automatic IP.",nbranco
15930,Settings/Storage crashes VBoxManage (always...on one PC),all,VirtualBox 5.1.6,2016-09-14T11:04:00Z,2016-09-15T16:34:21Z,2016-09-15T16:34:21Z,"Selecting a VM then Settings->Storage crashes VirtualBox Manager.
[[br]]
This happens always on one PC but not at all on another.
Both are running Windows 10.

I note also that having triggered this fault deliberately I am getting
one Application Error at the point of the crash, followed by a number 
of further events relating to this over the following half an hour or 
so.

I am attaching all the Windows Event viewer reports that mention VBox 
Manager, and a zipped copy of all the referenced WER folders.
",Richard Kerry
14269,Error relaunching VirtualBox VM process: 5,Linux,VirtualBox 5.1.8,2015-07-13T18:47:55Z,2020-10-05T21:05:38Z,2020-10-05T21:05:38Z,Unable to run guest VM using latest OVM 5.0 release. See attached screenshot for details.,sombra
16127,Setting up virtual LPT port to connect through to real LPT port stops DOS VM starting,other,VirtualBox 5.1.8,2016-10-29T23:19:37Z,2018-10-28T19:59:43Z,2018-10-28T19:59:43Z,"I run VirtualBox on a Windows 7 Ultimate 64 bit host.
I find that with VirtualBox 5.1.4, 5.1.6 and 5.1.8 and 5.1.9-111573 (with matching Extension Pack installed) my FreeDOS 1.1 VM will not start at all after issuing the following VBoxManage commands:
VBoxManage modifyvm ""FreeDOS 1.1"" --lptmode1 LPT1
VBoxManage modifyvm ""FreeDOS 1.1"" --lpt1 0x378 7
to create a virtual LPT port and connnect it through to my real LPT1 port (on a PCI card, at address I/O address C000)
I am reverting to VirtualBox 5.1.2 for now.
I am attaching the log files and configuration of the VM in a ZIP file.
The oldest log file ""VBox.log.3"" is one from when it last worked, the others are fails.
",Brian Gregory
16192,Virtualbox Windows clipboard integration causes problems copying in Excel,Linux,VirtualBox 5.1.8,2016-11-17T10:28:15Z,2018-09-20T12:28:19Z,2018-09-20T12:28:19Z,"Host: Windows 10 1607 14393.447 (+ all available updates up to mid-November 2016) with Office 2016 (+ all available updates up to mid-November 2016; Excel version 16.0.7466.2038)
VirtualBox: 5.1.8 r111374
Guest VM: Linux Mint

When, and only when, a guest VM is running (but even if the clipboard integration is disabled for that VM) then copying data in Excel 2016 on the host frequently gives the error ""There's a problem with the clipboard, but you can still paste your content within this workbook.""

How to reproduce: run Excel 2016 on the host, and start the guest VM. In Excel 2016 on the host, select a cell with some data, and repeatedly press CTRL+C - roughly 1 in 4 attempts will cause the above error - highly reproducible. With the VM shut down, CTRL+C on Excel on the host will never give this error.

Note that Excel has long been affected by applications that access/lock the clipboard. It seems that MS have recently tried to mitigate, and changed the message in Excel. I suspect it is possible older Excel versions may also be affected, but if so, the error will be slightly different: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_win10/clipboard-problem-in-excel-2016/224b2a59-8a0c-4897-baba-a481dd06e085?page=5


",hakster
16169,after restoring guest XP guest Bugcheck KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e),Windows,VirtualBox 5.1.8,2016-11-08T17:34:50Z,2018-02-08T15:53:58Z,2018-02-08T15:53:58Z,"The guest runs fine, the problem only happens after restoring a saved state.
The Bluescreen appears only in VBox 5.1 (not in version 5.0) for me and only when AMD-V is enabled.

The CPU is AMD Phenom II X4 965[[BR]]
Host OS: Win7 x64[[BR]]
Guest OS: WinXP 32bit I/O APIC enabled / PAE setting has no effect[[BR]]

Here is the Bugcheck: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)[[BR]]
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

Attached are two minidumps of the guest os. The crash is reproducible every time. Please let me know if you need any more information.",oracle_email_with_a_plus_sign
16439,Clipboard add CR character,Linux,VirtualBox 5.1.8,2017-02-01T15:48:36Z,2017-02-01T15:48:36Z,2017-02-01T15:48:36Z,"Hi,
I have problem with the end of line with the clipboard, it appears that virtualbox add a CR (carriage return) character before every LF (line feed). So if I change a file in the guest (linux) that ends already with CRLF, when I paste the result ends with CRCRLF and some program, i.e. pspad, add a blank line.

As example, if in the guest I copy
a
b

becomes in the host
a

b
",ubuguest
16123,"Host: Windows 10 x64, Guest: Debian x64. Host gets unusable, kind of freezes.",Linux,VirtualBox 5.1.8,2016-10-27T08:25:31Z,2016-12-07T09:59:30Z,2016-12-07T09:59:30Z,"Hi,

first my Setup:

Host:
CPU: Intel i7-6700K.
GPU: NVIDIA GeForce GTX 1060, Driver: 372.90.
Windows 10 64-Bit. Avira Antivirus.
VirtualBox 5.1.8

Guest:
Debian 8.6.0 amd64.


Basically most functionality works fine. The VM starts and works like a charm. But after a few minutes of using the Debian-Guest the Host begins to act strange. On the Windows 10 Host i can't start new Windows anymore. The Processes start, as seen in the Task-Manager, but no Windows appear. Already before started Programs in already running Windows are still working perfect, except something like System-Monitor Desktop-Widgets, which are freezing. Even the Start-Menu doesn't show up, if i click on the Windows-Banner. Ctrl+Alt+Del brings me a BlackScreen.
From this Point the VM still works great. But if i try to shut it down, VirtualBox freezes completely.
The only Way to get the Host back working from this Point is the Hard-Reset-Button.
Maybe a compatibility Problem between the Virtualization and the Graphics-Driver. I encountered a similiar Problem some time ago with another Virtualization Solution on another Platform, where it caused the NVIDIA Driver to collapse.",DenKr
16086,VBOX 5.1.8 is crashing,Windows,VirtualBox 5.1.8,2016-10-20T09:58:45Z,2016-11-22T08:17:51Z,2016-11-22T08:17:51Z,"My Windows 10 box upgraded on Monday. I'm running Windows 10 Pro 10.0.14393 Build 14393 x64 now. My vbox did not work after the upgrade, so I downloaded the latest version (5.1.6) and upgraded vbox
Since the upgraded, vbox is crashing. It crashed once on Tuesday, once yesterday, and already 5 times this morning. I've upgraded to 5.1.8 this morning, and disabled Audio, but it crashed again.

Is there something that I can do to prevent this?",Jaques
16203,Windows 10 Pro 64Bit crashes when VirtualBox 5.1 loads,Windows,VirtualBox 5.1.8,2016-11-19T01:12:05Z,2016-11-21T11:04:15Z,2016-11-21T11:04:15Z,"I installed VirtualBox 5.1 successfully 
but when it starts, the computer crashes.
",tonyc49
16187,VirtualBox-Error in suplibOsinit,all,VirtualBox 5.1.8,2016-11-15T12:07:04Z,2016-11-15T12:13:04Z,2016-11-15T12:13:04Z,"In Windows 10 Professional when I like to run any virtual machine I got an error.

Does anybody knows something about this error?",VIrtualtest
16180,windows host crashes when memory is full,Linux,VirtualBox 5.1.8,2016-11-11T14:08:48Z,2016-11-11T15:03:37Z,2016-11-11T15:03:37Z,"I have recently started to get windows BSODs when the guest VMs are trying to allocate too much memory.

I am running Win 8.1 64bit on a laptop with 16GB of RAM, and have 2 VMs open at the same time with 8GB of memory set to each, so there is obviously some over-provisioning going one.
This works fine until some heavy-duty operation starts in one of the VMs. What happens then is:
- windows slows down to a crawl - I can see screen and cursor refreshes
- I can briefly see the 'vm has been suspended because of lack of memory' dialog box popping up
- the win BSOD kicks in

This did not happen until recently (version 5.1.8) at the moment, but it might be simply due to the fact that I was not using intensively 2 VMs with memory over-provisioning before.

The windows event log says:

L’ordinateur a redémarré après une vérification d’erreur. La vérification d’erreur était : 0x0000007e (0xffffffffc0000005, 0xfffff8015d657f50, 0xffffd0005c195d78, 0xffffd0005c195580)

The guest OS is dDebian 8.6

Note that the VM additions inside the VMs might not correspond exactly to the version of VBox running.",gggeek
16173,USB3 Passthrough Fails w/ VLI USB3 Controller,Windows,VirtualBox 5.1.8,2016-11-09T13:38:39Z,2016-11-09T13:38:39Z,2016-11-09T13:38:39Z,"I've been unable to get USB 3.0 or 2.0 devices to attach to VMs on a machine I've added a VLI-based PCIe USB 3.0 card to. It shows up as ""captured"" in the devices menu, but never appears in the VM. The device is also not replaced with the passthrough driver on the host. I've reason to believe this is related to the VLI chipset the card uses as USB 2.0 devices attached to the Intel chipset's USB 2.0 controller work just fine. The same VMs are able to have devices passed through to them properly on a machine that uses Intel's USB 3.0 controller. I've tested this with an external USB 3.0 hard drive (ASMedia controller) and two flash drives. (Sandisk Ultra and a Silicon Power.)",Ziginox
16167,Clipper directory() and shared folders inconsistency,Windows,VirtualBox 5.1.8,2016-11-07T19:56:28Z,2016-11-07T19:56:28Z,2016-11-07T19:56:28Z,"Hi,
I'm using a VM with xp sp3 (home edition) as guest and Win10 Home as host.
Under the VM I develop using the old Ca-clipper compiler: the compiler and the sources, together with the files for testing, are stored on the hd of Win10 and I access them by shared folders on the VM.
When I use CA-Clipper directory() function to get a list of files stored on a shared folder, the return value (directory() returns an array of filenames) is empty, like in the folder there isn't any file.
I investigated deeply and I found that if in the folders there are no more than 8 files the function returns a correct array.
Then I copied all the test shared folder, locally on the hd of the VM, and when I launched the program and tested the directory() function, it runs without any problem and returns all the filenames that are stored on the folder, no matter if they are more then 8, 1000, or more.
To be sure that it's not a Clipper related problem (maybe with shared folders), I tested the program with WMWare. I exported the Virtualbox VM and then imported in WmWare, created the shared folders (like in Virtualbox) and launched the program to read the content of shared folder: in this case there was any problem and the content of the test (shared) folder was returned entirely. So I think the problem is related to VirtualBox.
Regards,
Marco",mark63
16161,Opening a VBOX file from Win Explorer opens a 2nd instance of VirtualBox Manager,all,VirtualBox 5.1.8,2016-11-06T16:56:24Z,2016-11-06T16:56:24Z,2016-11-06T16:56:24Z,"== NOTE: This affects BOTH Win & Linux Hosts ==
Launch !VirtualBox Manager. Double-click (or open) a VBOX file from Windows Explorer/File Manager.
* If the VM is already registered and not running, it will run. Good.
* If the VM is already registered and running, it will get the focus. Good.
* If the VM is not registered, a 2nd instance of !VirtualBox Manager opens up just to register the VM, which also appears on the 1st instance as well. __Not good__.
Especially on Windows, if you couple this, with #14988 it makes things not ... optimal.",Socratis
16157,Windows installer should add VirtualBox path to the PATH environment variable,other,VirtualBox 5.1.8,2016-11-06T09:02:09Z,2016-11-06T09:02:09Z,2016-11-06T09:02:09Z,"I believe the title pretty much covers it, but in detail, installing !VirtualBox on a Windows host should modify the ""PATH"" environment variable to include the !VirtualBox installation directory as well (typically {{{""C:\Program Files\Oracle\VirtualBox""}}}).

Reason? One less step to issue ""VBoxManage"" commands, one less step to make a mistake. Plus, it's already there in the other hosts...",Socratis
16153,Trac detected an internal error.,Windows,VirtualBox 5.1.8,2016-11-05T15:10:30Z,2016-11-05T15:10:30Z,2016-11-05T15:10:30Z,It happened when I was finishing to create my VirtualBox account.,Nelson Sampaio Jr
16151,[5.1.6 & 5.1.8] - Failed to open a session for the virtual machine,Linux,VirtualBox 5.1.8,2016-11-04T17:29:21Z,2016-11-04T17:29:21Z,2016-11-04T17:29:21Z,"I just reinstalled my OS and noticed that none of VirtualBox versions work in my system. I can't launch any machine. Thoughts?

Error details
----
The virtual machine 'Linux' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'G:\Other\VMs\Linux\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

----

VBoxHardening.log

{{{
1030.3bc: Log file opened: 5.1.6r110634 g_hStartupLog=00000000000000e4 g_uNtVerCombined=0xa0383900
1030.3bc: \SystemRoot\System32\ntdll.dll:
1030.3bc:     CreationTime:    2016-11-02T22:03:40.495512200Z
1030.3bc:     LastWriteTime:   2016-10-15T04:47:16.150180800Z
1030.3bc:     ChangeTime:      2016-11-02T22:18:32.862586300Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x1cbe88
1030.3bc:     NT Headers:      0xd8
1030.3bc:     Timestamp:       0x5801a332
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x5801a332
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x1d1000 (1904640)
1030.3bc:     Resource Dir:    0x168000 LB 0x67998
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.351
1030.3bc:     FileVersion:     10.0.14393.351 (rs1_release_inmarket.161014-1755)
1030.3bc:     FileDescription: NT Layer DLL
1030.3bc: \SystemRoot\System32\kernel32.dll:
1030.3bc:     CreationTime:    2016-07-16T11:42:16.155721400Z
1030.3bc:     LastWriteTime:   2016-07-16T11:42:16.155721400Z
1030.3bc:     ChangeTime:      2016-11-02T20:44:02.571188800Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0xaade8
1030.3bc:     NT Headers:      0xf0
1030.3bc:     Timestamp:       0x57899a29
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57899a29
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0xab000 (700416)
1030.3bc:     Resource Dir:    0xa9000 LB 0x528
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.0
1030.3bc:     FileVersion:     10.0.14393.0 (rs1_release.160715-1616)
1030.3bc:     FileDescription: Windows NT BASE API Client DLL
1030.3bc: \SystemRoot\System32\KernelBase.dll:
1030.3bc:     CreationTime:    2016-11-02T22:03:41.375540300Z
1030.3bc:     LastWriteTime:   2016-10-05T10:31:27.772259900Z
1030.3bc:     ChangeTime:      2016-11-02T22:18:30.003207600Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x21c580
1030.3bc:     NT Headers:      0xf8
1030.3bc:     Timestamp:       0x57f4c4f0
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57f4c4f0
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x21d000 (2215936)
1030.3bc:     Resource Dir:    0x201000 LB 0x560
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.321
1030.3bc:     FileVersion:     10.0.14393.321 (rs1_release_inmarket.161004-2338)
1030.3bc:     FileDescription: Windows NT BASE API Client DLL
1030.3bc: \SystemRoot\System32\apisetschema.dll:
1030.3bc:     CreationTime:    2016-07-16T11:42:21.577586000Z
1030.3bc:     LastWriteTime:   2016-07-16T11:42:21.577586000Z
1030.3bc:     ChangeTime:      2016-11-03T05:41:32.804568800Z
1030.3bc:     FileAttributes:  0x20
1030.3bc:     Size:            0x18960
1030.3bc:     NT Headers:      0xc8
1030.3bc:     Timestamp:       0x57899bd2
1030.3bc:     Machine:         0x8664 - amd64
1030.3bc:     Timestamp:       0x57899bd2
1030.3bc:     Image Version:   10.0
1030.3bc:     SizeOfImage:     0x19000 (102400)
1030.3bc:     Resource Dir:    0x18000 LB 0x400
1030.3bc:     ProductName:     Microsoft® Windows® Operating System
1030.3bc:     ProductVersion:  10.0.14393.0
1030.3bc:     FileVersion:     10.0.14393.0 (rs1_release.160715-1616)
1030.3bc:     FileDescription: ApiSet Schema DLL
1030.3bc: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1030.3bc: supR3HardenedWinFindAdversaries: 0x0
1030.3bc: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1030.3bc: Calling main()
1030.3bc: SUPR3HardenedMain: pszProgName=VirtualBox fFlags=0x2
1030.3bc: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1030.3bc: SUPR3HardenedMain: Respawn #1
1030.3bc: System32:  \Device\HarddiskVolume4\Windows\System32
1030.3bc: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1030.3bc: KnownDllPath: C:\Windows\System32
1030.3bc: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
1030.3bc: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe)
1030.3bc: supR3HardNtEnableThreadCreation:
1030.3bc: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffad02a8d60 pvNtTerminateThread=00007ffad02d58b0
1030.3bc: supR3HardenedWinDoReSpawn(1): New child 13d0.8e4 [kernel32].
1030.3bc: supR3HardNtChildGatherData: PebBaseAddress=00000000010af000 cbPeb=0x388
1030.3bc: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffad0230000 uNtDllChildAddr=00007ffad0230000
1030.3bc: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffad02a8d60
1030.3bc: supR3HardenedWinSetupChildInit: Start child.
1030.3bc: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1030.3bc: supR3HardNtChildPurify: Startup delay kludge #1/0: 257 ms, 30 sleeps
1030.3bc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1030.3bc:  *0000000000000000-ffffffffff06ffff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000f90000-0000000000f6ffff 0x0004/0x0004 0x0020000
1030.3bc:  *0000000000fb0000-0000000000f99fff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fc6000-0000000000fbbfff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fd0000-0000000000fcbfff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fd4000-0000000000fc7fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fe0000-0000000000fddfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000000fe2000-0000000000fd3fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000ff0000-0000000000feefff 0x0040/0x0040 0x0020000 !!
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: Freeing exec mem at 0000000000ff0000 (LB 0x1000, 0000000000ff0000 LB 0x1000)
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: Free attempt #1 succeeded: 0x0 [0000000000ff0000/0000000000ff0000 LB 0/0x1000]
1030.3bc: supHardNtVpFreeOrReplacePrivateExecMemory: QVM after free 0: [0000000000000000]/0000000000ff0000 LB 0x10000 s=0x10000 ap=0x0 rp=0x00000000000001
1030.3bc:   0000000000ff1000-0000000000fe1fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000001000000-0000000000f50fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000010af000-00000000010abfff 0x0004/0x0004 0x0020000
1030.3bc:   00000000010b2000-0000000000f63fff 0x0000/0x0004 0x0020000
1030.3bc:  *0000000001200000-0000000001104fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000012fb000-00000000012f7fff 0x0104/0x0004 0x0020000
1030.3bc:   00000000012fe000-00000000012fbfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000001300000-ffffffff8261ffff 0x0001/0x0000 0x0000000
1030.3bc:  *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000
1030.3bc:   000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000
1030.3bc:   000000007fff0000-ffff800a248effff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6db6f0000-00007ff6db6ccfff 0x0002/0x0002 0x0040000
1030.3bc:   00007ff6db713000-00007ff6da8d5fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6dc550000-00007ff6dc550fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc551000-00007ff6dc5bffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c0000-00007ff6dc5c0fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c1000-00007ff6dc605fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc606000-00007ff6dc606fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc607000-00007ff6dc607fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc608000-00007ff6dc60cfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60d000-00007ff6dc60dfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60e000-00007ff6dc60efff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc60f000-00007ff6dc612fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc613000-00007ff6dc65afff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc65b000-00007ff2e8a85fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffad0230000-00007ffad0230fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0231000-00007ffad0337fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0338000-00007ffad037bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad037c000-00007ffad0384fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0385000-00007ffad0392fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0393000-00007ffad0393fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0394000-00007ffad0396fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0397000-00007ffad0400fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0401000-00007ff5a0821fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffffffe0000-00007ffffffcffff 0x0001/0x0002 0x0020000
1030.3bc: VirtualBox.exe: timestamp 0x57d6d53c (rc=VINF_SUCCESS)
1030.3bc: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
1030.3bc: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1030.3bc: supR3HardNtChildPurify: cFixes=1 g_fSupAdversaries=0x80000000
1030.3bc: supR3HardNtChildPurify: Startup delay kludge #1/1: 513 ms, 59 sleeps
1030.3bc: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1030.3bc:  *0000000000000000-ffffffffff06ffff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000f90000-0000000000f6ffff 0x0004/0x0004 0x0020000
1030.3bc:  *0000000000fb0000-0000000000f99fff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fc6000-0000000000fbbfff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fd0000-0000000000fcbfff 0x0002/0x0002 0x0040000
1030.3bc:   0000000000fd4000-0000000000fc7fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000000fe0000-0000000000fddfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000000fe2000-0000000000fc3fff 0x0001/0x0000 0x0000000
1030.3bc:  *0000000001000000-0000000000f50fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000010af000-00000000010abfff 0x0004/0x0004 0x0020000
1030.3bc:   00000000010b2000-0000000000f63fff 0x0000/0x0004 0x0020000
1030.3bc:  *0000000001200000-0000000001104fff 0x0000/0x0004 0x0020000
1030.3bc:   00000000012fb000-00000000012f7fff 0x0104/0x0004 0x0020000
1030.3bc:   00000000012fe000-00000000012fbfff 0x0004/0x0004 0x0020000
1030.3bc:   0000000001300000-ffffffff8261ffff 0x0001/0x0000 0x0000000
1030.3bc:  *000000007ffe0000-000000007ffdefff 0x0002/0x0002 0x0020000
1030.3bc:   000000007ffe1000-000000007ffd1fff 0x0000/0x0002 0x0020000
1030.3bc:   000000007fff0000-ffff800a248effff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6db6f0000-00007ff6db6ccfff 0x0002/0x0002 0x0040000
1030.3bc:   00007ff6db713000-00007ff6da8d5fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ff6dc550000-00007ff6dc550fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc551000-00007ff6dc5bffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c0000-00007ff6dc5c0fff 0x0040/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc5c1000-00007ff6dc605fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc606000-00007ff6dc612fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc613000-00007ff6dc65afff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc:   00007ff6dc65b000-00007ff2e8a85fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffad0230000-00007ffad0230fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0231000-00007ffad0337fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0338000-00007ffad037bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad037c000-00007ffad037ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0380000-00007ffad0384fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0385000-00007ffad0392fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0393000-00007ffad0393fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0394000-00007ffad0396fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0397000-00007ffad0400fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1030.3bc:   00007ffad0401000-00007ff5a0821fff 0x0001/0x0000 0x0000000
1030.3bc:  *00007ffffffe0000-00007ffffffcffff 0x0001/0x0002 0x0020000
1030.3bc: supR3HardNtChildPurify: Done after 852 ms and 1 fixes (loop #1).
13d0.8e4: Log file opened: 5.1.6r110634 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa0383900
13d0.8e4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffad0230000 g_uNtVerCombined=0xa0383900
13d0.8e4: ntdll.dll: timestamp 0x5801a332 (rc=VINF_SUCCESS)
13d0.8e4: New simple heap: #1 0000000001400000 LB 0x400000 (for 1904640 allocation)
1030.3bc: supR3HardNtEnableThreadCreation:
13d0.8e4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
13d0.8e4: System32:  \Device\HarddiskVolume4\Windows\System32
13d0.8e4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
13d0.8e4: KnownDllPath: C:\Windows\System32
13d0.8e4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
13d0.8e4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
13d0.8e4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
13d0.8e4: Registered Dll notification callback with NTDLL.
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
13d0.8e4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Windows\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ffacd5a0000 LB 0x0021d000 C:\Windows\System32\KERNELBASE.dll [fFlags=0x0]
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ffacef80000 LB 0x000ab000 C:\Windows\System32\KERNEL32.DLL [fFlags=0x0]
13d0.8e4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
13d0.8e4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffacef80000 'C:\Windows\System32\KERNEL32.DLL'
13d0.8e4: supR3HardenedDllNotificationCallback: load   00007ff6dc550000 LB 0x0010b000 C:\Program Files\Oracle\VirtualBox\VirtualBox.exe [fFlags=0x0]
13d0.8e4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe' has no imports
13d0.8e4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe)
13d0.8e4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
1030.3bc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 74 ms, CloseEvents);

}}}

",x7370616d
16147,Error in supR3HardenedWinReSpawn (System32\ntdll.dll rc=-626),Linux,VirtualBox 5.1.8,2016-11-04T10:49:21Z,2016-11-04T12:47:38Z,2016-11-04T12:47:38Z,"VirtualBox on my machine is failing to start any virtual machine.  I'm sure the log can explain what's going on better than I can, so I've attached the log.

Thanks for any help you can provide,
skippythegoat",skippythegoat
16140,copy paste is not working,Windows,VirtualBox 5.1.8,2016-11-02T14:05:47Z,2016-11-02T23:29:54Z,2016-11-02T23:29:54Z,"Yesterday I upgraded my version to 5.1.8 and my copy paste stopped working thru out the windows 10 ver 1607 (OS Build 14393.351). This happens when I have bi-directional clipboard sharing enabled. Once I disable this things go back to normal. This is truly a pain as I have to copy and paste all the time for differnt bugs and event or commands all the time. My guest OS is windows 2012 R2 (all the latest patches are applied on host and guest OSs)

Ctrl+C and Ctrl+V as well as right click copy and paste are acting the same I have tried relauncing clip.exe on host and also cleared out the buffer with cmd \c.. commands nothings works until I disable the clipboard sharing",sys janitor
16136,VirtualBox not detecting VMs started on boot,Linux,VirtualBox 5.1.8,2016-11-02T02:04:21Z,2016-11-02T23:26:02Z,2016-11-02T23:26:02Z,"I have a server using Microsoft Windows Server 2012 R2, and a virtual machine on it (Debian).

However, I'd like for the virtual machine to be started on boot, without user log in.

So, I used Task Scheduler for this (also tryied nssm and pstools), but no success.

The virtual machine DOES START, however, when I log in and open VirtualBox,
it does not detect the virtual machine running, so it's quite troublesome as I am not planning on RDP or SSH to the guest.

If I do start the VM with VBoxManage while logged in, all works ok.
If I do start the VM with Task Scheduler (admin nor non-admin) it does not work.

I've also reinstalled VirtualBox and ran it without success.",Hario
16139,Invisible network adapter in network settings,all,VirtualBox 5.1.8,2016-11-02T09:09:45Z,2016-11-02T09:09:45Z,2016-11-02T09:09:45Z,"Host: Windows 7 Pro 64 bit, Intel Core i5-2400, 8 GB RAM

Guest: All

Problem:
On windows hosts not all network adapters are visible in dropdown list. 
On a computer with two onboard NICs and one PCI NIC only one of the onboard NICs and the PCI NIC is shown in the list. The second onboard NIC is missing in the list. VirtualBox NDIS6 Bridged Networking Driver is installed and activated for all three adapters. ",KilO76
16124,Sudden crash of VirtualBox.exe,Linux,VirtualBox 5.1.8,2016-10-27T13:21:29Z,2016-10-29T12:18:35Z,2016-10-29T12:18:35Z,"It happens from time to time that the running Virtual Machine suddenly crashes, without any particular action on the guest system other than using it normally.
For example, last time I was just about to enter a search term into the address bar of the Firefox Browser of my Ubuntu 14.04LTE guest system when it crashed. The moment I clicked on the address bar, VirtualBox crashed. This was only one example of many crashes.

Unfortunately, the appearing error message doesn't say much (see attached screenshot) and from the log file I couldn't find an answer either. It looks like it didn't log anything.
",tacarrie
16104,Build 5.1.8: Cannon view or hear YouTube videos in various guests (or flash based vid),all,VirtualBox 5.1.8,2016-10-22T12:25:54Z,2016-10-28T14:48:15Z,2016-10-28T14:48:15Z,"Host: Win 7 64 pro sp1: Guests: 1) ubuntu 16.04 64, 2) win 10 latest fast ring build 64. 

In either guest with all same working settings as 5.1.6 and before, I can use any available browser (chrome, firefox, or native) , bring up YouTube, choose any video, and it ""might"" show the first frame and hang there, or it might now show a frame. This is true for video & audio.

It will not play a video regardless of any other attempts on my part. I don't see anything about it showing up in logs so for now will hold off on including one. 

It just seems like a regression from the last build.

Notes: Ubuntu won't give me a screenshot that contains anything but the screen background regardless of how I select or take it.

I'm going to attempt to put my ""post-screenshot"" log here at the end:


{{{
00:00:24.411887 VMMDev: Guest Log: VBoxService 5.1.8 r111374 (verbosity: 0) linux.amd64 (Oct 18 2016 15:52:41) release log
00:00:24.411907 VMMDev: Guest Log: 00:00:00.000100 main     Log opened 2016-10-22T12:10:54.019610000Z
00:00:24.411970 VMMDev: Guest Log: 00:00:00.000182 main     OS Product: Linux
00:00:24.412011 VMMDev: Guest Log: 00:00:00.000217 main     OS Release: 4.4.0-45-generic
00:00:24.412049 VMMDev: Guest Log: 00:00:00.000248 main     OS Version: #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016
00:00:24.412088 VMMDev: Guest Log: 00:00:00.000278 main     Executable: /opt/VBoxGuestAdditions-5.1.8/sbin/VBoxService
00:00:24.412122 VMMDev: Guest Log: 00:00:00.000279 main     Process ID: 1053
00:00:24.412126 VMMDev: Guest Log: 00:00:00.000280 main     Package type: LINUX_64BITS_GENERIC
00:00:24.413273 VMMDev: Guest Log: 00:00:00.001226 main     5.1.8 r111374 started. Verbose level = 0
00:00:24.419240 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.419266 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.425031 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.425057 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.425063 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.425067 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.433624 VMMDev: Guest Log: 00:00:00.020413 automount vbsvcAutoMountWorker: Shared folder 'XPDrive' was mounted to '/media/sf_XPDrive'
00:00:24.663061 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:24.663105 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:24.663112 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:24.663116 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:24.678804 VBVA: InfoScreen: [0] @0,0 1592x1029, line 0x18e0, BPP 32, flags 0x1
00:00:24.678851 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.678896 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.678959 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.678974 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.678992 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.680061 Display::handleDisplayResize: uScreenId=0 pvVRAM=0000000010b00000 w=1592 h=1029 bpp=32 cbLine=0x18E0 flags=0x1
00:00:24.680061 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1592x1029, Sending to async-handler
00:00:24.680754 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:24.699300 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1592x1029
00:00:24.699323 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1592x1029
00:00:24.699339 GUI: UIFrameBufferPrivate::performResize: Size=1592x1029, Directly using source bitmap content
00:00:24.699403 GUI: UIMachineView::storeGuestSizeHint: Storing guest-screen size-hint for screen 0 as 1592x1029
00:00:26.240260 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:26.334726 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.649947 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:31.659948 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:34.756490 VMMDev: Guest Additions capability report: (0x0 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
00:00:34.756891 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:34.756935 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:34.756945 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:34.756951 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:36.216479 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.216499 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.216506 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.216515 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:36.262052 OpenGL Info: Render SPU: GL_VENDOR:   NVIDIA Corporation
00:00:36.262087 OpenGL Info: Render SPU: GL_RENDERER: GeForce GTX 650 Ti BOOST/PCIe/SSE2
00:00:36.262097 OpenGL Info: Render SPU: GL_VERSION:  4.5.0 NVIDIA 375.57
00:00:36.262106 OpenGL Info: Render SPU: GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 
00:00:41.700223 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
00:00:41.710224 DSound: Guest source 'Line In' is using host recording device with GUID '{59A1A85D-D99C-484E-82D1-6761B9C037BE}'
}}}

",Papolytic
16100,Win10 graphic adapter driver fails after install 5.1.8+addons,Windows,VirtualBox 5.1.8,2016-10-21T16:05:05Z,2016-10-24T09:17:23Z,2016-10-24T09:17:23Z,"Host: win7, i7 4770, 1440x2560(portrait)[[BR]]
Guest: Win10, use with 1440x2560(portrait)[[BR]]
[[BR]]
When i trying to install 5.1.8 driver i got black screen with task panel at the bottom, few secods after win10 tells me that cant launch screen driver and will use default microsoft driver with 1280x1024 resolution.[[BR]]
VirtualBox Graphics Adapter for Windows 8+ : device is stopped because error №46",adrenalin86
16094,Blue Screen of computer when plugging in USB drive,all,VirtualBox 5.1.8,2016-10-20T15:34:04Z,2016-10-20T15:34:04Z,2016-10-20T15:34:04Z,"If I have any virtual box related program running, whether it is the manager or VM if I plug in a certain USB drive it will blue screen the machine.  The usb drive is an Apricorn Aegis Secure Key: [https://www.cdw.com/shop/products/Apricorn-Aegis-Secure-Key-16-GB-USB-2.0/2544731.aspx?cm_cat=GoogleBase&cm_ite=2544731&cm_pla=NA-NA-APR_DR&cm_ven=acquirgy&ef_id=VoqpAAAAAM2hNEIN:20161020153038:s&gclid=CjwKEAjw1qHABRDU9qaXs4rtiS0SJADNzJiskwfgwH9FOtljO4nsvRtWsa6-g1FSC16RwESXdPa8DhoCVqvw_wcB&s_kwcid=AL!4223!3!61836302419!!!g!18283950120!].  I can get around it by not using the drive when I am using the VM, but if I accidently forget for any reason, it will immediately blue screen my computer as soon as it is plugged in.",jammer2000b
16082,vboxmanage updagega cli crashes guest vboxservice,Windows,VirtualBox 5.1.8,2016-10-19T13:45:50Z,2016-10-19T13:45:50Z,2016-10-19T13:45:50Z,"I am running v5.1.8 along with the latest guest additions. 
My host is windows 8.1 64bit, my guests are a mixture of windows clients (32 and 64 bit) and a mixture of windows servers (32 and 64 bit) and i have the same issue with all of them.

i can start the vms, issue guestcontrol and guestproperty commands and they all run perfectly. However when i use the command:

{{{vboxmanage.exe guestcontrol ""vm name"" updatega}}}

it sits there waiting to talk to my guest vm and then times out with a bunch of errors about not being able to communicate with the vm.

Example errors are
{{{
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={13a11514-402e-022e-6180-c3944de3f9c8} aComponent={GuestWrap} aText={Could not open guest session: VERR_TIMEOUT}, preserve=false aResultDetail=0
ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={13a11514-402e-022e-6180-c3944de3f9c8} aComponent={GuestWrap} aText={Could not open guest session: VERR_NOT_FOUND}, preserve=false aResultDetail=0
}}}
Searching around didnt yield any help and it was only when i looked closely at the guest did i notice that the vBoxService crashed.

I ran the service in the foreground using:

{{{vBoxService.exe -f}}}

and even with verbose does not produce any error in the console window, but does generate the following in the event log:

{{{
Faulting application name: VBoxService.exe, version: 5.1.8.11374, time stamp: 0x5806294f
Faulting module name: VBoxService.exe, version: 5.1.8.11374, time stamp: 0x5806294f
Exception code: 0xc0000005
Fault offset: 0x0004e060
Faulting process id: 0x148
Faulting application start time: 0x01d229ee825251a2
Faulting application path: C:\Windows\System32\VBoxService.exe
Faulting module path: C:\Windows\System32\VBoxService.exe
Report Id: 3496c096-95e2-11e6-b2e6-08002785e35e
}}}


Any help really appreciated to debug and get updating of the guest additions working from the host cli (as it appears a few people are experiencing these issues).



",Southdave
17345,"Display showing at 1/4 size, mouse input area normal (Windows host / Linux guest)",Linux,VirtualBox 5.2.0,2017-12-04T23:01:51Z,2022-06-03T16:02:23Z,2022-06-03T16:02:23Z,"The guest displays over 1/2 x 1/2 (a quarter) of the top left of the total screen area, while the mouse responds over the whole area. If I want to click the system menu in the top right of the screen, for example, I have to click at the top right of the black space, and the menu responds as shown.


This is definitely a HiDPI issue. As you can also see in the picture, the title bar is half the size it should be, the menu bar is twice the size it should be (like the scaling was applied twice), and the icons at the bottom are also twice as large. Scaling is at 200%, so I think the title bar is at 100% and the title bar is at 400%. However, some of this is probably confounded with having a HiDPI and a normal screen on different monitors.

Changing resolution on the guest or scaling on the host doesn't fix the problem; it makes the overall window change as expected but the visible area is still a quarter of the size.

Disabling 3D acceleration fixes the issue, but it just makes everything a whole lot laggier to use as compositing is not available.

I ran into this issue after updating from 5.1.22. Several versions I tried from 5.1.24 to 5.2.2 have the same problem, so I think some change in 5.1.24 broke it.

Related thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=83223 . In that thread someone with an Ubuntu host / Win 8 guest claims to have the same problem.",mizzao
17228,5.2.0 breaks NVMe support on Win10 1703 or later [regression],Windows,VirtualBox 5.2.0,2017-10-31T12:02:02Z,2021-07-05T21:23:28Z,2021-07-05T21:23:28Z,"NVMe drive stopped working in a Win10 1703 VM after upgrading VB from 5.1.18 to 5.2.0.

In Device Manager, stornvme.sys is shown with yellow exclamation and (the German version of) this error message:
''This device cannot start. (Code 10) An invalid parameter was passed to a service or function.''

With an older 1607 snapshot of same VM, NVMe worked again.
After copying stornvme.sys from 1607 to 1703, NVMe worked again.
Same with a fresh install of 1709 (upgrade install crashed VB 5.2.0): NVMe failed and worked again after downgrading the driver.

Test results after downgrading VB to latest 5.1:

||= stornvme.sys       =||= 5.1.18/30 =||= 5.2.0 =||
|| 10.0.14393.0 (1607)  || OK          || OK      ||
|| 10.0.15063.0 (1703)  || OK          || Error   ||
|| 10.0.16299.15 (1709) || OK          || Error   ||

Possibly related or duplicate: #16078.
",chrfranke
17225,Audio distortion/skipping/stutter in Windows 7 Guest,Windows,VirtualBox 5.2.0,2017-10-29T07:02:40Z,2020-11-03T00:15:38Z,2020-11-03T00:15:38Z,"Both my host and guest are Windows 7 Professional.  If I use the HD Audio driver for the guest, the audio lags behind the video a few frames for any streaming video such as news or YouTube.  Also, there is distortion, popping, crackling, skipping, etc. of the audio.  After switching to AC97 ICH in the guest, the LAGGING problem goes away.  However, the distortion persists.

I followed the steps for Audio Debugging in the Wiki.  The WAV file also exhibits some distortion when played on the host, though perhaps not quite as noticeable as the distortion in the guest.  I am attaching the VBox.log file.

Finally, it may be worth noting that NONE of these issues existed for me when I was using VBox version 5.0.26.  Every version of 5.1 I have tried as well as the newest 5.2 has this problem.",LittleJeff1970
17321,Unhandled exception in DirectSound,Windows,VirtualBox 5.2.0,2017-11-28T14:04:43Z,2018-03-18T04:47:20Z,2018-03-18T04:47:20Z,"Vbox crashes when resume a vm on my win 10 host. It happens 90% of time to vm which has audio enabled.

There is a problem with my windows 10. The DirectSound device has a problem(0x88890008, I don't think the meaning of the code is ERROR_NOT_ENOUGH_MEMORY). The error causes any application which uses DirectSound no sound on my win host. The other applications(such as media player, audio player) simply have no sound output. It should not cause the crash though.

A suggestion from me is to check this exception and ignore it(or report to user whichever solution applies to your coding standard). No crash is expected. I knows the issue with DirectSound so I do expect some of applications do not output sound. It is good to have an option to select device from DirectSound or WASAPI. Audio output available when switch to WASAPI in some applications. It's very strange.

If you need more info, I'll attach log files.

The partial log from VBox.log:
{{{
00:00:08.098377 DSound: Starting playback failed with ERROR_NOT_ENOUGH_MEMORY 0x88890008
00:00:08.099284 
00:00:08.099284 !!Assertion Failed!!
00:00:08.099285 Expression: !VMCPU_FF_IS_SET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:08.099285 Location  : F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\PDM.cpp(1006) int __cdecl pdmR3LoadExec(struct VM *,struct SSMHANDLE *,unsigned int,unsigned int)

00:00:08.099404 
00:00:08.099404 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001eb8!!!
00:00:08.099409 
00:00:08.099409 ExceptionCode=0x80000003 ExceptionFlags=0x00000000 ExceptionAddress=00007ffbafc9c395
00:00:08.099413 ExceptionInformation[0]=0000000000000000
00:00:08.099417 
00:00:08.099417 cs:rip=0033:00007ffbafc9c395
00:00:08.099421 ss:rsp=002b:000000000955d3e0 rbp=000000000955d458
00:00:08.099424 rax=0000000000000001 rcx=8aecc971d1340000 rdx=0000000000000000 rbx=00000000084fc000
00:00:08.099428 rsi=000000000955d5e0 rdi=0000000000000000 rsp=000000000955d3e0 rbp=000000000955d458
00:00:08.099432 r8 =7efefefefefefeff r9 =7efefefefefeff52 r10=0000000000000001 r11=8101010101010100
00:00:08.099436 r12=0000000000000000 r13=00000000084e0000 r14=0000000000000005 r15=00007ffbafe53550
00:00:08.099440 ds=002b es=002b fs=0053 gs=002b eflags=00000206
00:00:08.099443 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000084fc000
00:00:08.099447 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:00:08.099450    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:00:08.099453 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:00:08.099457 
00:00:08.099458 Stack 000000000955c360, dumping 0x3ca0 bytes (low=0000000009460000, high=0000000009560000)
00:00:08.099462 000000000955c360 0000: 60 c3 55 09 00 00 00 00-73 74 61 63 6b 6d 61 72 `.U.....stackmar
00:00:08.099465 000000000955c370 0010: 6b 65 72 00 fb 7f 00 00-80 00 00 00 00 00 00 01 ker.............
00:00:08.099467 000000000955c380 0020: 00 f0 59 00 00 00 00 00-40 c5 55 09 00 00 00 00 ..Y.....@.U.....
00:00:08.099468 000000000955c390 0030: 70 c6 55 09 00 00 00 00-30 fa 55 09 00 00 00 00 p.U.....0.U.....
00:00:08.099470 000000000955c3a0 0040: 01 00 00 00 00 00 00 00-70 92 12 97 fb 7f 00 00 ........p.......
00:00:08.099472 000000000955c3b0 0050: 00 00 00 00 00 00 00 00-30 fa 55 09 00 00 00 00 ........0.U.....
00:00:08.099473 000000000955c3c0 0060: 00 00 00 00 00 00 00 00-f0 94 12 e3 fb 7f 00 00 ................
00:00:08.099475 000000000955c3d0 0070: 40 c5 55 09 00 00 00 00-95 c3 c9 af fb 7f 00 00 @.U.............
00:00:08.099476 000000000955c3e0 0080: 00 00 56 09 00 00 00 00-00 00 46 09 00 00 00 00 ..V.......F.....
00:00:08.099478 000000000955c3f0 0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
00:00:08.099479 000000000955c400 00a0: 04 00 00 00 06 00 00 00-00 00 00 00 01 00 00 00 ................
00:00:08.099481 000000000955c410 00b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
00:00:08.099482 000000000955c420 00c0: 00 00 00 00 00 00 00 00-10 16 95 e6 fb 7f 00 00 ................
00:00:08.099484 000000000955c430 00d0: 40 c5 55 09 00 00 00 00-00 c8 55 09 00 00 00 00 @.U.......U.....
00:00:08.099485 000000000955c440 00e0: 38 de c5 cc fb 7f 00 00-b8 ce 55 09 00 00 00 00 8.........U.....
00:00:08.099487 000000000955c450 00f0: fe ff ff ff ff ff ff ff-04 00 00 00 00 00 00 00 ................
00:00:08.099488 000000000955c460 0100: 04 15 24 c0 ec 8a 00 00-5d 5d 06 e6 fb 7f 00 00 ..$.....]]......
00:00:08.099490 000000000955c470 0110: 48 cc 31 07 00 00 00 00-da 20 cc 60 00 00 00 00 H.1...... .`....
00:00:08.099492 000000000955c480 0120: 00 00 00 00 fb 7f 00 00-80 a7 48 03 00 00 00 00 ..........H.....
00:00:08.099493 000000000955c490 0130: b8 ce 55 09 00 00 00 00-b7 f2 97 e6 fb 7f 00 00 ..U.............
}}}",jumperstart
17213,Distorted audio in Windows 10 FCU or Windows 10 Insider Preview (RS4) guest running on Windows 10 FCU (16299.19) host,Windows,VirtualBox 5.2.0,2017-10-26T09:04:16Z,2018-02-13T08:43:00Z,2018-02-13T08:43:00Z,"When I run Windows 10 FCU as well as Windows 10 Insider Preview (RS4) guest on top of the Windows 10 FCU (16299.19), the sound played by the virtual machine is very distorted and noisy. Especially when it plays for the first time after VM launch.

When I launched for the first time a Windows 10 FCU in the VirtualBox running also on Windows 10 FCU, immediately after lauch the OneDrive toasted has popped out and I've heard something like very loud white noise instead of Windows 10 notification sound. The next times, VM tried to play sound it was less distorted but still very much.

When I set the volume in sound mixer on VM to smaller value, it's less distorted, then I set volume to bigger value, it's more distorted.

I use the VM with the following setting:
-3 GB of RAM, 32 GB of HDD as SATA drive
-2 CPU cores
-2D video and 3D graphics acceleration enabled
-Intel HD Audio
-USB 1.1 enabled
-EFI disabled
-PAE/NX disabled.
",przemek1234pl
17300,crash of all virtual machines,Windows,VirtualBox 5.2.0,2017-11-22T16:30:08Z,2018-01-18T14:35:20Z,2018-01-18T14:35:20Z,"Running several VM's.  When all VM's crash with same error simultaneously.  Log of one vm's crash is attached.  This has happened twice over the last week or two. 

Cannot say what steps are needed to reproduce as it seems random when this occurs.",ArtZ
17268,Guest Addition graphics driver build fails on Debian 9.2 -> fixed,Linux,VirtualBox 5.2.0,2017-11-11T23:56:16Z,2018-01-17T15:12:04Z,2018-01-17T15:12:04Z,"Running Debian 9.2, Kernel 4.9.0-4-amd64 as client on a Win10 guest the build of the grahics guest addition driver fails.

vboxadd-setup.log attached.

Maybe related to #17210",Gevatter Gaul
17206,VBoxLinuxAdditions.run fails in Ubuntu Server 16.04.3 -> module signing problem,Linux,VirtualBox 5.2.0,2017-10-23T22:00:34Z,2018-01-17T11:42:56Z,2018-01-17T11:42:56Z,"VBoxLinuxAdditions.run fails in Ubuntu Server 16.04.3:

{{{
administrator@ubuntu:~$ sudo /media/cdrom/VBoxLinuxAdditions.run
.
.
.
  ld -r -m elf_x86_64 -T ./scripts/module-common.lds --build-id  -o /tmp/vbox.0/vboxvideo.ko /tmp/vbox.0/vboxvideo.o /tmp/vbox.0/vboxvideo.mod.o
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.4.0-97-generic/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 INSTALL_MOD_PATH= INSTALL_MOD_DIR=misc modules_install
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 ""  ERROR: Kernel configuration is invalid."";           \
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /lib/modules/4.4.0-97-generic/misc
make -f ./scripts/Makefile.modinst
  mkdir -p /lib/modules/4.4.0-97-generic/misc ; cp /tmp/vbox.0/vboxvideo.ko /lib/modules/4.4.0-97-generic/misc ; true /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko ; if (echo ""/lib/modules/4.4.0-97-generic/misc/vboxvideo.ko"" | egrep -q ""\/drivers\/staging\/"") && (! egrep -x ""vboxvideo.ko"" ./drivers/staging/signature-inclusion) ; then echo Not signing ""/lib/modules/4.4.0-97-generic/misc/vboxvideo.ko""; else scripts/sign-file ""sha512"" ""certs/signing_key.pem"" certs/signing_key.x509 /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko || true && true /lib/modules/4.4.0-97-generic/misc/vboxvideo.ko; fi
At main.c:222:
- SSL error:02001002:system library:fopen:No such file or directory: bss_file.c:175
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178
sign-file: certs/signing_key.pem: No such file or directory
  /bin/bash ./scripts/depmod.sh /sbin/depmod 4.4.0-97-generic """"
Creating user for the Guest Additions.
Creating udev rule for the Guest Additions kernel module.
Could not find the X.Org or XFree86 Window System, skipping.
}}}

Fails for following:

VBoxGuestAdditions_5.2.1-118447.iso
[[BR]]
VBoxGuestAdditions_5.2.1-118468.iso
[[BR]]

{{{
administrator@ubuntu:~$ uname -a
Linux ubuntu 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

}}}
",Red Viking
17235,5.2 causes blue screen of death on windows 10,Linux,VirtualBox 5.2.0,2017-11-04T03:22:51Z,2017-12-11T20:00:20Z,2017-12-11T20:00:20Z,"I upgraded from 5.1.30 to 5.2 to use my ubuntu 17.04 and 17.10 machines. I had multiple BSOD per hour until I reverted to 5.1.30. No BSOD since then.

I have a Surface Pro 4 with the latest Windows 10 updates.

Sorry, I could not capture the error code or QR on the blue screen before the PC rebooted.",silvermangb
17239,Serial port missing characters.,Linux,VirtualBox 5.2.0,2017-11-04T14:38:09Z,2017-12-07T08:32:04Z,2017-12-07T08:32:04Z,"Using 'Windows 10' as host, and being Linux 'Ubuntu 14.04 LTS' as guest, with 
Virtual Box 5.2.0 and its associated guest additions, once the guest Ubuntu has
been launched, by using the serial port: /dev/ttyS0, from within the guest, some 
characters are missed (they don't appear in the serialized stream of data 
shown in the terminal's screen).

This problem is also present in other versions of virtual box (for example: 
5.1.18). On the other hand, this issue works fine under Windows 7 as host 
using virtual box 5.1.18.

¿Perhaps is there some incompatibility between guest additions and windows 10?
",jim_
17349,VINF_EM_TRIPLE_FAULT,Linux,VirtualBox 5.2.0,2017-12-05T22:41:28Z,2017-12-07T02:13:13Z,2017-12-07T02:13:13Z,"I get guru meditation immediately after the Virtualbox BIOS screen and the log says VINF_EM_TRIPLE_FAULT. This is in a guest machine where I just freshly installed RHEL 7.4 64 bit running on Windows 7 64 bit host. The guest started to boot the first start after I installed RHEL but triple fault occurred before boot finished. Every other boot gets triple fault immediately after the Virtualbox BIOS screen. I see lots of other triple fault bugs but none for Red Hat.

Error occurs on latest stable and latest testing builds

Stable
VirtualBox-5.2.2-119230-Win.exe

Testing
Version 5.2.3 r119405 (Qt5.6.2)",ke
17344,VirtualBox 5.2.x installer: ProductID in MSI File and ProductID on installed system do not match,other,VirtualBox 5.2.0,2017-12-04T13:22:11Z,2017-12-04T13:22:11Z,2017-12-04T13:22:11Z,"With the installation packages for VirtualBox 5.2.x on Windows the ProductCode that can be read from the MSI files, is not the ProductCode that is found on the system after Installation.

E.g.: 
||=Version=||=MSI value=||=""real"" value=||
|| 5.2.0-r118431 ||{1E6A323C-1BE9-49B6-8FDC-107307DBC6CE}||{9df09fcf-7f55-402e-aab8-67ffba56ea3b}||
|| 5.2.2-r119230 ||{9F5D10F9-A372-4B1E-BEB3-001B47E0C325}||{b4758fb7-76a2-4391-aca1-6bffcfc90c40}||
|| 5.2.3-119337  ||{8B91C2E7-6A86-43AE-8797-48A61E6C59AB}||{9988FC09-BE58-4DF3-9943-AC14E7A0882C}||

This breaks the common procedure ind automated software deployment:
1. extract ProductID from MSI
2. install MSI
3. check whether MSI for ProductID is installed",WRatzka
17340,Windows PosReady 2009 doesn't work,Windows,VirtualBox 5.2.0,2017-12-02T16:40:26Z,2017-12-02T22:49:27Z,2017-12-02T22:49:27Z,"I do not even know did i install it, but i think there were various errors even during isntall, hell I forgot...
Anyway now when I start os it's giving bsod in guest os DRIVER UNLOADED WITHOUT CANCELLING PENDING OPERATIONS. And at the same time my host os windows xp pro sp3 says The instruction at ""0x121d39d4"" referenced memory at ""0x00000008"". The memory could not be ""read"".

So let's conclude: Posready 2009 is not supported by virtualbox???
Regardless is it install or running of that os or somewhere in between or both.

Posready 2009 is downloaded as preview directly from microsoft.com and size is less than GB, or few hundreds MB.
https://www.microsoft.com/en-us/download/details.aspx?id=11196",nijazxp
17339,"Windows 98 can't be installed on windows xp, but can on windows 10",Windows,VirtualBox 5.2.0,2017-12-02T16:27:34Z,2017-12-02T22:42:05Z,2017-12-02T22:42:05Z,"When I put windows 98 se iso which is itself bootable, immediately, even before anything is read from it, app in my host windows xp os says ""VirtualBox.exe . Application Error"", ""The instruction at ""0x77c47631"" referenced memory at ""0x000c000c"". The memory could not be ""written"".""
Click on OK to terminate the program...

This is an all versions. Tested on xp pro sp3 with or without windows updates and addons like net framework, dx, vc redists...
I was never since i was born able to install windows 98 while using windows xp.

Windows XP cd boots when used in for win98 settings.",nijazxp
17314,V 5.2.2 doesn't work and cannot be unistalled,Windows,VirtualBox 5.2.0,2017-11-26T20:37:33Z,2017-11-26T22:03:29Z,2017-11-26T22:03:29Z,"I downloaded and installed the latest release over a 5.1 release under Win10. When I attempted to run an XP VM used 15 mins earlier it saied teh Extensions were out of date. I attempted to installed the new extensions but it failed with an URL error on the validation. So now I could not run my XP machine. I deleted the VM and tried to uninstall VirtualBox. That was rejected - cannot access path - you may not have authority, (I run as administrator). Nor would it let me modify the installation. Can anyone tell me how to get out of this mess, please? ",Benjiboy
17272,My Windows 10 crash when I try to start the install of a linux vm,other,VirtualBox 5.2.0,2017-11-14T15:55:31Z,2017-11-22T15:48:05Z,2017-11-22T15:48:05Z,"My Windows 10 crash when I try to start the install of a linux vm. It works fine up until I hit start, I can load in the ISO file into storage but once i hit start windows crashes. I have tried the ISO for debian and ubuntu and it works fine with hyper V.",cgarry
17254,VM inaccessible due to guest additions attach issue,other,VirtualBox 5.2.0,2017-11-08T05:10:21Z,2017-11-22T02:32:25Z,2017-11-22T02:32:25Z,"After upgrading to version 5.2 initially there was no issue with the guest (eComStation) and I was able to start it a few times and also installed the new guest additions in it. Last time it seemed to shut down fine, but now I'm unable to start the guest. In the GUI is shows as inaccessible.[[BR]]
The error message is:[[BR]]
Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {a2ff5d7d-6ede-4ade-80df-1ffc0ccfa03c}: medium is already associated with the current state of machine uuid {ee69103a-fec1-489f-adf2-25eb10922ba1}!.[[BR]]
Result Code: 
VBOX_E_OBJECT_IN_USE (0x80BB000C)[[BR]]
I don't understand how this non-essential medium can make the guest inaccessible, however the worst thing is that the Settings icon is disabled for the client, so I can't detach the guest addition image nor make any changes. And the guest addition image is there and I even re-installed it with no effect.[[BR]]
The log file seems to be from the time the last successful launch of the guest.
",Rafcio
17295,VM doesn't works after last windows10 upgrade on Host,Windows,VirtualBox 5.2.0,2017-11-19T23:57:44Z,2017-11-19T23:57:44Z,2017-11-19T23:57:44Z,"Windows 10 running on host, and VMs (Windows10) works fine until the last Windows10 on host
After this update, VM can be launch (I have a Virtual Box 5.0 installed),
So I upgrade Virtual Box to 5.2 and I can launch the VM.
The problem is VM have a black screen ...
I remove the additional guest on my vm, no change.
from now all my VMs are out of order

",dingdingdong
17292,VirtualBox-5.2.0-118431-Win.exe post install causing NetBT errors in Event Log,Windows,VirtualBox 5.2.0,2017-11-18T19:19:45Z,2017-11-19T21:11:16Z,2017-11-19T21:11:16Z,"After i installed VirtualBox-5.2.0-118431-Win.exe along with the Guest Additions on a 64 bit Windows 7 machine i continually get the following errors every few seconds in the Event Logs.  I downgraded back to 5.1.30 and the errors stopped.  So, 5.2.0 has some bugs with the NIC.  I am using NAT for Host Network settings and disabled all other NIC cards.  The only active NIC is the Wireless NIC: Intel(R) Dual Band Wireless-AC 7260

Here is the error with attachment:

Level	Date and Time	Source	Event ID	Task Category
Error	11/18/2017 10:37:24 AM	NetBT	4321	None	""The name """"WORKGROUP      :1d"""" could not be registered on the interface with IP address 10.0.2.15. The computer with the IP address 10.0.2.2 did not allow the name to be claimed by this computer.""
",kingpoop
17279,Not Responding when going to settings after upgrade,all,VirtualBox 5.2.0,2017-11-16T12:10:05Z,2017-11-16T12:10:05Z,2017-11-16T12:10:05Z,"Upgraded to 5.2 - When going to settings of any previous or new VM - it
freezes and says ""not responding"". it never recovers and you must force close
VirtualBox. Just had a couple of Windows updates prior to this upgrade.
(KB4049011) and (KB4048954)
Windows 10 Pro Version 1703
SurfaceBook",marshef
17278,Desplome de la Maquina virtual gana 10 al usar que Explorer,Windows,VirtualBox 5.2.0,2017-11-16T10:40:21Z,2017-11-16T10:40:21Z,2017-11-16T10:40:21Z,"Iniciar Internet explorer, y en ocasiones sin hacer nada se produce un error 
critico, abrir una nueva pestaña, cerrar I E., no es posible hacer nada con
 I. E.

Produce un error y muchas veces cierra la maquina virtual.

solo es necesario abrir I.E. y cerrarlo.

host 1709 ( c de so 16299.64 )
guest 1709  ( c de so 17035.1000 )

con guest windows 8.1 ocurre muy parecido, pero no cierra la maquina virtual
",Josep Maria Mercé Currià
17233,vm not start,other,VirtualBox 5.2.0,2017-11-01T09:06:17Z,2017-11-15T10:50:17Z,2017-11-15T10:50:17Z,"real OS Win7x64 I install VirtualBox 5.2 and create new VM win7x32
i push ""normal start"" button, but VM win7x32 not start. error message:

The virtual machine '2' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'D:\Users\romall.rainb\VirtualBox VMs\2\Logs\VBoxHardening.log'.
Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

BUT if push ""headless Start"" VM start!, next push ""show"" i see VM running and normal work.

",romall
17245,VBoxGuestAdditions_5.2.1-118918 does not work with Ubuntu 17.10 guest,Linux,VirtualBox 5.2.0,2017-11-05T16:09:16Z,2017-11-08T11:57:40Z,2017-11-08T11:57:40Z,"After installing guest additions version VBoxGuestAdditions_5.2.1-118918, Ubuntu 17.10 will not boot. Initially the ""Ubuntu"" logo appears as per normal, then screen goes black, does not get to login screen. However, pressing ctrl-alt-F* keys will bring up terminal prompt.
In order to get Ubuntu guest to boot, I have to re-install distribution-package version of guest additions (5.1.30)",Christopher777
17251,Critical Error whilst starting game,Windows,VirtualBox 5.2.0,2017-11-07T06:04:55Z,2017-11-07T06:04:55Z,2017-11-07T06:04:55Z,I was trying to start Melbourne Cup Challenge/Frankie Dettori Racing when the Critical Error message came up. I am running Windows 10 and this game last ran on Windows XP. I have Windows XP 32-bit installed on Virtual Box.,James Bluntus
17244,CentOS 7 Kernel-ml hangs,Linux,VirtualBox 5.2.0,2017-11-05T13:45:10Z,2017-11-05T13:45:10Z,2017-11-05T13:45:10Z,"Documented here: https://bugs.centos.org/view.php?id=11065

Kernel hangs on CPU making the guest graphics mainly unuseable unless you run all Linux in CLI

I'm using the Virtualbox guest additions as advised on the main site, aware that the latest won't compile properly.

Also doesn't like bridging with an RTL8188EE adapter properly, this could be because of the native drivers.",koolholio
17229,Please add HP Sure Click as a hardening adversary.,all,VirtualBox 5.2.0,2017-10-31T16:13:39Z,2017-10-31T18:47:23Z,2017-10-31T18:47:23Z,"Please see a forum discussion here: https://forums.virtualbox.org/viewtopic.php?f=6&t=85134.

A log is provided in the forum.

The user was having typical hardening problems, it looked like an AV conflict, but the ""adversaries"" list in VBoxHardening.log was empty. Plus the user said he normally uses Defender on his Win10 host, which we usually consider as not a problem.

Eventually, after tips on what kind of software to consider, the user discovered that removing ""HP Sure Click"" (a browser filter) fixed the problem.

I am drawing attention to the discussion in case you decide that ""HP Sure Click"" should be added to the adversaries that the hardening feature looks for. Had it been listed then we would have come to the correct diagnosis much faster.
",mpack
17223,virtualbox 5.2 win nt 4 sp1,other,VirtualBox 5.2.0,2017-10-29T04:28:55Z,2017-10-29T04:34:24Z,2017-10-29T04:34:24Z,"it gives misc error if type set to win nt 4

if type set to other unknown i get this error",jammak
17192,5.2 Guest Extension : no share Drives ?!,Windows,VirtualBox 5.2.0,2017-10-21T03:22:46Z,2017-10-25T20:15:37Z,2017-10-25T20:15:37Z,"1.) have upgrade from 5.1.30 and run 5.2 OK. than install Guest Extension.
2.) after reboot i want to reject CD and saw NO share Drives any more ?
3.) after change User i complete lost setup information so i have to attach VDI again and make all setup entry
both Windows 10 1703 Host 64bit / Guest 32bit",Xbase++
17179,Extension pack upgrade failure (from within VirtualBOX offer to do so),other,VirtualBox 5.2.0,2017-10-18T18:54:04Z,2017-10-18T18:54:04Z,2017-10-18T18:54:04Z,"Running VirtualBox 5.2.0 on a recent Windows 10 Pro :
   After upgrading the software from version 5.1.28 to 5.2.0 it offered to install new extension pack to match the upgrade.
   Agreed to do so -- it showed the window and appeared as if it was downloading the pack (I believe it did, but I do not know where).
   Then it proceeded to install and failed, saying something about wrong url.
   Then it offers to retry, but the result is the same dialog, where it ""swears"" the same, so I cancel it.
   
   Downloaded the extension pack from the website. Tried to install it -- VirtualBox said I need to log on as administrator :). 
  
   Logged on as administrator, started VirtualBox and received an offer to upgrade the Extension pack to 5.2.0 -- agreed, dowloaded, and same failure trying to install with seemingly unrelated ""wrong url"".
   Downloaded the pack from the website. Fired it to install (this time as Windows administrator) -- it succeeded.
   ",Kestutiss
17738,Distorted sound is still present in 5.2.10,Windows,VirtualBox 5.2.10,2018-05-05T20:22:58Z,2019-04-21T19:23:16Z,2019-04-21T19:23:16Z,"This is follow-up ticket for the #17225. The situation has changed after some experiments in the audio back end. So now this distortion is always slightly here and can be clearly heard. But not in the dumped files. Previously this distortion came for thirty seconds every 5 or 7 minutes, but then the sound was heavily distorted. Hope this would help to locate and eliminate this issue.",boxer01
17739,Seamless mode not working with Fedora 28 guest,Linux,VirtualBox 5.2.10,2018-05-06T19:15:33Z,2018-07-31T19:11:04Z,2018-07-31T19:11:04Z,"After vbox guest additions are installed with no errors, I observe that the seamless mode option is no longer disabled but I am still unable to copy/paste in either direction.

Entering seamless mode also does not show the windows open in guest OS but I am unfamiliar with seamless mode to know if it was user error or system error.

Host - 
Windows 10
Virtual box version - 5.2.10 r122406

Guest - 
Fedora 28
`uname -r` - 4.16.6-302.fc28.x86_64",AB
17741,Raw-mode is unavailable courtesy of Hyper-V,other,VirtualBox 5.2.10,2018-05-07T16:01:44Z,2018-06-30T15:09:58Z,2018-06-30T15:09:58Z,"Hi,
I am getting the famous error when trying to boot a VM:

""Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT)""

Here are all the steps I have already done with no success:
1  - bcdedit /set hypervisorlaunchtype off
2 - Remove all ""hyper-v"" features through the add/remove programs GUI
3 - Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
4 - dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All
5 - sfc /scannow
6 - A few other DISM commands to clean the file system.
7 - Un/re installed virtualox

I'm not sure what else I can try? My guess is this happened at some point after I installed RSAT package for Windows which may have also installed Hyper-V with it despite me disabling it all. I would be happy to attach logs or other items you need to help.

Thanks!",micahagilent
17697,all new VirtualBox session hang when Skype for Business start a conference/meeting call,Windows,VirtualBox 5.2.10,2018-04-19T10:04:14Z,2018-05-28T07:23:16Z,2018-05-28T07:23:16Z,all new VirtualBox (after interface changed) session hang when Skype for Business start a conference/meeting call.,blaine
17732,64bit guest on 32bit host,Windows,VirtualBox 5.2.10,2018-05-05T00:36:11Z,2018-05-18T08:43:06Z,2018-05-18T08:43:06Z,"After downloading the newest 64bit version of Windows 10 (April update), i faced with a serious problem, when i tried to create a fresh install on a new virtual disk (12GB dynamic VDI). Most likely, the cause of the issue, that my host (it has a C2D P8400 CPU) is running the 32bit version of Windows 7. Altought, it'd be not a problem at all, as long, as VT-x is turned on, in both the BIOS and the VM and the CPU has 64bit support. Nonetheless, installing this OS is currently impossible, because guest is always going to hang, shortly after starting (captured wbem file is attached).
Anyways, i'm pretty sure, VT-x is enabled system-wide, because when i disable it in BIOS, i get the expected error message:

{{{
Failed to open a session for the virtual machine VM_00002.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Also i'm sure, the bug is hiding somewhere in Virtualbox's Windows 10 support, since right after this, i successfully managed to install a 64bit Windows 7 system on exactly the same guest and host (screenshot is attached of this).
",T800
17755,[guest additions] mouse laggy after unlock screen,Linux,VirtualBox 5.2.10,2018-05-11T06:56:04Z,2018-05-11T15:33:08Z,2018-05-11T15:33:08Z,"After locking screen and unlocking it in guest system the mouse pointer becomes slow and laggy. I have enabled guest additions.

guest xubuntu 64bit 18.4 running on xfce4,
host win 10

",mar10
17723,VirtualBox cannot catch USB devices if RemoteFX USB Redirection enabled,Linux,VirtualBox 5.2.10,2018-05-01T19:59:38Z,2018-05-10T19:19:25Z,2018-05-10T19:19:25Z,"Host: Windows 7 SP1 Pro 64 bit. VirtualBox Version 5.2.10 r122406
Guest: Mageia Linux 6 with kernel 4.14.30
The guest additions have been installed 

I had to enable RemoteFX USB Redirection on my Windows 7 Laptop using Group Policy Editor (Enabled for Administrator and User). This feature is necessary in order to redirect ""other"" devices like Dongles etc. to a remote computer using Microsoft RDP protocol version 8.0.
But if this feature is enabled VirtualBox is not able to catch any USB device, neither a simple mass storage device like an USB stick nor a camera...
The first try to connect doesn't show anything, the second try results in an error ""USB device is busy with a previous request""

I tested this on Windows 7 SP1 Pro 64 bit host with a Mageia Linux 6 Guest and with a Knoppix Live ISO (Guest).
When disabling RemoteFX USB Redirection on the host again, everything works as expected.

How to reproduce:
1. Open Group Policy Editor (gpedit.msc) from the command line and 
2. navigate to: Computer Configuration \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop  Connection Client \  RemoteFX USB Device Redirection \ Allow RDP redirection of other supported RemoteFX USB devices from this computer
3. Set to Enabled and the rights to Administrator and User
4. Run gpupdate /force from an elevated command prompt or better do a reboot of the host as advised within the description
5. Connect a simple USB Stick to Windows host
6. Start a virtual machine within VirtualBox and try to catch this USB stick within the Guest
7. The USB device will not be connected. A second try will result in the error: ""USB device is busy with a previous request""

Related tickets: There may be some parallels to Ticket #13513 but the setting is little bit different. Host is a native computer (not a guest somewhere) and Windows 7 itself is not connected via RDP.

Expected behaviour: The setting of ""RemoteFX USB Redirection"" should not have any impact on the USB driver used within VirtualBox

--> maybe it would be helpful to ad this setting to ""USB basics and troubleshooting"" within the VirtualBox forum as it took me hours to narrow this bug down
",spuch
17743,Ryzen 7 X2700 - Not detecting 64bit host,all,VirtualBox 5.2.10,2018-05-08T14:13:33Z,2018-05-08T18:45:38Z,2018-05-08T18:45:38Z,"On windows 10 Pro x64 running a Ryzen x2700 VirtualBox does not correctly detect it is running on a 64bit host, as a result only 32bit guest machines can be created. This applies to both Windows/Linux guest machines.",Timur
17734,Error on starting the new machine,Linux,VirtualBox 5.2.10,2018-05-05T01:22:57Z,2018-05-05T22:49:17Z,2018-05-05T22:49:17Z,I installed virtualbox and set all the settings and installed the extension pack. Then created my first vb with vhd and 32 bit linux os.,greybeard74
17731,virtual drive,Linux,VirtualBox 5.2.10,2018-05-04T13:24:06Z,2018-05-04T14:30:07Z,2018-05-04T14:30:07Z,"the problem enhances, wen I am testing a new OS X86 / internet data mikeOS
the drive get un link’t , after 1 after a month of use


",NadirVT
17717,DNS resolver does not work,Linux,VirtualBox 5.2.10,2018-04-28T20:27:43Z,2018-04-30T14:56:28Z,2018-04-30T14:56:28Z,"Adapter in NAT mode, network ""192.168.100/24"".

Guest network adapter is called enp0s3, `ip addr` shows the interface is up with ""inet 192.168.100.15/25"".

`ip route` shows ""default via 192.168.100.2 dev enp0s3"".


Now, on the host-side the default DNS is 192.168.1.1.
The guest can ping this IP, but according to the [https://www.virtualbox.org/manual/ch09.html#changenat manual/ch09.html#changenat] the name server should be available at 192.168.100.3.

In the guest: `drill virtualbox.org @192.168.100.3` fails with ""Error: error sending query: Could not send or receive, because of network error"".
`drill virtualbox.org @192.168.1.1` (""directly"" through the DNS in the host's network) works.

I can however ping 192.168.100.3. I can also ping .2 and .4 successfully.",xnoreq
17719,"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors",other,VirtualBox 5.2.10,2018-04-30T03:50:26Z,2018-04-30T07:04:35Z,2018-04-30T07:04:35Z,"Windows installer for 5.2.10 fails with dozens of ""Could not write value to key"" registry errors.

Representative screen shots attached.

",Kriston
17718,Poor network latency performance / consistency,Linux,VirtualBox 5.2.10,2018-04-28T21:02:15Z,2018-04-28T21:02:15Z,2018-04-28T21:02:15Z,"For VBox.log see the attached log from #17717.

Pinging a computer in the LAN from the host I get constant <1 ms RTT.

Pinging the same computer through from the guest I get ping times that fluctuate from >1 to 10ms. Sometimes it jumps to over 70ms, and even over 160 ms.

This is with both the host and guest essentially idle. Similarly poor performance is observed with TCP and UDP.",xnoreq
17811,VirtualBox (vboxdrv) installation FAILED on some Windows 7 PCs,other,VirtualBox 5.2.12,2018-06-08T02:16:11Z,2020-06-15T19:31:59Z,2020-06-15T19:31:59Z,"Hi All,

I'we got a new Win 7 PC: Toshiba Z40-C laptop with Intel Core i7 6600U CPU.
VirtualBox 5.2.12 (latest), but also tried 5.1.38 and 5.0.40, with the
same problem. (and even the ancient 4.1.6 version from 2011, before hardening)

One thing is special about this particular Windows 7 PC: It uses UEFI.
All the other dozens of my Windows 7 PCs, where VirtualBox works like
a charm, all use BIOS.
Maybe some kind of security properties do differ somehow.

VBox.log:
https://www.dropbox.com/s/8ss3510bofy4ntd/vbox.log.txt?dl=0

The problem is: no matter what I do, ""vboxdrv"" never gets installed.

It says cannot start VM : ""Make Sure the kernel module has been loaded
successfully"".

Error in supR3HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed

Looking at a list of drivers in ""Device Manager"", I cannot see
""vboxdrv"" listed there. (Even with show hidden -> Non-plug-n-play
devices)

More info:
C:\Users\Alexey>sc.exe query vboxdrv

{{{
SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 2  (0x2)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}

It seems there is a conflict between VirtualBox and some other
software / device driver on my PC, or OS configuration. But how to figure it out ?
The PC is totally new, but it has a lot of Toshiba drivers & utils included.
Restarting the PC (the Windows way) didn't help either.

Registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
{{{
DisplayName=VBox Support Driver
ImagePath=\??\C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
ErrorControl=1
Start=3
Type=1
}}}

Event Viewer:
{{{
System/Information

---
A service was installed in the system.

Service Name:  VBox Support Driver
Service File Name:  C:\Program Files\Oracle\VirtualBox\VBoxDrv.sys
Service Type:  kernel mode driver
Service Start Type:  demand start
Service Account:

---
System/Error

The VBox Support Driver service failed to start due to the following error:
The system cannot find the file specified.
}}}


In reality the driver file exists:

C:\Windows\System32\drivers\vboxdrv.sys
and
C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv.sys

yet, it is completely absent from Windows Device Manager (driver list).
So the driver was copied, but not loaded.


-Alexey Eromenko ""Technologov"". 08.06.2018.",Technologov
17912,Crash on Dell docking station disconnect,Windows,VirtualBox 5.2.12,2018-08-03T12:44:02Z,2019-03-11T10:30:45Z,2019-03-11T10:30:45Z,"Hello,

I'm using VirtualBox 5.2.12 r122591 (Qt5.6.2) on Windows 7 x64 Dell Latitude E7440. This laptop is usually connected with the docking station to which I have connected 2 monitors. One of those monitors is also a USB hub to which I have attached USB Wifi. I use this Wifi in my Virtual Machine.

My VM is also a Windows 7 x64 system.

Now... sometimes (not everytime but several times per week) when I disconnect laptop from docking station - VirtualBox crashes (only the window with virtual machine, the main window with list of machines is still open).
This isn't a new issue - with previous versions I had the same problem.


{{{
03:44:32.016942 VUSB: Detached '000000000eebcd30[proxy 7392:7811]' from port 1 on RootHub#0
03:44:32.026037 
03:44:32.026039 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000264c!!!
03:44:32.026081 
03:44:32.026082 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fed194d510
}}}
",dariuszszyc
17772,Guru meditation 1155 on loading driver in guest,Windows,VirtualBox 5.2.12,2018-05-17T09:35:19Z,2018-07-12T11:45:41Z,2018-07-12T11:45:41Z,"So we trying to load driver inside Windows 7 (6.1.7601.24000) guest machine on Windows 7 host machine with VirtualBox:

{{{
sc create ltest type= kernel start= demand error= ignore binpath= ""<full path to sample>"" DisplayName= ltest
sc start ltest
}}}
and we catch ""Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""

Actually the driver is windows kernel 6.1.7601.24000 (win7sp1_ldr.171231-1547), so it's like trying load second kernel to system. Yes, I known it's crazy, but anyway it's not ok catch guru meditation on this crazy actions.
",gim
17845,"Managing groups of VMs will not be synchronized in filesystem, VM stay on their location",all,VirtualBox 5.2.12,2018-07-01T10:02:34Z,2018-07-01T10:02:34Z,2018-07-01T10:02:34Z,"Managing of groups (new group, move VM to new group, add VM to group) will not synchronized in filesystem.

Steps: 
- VBox running without any Virtual Machines (VM)
- Create on VM: ""vm1""
- ""Group"" this ""vm1"": Group ""New Group"" will created, also in Filesystem (FS) a directory ""New Group"" is created, directroy ""vm1"" is now inside ""New Group""
- Rename ""New Group"" to ""grp1"": ""vm1"" is displayed in group ""grp1"", in FS directory is renamed to ""grp1"", ""vm1"" is inside ""grp1"": OK 
- Clone ""vm1"" to ""vm2"": ""vm2"" is displayed outside ""grp1"", directory ""vm2"" is created outside ""grp1"" (parent directory)
- ""Group"" ""vm2"" to a second group ""grp2"" as before: Group ""grp2"" is displayed with ""vm2"" inside. But no directory for group ""grp2"" is created, ""vm2"" is still outside.
- Move ""vm2"" to ""grp1"" (drag an drop): ""grp2"" is no longer displayed, ""grp1"" has members ""vm1"", ""vm2"". In FS ""vm2"" is still outside of ""grp1""
- ""Add new VM"" in group ""grp1"": Displayed in ""grp1"", but in FS it is created outside of ""grp1"".

Summary:
Only one group will be managed in filesystem. Display and Filesystem are not synchornized.
The first VM of the group will be moved inside group directory.
No further group directories will be created.
Other vms (by clone, by add, by move) will stay outside (in the parent-directory).
",TKinVBOX
17836,ERROR TO OPEN VB,Windows,VirtualBox 5.2.12,2018-06-22T17:30:20Z,2018-06-22T20:51:18Z,2018-06-22T20:51:18Z,"I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB:

""Error in supR3HardNtChildWaitFor
Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles).
Plea try reinstallin VirtualBox.
where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)""

So I tried to reinstal but it's the same error.

What's happening???",alaz
17832,Vt-x is not available.  What tool will identify the problem?,other,VirtualBox 5.2.12,2018-06-21T11:00:09Z,2018-06-22T05:08:43Z,2018-06-22T05:08:43Z,"Failed to open a session for the virtual machine GreyCampus Big Data and Hadoop Developer Virtual Machine.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I am trying to complete an online course in Hadoop that has a Virtualbox VM as part of the course.  My computer is a Dell XPS 15 (2017) and it has run VirtualBox VMs before. The Bios has this turned on and Hyper-V in the Windows 10 OS is turned off.  I also have Visual Studio 2017 installed but have gone in and uninstalled any features in it I can find that might use this.  Perhaps there still is something, but it is like finding a needle in a haystack.  There should be a tool or a log description can point a finger at precisely what has captured the virtualization so I can fix this.  ",superdml
17818,Guru Meditation 1155 (VING_EM_TRIPLE_FAULT),other,VirtualBox 5.2.12,2018-06-13T16:30:12Z,2018-06-15T18:49:56Z,2018-06-15T18:49:56Z,Getting the above message in the vbox log.  VBox v5.2.12.  Running a Windows 7 32 bit vm in a Windows 10 environment.,NateK
17816,Can't connect to on Linux guest from Windows via host-only network,Linux,VirtualBox 5.2.12,2018-06-12T11:20:47Z,2018-06-12T17:32:08Z,2018-06-12T17:32:08Z,"I have an Ubuntu VM that runs a MySQL server among other things. I connect to it from different host systems - macOS, Windows.

For some unknown reason the host system can no longer connect to the server (mysql says ""connection refused""). I'm connecting through a host-only network via 192.168.56.101. I can ping this IP address without problems.

I have no idea why it stopped working. I did not change any configuration. Deleting and re-creating the host-only network doesn't solve the issue. 

I'm not a networking expert, I have no knowledge of debugging this sort of issues. I was hoping that you could fix this bug.",szx
17815,Failed to save settings - Empty or null bridged interface name is not valid.,Linux,VirtualBox 5.2.12,2018-06-12T09:19:14Z,2018-06-12T13:15:56Z,2018-06-12T13:15:56Z,"After I disable the bridged network (because is no adapter for some reason, so can't use it) and try to save settings, I get the following error:

Failed to save settings

Empty or null bridged interface name is not valid.


Result Code: 
E_FAIL (0x80004005)
Component: 
NetworkAdapterWrap
Interface: 
INetworkAdapter {e925c2aa-4fe4-aaf6-91c5-e9b8ea4151ee}

",szx
17804,Win10 and 7 host OracleEnterpriseLinux 6.7 guest addition clipboard and window resize does not work,Linux,VirtualBox 5.2.12,2018-06-05T20:46:33Z,2018-06-12T09:39:34Z,2018-06-12T09:39:34Z,"HostOS: Win10 Pro, Win7Pro
GuestOS: Oracle Linux 6.7
uname -a: Linux demo.us.oracle.com 3.8.13-118.4.2.el6uek.x86_64 #2 SMP
VBox: Version 5.2.12 r122591 (Qt5.6.2)
Guest Addition: 5.2.12 successfully installed under OS user 'oracle' and root authentication was given during the install.
Mouse integration works, I can move the mouse outside of VBox window without pressing Right-CTRL.
Devices/Shared Clipboard is set to bi-directional
Devices/Drag and drop disabled
Devices/Shared Folder is set and auto-mount is working, files can be read and written.

What does not work is:
1. Clipboard between host and guest do not work in any direction regardless what is the Devices/Shared Clipboard setting
2. VBox window resizing worked before guest addition was installed, after that it stopped working only 800x600 screen size is available by default. Within Linux manual reset of the resolution works but the information gets lost and reset to 800x600 after reboot.
3. when switching Linux OS user from 'oracle' to 'root' the screen resizing starts working and the clipboard bidirectional as well.
4. When switching back to 'oracle' it is not working

The clipboard integration makes it as a major incident.

",Laszlo
17807,VM fails to start,Linux,VirtualBox 5.2.12,2018-06-06T18:55:20Z,2018-06-11T16:32:38Z,2018-06-11T16:32:38Z,"Running Version 5.1.14 r112924 (Qt5.6.2) on Windows 7 64bit, suddenly it fails to start with below error:

The virtual machine 'Oracle Linux 6.7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\Virtual_Machines\Oracle Linux 6.7\Logs\VBoxHardening.log'.
",Abdelj
17806,Error 0x80070057 usb,Windows,VirtualBox 5.2.12,2018-06-06T14:36:57Z,2018-06-11T16:30:57Z,2018-06-11T16:30:57Z,"Hola, cree una maquina virtual w10, el SO donde esta instalado virtualbox es w7. y no logro utilizar un pendrive, probé varios.",woltsp
17793,Change in VM settings not taken into account with snapshots,Windows,VirtualBox 5.2.12,2018-05-31T03:46:27Z,2018-06-08T14:58:51Z,2018-06-08T14:58:51Z,"On a UEFI Windows 10 x64 virtual machine with multiple snapshot, change in the configuration are not taken into account when booting, even if the virtual machine file show that these change are saved.

For example, I tried to change the boot order to ''Network'' on that virtual machine, but it still tries to boot to ''DVD'' and then ''Hard Drive'' (if I press F12 and go to '''Boot Manager''', ''Network'' is not even there and the order doesn't correspond to the one saved.

Virtual Box version 5.2.12 r122591 running on Windows 10 Pro x64 v1709",Michael Tremblay
17785,Start Kali Linux,Linux,VirtualBox 5.2.12,2018-05-23T14:11:23Z,2018-05-23T16:25:01Z,2018-05-23T16:25:01Z,I installed kali linux virtual machine and the error occurs during startup,LucaFaggiani
17782,"Virtualbox for Windows 5.2.12: ""Failed to aquire the Virtualbox COM object""",Windows,VirtualBox 5.2.12,2018-05-21T23:46:51Z,2018-05-22T20:35:51Z,2018-05-22T20:35:51Z,"Hi,
I have been having this issue for multiple weeks, and I was hoping someone could help.
I understand that many people have had this issue, and I have tried almost every fix, repair, and etc. that I have the power to do.
",MaxMega12
17773,Distorted sound Host: Windows 10 Guest: Ubuntu 18.04,Linux,VirtualBox 5.2.12,2018-05-17T14:03:17Z,2018-05-17T14:03:17Z,2018-05-17T14:03:17Z,"Distorted sound after about 8 minutes, restores to normal by another minute.[[BR]][[BR]]
Repeat this issue indefinitely with random times.
[[BR]][[BR]]
Recorded audio debug wav files as in [https://www.virtualbox.org/wiki/AudioDebug]
and found no file with distortion. (So they are not attached)

It should be the first case in Diagnosis table
||= Playback in running VM =||= Dumped file(s) =||= Diagnosis =||
|| Distorted || OK || '''Host driver (backend) problem''' ||
[[BR]]
Same issue with a previous configuration Host: Windows 7 Guest: Ubuntu 16.04 with many versions of VirtualBox.
Only VirtualBox 5.2.7 solved partially as instead of distorted sound it goes mute. 

Thanks.[[BR]]

P.S. Classified as major priority as this issue is a long time pending.[[BR]]

P.P.S. by the way debug wav files are not compatible with windows media player",Han Fastolfe
17760,"can not start the vm and get the error ""VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)""",Linux,VirtualBox 5.2.12,2018-05-12T22:19:42Z,2018-05-14T14:15:32Z,2018-05-14T14:15:32Z,"Hi,

I created a centos 7.4 virtual machine. After creating, it works ok under virtual box. However it randomly can not start and the log complains below error: 
VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

Attached please find the log file and the screenshot image. 

Thanks,
Shifeng",shzhang
17761,Virtual machine stuck at initializing (windows logo),Windows,VirtualBox 5.2.12,2018-05-14T02:49:17Z,2018-05-14T06:01:19Z,2018-05-14T06:01:19Z,"-Create a windows 10 32 bits virtual machine
-2 GB of hard disk + ISO Image (SATA)
-128 MB graphics
-4 GB of dedicated TAM",Leviathan
17751,"""A critical error has occured while running the virtual machine and the machine execution has been stopped.""",Linux,VirtualBox 5.2.12,2018-05-10T17:19:51Z,2018-05-10T20:03:42Z,2018-05-10T20:03:42Z,"Hello.
I just installed VirtualBox on Windows 8.1, in order to install Kali Linux, however I keep getting the warning ""A critical error has occured while running the virtual machine and the machine execution has been stopped."".
What should I do?
Thank you in advance.",Nyctivoe
17858,VBox Guest Additions make crash VM VB during take VM snapshots,Linux,VirtualBox 5.2.14,2018-07-05T18:46:11Z,2018-11-07T05:58:14Z,2018-11-07T05:58:14Z,"Hi All!

I have a VBox VM with Ubuntu 18.04 as guest on WIndows 10 Host. Before installing the VBox Guest Addition (VB GA) on Ubuntu VM, the VM snapshots all worked very well! But after installing it, all the snapshots that are made cause a crash of the same VM (they interrupt its functioning). In practice, the snapshot process stops and crashes as soon as it reaches 96% of the acquisition of the same. I need the VB GA to implement the shared network folder between guest and host.

In my opinion this is a bug of the VB GA.

  - What's the cause of this crash? Is it possible to fix it?

Thank you.

Greetings,

Lorenzo",Kowa92
17874,Drag and drop feature doesnt work Windows 10,Windows,VirtualBox 5.2.14,2018-07-19T12:16:42Z,2018-08-28T09:42:29Z,2018-08-28T09:42:29Z,"Multiple installations and different versions of 64bit win 10
Drag and drop is enabled, this does not allow drag and drop of a folder onto the VM  

The red circle is presented.

This works sporadically, sometimes a reboot of vm required with it turned on or off before it works
Sometimes I cannot get it to ever work.",Pierre81
17853,Sayign that Virtualisation is disabled when it is definitely enabled,Linux,VirtualBox 5.2.14,2018-07-03T16:54:53Z,2018-07-12T21:59:26Z,2018-07-12T21:59:26Z,"When i try to load a virtual machine i get the following error

    ''Failed to open a session for the virtual machine Linux.
    
    VT-x is not available (VERR_VMX_NO_VMX).
        
    Result Code: E_FAIL (0x80004005)
    Component: ConsoleWrap
    Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
''
This is also happening for my Windows 7 Virtual machine (Both machines are 64-bit)

I have checked all the the things i could think of, and anything that came up after a quick google search and all seems okay to me.

So far i have checked:

Virtualisation Enabled in BIOS - Yes ->(https://imgur.com/gallery/cxYxs7d)

Hyper-V disabled in Windows - Yes -> (https://imgur.com/gallery/rO8u0j9)

Windows sees that Virtualisation is enabled in the Task Manager ->(https://imgur.com/gallery/92A0Ebb)

I have tried enabled and disabling Hyper-V to no avail.
I have also tried with both VT-D enable and disabled - Yet it makes no difference",TheBritishBoi
17860,USB 3.1 support,Linux,VirtualBox 5.2.14,2018-07-09T11:44:14Z,2018-07-09T12:17:10Z,2018-07-09T12:17:10Z,"The usb camera that reports as USB 3.1 will not be recognized by Virtual box while every things working fine with USB 3.0 camera. 

I am not sure if anyone has already reported this. But I did not find any thing in google search.

I am using latest version of Virtual box 5.xx and USB extension package.  ",T1000
20281,Critical error CentOS 7,Linux,VirtualBox 5.2.16,2021-04-02T10:18:23Z,2021-04-02T10:18:23Z,2021-04-02T10:18:23Z,"Once a week, a virtual machine running centos 7 crashes with a critical error. Windows server 2008 r2 host - freezes. It is not possible to shutdown virtualbox. Only rebooting the host helps.",Ruby_Ridge
17911,Audio missing with applications on Windows 98,Windows,VirtualBox 5.2.16,2018-08-03T00:20:59Z,2018-10-29T19:37:46Z,2018-10-29T19:37:46Z,"When I first install Windows 98, the audio and start sound work as expected but any other applications such as the built in media player are silent. The only audio I can hear is the Windows notification sounds and everything else is silent. I'm unsure as to whether this is being caused by something I'm doing or if this is being caused by a VirtualBox bug.",Eddy Smith
17923,miracast on Windows 10 guest system not working,Windows,VirtualBox 5.2.16,2018-08-10T13:37:52Z,2018-08-11T05:41:59Z,2018-08-11T05:41:59Z,"trying to use miracast on windows 10 (virtual) system of virtualbox not working?
could you please tell me if it's possible to make it work or is it a limitation.
thanks",babouchka
17907,"Mouse pointer icon frozen, mouse clicks working when USB2 enabled in Win10 VM",Windows,VirtualBox 5.2.16,2018-08-01T19:59:31Z,2018-08-01T23:00:57Z,2018-08-01T23:00:57Z,"1. hp Zbook STudio G3 laptop, 16GB RAM, I7-6700HQ CPU @2.6GHz
2. Windows 10 Enterprise, 64-bit OS, x64-based processor
3. Logitech wireless mouse and keyboard, M510.
3. VirtualBox-5.2.16-123759-Win.exe
4. Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack

Problem Description:

Installed VirtualBox-5.2.16-123759-Win.exe.  
Downloaded Windows 10 trial to create a Windows 10 VM with.
Used without issue for several days.  Mouse and keyboard working fine.

Installed VirtualBox guest additions.  
Settings->UserInterface->Devices checked Insert Guest Additions CD Image.
Started VM.
Ran the installer, VBoxWindowsAdditions-amd64. rebooted.
Mouse and keyboard still working fine.

Needed access to usb2 devices.
shutdown vm.
USB2 & 3 could not be enabled. Instructions said to install extension pack.
downloaded Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack and installed.
Enabled USB2:  Settings->USB.  Added USB devices, Intel Corp. [0001], Logitech USB Receiver [1203] 
Usb2 & usb3 could now be enabled in Settings.
start vm.

As soon as Windows initial screen appears, mouse pointer icon appears frozen.
The wait cursor (round circle) is showing and changing.
moving the mouse makes the mouse cursor blink but the actual cursor does not change position.
as you physically move the mouse, You can see different areas of the windows screen responding as 
an ""invisible"" mouse cursor passes over them.
clicking the mouse brings up the mouse dialog menus. 
The host computer has no mouse capability.
If I don't login and enter windows, and I stay on the login screen, I can use the tab key to move over and select 
shutdown.
As soon as the VM shuts down, I have control over the mouse again.

While VM is shutdown, I can go back to settings, delete the USB devices I added for USB 2.
when vm is restarted, I can move mouse.

I also tried a wired HP usb mouse.  Same behavior.

I tried going to logitech site for updates for mouse driver.  Did not find anything.
Since the HP wired mouse has the exact same behavior, I don't think it is Logitech related.",inxe
17906,I cant run my VM,Windows,VirtualBox 5.2.16,2018-07-31T13:55:46Z,2018-07-31T14:24:44Z,2018-07-31T14:24:44Z,"Good day,
I need your help solve my vm problem, it cant run, I have the message and the name error that printout.
""
Error in supR3HardNtChildWaitFor
Timed out after 2001 ms waiting for child request #0
(PurifyCuildAndCloseHandles).
(rc=258)

Please try reinstalling VirtualBox.

where supR3HardNtChildWaitFor what? 5 Unknow Status 258 (0x102)(258)-
Unknown Status 258 (0x102)
""",BrADT23
17901,Bugs related to Copy files from Host to the virtual machine.,Windows,VirtualBox 5.2.16,2018-07-28T14:04:16Z,2018-07-29T13:54:19Z,2018-07-29T13:54:19Z,"  Can not copy and paste with Bi-directional option enabled
and it is stopping drag and drop when I freeze the current state and return later, so I always have to shut down the machine in order to work Drag and drop
these problems are happening with Windows 7 64 Bit and Windows 10 64 Bit

Note: I installed the virtual machines using the standard Virtual Box did not do customizations in the HD, just changed the size of ram memory to 4 GB and put 4 processor cores, the network card I used Bridge.",Luciano_F
17893,Image doesn't start under Windows 10,all,VirtualBox 5.2.16,2018-07-27T00:23:47Z,2018-07-29T08:33:03Z,2018-07-29T08:33:03Z,"I try to create a virtual box under Windows 10. I tried multiple OSs and also VirtualBox 5.1.38. I always get the following error code when I try to start the newly generated image:

Failed to open a session for the virtual machine UbuntuDon.

The virtual machine 'UbuntuDon' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\do991164\VirtualBox VMs\UbuntuDon\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",Don83
17883,Bridge adaptor removed when updating to 5.2.16,Linux,VirtualBox 5.2.16,2018-07-22T16:45:54Z,2018-07-28T20:57:56Z,2018-07-28T20:57:56Z,"Hello,

When updating from 5.2.14 on a Windows 10 host, my VM configured with network using a Bridge Adaptor were not able to boot. By looking at the settings, the dropdown list when selecting the Bridged Adapter is empty. If I'm not mistaken, there is a Network adapter that should be showing in the Windows control panel, but it doesn't. Is it like the update deleted the adapter (as design I guess since there is a warning for that in the installer), but didn't recreate it.

I was able to resolve this by doing a complete uninstall and install, the bridged adapter was shown in the list. But I feel the update shouldn't break that.

PS: I selected Linux as Guest type, as it's my only guest, but I'm sure it applies to all guest.",sharky98
17881,Network in Bridged mode - Guest can't ping host,Linux,VirtualBox 5.2.16,2018-07-21T21:58:53Z,2018-07-28T20:45:37Z,2018-07-28T20:45:37Z,"- Network configuration: 1 Interface using the Bridged Mode on the Ethernet interface.
- The Guest has access to the internet.
- The host can connect to the guest (ping, ssh, ...)
- The Guest can find the host MAC address and fills the ARP table.
- The Guest can't ping the host. (no answer for the ping).

",zeralight
17877,RHEL 7.5 Guest Blank Login screen,Linux,VirtualBox 5.2.16,2018-07-20T06:54:19Z,2018-07-28T17:45:32Z,2018-07-28T17:45:32Z,"Installed Latest RHEL 7.5 and used Virtual Box 5.2.16 r123759. As soon as 
I install the Guest additions and reboot, I can not login to 
Graphical Desktop. Instead of login, it just shows blank screen. Uninstalling
the guest additions fixes the issue. 

Please note that guest additions installs fine and no issues are
reported. 

Output of /var/log/vboxadd-setup.log
Building the main Guest Additions module.
Building the shared folder support module.
Building the graphics driver module.

Red Hat Enterprise Linux Server release 7.5 (Maipo)

Kernel version

3.10.0-862.9.1.el7.x86_64",ketan
17902,VirtualBox non funziona,Windows,VirtualBox 5.2.16,2018-07-28T16:23:31Z,2018-07-28T16:23:31Z,2018-07-28T16:23:31Z,"ho effettuato una pulizia con CCleaner e non riesco a fare ripartire VirtualBox.
Il log che esce è:
VirtualBox COM Server 5.2.16 r123759 win.amd64 (Jul 16 2018 15:52:14) release log
00:00:00.015619 main     Log opened 2018-07-26T11:32:49.851605900Z
00:00:00.015619 main     Build Type: release
00:00:00.015619 main     OS Product: Windows 10
00:00:00.015619 main     OS Release: 10.0.17134
00:00:00.015619 main     OS Service Pack: 
00:00:00.031240 main     DMI Product Name: System Product Name
00:00:00.031240 main     DMI Product Version: System Version
00:00:00.031240 main     Host RAM: 4016MB (3.9GB) total, 1812MB available
00:00:00.031240 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.031240 main     Process ID: 13232
00:00:00.031240 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.031240          VirtualBox: object creation starts
00:00:00.046862          Home directory: 'C:\Users\piero\.VirtualBox'
00:00:00.046862          Installed Drivers:
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.2.16.23759)
00:00:00.046862            C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.2.16.23759)
00:00:00.062483          Loading settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:00.062483          Getting USB descriptor failed with error 31
00:00:00.078104          USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
00:00:00.171832          HostDnsMonitor: old information
00:00:00.171832            no server entries
00:00:00.171832            no domain set
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitor: new information
00:00:00.171832            server 1: 192.168.1.1
00:00:00.171832            domain: station
00:00:00.171832            no search string entries
00:00:00.171832          HostDnsMonitorProxy::notify
00:00:00.203076          SUPR0QueryVTCaps -> VERR_VMX_MSR_ALL_VMX_DISABLED
00:00:00.250013          VD: VDInit finished with VINF_SUCCESS
00:00:00.250013          Loading settings file ""C:\Users\piero\VirtualBox VMs\Windows Xp\Windows Xp.vbox"" with version ""1.15-windows""
00:00:00.265565          VirtualBox: object created
00:00:01.653184          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:01.663208          Saving settings file ""C:\Users\piero\.VirtualBox\VirtualBox.xml"" with version ""1.12-windows""
00:00:05.471174          Load [C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL] rc VINF_SUCCESS
00:00:05.714537          ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
01:21:15.783203 USBPROXY Getting USB descriptor failed with error 31
02:59:48.161337 MainPower Host suspending: Paused 1 VMs
03:01:39.953430 MainPower Host resumed: Resumed 1 VMs
03:01:41.573588 dns-monitor HostDnsMonitor: old information
03:01:41.573588 dns-monitor   server 1: 192.168.1.1
03:01:41.573588 dns-monitor   domain: station
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitor: new information
03:01:41.573588 dns-monitor   no server entries
03:01:41.573588 dns-monitor   no domain set
03:01:41.573588 dns-monitor   no search string entries
03:01:41.573588 dns-monitor HostDnsMonitorProxy::notify
03:02:05.331431 USBPROXY Getting USB descriptor failed with error 31
03:02:05.332406 USBPROXY USB: Unknown USB device detected (idVendor: 0x0a5c, idProduct: 0x21ec)
03:02:05.896003 dns-monitor HostDnsMonitor: old information
03:02:05.896003 dns-monitor   no server entries
03:02:05.896003 dns-monitor   no domain set

Ho provato anche a fare la riparazione reinstallando il programma ma non funziona ugualmente. 
Qualcuno mi può aiutare? Ringrazio. Piero",Piero
17885,AVAST Internet Security reports threats when I start any machine under VB,Windows,VirtualBox 5.2.16,2018-07-23T08:45:28Z,2018-07-23T13:07:15Z,2018-07-23T13:07:15Z,"Hi! I've been using VBox since Jan 2014. Since last year I keep getting Threats Blocked messages by my AVAST Internet Security. Threats messages read:
""We’ve safely blocked connection on Sportgoods.co.in because infected with URL:Mal.
 We’ve safely blocked connection on Spmpart.com because infected with URL:Mal.
We’ve safely blocked connection on Tektasarim.com because infected with URL:Mal.
""
This threat is quite annoying. And always shows that Virtual Box is trying to contact the above 3 sites!?!
I'm running Virtual box under Windows-10, fully updated. The guest system runs Windows XP. ",VBFan2018
17876,Audio gets looped over.,Windows,VirtualBox 5.2.16,2018-07-19T16:08:49Z,2018-07-19T16:08:49Z,2018-07-19T16:08:49Z,"So i have:

 1. [ host] Win10x64
 2. [ guest] win7
 3. in win7 installed ""Screen.Capturer.Recorder.v0.12.10"" for audio capture
 4. listening siriusxm via chrome
 5. issue starts in 5-15mins

on VirtualBox-5.1.30-118389-Win same ""machine"" works fine, and
each new version of vbox up to VirtualBox-5.2.16-123759-Win have the same issue
with audio.
Need some additional files/tests ?",Genius
17962,Display after resize goes black,Linux,VirtualBox 5.2.18,2018-08-30T13:05:18Z,2019-10-10T01:54:06Z,2019-10-10T01:54:06Z,"Hi,

after resizing display it goes black and VM has to be restarted. VB is running on Win10 enterprise 64bit, guest system is Ubuntu.",Zool0
18445,Problem when starting my virtual machin,Linux,VirtualBox 5.2.18,2019-02-21T13:00:54Z,2019-02-21T16:22:15Z,2019-02-21T16:22:15Z,"i've downloaded an i386 version of Kali linux but when i start it in my virtual machin, it doesn't work.
It was giving me this error: this kernel requires the following features not present on the CPU:pae but i've been able to fix it and now when i start my virtual machin it tells me that it find a critical error when executing the virtual machin and the virtual machin has stopped working. ",Elbro
17933,RDP from iPad 3 (iOS 9.3.5) Problem Keyboard Access to Windows 10 pro,other,VirtualBox 5.2.18,2018-08-16T06:38:46Z,2019-02-17T01:09:51Z,2019-02-17T01:09:51Z,"RDP from iPad 3 (iOS 9.3.5) Problem Keyboard Access, to access windows 10 pro.
Keyboard Loss can't access Windows 10 Pro. Can't input Any Char. 
Used VirtualBox 5.2.18 in Windows 7 and Virtualbox before same problem.

Thank You.

",Kenzo
18203,Confirmation box to Remove Machine with Delete all files,all,VirtualBox 5.2.18,2018-12-19T13:43:07Z,2018-12-20T05:48:06Z,2018-12-20T05:48:06Z,"Machine is deleted immediately after pressing Delete all files.
There should be some confirmation box to remove all files :).",twom
18029,NAT network UDP port forwarding not working,Linux,VirtualBox 5.2.18,2018-10-04T07:07:04Z,2018-11-23T11:25:11Z,2018-11-23T11:25:11Z,"I've created a machine with linux ubuntu with NAT network attached.
The machine connects properly and receives an address 10.0.2.7.
I've created a port forwarding from UDP 500 to 10.0.2.7 UDP 500.
It seems that packets sent to UDP 127.0.0.1:500 are not arriving to the machine. (checked with tcpdump -i enp0s3 udp 500 on the machine.
Doing the exact same with TCP works fine.
Packets are sent with ""Packet Sender"", and verified with rawcap on the host.",Asi Lev
17942,"Audio is almost unusable on Windows 10 Insider builds, when they are cleanly installed.",Windows,VirtualBox 5.2.18,2018-08-20T19:48:03Z,2018-11-15T23:23:56Z,2018-11-15T23:23:56Z,"Steps to reproduce
* Install Windows 10 into a virtual machine.
* Upgrade it to latest fast ring insider build (at the time of this report 17741).
* Notice that audio is working as expected.
* From settings; update and security; reset perform reset of this machine.
* Notice, that audio sounds horribly.
I'm Attaching a logs before and after reset, audio files dumped before a reset and after a reset.
This issue is very important, because it affect also a clean installations of recent Insider builds into Virtual Box vms, and it prevents blind people like me from doing it independently.
I've also verified, that the driver used for the sound card is the same before and after the reset.",lukaszgo1
18051,My screen is all discombobulated! SOS,Linux,VirtualBox 5.2.18,2018-10-14T03:28:28Z,2018-10-17T08:20:08Z,2018-10-17T08:20:08Z,"When I start my VM for Linux Mint, my laptop cant seem to get
the display right. All I can see is a bunch of lines that seem
to make up my screensaver and I see my mouse divided into approx.
12 different slices along the lines that seem to make up my 
screensaver. I use the VM as a programming environment for my 
CS class and I have project due tomorrow but can't get it to run
so I can add the finishing touches... Please help. I would add a
pic if a knew how
",Diddy
18041,guest suse leap 15.0 could not be started after kernel update openSUSE-2018-1140,Linux,VirtualBox 5.2.18,2018-10-10T09:09:19Z,2018-10-17T08:11:08Z,2018-10-17T08:11:08Z,"With VirtualBox 5.2.18r on a Windows 10 host my Open Suse Leap Linux updated
the kernel with openSUSE-2018-1140 and from then on the suse guest couldn't be
started again.
Attached you'll find a hardcopy of the Startup sequence Messages.

An native Installation of Suse, including the kernel 4.12.14.lp150.12.19, 
works w/o any issues.",guenni
18045,glGetFramebufferAttachmentParameter missing in libGL.so.1,Linux,VirtualBox 5.2.18,2018-10-11T14:00:21Z,2018-10-17T08:08:26Z,2018-10-17T08:08:26Z,"I run a linux guest in a Windows 10 host.

In the guest, the OpenGL function glGetFramebufferAttachmentParameter is missing in /usr/lib/virtualbox/additions/libGL.so.1

Due to this, I get linker errors in many packages and can't enable 3D acceleration.

Is this something you can support? What is the status on this?
",Mikael Djurfeldt
18036,MachineTools toolbar buttons disappear after starting VM from Windows Explorer,all,VirtualBox 5.2.18,2018-10-07T12:12:30Z,2018-10-09T19:16:36Z,2018-10-09T19:16:36Z,"Normally in the VM VirtualBox Manager (VirtualBox.exe) I have the Machine Tools toolbar showing both Details and Snapshots. However if I run a VM by double-clicking the .vbox file in Windows Explorer when VirtualBox.exe is not running, next time I run VirtualBox.exe those buttons are not showing on the toolbar. In particular, before I have in VirtualBox.xml
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""Details,Snapshots""/>
but after, I have
  <ExtraDataItem name=""GUI/Toolbar/MachineTools/Order"" value=""None""/>",mf86a
18002,Heap corruption in VBoxSVC.exe leading to a crash (possibly due to double free),Linux,VirtualBox 5.2.18,2018-09-22T14:47:11Z,2018-10-08T14:28:45Z,2018-10-08T14:28:45Z,"I have encountered a crash of latest VBoxSVC.exe 5.2.18.24319 on a Windows 10 host while running two VMs in parallel (one Windows VM and one Linux VM). The crash happend while I was accessing internet resources from the Linux VM.

I have collected a crash dump which indicates that the crash is caused by a heap corruption in VBoxSVC.exe while calling free function from msvcr100.dll. So, this looks like a double-free issue in VBoxSVC.exe.

I could not find a way to reproduce this crash. Usually, I run 3 or 4 VMs at the same time but VBoxSVC never crashed but this time just with 2 VMs and no extensive CPU load (just internet browsing) and it crashed.

I'm attaching the full log from Linux machine. For the crash dump, I can post it but since it is related to potential double free issue in VBoxSVC which are sometime a security vulnerability I prefer to confirm with you first that it is ok to post here.

",idrassi
18026,Detach GUI Option on Window close (suggestions for improvements),Windows,VirtualBox 5.2.18,2018-10-02T09:27:49Z,2018-10-02T09:27:49Z,2018-10-02T09:27:49Z,"Hi I am a Windows user and I have a suggestion,
 when you close the virtualbox window with the X (top right to close a window) you can also have the option to ""Detach GUI"" This would be much easier to use this way!
Thanks a lot for listening to my suggestion :)",adamw
18020,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your system",Windows,VirtualBox 5.2.18,2018-09-27T20:19:34Z,2018-10-01T23:16:53Z,2018-10-01T23:16:53Z,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your windows 10 machine

Scenario to reproduce the issue.

1. reboot the laptop/system
2. try to ping any static IP 192.168..
3. you will see ""destination host unreachable"" for the 1st packet
4. result:""destination host unreachable"" for first ICMP packet 

Manual solution:
1. reboot the machine
2. go to control panel/network and sharing center
3. then go to change adapter settings
4. disable ""virtualBox Host-Only Network""
5. enable  ""virtualBox Host-Only Network""
6. Now ping any static IP
7. results: No error. Works great


",raza
18000,inaccessability of virtual box guest controls on nvda,all,VirtualBox 5.2.18,2018-09-21T08:52:19Z,2018-10-01T22:54:56Z,2018-10-01T22:54:56Z,"the guest controls that contains in running machine window is fully unaccessable for nvda screenreader (nvaccess.org)
this impacts 99% of controls in machines window (machine menu, shutdown dialog, settings dialog, error dialogs...)
settings dialog unaccessable only when it opened from machine window. if it opened from main vbox window, it fully accessable.

also I have sugestion to fix it:
the nvda screenreader has an a special library, called nvda controller client (https://github.com/nvaccess/nvda/tree/master/extras/controllerClient)
this library allow apps to send text directly to screenreader.
I know that every gui item has focus event.
If VirtualBox Gui Application will send to nvda names of dialogs and menu items, possible without any status information, it will become accessable without any big interface changes.
I'm also starting developer and I know that it's very easy to implement, but, if it will be implemented, vbox become mutch more accessable.

I placed the same request in main VirtualBox forum and in VBoxDev list, but no get any response.",ilyapashuk
18013,Suggestion: ability to enable/disable 2nd Virtual Screen in Full-screen mode,all,VirtualBox 5.2.18,2018-09-27T08:52:13Z,2018-09-27T08:52:13Z,2018-09-27T08:52:13Z,"Tested on Windows host. If a 2nd Virtual Screen is present in the vm settings, it can only be enabled and disabled while the VM is running if the vm is not in Full-screen mode. This can be done from the ""Virtual Screen 2"" menu item in the ""View"" menu. Once Full-screen mode is active, the ""Enable"" menu item from this menu disappears and only ""Use Host screen 1"" etc are available.

To disable ""Virtual Screen 2"", you must now first exit Full-screen mode, uncheck the ""Enable"" menu item that is then present in windowed mode, and then re-enter Full-screen mode. 

The suggestion is to show the ""Enabled"" menu-item for the Virtual Screen menu's also in Full-screen mode, so that exiting and re-entering Full-screen mode would no longer be necessary. ",Jeroen V
18004,Can't restore state of Windows XP guest machine when playing games,Windows,VirtualBox 5.2.18,2018-09-23T08:33:53Z,2018-09-23T08:33:53Z,2018-09-23T08:33:53Z,"Hello.

I have a '''Windows XP SP3 guest machine'''. It's running fine and I can pause it, close (with saving state option) and restore it when I'm in desktop.

When I play games and I want to do the same, '''I'm getting error (unknown software exception) in application in localization'''. 

'''So what I'm doing is:'''
1. Start the game.
2. Pause machine once games has loaded.
3. Close machine by saving its state.
4. Open machine with its saved state.

I tried two games: Superbike 2001 and International Rally Championship. Both produce similar error.",Mtik
18003,Error -104 in supR3HardenedWinReSpawn,other,VirtualBox 5.2.18,2018-09-22T21:46:28Z,2018-09-22T21:57:30Z,2018-09-22T21:57:30Z,"VirtualBox fails when launching any VM. 
Tried reinstalls and also reverting to older 4.x versions and other suggestions. Always fails with the same error.

OS: windows 10
VB: 5.2.18 (also other 4.x versions)

",vbfxuser
17978,Menuet64 intelhda does not work anymore,other,VirtualBox 5.2.18,2018-09-11T05:44:01Z,2018-09-16T15:41:57Z,2018-09-16T15:41:57Z,"Menute64 boots fine on latest VB versions. However when updating form 5.1.30 to 5.1.38, initializing audio driver intelhda crashes VB. Included vbox.log (5.2.0).

M64 driver init while running: Menu->System->Setup (autom.driver search) (apply for audio)

Audio testapp at Menu->Coding->audio(.asm)

Menuet 64bit available at Menuetos . net / download area

Running VB on Windows 7 Home Service Pack 1, Intel Core i3, M 380, 2.53Ghz

",MikaelM
17985,VM stop working,Windows,VirtualBox 5.2.18,2018-09-13T08:01:33Z,2018-09-13T08:01:33Z,2018-09-13T08:01:33Z,"Hi.
Very often a Windows 10 virtual machine crashes.
The error message says to open a ticket and send the log files.
From the logs I could not understand why.

I attach log files.

Best Regards
Paolo",paolo_len
17982,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Windows,VirtualBox 5.2.18,2018-09-12T09:53:20Z,2018-09-12T09:53:20Z,2018-09-12T09:53:20Z,"Hello, i have virtual machine with Win 7 Pro x64, on Win 10 x64 host. Last week it was fully functional, but when I started it today it shows me an error VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) and virtual machine stops working. When I start virtual machine in safe mode, it is working fine, but in normal mode don't :(
I' ve attached logs.
Thanks for any advice.",petrsk
17972,vboxsf module crashes guest OS after accessing host-side symlinks in shared folder,Linux,VirtualBox 5.2.18,2018-09-07T16:21:10Z,2018-09-07T17:11:50Z,2018-09-07T17:11:50Z,"Host OS: Windows 7 x64 Enterprise[[BR]]
Guest OS: CentOS 7 x64, kernel 3.10.0-862.11.6.el7.x86_64

Scenario:
* A shared folder is configured, with host path ""d:\VirtualBox Shared"", under name ""shared"".
* HOST: Create a file symlink d:\VirtualBox Shared\2\test.txt pointing to a file C:\Temp\test.txt:[[BR]]
{{{
C:\>mklink ""d:\VirtualBox Shared\2\test.txt"" c:\Temp\test.txt
symbolic link created for d:\VirtualBox Shared\2\test.txt <<===>> c:\Temp\test.txt
}}}
* GUEST: try to access the symlink (in the last output, the link target is blinking, indicating it's inaccessible):
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
cp: cannot stat ‘/media/sf_shared/2/test.txt’: No such file or directory
flint@localhost / $ ls -l /media/sf_shared/2/test.txt
lrwxrwx--- 1 root vboxsf 0 Sep  7 18:39 /media/sf_shared/2/test.txt -> C:/Temp/test.txt
}}}
* HOST: Delete the link and replace it with a plain file:
{{{
C:\>del ""d:\VirtualBox Shared\2\test.txt""

C:\>copy nul ""d:\VirtualBox Shared\2\test.txt""
        1 file(s) copied.
}}}
* GUEST: try to acccess the replaced file again:
{{{
flint@localhost / $ cp /media/sf_shared/2/test* /tmp
}}}

Result: guest OS crashes and reboots. My friend helped with analyzing the dump, and concluded that the crash occurred in the vboxsf.ko module. Most of the dentry->d_inode->i_op callback fields on this file have zero values (all of them, except for getattr and setattr).

The dmesg is attached; kernel core dump can be downloaded from here:
https://drive.google.com/open?id=1yFrDInJg8bgWXv-8kErs31W8Vn90aRYo",Konstantin Vlasov
17967,Shared Folders from Linux Guest VM not accessible,Linux,VirtualBox 5.2.18,2018-09-02T03:45:25Z,2018-09-02T03:45:25Z,2018-09-02T03:45:25Z,"After an update from Arch Linux 4.15.12-1 to 4.18.3 the use of shared folders in a Linux Guest VM is broken. The VirtualBox drivers were updated from 5.2.8 to 5.2.18.

During the build of my Arch Linux I performed the following steps:
I created a file /etc/modules-load.d/virtualbox.conf with three lines:

{{{
vboxguest
vboxsf
vboxvideo
}}}

Then I entered:

{{{
pacman -S virtualbox-guest-modules-arch
pacman -S virtualbox-guest-utils
systemctl enable vboxservice.service
reboot

}}}

My Arch Linux systems were running without problems for more than a year. I had several updates in between. After the last update I can’t access the files on the Windows host via shared folders.
Every time I boot I get the following error message in front of the login prompt:
vboxsf: Old binary mount data not supported, remove obsolete mount.vboxsf and/or update your VBoxService.

My mount as a user in .bashrc doesn’t work:

{{{
sudo mount -t vboxsf D_DRIVE /home/peter/d
}}}


I have tried a lot to find a solution. I have renamed or removed the following files:

{{{
/usr/lib/virtualbox/mount.vboxsf
/usr/bin/mount.vboxsf
/etc/modules-load.d/virtualbox.conf
}}}


----

Then I have built a completely new Arch Linux VM system with Kernel 4.18.5. I know that since kernel 4.16 the modules vboxguest and vboxvideo are integrated into the kernel.
I don’t get the error message, but I can not mount as root:

{{{
mount -cit vboxsf D_DRIVE d
}}}


I have tried to blacklist the vboxguest module and install the drivers like above. Then I get the error message.

I think there is a bug in the vboxguest modules.
",PeterE
17955,fullscreen and gpu passtrough,other,VirtualBox 5.2.18,2018-08-25T22:49:27Z,2018-08-26T15:11:35Z,2018-08-26T15:11:35Z,windows User account control (run app like admin) does not work in fullscreen. Also I want gpu passtrough. I installed windows vista. Other OS was not tested. Internet is slow like turtle and it sometimes show latency error. I installed extensions and guest additions by iso. My device is asus g750jh with windows 10 insider preview 17744.,puppygamer1994
17953,supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll,Linux,VirtualBox 5.2.18,2018-08-23T21:16:34Z,2018-08-24T14:12:37Z,2018-08-24T14:12:37Z,"VM boot fails with following error in the VBoxHardening.log

768.1808: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -22900 (0xffffa68c)) on \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Error (rc=0):

768.1808: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 cHits=4 \Device\HarddiskVolume3\Windows\System32\shell32.dll

768.1808: Fatal error:

768.1808: supR3HardenedDllNotificationCallback: supR3HardenedScreenImage failed on 'C:\Windows\system32\SHELL32.dll' / '\??\C:\Windows\system32\SHELL32.dll': 0xc0000190

1d50.15d4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1651 ms, the end);

1b18.ac8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2014 ms, the end);
",IvanP2017
17952,5.2.18 - Windows 10 Pro Host 64-bit only supports 32-bit OS.,Linux,VirtualBox 5.2.18,2018-08-23T02:53:36Z,2018-08-23T05:20:54Z,2018-08-23T05:20:54Z,"In Setting-General for Linux virtual machine, Type: Linux Version: only displays 32-bit OS.  Need 64-bit OS as in past.",BigAlKC
17948,Saving a Linux VM (Debian) crashes very often,Linux,VirtualBox 5.2.18,2018-08-22T15:49:52Z,2018-08-22T15:49:52Z,2018-08-22T15:49:52Z,"I have a Windows 10 host system where VirtualBox 5.1.28 is installed.
In one VM I installed Linux Debian Stretch.

Starting and running that Linux system works fine.
However when closing the VM by saving its state, the saving process crashes in about 7 out of 10 cases.

A windows with these error messages is shown (translated back from German so it might not be totally correct):

The state of the virtual machine could not be saved.

Details: The object is not ready
Error code: E_ACCESSDENIED (0x80070005)
Component: SessionMachine
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}


These crashes also occured in older versions of VirtualBox (5.1.x).

I could not notice this crashing behaviour with other VMs running a different flavour of Linux (Centos).

",DonJuan
17834,PGM: Failed to procure handy pages; rc=VERR_GMM_HIT_VM_ACCOUNT_LIMIT,Windows,VirtualBox 5.2.2,2018-06-22T04:36:45Z,2018-06-22T04:36:45Z,2018-06-22T04:36:45Z,"Bug reproduce:
- Set guest memory balloon to maximum value
- Power on VM and make it crash, Ex: driver failure
- Windows guest will be restarted after crash
- Error will be occurred while VM restart

Error cause:
- When guest crashed, ballooned pages are not cleanup

Suggest fix:
- Cleanup all ballooned pages when VM state change to RESETTING",AnhNN
17401,Snapshot saved state discarding,all,VirtualBox 5.2.2,2017-12-26T04:01:27Z,2018-01-17T07:33:42Z,2018-01-17T07:33:42Z,Can't find an option to discard a snapshot saved state. I.e. discard its running instance saved memory leaving the drive snapshot. If you made a snapshot of a running machine then its memory is saved forever too. This ram state is probably responsible for the most of its snapshot size.,GnomeUser
17446,Multiple pointing device reported when choosing USB Multi-Touch Tablet,other,VirtualBox 5.2.2,2018-01-10T18:14:05Z,2018-01-16T14:41:00Z,2018-01-16T14:41:00Z,"I'm running Android x86 in VirtualBox (I know, it is not a supported guest), on a Windows host, running on a machine with a touch screen. I'm trying to have a proper touch behavior in the virtual machine, ideally without having to forward the USB device of the touch screen to the VM (this is causing issues where the USB driver would eventually detach itself and stop responding. But this is not the point of my post). 

I've tried the differents ""Pointing device"" of the ""System/Motherboard"" settings tab. At first none of them seemed to give me the expected behavior in my host, but then I realized something:

If I enable USB Tablet, I can check from the Android command line (running the ""dumpsys input"" command) that this particular input device is present:

7: VirtualBox USB Tablet
    Classes: 0x800000004
    Path /dev/input/event3
    [...]

However, it doest not behave like a proper touch screen. 

If I enable USB Multi-Touch Tablet, the touch seems broken too. But if I inspect the available input devices in Android, I can see that both devices are present:

7. VirtualBox USB Multi-Touch
    Classes: 0x80000014
    Path: /dev/input/event4
    [...]

8. VirtualBox USB Tablet
    Classes: 0x800000004
    Path /dev/input/event3
    [...]


After inspecting the touch events in the Android guest, I realized that the presence of both devices is the cause of my incorrect touch behavior. When I touch the screen, the Virtual Box Multi-Touch device reports the event, but as soon as I move my finger around, the touch is ""intercepted"" by the VirtualBox USB Tablet device.

To confirm that, I deleted the /dev/input/event3 file (the one mapped to the VirtualBox USB Tablet device). After that everything was correct. The touch screen was working properly and only the proper device was handling the touch.

So, I think there is an issue with the actual pointing devices when choosing VirtualBox USB Multi-Touch tablet. VirtualBox USB Tablet shouldn't be reported by the guest OS in that case.",Cyrrus30
18240,audio clips are truncated at the end,Windows,VirtualBox 5.2.20,2018-12-27T18:28:14Z,2019-02-08T11:01:38Z,2019-02-08T11:01:38Z,"VirtualBox [v5.2.20 and 5.2.22] stops playing audio clips before they finish.

I had this issue somewhere back around ???[v5.1.26/27]???, but is was corrected shortly there after.

The issue has now resurfaced since v5.2.18.

I was keeping up with updates, but was not using the audio applications.

I downgraded to v5.2.18 and plan on staying {safe} with v5.2.18 just because I know the audio is still working correctly.

Just FYI, Tracey

If anyone cares, maybe the archived versions (5.2.20 and 5.2.22) should be fixed as well.",Tracey
18251,Unable to mount shared windows folder to Linux via VirtualBox,Linux,VirtualBox 5.2.20,2018-12-30T17:54:34Z,2018-12-30T20:57:08Z,2018-12-30T20:57:08Z,"Unable to mount shared windows folder to Linux via VirtualBox

I am following steps mentioned in the below below blog 
https://blogs.sap.com/2017/09/04/newbies-guide-installing-abap-as-751-sp02-on-linux/

I am using Version 5.2.22 r126460 (Qt5.6.2) VirtualBox - I installed Linux  openSUSE-Leap-42.3-DVD-x86_64.iso version. 

The config goes through fine in Virtual Box but when I look for the cd /media/sf_s4installer folder ( media folder) - it is not available in Linux. 

Please help. 

Thanks,
Rama 
",Rama
18117,vboxsf filesystem doesn't handle no extension file name,Linux,VirtualBox 5.2.20,2018-11-08T20:33:06Z,2018-11-12T16:32:23Z,2018-11-12T16:32:23Z,"I am using VirtualBox version 5.2.20. 
My virtual machine (Ubuntu Linux) is running Windows 10.
I set up shared folders and it mounted with -t vboxsf on the Ubuntu.

Here is error case with vboxsf filesystem: I created "".new.test1."" file but it created "".new.test1"" file.
{{{
chwon@chwon-VirtualBox:~/sandbox/tmp$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls -la
total 5
drwxrwxrwx 1 chwon chwon    0 Nov  8 15:12 .
drwxrwxrwx 1 chwon chwon 4096 Nov  8 15:11 ..
-rwxrwxrwx 1 chwon chwon    6 Nov  8 15:12 .new.test1
chwon@chwon-VirtualBox:~/sandbox/tmp$ 
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1.
ls: cannot access .new.test1.: No such file or directory
chwon@chwon-VirtualBox:~/sandbox/tmp$ ls .new.test1
.new.test1
}}}

I did same test on Linux ext4 filesystem.
{{{
chwon@chwon-VirtualBox:~/tmp/test$ echo ""hello"" > .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls -la
total 12
drwxrwxr-x 2 chwon chwon 4096 Nov  8 15:28 .
drwxrwxr-x 4 chwon chwon 4096 Nov  8 15:28 ..
-rw-rw-r-- 1 chwon chwon    6 Nov  8 15:28 .new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1. 
.new.test1.
chwon@chwon-VirtualBox:~/tmp/test$ ls .new.test1
ls: cannot access .new.test1: No such file or directory
}}}

",Arirang
18114,Tray task start looping after dragging a file object from Host to Guest,Windows,VirtualBox 5.2.20,2018-11-07T12:20:49Z,2018-11-11T11:02:40Z,2018-11-11T11:02:40Z,"When I try to drag file objects from my Windows 10 1803 64bit Host-Desktop to the Desktop of Windows 10 1803 32 bit Guest, VirtualBox Guest Additions Tray Application immediately starts to loop during creating interrupts. After passing to the Guest windows, the drag indicator changes ""Cannot drop"".

This is fully reproducible. When dragging extremely slow, the drop may succeed.",SchweizerGarde
18119,Linux Mint 19 freezes when resizing Window,Linux,VirtualBox 5.2.20,2018-11-10T14:14:49Z,2018-11-10T14:14:49Z,2018-11-10T14:14:49Z,"Sometimes when I maximize the virtual machine window the guest OS freezes.  I am running Mint 19 guest on Windows 10 Host.
",Motoko
18111,Always in Snapshot-View - 5.2.20,Windows,VirtualBox 5.2.20,2018-11-06T08:01:53Z,2018-11-06T17:31:43Z,2018-11-06T17:31:43Z,"My english isn't so good to translate my problem:
https://forums.virtualbox.org/viewtopic.php?f=5&t=90176",VM-F4n
18109,Error when drag-and-drop zero length files from guest to host,Windows,VirtualBox 5.2.20,2018-11-05T21:50:45Z,2018-11-06T06:41:33Z,2018-11-06T06:41:33Z,"Version: 5.2.20, 5.2.18
Host: Windows 7 SP1
Guest: Windows 7 SP1 RU/EN, Windows XP SP3 RU
Guest additions: installed according to VirtualBox version

Error occurs when dragging zero length file from guest to host:
{{{
Drag and drop operation from guest to host failed.
Current drop operation still in progress.
Result Code: E_FAIL (0x80004005)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Same error occurs when dragging folder with zero-length file from guest to host.

After that error any other drag-and-drop operation even with non-enpty files fails with error:
{{{
Drag and drop operation from guest to host failed.
Another drop operation already is in progress.
Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}

Steps to reproduce:
1) Install guest Windows 7 or Windows XP (any language in to the VB) 
2) Install VB Additions
3) Turn on drag-and-drop from guest to host (or bidirectional)
4) Drag and drop any non-zero-length file to check that it works
5) Create any new empty file (for ex. new notepad document)
6) Drag it from guest to host
7) Get error

It is possible to ""reset"" the satuation by trying to drag any file from host to guest. May be not immediately, may be couple of times.
I did not find exact scenario. 
Sometimes attempts to drag files from host to guest after error leads to guest interface partially hang. In that case shutdown procedure asks to forcibly close VBoxTrayDnDWnd.

Additional: errors appear in host log files, not in guest.
",yumashka
18059,Upgrade to 5.2.20 breaks usb passthrough,all,VirtualBox 5.2.20,2018-10-18T09:21:20Z,2018-11-05T15:10:52Z,2018-11-05T15:10:52Z,"Host : Windows 10 Enterprise 1607

Upgraded Virtualbox to 5.2.20 from 5.2.18 with extension pack and USB passthrough does not detect any connected devices. Downgrading Extension pack to 5.2.18 does not resolve the issue, downgrading Virtualbox to 5.2.18 solves it.

I can upgrade again to collect any logs you want to help you solving this bug

Regards",3mptyy
18092,Guest editions won't install in new Windows 10 1809,Windows,VirtualBox 5.2.20,2018-10-31T18:27:11Z,2018-10-31T20:21:13Z,2018-10-31T20:21:13Z,"As soon as guest edition installation is run on Windows 10 1809 host, the mouse and keyboard stops working. The installation can never be completed because it is impossible to respond to UAC prompt. Tried reboot several times, windows updates, didn't fix the issue.",Skippy
18088,guest additions fail to compile against kernel 4.19,Linux,VirtualBox 5.2.20,2018-10-29T14:55:48Z,2018-10-30T17:08:44Z,2018-10-30T17:08:44Z,"Here is the link for the errors I get:
https://paste.pound-python.org/show/ohbTEHj8QWpqgz3vjxWS/

Best regards,
Serge",pourpier
18085,Audio ICH AC97 Host Win7 x64 troubles 5.2.x and 6.x BETA,Windows,VirtualBox 5.2.20,2018-10-27T03:57:30Z,2018-10-29T11:11:53Z,2018-10-29T11:11:53Z,"Guest - Windows 7 SP1 x64 and Windows XP SP2 x64 - with '''ICH AC97''' audio will not work in/with Host Windows 7 SP1 x64.[[BR]]
The same troubles in 5.2.x and 6.x Beta.[[BR]]
But no troubles with Host Windows XP SP2 x64.
Have a look in the attached LOG at line 1429:[[BR]]
DSound: Creating capture buffer failed with E_FAIL[[BR]]
[[BR]]
Harry",Harald Welkovics
18084,Audio ICH AC97 Host Win7 x64 troubles 5.2.x and 6.x BETA,Windows,VirtualBox 5.2.20,2018-10-27T03:53:58Z,2018-10-27T16:12:52Z,2018-10-27T16:12:52Z,"Guest - Windows 7 SP1 x64 and Windows XP SP2 x64 - with '''ICH AC97''' audio will not work in/with Host Windows 7 SP1 x64.[[BR]]
The same troubles in 5.2.x and 6.x Beta.[[BR]]
But no troubles with Host Windows XP SP2 x64.",Harald Welkovics
18076,Linux Mint 19 guest using Touch Keyboard in Windows 10 host not working with some keys,Linux,VirtualBox 5.2.20,2018-10-24T13:17:02Z,2018-10-26T00:42:48Z,2018-10-26T00:42:48Z,"I am having problems with Windows 10 the full touch keyboard not the basic one with the arrow keys, Shift and space bar not working and it is in USB Tablet mode. The strange thing is that basic touch keyboard work with space bar, but arrow keys still not working.",Motoko
18062,VirtualBox Application Error - memory could not be read,Linux,VirtualBox 5.2.20,2018-10-18T15:34:24Z,2018-10-18T15:34:24Z,2018-10-18T15:34:24Z,"Updated from 5.2.18 to 5.2.20 last night (with Guest Additions) and left for the day.  Since this morning, two similar crashes - the second is below and attached.  I've updated to Win10 Pro (1809) last week (from previous patch level).  Some additional information that I suspect as relevant ... Dell laptop with Dell D1000 USB3.0 Dock (DisplayLink driver).  Main video, Wired Internet, and USB is run through the dock.

The instruction at 0x00007FFF24DBD680 referenced memory at 0x0000000000000010. The memory could not be read.",Brewsters
18148,Audio hangs when host screen turns off,Windows,VirtualBox 5.2.22,2018-11-22T21:02:16Z,2019-01-24T10:16:52Z,2019-01-24T10:16:52Z,"I upgrade to 5.2.22 from 5.2.20 because it should fix the problem, according to the changelog:
""Audio: fixed a regression in the Core Audio backend causing a hang when returning from host sleep when processing input buffers"".

But it's not, at least for me. Tested under W2k8 R2 (host) and W7 (guest).
Once the screen enter into power save mode, the audio hangs until I shutdown the guest machine (rebooting the machine doesn't solve the problem).",IzK
18173,Bridged Adapter not working version 5.2.22,Windows,VirtualBox 5.2.22,2018-12-07T03:26:14Z,2019-01-18T02:44:59Z,2019-01-18T02:44:59Z,"Using Bridged Adapters with Windows 10 Host and Windows 10 Guest fails to work as expected. The host and the guest can not ping each other , neither can the guest ping anything outside of its own machine. 

This issue I have narrowed down to having a locally administered MAC address with in the Guest machine.  While the work around is to use the VirtualBox setting as the MAC address - this is not the preferred method for portability of the Disk Image File. I had narrowed it down by swapping the bound network interface lan and wifi to network 1 and network 2 and then reversing that - disabling the first network with in the guest (which had the locally administered address) - everything then worked - and I only realized it was the MAC address being locally administered within the guest - because I needed to set it for Network2 at which point everything failed to communicate again. 
I then administered the local mac in the Vbox Settings network page. I would prefer this to be with in the image itself in network properties. If I have several images with the same locally administered MAC , I would think the VBox Bridge would act as the router hop so that I could  have multiple of this image on the same network.



",Ken The Eskimo
18229,CentOS VM does not start after virtual guest additions 5.2.22 upgradation,Linux,VirtualBox 5.2.22,2018-12-24T07:43:04Z,2018-12-24T22:28:28Z,2018-12-24T22:28:28Z,"My CentOS VM was running fine in Windows 10, Virtualbox 5.2.18 . But after updating it to 5.2.22 and installing the guest additions 5.2.22, it does start. It gives error during boot : Job x11vnc.service/start deleted to break ordering cycle started with multi-user.target/start. My Caps lock led keeps blinking and I have to shutdown the VM.",anupam.m
18188,WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX,Windows,VirtualBox 5.2.22,2018-12-16T16:34:41Z,2018-12-18T23:14:41Z,2018-12-18T23:14:41Z,"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY.",dannyo1
18184,arp fails when connecting to a wireless connection on host via bridged network,other,VirtualBox 5.2.22,2018-12-15T08:46:29Z,2018-12-18T13:51:03Z,2018-12-18T13:51:03Z,"Host: Windows 10 Pro
Guest: eCS 2.2 beta (drivers: all the latest and greatest)

From the guest, I am trying to connect to a wireless connection on the host. For sake of simplicity and performance I have set up ""bridged network"".

Sometimes but not always I have problems to access the net from the guest. When that happens, I see this (example) in the ARP table of the guest:

""arp -a"":

ARP table contents:
{{{
interface   hardware address   IP address       minutes since last use
lan 0       (incomplete)       www.xxx.yyy.zzz  0
}}}
Apparently, the ARP request does not pass through. If I reboot the guest a couple of times AND if I actually use the wireless connection on the host, then eventually, I will be able to access the wireless connection from the guest.
I have not observed this problem with a wired connection (on the host). This seems to always work ok.",lerdmann
18190,WINDOWS 10/HP UPDATED CAN NOT OPEN VIRTUAL BOX,Windows,VirtualBox 5.2.22,2018-12-16T18:22:02Z,2018-12-17T12:03:43Z,2018-12-17T12:03:43Z,"AFTER WINDOWS 10/HP UPDATE VIRTUAL BOX WOULD NOT OPEN.
I TRIED THE VIRTUAL BOX 6.0 TEST BUILD BUT FILE RUN HAD ERRORS.
I TRIED UPDATING VIRTUAL BOX 5.2.23 EXE, EXT AND GUEST ADDITIONS.
I ATTACHED A SCREEN SHOT OF THE VIRTUAL BOX OPENING SCREEN.
I DO NOT HAVE A LOG FILE AVAILABLE.

REALLY APPRECIATE ANY HELP.
THANKS, DANNY.",dannyo1
18186,Audio Lipsync Problem with VBox 5.2.22,Windows,VirtualBox 5.2.22,2018-12-15T17:07:46Z,2018-12-15T17:28:58Z,2018-12-15T17:28:58Z,"When I upgraded to VBox 5.2.22 I get audio lipsync errors in games using the 3D support from the extensions pack disk.

Downgrading back to VBox 5.2.18 the audio lipsync is fine again.

I am using Windows 7 Home Premium 64bit as the host and Windows XP 32bit as the guest.

I can run OFP GOTY edition (Bohemia Interactive Operation Flashpoint) very well under these conditions, I do this because it is impossible to install video drivers for my hardware into Windows XP and the game will only run under Windows XP.
",Solrac42
18181,"Windows guest, Linux host: copying directories from host to guest copies top-level directories only, not contents",Linux,VirtualBox 5.2.22,2018-12-13T17:36:44Z,2018-12-13T18:25:21Z,2018-12-13T18:25:21Z,"Virtual Box test build 5.2.23
Host: Windows 8.1 x64
Guest: Linux Mint 19.1 x64 beta, Cinnamon.

Guest Additions installed. Bidirectional clipboard enabled.

Copying directory D1, with contents directory D2 and file F1, copies only D1.

The same setup, but with a Linux Mint 19.0 host, does not seem to have the problem.",JN
18175,"Windows 10 build 1709 build 16299 64bit VM is not working showing error as ""Error In supR3HardenedWinReSpawn""",other,VirtualBox 5.2.22,2018-12-10T10:11:10Z,2018-12-10T16:19:24Z,2018-12-10T16:19:24Z,"Windows 10 build 1709 , Virtualbox is not working showing error as ""Error In supR3HardenedWinReSpawn"". Windows 10 build 1703 it was working good. After updation it's not working. Please solve the issue.",Ekanath
18166,Ryzen 1700x - no 64 bit option,Linux,VirtualBox 5.2.22,2018-12-03T00:28:38Z,2018-12-03T05:56:39Z,2018-12-03T05:56:39Z,"Hello,
- I have windows 10
- I have a ryzen 1700X.
- SVM is enabled in the BIOS.
- HyperV is not installed.
VirtualBox won't let me chose a 64 bit option for guestn or even if i try 32bit it won't let me give it more than 1 core.
thanks for the help.",Wolfkiller
18164,FUll screen with VBox 5.2.22 on windows 7,Linux,VirtualBox 5.2.22,2018-12-02T16:15:47Z,2018-12-02T17:50:11Z,2018-12-02T17:50:11Z,"Hi,
I have been using fedora as guest system on windows 7 hosted VBox since years. Yesterday I upgraded from 5.2.18 to 5.2.22 and installed also the vbox additions for it under fedora 29 (linux 4.19).
As a result of this upgrade, suddenly full screen does not work, only normal window mode as well as the adaptive mode (Host-C) are working. Switching to full screen results in the screen freezing - reacting neither to mouse nor to keyboard.",TomKov
18163,Guest property LoggedInUsers does not work with 'wait' in VBoxManage,Linux,VirtualBox 5.2.22,2018-12-02T13:54:57Z,2018-12-02T17:47:06Z,2018-12-02T17:47:06Z,"To wait for a machine to be ready for logins I used

    vboxmanage guestproperty wait <machine> /VirtualBox/GuestProperty/OS/LoggedInUsers

At some point (before 5.2.22) that stopped working. You can still 'get' that property, and it is listed with 'enumerate' for a running <machine>.",thoni56
18161,Sound truncates on Windows XP,Windows,VirtualBox 5.2.22,2018-11-30T14:36:46Z,2018-11-30T14:36:46Z,2018-11-30T14:36:46Z,"Hi

I use Windows XP for using Microsoft Encarta Encyclopedia 99. It may be a bit outdated, but just because something is a bit outdated does not necessarily mean it has lost its charm. The problem I have with Windows XP is that the sound truncates just before the sound clip ends. For example, when I hear the sound clip that is supposed to go ""That's one small step for man. One giant leap for mankind."", it actually goes ""That's one small step for man. One giant leap for--"" and all the other sound clip ends just like that and it is very annoying. I would appreciate your help.",Lukester
18160,Virtual Box machines fail to start after migration from Win7 to Win10,Linux,VirtualBox 5.2.22,2018-11-30T12:33:32Z,2018-11-30T14:31:46Z,2018-11-30T14:31:46Z,"I upgraded to Windows 10, turned off hyper-v, rebooted, etc.: I can create new 64bit machines, I can run rescue disk .iso in them but existing machines fail to start.",aivarsk
18155,Unknown fatal error!,other,VirtualBox 5.2.22,2018-11-28T15:28:51Z,2018-11-30T01:55:31Z,2018-11-30T01:55:31Z,Virtual box for Windows 7 x64.,AlnXpr
18130,VBoxGuestAdditions 5.2.22 3d acceleration not working,Linux,VirtualBox 5.2.22,2018-11-13T19:07:55Z,2018-11-28T16:46:56Z,2018-11-28T16:46:56Z,"System environment:[[BR]]

''Host OS'': Windows8 Pro 64 bit (all updates)[[BR]]

''Guest OS'': Debian 8.11 (kernel 3.16.0-4, all updates from stable branch 8.11)

After update from 5.2.20 to 5.2.22 and apply VBoxGuestAdditions.iso - 3d acceleration stopped working.

If roll back GuestAdditions to 5.2.20 (but save Vbox version 5.2.22) - 3d acceleration working again.",ilyalesnoi
18136,Audio canceled strangely with virtualbox grater than 5.2.18.,Linux,VirtualBox 5.2.22,2018-11-18T00:17:29Z,2018-11-18T00:33:05Z,2018-11-18T00:33:05Z,"== The problem ==

Starting with virtualbox 5.2.20, the audio began to not work properly for me.  When I try to play some audio, I hear the first part of the audio, but it is cut of a short time before the end. So, if I for example try to play a file containing the words ""Hello World!"", I may only hear ""Hello Wo"". If I then try to replay the file, it works exactly as previously: I only hear the first part of the file. It works with virtualbox 5.2.18, but not with 5.2.20 or later, so the bug was introduced with the 5.2.20 release.

== System ==

I am running windows 7 as host and headless arch linux as guest. I am using alsa as sound server on the guest.

== Attachments ==

I will attach VBox.log and a webm file where I try to play audio. The webm file is recorded video from the guest. I try to create a file containing ""Hello world!"", called hello.wav, with espeak. Then I try to play the file with aplay, both in userspace and as root. Audio is included so you can hear the result.

== Priority ==

This bug is very critical for me. I am blind and therefore I am partially using speech to access the screen content.

Thanks in advance!",Tage
18128,Some strings are not translatable in macOS,other,VirtualBox 5.2.22,2018-11-13T16:52:28Z,2018-11-14T19:08:34Z,2018-11-14T19:08:34Z,"In macOS some of the text is in english.
I would like the text to be translatable or removed for a more fully translation of VirtualBox.

Running the dmg file the first i see is the image from VirtualBox/.background/vbox_folder.tiff with the text:
""1 Double click on this icon:""
""2 Run the VirtualBox application
   from the Application Folder:""

Looking at other installers i have tried in macOS it seems they tend to use a way where you drag the icon to the application folder from left to right and then there might be an arrow suggesting what to do and some installations have no text.
If this is the ways its done in macOS then perhaps VirtualBox install could do it the same way so its consistent with how its done in other software and then perhaps the english text can be removed.



When i double click the installer (VirtualBox.pkg) i see some text like:
""Installer Oracle VM VirtualBox""
""Installering af Oracle VM VirtualBox""
""Oracle VM VirtualBox for Mac OS X""
""Welcome to Oracle VM VirtualBox 5.2.22 for Mac OS X! This installer...""

It seems to be from CoreServices/Installation so maybe the installer is already translated by Apple and then VirtualBox have added some strngs that is not translatable.
I would like the strings to be translatable.",scootergrisen
18125,Extention Pack  Install Error,Windows,VirtualBox 5.2.22,2018-11-12T11:21:55Z,2018-11-12T16:25:37Z,2018-11-12T16:25:37Z,"Failed to install the Extension Pack F:/Downloads/Tools/Oracle/Oracle_VM_VirtualBox_Extension_Pack-5.2.22.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-16880' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",Hercules Oberholzer
18388,"""The instruction at 0x000000006BC88A90 referenced memory at 0x0000000000000008. The memory could not be read."" when trying to open Devices > Optical Drives",Linux,VirtualBox 5.2.26,2019-01-30T10:53:05Z,2020-04-05T11:30:06Z,2020-04-05T11:30:06Z,"Im using
Host: Windows 10 Pro 64 bit v1803
VB: VirtualBox 5.2.26r128414
Guest: Ubuntu 18.04

Getting the error consistently.",custard130
18558,Shutdown gracefully upon Windows Update reboot,all,VirtualBox 5.2.26,2019-04-11T15:10:48Z,2019-04-11T15:10:48Z,2019-04-11T15:10:48Z,"On Windows 8 and up, it's difficult (at best) for users to prevent Windows from automatically rebooting after some automatic updates have been installed.

Several times, I have had one of my guest OS's running, and lost whatever was going on there when the process was killed during an automatic reboot.

My suggestion is to have options upon reboot to allow...
-- preventing the reboot
-- save guest machine state and exit
-- shut down guest machine and exit
-- power off guest machine and exit
",adaptatron
18455,Unable to create VM: Error in sup3RHardenedWinReSpawn,Windows,VirtualBox 5.2.26,2019-02-26T03:33:39Z,2019-02-26T07:02:47Z,2019-02-26T07:02:47Z,"I'm trying to run the VM that I created, unfortunately, there's a frequent error that I received. ""VirtualBox - Error in sup3RHardenedWinReSpawn"", hope to hear from y]ou soon. Thanks in advance,
",LMPadolina
18424,Host crashes when using VirtualBox,Linux,VirtualBox 5.2.26,2019-02-11T03:19:50Z,2019-02-11T03:19:50Z,2019-02-11T03:19:50Z,"The problem I have is that sometimes my host (Windows 10 laptop) crashes sometimes when I am using VirtualBox. This only happens if I close the laptop or if it goes to sleep while a VM is still running. 

Whenever the laptop goes to sleep while a VM is running, the host will shut down all applications and restart the computer. Occasionally, there will be a BSOD instead of the host just restarting. I was wondering if this is a common issue when users leave a VM running. The VM was Ubuntu 18 and the host was Windows 10.",mttwh
18612,VM window can’t be seen or activated after host’s hibernation.,Windows,VirtualBox 5.2.28,2019-04-30T06:44:13Z,2019-04-30T06:44:13Z,2019-04-30T06:44:13Z,"I have a Windows 8.1 x64 host with Windows 7 x86 guest combination. This happened only once, but I couldn’t find any similar ticket, so I file this one here. After my host was woken up from the hibernation I couldn’t activate the VM window. It can’t be seen in the taskbar, only the manager’s window is here and can be seen and activated. Beside the VM window is present in the list of the running applications (Alt + Tab) but you can’t activate it here as well. What could be done is: save the state of the VM from menu in the manager window and start it again. This way the window of VM appears in taskbar and can bee fully seen and activated. I put my logs here, probably somebody could see what went wrong here.",boxer01
18586,"After 18.04 LTS Ubuntu installation and reboot on VM with Windows7 32bit as host, the guest freezes after 1 min",Linux,VirtualBox 5.2.28,2019-04-20T16:59:40Z,2019-04-23T17:43:03Z,2019-04-23T17:43:03Z,"Hi,

I was able to successfully install the Ubuntu as my guest OS (though had lot of struggle to get there) however every time guest OS is started, it only works for few secs to a minute and then it is frozen completely.
I don't run any other program on my host OS and have monitored the resources as well to check on whether RAM is getting exhausted but i don't this so think that is happening.

Below is the Host setup that I have:
OS: Windows 7 ultimate 32 bit with 4GB Ram and Usable is 2.44GB

Virtual Box Version: 5.2.28

Below is the Guest setup that I have:
OS: Ubuntu 18.04 with 64Bit
Video Memory: 120MB
Base Memory: 1149MB
Pointing Device: USB Tablet
CPUs: 2
EFI: Enabled
3D Accelration: Disabled
Paravirtualization Interface: Default
Hardware Virtualization: Enabled Nested Paging and Enabled VT-x/AMD-V
",Dinesh
18748,bsod after installing alcohol 52% and rebooting in windows xp sp3 guest,Windows,VirtualBox 5.2.30,2019-07-08T19:55:53Z,2020-03-03T13:03:57Z,2020-03-03T13:03:57Z,"bsod after installing alcohol 52% and rebooting in windows xp sp3 guest
This problem seems to be in Virtualbox 6 also",nikitastepanov
18729,virtualbox.exe - application error when running steam on windows xp sp3 guest,Windows,VirtualBox 5.2.30,2019-06-27T18:39:54Z,2019-06-27T18:39:54Z,2019-06-27T18:39:54Z,"when running steam on windows xp sp3 guest, appears window: virtualbox.exe - application error",nikitastepanov
18702,Windows Server 2016 guest completely hangs in loading UserProfileService after upgrading GA to 5.2.30,Windows,VirtualBox 5.2.30,2019-06-11T16:00:50Z,2019-06-11T16:00:50Z,2019-06-11T16:00:50Z,"Version: VirtualBox 5.2.30
Host OS: Windows 2010 Professional
Guest OS: Windows Server 2016 Standard Version 1607 (64-bit)

on a Windows Server 2016 Standard Version 1607 (64-bit), immediately after upgrade from VBox Extensions v5.2.26 to v5.2.30 and the suggested guest reboot, Windows fails to come up completely and hangs permanently loading User Profile Service. 

""Please Wait for the User Profile Service"" with Windows startup spinner. 

PS: I have redone this 4 times after restoring from Snapshots... inclduing with the only change made the Guest Additions install. 
Note: the guest VM is running from .vmdk disks (as it was imported), but it was working fine on VBox 5.2.26, and still works fine in VBox 5.2.30 AS LONG AS I DON'T UPDATE GUEST ADDITIONS.  As soon as GA are updated to 5.2.30 + reboot, it explodes.


",mkorning
18700,Virtualbox.exe - application error when running dxdiag or hl2 in Windows XP sp3 guest,Windows,VirtualBox 5.2.30,2019-06-09T19:36:13Z,2019-06-09T19:36:13Z,2019-06-09T19:36:13Z,"When running dxdiag or hl2 in windows xp sp3 guest, appears window Virtualbox.exe - application error",nikitastepanov
18660,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",Windows,VirtualBox 5.2.30,2019-05-20T01:39:53Z,2019-05-23T09:01:44Z,2019-05-23T09:01:44Z,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",0o0o
20321,disk vmdk corrupted,Linux,VirtualBox 5.2.32,2021-04-23T17:36:32Z,2021-04-23T17:36:32Z,2021-04-23T17:36:32Z,"I want to describe my happening:
I have 2 laptops
One with Virtual box 5.2.32 r132073 (Qt5.6.2) version
One with Virtual box 6.1 version

I have first enlarged my vmdk by using VBoxmanage.exe from 10 GB to 100Gb and I have used with my Ubuntu Linux VM for developing. All right.
Then I have moved this vmdk on an external disk (1 Tera) in order to have much more space on my physical disk c:


Any days ago I have thought of create another Vm on second laptop with Virtual Box 6.1 version and use the same virtual disk after lighting my first VM on first laptop off.

So I have corrupted my virtual disk vmdk. In fact now when I use my first laptop and launch my VM I obtain this list of message:

....
...
...
...
...

...

fatal error token exceeds yylmax

  ",masdelmon
18784,Windows guests hang exactly once after each host reboot,Windows,VirtualBox 5.2.32,2019-07-23T21:53:30Z,2019-12-17T01:21:03Z,2019-12-17T01:21:03Z,"At some point during the 5.2.x series (I don't remember exactly which version), I started consistently experiencing the following problem with VirtualBox on my (64-bit) Windows 10 host.  It occurs only with my Windows (10) guests, not with my (Manjaro) Linux guest.

Whenever I reboot the host, after restarting VirtualBox and my VMs, each Windows guest (but not the Linux one) will freeze exactly once, very soon after its first startup.  When it freezes, if I try to close the window, which causes the ""power off / send reset / etc."" dialog box to come up, then whatever I choose, nothing happens; instead, that dialog box also freezes.  If I choose ""power off"", for example, the guest window does not close.  Then I click the 'x' to close either the dialog box or the host window, and it simply disappears (leaving the guest in the aborted state).

After I restart the guest, it remains up for a very long time.  It never freezes again on the second or ensuing startups, until after I reboot the host again.

This has been happening on all 5.2.x versions since the first one on which it happened (alas I don't remember which one that was).  I'm unable to use 6.0.x because of ticket #14366, so I'm not sure whether the bug also exists there or not.  I think I have had at least one VM freeze on 6.0.10 while checking to see whether ticket #14366 still existed there (it does), so perhaps this bug does still exist on 6.0.x, but I didn't run long enough (because of ticket #14366) to confirm that it was the same behavior (i.e. successful long-term operation on the second and ensuing guest reboots, with the problem recurring only after the next host reboot).",rokopt
19017,Updated to 5.2.34 and now VM constantly crashes,other,VirtualBox 5.2.34,2019-10-16T03:26:26Z,2019-10-16T03:29:55Z,2019-10-16T03:29:55Z,"See attached log.

This is running Win9x DOS and using dos network support.
",dfatvb
19256,VBoxManage copyfrom --target-directory fails to copy,Windows,VirtualBox 5.2.36,2020-01-22T11:40:16Z,2020-02-14T21:34:40Z,2020-02-14T21:34:40Z,"""copyfrom --target-directory"" fails on Windows 7 host with Windows XP/Windows 7 guests in VirtualBox 5.2.34 and 5.2.36.
The fix of #18724 seems to break this.
{{{
>""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" guestcontrol vm_win7 copyfrom -v --username User --password 123 --target-directory D:\log C:\Users\User\Desktop\1.txt
Creating guest session as user 'User'...
Waiting for guest session to start...
Successfully started guest session (ID 1)
Copying from guest to host ...
Directory ""D:\log\"" already exists
Source: C:\Users\User\Desktop\1.txt
Copying ""C:\Users\User\Desktop\1.txt"" to ""D:\log\"" ...
0%...
Progress state: VBOX_E_IPRT_ERROR
VBoxManage.exe: error: Opening/creating destination file on host ""D:\log\"" failed: VERR_PATH_NOT_FOUND.
VBoxManage.exe: error: Error processing ""C:\Users\User\Desktop\1.txt"", rc=VERR_GENERAL_FAILURE
Closing guest session ...
}}}

When I try without --target-directory,
{{{
                      copyfrom [common-options]
                      [--dryrun] [--follow] [-R|--recursive]
                      <guest-src0> [guest-src1 [...]] <host-dst>
}}}
<host-dst> is written from start but not replaced. This corrupts <host-dst> if a smaller file is copied.
",robpats
19409,Windows 98: Arbitrary corruption of files in guest OS,Windows,VirtualBox 5.2.38,2020-03-16T23:48:11Z,2020-03-17T00:01:31Z,2020-03-17T00:01:31Z,"1. Create a VM for Win98 and install Windows 98SE there.
2. Inside this VM, install Total Commander 9.51rc3 (the exact version is important!).
3. Make a backup copy of the TC installation folder.
4. Start TC, then exit it (if you're lucky enough that it does not crash).
5. Compare the TOTALCMD.EXE file contents with the one from the backup copy (for example, you can have another version of TC installed into another directory; there is a built-in function for comparing files).

Result: The file contents is different from what it was initially.

Expected result: The file should not change, because Total Commander does not modify its own executable. This was confirmed by the author of TotalCmd, but just in case I also monitored the situation with Sysinternals FileMon. During the whole period from launching Total Commander to its exit, FileMon showed absolutely NONE write operations to the totalcmd.exe file by any process in the system. And still, the file ended up being modified.

The corruption always happens on cluster-level; that is, the changes always consist of one or more cluster-sized chunks (4096 bytes on my guest file system). The exact position and contents of the corrupted data may vary in different experiments.

The issue can be reproduced in VirtualBox 5.2.36 and 5.2.38. With 5.2.34 I could not reproduce it. For some reason, I could reproduce this issue only with that particular version of Total Commander; neither rc2 nor rc4 seem to trigger the corruption scenario. If the version 9.51rc3 is no longer available at the official web site at some later time, it can still be downloaded from here: http://totalcmd.net/beta/tc951x32_rc3.exe (the authenticity can be validated by the digital signature).

I understand that Win98 is completely outdated, but it's a really serious bug causing data loss! And since I don't know what causes it, I cannot be sure if it does not affect any other guest OS.

I've looked at the log files, but they contain nothing at all at the moment of the experiment. Just in case, I'll attach the log file, but you can see it's empty between 13.5 seconds (when the OS started) and 26-something minutes, when I shut down the guest OS after performing the experiments.",Konstantin Vlasov
19353,Bad installiation on Windows XP 32 bits.,all,VirtualBox 5.2.38,2020-02-27T08:03:11Z,2020-02-27T08:04:22Z,2020-02-27T08:04:22Z,"Hello. I had the installed version of Virtualbox 5.2.36 r135684. I tried installing update 5.2.38. It did not install, the program did not reach the end of the installation process. I don’t know if there were driver updates. Just in case, I inform you that there were no dialog boxes offering to install drivers. I saw only the green line of the installation indicator for a long time (more than an hour) and the button to stop the installation.",hellodearfriends
17515,VBoxManager gets into a bad state,Linux,VirtualBox 5.2.4,2018-01-31T21:28:23Z,2020-08-19T18:56:17Z,2020-08-19T18:56:17Z,"
simple repro on windows, foo.bat:


    set VBOX=""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe""

    :loop
    %VBOX% controlvm ""%1"" poweroff
    %VBOX% snapshot ""%1"" restorecurrent
    %VBOX% startvm ""%1""

    goto loop


this results in a bunch off issues, including:


VBoxManage.exe: error: The machine 'box' is already locked by a session (or being locked or unlocked)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp


VBoxManage.exe: error: Invalid machine state: PoweredOff (must be Running, Paused or Stuck)
VBoxManage.exe: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component ConsoleWrap, interface IConsole, callee IUnknown
VBoxManage.exe: error: Context: ""PowerDown(progress.asOutParam())"" at line 578 of file VBoxManageControlVM.cpp


and eventually it dies:

Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Snapshot operation failed
VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleSnapshot(struct HandlerArg *)"" at line 539 of file VBoxManageSnapshot.cpp
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""LaunchVMProcess(a->session, sessionType.raw(), Bstr(strEnv).raw(), progress.asOutParam())"" at line 600 of file VBoxManageMisc.cpp

at this point a full restart of all VBox processes is required.
",spongman
17455,Host USB is locked after shared folders were added,Windows,VirtualBox 5.2.4,2018-01-14T22:47:04Z,2019-01-27T22:12:20Z,2019-01-27T22:12:20Z,"I have a USB Stick with Windows 10 Installation files on it. If this stick is attached and I added some folders in the VM, I simply can’t eject it in the host Windows, because it is constantly locked. Even if I add some folders not on the USB drive. After I used a Process Explorer I could see, that there is a handle to the setup.exe on the USB. I attached the logs, because there one can see, that this is hardening issue. The only way to solve it right now is either kill the handle or close VM. This started way back, as hardening was added.",boxer01
17461,writethrough affected by snapshots,Windows,VirtualBox 5.2.4,2018-01-16T18:53:26Z,2019-01-26T03:29:12Z,2019-01-26T03:29:12Z,"I made this critical because not everyone will check for correct functionality. Restoring a snapshot will cause an unexpected data loss on a drive of type writethrough.

I've got a VM with a main drive and an attached writethrough drive. I see twice as many .vdi files than .sav files in the snapshot directory. And yes a restore changes the writethrough drive.


C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi[[BR]]
UUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx[[BR]]
Parent UUID: base [[BR]]
State: created [[BR]]
Type: writethrough [[BR]]
Location: E:\DataW10.vdi [[BR]]
Storage format: VDI Format [[BR]]
variant: fixed default [[BR]]
Capacity: 4096 MBytes [[BR]]
Size on disk: 4098 MBytes [[BR]]
Encryption: disabled [[BR]]
In use by VMs: Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)",Loafer
17443,Drag and drop operation from guest to host failed - Occurs when trying to move a file with 0kb file size -> fixed in 5.2.20,Windows,VirtualBox 5.2.4,2018-01-10T05:00:34Z,2018-11-29T12:37:48Z,2018-11-29T12:37:48Z,"Windows XP guest

After receiving this error I started transferring files one at a time and noticed that empty text documents with a file size of 0kb were causing the error.

Error info:

{{{
Drag and drop operation from guest to host failed.

Another drop operation already is in progress.

Result Code: E_INVALIDARG (0x80070057)
Component: GuestDnDSourceWrap
Interface: IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

}}}

Each time the error occurs, I can no longer move any files and must restart the virtual machine.

VirtualBox does not crash, however
When exiting the machine there is an Application Error

Error Details:

{{{
The instruction at 0x00007FF8C4742C98 referenced memery at 0x0000000000000028. The memory could not be read.
}}}



",lukemeow
17423,Oracle Linux 6 Booting Error From vboxadd,Linux,VirtualBox 5.2.4,2018-01-05T23:20:07Z,2018-02-15T01:41:36Z,2018-02-15T01:41:36Z,"When booting version 6 of Oracle Linux (4.1.12-112.14.2.el6uek.x86_64 in this case but failed in previous ones) in the vboxadd script. This is because the log is not yet initialized. By adding line 256 shown below, the error no longer occurs and the script completes.

    253     fi  # INSTALL_NO_MODULE_BUILDS
    254 
    255     # Put the X.Org driver in place.  This is harmless if it is not needed.
    256 log ""Dons fix.""
    257     ""${INSTALL_DIR}/init/vboxadd-x11"" setup 2>> ""${LOG}""
    258     # Install the guest OpenGL drivers.  For now we don't support
 ",DonC
17506,It should be possible to boot a guest with an unconnected hotplug disk,Linux,VirtualBox 5.2.4,2018-01-27T15:18:51Z,2018-01-28T01:57:16Z,2018-01-28T01:57:16Z,"If there is a hotplug virtual disk (a VDI file on an external drive) attached to a SATA controller, the virtual disk is unplugged in the running guest, the external drive is removed and the guest is shutdown, then the guest cannot be booted anymore. I got the following message:
{{{
Could not open the medium 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi'.
VD: error VERR_PATH_NOT_FOUND opening image file 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi' (VERR_PATH_NOT_FOUND).

Fehlercode:
E_FAIL (0x80004005)
Komponente:
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}

Steps to reproduce the problem:

1. Assume you have a Windows 7 host (other host may have the same problem), an USB drive (an USB stick may have the same problem) and a Linux guest (other guests may have the same problem).
2. Shut down the guest.
3. Connect the USB drive to the host.
4. Add a new virtual disk to the guest as a VDI file on the USB drive with a virtual SATA controller. Mark the virtual disk as hotpluggable.
5. Start the guest.
6. Check that the hotplug disk is there: {{{ls /dev/sdb1}}}
7. Unplug the disk: {{{echo 1 > /sys/block/sdb/device/delete}}}
8. Check that the hotplug disk is unplugged (output should be an error message): {{{ls /dev/sdb1}}}
9. Disconnect the USB drive from the host.
10. Shut down the guest.
11. Start the guest.

For a simple test you can omit the steps 5 to 8 and 10.

From my point of view a hotplug disk should be handed like a DVD: It is not necessary that it there (is in the drive) to boot the guest.

Workaround: Disconnect the hotplug disk by hand from the SATA controller before booting, in cold state between step 10 and 11 (in the GUI or by the command {{{VBoxManage storagectl}}}).
 ",dlippold
17495,Échec de l'installation de l'extension,other,VirtualBox 5.2.4,2018-01-22T21:49:35Z,2018-01-23T12:45:31Z,2018-01-23T12:45:31Z,"Échec de l'installation de l'extension C:/Users/moimeme
/.VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-5.2.6.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-32428' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-32428')


rcExit=1.

Code d'erreur : E_FAIL (0x80004005)
Composant : ExtPackManagerWrap
Interface : IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",dedalios
17459,Keyboard/mouse not working after connecting to Dell Docking Station,Linux,VirtualBox 5.2.4,2018-01-16T16:54:46Z,2018-01-17T07:23:43Z,2018-01-17T07:23:43Z,"I have a Dell docking station and the USB keyboard and mouse are plugged into the docking station. If VirtualBox is already running and I connect the laptop to the docking station, the keyboard and mouse do not work. If I first connect the laptop to the docking station and then start VirtualBox, then keyboard and mouse work fine. So I have to close down all VirtualBox windows everytime I disconnect and reconnect back to the dock.",vix
17458,"type/mtype can't be set to ""shareable""",Windows,VirtualBox 5.2.4,2018-01-16T13:19:19Z,2018-01-17T07:13:22Z,2018-01-17T07:13:22Z,"The virtual drive is erroneously recognized as dynamic. See cmd-responses:

C:\Program Files\VirtualBox>VBoxManage storageattach Win10 --storagectl SATA --port 2 --medium E:\DataW10.vdi --mtype shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 708 of file VBoxManageStorageController.cpp
VBoxManage.exe: error: Failed to set the medium type

C:\Program Files\VirtualBox>VBoxManage modifymedium  disk e:\dataw10.vdi --type shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 705 of file VBoxManageDisk.cpp

C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi
UUID:           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Parent UUID:    base
State:          created
Type:           writethrough
Location:       E:\DataW10.vdi
Storage format: VDI
Format variant: fixed default
Capacity:       4096 MBytes
Size on disk:   4098 MBytes
Encryption:     disabled
In use by VMs:  Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)
",Loafer
17462,VM Lockup with evernote screenshot,Windows,VirtualBox 5.2.4,2018-01-16T20:01:22Z,2018-01-16T20:01:22Z,2018-01-16T20:01:22Z,"Version 5.2.4 r119785 (Qt5.6.2)
Windows 7 VM 32 bit. 
Windows 10 Host. 

I have evernote 6.7.5.5825 on my host machine. 

I can use the VM all day long with no issues whatsoever. 
As soon as i use evernote to take a screenshot of either the VM or the host, any pert of either, it locks up the VM to the point that it is nearly un-responsive. Only a left click works, and it only marginally works at that.

Evernote is the only application that i have seen cause this, and it is only when a screenshot is taken. ",link81
17433,VMMR0.r0 Bluescreen on HP Laptop Win10 v1709,other,VirtualBox 5.2.4,2018-01-08T19:22:33Z,2018-01-11T18:49:56Z,2018-01-11T18:49:56Z,"VMMR0.r0 ( VMMR0!VMMR0EntryFast+13de )
Virtual Box 5.2.4 (fresh install)
Windows 10 v1709 10.0.16299.125 (Enterprise) (fresh install)
HP EliteBook 840 G3 W4S08UC#ABL (bios and drivers updated 2018-01-08)

Starting a fresh VM on this configuration triggers a bluescreen.
May also occur on HP Elite X2. Not on HP Z230.
Computer available for remoting

",Patrick_BNC
17436,[FIXED IN SVN] VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation,Linux,VirtualBox 5.2.4,2018-01-08T20:46:23Z,2018-01-10T23:04:19Z,2018-01-10T23:04:19Z,"I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows:

A critical error has occurred while running the virtual machine and the machine execution has been stopped.
For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window.
Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows)

I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out:

00:00:17.401353 !!   VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR)

I am attaching a .ZIP file of the VBox.log.



",GregB3
17440,VBoxHardening- Exit Code 0x1,Windows,VirtualBox 5.2.4,2018-01-09T21:41:58Z,2018-01-09T22:41:16Z,2018-01-09T22:41:16Z,"I have a few different VMs on my current laptop which I am trying to move to my new laptop. However, after importing the machines, I am getting an error message when I try to open the VMs:

[[Image(ticket:1:ErrorMessage.gif)]]

and

[[Image(ticket:1:ErrorMessage2.gif)]]

My previous laptop is running Win7x64 and I am using VirtualBox 5.1.30 r11838. This has been upgraded as releases have come out so I am not sure what version of VirtualBox I was using when I created the VMs. Each machine is running a similar copy of Windows Server 2008 R2.

I have attached the VBoxHardening.log file for one of the VMs- they are all causing the same error.

I was able to open a few of the VMs once, but then after either powering off  (no saved state) or saving, I get the error message again on restart. I  have tried headless, normal, and detached starts. 

I know this issue has been raised on past versions of VirtualBox, but I didn't see a method for fixing the error which worked- I have un-installed and re-installed VirtualBox, I have tried to recreate the VMs using the same hard disk image, I have turned off my virus software, I have confirmed that I do not have the layout registry key (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers), and I have done a software scan (sfc /scannow). I would appreciate any assistance in trying to solve this issue.",mdr
17422,Switching away from guest alters NumLock state of host,Linux,VirtualBox 5.2.4,2018-01-05T09:27:40Z,2018-01-05T18:55:21Z,2018-01-05T18:55:21Z,"Host: Windows 7 Enterprise, initial NumLock state at ""On""
Guest: KDE Neon, initial NumLock state at ""On""

Steps:
Ensure NumLock is on for the host.
Start the guest.
Observe that the host's NumLock remains on.
Enter the guest (e.g. click within the window).
Ensure NumLock remains on.
Return to the host (click the task bar or something that causes VBox to lose focus).

Expected outcome:
Host's NumLock remains on.

Actual outcome:
Host's NumLock turns off.

VBox version first observed: 5.1
Is 5.2.4 affected: Yes

After running a search, I wonder if these bugs are related in some way:
https://www.virtualbox.org/ticket/14614
https://www.virtualbox.org/ticket/14302

I am happy to provide any logs that might be needed.",Twisted Lucidity
17417,VirtualBox crashes,Windows,VirtualBox 5.2.4,2018-01-04T14:32:44Z,2018-01-05T08:37:09Z,2018-01-05T08:37:09Z,"When I craete a new SATA-HD, then the Client crashes if I create with right mouse button on SATA.

There runs a windows 2012 r2 server.

",rhino
17413,simplify the automatically offered extension pack upgrade procedure,other,VirtualBox 5.2.4,2018-01-03T09:28:31Z,2018-01-03T09:28:31Z,2018-01-03T09:28:31Z,"After upgrading an existing VirtualBox installation with extension pack installed and starting VirtualBox, a dialog is presented that an older extension pack was found and if the user wants to upgrade the extension pack. 

This is fine, however the procedure to upgrade the extension pack is rather complicated and goes as follows:

  - Older ExtPack was found, want to download and install new version? Click download
  - This is the file to download, still want to download? Click download
  - File was downloaded, upgrade? Click upgrade
  - Hey, here are the T&C for the ExtPack, agree? Click agree (after reading it carefully obviously  ;)
  - Installation occures
  - Installation successfull, do you want to delete the downloaded file? Click delete

Well, it's not that complicated but just rather annoying because it is every time the same thing and the user already made clear that he wanted to upgrade the ExtPack with the first click.

I would like to propose a simplification for this upgrade procedure:

  - After starting VirtualBox, the initial dialog is presented to give the user the chance to decide if he wants to upgrade or not
  - If the user decided to upgrade, a single dialog is presented.
    - It could contain either the link to the ExtPack that will be installed or a version comparison (current version vX.X.X, new version vX.X.Y)
    - It could contain a checkbox, which is checked by default, to delete the file after the upgrade
    - It could contain a linked message like ""By installing the extension pack, you agree to the T&C"" where the link poins to the said T&C
    - It has two buttons: ""Download & Install"" and ""Cancel""
    - Optionally display an OK dialog that installation was finished

This would drastically increase user friendliness and simplify the ExtPack upgrade procedure. Keeping the initial yes/no dialog choice to upgrade also helps the average joe to panic by being slapped in the face with a full blown dialog",Aoshi
17412,Installing Guest Additions 5.2.4 on CentOS 7 fails,Linux,VirtualBox 5.2.4,2018-01-02T17:12:13Z,2018-01-02T17:12:13Z,2018-01-02T17:12:13Z,"Host: Windows 7, 64-bit, VirtualBox 5.2.4
Guest: CentOS 7 with all upgrades, initially set up for VirtualBox 5.1.22

Bug: 
When I upgraded VirtualBox and ran the Guest Additions installer in my CentOS guest to upgrade Guest Additions, the video driver build failed.  It seems to have failed on an unimportant driver, because it actually works correctly.  Still, it's worth reporting the build failure.  The attached is an excerpt from the log file.

Building the graphics driver module
make V=1 CONFIG_MODULE_SIG= -C /lib/modules/3.10.0-327.18.2.el7.x86_64/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j2 modules
make[1]: warning: -jN forced in submake: disabling jobserver mode.
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (	\
echo >&2;							\
echo >&2 ""  ERROR: Kernel configuration is invalid."";		\
echo >&2 ""         include/generated/autoconf.h or include/config/auto.conf are missing."";\
echo >&2 ""         Run 'make oldconfig && make prepare' on kernel src to fix it."";	\
echo >&2 ;							\
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
  gcc -Wp,-MD,/tmp/vbox.0/.hgsmi_base.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include -Iarch/x86/include/generated  -Iinclude -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/uapi -Iinclude/generated/uapi -include /usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -Wframe-larger-than=2048 -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/3.10.0-327.18.2.el7.x86_64/build/include -I/tmp/vbox.0 -Iinclude/drm -D__KERNEL__ -DMODULE  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(hgsmi_base)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxvideo)"" -c -o /tmp/vbox.0/.tmp_hgsmi_base.o /tmp/vbox.0/hgsmi_base.c
  gcc -Wp,-MD,/tmp/vbox.0/.modesetting.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/4.8.5/include -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include -Iarch/x86/include/generated  -Iinclude -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/arch/x86/include/uapi -Iarch/x86/include/generated/uapi -I/usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/uapi -Iinclude/generated/uapi -include /usr/src/kernels/3.10.0-327.18.2.el7.x86_64/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mno-sse -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -Wframe-larger-than=2048 -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -g -pg -mfentry -DCC_USING_FENTRY -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/3.10.0-327.18.2.el7.x86_64/build/include -I/tmp/vbox.0 -Iinclude/drm -D__KERNEL__ -DMODULE  -DMODULE  -D""KBUILD_STR(s)=#s"" -D""KBUILD_BASENAME=KBUILD_STR(modesetting)""  -D""KBUILD_MODNAME=KBUILD_STR(vboxvideo)"" -c -o /tmp/vbox.0/.tmp_modesetting.o /tmp/vbox.0/modesetting.c
In file included from /tmp/vbox.0/vboxvideo_guest.h:32:0,
                 from /tmp/vbox.0/modesetting.c:27:
/tmp/vbox.0/vbox_drv.h:256:24: error: field ‘gem’ has incomplete type
  struct drm_gem_object gem;
                        ^
In file included from /tmp/vbox.0/hgsmi_base.c:27:0:
/tmp/vbox.0/vbox_drv.h:256:24: error: field ‘gem’ has incomplete type
  struct drm_gem_object gem;
                        ^
make[2]: *** [/tmp/vbox.0/hgsmi_base.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/tmp/vbox.0/modesetting.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxvideo] Error 2
",gbartlett
17403,Touchscreen input is not scaled to VM location on screen,Linux,VirtualBox 5.2.4,2017-12-27T06:40:05Z,2017-12-27T06:40:05Z,2017-12-27T06:40:05Z,"host: Win 10 on HP Envy 14-k111nr with touchscreen (3200x1800), virtualization enabled.
guest: Android 7.1-rc1 64bit, set as Linux (Version 2.6/3.x/4.x 64 bit)


Problem: When I dont disable mouse-integration i can only control the cursor with touch interactions. Also cursor only moveable by mouse when clicked - otherwise it just wouldnt move. 
When I disable it I can ""use"" the touchscreen ""nativly"". But thats the problem because it seems that it just reads out the coordinates of the touch input rather than the position in the VM-machine. It doesnt bother where the VM-""display"" is located on the desktop. If i push at 3000;1000 the VM will detect the click on 3000;1000 even though it only covers the area until 2000;500.

The solution would be to detect the VM window if not 100% fullscreen and translate the touch input postition to the guest screen. ",FUKU
17402,Unexpected input upon minimize/maximize host window,Linux,VirtualBox 5.2.4,2017-12-26T20:13:40Z,2017-12-26T20:13:40Z,2017-12-26T20:13:40Z,"After upgrading VirtualBox to VirtualBox-5.2.4 (VirtualBox-5.2.4-119785-Win.exe) I noticed the Linux guests started receiving weird escape sequences (`~`, `^[^[[29~`) or mouse clicks on the Linux guests.


Going back to the older version is not an option, as after reinstalling the host (Windows 10) the older versions (5.0.20, 5.0.40, and 5.1.30) all fail to start VMs with a `hardening error` (the problem persists even after following the instructions [https://forums.virtualbox.org/viewtopic.php?f=25&t=82106 on the support forum]).

Reproduction steps:

- host: Windows 10 Pro, 64 bits, all updates installed
- Salix guest:
  1. create a VM with [https://www.salixos.org/download.html the latest version (salix64-xfce-14.2.iso)]
     * Type: Linux
     * Version: Other Linux (64-bit)     
     * no swap
     * install from disk
     * auto select
     * Basic installation mode
     * select mirror: mirrors.xmission.com/salix
  2. on the VM, open a terminal and then:
     a. minimize and maximize the VBox window using the keyboard (Win key + D)
     b. alt-tab
     c. or switch Windows 10 workspaces (Win key + Tab)
     --> a right-mouse click is issued on the guest on the last mouse position
  3. installing guest additions does *not* change the problem
     {{{
     (as root)
     slapt-get --update
     slapt-get --install kernel-huge kernel-headers kernel-modules kernel-firmware 
     lilo -v
     slapt-get --install kernel-source
     reboot
     <insert the guest additions media, double click it on desktop to mount>
     sudo /run/media/<user name>/VBox_GAs_5.2.4/VBoxLinuxAdditions.run
     }}}
     
     
- Ubuntu guest:
  1. create a VM with [https://www.ubuntu.com/download/desktop the current LTS (ubuntu-16.04.3-desktop-amd64.iso)] with all the default options      
  2. install urxvt: sudo apt-get install rxvt-unicode-256color
  3. on the VM, open urxvt and then:
     a. minimize and maximize the VBox window using the keyboard (Win key + D)
     b. alt-tab
     c. or switch Windows 10 workspaces (Win key + Tab)
     --> `~` or `[29~` are inserted in urxvt
  4. installing guest additions does *not* change the problem
",mMontu
17399,Video driver fails for Win 10 guest version 1709 Preview build 17063.1000,Windows,VirtualBox 5.2.4,2017-12-24T21:04:36Z,2017-12-26T00:27:40Z,2017-12-26T00:27:40Z,"Video driver fails for Win 10 guest version 1709 Preview build 17063.1000

Fails for VB 5.1.28 , 5.1.30 and 5.2.4 .

Repeat:
1. Turn on Windows insider program from Windows Settings/Windows Insider Program and chose ""What pace do you want to get new builds"" - ""fast""
2. Check for updates via Windows Settings/Windows Update
3. Reboot
4. See the way it fails and Win 10 guest substs VB driver by default Microsoft Basic Display driver

Thank you for development.",MikhailRokhin
17381,virtualbox additional functions are uninstallable,Linux,VirtualBox 5.2.4,2017-12-20T12:19:13Z,2017-12-22T06:20:14Z,2017-12-22T06:20:14Z,"host computer:windows10 64bit
guest: ubuntu 16.04.3
When I click install additional functions, an error raised.

未能加载虚拟光盘 C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso 到虚拟电脑 ubuntu.



Could not mount the media/drive 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (VERR_PDM_MEDIA_LOCKED).

返回 代码:E_FAIL (0x80004005)
组件:ConsoleWrap
界面:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
被召者:IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",f-sky
17384,ElementaryOS Loki not usable with 3D enabled -> unlikely to be fixed in near future,Linux,VirtualBox 5.2.4,2017-12-20T22:37:37Z,2017-12-21T09:05:22Z,2017-12-21T09:05:22Z,"If I activate 3D support, the Desktop turns black or is not usable at all, that is I see the Icons, but nothing happens.

This issue persisted for some time now and I had hoped with the latest release which also fixed a 3D issue for GDM, this would be solved now. Obviously it is not.",jeansen
19790,virtual machine startup error (0x80004005),other,VirtualBox 5.2.40,2020-08-04T18:37:56Z,2020-08-04T18:53:27Z,2020-08-04T18:53:27Z,"Не удалось открыть сессию для виртуальной машины deb1.

The virtual machine 'deb1' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Melchiorre\VirtualBox VMs\deb1\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

",Megasort
19584,Need for Speed Underground 2 causes Virtualbox.exe application error,Windows,VirtualBox 5.2.40,2020-05-14T14:15:34Z,2020-05-14T14:15:34Z,2020-05-14T14:15:34Z,"When I run Need for Speed Underground 2, window VirtualBox.exe application error appears",Nikita Stepanov
19536,"Problems when switching from ""NAT"" to ""Bridge"" and vice versa. VM is not assigned an IP address via DHCP when using ""Bridge"".",Windows,VirtualBox 5.2.40,2020-04-26T14:19:17Z,2020-04-26T14:19:17Z,2020-04-26T14:19:17Z,"Host is a Windows 10 (Build 1909). If you change in Virtualbox 5.2.40 with a VM (Windows 10 (Build 1909) in the network area from ""NAT"" to ""Bridge"" the VM does not get a new IP address via DHCP within the VM. 
With Virtualbox 5.2.38 it works with the same host and with the same VMs without problems online. You can switch between ""NAT"" and ""Bridge"" and the VM gets an IP address internally via its DHCP service. This can also be observed in the DHCP server of the network.  

The error is reproducible and occurs immediately after installing Virtualbox 5.2.40 and disappears as soon as Virtualbox 5.2.38 is installed again.",RonaldMcDonald
19514,Win 10 x64 guest setup hangs on Win 7 x64 host if CPU count > 1,Windows,VirtualBox 5.2.40,2020-04-20T07:08:45Z,2020-04-21T14:19:46Z,2020-04-21T14:19:46Z,"If CPU count is more than one Windows 10 x64 guest hangs during setup on Windows 7 x64 host, while Windows 10 x32 and Windows 7 x64 guests are running fine. If CPU count is one Windows 10 x64 guest is running fine too. Problem exists regardless of chipset is ICH9 or PIIX3, EFI is enabled or disabled. Versions 5.2.38.136252, 6.0.18.136238 and 6.1.4.136177 are also affected.

Related tickets: #19352 (?), #18856, #15529.",Researcher
20025,"DirectSound Device on windows host not found, no sound on host OS, independent of guest OS",all,VirtualBox 5.2.42,2020-11-08T16:31:33Z,2020-11-08T16:31:33Z,2020-11-08T16:31:33Z,"In VBox.log the following occurs during Direct Sound Initialisation on Windows 7 32-bit host, independent of guest OS, the improvement is applicable to all Windows hosts versions:

00:00:02.768338 Audio: Initializing DirectSound audio driver
00:00:02.796743 DSound: DirectSound not available: REGDB_E_CLASSNOTREG
00:00:02.796782 Audio: Initialization of host driver 'DSoundAudio' failed with VERR_NOT_SUPPORTED
00:00:02.797158 Audio: Initializing NULL driver
00:00:02.797183 VM: Raising runtime error 'HostAudioNotResponding' (fFlags=0x0)
00:00:02.797189 Console: VM runtime error: fatal=false, errorID=HostAudioNotResponding message=""Host audio backend initialization has failed. Selecting the NULL audio backend with the consequence that no sound is audible""

In DrvHostDSound.cpp, line 2253 the intialisation happens on a fixed audio device interface ID (of what I can see, I am not 100% sure, just looks like it). Rather build an ""enum"" list of sound devices in the computer. These audio devices can have any IDs. Make that list available in the user interface by audio device name (two lists for Sound In and Sound Out). The user can then select the audio device he/she wants to use, one for sound in, and the other for sound out. So then it does not have to be the default audio device. The user can have several audio devices, e.g. Intel HD Audio, Creative audio, NVidia Sound, etc on the Windows host.

The default audio device fails on my machine, since I have a Creative Audio Product, which has a non-standard GUID.

Attached I have the user interface of the audio tab (there is no device selectable, only a default WindowsDirectSound Device. That's no good. Make a list of direct sound audio devices available in the computer, and expose that list to the user interface. That way, the user can select the audio device to use (does not have to be default, then).

The issue is here, /src/VBox/Devices/Audio/DrvHostDSound.cpp, line 2253:

static DECLCALLBACK(int) drvHostDSoundInit(PPDMIHOSTAUDIO pInterface)
{
    PDRVHOSTDSOUND pThis = PDMIHOSTAUDIO_2_DRVHOSTDSOUND(pInterface);
    LogFlowFuncEnter();

    int rc;

    /* Verify that IDirectSound is available. */
    LPDIRECTSOUND pDirectSound = NULL;
    HRESULT hr = CoCreateInstance(CLSID_DirectSound, NULL, CLSCTX_ALL, IID_IDirectSound, (void **)&pDirectSound);
    if (SUCCEEDED(hr))
    {
        IDirectSound_Release(pDirectSound);

        rc = VINF_SUCCESS;

        dsoundUpdateStatusInternal(pThis);
    }
    else
    {
        DSLOGREL((""DSound: DirectSound not available: %Rhrc\n"", hr));
        rc = VERR_NOT_SUPPORTED;
    }

The IID_IDirectSound should be an enum list with all audio devices attached to the host computer, make that list available in the user interface, so the user can select an audio device of his choice by device name.

It would be nice to also get that feature on the Virtual Box 5.2 for 32-bit Windows hosts, which I am currently using.

",Garfield
17563,Drag and Drop does not work: Host Windows 10 and guest Linux XUbuntu 14.04,Linux,VirtualBox 5.2.6,2018-02-23T14:08:34Z,2022-02-04T10:52:07Z,2022-02-04T10:52:07Z,"
The context: Host: Windows 10 Guest: XUbuntu 14.04 with Kernel(3.13.0-139-generic and 4.12-generic and ... does not work) linux Guest Additions 5.2.6 installed and update new Linux Kernel bidirectional clipboard  does not work

The problem: Drag and Drop between guest and host does not work in either direction after update of virtual box and linux update from 22.2.17. 

Error message: vboxvideo, vboxguest: version magic should be ""4.4.0-116-generic SMP mod_unload modversions retpolin"" ?

",m.k.IOSB
20677,kernel module isn't loaded because the VBox drive is not installed,Windows,VirtualBox 5.2.6,2021-11-19T09:34:28Z,2021-11-22T20:15:36Z,2021-11-22T20:15:36Z,"After several months that I used the version 5.2.6 (with Win 7 - 64), one month ago, I had some Windows problems due pc overheating and to the power source. Despite I solved any Windows failure (in particular those related to the desktop windows managing and to explorer block) Since that moment VM has stopped to run and every time I try tro run my virtual machine (Windows XP 32) it show the attached error, as in summary. 
I'm not expert and my attemp to unblock the situation, even by uninstalling and reinstalling VB, have not been successful.
Thanks for all.",marcopro
17485,"Crash 0xc0000005 after host suspend (Linux guest, Windows 7 host)",Linux,VirtualBox 5.2.6,2018-01-19T15:58:16Z,2019-09-12T12:38:50Z,2019-09-12T12:38:50Z,"Crash occurred twice for me.
{{{
03:20:07.990450 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000001140!!!
03:20:07.990470 
03:20:07.990471 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007fefb15be75
03:20:07.990477 ExceptionInformation[0]=0000000000000000
03:20:07.990482 ExceptionInformation[1]=0000000000000070
}}}
!VirtualBox show error message, then virtual machine become turned off.",ukolovda
17533,USB3.1 USB stick fails to enumerate,Linux,VirtualBox 5.2.6,2018-02-08T12:37:24Z,2019-01-29T15:19:48Z,2019-01-29T15:19:48Z,"Host: W10 LTSB (64bit)
Guest: Linux (64bit)
VB Version: 5.2.6 r120293 (Qt5.6.2)

I've recently purchased another one of these sticks (Verbatim Go V3 MAX). The old ones (read out as USB3.0) work just fine.

This one however shows up as USB3.1 (booting linux on physical machine). The stick works just fine on W10 / linux, as long as I don't use a VM.

Disabling USB3 in the VM ""helps"", but USB2 speeds are just 5MB/s.",robert spitzenpfeil
17856,Error -5640 in supR3HardenedWinReSpawn! (enmWhat=1) (Hardening Issue while starting an image),Linux,VirtualBox 5.2.6,2018-07-04T12:43:41Z,2018-07-04T18:34:01Z,2018-07-04T18:34:01Z,"I am running Oracle Virtual Box 5.2.6 r120293 (Qt5.6.2) and I am trying to launch CentOS 7 gust image and see the error ""Error (rc=-5640)""

I am on Windows 10 [1709] 64-bit OS and x64-bit Processor.

I have tried most of the options that are mentioned in the link:

https://forums.virtualbox.org/viewtopic.php?f=25&t=82106

Can anyone help us if this is a bug or something that is coming from my environment.

I have attached the VBoXHardening.log",SarmaK
17617,guru meditation,Linux,VirtualBox 5.2.6,2018-03-12T16:01:22Z,2018-04-24T20:03:27Z,2018-04-24T20:03:27Z,"Hi,

Please am unable to install my new kali-linux-light-2018.1-i386 on windows 7 host which is giving me a guru meditation error.

Attached are details of error report.
Thank you.",swagalimo
17601,Error when loading VM,Windows,VirtualBox 5.2.6,2018-03-07T09:08:09Z,2018-04-17T13:42:01Z,2018-04-17T13:42:01Z,"Hi
i have error on VBOX when i try to run VM 
The error is 
(rc=-5640)
Where supR3HardenedWinReSpawn What :1 VERR_SUP_VP_THREAD_NOT_ALONE(-5640) - Process Verification Failure The Process have more than one thread.

how can i fix this issue it happen to Laptop and Desktop IBM hardware VT enabled 
we try to install the new Ver and try to install old ver 
we try to go back to Windows 10 1607 
Please help 

Thank you for the help",yotama
17672,VM crash after winXP resumes from hibernation,Windows,VirtualBox 5.2.6,2018-04-09T11:30:26Z,2018-04-09T11:30:26Z,2018-04-09T11:30:26Z,WinXP install > hibernate it via windows's own hibernation > start VM back up > VM crashes with the 'critical error' dialogue.,Paul17041993
17522,After updating software and kernel of Xubuntu 17.10.1 - critical error on restart,Linux,VirtualBox 5.2.6,2018-02-02T20:44:39Z,2018-04-09T05:43:59Z,2018-04-09T05:43:59Z,"After a good install of Xubuntu, ran software updates, during restart got a critical error:

Installed latest 5.2.7 test build and got same error:

""A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on  https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /Users/dwhea/VirtualBox VMs/Ubuntu/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now.""",wadesnj
17648,Host-Only adapter failed to install on Windows 10 OS,other,VirtualBox 5.2.6,2018-03-29T07:20:36Z,2018-03-29T07:20:36Z,2018-03-29T07:20:36Z,"'''[How to reproduce]''' [[BR]][[BR]]
From fresh installation, I had no problem to use host-only network and the host-only adapter was present.[[BR]]
The problem began when I removed my host-only adapters using VirtualBox GUI. I was then not able to re-create it using either the GUI and the command line.

'''[Research]''' [[BR]][[BR]]
I've walk through the VirtualBox forum and Bug tracker before posting and I found a similar issue : [[BR]]
+ https://www.virtualbox.org/ticket/17354 [[BR]]
+ https://forums.virtualbox.org/viewtopic.php?f=6&t=86179 [[BR]]
Here the antivirus was involded and disable it resolved the issue. [[BR]]In my case I've completely uninstall my corporate antivirus + deactivate Windows Defender without success. [[BR]]

'''[Troubleshooting]''' [[BR]][[BR]]
+ Repair VirtualBox [[BR]]
+ Uninstall VirtualBox [[BR]]
+ Remove %userprofile%\.virtualbox [[BR]]
+ Remove drivers in %windir%\System32\drivers [[BR]]
+ Remove registry keys about VirtualBox [[BR]]
+ Install 5.2 VirtualBox [[BR]]
+ Run Installer as Admin right [[BR]]
+ Run a Ccleaner registry cleaning [[BR]]
[[BR]]
With a result always the same, failed to create host-only adapter. [[BR]]

'''[logs]''' [[BR]][[BR]]

VirtualBox Gui logs are showing : [[BR]]
{{{
Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Code d'erreur : E_FAIL (0x80004005)
Composant : HostNetworkInterfaceWrap
Interface : IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
}}}

C:\Windows\INF\setupapi.dev.log
{{{
>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\vboxnetadp6.inf_amd64_37fe176ed22ac0b0\vboxnetadp6.inf]
>>>  Section start 2018/03/27 18:20:45.493
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{a2f92065-56fc-42e5-ada7-359a3774292e}
     sto: Source Filter  = VBoxNetAdp6.ndi
     sto: Target Filter  = ROOT\NET\0002
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37fe176ed22ac0b0'. Error = 0x00000005
<<<  Section end 2018/03/27 18:20:45.540
<<<  [Exit status: FAILURE(0x00000005)]
}}}

'''[other]'''[[BR]][[BR]]
I remember once clicking [NO] on the UAC pop-up message asking to install host-only driver. Could the issue be trigered by this action?
[[BR]][[BR]]

Thanks for your help.",AlexRoux42
17620,VERR_VMX_NO_VMX,Linux,VirtualBox 5.2.6,2018-03-13T11:01:44Z,2018-03-14T01:03:52Z,2018-03-14T01:03:52Z,"Hello 
I imported a virtual disk from W7 to W10.
When I run it I got the error message :
VT-x is not available (VERR_VMX_NO_VMX).
E_FAIL (0x80004005)
ConsoleWrap
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

VirtualBox is version 5.2",Harvey13
17469,VB 5.2.6 Audio issues,Windows,VirtualBox 5.2.6,2018-01-17T16:49:40Z,2018-03-11T20:16:47Z,2018-03-11T20:16:47Z,"I think v5.2.6 messed up the audio somehow - after a while, it goes distorted & echo-y - I only use audio in the browser, not sure via WMP/etc.

Tried un-ticking ""Audio Input"" (new on Status Bar), no dice.

Even tried reverting to 5.2.2, but the GUI still looks like 5.2.6. 

I made a capture of what this audio on VB does now... http://www.screencast.com/t/98kW3skJVejU  you can hear it after 23 secs

Is this just me?",PalsyP
17613,Installing Guest Additions fails on Windows Vista Guest.,Windows,VirtualBox 5.2.6,2018-03-10T16:51:46Z,2018-03-10T16:51:46Z,2018-03-10T16:51:46Z,"I am trying to install Guest Additions onto a Windows Vista Sp1 VM, but it keeps stopping. All I try to do is install it, but it fails. My Host System is Windows 10 Fall Creators Update.",RealTTNetwork
17585,Audio Output and Input issues on Ubuntu 17.04 with Windows 10 Host,Linux,VirtualBox 5.2.6,2018-03-04T01:01:21Z,2018-03-04T01:01:21Z,2018-03-04T01:01:21Z,"There are two Audio issues that I've found, one is already documented and the other is not.

Firstly, audio output periodically becomes filled with static in the most recent releases (I believe 5.2.6 was the start of it).  The static is not constant, but rather it comes and it goes.  This has persisted for the past two versions I've used, but as I've stated previously it's already known.

Secondly, with the most recent release of Virtualbox (5.2.8) my guest does not detect any input Audio.  I have tried all of the various available audio drivers, and none of them detect any form of audio input.  Reverting back to 5.2.6 has rectified the issue.",Aaro
17581,Vbox Guest Additions support for kernel-4.16.0-rc2,Linux,VirtualBox 5.2.6,2018-03-02T08:24:33Z,2018-03-02T08:24:33Z,2018-03-02T08:24:33Z,"1> Virtual Box version - 5.2.6 r120293

2> Created Virtual Machine  ( CentOS Linux (3.10.0-693.el7.x86_64) 7 ).

3> Default Guest additions image ( which comes when we mount it from devices options ) is working fine.  

4> Downloaded Linux Kernel  ( version - 4.16.0-rc2 )

5> Compiled Linux Kernel ( version - 4.16.0-rc2 ) and booted with it.

6> Guest Additions stopped working, so I debugged around it.

7> And re-installed default guest addition, but its not working ( auto-size guest display is not working  )

8> Downloaded Guest Addition iso image ( VBoxGuestAdditions_5.2.8.iso ) from ""http://download.virtualbox.org/virtualbox/5.2.8/"".

9> Run the Vbox Guest additions agains. I see some compilation errors. Attaching logs.

So I just want to understand if I did something wrong here or is the kernel with which I have booted is still not supported in Virtual Box guest additions 5.2.8.
  

",Zubraj
17578,Blue screen after upgrading to 5.2.6 version,Windows,VirtualBox 5.2.6,2018-03-01T01:54:57Z,2018-03-01T01:54:57Z,2018-03-01T01:54:57Z,"5.1.30 version of the work is normal, upgrade to 5.2.6 version of the virtual machine and the host has a blue screen phenomenon.
The following is the host debugging information.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {61948, 2332810, 1, 2332810}

Probably caused by : memory_corruption ( nt!MiDereferenceIoPages+ccea8 )

Followup:     MachineOwner
---------

nt!KeBugCheckEx:
fffff802`1ad85430 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe68b`5f1bf1b0=000000000000001a",Minghao
17569,QtCreator does not work on Linux Ubuntu after new Update,Linux,VirtualBox 5.2.6,2018-02-27T11:42:20Z,2018-02-28T23:13:10Z,2018-02-28T23:13:10Z,"Host: Windows 10 Guest: XUbuntu 14.04 linux (64 bit sytem)Guest Additions 5.2.6 installed.

QtCreator does not work on Linux Ubuntu after new Update.
QtCreator does not start after an update. 
VirtualBox graphics adapter: This device is not working.

Error message: OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.

 Can somebody help?",m.k.IOSB
17527,appcrash virtualbox 5.2.6 on win7 32 bit,Linux,VirtualBox 5.2.6,2018-02-05T14:02:00Z,2018-02-28T16:20:38Z,2018-02-28T16:20:38Z,"Hello kindly help us solve the application crash every time we press on ""New"" to create a new Machine. We are using win 7 32bit..

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	5.2.6.20293
  Application Timestamp:	5a5cc3df
  Fault Module Name:	VirtualBox.dll
  Fault Module Version:	5.2.6.20293
  Fault Module Timestamp:	5a5cc3f2
  Exception Code:	c0000005
  Exception Offset:	001edcd7
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

",reviewsarl
17571,Guest additions will not build using gcc 6,Linux,VirtualBox 5.2.6,2018-02-27T15:36:43Z,2018-02-28T14:51:56Z,2018-02-28T14:51:56Z,"See attached log.
This is on a Ubuntu 1204 guest using gcc6 from 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test 

Builds are OK using gcc5 from same source",tomasth
17474,Black Screen of Death after update to 5.2.6 from 5.2.4,Linux,VirtualBox 5.2.6,2018-01-18T03:00:26Z,2018-02-28T09:59:38Z,2018-02-28T09:59:38Z,I am using Windows 10 to run Oracle Virtual Box 5.2.4. The notification of an update came and I updated it to the latest (5.2.6) and that was fine. I have a virtual machine running Ubuntu 16.04 and while running the old vm tools I updated the vm tools and it crashed. The virtual machine will not boot past the Oracle boot screen,Dominic M
17560,System Unstable,other,VirtualBox 5.2.6,2018-02-22T18:08:14Z,2018-02-28T06:44:13Z,2018-02-28T06:44:13Z,"I am running a Windows 10 Pro system with AMD 1700x processor, 64 Gig memory, 512SSD (OS drive), 4tb 7200 RPM drive, and just added 120SSD to see if another drive would help.  

At first I thought I might have a bad hard drive, replaced it and I continue to have issues which tells me it is software. 

I am unable to import any machines and when I export and test it on another machine it tells me the file is corrupt. When I build a machine from scratch it runs for a few hours then crashed to the point it won't boot. 

I have tried to uninstall and reinstall, along with reinstalling an older version with no success. 




",SilentWraith
17559,Error al mostrar informacion,all,VirtualBox 5.2.6,2018-02-22T17:23:40Z,2018-02-28T06:42:10Z,2018-02-28T06:42:10Z,al mostrar la informacion si el puntero esta en el anfitrion o en la MV sale codigo html,FalconXCI
17476,Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10,other,VirtualBox 5.2.6,2018-01-18T08:41:55Z,2018-02-23T21:22:58Z,2018-02-23T21:22:58Z,"When starting an imported OVA on a fresh install of WinBox my Win10 machine ends up in a BSOD.

Winbox 5.2.6r120293
Windows 10 Enterprise 64bit

",woli
17551,Error relaunching VirtualBox process : 5,Windows,VirtualBox 5.2.6,2018-02-19T13:58:42Z,2018-02-19T15:36:29Z,2018-02-19T15:36:29Z,"VirtualBox crash during Windows 2012 server installation on new VM. Then get an error message when i was trying to restart VM.
",cbr45
17548,[5.2.6 r120293] Guest linux hangs on boot-up if audio is enabled,Linux,VirtualBox 5.2.6,2018-02-18T08:18:26Z,2018-02-18T10:16:00Z,2018-02-18T10:16:00Z,"Host :- Windows 7 Enterprise 64 Bit
Guest:- Linux unix 4.13.0-32-generic lubuntu 17.10 64 bit
Audio :- ICH AC97

When i unable audio support linux failed to boot-up and if i disable everything works correctly.
",manoj_red_hat
17546,Windows 10 guest keeps hanging,Windows,VirtualBox 5.2.6,2018-02-16T19:53:37Z,2018-02-16T19:53:37Z,2018-02-16T19:53:37Z,"I'm using VirtualBox v5.2.6r120293. My host and guest are Windows 10. The guest is frequently hanging, becoming completely unresponsive; when it does, VirtualBox Manager will oftentimes be unresponsive, too. My only recourse is to close either the guest or the VirtualBox Manager, sometimes having to resort to doing so via Task Manager. After such an event, the guest has a status of ""Aborted"" but I can re-start it without apparent issue.

The guest just froze again; VirtualBox Manager didn't freeze this time. The VirtualBox Log Viewer lists five log files; however, I don't see much of interest therein except the last line which reads (in VBox.log and VBox.log.2) ""GUI: Request to close machine-window."", (in VBoxHardening.log) ""4a88.4ccc: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xcfffffff (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1429056 ms, the end);"", and (in VBox.log.3) ""GUI: Passing request to close Runtime UI from machine-logic to UI session."" I've attached the log from Machine > Show Log > Save.

Any suggestions on how to resolve this issue?",CGW
17545,"Drag and Drop does not work: Windows 7 host, Fedora linux guest",Linux,VirtualBox 5.2.6,2018-02-14T16:41:17Z,2018-02-14T16:41:17Z,2018-02-14T16:41:17Z,"The context:
Host: Windows 7 Pro SP 1
Guest: Fedora 23 linux
Guest Additions 5.2.6 installed and confirmed to work (for example, dynamic screen resizing works, and bidirectional clipboard works).

The problem:
Drag and Drop between guest and host does not work in either direction. When dragging from Windows 7 host to Fedora 23 linux guest the file icon under the mouse pointer in the guest windows has a red, ""not allowed"" sub-icon once the guest window boundary is crossed. When released inside a file manager window, the icon disappears, and the files are not copied. This happens both with directories and simple text files.

When dragging from guest to host the file icon under the mouse pointer disappears at the guest window border and no files are copied.",ryac
17542,VirtualBox 5.2.6 Guru Meditation Error,Linux,VirtualBox 5.2.6,2018-02-13T17:37:21Z,2018-02-13T17:37:21Z,2018-02-13T17:37:21Z,"Since VirtualBox 5.2.6 my VirtualBox keeps crashing with a Guru Meditation Error on Windows 10 Host with Debian guest.
My Log.txt is attached.",Frank Breitling
17541,Input/output error when running ./VBoxLinuxAdditions.run on headless guest,Linux,VirtualBox 5.2.6,2018-02-13T15:32:29Z,2018-02-13T15:47:00Z,2018-02-13T15:47:00Z,"After having installed build-essential on a fresh installed Guest running Ubuntu 17.10 Server (installed from ubuntu-17.10.1-server-amd64.iso) I tried to install the Guest Additions but failed with an Input/output error.

{{{
peter@ubuntu-s:~$ sudo /mnt/VBoxLinuxAdditions.run
sudo: unable to execute /mnt/VBoxLinuxAdditions.run: Input/output error
}}}

Next I tried to install the guest additions for 5.2.7. While this worked so far it produced a ""modprobe vboxsf failed"" message.

After a reboot and a second try to install VirtualBox 5.2.7 Guest Additions for Linux the installation finished without an error.

For further details see attached console-log-1.txt.",PeterG
17539,VirtualBox driver crashes when rebooting with kexec on Ubuntu 16.04,Linux,VirtualBox 5.2.6,2018-02-12T02:54:03Z,2018-02-12T11:33:03Z,2018-02-12T11:33:03Z,"Restarting into another kernel is faster with kexec. There's a crash when I try to reboot into another kernel with kexec. The problem (says the screenshot) is because VirtualBox.

The commands I issued were:

diwou@diwou-VirtualBox:~$ sudo kexec -l /boot/vmlinuz-`uname -r` --reuse-cmdline
[sudo] password for diwou:
diwou@diwou-VirtualBox:~$ sudo systemctl kexec

Then I can see a crash on the GUI screen...

This bug was reported 5 years ago, I read it was marked as obsolete, but I think it's not fixed.",D1W0U
17538,Virtual Box displays black screen,Windows,VirtualBox 5.2.6,2018-02-11T22:31:28Z,2018-02-12T11:31:18Z,2018-02-12T11:31:18Z,I have been using Virtual Box for a class I am in for college. The other day I tried to bring up my Virtual Box VM program and only had a black screen. I have attached a picture showing what my screen has. It just sits there and not doing anything. I have loaded up a new OVA file for my VM program and still get same thing. What can I do to fix this or what is causing this. I have been using Virtual Box and this program for about 4 weeks now.,fuzzwuzzy13
17535,Guest Additions contain old DirectX9 DLLs,Windows,VirtualBox 5.2.6,2018-02-09T17:29:02Z,2018-02-12T11:09:20Z,2018-02-12T11:09:20Z,"Hello,

when installing the Guest Additions, the following files are replaced d3d8.dll and d3d9.dll. Unfortunately this are old DLL versions (it should be at least 5.03.2600.5512), the Oracle Version is 5.02.0006.20293. So DxDiag shows an error with those two files. Furthermore, it seems that this error is also causing sound issues with iTunes and VirtualDj 8, as there is a crackling in the sound. Both are using DirectX.

Can you please fix this in the next version of the GuestAdditions?

Kindest regards,
Heiko",Boettgerie
17526,Memory exception,Linux,VirtualBox 5.2.6,2018-02-05T14:01:03Z,2018-02-05T16:35:56Z,2018-02-05T16:35:56Z,Get an error message that program is trying to access protected memory location 0x0000000000000040 and on click of OK button guest session ends.,kpenrose
17504,VCPU1: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Linux,VirtualBox 5.2.6,2018-01-27T10:53:10Z,2018-02-05T11:35:34Z,2018-02-05T11:35:34Z,"Upgraded VB on VirtualBox 5.2.6 version.
Run Guest Ubuntu 16.04 host (has not been running/updated for about a month)
Executed ubuntu updates with:

{{{
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
}}}

Was unable to create a symlinks in my shared directory.
Executed the following command which was supposed to help:


{{{
VBoxManage.exe setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate/SHARE_NAME 1
}}}

Then unable to start the Guest machine because of GURU error from the subject.",Faly
17525,Conflict between VESA VBE 2.0 graphic adapter and NAT network on WINDOWS ME,Windows,VirtualBox 5.2.6,2018-02-05T03:55:19Z,2018-02-05T03:55:19Z,2018-02-05T03:55:19Z,"When you install VESA VBE 2.0 Oracle VM VirtualBox VBE Adapter to have 32 bits true color on WINDOWS ME MILLENIUM EDITION with a program called SciTech Display Doctor (this also works with win 98) you can't connect with the internet cause it seems that there's a conflict between the NAT network adapter and VESA VBE 2.0 cause I uninstalled SciTech Display Doctor and went back to standard 16 colors graphic adapter and I could access internet again. This doesnt happen with Win 98 I can install it and internet works, it's just with Millenium edition",tonypark77
17523,CentOS7 hangs after installing guest additions,Linux,VirtualBox 5.2.6,2018-02-03T12:59:50Z,2018-02-03T13:08:36Z,2018-02-03T13:08:36Z,"This Virtual machine was working just fine in previous version of Virtual Box. After installing version 5.2.6 of Virtual Box the os was still booting fine. Then I installed Guest Additions and restarted os. Now, the os hangs (see picture attached).",noone
17518,Scratchy/cracklinkg sound on all VM with Windows host,all,VirtualBox 5.2.6,2018-02-01T19:37:48Z,2018-02-02T18:52:43Z,2018-02-02T18:52:43Z,"For quite a long time (at least 5.1.26, but probably earlier, i think i got this problem back in 5.0.6 on winxp, but I'm not sure) there's a problem with scratchy sound on all my VM. It doesn't matter it's windows xp, 8.1, 10 or various linuxes (ubuntu 14.04, 16.04, 17.10, manjaro) sound is scratchy, but new windows (8.1, 10) are worse. I tested it on 3 machines, one with win7 and two with win8.1. It doesn't matter it's new vm, old one, with or without addons.
The best part is, everything is ok on linux hosts (same vm, same pc).

How is sound scratchy? When playing any sound (win8.1 test sounds in device settings are best example) are similar to electronic crackling 50% of time. When playing music it gets a little better, but still ~10% of time it's crackling.
",Akkak
17508,USB Passthrough Keyboard sometimes does not detect keystrokes,other,VirtualBox 5.2.6,2018-01-29T09:14:54Z,2018-01-29T14:07:24Z,2018-01-29T14:07:24Z,"Hi there!

I use Virtualbox on Windows 10 and have a Ubuntu 16 VM. I attach a seperate USB keyboard and mouse to the host and pass them through to the VM. This is pretty nice because with additional screen where the VM is in fullscreen mode, its almost like having two fully operational computers.

Everything works fine with the rather old version 5.0.8 r103449 of VB. I noticed that with later versions it happens that sometimes keystrokes get lost / do not get detected in the VM, especially when typing fast. The latest version I tried and I can still reproduce that behavior is 5.2.6 r120293 (Qt5.6.2). I always have the guest utilities updated and installed but they seem to have no effect here.

I really would appreciate you guys looking into that issue and fixing it, it worked in the past so maybe it's an small and easy fix. Unfortunately it's what keeps me from updating to later VB version.

Thank you and best regards,
Nils",Nils Koenig
17503,VBoxExtPackRegister returned VERR_VERSION_MISMATCH,Windows,VirtualBox 5.2.6,2018-01-27T05:29:19Z,2018-01-27T09:44:05Z,2018-01-27T09:44:05Z,"VBoxExtPackRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='VirtualBox version mismatch - expected 5.2 got 5.0'.


Result Code: 
E_FAIL (0x80004005)
Component: 
ExtPackManagerWrap
Interface: 
IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}
",DSquad
17501,Ubuntu guest fails after waking from windows 10 host sleep,Linux,VirtualBox 5.2.6,2018-01-26T17:46:47Z,2018-01-26T17:46:47Z,2018-01-26T17:46:47Z,"Hi, 
I have the latest version of VirtualBox -- 5.2.6 running on a windows 10 host.   I've tried a couple of different guest OSes, Fedora Core 27 and Ubuntu 16.04.   Both fail to survive a sleep-wake-cycle on the Windows 10 guest.    

I've tried many things from previous bug reports, more memory, more video memory.   Also with and without 3D acceleration and with and without hardware virtuatization, etc.  

Occasionally, the guest will survive one sleep-wake cycle but will slip into  'Guru Mediation' after the second cycle.  

I have also installed the latest guest additions on the host as well. 

I'll attach the virtualbox log file and the virtualbox hardening log file.  


Please advise. 
Thanks,
Jeff
",jmcdonal
17496,critical error guru meditation,Windows,VirtualBox 5.2.6,2018-01-23T06:52:37Z,2018-01-23T09:35:36Z,2018-01-23T09:35:36Z,"sir,
   there is an issue in my virtual box in which my xp virtual window going to
 guru meditation & not work my virtual box window.
",lalla
17481,VM crashes when allocating memory at MSR_LSTAR address range,Linux,VirtualBox 5.2.6,2018-01-19T10:45:07Z,2018-01-19T22:32:20Z,2018-01-19T22:32:20Z,"Hi,

I'm developing a Linux LKM, and I tried to reserve memory in the same range of MSR_LSTAR (SYSCALL handler), with __vmalloc_node_range().

On the 3rd execution of that function, returning first NULL, second an address and third time NULL, the Guru Mediation spawns.

I'm attaching the source code to reproduce the bug, the log and the screenshot.

Thanks for help.",D1W0U
17478,ExtensionPack Installation Error,all,VirtualBox 5.2.6,2018-01-18T15:00:51Z,2018-01-18T18:06:15Z,2018-01-18T18:06:15Z,"Не удалось установить плагин C:/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.2.6-120293.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1048' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')

rcExit=1.

Код ошибки: E_FAIL (0x80004005)
Компонент: ExtPackManagerWrap
Интерфейс: IExtPackManager {edba9d10-45d8-b440-1712-46ac0c9bc4c5}

",zats
17679,Error on trying to run VM in headless mode.,Windows,VirtualBox 5.2.8,2018-04-12T13:02:55Z,2022-09-29T17:32:06Z,2022-09-29T17:32:06Z,"Host: Windows 10 Pro x64
Quest: Windows XP x32

All going norm. VM works and launches.
Problem is error when attempt to launch VM in headless mode.

Error:
Не удалось открыть сессию для виртуальной машины VWXP.
The virtual machine 'VWXP' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\User\VirtualBox VMs\VWXP\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {fecae8e8-46da-44cf-8fc0-2ba9aeb796a7}",UnclWish
17696,Processor ID and MotherBord ID Missing,other,VirtualBox 5.2.8,2018-04-19T09:18:06Z,2021-07-26T05:31:58Z,2021-07-26T05:31:58Z,"Hello,

We need some hardware information to do software licensing.
In a Windows 10 VM, Processor ID and MotherBord ID cannot be requested.

These commands return default or empty values. 
wmic PATH Win32_Processor GET ProcessorId /VALUE
wmic PATH Win32_BaseBoard GET SerialNumber /VALUE

My expectation :
- When the VM is creator, random ProcessorId and MotherBordId are attributed.
- When the VM is moves/dupplicated, ProcessorId and MotherBordId are randomly updated

Please tell me if you plan to resolve this ticket because similar tickets are quite old and were never treated.",Nicolas M
17604,"VM becomes ""inaccessible"" on re-launching GUI, Sharable VDI removed from media registry",Windows,VirtualBox 5.2.8,2018-03-07T16:51:29Z,2021-02-03T13:47:07Z,2021-02-03T13:47:07Z,"Hello all,

Running into a ''very'' annoying problem, where my shareable vdi disk gets removed from the the VM (.vbox) xml on shutting down the VirtualBox Manager GUI -- resulting in my guest becoming ""inaccessible"" -- this has been happening for the past few versions (at least as far back as 5.2.6).
I can make the VM ""accessible"" again by manually specifying the shared disk in the .vbox file (or temporarily attaching the shared disk to another guest, to have it show up in the media registry).
As soon as I close/re-open the VirtualBox Manager GUI, my VM becomes ""inaccessible"" again.

Anyhow, here is the message I get:

{{{
A differencing image of snapshot {5912e4a6-b6c8-4ba7-ae4c-51b15512b9f5} could not be found. Could not find an open hard disk with UUID {662e4d2d-9085-4ecb-819e-f1f9875367e2}.
Result Code: 
E_FAIL (0x80004005)
Component: 
SnapshotMachine
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
}}}

When manually editing the .vbox file, this is what I have been adding... but it get's overwritten when cycling the VirtualBox Manager GUI:

{{{
<VirtualBox ...>
  <Machine ...>
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{662e4d2d-9085-4ecb-819e-f1f9875367e2}"" location=""C:\Users\{me}\VirtualBox VMs\Shared\ActivationsDisk.vdi"" format=""VDI"" type=""Shareable""/>
      </HardDisks>
      <.../>
    </MediaRegistry>
    <.../>
  </Machine>
</VirtualBox>
}}}

Any help/fixes would be greatly appreciated.

Thanks!
",pbouill
17597,Audio input broken on Windows 10 v1709 hosts,Windows,VirtualBox 5.2.8,2018-03-06T22:28:45Z,2019-05-12T16:57:43Z,2019-05-12T16:57:43Z,"Audio input seems to be broken on Windows 10 v1709 hosts for any guest OS with the latest (didn't test for regressions) version of VirtualBox (5.2.8). I tested Win10 v1709 guests and modern Linux guests (Arch Linux). On an Arch Linux host with the latest VirtualBox a Win10 v1709 guest works fine. So this seems to only impact Windows hosts.

I've tried it on 3 completely different machines, an older Sandy Bridge era desktop, a modern desktop and a current laptop.

I've tried it on Realtek audio hardware with a 3.5mm microphone plug and a Logitech G533 wireless headset with a USB dongle. I tried disabling (from Device Manager) all other hardware devices except the Logitech device when testing this. I tried uninstalling the Realtek drivers as well.

I tried a clean install of the latest VirtualBox with a clean Win10 v1709 guest install with audio input/output enabled from the start.

Everything appears fine on the surface, audio input/output are enabled in VirtualBox settings, the devices appear in the guest, audio output works fine but audio input does not - there's only silence. The Windows Sound -> Recording dialog in the guest does not show any activity and ""Listen to this device"" does not result in any output. On the host itself it does work.

I didn't see a relevant looking ticket for this so I'm submitting a new one.",vbutilizer
17583,VBoxControl guestproperty set fails with error VERR_PERMISSION_DENIED,Linux,VirtualBox 5.2.8,2018-03-02T22:57:29Z,2019-02-16T22:39:27Z,2019-02-16T22:39:27Z,"The VBoxControl commands below have run fine on numerous previous versions of VirtualBox no longer work on VirtualBox 5.2.8 in the specified guest/host

These commands are being run as root in the guest and fail as shown below:

[root@localhost sva.ledgerU]# VBoxControl --nologo guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountPrefix ''

VBoxControl: error: Failed to store the property value, error VERR_PERMISSION_DENIED

[root@localhost sva.ledgerU]# VBoxControl --nologo guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir ""/mnt/hgfs""

VBoxControl: error: Failed to store the property value, error VERR_PERMISSION_DENIED

",jimf
17799,USB Webcams are Not Working in Windows Guest (w. Extension Pack & Guest Additions),Windows,VirtualBox 5.2.8,2018-06-03T22:13:44Z,2018-06-21T05:24:35Z,2018-06-21T05:24:35Z,"I am trying to get my webcam, Microsoft LifeCam (USB), to work in a Windows 7 (64 bit) Guest on Windows 7 (64 bit) Host.


The camera works fine in the Host using two different applications:
1. Microsoft LifeCam software
2. Portable Webcam (http://sourceforge.net/p/portablewebcam)

I am currently using VirtualBox 5.2.8 w. Guest Edition and Extension Pack. I select the WebCam under devices (and not in USB devices). The camera is recognized in Device manager. However, the Camera is not working;
1. Microsoft LifeCam software: ""No Camera found""
2. Portable Webcam: Camera light turns on then off. I just get a white screen

I can use the camera in the Host, using either application, even when virtual box is running with the camera attached to the Guest (Should that work? I had expected the Guest to take ownership of the camera).

I also tried Logitech C270 Webcam and I have the same problem. 

Please help, I have spent several months on this using different guests and versions of VirtualBox.
Thank you in advance!

p.s. 
1. The cameras works fine in VMware virtual machines and Windows 7 Host/Guests.
2. I posted this previously in the forum but got no response (https://forums.virtualbox.org/viewtopic.php?f=6&t=87569)",ppan
17621,USB and LAN error when re-connecting notebook to dock,other,VirtualBox 5.2.8,2018-03-14T14:54:10Z,2018-06-12T06:55:04Z,2018-06-12T06:55:04Z,"Environment 1:
Hardware: Dell XPS 15 with Dell Dock TB16
Software: Oracle VirtualBox 5.2.6, then updated to 5.2.8 r121009 

Environment 2:
Hardware: Dell Precision 5520 with Dell Dock TB16
Software: Citrix Desktop Player 2.5.0.10 with integrated Oracle VirtualBox 5.1.25 r117057(Qt5.6.2)


Reproducible error:

After disconnecting and reconnecting the notebook to dock:
- LAN and USB devices connected to the dock do not work
- In device manager the device ""ASMedia USB Root Hub"" shows an error:
""Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)""


Workarounds to temporarily fix the issue:

Environment 1:
Close all open VirtualBox windows

Environment 2:
Disable:
- DesktopPlayer Service 
- Citrix DesktopPlayer Mped Service
- VirtualBox Host-Only Network (in network connections)
",ChrisSt
17789,Virtual computer failed to start,Linux,VirtualBox 5.2.8,2018-05-30T13:36:22Z,2018-05-30T14:21:39Z,2018-05-30T14:21:39Z,,zhangwei01
17577,Unusable window system on Ubuntu 1204 guest using 5.2.8 or GA 5.2.7,Linux,VirtualBox 5.2.8,2018-02-28T22:51:03Z,2018-05-22T09:56:11Z,2018-05-22T09:56:11Z,"After installing 5.2.8 (and also after testing GA 5.2.7 against 5.2.6 to address 3D acceleration bug - Ticket #17463, Ticket #17569) my Ubuntu 1204 system became unusable. E.g. when I try to run terminal I cannot see the console window and cannot switch to it with Alt-Tab or any other means. The Alt-Tab icons look different as well. The problem went away on 5.2.6 after moving back to GA 5.2.6 but I really need a fix for the 3D issue so that is not where I want to be.",tomasth
17729,Current GuestAdditions have problems with resolutions on CentOS 6.2 guests,Linux,VirtualBox 5.2.8,2018-05-04T11:24:12Z,2018-05-15T15:51:35Z,2018-05-15T15:51:35Z,"Hi. Plse see this discussion for additional details, log files and a duplication procedure: https://forums.virtualbox.org/viewtopic.php?f=6&t=87685&start=15

In short, on a CentOS 6.2 guest I am stuck with only three display resolution settings if I use GuestAdditions >= 5.1.0. GAs version 5.0.40 work fine and offer a multitude of resolutions and although I have not tried it, I suspect that using 5.0.40 I could also use xrandr to add additional modes. Moderator socratis has reproduced the issue also in 5.2.10. I have not tried this on other hosts than my Win7 laptop. socratis is on a MAC if I remember correctly, I doubt the host matters here. For me personally the priority could be set to minor since there is a workaround, on the other hand, many users may  depend on other GAs-stuff fixed in newer versions.",MatsBoekelund
17690,Windows 98SE will not install,Windows,VirtualBox 5.2.8,2018-04-17T03:15:20Z,2018-04-26T09:19:52Z,2018-04-26T09:19:52Z,"Hi, Windows 98SE won't install on my system.

Here's the sitation.

I have two Win 98SE installation packages.  One is a bootable CD, the other a non-bootable one.

With the bootable installation CD, the error appears immediately.  With the non-booable one (where setup is started with MS-DOS), the machine goes a fair way through the process..installing the system on the hard drive. The error appear when the system reboots to load WIN98 from the hard drive to complete the installation .

The error is the same in both cases. It says ""

VirtualBox.exe - Application Error

The instruction at 0x77839A95 referenced memory at 0x000C000C.  The memory could not be written.""

Installation cannot proceed from this point.

I'm using Virtual Box Version 5.2.8 r121009 (Qt5.6.2)

The machine I am using is a 32-bit Intel(R) Core TM i5 CPU running Windows 10.  

In the virtual machine, the acceleration tab in the System property is greyout out (I've checked CMOS and it looks as if the motherboard doesn't support hardware virtualisation). All extended features (PAE/NX, I/O APIC) are switched off.  RAM is set for 64MB.

Other OS's (MS-DOS, Windows 95, Windows 2000, Xp and 7) install just fine.

The Log attached is that produced from the bootable CD.",tezza
17670,clonevm --groups does not create new group,Windows,VirtualBox 5.2.8,2018-04-06T10:55:31Z,2018-04-20T19:29:27Z,2018-04-20T19:29:27Z,"`VBoxManage clonevm VM1 --groups /NewGroup --register` successfully clones and registers `VM1` (placing it in a subdirectory `NewGroup`), but does not create the group `/NewGroup`. (`VBoxManage list groups` does not show the new group.)",BrianNixon
17680,Problem Starting Windows 10 VM,Windows,VirtualBox 5.2.8,2018-04-12T16:02:05Z,2018-04-20T07:11:18Z,2018-04-20T07:11:18Z,"Dear, I use windows 10 pro (64-bit) on my physical machine in version 1709 and need to install install vm with windows 10 pro (32-bit). But when you start vm you have an error. Code: ""Failed to open a session for Win10 virtual machine.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

""

I have already changed the settings several times, but all to no avail.
Any help is welcome.

I have a dropbox link where I am sharing the error screens.
https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0

[https://www.dropbox.com/sh/0tlbv6jkd30s2rm/AAAwI4y48RckShxbcYhFH-NRa?dl=0]

Thank you!",macklains
17662,NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries),Windows,VirtualBox 5.2.8,2018-04-03T17:57:25Z,2018-04-19T21:26:40Z,2018-04-19T21:26:40Z,"Unable to start the VM after system reboot

{{{

{{{
9d4.9d8: supR3HardNtChildPurify: Done after 1093 ms and 1 fixes (loop #1).
9d4.9d8: supR3HardNtEnableThreadCreation:
293c.2ac4: Log file opened: 5.2.8r121009 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa03ad700
293c.2ac4: supR3HardenedVmProcessInit: uNtDllAddr=00007ff906860000 g_uNtVerCombined=0xa03ad700
293c.2ac4: ntdll.dll: timestamp 0xb79b6ddb (rc=VINF_SUCCESS)
293c.2ac4: New simple heap: #1 0000000000c00000 LB 0x400000 (for 1945600 allocation)
293c.2ac4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume1\Program Files\Oracle\VirtualBox'
293c.2ac4: System32:  \Device\HarddiskVolume1\Windows\System32
293c.2ac4: WinSxS:    \Device\HarddiskVolume1\Windows\WinSxS
293c.2ac4: KnownDllPath: C:\WINDOWS\System32
293c.2ac4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
293c.2ac4: Error opening VBoxDrvStub:  STATUS_OBJECT_NAME_NOT_FOUND
293c.2ac4: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034
293c.2ac4: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
293c.2ac4: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: supR3HardenedWinCheckChild: enmRequest=2 rc=-101 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
9d4.9d8: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3)
9d4.9d8: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.
}}}

}}}
",AshokMazumder
17660,Critical Error on Boot,Windows,VirtualBox 5.2.8,2018-04-02T21:28:56Z,2018-04-19T20:47:18Z,2018-04-19T20:47:18Z,"can not star my virtual machine, I recceive a critical error and cirtual machine stops.",joaocamara
17654,Windows 98 VM won't boot,Windows,VirtualBox 5.2.8,2018-03-30T22:01:22Z,2018-04-19T20:37:39Z,2018-04-19T20:37:39Z,"Every time that I try to install Windows 98 on a VM, the VM would not boot at all, showing two different errors: [https://imgur.com/3m4qkX5] [https://imgur.com/xQWl2HV]

The only two OSs that I know of that do this when I try to install them are Windows 98 and Windows ME, any help?",GenericUsername
17646,Failure to launch windows 10,other,VirtualBox 5.2.8,2018-03-29T01:44:05Z,2018-04-19T18:46:29Z,2018-04-19T18:46:29Z,"I'm not entirely sure what's going on. Every time I go to launch VirtualBox, VirtualBox Interface and VirtualBox Manager just sit in my tasks. No gui comes up. Nothing is changing. The processes are not using anything except for ram (which also doesn't change). It's not crashing. It's just nothing. I've tried installing the newest version. I tried the test version, Compatibility, administrator. All my drivers are up to date. I am honestly stumped. If anyone wants to give me some advice on how to fix this that would be great. If it helps at all I can run the free VMware just fine.

I don't have a log file because one is not created in this situation as it never crashes and continues to be benign

I am running 
latest version of windows 10 pro
AMD Ryzen 5 1600X
NVIDIA GeForce GTX 1070
",Deszip
17640,supR3HardenedWinReSpawn VERR_INVALID_NAME on specific driver paths,all,VirtualBox 5.2.8,2018-03-26T17:13:11Z,2018-04-19T18:09:38Z,2018-04-19T18:09:38Z,"When Hardening rejecting DLL with name like ""\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll"", an error will always show as below and none of the VM can be started.


VirtualBox - Error In supR3HardenedWinReSpawn 
Error relaunching VirtualBox VM process: 5 Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment Windows10 --startvm 1e2c22cb-276b-43b0-9049-1e50628f9490 --no-startvm-errormsgbox ""--sup-hardening-log=C:\Users\latifrons\VirtualBox VMs\Windows10\LogsWBoxHardening.log's (rc=-104) 
Please try reinstalling VirtualBox. 
where: supR3HardenedWinReSpawn what: 5 '''VERR_INVALID_NAME''' (-104) -Invalid (malformed) file/path name. 


VBoxHardening.log:
{{{
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: Error (rc=0):
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23021 (0xffffa613) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1024 \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll
4530.4674: Error (rc=0):
4530.4674: supR3HardenedMonitor_LdrLoadDll: rejecting 'D:\opt\adguolvds\glhp64.dll' (D:\opt\adguolvds\glhp64.dll): rcNt=0xc0000190
4530.4674: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'D:\opt\adguolvds\glhp64.dll'
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]WinVerifyTrust]\Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4530.4674: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume6\opt\adguolvds\glhp64.dll [lacks WinVerifyTrust]
4788.4444: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 129076 ms, the end);
}}}


Seems that file path beginning with \Device is not supported?

How to get this dll:
Goto http://www.admon.cn and download the installer at the bottom of the page. This software is a low level ad removing tool which hooks many processes. D:\opt\adguolvds\glhp64.dll is its dll hook.

For those who comes here from Google:
Just remove this software and your VirtualBox will be fine.",latifrons
17632,aero in vBOX,Windows,VirtualBox 5.2.8,2018-03-22T09:05:17Z,2018-04-19T15:39:30Z,2018-04-19T15:39:30Z,"in virtualbox, when i install windows 7 for exemple and install add-ons for drivers, i am not able to activate aero or other visual effects. I have also activate 3d support in the configuration of the VM.

Is it a bug?",jejelegeek
17685,Weird acting of vboxmanage.exe's --compact flag,Windows,VirtualBox 5.2.8,2018-04-14T17:29:01Z,2018-04-18T15:01:10Z,2018-04-18T15:01:10Z,"When using the 
{{{
vboxmanage modifymedium <virtual VDI disk> --compact
}}}
command on a dynamic type VDI disk (previously nulled the free spaces, with [https://technet.microsoft.com/en-us/library/2009.08.utilityspotlight.aspx Sdelete] on Windows), it seems to be successful, though, the resulted image's content cannot be viewed with [https://www.7-zip.org/ 7zip] anymore, even though, VDI is a supported format of it and before running the command, it was working too. At this point, the image is mountable and the system on it is bootable, like it should.
But, after all of these, when i try to clone the image with
{{{
vboxmanage clonemedium <input file> <output file>
}}}
even though, the operation is finishes, without any problems, the system on the cloned disk, isn't bootable anymore, because the whole VM crashes, right in the middle of the boot process. Suprisingly, it can be opened with 7zip again. Cloning again and again doesn't change anything, while ''chkdsk'' cannot find any problems.
Additionally, this isn't the first case, when i have to face with this issue, so i guess, i can label it, as reproducible.",T800
17596,Critical Error occurs when trying to build Ubuntu 16.04.4,other,VirtualBox 5.2.8,2018-03-06T15:22:55Z,2018-04-17T13:08:10Z,2018-04-17T13:08:10Z,"VirtualBox allows me to create a new VM, but just a couple seconds after I point to the ISO for the start-up disk selection, I get a somewhat generic error screen.  It's titled ""VirtualBox - Guru Meditation "".  It says ""A critical error has occurred while running the virtual machine and the machine execution has been stopped.""

I've used many other versions of Ubuntu and Linux on this Win10 host running VirtualBox version 5.2.8 r121009.  I've downloaded this Ubuntu-16.04.4-desktop-i386.iso from several different sources now and they all yield the same result when trying to build a VM.",runnerb0y
17684,Windows Server 2016 guest freezes after a few minutes,Windows,VirtualBox 5.2.8,2018-04-13T12:22:13Z,2018-04-13T12:22:13Z,2018-04-13T12:22:13Z,"VirtualBox Version:
5.2.8 r121009 (Qt5.6.2)

Host:
Microsoft Windows 10 Pro
64-bit
Version        : 10.0.16299
BuildNumber    : 16299

Guest:
Windows Server 2016 (64-bit)

Problem:
Guest freezes after a few minutes. Happens every time I restart the guest.

Host & guest up-to-date with updates.

Host has been rebooted and problem continues.

Log attached.",rafinnerty
17681,mini toolbar not working. Seamless mode is never on,Windows,VirtualBox 5.2.8,2018-04-12T19:22:56Z,2018-04-12T19:22:56Z,2018-04-12T19:22:56Z,"I was not able to open a VM win7 in Seam Less mode. 

Also, Mini Tool Bar is not visible. Even after setting in the User Interface tab in the settings.

I installed Oracle Virtual Box in Win server 2012 R2",smangu
17669,Virtual Box not saving Default Machine Folder after closing app,Linux,VirtualBox 5.2.8,2018-04-06T03:55:38Z,2018-04-06T03:55:38Z,2018-04-06T03:55:38Z,"The version of VBox I have is 5.2.8. I have Windows 10 as my host. I have an SSD as my C drive and a HDD as my D drive. Both internal drives. When I go to file-> Preferences->Default Machine Folder->Other and select a folder on my D drive. It changes. However, when I close the application, all the preferences revert back to the default, and the VMs that were save to the D drive are removed from the main list of VMs.",Joe5232
17635,Linux guest OGL regression in 5.2.8 (LKG 5.1.30),Linux,VirtualBox 5.2.8,2018-03-23T07:20:30Z,2018-03-23T07:20:30Z,2018-03-23T07:20:30Z,"After updating the host from 5.1.30 to 5.2.8, an Ubuntu 16.04 guest that has 3D enabled continued to work fine for a couple of hours, until I got round to updating the GAs as well. At that point, restarting the guest arrived at the desktop but immediately started consuming memory at an impressive rate, killing the X session (as you'd expect).

The leak can be traced to the Compton compositor, which when started from a terminal instead of automatically is spitting out thousands of these messages:

glx_bind_pixmap(32): Couldn't find FBConfig with requested depth.
win_paint_shadow(0x0320002d): Missing painting data. This is a bad sign.

glxinfo looks good, containing the one visual I'd expect to see:

1 GLX Visuals
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y y   8  8  8  8 .  .  0 24  8 16 16 16 16  0 0 None

1 GLXFBConfigs:
    visual  x   bf lv rg d st  colorbuffer  sr ax dp st accumbuffer  ms  cav
  id dep cl sp  sz l  ci b ro  r  g  b  a F gb bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------------
0x021 24 tc  0  32  0 r  y .   8  8  8  8 .  .  0 24  8  0  0  0  0  1 1 None

I can try bisecting to narrow down the breaking revision, but it'll take a while.
",arQon
17630,wireshark can capture only one way packet,other,VirtualBox 5.2.8,2018-03-20T11:30:15Z,2018-03-21T13:24:45Z,2018-03-21T13:24:45Z,"hi
I have windows 10 computer. 
I installed virtual box 5.2.8 and vmware workstation 14. 
I have created ubuntu vm on both virtual box and workstation and bridged network adapters to 
physical interface.  
I have installed wireshark to my computer. 
when I tried to get IP from DHCP server of DSL modem, virtualbox ubuntu get IP with same IP of the host computer. why? should it get different IP from host computer? isn't it?
I have set up static IP to ubuntu machines. I can send packets between host computer, virtual box ubuntu, vmware ubuntu and DSL modem.
when I tried to capture packets with wireshark from physical interface, I can capture both direction between host and vmware but I cannot capture virtual box packets both direction.
I can see only virtual box ubuntu outbound traffic to other machines, I cannot see inbound traffic from other machines. during this period, all traffic goes succesfully. 
why I couldn't see inbound traffic to virtual box machines. 
     ",sesci
17591,windows10 host failed to open a session for virtual machine,Windows,VirtualBox 5.2.8,2018-03-06T06:50:10Z,2018-03-08T07:35:24Z,2018-03-08T07:35:24Z,"host:
OS name:          Microsoft Windows 10 enterprise
OS edtion:          10.0.16299  
manufactor:       Dell Inc. OptiPlex 790    x64-based PC

BIOS edtion:        Dell Inc. A18, 2013-9-24


The virtual machine 'win10'
 has terminated unexpectedly
 during startup with exit code -1073741819


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
",eiddy
17595,Try to attach USB device to VM crashes the VM,Linux,VirtualBox 5.2.8,2018-03-06T14:51:24Z,2018-03-06T14:51:24Z,2018-03-06T14:51:24Z,"When enabling access to intel USB device (Vendor ID: 8087 Product ID: 07dc) the VM gets totally stucked and a reboot of the host is necessary. That is easily reprocible and happens each time.

The logs displays this error message:
ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={c19073dd-cc7b-431b-98b2-951fda8eab89} aComponent={HostUSBDeviceWrap} aText={USB device 'Intel Corp.' with UUID {674944f8-07e8-4224-b303-cb4161d16cb4} is busy (state 'CapturingForVM[Detach]'). Please try again later}, preserve=false aResultDetail=0

Tried with Lubuntu & Debian Guest OS. Of course guest Add-ons have been properly installed.

The bluetooth device works properly on the host.

",jeanbox
17589,No virtual screen repaint when external monitor is connected to laptop.,Linux,VirtualBox 5.2.8,2018-03-05T10:44:33Z,2018-03-05T10:44:33Z,2018-03-05T10:44:33Z,"I have Windows 10 host with Ubuntu 16.04 guest. With enabled 3D acceleration (which is required because without that everything is laggy) and external monitor connected (tested with dvi and mini display port), the drawing on virtual screen freezes when in gnome. It does not matter whether monitor is an extension, clone or primary display. Immediately after monitor disconnection, the virtual screen starts to repaint.

Under the frozen screen the system is running (cursor changes with the windows even after repositioning which is not visible on the frozen screen, ctrl alt fx can be used to display working and visible shell).

When 3D acceleration is disabled, screen repaints fine with external monitor connected. 
I tested also development version 5.97 with the same result.",mvodolan
17587,exiting full screen resizes guest desktop size,Windows,VirtualBox 5.2.8,2018-03-05T09:01:41Z,2018-03-05T09:01:41Z,2018-03-05T09:01:41Z,"Steps to reproduce:
1. Turn on Auto-resize Guest Display.
2. Enable Full-screen Mode.
3. Turn off Auto-resize Guest Display.
4. Disable Full-screen Mode.
Guest display is resized despite auto-resize is off.

This bug might be related to #6917, #7219 and possibly also to #14948.",_mik
18285,Cannot paste copied Chromium URL into Windows,Linux,VirtualBox 6.0.0,2019-01-07T17:03:12Z,2020-02-24T09:48:32Z,2020-02-24T09:48:32Z,"If I copy the URL in Chromium's address bar on the Linux VM, I cannot paste it into any app on my Windows host. So far, all other uses of the bidirectional clipboard, either direction and with any application, works fine. Also, I can paste a copied Chromium URL into any other app on the same VM.

I have a Ubuntu 18.10 VM on VirtualBox 6.0 running on Windows 10 Pro x64 host. Running the release of Extension Pack that is for VirtalBox 6.0.0. In case it matters, I created this app on a 5.2 release of VirtualBox.

This seems like a VirtualBox bug because it only happens with a specific use of VirtualBox's bidirectional clipboard feature.",Aren Cambre
18308,Aero/transparency on Windows Vista no longer working with VirtualBox 6.0.0 r127566,Windows,VirtualBox 6.0.0,2019-01-13T09:52:01Z,2019-10-21T21:02:58Z,2019-10-21T21:02:58Z,"I performed the following steps:
* On my Windows 10 Professional (version 1809, build 17763.253) host, I upgraded VirtualBox 5.2.22 to 6.0.0 r127566
* In an exisiting Windows Vista Ultimate guest, upgraded VirtualBox Guest Additions from 5.2.22 to 6.0.0. 
* During the Guest Additions upgrade, as before, I selected experimental 3D accelleration and chose ""no"" when asked if I wanted basic Direct3D support.
* Restarted the guest when prompted.

After these steps: 
* Aero/transparency effects no longer work in the Vista guest (and Aero is no longer offered as an option within Windows Vista) where they did with VirtualBox 5.2.22 and earlier 5.2 versions.
* The VBox.log indicates that 3D is enabled and available, and contains no apparent indications of errors.",Rutger van Bergen
18212,Windows 10 Host - Hardening error - VMs do not start,Linux,VirtualBox 6.0.0,2018-12-20T15:01:59Z,2019-08-07T13:56:10Z,2019-08-07T13:56:10Z,"Windows 10 Host - Hardening error - VMs do not start

Steps (on latest Windows Release build - Windows 10 x64 Version 1809 Build 17763.195):

- Install and use !VirtualBox v6.0.0
- Start with a Linux VM that has a restored snapshot from v5.2.23 (mine was from !VirtualBox v5.2.23 Test Build 127495)
- Start the VM - it starts successfully
- Take an online snapshot
- While the VM is running, delete the old v5.2.23 snapshot
- Power off the VM
- Restore the online snapshot
- Attempt to Start the VM
- BUG: Progress gets to 97% and hangs. It does not start. Later, a secondary progress dialog appears on the VM Manager window, and also hangs.
- NOTE: The following lines in VBoxHardening.log may indicate a problem with ""wintab32.dll"":
{{{
2658.2dec: supR3HardenedMonitor_LdrLoadDll: error opening 'C:\WINDOWS\system32\wintab32.dll': 0 (NtPath=\??\C:\WINDOWS\system32\wintab32.dll; Input=C:\WINDOWS\system32\wintab32.dll; rcNtGetDll=0x0
2658.2dec: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000034 'C:\WINDOWS\system32\wintab32.dll'
}}}
Attached are:
- .vbox files (multiple versions), showing the progression of the steps
- .log files (VBox.log, VBoxHardening.log)
- Image showing failure

This worked properly using !VirtualBox v5.2.23 Test Build 127495.

Let me know if you require the actual VM itself.",Jacob Klein
18451,Guest Additions breaks keyboard on Windows Server 2019 Guest,Windows,VirtualBox 6.0.0,2019-02-25T14:54:51Z,2019-02-25T14:54:51Z,2019-02-25T14:54:51Z,"Host = Windows 10 64-bit
Guest = Windows Server Core 2019 64-bit
Note: Core means no Desktop GUI included i.e. Command-line only

After installing Guest Additions, the keyboard no longer works inside the Guest, meaning I cannot type anything inside the guest command line. I used remote desktop to access the guest so I could uninstall Guest Additions after which the keyboard works fine.
",jahbwoy0
18221,"Getting ""can't apply partial context to unlabeled file"" in Version 6.0.0 -> fixed after (not in) 5.2.26/6.0.4",Linux,VirtualBox 6.0.0,2018-12-22T03:20:08Z,2019-01-31T22:40:16Z,2019-01-31T22:40:16Z,"While booting after changing to Version 6 of VirtualBox running a guest  Oracle Linux 4.1.12-124.22.4.el6uek.x86_64, I get the following message in boot.log:
{{{
VirtualBox Guest Additions: Starting.
chcon: can't apply partial context to unlabeled file `/opt/VBoxGuestAdditions-6.0.0/src/vboxguest-6.0.0/build_in_tmp'
Starting auditd: ^[[60G[^[[0;32m  OK  ^[[0;39m]^M
}}}

It seems stuff is working, I think, but would like to know if this error is a sign that trouble is on the way.

The machine log is also attached.",DonC
18228,Copy/Paste From Shared Folder Hangs Win7 32 bit Guest With 6.0.0r12766 Additions,Windows,VirtualBox 6.0.0,2018-12-23T21:40:47Z,2019-01-27T22:02:03Z,2019-01-27T22:02:03Z,"VBox 6.0.0r127566 (QT5.6.2) in win10 1809 host with win7 32 bit guest works fine using additions from previous release. After updating guest to new additions attempting to copy a file from a shared folder hangs the win7 32 bit guest. If VM is powered down -- regular shut down or restart won't work -- & restarted, shared folder will not show up in win7 guest's Windows Explorer. If when the guest is shut down, VBox is closed & restarted, the shared folder will appear, but the guest hangs next time any file transfer is attempted.",mikiem
18336,Virtual Box Extension Pack 6.0.0 Installation Error,Windows,VirtualBox 6.0.0,2019-01-19T13:49:22Z,2019-01-20T08:10:14Z,2019-01-20T08:10:14Z,"Every time I update VirtualBox and install extension pack I got an error message.In previous update when I update VirtualBox to 6.0.0 and then I install Extension Pack I got the same error message.
I have detailed video link of this error message on youtube:- https://youtu.be/orHQHsoe6NY

Can any one help me?",Binoy
18320,Virtual Hard Disk wizard defaults to file size less than recommended for Ubuntu 18,Linux,VirtualBox 6.0.0,2019-01-17T00:28:43Z,2019-01-19T20:51:09Z,2019-01-19T20:51:09Z,"Using VirtualBox 6.0.0 r127566 (Qt5.6.2) on host Windows 7 SP1 amd64.

I am creating a new VM using the GUI wizard. The Create Virtual Machine wizard detects I am intending to install Ubuntu and set the ""Version"" to ""Ubuntu (64-bit)"". The Virtual Hard Disk wizard defaults to a 10GB hard disk.

The download page for Ubuntu 18 (Desktop) at https://www.ubuntu.com/download/desktop suggests 25Gb of free hard drive space.

",Adam Piggott
18306,Virtual box causes the PC to restart many times,other,VirtualBox 6.0.0,2019-01-13T01:55:44Z,2019-01-14T19:15:28Z,2019-01-14T19:15:28Z,"Since one year ago I observed that my PC, when left in stand-by, restarted continuously at night after 2.00 p.m.. 
After many attempts I verified that whenever VirtualBox was open, this continuous restart happened. When it was closed, it did not. 

Recently, I upgraded to VB 6.0 and tried again: same result.

I've observed this behaviour n two different PCs, both using up-to-date Windows 10 64 bit.",ceraolo
18214,"VM Crash when hovering optical media menu, with inaccessible media",other,VirtualBox 6.0.0,2018-12-20T17:02:19Z,2019-01-14T17:33:13Z,2019-01-14T17:33:13Z,"Reproduce:
* Start VM
* Menu -> hover Optical media 
* an last used optical media exists which is on an inaccessible/office n etworkstorage
* the vm freezes and crashes after some seconds
* if you leave vboxmanager open, a second try works,
* if you close it, its crashing again

The bug exists at least since v5.0

Its very annoying to me, I'm using a NAS-Box which shutdowns over night till i manually start it, when i start a vm beforce that and hover the menu by accident -> crash

e.g. ISO image on \NAS542\image\Win10.iso",serpen
18311,user interface not accessible any more using nvda screen reader,other,VirtualBox 6.0.0,2019-01-14T12:02:40Z,2019-01-14T12:02:40Z,2019-01-14T12:02:40Z,"running windows 10 pro insider build with nvda screen reader.
can access file menus e.g file edit view but not able to hear the names of the virtual machines or arrow in the settings.
virtualbox 6.0
please could this be fixed?
Majid",maj
18310,Can't change display settings in an Oracle Linux 6.5 guest,Linux,VirtualBox 6.0.0,2019-01-14T07:42:32Z,2019-01-14T08:37:37Z,2019-01-14T08:37:37Z,"I recently updated to v 6.0.0 r 127566 on Windows 10. All other guests (Debian Linux distros & earlier Windows versions) work fine, except Oracle Linux 6.5. Display becomes garbled when trying to change the resolution after installing the Guest Addition.",whosnick
18307,VM Hang during installing of Centos,other,VirtualBox 6.0.0,2019-01-13T08:10:48Z,2019-01-14T08:13:22Z,2019-01-14T08:13:22Z,"Hello Team,
i created new VM and attach the Centos 7 ISO file
the installation screen appears after that it hang 
i tried to change the display settings as i suspect its video card issue 
but its the same issue 
i attached the logs 
thanks for support 
regards

",Alaa
18302,Can not install VirtualBox Guest Additions in CentOS 6.10,Linux,VirtualBox 6.0.0,2019-01-11T18:10:19Z,2019-01-12T17:17:14Z,2019-01-12T17:17:14Z,"I am using Vagrant 2.2.3 and I have installed the latest VirtualBox 6 (VirtualBox-6.0.0-127566-Win). My Vagrantfile looks like follow:

{{{
  # -*- mode: ruby -*-
  # vi: set ft=ruby :

  Vagrant.configure(""2"") do |config|
    config.vm.box = ""reynierpm/centos6""
    config.vm.box_version = ""4""

    config.vm.provider :virtualbox do |vb|
      vb.customize [""modifyvm"", :id, ""--memory"", 2048]
    end
  end
}}}

But VirtualBox Guest Additions won't install and fails with the following error:

    VirtualBox Guest Additions: modprobe vboxsf failed

Have tried to install them manually and I got the same result:

{{{
# sh VBoxLinuxAdditions.run                                                          
Verifying archive integrity... All good.                                                                   
Uncompressing VirtualBox 6.0.0 Guest Additions for Linux........                                           
VirtualBox Guest Additions installer                                                                       
Removing installed version 6.0.0 of VirtualBox Guest Additions...                                          
vboxadd-service.sh: Stopping VirtualBox Guest Addition service.                                            
You may need to restart your guest system to finish removing the guest drivers.                            
Copying additional installer modules ...                                                                   
Installing additional modules ...                                                                          
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run                              
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>                                         
VirtualBox Guest Additions: Building the modules for kernel 2.6.32-754.9.1.el6.x86_64.                     
																										   
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong                 
VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted      
VirtualBox Guest Additions: Starting.                                                                      
VirtualBox Guest Additions: modprobe vboxsf failed                                                         
}}}

Logs aren't helpful:
{{{
# cat /var/log/vboxadd-setup.log
Could not find the X.Org or XFree86 Window System, skipping.
}}}",reynierpm
18287,windows 10 x64 guest crashes (vb restarts the guest windows),Windows,VirtualBox 6.0.0,2019-01-08T12:16:53Z,2019-01-08T14:44:24Z,2019-01-08T14:44:24Z,"so I have a windows x64 host and a windows x64 guest, from time to time the os of the guest reboots for no reason (no error shown)",xhums1
18253,"Windows10 sleep, wake up, VirtualBox(V6.0.0) display: abnormal exit.",Linux,VirtualBox 6.0.0,2018-12-31T12:14:04Z,2019-01-07T05:10:39Z,2019-01-07T05:10:39Z,"Host Machine System: Windows10 1809
Virtual Machine System: CentOS7.0
Virtual machine running, and then wait 10 minutes not to use Windows system, then Win sleep... Then, wake up Windows, VirtualBox shows: abnormal exit.",solan
18260,Not able to Start VM in Virtual Box when Bridge Adapter Network Setting is Selected After latest update to Windows 10,Linux,VirtualBox 6.0.0,2019-01-01T07:40:50Z,2019-01-05T15:27:30Z,2019-01-05T15:27:30Z,"Hi Team,

I am Not able to start VM on virtual box when Bridge Adapter Network Setting is Selected and This is seen after latest update to Windows 10.

Have tried all the possible solutions listed in google, Nothing Worked.

Have tried 5.2.18, 5.2.22 and also 6.0 versions of VB but observing same Error on all these version.

Below Error is Observed:

Failed to open a session for the virtual machine .

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Linda
18276,Graphic glitches,Windows,VirtualBox 6.0.0,2019-01-04T00:18:57Z,2019-01-04T01:10:07Z,2019-01-04T01:10:07Z,"When i downloaded the version 6.0.0 (first time install on this computer on all of versions of windows that i installed xp-10)i installed the virtualbox guest additions as well and when i am moving the windows programs i see graphic glitches and problems during moving the window on host and i am using cpu virtualaziation too.


my system specs

AMD A8-9600, 
Kingston 4gb ram ddr4 2666 mhz
, ASRock A320M Pro4 (mb)
 ,Coolermaster masterwattlite 500w 80+
 and Intergrated GPU AMD Radeon R7 ",Undead
18241,unable to install centos in VM. Facing error which says kernel panic,other,VirtualBox 6.0.0,2018-12-27T21:28:06Z,2018-12-28T02:23:58Z,2018-12-28T02:23:58Z,"installed virtual box
created Virtual machine.
tried to install centos 7 but i facing issue over here. getting an error which says kernel panic - not syncing : fatal exception
",Vishal Pokala
18231,unable to see mouse pointer in guest,Linux,VirtualBox 6.0.0,2018-12-24T21:56:53Z,2018-12-24T21:56:53Z,2018-12-24T21:56:53Z,,kapstone
18208,VMs with a PIPE in the name cannot be moved in groups,all,VirtualBox 6.0.0,2018-12-20T09:58:26Z,2018-12-23T17:46:13Z,2018-12-23T17:46:13Z,"If a machine has a PIPE (|) in its name it cannot be moved in or out a group because the config file of the machine (vbox) cannot be edited.

If I rename the VM and replace the pipe with another character (i.e. a minus or a space) it works perfectly.",KevinW
18209,Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox,Linux,VirtualBox 6.0.0,2018-12-20T11:22:46Z,2018-12-20T11:25:32Z,2018-12-20T11:25:32Z,"Intel(R) Xeon(R) W-2102 is not recognized by VirtualBox, and it does not report to guest system that this CPU supports AVX512 instruction sets. I tried to modify CPUID data for guest, but after doing so Linux guest was not able to boot, so looks that some extra support on VBox side it needed too.

VBoxManage.exe list hostcpuids
Host CPUIDs:

Leaf no.  EAX      EBX      ECX      EDX
00000000  00000016 756e6547 6c65746e 49656e69
00000001  00050654 04100800 7ffefbff bfebfbff
00000002  76036301 00f0b6ff 00000000 00c30000
00000003  00000000 00000000 00000000 00000000
00000004  1c004121 01c0003f 0000003f 00000000
00000005  00000040 00000040 00000003 00002020
00000006  00000ef5 00000002 00000009 00000000
00000007  00000000 d39ffffb 00000000 9c000000
00000008  00000000 00000000 00000000 00000000
00000009  00000000 00000000 00000000 00000000
0000000a  07300804 00000000 00000000 00000603
0000000b  00000001 00000001 00000100 00000004
0000000c  00000000 00000000 00000000 00000000
0000000d  000000ff 00000a80 00000a80 00000000
0000000e  00000000 00000000 00000000 00000000
0000000f  00000000 0000002f 00000000 00000002
00000010  00000000 0000000a 00000000 00000000
00000011  00000000 00000000 00000000 00000000
00000012  00000000 00000000 00000000 00000000
00000013  00000000 00000000 00000000 00000000
00000014  00000001 0000000f 00000007 00000000
00000015  00000002 000000f2 00000000 00000000
00000016  00000b54 00000b54 00000064 00000000
00000017  00000b54 00000b54 00000064 00000000
80000000  80000008 00000000 00000000 00000000
80000001  00000000 00000000 00000121 2c100800
80000002  65746e49 2952286c 6f655820 2952286e
80000003  322d5720 20323031 20555043 2e322040
80000004  48473039 0000007a 00000000 00000000
80000005  00000000 00000000 00000000 00000000
80000006  00000000 00000000 01006040 00000000
80000007  00000000 00000000 00000000 00000100
80000008  0000302e 00000000 00000000 00000000
80000009  00000b54 00000b54 00000064 00000000",SirZooro
18872,I cannot enable second monitor,Linux,VirtualBox 6.0.10,2019-08-28T08:47:59Z,2020-12-03T15:09:19Z,2020-12-03T15:09:19Z,"I set 2 displays in preferences. Linux starts with one. When I right click on the screen icon in the status bar, I see the second virtual display. Unfortunately, nothing happens when I click on ""Enable"".

linux xrandr 
{{{
Screen 0: minimum 1 x 1, current 1920 x 975, maximum 8192 x 8192
Virtual1 connected primary 1920x975+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1920x975      60.00*+
   2560x1600     59.99  
   1920x1440     60.00  
   1856x1392     60.00  
   1792x1344     60.00  
   1920x1200     59.88  
   1600x1200     60.00  
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.81  
   1152x864      75.00  
   1280x768      59.87  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
Virtual2 disconnected (normal left inverted right x axis y axis)
Virtual3 disconnected (normal left inverted right x axis y axis)
Virtual4 disconnected (normal left inverted right x axis y axis)
Virtual5 disconnected (normal left inverted right x axis y axis)
Virtual6 disconnected (normal left inverted right x axis y axis)
Virtual7 disconnected (normal left inverted right x axis y axis)
Virtual8 disconnected (normal left inverted right x axis y axis)
}}}




linux systemctl status vboxadd.service:
{{{
● vboxadd.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.0.11/init/vboxadd; enabled; vendor preset: enabled)
   Active: active (exited) since Wed 2019-08-28 10:31:45 CEST; 10min ago
  Process: 737 ExecStart=/opt/VBoxGuestAdditions-6.0.11/init/vboxadd start (code=exited, status=0/SUCCESS)
 Main PID: 737 (code=exited, status=0/SUCCESS)
    Tasks: 2 (limit: 4915)
   Memory: 216.7M
   CGroup: /system.slice/vboxadd.service
           ├─1231 VBoxClient --vmsvga
           └─1232 VBoxClient --vmsvga

Aug 28 10:31:42 ubuntu vboxadd[737]: modules.  This may take a while.
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: To build modules for other installed kernels, run
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions: or
Aug 28 10:31:42 ubuntu vboxadd[737]: VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
Aug 28 10:31:45 ubuntu useradd[1166]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu useradd[1167]: failed adding user 'vboxadd', data deleted
Aug 28 10:31:45 ubuntu vboxadd[737]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
Aug 28 10:31:45 ubuntu vboxadd[737]: the system is restarted
Aug 28 10:31:45 ubuntu systemd[1]: Started vboxadd.service.
}}}",Benmaxrei
18882,OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.,BSD,VirtualBox 6.0.10,2019-08-29T23:17:56Z,2020-02-18T22:35:57Z,2020-02-18T22:35:57Z,"(This looks like a repeat of the Bug #9889, but is probably unrelated.)

I'm using VirtualBox on a Windows 10 host to run a FreeBSD and some Linux VMs (guests). The FreeBSD VM is my main desktop -- and the only guest with GUI (X11) configured.

My access to the Windows host itself is through Remote Desktop -- from a ""dumb"" terminal capable of running only the Remote Desktop client.

Things were working fine until the recent upgrade of the hardware -- the same disk was moved into a new machine, with faster CPUs and bigger RAM. There were no software configuration-changes.

VMs also came up Ok, but, upon starting X11 session in the FreeBSD guest, I started getting the error in subject from various X11-clients.

Since then I tried the following changes, to no avail:
 1. Upgrade the host software (including the extras pack) from 5.x to 6.0.10
 2. Change the ""Graphics Controller"" to ""VBoxSVGA"" in the VM's definition.
 3. Upgrade the virtualbox-ose-additions inside the VM from 5.x to 6.0.10

Nothing helped -- the machine comes up fine, simpler X11-clients (like xterm) work, but many (including Qt5-using programs) fail with the same message about 3D-acceleration...

I'm attaching the X-server's log from inside the VM, and VM's log from the host.

At the very least, the error should be more detailed. At best, it should not happen :)",mi
18874,Slowdown of X11 drawings in VBox 6.0.10 in comparison to 5.2.* series.,Linux,VirtualBox 6.0.10,2019-08-28T13:39:39Z,2019-12-11T19:14:21Z,2019-12-11T19:14:21Z,"First the environment:

Host OS: Windows 10 64bit
Guest OS: Debian GNU/Linux 64-bit.
         Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-6 (2019-07-18) x86_64
Memory: 16 GB memory is assigned to VBox out of 32GB real memory.
CPU: Ryzen 2700, 6 out of 16 (8 real core + 8 hyper-thread) are
     assigned to the VBox guest.

Real Display used: 3840x2160 (60Hz) Dell 
Real Display Adaptor on the host: NVidia GeForce GT 1030

Background and Symptom:

I am using VBox under Windows 10 host on a few PC's.
I have used VBox for at least several years now.

On a home PC, I switched from 5.2 series to the latest 6.0.10 about a
couple of weeks ago, and experienced a visible slowdown of X11 drawing
inside the guest Linux. (Say, when I move terminal windows around the
screen. The move is not smooth and very jaggy).

Fast operation with VBox 5.2 series

The slowdown is so much so that I switched back to the 5.2.32 VBox
today, and verified that the moving of terminal window inside the
Linux guest that runs inside 5.2.32 VBox is fast and much
smoother. With 6.0.10 VBox, moving windows shows the wiggling of
window frame if you know what I mean.

I have duly installed the guest tool in both versions.

BTW, when I downgraded from 6.0.10, I had to reinstall/downgrade VBox
extension so that proper USB3.0 support is available.  Funny thing is
that downgraded VBox 5.2.32 resulted in the fast X11 drawing within
the guest OS when I moved the terminal window around EVEN BEFORE I
installed the guest tool. (Does the old guest tool remain in the
system? I don't think so...)

Observation: High Xorg CPU utilization with VBox 6.0.10

With VBox 6.0.10, the linux command ""top"" shows the Xorg x11 server
consuming almost 20% of CPU time CONSTANTLY. This is definitely the
symtom ofslowdown of drawing. The CPU utilization goes up near 25% if
heavy drawing is involved: I felt that other operation became also
slow from time to time. Xorg was slowing down everything, I think.

OTOH, with VBox 5.2.32, Xorg server in the linux guest OS spends
only 2.3% of CPU time when there is not much X11 drawing and the
utilization goes up to 5-6% or so when I move the terminal window, etc..
There is a clear difference of drawing efficiency here between the linux guest in Vbox 6.0.10 and 5.2.32.

Display Setting of VBox

Naturally I checked the display setting of the VBox.

Memory for the graphics display is set to 128MB (maximum) in both
versions of VBox. (BTW, is this memory size relevant in the days of 4K
color display? Or does the guest tool tries to access the native
graphics adaptor memory directly???) 

With VBox 5.2.32, 2D/3D acceleration is set to 3D acceleration only.

With VBox 6.0.10, there are choices of VGA, ..., SVGA. I checked the
both setting of VGA and SVGA and their choice did not make much
difference:Still slow drawing in both cases.
With 6.0.10., 3D setting does not seem to offer much improvement. I
mean disabling (not marking it) does not change much. (I wonder if the
guest graphics module is working or not ...)

When I tried to set 2D under 6.0.10, VBox says it is an illegal
setting and ignored stating that the virtual machine is set to use
video streaming (?) acceleration and it is only supported for Windows
guest and thus ignored. (Sorry, I am using a Japanese-locale Windows
and and the message shown is in Japanese and the above is my best
attempt to translate the gist of the message for this report.)

Well, I can use this 5.2.32 or subsequent 5.2 series until June 2020
when the support of 5.2 series will be terminated.

But I certainly hope to see this issue resolved on this PC before 
5.2 series will become unsupported so that I can use 6.0.x series
comfortably without X11 drawing slowdown..

Strange thing is that I don't think I see similar slowdown problem on another
PC that I use at the office. That machine uses Intel CPU with built-in
graphics co-processor and so it does not use separate graphics
adaptor. It also runs Windows 10 64-bit and runs Debian GNU/Linux.
It runs VBox 6.0.8 or 6.0.10 (I need to re-check.) but the speed of X11
redrawing in the guest linux OS is just fine there.
That VBox 6.0 series runs fine on that office PC was the reason I wanted to
switch to 6.0 series on my home PC in the first place.

Does anyone see similar X11 slow down inside the linux guest under
Windows?

TIA





",ci-zephyurus
18883,Issue with USB joystick SPEEDLINK COMPETITION PRO,Windows,VirtualBox 6.0.10,2019-08-30T10:29:38Z,2019-09-29T15:23:00Z,2019-09-29T15:23:00Z,"Issue when arcade joystick Speedlink Competition Pro is inserted: when VBox GUI is running ('''don't need to start a VM''') this device switches erroneously from
SPEEDLINK COMPETITION PRO (VID_0738&PID_2217)
into
Game Controller for Android (VID_0079&PID_181C).

The same issue was already fixed by SDL author blacklisting the device from HID enumeration, so I hope you can do the same to solve this problem forcing me to unplug the device every time:
https://hg.libsdl.org/SDL/rev/64d32e614d64 ",hexaae
18940,"Smart hide, auto-hide, hot corners and etc.. not working",Linux,VirtualBox 6.0.10,2019-09-18T04:26:48Z,2019-09-20T16:50:19Z,2019-09-20T16:50:19Z,"Docks, top bars and title bars can be easily hidden by configuring the system from the settings or by downloading extensions. But none of them showing up when pointing/pushing/triggering their hot corners or places....",centaurusa
18908,The access to shared folder hangs the vmachine and makes it to restart itself,Windows,VirtualBox 6.0.10,2019-09-05T06:31:47Z,2019-09-05T09:07:55Z,2019-09-05T09:07:55Z,"Sometimes when I connect to the shared folder the vmachine W1064bits hangs and 1 or 2 seconds after, restarts itself. I change the host machine, I reinstall a new vmachine but I got the same issue.
I updates the guestaddit from 6.0.10 to 6.0.12 but no change",llazare
18891,USB support feature make error in silent installation,Windows,VirtualBox 6.0.10,2019-09-02T10:27:44Z,2019-09-02T12:15:02Z,2019-09-02T12:15:02Z,"Hello,

I tried to make silent install via msiexec.exe and with .msi file. So, when I used command ""msiexec /i [path/to/file.msi] /norestart /qn"" nothing happened. I attach log from one of my tries. 

This problem applies to 6.0.10 and 5.x version.

I discovered when I use command ""msiexec.exe /i [path/to/file.msi /norestart /qn -msiparams ADDLOCAL=VBoxApplication,VBoxNetwork,VBoxPython"" (so I'm not installing USB feature) it works and installation can go on. 

This happen's only on machines which hadn't got VB earlier. Machines with older versions can be updated without any problem.    ",Fangier
18886,"Virtual screen 2 crashes after update to virtualbox 6.0.10, but only when running ubuntu",Linux,VirtualBox 6.0.10,2019-08-31T00:10:05Z,2019-08-31T16:08:46Z,2019-08-31T16:08:46Z,"I usually run ubuntu 18.04 in a virtual box on a Windows 10 host and use two virtual screens, i.e. virtual screen 1 and virtual screen 2. Today I updated my virtualbox to 6.0.10. When I restarted the virtual machine with ubuntu, virtual screen 1 and virtual screen 2 opens as usual, see screen shot here: https://imgur.com/a/owwjNnL

Furthermore, I can move the windows with virtual screen 1 and virtual screen 2 around. However, when I try to go to full screen or to resize the windows, screen 2 closes/crashes. It is then impossible to restart it by choosing view->virtual screen 2 -> enable. 

To see where the problem lies I also installed ubuntu 19.04 and windows 10 in virtual machines. With ubuntu 19.04 I still got the same problem. But with the windows 10 virtual machine everything worked, even if the graphics of window is flickering a couple of seconds before adapting to the new size. What can I do?
",haggle
18877,binary in shared folder loses executable permission while running,Linux,VirtualBox 6.0.10,2019-08-29T07:36:41Z,2019-08-29T07:36:41Z,2019-08-29T07:36:41Z,"After upgrading from virtualbox v5.0 to v6.0.10 I was not able to execute a binary from a shared folder (host Windows, guest Ubuntu) twice in parallel: while executing its permission would change from -rwxrwxrwx to -rw-rw-rw-.

I had mounted it via a line in /etc/fstab:
{{{
FolderName  /home/somewhere vboxsf rw,uid=1000,gid=1000,dmode=755  0  0
}}}

how to reproduce: with that mount:
{{{
cp /bin/cat /home/somewhere/cat2
ls -l /home/somewhere/cat2 # => permissions -rwxrwxrwx, owner me:me
/home/somewhere/cat2 &
ls -l /home/somewhere/cat2 # => permissions -rw-rw-rw-
/home/somewhere/cat2   # => 'permission denied'
}}}
After stopping the running executable the permissions return to -rwxrwxrwx again.

Mounting as an automount instead resolves the problem: cat2 has owner root:vboxsf, and permissions -rwxrwx--- - and that doesn't change while running.

",nijhof
18861,The virtual machine has terminated unexpectedly during startup,Windows,VirtualBox 6.0.10,2019-08-22T08:18:27Z,2019-08-22T09:13:58Z,2019-08-22T09:13:58Z,"Не удалось открыть сессию для виртуальной машины МЗНП_10.

The virtual machine 'МЗНП_10' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005).  More details may be available in 'C:\Users\bxz\VirtualBox VMs\МЗНП_10\Logs\VBoxHardening.log'.

Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

",bxz
18859,"Guest randomly crashes with ""The memory could not be read""",Linux,VirtualBox 6.0.10,2019-08-21T13:07:19Z,2019-08-21T19:15:03Z,2019-08-21T19:15:03Z,"I am running a Windows 10 1903 host and a Ubuntu 19.04 guest. The Ubuntu guest crashes fairly often with the attached dialog (see attached PNG file), warning of ""The memory could not be read.""

Both host and guest are using the latest patches. The guest has the current VMWare Extensions installed. The guest has 3D acceleration enabled.

Almost all of this guest OS's usage is for using Chromium browser to browse everyday sites, like Gmail, Facebook, CNN, etc. I feel it's fairly vanilla other than installing a few commodity apps like Chromium, GIMP, and Visual Studio Code.

The crash can happen when I am using nothing other than Chromium. In fact, just today, the crash happened less than 15 minutes after starting the VM. I attached log files from that crash.

Sometimes right-click context menus in Chromium go black. That is, you right-click on something, and the context menu that pops up is just a black rectangle. You can still click on things in that menu, but . I ''loosely'' correlate this to ""the VM is going to crash sooner than later"", but I am not sure there is a correlation. This morning, I did not notice the black context menus, although I do not think I invoked one.",Aren Cambre
18855,please add much better sound support for DOS VMs,other,VirtualBox 6.0.10,2019-08-20T01:30:09Z,2019-08-20T06:30:37Z,2019-08-20T06:30:37Z,"The current implementation you have is apparently DMA-based only and is based on an unknown model number of SoundBlaster 16, which I think is the only choice that has a chance of working in DOS (I don't know about ICH AC97).

Most use in DOS hinges on making use of an I/O address such as A220. That is what I'm hoping you can implement along with the address for MIDI support (i.e. P330). I do not know how you implement the interrupt and high/low DMA but seems like the I/O address has been the biggest issue stopping sound from working.

Also, how exactly is your sound virtualization implemented?  Is there a module that can be added to VirtualBox to accomplish this (something like an Extension Pack for DOS), or is there a module that can be added as a 'pre-boot' BIOS extension inside the DOS guest (similar to how OnTrack DDO used to work)?",Steve Sybesma
18796,Virtualbox 6.0.10 Lockup Issue,Windows,VirtualBox 6.0.10,2019-07-29T17:16:28Z,2019-08-19T12:18:49Z,2019-08-19T12:18:49Z,"I am creating this ticket because my companies Windows 7 64/32 bit virtual machines are randomly locking up.  This issue has been present since 6.0 was first released.  I have not been able to figure out how to recreate the issue so I have attached a 7-zip file that include the virtual machine html file along with the log files from a session that locked up and had to be aborted.

Please let me know if you need anything else from me to resolve this ticket.

Thank you
Chris

",cmccarron
18839,Guest VMs will only start headless,Linux,VirtualBox 6.0.10,2019-08-15T22:06:46Z,2019-08-18T21:17:40Z,2019-08-18T21:17:40Z,"After upgrading from VirtualBox5 to VirtualBox6 none of my existing VMs will start unless I choose the ""Headless Start"" option from the dropdown menu.

Once a VM is running I'm able to bring up the GUI by clicking on the ""Show"" button.",nthexwn
18837,VB Manager crash silently when maximizing window (Fixed in SVN),other,VirtualBox 6.0.10,2019-08-15T03:15:16Z,2019-08-18T19:50:44Z,2019-08-18T19:50:44Z,"host win10 10.0.17763 N/A Build 17763
VB 6.0.10 r132072 (Qt5.6.2)

* Open VM VB Manager, select VM
* Open VM logs
* Maximize window

List of VM widget become black and then process silently crash",gvaduha
18828,VirtualBox client crash when opening VBox shared folder,Windows,VirtualBox 6.0.10,2019-08-11T09:57:22Z,2019-08-17T09:28:11Z,2019-08-17T09:28:11Z,"Server-OS: Win-10
VirtualBox 6.0
Client-OS: WIN-7

WHen double-click/open a VBOX shared folder in the client, the client chrashes.
",LarsHes
18840,Guest VM with Windows 10 64 bit Pro 1903 is resetting with no reason,Windows,VirtualBox 6.0.10,2019-08-16T01:00:00Z,2019-08-17T08:29:31Z,2019-08-17T08:29:31Z,,fduenas
18833,Virtualbox doesn´t work with new Windows update,Windows,VirtualBox 6.0.10,2019-08-13T05:54:58Z,2019-08-17T06:26:54Z,2019-08-17T06:26:54Z,"I have updated my OS to the latest Windows 10 version, after that I can´t run open any virtual OS.

The virtual machine 'Pintura WinCC 7.3' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Usuario\VirtualBox VMs\Pintura WinCC 7.3\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976} ",erjefe
18787,Blue screen when try to launch WinSCP-5.15.3.,Windows,VirtualBox 6.0.10,2019-07-24T17:08:00Z,2019-08-17T04:52:53Z,2019-08-17T04:52:53Z,"Guest machine Windows 7 - Win 6.1 (Build 7601 SP 1)

Host machine Windows 10 Ver 1809 (OS Build 17763.615)

Virtual Box - VirtualBox Graphical User Interface, Version 6.0.10 r132072 (Qt5.6.2)

Guest machine fall with Blue screen when try to launch WinSCP-5.15.3. (WinSCP.exe)

Downloaded from here 
https://winscp.net/download/WinSCP-5.15.3-Portable.zip",dimabol
18813,Linux installation fails when machine folder points to non-OS directory | Win 8.1 x64,Linux,VirtualBox 6.0.10,2019-08-05T09:20:35Z,2019-08-17T02:55:43Z,2019-08-17T02:55:43Z,"Tried to install Ubuntu 16 x VM by selecting ""Machine Folder"" to a non-os directory. Installation always fails at Use entire disk and setup LVM.

ENV:
- Windows 8.1 x64 8GB RAM/500 GB HDD
- VM Conf: Memory: 1024 MB, create vhd now, VDI [dynamic alloc][10 GB]",cheruvattil
18830,Problem with Version 6.0.10 Guest Additions,Windows,VirtualBox 6.0.10,2019-08-11T17:23:49Z,2019-08-12T07:29:36Z,2019-08-12T07:29:36Z,"I'm running VirtualBox 5.2.32 with a Windows XP virtual machine. Everything works fine. However, when I installed 6.0.10, it reports ""Disk is full"" when a program tries to write to a file on a FAT16 (yes, FAT16) shared partition. This only happens if I install the 6.0.10 guest additions. If I stay with the 5.2.32 guest additions, it doesn't occur. (I don't know if it would occur with a FAT32 or NTFS partition, because the program only works with FAT16, which is why I have a FAT16 partition).",cdgoldin
18821,VirtualBox (VirtualVM.exe) crashes on Xubuntu 18.04 guest shutdown,Linux,VirtualBox 6.0.10,2019-08-08T11:18:44Z,2019-08-08T11:18:44Z,2019-08-08T11:18:44Z,"More often than not, my Xubuntu 18.04 guest OS does not shutdown cleanly. The host OS is running the latest version of Windows 10. A crash is raised in VirtualVM.exe. An example screenshot of the 'Application Error' is attached.

Attached are the following files:
* VBox Manager log
* Link (not actual attachment) to compressed, '''full''' crash dump (generated via Task Manager) - [https://drive.google.com/file/d/1CiOAs_8KejRZzMYjGd3UtA71kUOobv5a/view?usp=sharing Google Drive].
* Screenshot of application error raised by Windows. For the record, this screenshot does not (unfortunately) correspond to the attached crashdump.

I initially suspected the issue was related to Graphics acceleration, but I have disabled both 2d/3d but it has not changed the resulting behaviour.",zerodefect
18819,3D Acceleration not working in 6.0,Windows,VirtualBox 6.0.10,2019-08-08T01:05:53Z,2019-08-08T01:05:53Z,2019-08-08T01:05:53Z,"Reference forum post:
https://forums.virtualbox.org/viewtopic.php?f=2&t=94052

Seems there are at least three people voicing this complaint.

I was using VB 5.2.22 on Win7 host with Win10 guests for a long time. I set the guests to use 3D and 2D acceleration and never noticed an issue.

I rebuilt my host to Win10 v1709, same hardware including the NVIDIA Quadro GPU. I installed VB 6.0.10, created new VMs, and then quickly ran into the shared folder crash, so backed down to 6.0.8.

When I set the Win10 guest to use 2D and 3D (256MB), I have graphics issues. The most notable is that videos won't play in WMP or VLC (audio only, no image shown). There is also a lot of flickering and choppiness in the OS UI. If I toggle off 3D, then videos will play and other OS UI animations are smooth again.
",Justinh
18804,VirtualBox Manager terminating without notice after start,Linux,VirtualBox 6.0.10,2019-08-02T08:58:57Z,2019-08-02T08:58:57Z,2019-08-02T08:58:57Z,"When I start the VirtualBox Manager, it briefly shows the selector window, then terminates without any notice. I have a single Linux VM in the list.",sgiesecke
18794,"VM stopped scaling correctly ater update to 6.0.10 from 6,0,08",Linux,VirtualBox 6.0.10,2019-07-26T15:08:10Z,2019-07-26T17:57:20Z,2019-07-26T17:57:20Z,"Hi there 
I updated VMBox vom 6.0.8 to 6.0.10
this went well.- 
Then I started the Guest Cd 6.0.10 , after that the scaling of the desktop in the VM stoppend working. 
the size is set and is not changeable. 
I counter checked via a recent clone of the VM and there the scaling of the screen still works.-  
I am not sure what else I can give. please let me know.
cheers
   Me",Baros
18788,Für die virtuelle Maschine WindowsXP konnte keine neue Sitzung eröffnet werden.,Windows,VirtualBox 6.0.10,2019-07-24T20:42:56Z,2019-07-25T09:10:23Z,2019-07-25T09:10:23Z,"Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",burghard007
18782,Host machine crashes when booting guest for installation,all,VirtualBox 6.0.10,2019-07-23T11:55:51Z,2019-07-25T08:29:22Z,2019-07-25T08:29:22Z,"I posted a couple of threads seeking help for my issue, someone suggested I post a bug report.

https://superuser.com/questions/1462614/oracle-virtualbox-host-machine-crashes-when-booting-guest-for-installation

https://forums.virtualbox.org/viewtopic.php?f=6&t=93933&sid=4632274c1fd7c536357bd0c7c7877e99
",diamondpumpkin
18780,VirtualBox-6.0.10-132072-Win  BSOD,Windows,VirtualBox 6.0.10,2019-07-22T17:55:40Z,2019-07-25T05:16:39Z,2019-07-25T05:16:39Z,"Steps to reproduce:
-create or use an existing Windows7 VM
-download VNC viewer standalone
-run it inside the VM => BSOD

No BSOD with VirtualBox-5.2.30-130521",jcstaquet
18774,Virtual Box is causing random host reboots,all,VirtualBox 6.0.10,2019-07-19T13:01:56Z,2019-07-20T15:39:34Z,2019-07-20T15:39:34Z,"When I turn on three virtual machines windows 7, windows vista, windows 8.1 pro my computer just reboots after 10 minutes. When I only run Windows 8.1 pro I get a BSOD system service exception error. Also, in vmware that happens. Hyper-V on my computer was disabled and also Virtualization Based Security in Device Guard was disabled. Can anyone help me with this?",obedyaw
18772,USB flash drive selection / addition causing crash or on removal,Linux,VirtualBox 6.0.10,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,"Intermittent, but fails enough to be extremely troublesome.",xlar54
18763,CMPXCHG16B,Windows,VirtualBox 6.0.10,2019-07-17T03:48:17Z,2019-07-18T11:29:54Z,2019-07-18T11:29:54Z,"Just upgraded from v5.32 to v6 here, but get this error on about half of the VM's I am trying to upgrade.  I didnt see where a user can change this, please help!
Occurs when I try to launch the VM's.
Thank you.

Duplicate config values '/CPUM/CMPXCHG16B' and '/CPUM/IsaExts/CMPXCHG16B' - please remove the former! (VERR_DUPLICATE).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",LindaCarter
18765,ICH AC97 don't work on Wondows ME,Windows,VirtualBox 6.0.10,2019-07-17T16:17:13Z,2019-07-17T16:17:13Z,2019-07-17T16:17:13Z,"When I've updated to VirtualBox 6.0.0, audio in Windows ME became buggy or don't working.",WinWins
18985,Appdata folder contents copied to host drives when dragging and dropping files from kali linux vm,Linux,VirtualBox 6.0.12,2019-10-05T21:58:29Z,2020-08-11T11:45:33Z,2020-08-11T11:45:33Z,"I have attached a video of the bug or whatsoever and managed to reproduce it like 3 times and as its mentioned in the summary it happened when i tried to drag and drop from vm to host, and after the copying started after calculating the files(110 GB the second time I tried), i cancelled copying and some files from appdata folder and the screenshots i wanted were copied to the host drive. thank you.",hasa
18969,VirtualBox manager sometimes crashes on start,other,VirtualBox 6.0.12,2019-09-26T17:26:18Z,2020-06-25T16:29:55Z,2020-06-25T16:29:55Z,"I can't determine repeatable conditions, but sometimes VirtualBox.exe crashes on start. It's a normal install of the latest release (6.0.12) on Windows 10 x64 1903.
It always crashes in Qt5GuiVBox.dll, but the exception differs, sometimes it's 0xc0000005, sometimes it's 0xc000041d. Offset is always 0x00000000001e384e.

I'm not using VB that often nowadays, but I haven't seen any crashes when running VMs yet, only on start of the manager GUI.",pupertest
18953,guest additions fail to install,Windows,VirtualBox 6.0.12,2019-09-22T10:04:43Z,2020-03-31T11:59:06Z,2020-03-31T11:59:06Z,"fails to install see log

https://pastebin.com/sw74ba1C",DeGarden
18966,[VBoxSVGA with WDDM] Graphics corruption,Linux,VirtualBox 6.0.12,2019-09-26T06:51:59Z,2020-02-12T12:55:08Z,2020-02-12T12:55:08Z,"Corrupt display of various elements in GUI / dialog boxes when using VBoxSVGA and Aero in Windows 7 guest on Linux host.

No problem using VBoxVGA / WDDM.",Thomas S.
18943,High DPI support,Linux,VirtualBox 6.0.12,2019-09-18T14:13:53Z,2020-01-23T22:17:10Z,2020-01-23T22:17:10Z,"High DPI support has always been a little wonky, but after upgrading to 6.0, it has gotten worse.

I use my high DPI laptop with a normal external monitor.  My laptop is set to 250% zoom and the external monitor is set to 100% zoom.  When I start Virtualbox Manager with this set up, it looks okay for my laptop, but if I drag it to the external monitor, everything is too small.  If I set my laptop to 100% zoom, start Virtualbox Manager, and then change the zoom back to 250%, it looks great on my external monitor, but everything is too big on my laptop.",morriw
18954,VBoxSVGA x64 Vista guest 3D accelerated video broken in VirtualBox 6.0.12,Windows,VirtualBox 6.0.12,2019-09-23T06:17:07Z,2019-11-20T14:04:41Z,2019-11-20T14:04:41Z,"On a x64 Windows Vista guest, after the installation of VirtualBox 6.0.12, I followed the recommendation to switch to the VBoxSVGA graphics controller in the context of the upcoming deprecation of VBoxVGA. As part of switching to VBoxSVGA I installed the 6.0.12 guest additions with 3D acceleration enabled. 

Following the restart of the guest (eventually multiple times), I consistently get display behavior that effectively makes the VM unusable. What seems to happen is that whatever section of the screen (like an icon, desktop gadget, title bar and occasionally the entire desktop) was updated last is displayed in full screen within the guest.

I will attach a number of screenshots displaying this behavior as I moved my mouse pointer over the guest's screen. Do note that some of those screenshots, being the ones showing the VirtualBox window decorations, were taken in the (Windows 10) host, and some within the guest itself. As you can see, the results are consistent independent of the source of the screenshot.",Rutger van Bergen
19038,"Windows 10 VirtualBox uninstallation required for 6.0.12, or application within VM crashes.",Windows,VirtualBox 6.0.12,2019-10-22T17:14:21Z,2019-10-22T17:14:21Z,2019-10-22T17:14:21Z,"Submitted for third-party in order to document rare issue encountered by a third party.

Third-party virtualizes a physical classroom disk image with VirtualBox for portability, deployment, and testing, and has done so for years.

A recent upgrade from 6.0.10 to 6.0.12 caused a commercial application within the VM to crash when accessing HTML files. We determined that UNINSTALLING 6.0.10 and then conducting a fresh installation of 6.0.12 solved this application crash, so something is not being uninstalled properly during the upgrade process.

I apologize for the lack of log files. Third party encountered this bug on a production machine and deadlines prevented retrieval of additional troubleshooting assistance. 6.0.12 was already uninstalled and 6.0.14 freshly installed, without issue.",.
19011,Right screen buttons etc,other,VirtualBox 6.0.12,2019-10-13T17:55:23Z,2019-10-21T06:09:10Z,2019-10-21T06:09:10Z,"Win 10 pro / Chrome / 
Right side - menu ellipses, x out and minimize/maximize, more than 5 tabs -cease working.
VB reinstall was a temporary fix
",Amadeo
19026,Windows sleep breaks network hotplugging,Linux,VirtualBox 6.0.12,2019-10-18T06:31:03Z,2019-10-19T00:50:00Z,2019-10-19T00:50:00Z,"I have a windows 10 host system with archlinux as guest. Both operate using virtualbox 6.0.12.

In virtualbox, I have set up two network interfaces
1. Bridge 
2. Host only adapter


The network bridge usually operates either on a USB-C docking station or the laptops own network interface depending on where I am working.
So far, changing the bridges' interface (docking station vs built-in) seems to work fine. However, if I meanwhile put the windows asleep, e.g., through closing its lid it seems to break.

Here is what I mean with break:
The bridge network (when connected to either the docking station or the built-in adapter) obtains an IP from a DHCP which offers IPs in range 172.28.0.0/16.
If the above mentioned problem occurs (putting windows asleep and changing the bridge's interface e.g. from docking station to built-in or the other way around). The linux interface is not able to obtain an IP (it seems to default to an IP starting with 169.xxxx) and also restarting the dhcp client does not change this. The only thing that seems to work is to shutdown and start the VM again.",bomvir
19013,VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2),Linux,VirtualBox 6.0.12,2019-10-13T21:50:45Z,2019-10-16T03:40:36Z,2019-10-16T03:40:36Z,"I am using VirtualBox Graphical User Interface Version 6.0.12 r133076 (Qt5.6.2)  installed on windows 10 64 bit and my host oracle linux 6.6 x86_64.
here problem is view ( resizing windows is not working in full screen).

kindly ! provide me solution ",gaurav12
19012,VERR_CFGM_VALUE_NOT_FOUND on boot.,other,VirtualBox 6.0.12,2019-10-13T20:03:29Z,2019-10-16T03:34:08Z,2019-10-16T03:34:08Z,"Using VirtualBox version 6.1.0_BETA1 r133315. VM crashed on guest shutdown and now won't boot, throws ""Failed to construct 'efi'/0! VERR_CFGM_VALUE_NOT_FOUND (-2103) - Value not found."" on boot.

Logs: https://pastebin.com/sBQjAhfY

vbox: https://pastebin.com/HLNQWz4S",DeezNutz
18968,Installing Guest Additions on Windows does not check for admin rights,all,VirtualBox 6.0.12,2019-09-26T14:01:09Z,2019-10-07T08:30:14Z,2019-10-07T08:30:14Z,"Host is Windows 10, 64-bit, all latest updates.  As good practise in our corporate environment, our accounts do not have admin rights.  All PCs have the same admin account set up, to which we all know the password, so if we need to install something then we can - but it stops viruses (and incompetence!) from doing major damage.

I've just upgraded VirtualBox from 6.0.10 to 6.0.12.  As expected, running the installer asked me for my admin password, which I entered, and 6.0.12 was installed correctly.  At the time, it also asked me if I wanted to upgrade Guest Additions.  I'd already downloaded the 6.0.12 ""vbox-extpack"" file, so I said no.

When VirtualBox started back up, I went to ""Preferences"" and tried adding the new 6.0.12 Guest Additions.  It failed on installation with just the error message ""E_FAILED"".  Upgrading via the ""Check updates"" option also failed the same way, and so did attempting to remove the 6.0.10 Guest Additions.  Rebooting the PC didn't help.

Looking in the log file, I found the following line:

> 00:11:43.122154 ExtPackUninst ExtPack: enmReason=1 iStatus=1 stderr='VBoxExtPackHelperApp.exe: error: Membership in the Administrators group is required to perform this action

Then I realised.  I ran VirtualBox using ""Run as administrator"", and this time installing the 6.0.12 Guest Additions worked perfectly.

So VirtualBox internally *IS* aware why installation failed - but the UI is not reporting this to the user.  Even if it just passed through that text unchanged, it would still be more meaningful than ""E_FAILED""!

I'm listing this as a defect, because the program is not working to reasonable user expectations for a reasonable user action.  I'm savvy enough to try to interpret a log file, and I know where to find the log file, but most users don't.",GBartlettPrior
18984,failure to install tools,Windows,VirtualBox 6.0.12,2019-10-05T05:55:54Z,2019-10-05T16:00:05Z,2019-10-05T16:00:05Z,windows 10 host and guest. see screenshot.,DeGarden
18973,BSOD (crash) on Windows 10 host with console Linux guest in network driver,Linux,VirtualBox 6.0.12,2019-09-29T08:18:40Z,2019-10-03T18:04:12Z,2019-10-03T18:04:12Z,"Bug previously opened as #18854 (BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver) is still exist in VirtualBox 6.0.12.
It is releated to active network I/O operations on Windows 10 x64 host with Linix guests (CentOS 7 or Debian 10 x64, for example).
I have reproduce it again when I have created and installed Debian 10 guest and have executed the command
cd /opt && mkdir -p ttt && wget -O - --user UserName --password Password ftp://192.168.0.28/full_backup_29.09.2019 | restore -x -a -T /opt/ttt -f /dev/stdin
where:
192.168.0.28 is IP address of Windows 10 host
192.168.0.91 is IP address of Debian 10 guest
192.168.0.0/24 is a 1 Gbps network on ""Intel(R) Ethernet Connection (2) I219-V"" NIC adapter.",MaaSoftware
18976,"""screen record"" doesn't work well on Windows 7 virtual machine",Windows,VirtualBox 6.0.12,2019-10-02T11:56:15Z,2019-10-02T11:56:15Z,2019-10-02T11:56:15Z,"I used ""screen record"" to record the screen of my Windows 7 virtual machine. Everything seems not bad till I stopped the recording by clicking the ""stop"" button on the toolbar. After stooped, all keyboard input seems to be masked(but the mouse is OK). It return to be OK after I quit the ""fullscreen"" mode.I think it might be a BUG.

(I've already installed the guest additions.)",Danyang
18958,virtualbox 6.0.12 update doesn´t allow Fedora 30 VM start,Linux,VirtualBox 6.0.12,2019-09-23T12:52:01Z,2019-09-25T04:49:39Z,2019-09-25T04:49:39Z,"Vm perfectly running on windows with version from 5.x to ""6.0.10 r132072 (Qt5.6.2)"" after 6.0.12 update was not able to start the vm. On configuration were displayed some problems about ""unsupported hardware acceleration"".

A fast roll-back to previous 6.0.10 fixed the proble,m, but seems that 6.10.12 have some problem.
 
Test environment: Windows 10 pro, notebook fujitsu lifebook i7-8650U, 32Gb ram, sss, lan",Piero Gerletti
18947,usb audio is extremely choppy,other,VirtualBox 6.0.12,2019-09-19T18:21:53Z,2019-09-24T06:09:08Z,2019-09-24T06:09:08Z,"Guest: OS/2

In principle, usb audio does work under OS/2 but the sound is extremely choppy. I am using a USB 1.x sound device (compatible with usb audio standard 1.0). With older versions of VirtualBox, this problem did not exist but the guest was more unstable (guest crashed).",lerdmann
18946,Screenshot is causing the disk size update to fail,Linux,VirtualBox 6.0.12,2019-09-19T15:08:23Z,2019-09-23T15:49:09Z,2019-09-23T15:49:09Z,"Hi, 
I am running a host PC Windows 10. Using the virtualbox to launch a Cent OS. 
I was trying to update my disk size on the CentOS as i had reached 100% utilisation. So i used (as recommended by many sites to update this) below command:
{https://stackoverflow.com/questions/8141045/virtualbox-extend-partition
/mnt/c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe modifymedium CentOSVD.vdi --resize 120000}

Idea was to increase the vdi size from 60Gb to 120Gb. 
But after this command, it was not directly reflecting in the Cent OS after restart (also windows restart). The increased volume succeeded on windows side without any errors. But CentOS was not showing this. 
After a lot of debug i found that i had a snapshot stored somewhere on the PC and this was preventing the additional disk to be shown on the CentOS.  {lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 68.3G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part 
}
The sda partition was always showing 68.3G. Even though i increased the VDI to 120G, it was not reflecting here. Then i deleted the snapshot and then i saw the correct results. 
{ lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda               8:0    0 117.2G  0 disk 
├─sda1            8:1    0     1G  0 part /boot
└─sda2            8:2    0 63.2G  0 part }
So somehow the process in the snapshot is preventing the process of disk space update. Please check.
Steps to reproduce:
1. Run Virtual Box on a windows 10 machine. 
2. Install the Cent OS running as guest OS on Virtual Box. 
3. Check the VDI disk size (Virtual and actual size)
4. Take a snapshot (Ctrl + Shift + T). Notice another VDI file is created in another location
5. Increase VDI disk size with above command (VBoxManage.exe modifymedium)
6. Reboot both windows and VBox. 
7. Check the disk space on guest OS (CentOS) it will not show the increase
8. Delete Snapshot. Newly created VDI file is deleted from Step 4.
9. Reboot both windows and VBox. 
10. Check the disk space on guest OS (CentOS) it will show the increase",aanche
18950,clipboard stops working,Linux,VirtualBox 6.0.12,2019-09-20T07:07:09Z,2019-09-20T07:07:09Z,2019-09-20T07:07:09Z,"As long as I've used VirtualBox this issue has occurred.  It's the same as described in bug #5266.  

> After a period of time the shared clipboard will stop working either in
> one direction or the other and sometime in both directions. A reboot of 
> the guest will bring it back. Logfile included.

Awhile back I found out that I can do this to rectify it sometimes...

killall -9 VBoxClient && /usr/bin/VBoxClient --clipboard && /usr/bin/VBoxClient --display && /usr/bin/VBoxClient --seamless && /usr/bin/VBoxClient --draganddrop

I'm hoping with the extra information regarding killing of the VBoxClient, that it will lead to a fix.  This has been happening for many years, I think more than 10.",Trent
18932,No DNS from DHCP on NAT connection,all,VirtualBox 6.0.12,2019-09-16T13:48:19Z,2019-09-17T00:05:17Z,2019-09-17T00:05:17Z,"On VirtualBox 6.0.12, with plain NAT configuration, the domain name resolution does not work anymore on Windows/Linux guests on Windows host.

I've checked quite everything on host and guests configuration and come up to the hypothesis that VirtualBox dhcp ""server"" does not send the DNS address, but it used to do on previous versions.

This is confirmed by DHCP not containing the DNS entry as shown by the following DHCP response:


{{{
$ sudo nmap --script broadcast-dhcp-discover

Starting Nmap 7.60 at 2019-09-12 08:08 CEST
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 10.0.2.16
|     DHCP Message Type: DHCPOFFER
|     Subnet Mask: 255.255.255.0
|     Router: 10.0.2.2
|     IP Address Lease Time: 1d00h00m00s
|_    Server Identifier: 10.0.2.2
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.51 seconds
}}}
",Han Fastolfe
18919,Cursor doesn't capture,Windows,VirtualBox 6.0.12,2019-09-09T22:07:48Z,2019-09-12T13:14:40Z,2019-09-12T13:14:40Z,"Hello, I have a problem. The cursor doesn't capture on my Windows 98 guest. I hope there's a solution. It happens, surprise, on the !VirtualBox last version and Windows 98 SE.",SamiVirtualBox
18921,Received critical error on new VM,Windows,VirtualBox 6.0.12,2019-09-10T13:15:57Z,2019-09-10T13:15:57Z,2019-09-10T13:15:57Z,Log files attached,broberts160
18907,Guest display will not size correctly,Windows,VirtualBox 6.0.12,2019-09-04T19:33:39Z,2019-09-04T19:33:39Z,2019-09-04T19:33:39Z,"Guest Additions icon does not appear on taskbar
Guest Additions Service is running normally
Seamless Mode and Auto-resize Guest Display are both greyed out

VirtualBox 6.0
Version 6.0.12 r133076 (Qt5.6.2)

Guest Additions Installed
Version 6.0.12.0

Host
Win10 Pro
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Host Graphics
Intel UHD Graphics 620
Driver Version 23.20.16.4849

Guest
Win10 Pro 64
Version 1809
OS Build 17763.615
System Type: 64 bit operating system, x64 based processor

Guest Graphics
VirtualBox Graphics Adapter (WDDM)
Driver Version 6.0.12.0
",JTC
18925,"Virtualbox freeze all guest system (32, 64 bit, linux, windows, other)",all,VirtualBox 6.0.12,2019-09-12T13:06:01Z,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"The Virtualbox freeze after running guest operating system.
",agostonl119
19131,linux guest os does not recover from host sleep - Win 10 host,Linux,VirtualBox 6.0.14,2019-12-04T18:18:27Z,2022-09-15T08:26:09Z,2022-09-15T08:26:09Z,"Since 6.x, Ubuntu 18.04 guest does not recover from host (Win 10) going to sleep for around 30 min. 

If I send the host OS to sleep and immediately (within 5 min), everything is fine.

After a longer sleep, say 20 min, I get varying results:

1) the guest OS seems to have rebooted and I arrive at the login window.  My prior running apps and consoles are gone from the desktop.

2) the OS hangs, showing the login screen.  Mouse and keyboard are not working.  Software reboot (send a shutdown signal) does not work.  Must reboot the guest os. 


My computer is recovering from sleep mode and not hibernate mode.

This seems to have started since 16.x.  I created the guest OS in 15.x.
",eyn
19086,rm / rmdir  not working correctly in shared folders,Linux,VirtualBox 6.0.14,2019-11-14T07:22:32Z,2021-04-15T22:30:27Z,2021-04-15T22:30:27Z,"As it seems that comments to existing tickets are not enough, I make a ticket out of my comment to #18569.

Since the beginning of VirtualBox v6.x the ""rm -r"" command is not working correctly in shared folder within a Linux guest.

I attach a screen shot of an example what happens.

Host: Windows 10 1903
Guest: CentOS 6.6, kernel 2.6.32-504.el6.x86_64",Reiner Brodbeck
19030,guest window position not restored,all,VirtualBox 6.0.14,2019-10-19T09:58:55Z,2020-10-25T12:01:33Z,2020-10-25T12:01:33Z,"The guest window positions (guest with more than one monitor) are not restored.
In 5.0.40 it works well. In 5.1.Y it started not to work.

See also here: https://forums.virtualbox.org/viewtopic.php?f=6&t=95117",artelogic
19034,Drag drop from guest to host leads to full AppData drop,Windows,VirtualBox 6.0.14,2019-10-21T09:19:07Z,2020-08-11T11:46:00Z,2020-08-11T11:46:00Z,"Hi,

As said in title I'm facing a verry strange file drag/drop from VM to host.

Wherever I drag from (in term of folder), if the file is named ""006_remplissage_pieces_test_pause"" and whatever is the extension Virtualbox '''try to drop all the AppData folder content to my host.'''

Exactly the same if the file is named ""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" plus ANY extension.
Even in ""small path length"" conditions.
The same with 1 character removed. Works with 2 removed...

The same with 1, 2 or 3 characters added.

The ""uge drop file name length"" seems to be from 32 to 35 char, without ""."" and extension.

{{{

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   - 36 char / OK
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx    - 35 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx     - 34 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx      - 33 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx       - 32 char / KO
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx        - 31 char / OK
}}}


Host is Windows 7x64, latest updates[[BR]]
Guest is Windows 7x64, latest updates[[BR]]
Virtual box is 6.0.14 r133895[[BR]]
Guest additions are up to date (6.0.14).
",wkoenig_ngbe
19155,When shutting down guest. rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003b2c,Linux,VirtualBox 6.0.14,2019-12-13T12:39:25Z,2020-02-19T22:29:25Z,2020-02-19T22:29:25Z,"From Log file.

17:44:49.275875 
17:44:49.275877 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003b2c!!!
17:44:49.275893 
17:44:49.275894 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffcc8078561
17:44:49.275899 ExceptionInformation[0]=0000000000000001
17:44:49.275904 ExceptionInformation[1]=0000000000000021
17:44:49.275908 
17:44:49.275908 cs:rip=0033:00007ffcc8078561
17:44:49.275913 ss:rsp=002b:00000000099ef490 rbp=000000000c6e3cb0
17:44:49.275918 rax=0000000000000000 rcx=e8906b5e61f10000 rdx=0000000000000000 rbx=00000000087dc1e8
17:44:49.275923 rsi=0000000000000001 rdi=0000000000000021 rsp=00000000099ef490 rbp=000000000c6e3cb0
17:44:49.275927 r8 =00000000099ef148 r9 =000000000c6e3cb0 r10=0000000000000000 r11=00000000099ef420
17:44:49.275932 r12=0000000000000002 r13=000000000665cb40 r14=0000000000000000 r15=00000000fffffb83
17:44:49.275936 ds=002b es=002b fs=0053 gs=002b eflags=00010206
17:44:49.275941 p1home=00000000043b8c10 p2home=00000000043b8c10 pe3home=00000000087dc1e8
17:44:49.275945 p4home=00000000043b8c10 p5home=00000000099ef348 pe6home=0000000000000000
17:44:49.275949    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
17:44:49.275954 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
17:44:49.275961 
17:44:49.275962 Stack 00000000099ee370, dumping 0x1c90 bytes (low=00000000098f0000, high=00000000099f0000)
17:44:49.275970 00000000099ee370 0000: 70 e3 9e 09 00 00 00 00-73 74 61 63 6b 6d 61 72 p.......stackmar
17:44:49.275977 00000000099ee380 0010: 6b 65 72 00 fc 7f 00 00-80 00 00 00 00 00 00 01 ker.............
17:44:49.275979 00000000099ee390 0020: 00 20 5e 00 00 00 00 00-01 00 00 00 00 00 00 00 . ^.............
17:44:49.275980 00000000099ee3a0 0030: 80 eb 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.275981 00000000099ee3b0 0040: f0 f1 9e 09 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.275982 00000000099ee3c0 0050: 60 e5 9e 09 00 00 00 00-f0 f9 9e 09 00 00 00 00 `...............
17:44:49.275984 00000000099ee3d0 0060: 00 7f 89 80 fc 7f 00 00-6c 6c d5 f6 fc 7f 00 00 ........ll......
17:44:49.275985 00000000099ee3e0 0070: 60 e5 9e 09 00 00 00 00-61 85 07 c8 fc 7f 00 00 `.......a.......
17:44:49.275986 00000000099ee3f0 0080: 00 00 9f 09 00 00 00 00-00 00 8f 09 00 00 00 00 ................
17:44:49.275988 00000000099ee400 0090: 40 00 00 00 00 00 00 00-03 00 00 00 fc 7f 00 00 @...............
17:44:49.275989 00000000099ee410 00a0: 06 00 00 00 04 00 00 00-08 00 00 00 01 00 00 00 ................
17:44:49.275990 00000000099ee420 00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.275991 00000000099ee430 00c0: 00 00 00 00 00 00 00 00-bd b4 f9 f9 fc 7f 00 00 ................
17:44:49.275992 00000000099ee440 00d0: 60 e5 9e 09 00 00 00 00-80 98 f9 f9 fc 7f 00 00 `...............
17:44:49.275994 00000000099ee450 00e0: 00 00 00 00 00 00 00 00-80 e5 9e 09 00 00 00 00 ................
17:44:49.275995 00000000099ee460 00f0: 00 00 00 00 00 00 00 00-b0 e6 9e 09 00 00 00 00 ................
17:44:49.275996 00000000099ee470 0100: 00 00 00 00 00 00 00 00-bd b4 f9 f9 fc 7f 00 00 ................
17:44:49.275998 00000000099ee480 0110: fc 8c 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.275999 00000000099ee490 0120: 00 00 00 00 28 a0 00 00-da 20 77 55 00 00 00 00 ....(.... wU....
17:44:49.276000 00000000099ee4a0 0130: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276001 00000000099ee4b0 0140: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276003 00000000099ee4c0 0150: 11 82 c0 62 90 e8 00 00-7e 1d 7c 55 00 00 00 00 ...b....~.|U....
17:44:49.276004 00000000099ee4d0 0160: 00 00 f4 f9 fc 7f 00 00-f0 f9 9e 09 00 00 00 00 ................
17:44:49.276005 00000000099ee4e0 0170: f0 f1 9e 09 00 00 00 00-cb 81 fe f9 fc 7f 00 00 ................
17:44:49.276007 00000000099ee4f0 0180: 54 fc 7e 55 00 00 00 00-d4 33 08 fa fc 7f 00 00 T.~U.....3......
17:44:49.276008 00000000099ee500 0190: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276009 00000000099ee510 01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276010 00000000099ee520 01b0: 71 a2 06 00 00 00 00 00-56 fd fc f9 fc 7f 00 00 q.......V.......
17:44:49.276012 00000000099ee530 01c0: 30 00 00 00 00 00 00 00-00 00 00 00 06 00 00 00 0...............
17:44:49.276013 00000000099ee540 01d0: f0 f1 9e 09 00 00 00 00-28 eb 9e 09 00 00 00 00 ........(.......
17:44:49.276014 00000000099ee550 01e0: 10 e6 9e 09 00 00 00 00-74 79 6b f9 fc 7f 00 00 ........tyk.....
17:44:49.276015 00000000099ee560 01f0: f0 f1 9e 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276017 00000000099ee570 0200: f0 f1 9e 09 00 00 00 00-f0 f9 9e 09 00 00 00 00 ................
17:44:49.276018 00000000099ee580 0210: 10 e6 9e 09 00 00 00 00-71 a2 fa f9 fc 7f 00 00 ........q.......
17:44:49.276019 00000000099ee590 0220: 00 00 f4 f9 fc 7f 00 00-7f 47 fe f9 fc 7f 00 00 .........G......
17:44:49.276020 00000000099ee5a0 0230: 00 00 00 00 00 00 00 00-10 eb 9e 09 00 00 00 00 ................
17:44:49.276022 00000000099ee5b0 0240: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276023 00000000099ee5c0 0250: 80 eb 9e 09 00 00 00 00-ef 4b f4 f9 fc 7f 00 00 .........K......
17:44:49.276024 00000000099ee5d0 0260: 10 eb 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276025 00000000099ee5e0 0270: 3c bc 74 f9 fc 7f 00 00-00 00 6a f9 fc 7f 00 00 <.t.......j.....
17:44:49.276027 00000000099ee5f0 0280: 00 00 00 00 28 a0 00 00-40 e8 9e 09 00 00 00 00 ....(...@.......
17:44:49.276028 00000000099ee600 0290: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276029 00000000099ee610 02a0: c0 e7 3f 03 00 00 00 00-00 00 00 00 00 00 00 00 ..?.............
17:44:49.276030 00000000099ee620 02b0: de de de de ab ab ab ab-04 00 00 00 00 00 00 00 ................
17:44:49.276031 00000000099ee630 02c0: 07 00 01 11 04 02 01 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.276033 00000000099ee640 02d0: 0f 00 10 00 a0 1f 00 00-33 00 20 12 e3 12 82 48 ........3. ....H
17:44:49.276034 00000000099ee650 02e0: 30 51 2b 00 06 02 01 00-bd b4 f9 f9 fc 7f 00 00 0Q+.............
17:44:49.276035 00000000099ee660 02f0: 40 e8 9e 09 00 00 00 00-00 00 4e 04 00 00 00 00 @.........N.....
17:44:49.276037 00000000099ee670 0300: 00 00 64 03 00 00 00 00-00 00 00 00 00 00 00 00 ..d.............
17:44:49.276038 00000000099ee680 0310: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276039 00000000099ee690 0320: 00 00 00 00 00 00 00 00-00 00 40 01 00 00 00 00 ..........@.....
17:44:49.276040 00000000099ee6a0 0330: 00 00 00 00 00 00 00 00-70 fa 9e 09 00 00 00 00 ........p.......
17:44:49.276041 00000000099ee6b0 0340: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276043 00000000099ee6c0 0350: 00 00 00 00 00 00 00 00-80 49 40 01 00 00 00 00 .........I@.....
17:44:49.276044 00000000099ee6d0 0360: 50 0d 40 01 00 00 00 00-04 00 00 00 00 00 00 00 P.@.............
17:44:49.276045 00000000099ee6e0 0370: 30 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0...............
17:44:49.276046 00000000099ee6f0 0380: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276048 00000000099ee700 0390: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276049 00000000099ee710 03a0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276050 00000000099ee720 03b0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
17:44:49.276051 00000000099ee730 03c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276053 **************** ****  <ditto x 7>
17:44:49.276053 00000000099ee7b0 0440: 00 00 00 00 00 00 00 00-00 ea 9e 09 00 00 00 00 ................
17:44:49.276054 00000000099ee7c0 0450: 00 00 00 00 00 00 00 00-00 00 40 01 00 00 00 00 ..........@.....
17:44:49.276056 00000000099ee7d0 0460: 50 0d 40 01 00 00 00 00-04 00 00 00 00 00 00 00 P.@.............
17:44:49.276057 00000000099ee7e0 0470: 00 00 00 00 00 00 00 00-30 ea 9e 09 00 00 00 00 ........0.......
17:44:49.276058 00000000099ee7f0 0480: 00 00 00 00 00 00 00 00-80 49 40 01 00 00 00 00 .........I@.....
17:44:49.276059 00000000099ee800 0490: 50 0d 40 01 00 00 00 00-0a 00 00 00 73 1f c5 4c P.@.........s..L
17:44:49.276061 00000000099ee810 04a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276062 **************** ****  <ditto x 9>
17:44:49.276062 00000000099ee8b0 0540: a6 13 b1 d6 d7 c6 8d 3e-00 eb 00 00 06 00 00 00 .......>........
17:44:49.276064 00000000099ee8c0 0550: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276065 00000000099ee8d0 0560: 00 00 00 00 28 a0 00 00-20 eb 9e 09 00 00 00 00 ....(... .......
17:44:49.276066 00000000099ee8e0 0570: 00 00 00 00 00 00 00 00-30 eb 9e 09 00 00 00 00 ........0.......
17:44:49.276067 00000000099ee8f0 0580: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276068 00000000099ee900 0590: 00 00 00 00 28 a0 00 00-50 eb 9e 09 00 00 00 00 ....(...P.......
17:44:49.276070 00000000099ee910 05a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276071 00000000099ee920 05b0: c0 e7 3f 03 00 00 00 00-00 00 00 00 00 00 00 00 ..?.............
17:44:49.276072 00000000099ee930 05c0: de de de de ab ab ab ab-04 00 00 00 00 00 00 00 ................
17:44:49.276073 00000000099ee940 05d0: 07 00 01 11 04 02 01 00-00 00 00 00 00 00 00 40 ...............@
17:44:49.276075 00000000099ee950 05e0: 61 ea 9e 09 00 00 00 00-a8 44 6c 27 cd ba 06 49 a........Dl'...I
17:44:49.276076 00000000099ee960 05f0: a6 13 b1 d6 d7 c6 8d 3e-00 00 00 00 02 00 00 00 .......>........
17:44:49.276077 00000000099ee970 0600: 50 eb 9e 09 00 00 00 00-00 00 4e 04 00 00 00 00 P.........N.....
17:44:49.276078 00000000099ee980 0610: 00 00 64 03 00 00 00 00-00 00 00 00 00 00 00 00 ..d.............
17:44:49.276079 00000000099ee990 0620: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276081 00000000099ee9a0 0630: 30 ea 9e 09 00 00 00 00-0c 00 00 00 00 00 00 00 0...............
17:44:49.276082 00000000099ee9b0 0640: 00 00 00 00 00 00 00 00-39 94 ec f8 fc 7f 00 00 ........9.......
17:44:49.276083 00000000099ee9c0 0650: 00 00 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276084 00000000099ee9d0 0660: 00 00 00 00 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276085 00000000099ee9e0 0670: 06 00 00 00 00 00 00 00-30 ea 9e 09 00 00 00 00 ........0.......
17:44:49.276087 00000000099ee9f0 0680: 2c 80 43 da 28 a0 00 00-6b 97 ec f8 fc 7f 00 00 ,.C.(...k.......
17:44:49.276088 00000000099eea00 0690: 00 00 00 00 00 00 00 00-f0 ee 9e 09 00 00 00 00 ................
17:44:49.276089 00000000099eea10 06a0: f0 ee 9e 09 00 00 00 00-30 ed 9e 09 00 00 00 00 ........0.......
17:44:49.276090 00000000099eea20 06b0: 1c 80 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.276092 00000000099eea30 06c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276093 00000000099eea40 06d0: 48 f3 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276094 00000000099eea50 06e0: de de de de ab ab ab ab-30 ed 9e 09 00 00 00 00 ........0.......
17:44:49.276095 00000000099eea60 06f0: 02 00 00 00 fc 7f 00 00-00 30 cf 00 00 00 00 00 .........0......
17:44:49.276097 00000000099eea70 0700: d0 ef 9e 09 00 00 00 00-b9 b3 f9 f9 fc 7f 00 00 ................
17:44:49.276098 00000000099eea80 0710: e0 ea 9e 09 00 00 00 00-f0 f1 9e 09 00 00 00 00 ................
17:44:49.276099 00000000099eea90 0720: 00 ed 9e 09 00 00 00 00-40 cb 65 06 00 00 00 00 ........@.e.....
17:44:49.276100 00000000099eeaa0 0730: 02 00 00 00 00 00 00 00-21 00 00 00 00 00 00 00 ........!.......
17:44:49.276102 00000000099eeab0 0740: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276103 00000000099eeac0 0750: 00 00 00 00 00 00 00 00-d9 48 f4 f9 fc 7f 00 00 .........H......
17:44:49.276104 00000000099eead0 0760: f0 f1 9e 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276105 00000000099eeae0 0770: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
17:44:49.276107 00000000099eeaf0 0780: 19 00 00 00 00 00 00 00-fc 46 e7 f8 fc 7f 00 00 .........F......
17:44:49.276108 00000000099eeb00 0790: 02 00 00 00 00 00 00 00-50 eb 9e 09 00 00 00 00 ........P.......
17:44:49.276109 00000000099eeb10 07a0: 00 00 3b 04 00 00 00 00-64 d5 0a fa fc 7f 00 00 ..;.....d.......
17:44:49.276110 00000000099eeb20 07b0: 00 00 00 00 00 00 00 00-00 00 f4 f9 fc 7f 00 00 ................
17:44:49.276112 00000000099eeb30 07c0: f0 f1 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276113 00000000099eeb40 07d0: d4 33 08 fa fc 7f 00 00-f0 f9 9e 09 00 00 00 00 .3..............
17:44:49.276114 00000000099eeb50 07e0: 00 00 00 00 00 00 00 00-d0 eb 9e 09 00 00 00 00 ................
17:44:49.276115 00000000099eeb60 07f0: 71 a2 fa f9 fc 7f 00 00-00 00 8f 09 00 00 00 00 q...............
17:44:49.276117 00000000099eeb70 0800: 00 00 9f 09 00 00 00 00-00 ed 9e 09 00 00 00 00 ................
17:44:49.276118 00000000099eeb80 0810: 71 a2 fa f9 fc 7f 00 00-00 00 f4 f9 fc 7f 00 00 q...............
17:44:49.276119 00000000099eeb90 0820: 64 d5 0a fa fc 7f 00 00-f0 f9 9e 09 00 00 00 00 d...............
17:44:49.276120 00000000099eeba0 0830: 00 00 00 00 00 00 00 00-10 e6 9e 09 00 00 00 00 ................
17:44:49.276122 00000000099eebb0 0840: c0 fc fc f9 fc 7f 00 00-d4 33 08 fa fc 7f 00 00 .........3......
17:44:49.276123 00000000099eebc0 0850: d0 eb 9e 09 00 00 00 00-00 00 00 00 ab ab ab ab ................
17:44:49.276124 00000000099eebd0 0860: 0c 00 00 00 00 00 00 00-70 85 83 7f fc 7f 00 00 ........p.......
17:44:49.276125 00000000099eebe0 0870: bd 85 07 c8 fc 7f 00 00-00 00 05 c8 fc 7f 00 00 ................
17:44:49.276127 00000000099eebf0 0880: 98 08 0e c8 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276128 00000000099eec00 0890: 24 e6 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 $.........u.....
17:44:49.276129 00000000099eec10 08a0: 9c e6 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276130 00000000099eec20 08b0: 0c d7 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276132 00000000099eec30 08c0: 0c dd 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276133 00000000099eec40 08d0: bc de 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276134 00000000099eec50 08e0: 20 d5 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00  .........u.....
17:44:49.276135 00000000099eec60 08f0: f8 ba 11 80 fc 7f 00 00-00 00 75 7f fc 7f 00 00 ..........u.....
17:44:49.276137 00000000099eec70 0900: dc bb 11 80 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276138 00000000099eec80 0910: 54 ef 3b b6 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 T.;.............
17:44:49.276139 00000000099eec90 0920: 58 07 3b b6 fc 7f 00 00-00 00 0a b6 fc 7f 00 00 X.;.............
17:44:49.276141 00000000099eeca0 0930: 70 f8 3a b6 fc 7f 00 00-c0 ee 9e 09 00 00 00 00 p.:.............
17:44:49.276142 00000000099eecb0 0940: bc 83 43 da 28 a0 00 00-00 00 00 00 00 00 00 00 ..C.(...........
17:44:49.276143 00000000099eecc0 0950: 83 fb ff ff 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276144 00000000099eecd0 0960: 40 cb 65 06 00 00 00 00-02 00 00 00 00 00 00 00 @.e.............
17:44:49.276145 00000000099eece0 0970: 21 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 !...............
17:44:49.276147 00000000099eecf0 0980: b0 3c 6e 0c 00 00 00 00-ee 34 fe f9 fc 7f 00 00 .<n......4......
17:44:49.276148 00000000099eed00 0990: 10 8c 3b 04 00 00 00 00-10 8c 3b 04 00 00 00 00 ..;.......;.....
17:44:49.276149 00000000099eed10 09a0: e8 c1 7d 08 00 00 00 00-10 8c 3b 04 00 00 00 00 ..}.......;.....
17:44:49.276150 00000000099eed20 09b0: 48 f3 9e 09 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276152 00000000099eed30 09c0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
17:44:49.276153 00000000099eed40 09d0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
17:44:49.276154 00000000099eed50 09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276155 **************** ****  <ditto x 2>
17:44:49.276156 00000000099eed80 0a10: 00 00 f1 61 5e 6b 90 e8-00 00 00 00 00 00 00 00 ...a^k..........
17:44:49.276157 00000000099eed90 0a20: e8 c1 7d 08 00 00 00 00-90 f4 9e 09 00 00 00 00 ..}.............
17:44:49.276158 00000000099eeda0 0a30: b0 3c 6e 0c 00 00 00 00-01 00 00 00 00 00 00 00 .<n.............
17:44:49.276159 00000000099eedb0 0a40: 21 00 00 00 00 00 00 00-48 f1 9e 09 00 00 00 00 !.......H.......
17:44:49.276161 00000000099eedc0 0a50: b0 3c 6e 0c 00 00 00 00-00 00 00 00 00 00 00 00 .<n.............
17:44:49.276162 00000000099eedd0 0a60: 20 f4 9e 09 00 00 00 00-02 00 00 00 00 00 00 00  ...............
17:44:49.276163 00000000099eede0 0a70: 40 cb 65 06 00 00 00 00-00 00 00 00 00 00 00 00 @.e.............
17:44:49.276164 00000000099eedf0 0a80: 83 fb ff ff 00 00 00 00-61 85 07 c8 fc 7f 00 00 ........a.......
17:44:49.276166 00000000099eee00 0a90: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276167 00000000099eee10 0aa0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
17:44:49.276168 00000000099eee20 0ab0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276169 **************** ****  <ditto x 23>
17:44:49.276170 00000000099eefa0 0c30: 00 00 00 00 00 00 00 00-00 00 8f 03 00 00 00 00 ................
17:44:49.276171 00000000099eefb0 0c40: 40 00 00 00 00 00 00 00-05 00 00 00 00 00 00 00 @...............
17:44:49.276172 00000000099eefc0 0c50: a0 9f bc 06 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276173 00000000099eefd0 0c60: 00 00 00 00 00 00 00 00-c0 51 8f 03 00 00 00 00 .........Q......
17:44:49.276175 00000000099eefe0 0c70: b0 0d 8f 03 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276176 00000000099eeff0 0c80: 10 00 00 00 00 00 00 00-c0 48 8f 03 00 00 00 00 .........H......
17:44:49.276177 00000000099ef000 0c90: 00 00 00 00 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276178 00000000099ef010 0ca0: 00 00 00 00 00 00 00 00-02 00 00 00 00 00 00 00 ................
17:44:49.276180 00000000099ef020 0cb0: 10 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276181 00000000099ef030 0cc0: 00 00 9a 03 00 00 00 00-d9 f0 9e 09 00 00 00 00 ................
17:44:49.276182 00000000099ef040 0cd0: 01 00 00 00 00 00 00 00-97 d9 f4 f9 fc 7f 00 00 ................
17:44:49.276183 00000000099ef050 0ce0: 40 00 00 00 00 00 00 00-05 00 00 00 00 00 00 00 @...............
17:44:49.276185 00000000099ef060 0cf0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276186 00000000099ef070 0d00: 00 21 4f 07 00 00 00 00-e0 20 4f 07 00 00 00 00 .!O...... O.....
17:44:49.276187 00000000099ef080 0d10: 02 00 00 00 00 00 00 00-98 3a cc 06 00 00 00 00 .........:......
17:44:49.276188 00000000099ef090 0d20: 40 f2 9e 09 00 00 00 00-c0 48 8f 03 00 00 00 00 @........H......
17:44:49.276189 00000000099ef0a0 0d30: 00 00 00 00 00 00 00 00-02 00 00 00 00 00 00 00 ................
17:44:49.276191 00000000099ef0b0 0d40: 30 00 00 00 00 00 00 00-00 00 cc 06 00 00 00 00 0...............
17:44:49.276192 00000000099ef0c0 0d50: 01 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276193 00000000099ef0d0 0d60: 00 00 00 00 00 00 00 00-08 00 00 00 00 00 00 00 ................
17:44:49.276194 00000000099ef0e0 0d70: 30 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0...............
17:44:49.276196 00000000099ef0f0 0d80: 00 00 9a 03 00 00 00 00-78 e0 84 80 fc 7f 00 00 ........x.......
17:44:49.276197 00000000099ef100 0d90: d0 3e 41 05 00 00 00 00-f8 be 13 c7 fc 7f 00 00 .>A.............
17:44:49.276198 00000000099ef110 0da0: 00 21 4f 07 00 00 00 00-e0 20 4f 07 00 00 00 00 .!O...... O.....
17:44:49.276200 00000000099ef120 0db0: c0 e2 bb 06 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276201 00000000099ef130 0dc0: ff ff ff ff 00 00 00 00-70 cb 65 06 00 00 00 00 ........p.e.....
17:44:49.276202 00000000099ef140 0dd0: f0 3c 6e 0c 00 00 00 00-e5 c7 d2 f6 fc 7f 00 00 .<n.............
17:44:49.276203 00000000099ef150 0de0: 60 b8 6e 0c 00 00 00 00-78 e0 84 80 fc 7f 00 00 `.n.....x.......
17:44:49.276204 00000000099ef160 0df0: 00 04 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276206 00000000099ef170 0e00: 00 00 00 00 00 00 00 00-77 db 84 7f fc 7f 00 00 ........w.......
17:44:49.276207 00000000099ef180 0e10: 40 ca 65 06 00 00 00 00-00 30 cf 00 00 00 00 00 @.e......0......
17:44:49.276208 00000000099ef190 0e20: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276209 00000000099ef1a0 0e30: 00 e8 bb 06 00 00 00 00-70 cb 65 06 00 00 00 00 ........p.e.....
17:44:49.276211 00000000099ef1b0 0e40: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276212 00000000099ef1c0 0e50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276213 00000000099ef1d0 0e60: 30 fb ff ff 90 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
17:44:49.276214 00000000099ef1e0 0e70: f0 00 00 00 d0 01 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276215 00000000099ef1f0 0e80: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276217 00000000099ef200 0e90: 61 85 07 c8 fc 7f 00 00-02 00 00 00 00 00 00 00 a...............
17:44:49.276218 00000000099ef210 0ea0: 01 00 00 00 00 00 00 00-21 00 00 00 00 00 00 00 ........!.......
17:44:49.276219 00000000099ef220 0eb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276220 **************** ****  <ditto x 6>
17:44:49.276221 00000000099ef290 0f20: 61 85 07 c8 fc 7f 00 00-00 00 00 00 00 00 00 00 a...............
17:44:49.276222 00000000099ef2a0 0f30: 00 00 00 00 00 00 00 00-90 f4 9e 09 00 00 00 00 ................
17:44:49.276223 00000000099ef2b0 0f40: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276224 00000000099ef2c0 0f50: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
17:44:49.276226 00000000099ef2d0 0f60: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276227 **************** ****  <ditto x 19>
17:44:49.276227 00000000099ef410 10a0: a1 90 c0 62 90 e8 00 00-00 00 00 00 00 00 00 00 ...b............
17:44:49.276229 00000000099ef420 10b0: 83 fb ff ff 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276230 00000000099ef430 10c0: 40 cb 65 06 00 00 00 00-02 00 00 00 00 00 00 00 @.e.............
17:44:49.276231 00000000099ef440 10d0: 21 00 00 00 00 00 00 00-0e c6 d2 f6 fc 7f 00 00 !...............
17:44:49.276232 00000000099ef450 10e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276234 00000000099ef460 10f0: e8 c1 7d 08 00 00 00 00-01 00 00 00 00 00 00 00 ..}.............
17:44:49.276235 00000000099ef470 1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276236 00000000099ef480 1110: 00 00 00 00 00 00 00 00-5c 85 07 c8 fc 7f 00 00 ........\.......
17:44:49.276256 00000000099ef490 1120: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276257 **************** ****  <ditto x 2>
17:44:49.276258 00000000099ef4c0 1150: a0 bc e3 0c 00 00 00 00-3a 9b 85 7f fc 7f 00 00 ........:.......
17:44:49.276259 00000000099ef4d0 1160: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
17:44:49.276260 00000000099ef4e0 1170: 48 11 00 00 00 00 00 00-00 00 00 00 00 00 00 00 H...............
17:44:49.276262 00000000099ef4f0 1180: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276263 00000000099ef500 1190: 00 00 00 00 00 00 00 00-76 a4 85 7f fc 7f 00 00 ........v.......
17:44:49.276264 00000000099ef510 11a0: a0 bc e3 0c 00 00 00 00-00 e8 bb 06 00 00 00 00 ................
17:44:49.276266 00000000099ef520 11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276267 00000000099ef530 11c0: 00 00 00 00 00 00 00 00-65 00 85 7f fc 7f 00 00 ........e.......
17:44:49.276268 00000000099ef540 11d0: 00 00 00 00 00 00 00 00-8e 08 20 b6 fc 7f 00 00 .......... .....
17:44:49.276269 00000000099ef550 11e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276271 00000000099ef560 11f0: 00 00 00 00 00 00 00 00-b0 06 20 b6 fc 7f 00 00 .......... .....
17:44:49.276272 00000000099ef570 1200: 00 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276273 00000000099ef580 1210: 02 00 00 00 00 00 00 00-e5 30 85 7f fc 7f 00 00 .........0......
17:44:49.276274 00000000099ef590 1220: 00 00 00 00 00 00 00 00-00 e8 bb 06 00 00 00 00 ................
17:44:49.276276 00000000099ef5a0 1230: b0 3c 6e 0c 00 00 00 00-00 00 00 00 00 00 00 00 .<n.............
17:44:49.276277 00000000099ef5b0 1240: 68 36 d3 0d 00 00 00 00-18 0e d3 0d 00 00 00 00 h6..............
17:44:49.276278 00000000099ef5c0 1250: bb 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276280 00000000099ef5d0 1260: b0 3c 6e 0c 00 00 00 00-3a 42 85 7f fc 7f 00 00 .<n.....:B......
17:44:49.276281 00000000099ef5e0 1270: 00 e8 bb 06 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276282 00000000099ef5f0 1280: 02 00 00 00 00 00 00 00-5a 67 8a 80 fc 7f 00 00 ........Zg......
17:44:49.276283 00000000099ef600 1290: 02 00 00 00 00 00 00 00-81 f4 84 7f fc 7f 00 00 ................
17:44:49.276285 00000000099ef610 12a0: 00 00 00 00 00 00 00 00-10 fc e3 0c 00 00 00 00 ................
17:44:49.276286 00000000099ef620 12b0: 40 ca 65 06 00 00 00 00-78 e0 84 80 fc 7f 00 00 @.e.....x.......
17:44:49.276287 00000000099ef630 12c0: 83 fb ff ff 00 00 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276289 00000000099ef640 12d0: 01 00 00 00 00 00 00 00-50 de e0 09 00 00 00 00 ........P.......
17:44:49.276290 00000000099ef650 12e0: d0 e2 e0 09 00 00 00 00-1e 86 83 7f fc 7f 00 00 ................
17:44:49.276291 00000000099ef660 12f0: d8 e2 e0 09 00 00 00 00-0b 00 00 00 00 00 00 00 ................
17:44:49.276292 00000000099ef670 1300: 00 00 00 00 00 00 00 00-79 ac 17 b6 fc 7f 00 00 ........y.......
17:44:49.276294 00000000099ef680 1310: d0 e2 e0 09 00 00 00 00-c0 8f 83 7f fc 7f 00 00 ................
17:44:49.276295 00000000099ef690 1320: d8 e2 e0 09 00 00 00 00-0b 00 00 00 00 00 00 00 ................
17:44:49.276296 00000000099ef6a0 1330: 00 00 00 00 00 00 00 00-50 de e0 09 00 00 00 00 ........P.......
17:44:49.276297 00000000099ef6b0 1340: ae 85 fe 65 34 86 05 00-00 00 9f 09 00 00 00 00 ...e4...........
17:44:49.276299 00000000099ef6c0 1350: 83 fb ff ff 00 00 00 00-00 00 0a b6 fc 7f 00 00 ................
17:44:49.276300 00000000099ef6d0 1360: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276301 00000000099ef6e0 1370: 0b d2 00 00 00 00 00 00-26 de 1f b6 fc 7f 00 00 ........&.......
17:44:49.276303 00000000099ef6f0 1380: 60 7c 9f 09 00 00 00 00-50 8d 83 7f fc 7f 00 00 `|......P.......
17:44:49.276304 00000000099ef700 1390: 50 dd e0 09 00 00 00 00-dc d7 10 b6 fc 7f 00 00 P...............
17:44:49.276305 00000000099ef710 13a0: 01 00 00 00 00 00 00 00-07 83 22 00 00 00 00 00 .........."".....
17:44:49.276306 00000000099ef720 13b0: 00 00 00 00 00 00 00 00-00 c0 a0 09 00 00 00 00 ................
17:44:49.276308 00000000099ef730 13c0: 00 00 9f 09 00 00 00 00-0a 2e 0f b6 fc 7f 00 00 ................
17:44:49.276309 00000000099ef740 13d0: 00 00 00 00 00 00 00 00-3e 0a 00 00 00 00 00 00 ........>.......
17:44:49.276310 00000000099ef750 13e0: 00 00 00 00 00 00 00 00-46 b6 15 b6 fc 7f 00 00 ........F.......
17:44:49.276311 00000000099ef760 13f0: 01 00 00 00 00 00 00 00-99 3e 0e b6 fc 7f 00 00 .........>......
17:44:49.276326 00000000099ef770 1400: 3e 0a 00 00 00 00 00 00-b8 39 0e b6 fc 7f 00 00 >........9......
17:44:49.276328 00000000099ef780 1410: 00 c0 a0 09 00 00 00 00-20 f8 9e 09 00 00 00 00 ........ .......
17:44:49.276329 00000000099ef790 1420: 00 00 9f 09 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276330 00000000099ef7a0 1430: 00 00 9f 09 00 00 00 00-19 98 0e b6 fc 7f 00 00 ................
17:44:49.276331 00000000099ef7b0 1440: 00 c0 a0 09 00 00 00 00-01 00 00 00 00 00 00 00 ................
17:44:49.276333 00000000099ef7c0 1450: 01 00 00 00 00 00 00 00-20 f8 9e 09 00 00 00 00 ........ .......
17:44:49.276334 00000000099ef7d0 1460: 00 00 9f 09 00 00 00 00-a8 63 0e b6 fc 7f 00 00 .........c......
17:44:49.276335 00000000099ef7e0 1470: 00 c0 a0 09 00 00 00 00-06 00 00 00 00 00 00 00 ................
17:44:49.276336 00000000099ef7f0 1480: 01 00 00 00 00 00 00 00-5c 04 00 00 00 00 00 00 ........\.......
17:44:49.276338 00000000099ef800 1490: 00 00 00 00 00 00 00 00-00 00 9f 09 00 00 00 00 ................
17:44:49.276339 00000000099ef810 14a0: 00 c0 a0 09 00 00 00 00-00 20 53 07 00 00 00 00 ......... S.....
17:44:49.276340 00000000099ef820 14b0: 00 3f 53 07 00 00 00 00-c3 2e 15 b6 fc 7f 00 00 .?S.............
17:44:49.276341 00000000099ef830 14c0: 30 06 31 b6 fc 7f 00 00-50 01 31 b6 fc 7f 00 00 0.1.....P.1.....
17:44:49.276343 00000000099ef840 14d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276344 00000000099ef850 14e0: 00 00 00 00 00 00 00 00-00 00 9f 09 00 00 00 00 ................
17:44:49.276345 00000000099ef860 14f0: a0 3f 53 07 00 00 00 00-d8 3c 15 b6 fc 7f 00 00 .?S......<......
17:44:49.276346 00000000099ef870 1500: 00 00 9f 09 00 00 00 00-00 c0 a0 09 00 00 00 00 ................
17:44:49.276348 00000000099ef880 1510: 00 20 53 07 00 00 00 00-00 00 00 00 00 00 00 00 . S.............
17:44:49.276349 00000000099ef890 1520: c0 69 9a 03 00 00 00 00-32 b2 88 80 fc 7f 00 00 .i......2.......
17:44:49.276350 00000000099ef8a0 1530: 00 00 00 00 00 00 00 00-2c 3b 00 00 00 00 00 00 ........,;......
17:44:49.276351 00000000099ef8b0 1540: 50 e6 19 07 00 00 00 00-00 00 00 00 00 00 00 00 P...............
17:44:49.276353 00000000099ef8c0 1550: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276354 00000000099ef8d0 1560: 00 00 00 00 00 00 00 00-50 e6 19 07 00 00 00 00 ........P.......
17:44:49.276355 00000000099ef8e0 1570: 2c 3b 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ,;..............
17:44:49.276356 00000000099ef8f0 1580: 50 e6 19 07 00 00 00 00-3f c6 7f 80 fc 7f 00 00 P.......?.......
17:44:49.276358 00000000099ef900 1590: 00 00 00 00 00 00 00 00-a0 3f 53 07 00 00 00 00 .........?S.....
17:44:49.276359 00000000099ef910 15a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276360 00000000099ef920 15b0: 50 e6 19 07 00 00 00 00-52 63 8a 80 fc 7f 00 00 P.......Rc......
17:44:49.276361 00000000099ef930 15c0: 00 6b 31 07 00 00 00 00-00 6b 31 07 00 00 00 00 .k1......k1.....
17:44:49.276362 00000000099ef940 15d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276364 00000000099ef950 15e0: 00 00 00 00 00 00 00 00-9f 1d 77 55 00 00 00 00 ..........wU....
17:44:49.276365 00000000099ef960 15f0: 00 6b 31 07 00 00 00 00-00 00 00 00 00 00 00 00 .k1.............
17:44:49.276366 00000000099ef970 1600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276367 00000000099ef980 1610: 00 00 00 00 00 00 00 00-3b 1e 77 55 00 00 00 00 ........;.wU....
17:44:49.276369 00000000099ef990 1620: c0 2a 80 55 00 00 00 00-00 6b 31 07 00 00 00 00 .*.U.....k1.....
17:44:49.276370 00000000099ef9a0 1630: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276371 00000000099ef9b0 1640: 00 00 00 00 00 00 00 00-74 79 6b f9 fc 7f 00 00 ........tyk.....
17:44:49.276372 00000000099ef9c0 1650: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276373 00000000099ef9d0 1660: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276375 00000000099ef9e0 1670: 00 00 00 00 00 00 00 00-71 a2 fa f9 fc 7f 00 00 ........q.......
17:44:49.276376 00000000099ef9f0 1680: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276377 **************** ****  <ditto x 2>
17:44:49.276378 00000000099efa20 16b0: 00 00 00 00 5d c0 13 47-00 00 00 00 00 00 00 00 ....]..G........
17:44:49.276379 00000000099efa30 16c0: b0 6a d5 f6 fc 7f 00 00-60 e5 9e 09 00 00 00 00 .j......`.......
17:44:49.276380 00000000099efa40 16d0: e5 ff 03 00 68 57 35 8e-ed aa c6 b1 fc 7f 00 00 ....hW5.........
17:44:49.276381 00000000099efa50 16e0: b0 6a d5 f6 fc 7f 00 00-60 e5 9e 09 00 00 00 00 .j......`.......
17:44:49.276383 00000000099efa60 16f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276384 **************** ****  <ditto x 88>
17:44:49.276385 00000000099efff0 1c80: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
17:44:49.276399 Thread ID:   0000000000003b2c
17:44:49.276404 Thread name: EMT
17:44:49.276408 Thread IPRT: 000000000719e650
17:44:49.276412 
17:44:49.276412 Loaded Modules:
17:44:49.276412 Address range                    [*] Timestamp Path
17:44:49.276417 00007ff69d790000..00007ff69d8a4fff   5d9f7c37  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
17:44:49.276423 00007ffcf9f40000..00007ffcfa12cfff   1f1a0210  C:\WINDOWS\SYSTEM32\ntdll.dll
17:44:49.276428 00007ffcf96a0000..00007ffcf9752fff   250a0626  C:\WINDOWS\System32\KERNEL32.DLL
17:44:49.276433 00007ffcf6cd0000..00007ffcf6f62fff   fc217636  C:\WINDOWS\System32\KERNELBASE.dll
17:44:49.276438 0000000068000000..0000000068065fff   5b060941  C:\WINDOWS\System32\QIPCAP64.dll
17:44:49.276442 00007ffcf9890000..00007ffcf9932fff   b12069f9  C:\WINDOWS\System32\ADVAPI32.dll
17:44:49.276448 00007ffcf97f0000..00007ffcf988dfff   f362c2f9  C:\WINDOWS\System32\msvcrt.dll
17:44:49.276453 00007ffcf74e0000..00007ffcf757dfff   7d59184a  C:\WINDOWS\System32\sechost.dll
17:44:49.276458 00007ffcf8e20000..00007ffcf8f41fff   755dd37f  C:\WINDOWS\System32\RPCRT4.dll
17:44:49.276463 00007ffcf75c0000..00007ffcf8ab3fff   8126cd3a  C:\WINDOWS\System32\SHELL32.dll
17:44:49.276467 00007ffcf6f70000..00007ffcf6fb9fff   ca7e64ca  C:\WINDOWS\System32\cfgmgr32.dll
17:44:49.276472 00007ffcf6000000..00007ffcf60f9fff   15f8b9b3  C:\WINDOWS\System32\ucrtbase.dll
17:44:49.276477 00007ffcf8ac0000..00007ffcf8b67fff   9a0e77eb  C:\WINDOWS\System32\shcore.dll
17:44:49.276482 00007ffcf9120000..00007ffcf944bfff   c366780e  C:\WINDOWS\System32\combase.dll
17:44:49.276487 00007ffcf6160000..00007ffcf61ddfff   94fbdec9  C:\WINDOWS\System32\bcryptPrimitives.dll
17:44:49.276491 00007ffcf6490000..00007ffcf6bdcfff   9a536081  C:\WINDOWS\System32\windows.storage.dll
17:44:49.276496 00007ffcf6c10000..00007ffcf6caffff   448f33c2  C:\WINDOWS\System32\msvcp_win.dll
17:44:49.276501 00007ffcf5fb0000..00007ffcf5fd3fff   36191177  C:\WINDOWS\System32\profapi.dll
17:44:49.276506 00007ffcf5f50000..00007ffcf5facfff   8941f3e3  C:\WINDOWS\System32\powrprof.dll
17:44:49.276511 00007ffcf7160000..00007ffcf71b1fff   4392c932  C:\WINDOWS\System32\shlwapi.dll
17:44:49.276516 00007ffcf7590000..00007ffcf75b8fff   f945b633  C:\WINDOWS\System32\GDI32.dll
17:44:49.276520 00007ffcf6fc0000..00007ffcf7158fff   99521ac9  C:\WINDOWS\System32\gdi32full.dll
17:44:49.276525 00007ffcf9500000..00007ffcf9696fff   9d4422cf  C:\WINDOWS\System32\USER32.dll
17:44:49.276530 00007ffcf61e0000..00007ffcf61fffff   ff141dbb  C:\WINDOWS\System32\win32u.dll
17:44:49.276534 00007ffcf5f30000..00007ffcf5f40fff   be88784d  C:\WINDOWS\System32\kernel.appcore.dll
17:44:49.276539 00007ffcf6cb0000..00007ffcf6cc6fff   fe800ac7  C:\WINDOWS\System32\cryptsp.dll
17:44:49.276544 00007ffcf5500000..00007ffcf55c5fff   e8b181dc  C:\WINDOWS\SYSTEM32\DNSAPI.dll
17:44:49.276549 00007ffcf99c0000..00007ffcf9a2cfff   19b2d7cc  C:\WINDOWS\System32\WS2_32.dll
17:44:49.276554 00007ffcf8ca0000..00007ffcf8ca7fff   d06e5a23  C:\WINDOWS\System32\NSI.dll
17:44:49.276558 00007ffcf97c0000..00007ffcf97edfff   789dcfe1  C:\WINDOWS\System32\IMM32.DLL
17:44:49.276563 00007ffcf54c0000..00007ffcf54fcfff   1ee25965  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
17:44:49.276568 00007ffcf3bb0000..00007ffcf3bb4fff   5d9f7bec  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
17:44:49.276573 00007ffcf6100000..00007ffcf6158fff   d51e499a  C:\WINDOWS\System32\Wintrust.dll
17:44:49.276578 00007ffcf5fe0000..00007ffcf5ff1fff   ac91a4b2  C:\WINDOWS\System32\MSASN1.dll
17:44:49.276583 00007ffcf62b0000..00007ffcf648afff   b2fbbe58  C:\WINDOWS\System32\CRYPT32.dll
17:44:49.276587 0000000001010000..0000000001035fff   4d019572  C:\WINDOWS\System32\bcrypt.dll
17:44:49.276592 00007ffcf50c0000..00007ffcf50f2fff   eb037b86  C:\WINDOWS\system32\rsaenh.dll
17:44:49.276597 00007ffcf5970000..00007ffcf597bfff   210d2d73  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
17:44:49.276601 00007ffcf9100000..00007ffcf911cfff   00e30045  C:\WINDOWS\System32\imagehlp.dll
17:44:49.276606 00007ffcf4900000..00007ffcf4921fff   7f4edceb  C:\WINDOWS\SYSTEM32\gpapi.dll
17:44:49.276611 00007ffcd8d90000..00007ffcd8dbefff   1a60e9ce  C:\WINDOWS\System32\cryptnet.dll
17:44:49.276616 00007ffc80730000..00007ffc80d11fff   5d9f7c37  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.276621 0000000055750000..0000000055821fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.276626 0000000056070000..0000000056107fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
17:44:49.276630 00007ffcc7b40000..00007ffcc7cc7fff   5d9f7c48  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
17:44:49.276635 00007ffcf8cb0000..00007ffcf8e04fff   197cc46a  C:\WINDOWS\System32\ole32.dll
17:44:49.276640 00007ffcf8f50000..00007ffcf9013fff   bcde805b  C:\WINDOWS\System32\OLEAUT32.dll
17:44:49.276645 00007ffcda970000..00007ffcdaa96fff   9747484e  C:\WINDOWS\SYSTEM32\OPENGL32.dll
17:44:49.276650 00007ffc80d20000..00007ffc830a6fff   5d9f7c41  C:\Program Files\Oracle\VirtualBox\VBoxGlobal.dll
17:44:49.276656 0000000053f20000..0000000054484fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
17:44:49.276661 00007ffc80130000..00007ffc80726fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
17:44:49.276665 00000000539b0000..0000000053f10fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
17:44:49.276670 00000000556f0000..0000000055743fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
17:44:49.276675 00007ffcebbe0000..00007ffcebc03fff   01dd0441  C:\WINDOWS\SYSTEM32\WINMM.dll
17:44:49.276680 00007ffcda930000..00007ffcda95bfff   80b792c5  C:\WINDOWS\SYSTEM32\GLU32.dll
17:44:49.276685 00007ffcddd70000..00007ffcddd8afff   696e6b80  C:\WINDOWS\SYSTEM32\MPR.dll
17:44:49.276690 00007ffcebbb0000..00007ffcebbdcfff   61c36296  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
17:44:49.276694 00007ffcced10000..00007ffccee3dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
17:44:49.276699 00007ffcf2600000..00007ffcf269bfff   607fb06a  C:\WINDOWS\system32\uxtheme.dll
17:44:49.276704 00007ffcbf400000..00007ffcbf613fff   5c94072c  C:\Program Files\NVIDIA Corporation\nview\nViewH64.dll
17:44:49.276709 00007ffcf42c0000..00007ffcf42edfff   674bb59c  C:\WINDOWS\SYSTEM32\dwmapi.dll
17:44:49.276714 00007ffcef9e0000..00007ffcef9e9fff   b11b88e5  C:\WINDOWS\System32\VERSION.dll
17:44:49.276719 00007ffcf4c80000..00007ffcf4cb0fff   376a9861  C:\WINDOWS\SYSTEM32\ntmarta.dll
17:44:49.276724 00007ffcf5e30000..00007ffcf5e57fff   153decdb  C:\WINDOWS\system32\userenv.dll
17:44:49.276729 0000000004bb0000..0000000004c51fff   aaba4fa9  C:\WINDOWS\System32\clbcatq.dll
17:44:49.276734 00007ffcc6ee0000..00007ffcc7283fff   5d9f7c45  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
17:44:49.276739 00007ffcc80f0000..00007ffcc81c4fff   5d9f7c3c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
17:44:49.276743 0000000008580000..00000000086ebfff   3243efc5  C:\WINDOWS\System32\MSCTF.dll
17:44:49.276748 00007ffceb370000..00007ffceb3c5fff   28590552  C:\WINDOWS\system32\dataexchange.dll
17:44:49.276753 00007ffcf3320000..00007ffcf359dfff   13a31007  C:\WINDOWS\system32\d3d11.dll
17:44:49.276758 00007ffced1f0000..00007ffced3b2fff   517b0b92  C:\WINDOWS\system32\dcomp.dll
17:44:49.276763 00007ffcf49d0000..00007ffcf4a91fff   8bbb106a  C:\WINDOWS\system32\dxgi.dll
17:44:49.276767 00007ffcf3f80000..00007ffcf418cfff   270a22eb  C:\WINDOWS\system32\twinapi.appcore.dll
17:44:49.276772 00007ffcf4190000..00007ffcf41b7fff   fd3b8fed  C:\WINDOWS\system32\RMCLIENT.dll
17:44:49.276777 00007ffcc4640000..00007ffcc46d9fff   14ab50a3  C:\Windows\System32\ActXPrxy.dll
17:44:49.276782 00007ffce2d50000..00007ffce348efff   038397d3  C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
17:44:49.276787 00007ffcea490000..00007ffcea524fff   1163b0af  C:\WINDOWS\System32\TextInputFramework.dll
17:44:49.276792 00007ffce9d80000..00007ffcea0a1fff   0ef1f94b  C:\WINDOWS\System32\CoreUIComponents.dll
17:44:49.276797 00007ffced7c0000..00007ffced8a1fff   57021383  C:\WINDOWS\System32\CoreMessaging.dll
17:44:49.276801 00007ffcf14c0000..00007ffcf1612fff   57f8d9f0  C:\WINDOWS\SYSTEM32\wintypes.dll
17:44:49.276806 00007ffce5900000..00007ffce596bfff   2b9a3a00  C:\WINDOWS\system32\Oleacc.dll
17:44:49.276811 00007ffceb3d0000..00007ffceb3e0fff   80ed95b9  C:\WINDOWS\system32\wbem\wbemprox.dll
17:44:49.276816 00007ffcec520000..00007ffcec5a4fff   264de62a  C:\WINDOWS\SYSTEM32\wbemcomn.dll
17:44:49.276821 00007ffcea450000..00007ffcea463fff   42167f4e  C:\WINDOWS\system32\wbem\wbemsvc.dll
17:44:49.276826 00007ffcea920000..00007ffceaa10fff   c27bfeee  C:\WINDOWS\system32\wbem\fastprox.dll
17:44:49.276830 00007ffcb60a0000..00007ffcb63d0fff   5d9f7c3d  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.276835 00000000555e0000..00000000556eafff   5d9f7c48  C:\Program Files\Oracle\VirtualBox\VBoxREM.dll
17:44:49.276841 00007ffcd0a10000..00007ffcd0a90fff   c42656ba  C:\Windows\System32\NetSetupShim.dll
17:44:49.276846 00007ffcf9a30000..00007ffcf9ea5fff   cc9bc0eb  C:\WINDOWS\System32\setupapi.dll
17:44:49.276851 00007ffcebeb0000..00007ffcebed4fff   567de38b  C:\Windows\System32\NetSetupApi.dll
17:44:49.276856 00007ffcee450000..00007ffcee462fff   415b279a  C:\Windows\System32\DEVRTL.dll
17:44:49.276860 00007ffceda80000..00007ffcedb4cfff   b7ea870e  C:\Windows\System32\NetSetupEngine.dll
17:44:49.276865 00007ffcf18c0000..00007ffcf18cafff   4eee05dd  C:\WINDOWS\SYSTEM32\WINNSI.DLL
17:44:49.276870 00007ffcf3b10000..00007ffcf3b1afff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
17:44:49.276876 00007ffcf3920000..00007ffcf392cfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
17:44:49.276881 00007ffc7f750000..00007ffc80129fff   5d9f7c45  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.276885 00007ffceff10000..00007ffceff73fff   5d9f7c3c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
17:44:49.276890 00007ffceb580000..00007ffceb5dbfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
17:44:49.276895 00007ffcf21d0000..00007ffcf21e3fff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
17:44:49.276901 00007ffcf36e0000..00007ffcf36ebfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
17:44:49.276906 00007ffcf1e00000..00007ffcf1e0cfff   5d9f7c44  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
17:44:49.276911 00007ffcf26e0000..00007ffcf26f5fff   94c6e95c  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
17:44:49.276934 00007ffcf26c0000..00007ffcf26dbfff   3a6169db  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
17:44:49.276941 00007ffcf10c0000..00007ffcf112ffff   2aab5430  C:\WINDOWS\System32\MMDevApi.dll
17:44:49.276946 00007ffcf5d60000..00007ffcf5d88fff   3306001c  C:\WINDOWS\System32\DEVOBJ.dll
17:44:49.276953 00007ffcf3080000..00007ffcf3228fff   296f9bb4  C:\WINDOWS\System32\PROPSYS.dll
17:44:49.276962 00007ffcc8050000..00007ffcc80e5fff*  807cb1be  C:\WINDOWS\System32\dsound.dll
17:44:49.276970 00007ffcf0af0000..00007ffcf0c37fff   6716b91a  C:\WINDOWS\System32\AUDIOSES.DLL
17:44:49.276978 00007ffcf1270000..00007ffcf1279fff   e8464c59  C:\WINDOWS\SYSTEM32\AVRT.dll
17:44:49.276998 00007ffcf41c0000..00007ffcf41d3fff   dfd6e84b  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
17:44:49.277006 00007ffce5f60000..00007ffce5fa3fff   96f675cf  C:\WINDOWS\System32\wdmaud.drv
17:44:49.277011 00007ffcf3c70000..00007ffcf3c78fff   26b922dc  C:\WINDOWS\SYSTEM32\ksuser.dll
17:44:49.277016 00007ffcf3a30000..00007ffcf3a3cfff   d0ebc7cc  C:\WINDOWS\System32\msacm32.drv
17:44:49.277020 00007ffcf3a10000..00007ffcf3a2bfff   a416f17e  C:\WINDOWS\SYSTEM32\MSACM32.dll
17:44:49.277025 00007ffcf0d80000..00007ffcf0d89fff   240f6209  C:\WINDOWS\System32\midimap.dll
17:44:49.277030 00007ffcf57a0000..00007ffcf5806fff   9cffe601  C:\WINDOWS\system32\mswsock.dll
17:44:49.277035 00007ffcea5d0000..00007ffcea709fff   951b586c  C:\Windows\System32\Windows.UI.dll
17:44:49.277040 00007ffcea0e0000..00007ffcea1abfff   d5eb338f  C:\Windows\System32\InputHost.dll
17:44:49.277044 00007ffcf2710000..00007ffcf2ccdfff   9370a562  C:\Windows\System32\d2d1.dll
17:44:49.277049 
17:44:49.277049 Potential code addresses on the stack:
17:44:49.277053 Xcpt PC         : 00007ffcc8078561 - 0x00028561 bytes into C:\WINDOWS\System32\dsound.dll
17:44:49.277060 00000000099ef4c8: 00007ffc7f859b3a - 0x00109b3a bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277066 00000000099ef508: 00007ffc7f85a476 - 0x0010a476 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277072 00000000099ef538: 00007ffc7f850065 - 0x00100065 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277077 00000000099ef548: 00007ffcb620088e - 0x0016088e bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277082 00000000099ef568: 00007ffcb62006b0 - 0x001606b0 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277087 00000000099ef578: 00007ffc808a675a - 0x0017675a bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277093 00000000099ef588: 00007ffc7f8530e5 - 0x001030e5 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277100 00000000099ef5d8: 00007ffc7f85423a - 0x0010423a bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277105 00000000099ef5f8: 00007ffc808a675a - 0x0017675a bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277110 00000000099ef608: 00007ffc7f84f481 - 0x000ff481 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277116 00000000099ef628: 00007ffc8084e078 - 0x0011e078 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277122 00000000099ef638: 00007ffcb60a0000 - 0x00000000 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277127 00000000099ef658: 00007ffc7f83861e - 0x000e861e bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277133 00000000099ef678: 00007ffcb617ac79 - 0x000dac79 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277138 00000000099ef688: 00007ffc7f838fc0 - 0x000e8fc0 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277144 00000000099ef6c8: 00007ffcb60a0000 - 0x00000000 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277150 00000000099ef6e8: 00007ffcb61fde26 - 0x0015de26 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277155 00000000099ef6f8: 00007ffc7f838d50 - 0x000e8d50 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
17:44:49.277160 00000000099ef708: 00007ffcb610d7dc - 0x0006d7dc bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277166 00000000099ef738: 00007ffcb60f2e0a - 0x00052e0a bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277171 00000000099ef758: 00007ffcb615b646 - 0x000bb646 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277176 00000000099ef768: 00007ffcb60e3e99 - 0x00043e99 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277181 00000000099ef778: 00007ffcb60e39b8 - 0x000439b8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277187 00000000099ef7a8: 00007ffcb60e9819 - 0x00049819 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277193 00000000099ef7d8: 00007ffcb60e63a8 - 0x000463a8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277199 00000000099ef828: 00007ffcb6152ec3 - 0x000b2ec3 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277204 00000000099ef830: 00007ffcb6310630 - 0x00270630 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277210 00000000099ef838: 00007ffcb6310150 - 0x00270150 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277215 00000000099ef868: 00007ffcb6153cd8 - 0x000b3cd8 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
17:44:49.277221 00000000099ef898: 00007ffc8088b232 - 0x0015b232 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277227 00000000099ef8f8: 00007ffc807fc63f - 0x000cc63f bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277233 00000000099ef928: 00007ffc808a6352 - 0x00176352 bytes into C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
17:44:49.277238 00000000099ef958: 0000000055771d9f - 0x00021d9f bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277244 00000000099ef988: 0000000055771e3b - 0x00021e3b bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277248 00000000099ef990: 0000000055802ac0 - 0x000b2ac0 bytes into C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
17:44:49.277254 00000000099ef9b8: 00007ffcf96b7974 - 0x00017974 bytes into C:\WINDOWS\System32\KERNEL32.DLL
17:44:49.277258 00000000099ef9e8: 00007ffcf9faa271 - 0x0006a271 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
17:44:49.277263 00000000099efa30: 00007ffcf6d56ab0 - 0x00086ab0 bytes into C:\WINDOWS\System32\KERNELBASE.dll
17:44:49.277268 00000000099efa50: 00007ffcf6d56ab0 - 0x00086ab0 bytes into C:\WINDOWS\System32\KERNELBASE.dll
17:46:15.060205 GUI: UIMediumEnumerator: Medium-enumeration finished!
",garypx
19252,host Win10 crashes when guest Win10 reboots after update,Windows,VirtualBox 6.0.14,2020-01-22T02:56:05Z,2020-01-22T03:06:49Z,2020-01-22T03:06:49Z,"BSOD
DRIVER_IRQL_NOT_LESS_OR_EQUAL
VBoxDDR0.r0 

Happens only on guest restarts after it installed windows updates",EugeneK
19248,Accessability Bug: Certain text does not meet the minimum color contrast ratio,all,VirtualBox 6.0.14,2020-01-21T14:10:35Z,2020-01-21T14:10:35Z,2020-01-21T14:10:35Z,"Defect:  Certain text does not meet the minimum color contrast ratio. 
Description:  Please see example below for details.
Notes: 
•	Testing was performed using the Color Contrast Analyzer v2.2a.
•	This defect may exist elsewhere within the application.

Expected result:  The minimum contrast ratio for the visual presentation of text and image of text is expected to be at least 4.5:1, or 3:1 for text that is 18 points or larger, or 14 points bolded.
Reference: This defect is a failure against Section 508, 1.4.3 – Contrast (Minimum).
For more information, visit: http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html.
Steps to reproduce: 
1.	Open “Virtual Box”.
2.	Check the contrast ratio for the “Tools” text. (Highlighted below)

Notice that the contrast ratio for the Tools Menu is 2:4:1. Instead, the minimum contrast ratio for the visual presentation of text is expected to be at least 4.5:1, or 3:1 for text that is 18 points or larger or 14 points’ bolded.
 ",moshekaplan
19242,vdi file destroyed,Linux,VirtualBox 6.0.14,2020-01-19T09:55:22Z,2020-01-20T15:47:06Z,2020-01-20T15:47:06Z,"
So my .vdi has become empty - 0B size, checked with hex viewer. There is E_ACCESSDENIED entry at the very end of log from last proper run of my machine (previous log does not have this). Also modification date on the vdi file matches that of said log.

I understand that this error may be not reproducible but seems to me like a possible very major flaw. I have never tampered with disk file in any way and didn't notice any similar incidents on my hardware. 

I'm on windows 8.1, client was Linux Manjaro.

Thank you
",pk6610
19223,VirtualBox Extension Pack 6.0.16 installation failure,Linux,VirtualBox 6.0.14,2020-01-14T22:26:29Z,2020-01-19T21:32:23Z,2020-01-19T21:32:23Z,"Following 100% download of the Extension Pack for version 6.0.16, and during the verifying VirtualBox Extension Pack... the error message is displayed: ""The network operation failed with the following error: During network request: Url not found on the server."" I have attached the screenshot of this. Despite many repeated attempts, the error persists.",NickD
19123,VM Aborts On Laptop Suspend OR Machine Pause,Linux,VirtualBox 6.0.14,2019-12-02T12:53:20Z,2020-01-18T16:29:41Z,2020-01-18T16:29:41Z,"Hello,

Recently updated to 6.0.14 on Windows 10, hosting a Centos guest.

Two scenarios trigger a VM abort, maybe 50% of the time:
[1] pause VM (Machine -> Pause)
]2] send laptop to sleep

A dialog will pop up (immediately for [1]  and on resume for [2]).

Attaching logs and a screenshot of the dialog.

Cheers,
yato
",yato
19208,3d acecleration breaks VMSVGA,Linux,VirtualBox 6.0.14,2020-01-08T11:15:09Z,2020-01-16T10:33:20Z,2020-01-16T10:33:20Z,The Vivaldi browser gets broken when 3d acceleration is enabled with the graphics controller set to VMSVGA. Several users now experienced the issue while trying to run Vivaldi on Linux (ubuntu 18 in my case).,VincentX
19216,"When installing Ubuntu with finnish language, can no see continue tab",Linux,VirtualBox 6.0.14,2020-01-10T09:49:10Z,2020-01-10T09:49:10Z,2020-01-10T09:49:10Z,"Problem description:
When installing ubuntu-18.04.3-desktop-amd64 with language set to Finnish (Suomi) then next setup windows don't show ""continue"" button. I can continue using Tab button, so it means that continue button is there but it is not visible

Enviroment
Windows machine with 8G mem 250Gb SSDdisk and i5 Intel
Virtual machine has 2G memory and 15Gb disk allocated",Fugit185
19170,Oracle Linux 6 Fail Window Resize with VMSVGA,Linux,VirtualBox 6.0.14,2019-12-18T00:39:12Z,2019-12-31T17:45:05Z,2019-12-31T17:45:05Z,"Running Oracle Linux 6 (4.1.12-124.34.1.el6uek.x86_64) with the VMSVGA Graphics Controller selected does not allow the window to be resized keeping it full screen. Using the old VBoxVGA allows the resize of the window without issue.

The machine log is attached to this report.",DonC
19109,Host resume and VM does not respond,Windows,VirtualBox 6.0.14,2019-11-26T16:34:45Z,2019-12-10T10:44:09Z,2019-12-10T10:44:09Z,"Twice today I've resumed my host (after the host has gone to sleep because I've been away from my desk) and the guest has been frozen. The screen display is restored but the mouse isn't active.

After a minute or so the VM crashes and I have to restart the VM.

Logs are attached from after second crash.",Iain Waddell
19139,Kali linux VM buggy cursor,Linux,VirtualBox 6.0.14,2019-12-09T07:14:33Z,2019-12-09T22:23:55Z,2019-12-09T22:23:55Z,"hello,
My problem is that the mouse integration bugs after a while on kali linux so i have to reebot all the time.
I still can move the cursor graphicaly but its position stays the same. I can click but always on the same spot. 
But when i deactivate the mouse integration option the cursor now disapear but moves.",FvckNorris
19125,Crashes with vmsvga,Linux,VirtualBox 6.0.14,2019-12-02T19:51:45Z,2019-12-09T06:51:32Z,2019-12-09T06:51:32Z,"Vm crashes if more than 128 megabytes of vram is issued to vmsvga graphical controller.
for example 129
I booted from https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/25/Workstation/i386/iso/Fedora-Workstation-netinst-i386-25-1.3.iso",kotenok2000
19136,Failed to open a session for the virtual machine (hardening error),all,VirtualBox 6.0.14,2019-12-06T19:41:41Z,2019-12-08T15:48:53Z,2019-12-08T15:48:53Z,"Hello,

Failed to open a session for the virtual machine Linux 16LTS.

The virtual machine 'Linux 16LTS' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\Linux 16LTS\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}


Failed to open a session for the virtual machine WIN10.

The virtual machine 'WIN10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\ADELIO\VirtualBox VMs\WIN10\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}




Best Regards,

Adélio Miranda
",Adelio Miranda
19124,Installing the guest additions on Ubuntu results in no display,Linux,VirtualBox 6.0.14,2019-12-02T16:25:39Z,2019-12-03T05:07:21Z,2019-12-03T05:07:21Z,"All pre-requisites are installed.Installation gets to the point of generating the boot images and goes to blank screen. Rebooting does not help and the condition is only recoverable if you go into recovery mode and remove the virtual box guest additions.  
Repeated the process on Ubuntu 18.04 and 19.10 same result. 
The end result is a machine that cannot be interacted with graphically. ",RandomDude
19116,When accessing shared folders the WIN10 1903 VM reboots on a WIN10 1903 host,Windows,VirtualBox 6.0.14,2019-11-28T17:56:08Z,2019-11-30T11:57:21Z,2019-11-30T11:57:21Z,"Similar to ticket 18766, which was resolved in 6.0.14.  When I access shared folders some folders open up hesitantly, most cause a reboot of the VM.
I am new to this, so please let me know what other information would help.  Thanks.",psptconsp
19095,Network connection mode couldn't bridge to “VMware Network Adapter” on Windows 10,all,VirtualBox 6.0.14,2019-11-19T02:43:27Z,2019-11-22T08:51:41Z,2019-11-22T08:51:41Z,"I have a virtual machine that can only run on the vbox，but my primary system is installed on  ""Vmware Workstation Pro""。On MacOS，vbox network can bridge to vmware network adapter such as ""VMnet8""
.But it doesn't  work that way on window 10.",zlgxzswjy
19097,"""VirtualBox manager has stopped working"" when removing laptop from docking station",Linux,VirtualBox 6.0.14,2019-11-20T06:38:46Z,2019-11-20T06:49:34Z,2019-11-20T06:49:34Z,"When unddocking/docking my laptop (Fujitsu, Lifebook E Series) from the docking station the VirtualBox manager crashes with a dialog message: ""VirtualBox Manager has stopped working.

I'm running: Windows 10 x64 as host and have one virtual machine running at that time: ""Ubuntu 18.04.3 LTS"". This machine remains working, but the VM Manager is crasing. I followed the instructions to create a coredump which is attached.

My VM also crashes sometimes on dock/undock but here I need to gather more information and will file another ticket.

Expected behavior: Manger should not crash on dock/undock",martg
19081,Display shrinks to 1024x768,Windows,VirtualBox 6.0.14,2019-11-13T13:01:31Z,2019-11-16T08:39:50Z,2019-11-16T08:39:50Z,"I've been using VirtualBox for several years but recently my Windows 10 guest upgraded from release 1803 to 1903. Since then I've had problems.

Initially I would have random lockups. Suddenly the guest would be unresponsive and after a while it would crash and VirtualBox would report that the guest had aborted. Googling led me to sites that suggested the lockups were usually related to the graphics driver.

I was using VBoxVGA (as I'd originally started on v5.1 of VirtualBox). After lots of reading about the VirtualBox video drivers I discovered I should have been using VBoxSVGA when I upgraded to v6.0 of VirtualBox (currently on v6.0.14).

Since the switch I've not had any lockups but at random times instead my desktop shrinks. I'm using a 4K monitor in Full Screen mode (3840x2160) and when the shrink occurs the Windows 10 desktop has shrunk to 1024x768 and is centred on the screen with a massive black border all around. The guest hasn't crashed and Host+F twice restores the screen to the full size but all my open applications have been squashed too, so I have to resize them.

I asked this question on the forums and it was suggested I log the problem here with logs.

When I originally reported the issue in the forums I was at home using my Windows 7 desktop but it's just occurred while I'm away running the VM on my laptop (Win 10 Home host).

Host: Windows 10 Home (Build 1903)
Guest: Windows 10 Pro (Build 1903)",Iain Waddell
19087,"Crash with ExceptionCode=0xc0000005 on ""VMSVGA FIFO""",Windows,VirtualBox 6.0.14,2019-11-15T10:08:14Z,2019-11-16T02:59:14Z,2019-11-16T02:59:14Z,"Host is windows 10/
2 VMs launched. Virtualbox freezes ""1 VirtualBox GUI is frozen.png"". Correctly completing work in the 1st guest Windows XP. Error ""2 VirtualBoxCrush.png"" pops up and the 2nd guest Windows 10 disappears.
There is also a failure of the keyboard and mouse on the fault of the windows  10 host computer when connected to it via the RDP.

It started this week after updating the virtual box to 6.0.14 r133895 (Qt5.6.2), but the Windows 10 host was also updated.",Дмитро
19085,Error with Windows 10 Enterprise 1903 build 18362.476 and VirtualBox v6.0.14 error,Windows,VirtualBox 6.0.14,2019-11-14T04:21:10Z,2019-11-15T05:24:01Z,2019-11-15T05:24:01Z,"my MS Windows is in Portuguese-BR!
my user Windows: ""PCuserWin"" -> is a administrator, per default!
Then, all my software are installed in this profile!
My user Administrator, stay disabled, per default!

I use VirtualBox since v5. My pc is:
- CPU Intel i7 4770K
- RAM 8GB Corsair Vengeance
- VGA Gigabyte nVidia GTX650 Ti Boost 2GB
- SSD 120GB Corsair to Operating System MSWindows
- HDD 1TB free to my virtual machines (normally 2 or 3 for test, and later I delete it)

My antivirus Kaspersky Internet Security v2020, never got in the way of installing VirtualBox or virtual machines!

I do not see any changes on my computer so this new error appears!
-------------------

Sometimes i had this problem when try install ""Package"" as normal user (no Admin) as always:
- all my downloads stay (always) in Drive ""D"" (include VirtualBox + Package)
- my Drive ""C"" only MSWindows, Kaspersky, RAD Studio 10.3.2, and other utilities -> normally, only apps to work! No games!

to avoid this error, I try install it using run VirtualBox app ""As Administrator"", or, I copy the file ""Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack"" to into my folder VirtualBox on Disk""C"". then, works! 


----------- Screen error #1: Fail on install Extension Package  -----------
Falha ao instalar o Pacote de Extensões D:/Downloads/__Utils/VirtualBox/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-1644' -&gt; 'C:\MeusProgs\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


rcExit=1.

Código de Resultado: E_FAIL (0x80004005)
Componente: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}
---------------------------------


Now, using same MSWindows 1903 build 18362.476, i had another error when trying create new VM to test new ISO MSWindows 1909 (downloaded from Microsoft directly):

---------- Screen error #2: Fail to the open a session to ... ----------
Falha ao abrir uma sessão para a máquina virtual Windows101909. <-- my VM

 (VERR_NEM_MISSING_KERNEL_API).

VT-x is not available (VERR_VMX_NO_VMX).

Código de Resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
--------------------------------------------------------------

But my ""VIRTUALIZATION"" always is activated on BIOS and MSWindows, since always!  I never had this error before.

I always create my VM with 2GB and 1 (or 2 cpu virtual), and 80GB disk.
I never use 2 VM in same time.
Later test the new system, I delete my VM. Then, i have many disk space!

",Emailx45
19079,BSOD после обновления с 5.1.22 до версии 6.0.14,Windows,VirtualBox 6.0.14,2019-11-11T12:31:07Z,2019-11-14T08:27:10Z,2019-11-14T08:27:10Z,"После обновления VirtualBox с версии 5.1.22 до версии 6.0.14 на Windows 7_x64 не получается запустить ни одну из ранее установленных виртуальных машин, т.к. постоянно выскакивает BSOD. VM установлена не на системном диске.",Назаров Андрей Валерьевич
19072,VirtualBox 6.0.14 Oracle VM VirtualBox Extension Pack unable to install,all,VirtualBox 6.0.14,2019-11-08T13:44:40Z,2019-11-12T09:09:08Z,2019-11-12T09:09:08Z,"Upgrade of VirtualBox from 6.0.12 to 6.0.14 was successful but an issue happened during the upgrade of Extension Pack.

Fix: Manual removing all files under ''C:\Program Files\Oracle\VirtualBox\ExtensionPacks''

Error
''Failed to install the Extension Pack C:/Users/i314866/Downloads/Oracle_VM_VirtualBox_Extension_Pack-6.0.14.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Failed to rename the temporary directory to the final one: VERR_ACCESS_DENIED ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152' -&gt; 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack')


VBoxExtPackHelperApp.exe: error: Failed to delete the temporary extension pack directory: VERR_DIR_NOT_EMPTY ('C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack-_-inst-7152')


rcExit=1.

Result Code: E_FAIL (0x80004005)
Component: ExtPackManagerWrap
Interface: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

''",Lukáš Viktora
19078,"NT4 Guest: Weirdness with ""Enable Nested VT-x/AMD-V"" checkbox in guest settings",Windows,VirtualBox 6.0.14,2019-11-11T06:26:29Z,2019-11-11T06:26:29Z,2019-11-11T06:26:29Z,"I have a good working install of Windows NT4 Server that I toy around with every few months.  I am not sure when this issue began, but I am assuming during 6.x.

From a known good snapshot, I can boot into NT4 successfully and login as the administrator account.  However, when I reboot the guest, the *next* reboot will fail with this error message:

    HAL: MPS MP Structure not found[[BR]]
    HAL: No MPS Table Found.[[BR]]
    
    HAL: This HAL.DLL requires an MPS version 1.1 system[[BR]]
    Replace HAL.DLL with the correct hal for this system[[BR]]
    The system is halting

The solution that I found is to go into the guest's settings, and under System --> Processor, enable OR disable the ""Enable Nested VT-x/AMD-V"" checkbox.  That means, if the checkbox is currently checked, uncheck it.  If it is not currently checked, check it.  Save and then exit the settings dialog.

After this, the next boot will work fine.  But!  The next time you restart the guest, you must toggle the state of that checkbox again before the guest will successfully boot.

Definitely one of the weirder bugs I've ran into.  I'll attach a screenshot of the HAL message, but I'm not sure what else the VBox developers might need to figure this one out.",kumba
19064,No animation on Windows 7 start button,Windows,VirtualBox 6.0.14,2019-11-05T16:34:19Z,2019-11-05T19:51:04Z,2019-11-05T19:51:04Z,"There is no more an animation if the mouse cursor hovers over the start button (only windows 7). 

If then clicked on the start button, the ""hover""-design appears (It should be the ""clicked""-design). 

And if you then leave the start menu (and ""close"" it), the start-button keeps its ""hover""-design.",Timo
19056,Faulty cursor in 32 bit XP VM,Windows,VirtualBox 6.0.14,2019-10-31T22:13:32Z,2019-10-31T23:58:07Z,2019-10-31T23:58:07Z,"I recently downloaded 6.0.14 for windows clients in hopes that it would fix the cursor problem that I've experienced in updates since 5.2.34. I am running a 32 bit XP VM which I use to run an older drafting program, Drafix CAD. On version 5.2.34 and earlier the cursor displayed properly both on the desktop and within the CAD program. Later updates show an enlarged cursor (regardless of pointer settings in control panel) on both the desktop and within the program. This enlarged cursor is problematic in the CAD program because it creates an offset between where the cursor appears to be and where it actually is which renders the CAD program basically useless. To try to eliminate this problem in 6.0.14 I turned off 3D acceleration, 2D video acceleration, and have tried both VMVGA and VMSVGA modes. Nothing returns the cursor to normal appearance. My workaround is to reinstall 5.2.34. Works fine so I won't be accepting any updates.  ",Woodsaregood
19054,No USB Device on Windows 7 guest,Windows,VirtualBox 6.0.14,2019-10-31T14:02:05Z,2019-10-31T16:15:06Z,2019-10-31T16:15:06Z,"Host Win10 (64bit)
Guest Win7 (64bit)

After upgrading to 6.0.14 there is no USB device shown anymore in USB List. ",cyberoner
19055,Hang in VM after upgrade to 6.0.14,Linux,VirtualBox 6.0.14,2019-10-31T15:32:43Z,2019-10-31T15:38:58Z,2019-10-31T15:38:58Z,"My Ubuntu VM hangs after detecting the network card. This started after updating to 6.0.14, and has vanished when I stepped back to 6.0.12.
Network setup on the VM is Bridged to Intel Ethernet Connection (4)I219-V with Allow All and cable connected. ",hobson42
19040,ubuntu 16 guest aborted when restoring,Linux,VirtualBox 6.0.14,2019-10-23T01:03:01Z,2019-10-23T01:03:01Z,2019-10-23T01:03:01Z,"How to produce:
1. Open VirtualBox;
2. select the saved machine ""ubuntu-16"", and click ""start"" button;
3. New vm window comes up and then loading is processing;
4. when the progress bar almost finished the vm disappeared and aborted 

Host OS: Windows 7 SP1
I've been experienced this aborted situation since upgrade my virtualbox was upgraded to version 6, hope the information I've provided is helpful.",buffy
19035,Linux client can't use second monitor via Remote Desktop,Linux,VirtualBox 6.0.14,2019-10-21T10:15:07Z,2019-10-22T11:32:34Z,2019-10-22T11:32:34Z,"I have the following setup, which I give in full here in case it has some influence in the problem:
The physical workstation ""One"" is a Devuan/XFCE based Laptop with two external 1920x1080 monitors connected.
The physical workstation ""Two"" is a Windows 10 box somewhere far away.

On ""One"" I have a virtualbox 6.0.14 with a Windows 10 guest ""v1"" running. ""v1"" uses the two external monitors in full screen display  and connects via VPN and Remote Desktop Connection to ""Two"".

On ""Two"" I have a virtualbox 6.0.14 with a Devuan XFCE MV ""v2"" running. ""v2 is supposed to use both displays of the remote desktop connection, which are rendered on the two external monitors of ""One"".

What happens is that I do have both full screen displays of ""Two"" on the external monitors of ""One"" used by ""v1"", but ""v2"" only ever opens monitor 1. I did manage to get a small window for the second display once or twice by playing around with the view parameters for a long time, but as soon as I try to maximize it the window folds to never appear again. The ""Display"" settings inside ""v2"" only show me ""Virtual1"" monitor available.

I have attached the two screenshots made from ""One"". ""screen1"" shows the display of ""v2"" inside the remote desktop from ""v1"" to ""Two"", so on top there is the menubar from ""v1"" (in Spanish), at the bottom the menu bar from ""v2"" (in German). Please ignore the content of the target desktop. ""screen2"" shows the empty second monitor from ""Two"" via remote desktop from ""v1"", so it only has the ""v1"" menu bar on top and the windows background of ""Two"". What I expected to see there was the second full screen display of ""v2"", because that is the machine I di the actual work on, so I need both displays there.


Log from v2 attached, as soon as I find out how attaching files work.

",nubaltec
19024,Virtualbox Installer launches Virtualbox with non-quoted command line - Windows hosts,all,VirtualBox 6.0.14,2019-10-16T18:16:34Z,2019-10-16T18:16:34Z,2019-10-16T18:16:34Z,"At the end of the Virtualbox installer, the option is presented by default to start the main Virtualbox window. If there is a program called 'program' or 'program.exe' in the C drive root, that program launches instead of the main Virtualbox window.

This issue is ultimately a Windows issue, but the Virtualbox installer is run with admin privileges (asks for UAC elevate during the install, or is started right-click-run-as-admin), and the subsequent main Virtualbox windows is also launched with admin privileges. (Running the main Virtualbox window with admin privileges is required to install the Extension pack, for example.)

If C:\program or C:\program.exe exists, then 'program' is launched with admin privileges at the end of the Virtualbox installer, instead of the main Virtualbox window.

Is it possible to put double quotes around the command line to launch the main Virtualbox window in the MSI installer? Double-quotes will not launch C:\program or C:\program.exe.

See https://forums.virtualbox.org/viewtopic.php?f=6&t=95156",scottgus1
19302,Mouse support fails,Linux,VirtualBox 6.0.16,2020-02-12T13:48:54Z,2021-08-13T06:17:00Z,2021-08-13T06:17:00Z,"I've come across this really odd bug with my guest Kali Linux (2019.2, 2019.4 and 2020.1; all had the latest guest additions installed), where mouse support randomly fails.

I can move the cursor. The keyboard works perfectly fine but I can't click anything with the mouse. The really odd thing is, that if I use the menu key (or application key) on the keyboard, the targeted application opens the right-click menu. In this menu, the mouse works again as expected. I've captured a short clip showing the issue. Mouse clicks are not shown, but I've clicked on every button/menu in the clip, when I hover over them.",GarlicCheese
19308,"Networking mode ""NAT Network"" shows very poor throughput",Linux,VirtualBox 6.0.16,2020-02-13T12:47:40Z,2020-02-13T12:47:40Z,2020-02-13T12:47:40Z,"Information about my environment:

Physical Host: Windows 10
VBox version: 6.0.16

Guest VM: Debian 9 Linux, 64 bit
Guest additions: 6.0.16.
Networking mode: NAT Network



Use case and problem description: 
I have a Linux guest on Win10 host, using vbox 6.0.16 guest additions. The VM rsync files from a vboxsf shared folder to a remote host via SSH. The network is 
plenty fast (modern 802.11n network - not used for anything else) on which I can easily achieve > 50 MiB/s (measured by iperf) from the host to the remote 
server. However, when I go from guest to remote server, it maxes out at about 200kiB/s

I have checked via atop and htop that CPU is not a bottleneck on neither client nor server. And the physical network is obviously not the bottleneck...
I have verified that I can both read and write files from the vboxsf share plenty fast as well.



I just tried plain NAT as networking mode and that works MUCH better. Now it is several MiBs per second. So it must be something to do with NAT network


So I guess there must be a problem in how networking is implemented in NAT Network compared to plain NAT that causes the slowdown.

",tdn
19283,VirtualBox stuck zoomed in on Windows 10,Linux,VirtualBox 6.0.16,2020-01-31T20:37:42Z,2020-01-31T20:37:42Z,2020-01-31T20:37:42Z,"Hello, 
I am running virtual box through vagrant on Windows 10. I cannot perform many functions on VirtualBox that I need to for school and work projects because the screen is zoomed in and I can't click or see many of the things I need to. I have tried some of the recommended fixes mentioned online at stackexchange and others but none have worked. Please let me know what I can do to make this work.

Thank you!",BallsMahoney
19278,"Vboxmanage.exe fails when using ""quoted\folder\path\to""vboxmanage.exe",all,VirtualBox 6.0.16,2020-01-29T13:51:09Z,2020-01-29T13:51:09Z,2020-01-29T13:51:09Z,"On a Windows 7 host running 5.2.28, and Windows 10 hosts running 6.0.14, and 6.1.2, this vboxmanage command line:


{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""
}}}


finishes correctly.

This command line:


{{{
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""
}}}


errors out with the vboxmanage full help printout and this error:


{{{
Syntax error: Invalid command '\vboxmanage.exe'
}}}


Note the difference in the command lines:

{{{
""C:\Program Files\Oracle\VirtualBox\vboxmanage.exe"" showvminfo ""<vmname>""  <-- good
""C:\Program Files\Oracle\VirtualBox""\vboxmanage.exe showvminfo ""<vmname>""  <-- bad
}}}

The difference is in where the double-quotes are put after the space-named folder path.
The second command line was made by drag-n-dropping the Virtualbox install folder onto the command window, then adding the backslash and vboxmanage.exe.

These Windows command lines all work: (""calc.exe was copied to the ""test dir"" folder, ""InSpectre.exe"" is a stand-alone 3rd-party exe.)


{{{
""c:\users\snc\test dir\calc.exe""
""c:\users\snc\test dir""\calc.exe
""c:\users\snc\test dir\inspectre.exe""
""c:\users\snc\test dir""\inspectre.exe
}}}


Note that either with the ""\ or \..."", the command lines work.

It appears that Vboxmanage.exe does not parse the command line correctly. ",scottgus1
19274,WindowsHost - GUI - Incorrect VM deleted,all,VirtualBox 6.0.16,2020-01-28T12:35:12Z,2020-01-28T12:35:12Z,2020-01-28T12:35:12Z,"When removing a VM (by selecting a VM in the list, right clicking... Remove), sometimes the wrong VM is deleted resulting in the VM list getting out of sync. e.g. I removed a Linux VM, but discovered it actually destroyed a Windows VM (the Windows VM was listed above the Linux VM in the GUI list). The resulting visible VM list was actually correct (i.e. the Linux one disappeared off the screen list) but the Windows VM folder was corrupted ending up as a Linux VM). i.e. double clicking the Windows VM entry launched Linux. This fault has been in previous releases.",SolidDude
19273,WindowsHost CloneVM Incorrect VM Filename generated,all,VirtualBox 6.0.16,2020-01-28T12:17:46Z,2020-01-28T12:17:46Z,2020-01-28T12:17:46Z,"When Cloning a VM from the Windows GUI, (i.e. select a VM, right-click... Clone), it prompts you to enter a new name for the cloned VM. After generating the new clone VM inspection of the files produced show the VM file is based on the filename of the cloned VM and not that of the 'new' VMs name entered previously. This can lead to confusion about which file goes with which VM (only the containing folders differentiate them). This feature has been present in previous releases.",SolidDude
19266,Shared Clipboard not working bi-directionally,Windows,VirtualBox 6.0.16,2020-01-25T09:17:59Z,2020-01-25T09:17:59Z,2020-01-25T09:17:59Z,"Hi, I am running a Windows XP SP3 VM on a Windows 10 64bit Host machine and. I am struggling to make the shared clipboard functionality work. The actual shared clipboard function doesn't work at all but i can drag and drop files from the host machine to the guest machine. The other way round this doesn't work. Am attaching a log file. Would really appreciate any advice on this.",alexKite
19250,processor execution cap is broken for single cpu vms,other,VirtualBox 6.0.16,2020-01-21T19:37:35Z,2020-01-21T19:37:35Z,2020-01-21T19:37:35Z,"build a single cpu vm
set exec cap at 70%
host only ever uses 35% (as if 70% has been split between 2 cpus)

workaround create a dual cpu vm
set exec cap at 50%
host then uses 60% cpu (well it better than 35%)",clive darra
19396,Latest version (6.0.18) causes issues with DNS and VPN,Windows,VirtualBox 6.0.18,2020-03-12T12:52:09Z,2020-03-12T12:55:44Z,2020-03-12T12:55:44Z,"After I upgraded from 6.0.16 to 6.0.18 I started having network issues. After some futzing around and help from a friend I found a work around that forced me to be doing ipconfig /renew after connecting or disconnecting from our company's VPN. Just this morning I went back to 6.0.16 and the problem is gone which pretty much proves the latest version has broken something.

My host is Win 10 and my guest is Win 7.",WayneB64
19378,VirtualBox crashes with VMSVGA and 3D,Windows,VirtualBox 6.0.18,2020-03-04T20:30:47Z,2020-03-04T20:30:47Z,2020-03-04T20:30:47Z,"I'm using '''Win10''' host with newly installed '''Ubuntu 20.00''' guest on. 
[[BR]]

After login open ''Brave'' browser, open some tabs and close it. It will crash in 90% of cases. It also occurs with ''Chrome'' browser, but less often and predictable. They are both based on ''Chromium/V8''.
[[BR]]

Crash happens only with the new '''VMSVGA''' driver and enabled '''3D acceleration'''.
[[BR]]

I was having issues also with 6.1.2 and 6.1.4 builds, but have downgraded because 3D is not supported in VBoxSVGA mode. 
[[BR]]",mihaur
18356,Guest machines randomly freezing on Windows,Windows,VirtualBox 6.0.2,2019-01-23T20:17:13Z,2021-03-04T18:04:52Z,2021-03-04T18:04:52Z,"Guest machines are just freezing after an random number of minutes. Initially the missing guest heartbeat is just returning an error and resetting the machine. I changed the HeartbeatInterval in order to get the actual cause of this and the message before freezing is:

00:47:36.160501 AHCI#0: Port 0 reset
00:47:36.161610 VD#0: Cancelling all active requests
00:47:36.165047 AHCI#0: Port 0 reset
00:47:36.166097 VD#0: Cancelling all active requests
00:47:36.171464 AHCI#0: Port 0 reset
00:47:36.172509 VD#0: Cancelling all active requests
00:47:36.178255 AHCI#0: Port 0 reset

Same behavior on some version 5, on version 6.0.2 (latest at the time of bug recording) and 6.0.3 r128259. Logs captured from version 6.0.3.",serbanforyou
18547,"Host Win 10, Guest win XP works fine with 5.2.22. Win XP crash wtih 6.02 or higher",Windows,VirtualBox 6.0.2,2019-04-06T06:29:05Z,2019-04-12T22:52:50Z,2019-04-12T22:52:50Z,,Trehin
18339,VBox 6 unresponsive with ultrawide display,Windows,VirtualBox 6.0.2,2019-01-19T21:31:45Z,2019-03-02T06:28:21Z,2019-03-02T06:28:21Z,"11520x2160, dual Nvidia 1080's. This display size works fine with VBox 5, upgraded to Vbox 6 and VM becomes unresponsive until I reduce the screen size back to 4k or lower. Using the VboxSVGA driver. Windows 10",jamesf007
18335,Deleting a snapshot shows an incorrect estimated time (14714 days 5 hours),Windows,VirtualBox 6.0.2,2019-01-19T12:42:53Z,2019-02-13T07:13:41Z,2019-02-13T07:13:41Z,"After upgrading VirtualBox to version 6.0.0, when deleting a snapshot, the same time is always displayed (14714 days 5 hours), even if the snapshot deletion only takes a few minutes.
The problem also exists in version 6.0.2.
See also:
https://forums.virtualbox.org/viewtopic.php?f=8&t=90855
https://forums.virtualbox.org/viewtopic.php?f=15&t=90741
",MisVin
18353,Linux Mint 18.x VM Multimedia/Graphics Broken By 6.0.2 Guest Additions Install,Linux,VirtualBox 6.0.2,2019-01-23T14:22:47Z,2019-02-05T16:42:36Z,2019-02-05T16:42:36Z,"After installing the 6.0.2 guest additions on Linux Mint Cinnamon the following problems were observed:

-The screen lock window does not appear when the computer is locked after a period of inactivity, and the desktop is visible, but inaccessible to mouse clicks. The password can still be entered and the VM will wake up and return to the normal desktop.

-VLC media player 2.2.2 Weatherwax crashes with the error:
""corrupt module: /usr/lib/vlc/plugins/gui/libqt4_plugin.so""

-Web browser based video streams from FireFox fail to run or stop after rendering 100 or less frames

-Media Player does not render its window frame properly with respect to other windows, does not display menu contents, and freezes when playing content if launched as the default multimedia app.

-There may be many other graphical rendering and multimedia anomalies. So far the above were observed from a limited amount of troubleshooting time.

The environment(s) in which these problems were observed is:

o Linux Mint Cinnamon 18.2 with multimedia bundle accepted during install
o Linux Mint Cinnamon 18.3 with multimedia bundle accepted during install
o Running in VirtualBox 6.0.2 from Windows 10 with guest additions added to the VM (updated from 6.0.0 recently)
o VM configured with:
  - 2 Processors, VT-x/AMD-V, Nested Paging, PAE/NX, KVM Paravirtualization
  - >= 2 Gb RAM
  - >= 20 Gb HDD
  - 64 MB Video Memory
  - VBoxVGA Graphics Controller

The above issues did not exist before upgrading from VirtualBox 6.0.0 to 6.0.2. To confirm that the issue is caused by the guest additions, we created a new VM in 6.0.2 with the configuration described above and loaded a new install of Linux Mint Cinnamon 18.3, accepting the default Mint multimedia bundle during the install process. Before adding the guest additions, testing shows that none of the problems above were present. We then added the 6.0.2 guest additions and then re-tested and observed all the issues described above. Furthermore, we have confirmed that if the Graphics Controller setting on the VMs is changed to VMSVGA in 6.0.2 then the observed problems go away.
",cjrussell1962
18359,Wrong driver in the Windows 7 guest after the switch to the VBox SVGA adapter.,Windows,VirtualBox 6.0.2,2019-01-25T07:13:14Z,2019-02-05T07:25:49Z,2019-02-05T07:25:49Z,"I have a Windows 7 guest on the Windows 8 host. Because it’s new, after the test with an old VGA adapter I tested the new VBox SVGA adapter. After the first start the new device was automatically detected and installed. I have had to reboot the guest and after the reboot the new driver was active and I even had the Windows Aero activated.

Because of the problem I already posted in the forum (if I activate the experimental WDDM driver, my only Java desktop program, the TV Browser, has big skinning issues and becomes unusable) I usually install a regular driver with non-experimental Direct3D support only (Virtual Box Graphics Adapter). I have to boot my guest in safe mode for installation because of this. But time after time I test the experimental one. So after the reboot I found that the device name is “Virtual Box Graphics Adapter for Windows Vista and 7” now and beside the working Aero I also have the already mentioned issues in my Java program. More important: the driver version is 5.2.1 and it’s from the end of the year 2017. This was probably the last time I tested the experimental Aero supported drivers.

So I have to boot in safe mode once again, re-install the guest additions, but this time I answered “no” in the dialog about installing the regular Direct3D drivers and not the experimental WDDM ones. It looks for me, that by activating SVGA adapter the other device is simulated and under Windows 7 and Vista the Aero WDDM driver is used. And if one doesn’t install or re-install the additions explicitly, the wrong version of the drivers are used.

This was my experience from my test of original 6.0 release from December 2018. As I tested the 6.0.2 release, the new device was also detected and the driver was also installed. But this was probably once again not the newest one, so after the reboot I had the BSOD on the boot, more then once. Therefore, I have to repeat the additions installation and this way probably renew the Aero WDDM driver as well. After that the BSOD was gone, but I got the same situation with Aero and Java program as I already had before.",boxer01
18348,VBoxGuestAdditions 6.0.2 failed with OpenArena game (ioquake3/renderer_opengl1_x86_64.so),Linux,VirtualBox 6.0.2,2019-01-22T14:29:14Z,2019-01-29T16:16:36Z,2019-01-29T16:16:36Z,"System environment:
Host OS: Windows8 Pro 64 bit (all updates)
Guest OS: Debian 8.11 (kernel 3.16.0-4, all updates from stable branch 8.11)

After update from 6.0.0 to 6.0.2 and apply VBoxGuestAdditions.iso - game OpenArena cant be run with this error text:

""Trying to load ""renderer_opengl1_x86_64.so"" from ""/usr/lib/ioquake3""...
Trying to load ""renderer_opengl1_x86_64.so"" from ""/usr/lib/openarena""...
Loading ""renderer_opengl1_x86_64.so"" failed
failed:
""Failed loading /usr/lib/openarena/renderer_opengl1_x86_64.so: /usr/lib/openarena/renderer_opengl1_x86_64.so: cannot open shared object file: No such file or directory""
Failed to load renderer""

But file in /usr/lib/ioquake3/renderer_opengl1_x86_64.so is exist, and if downgrade GuestAddition to 6.0.0 OpenArena then can be run again.

But generally 3d acceleration works, AlienArena succefully run and play with fast fps.",ilyalesnoi
18375,Red Hat Linux 7.6 VM kernel panic running under Windows 10 host,Linux,VirtualBox 6.0.2,2019-01-28T17:28:55Z,2019-01-28T17:28:55Z,2019-01-28T17:28:55Z,"When I try running a Red Hat 7.6 VM under Windows 10 using Oracle VirtualBox 6.0.0 or 6.0.2 I get a Kernel Panic.

If the guest is configured for Enable I/O APIC unchecked and so 1 CPU I get a panic in: __native_set_fixmap
If the guest is configured for 4 CPUs I get a panic in: __lookup_address_in_pgd

I have Hyper-V disabled in Windows Features. I have Windows Hypervisor Platform enabled (as without that I get errors reported in my VirtualBox config and can't even get the VM to start).

Prior to a reboot on Jan 17th 2019 I'd not had a problem. After the reboot Windows Hypervisor Platform was disabled and that stopped the VM running at all. When I enabled that setting I got the kernel panic. I tried reinstalling the Red Hat 7.6 VM, but that also suffered from the kernel panic during the install.

Between the previous reboot and the Jan 17th reboot the only things installed on my machine were:

* Dell SupportAssistAgent 3.1.0.142
* Adobe Acrobat Reader DC (19.101.20069) 

I tried uninstalling the Dell utility. However it did not resolve the issue.


Attached is a log from a startup with 4 CPUs.",David Castell
18332,Windows 10 Guest additions 6.0.2 scramble drive mappings into shared folders,Windows,VirtualBox 6.0.2,2019-01-19T02:50:26Z,2019-01-20T02:17:18Z,2019-01-20T02:17:18Z,"Running Win 10 Pro (October 2018 Update, build 17763) on both host and guests, updated host from 5.2.22 to 6.0.2 with 6.0.2 guest additions.  Upgrading guest VMs to 6.02 guest additions scrambled the mapped drives into shared folders.  The windows drive mappings no longer corresponded to the originally assigned shared folders,.  Rolling back to a previous version of the VM (which still had 5.2.22 guest additions installed restored correct behavior.  

FWIW:
  net use v: \\vboxsrv\bbj5-c /persistent:yes
  net use w: \\vboxsrv\data   /persistent:yes
  net use x: \\vboxsrv\bbj5-e /persistent:yes
  net use y: \\vboxsrv\a      /persistent:yes
  net use z: \\vboxsrv\aa     /persistent:yes


Reproduced this behavior on a second (and different) vin 10 pro vm: changing nothing other than upgrading guest additions from 5.2.22 to 6.0.2 corrupted the mappings into shared folders.  

two logs
w10p-1-2019-01-18-21-21-45.log  scrambled VM 6.02 guest additions
w10p-1-2019-01-18-21-41-13.log	correctly mapped VM 5.2.22 guest additions					",BBoyar
18321,Virtual Machine has terminated unexpectedly.,Windows,VirtualBox 6.0.2,2019-01-17T07:01:18Z,2019-01-19T21:14:17Z,2019-01-19T21:14:17Z,"The virtual machine 'Windows 10 Test' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\Program Files (x86)\Oracle\VirtualBox VMs\Windows 10 Test\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
",Excaluburjmk
18326,Distorted audio on Windows guest after upgrade,Windows,VirtualBox 6.0.2,2019-01-17T19:46:41Z,2019-01-17T19:46:41Z,2019-01-17T19:46:41Z,"I upgraded my virtualbox installation from 5.2.22 to 6.0.2.

Now, the audio of one of my guests (Windows XP - 32 bits) is completely distorted. Actualy sometimes the sound plays nicely, sometimes distorted, and sometimes it didn't play at all.

I also updated the guest additions, trying to fix the problem, but no luck.

Host: Windows 10 (1809)
 ",rdweb
19660,Guest Crashes with in a minutes,Windows,VirtualBox 6.0.20,2020-06-11T18:27:12Z,2020-06-11T18:27:12Z,2020-06-11T18:27:12Z,After just started the virtual box manager. if we wait like 2 or 3 minutes  the mouse becomes unresponsive and eventually i cant open anything. The only thing i can do is close the virtual box directly and restart it and its happening often.,k00000
20164,Error while trying to use VM for SAS University Studio,other,VirtualBox 6.0.22,2021-01-30T04:31:00Z,2021-01-30T04:31:00Z,2021-01-30T04:31:00Z,"This is the description of the error

Fallo al abrir una sesión para la máquina virtual SAS University Edition.

The virtual machine 'SAS University Edition' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Eduardo Sandoval\VirtualBox VMs\SAS University Edition\Logs\VBoxHardening.log'.

Código resultado: E_FAIL (0x80004005)
Componente: MachineWrap
Interfaz: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
",EDUARDO SANDOVAL HERNANDEZ
18563,Drag and drop fails from guest to host,Linux,VirtualBox 6.0.4,2019-04-16T19:56:48Z,2022-02-04T10:49:50Z,2022-02-04T10:49:50Z,"Hello,

Drag and drop from guest (Ubuntu 18.04) to host (Windows 10) fails : the file is not created on host and following message box appears on guest : ""Dropping data...0%"" but stays at 0% undefinitely.
(drag and drop is working perfectly from host to guest).

Please find attached host and guest log files.

Thank you very much for your help.

Damien KLOTZ",damienklotz
20635,The USB device disappears from the host but doesn't appear on the guest,Windows,VirtualBox 6.0.4,2021-10-25T10:41:25Z,2021-10-25T10:41:25Z,2021-10-25T10:41:25Z,,LAWGR
18522,Audio transmitted with the VBox Remote Display server sounds chopped and pitched,Linux,VirtualBox 6.0.4,2019-03-26T11:03:16Z,2020-11-18T11:30:05Z,2020-11-18T11:30:05Z,"Audio generated in a Linux guest on a Windows 7 host can be transmitted via the VBox Remote Display server, and is received with a Windows 10 Remote Desktop client. (This was not possible in earlier versions of VBox, I believe).
However, the sound that is played back on the Remote Desktop client (Windows 10) sounds 'chopped'. Moreover, the sound is seemingly transmitted or played back with a wrong samplerate, i.e. the pitch is considerably higher than of the sound on the Linux guest.
",EsbenS
18404,No Audio on Linux Guest with Windows 10 x64 host when changing output device in host,Linux,VirtualBox 6.0.4,2019-02-01T10:49:39Z,2020-11-03T00:15:01Z,2020-11-03T00:15:01Z,"Audio in the linux guest completely hangs, after changing output audio device in the windows host (plugging in/out headphones)
Tried with both AC97 and HDAudio device under Manjaro.
Started with 6.0.4 comming from 6.0.2
",BartHandels
19338,Virtualbox randomly overwrote current state.,Linux,VirtualBox 6.0.4,2020-02-23T15:28:32Z,2020-02-23T15:28:32Z,2020-02-23T15:28:32Z,"I have a 'working' snapshot on my CentOS vm only.
When I just closed the window, it asked whether to turn off, save the state, or restore.
As soon as I selected 'save the current state', it immediately overwrote the current state with the snapshot and I lost a lot (a LOT) of work and data.
Please fix this before other people lose information.",K.W.555
18539,Serial Interface doesn´t work correctly,Windows,VirtualBox 6.0.4,2019-04-03T06:04:35Z,2020-01-20T08:53:09Z,2020-01-20T08:53:09Z,"Hi,

I installed VB 6.0.4 (Host W10 17763.379) and I use an old equiqment to transfer data to a virtual XP using the serial interface. I am using Port 1, COM1, Host-Interface, Pipe/Socket aktivated, Adresse COM1.
The transfer starts but after a fewsecond it terminats.
If I downgrad to VB 5.2.26 it work correctly.

Sorry about my bad enlish.

Best regards
Jürgen",motog
18390,'memory could not be read' crash in Linux guest / Windows host 6.02 and 6.04,Linux,VirtualBox 6.0.4,2019-01-30T17:32:41Z,2019-08-21T13:09:11Z,2019-08-21T13:09:11Z,"I am running a Linux guest (Mint Virtualbox image downloaded from www.osboxes.org) in a Windows 10 host.

I started running this guest under VirtualBox 6.0.2 and experienced this crash. A couple of days later I noticed 6.0.4 was available and tried updating to that to see whether it had been fixed, but the crash is still occurring and has happened 3x today, so it is fairly regular.

The guest isn't running too much - it's being used as a dev box with Docker (postgres / pgAdmin) and VS Code. There doesn't seem to be a particular pattern in what I'm doing before a crash. The VM doesn't have many modifications to base settings - 2 CPU, bidir clipboard and 2 networks (NAT and Host Only).

The error message is:
'The instruction at 0x00007FFC612061E3 referenced memory at 0x00000000000010. The memory could not be read'

I have attached the output from VBoxBugReport",MattA
18381,Certain sounds seem to crash OS/2 guest,other,VirtualBox 6.0.4,2019-01-29T06:24:16Z,2019-08-01T16:01:43Z,2019-08-01T16:01:43Z,"I don't know if this defect is new to version 6, but I've just noticed that generating some sounds crashes the guest. In particular generating system error sound in rapid succession does that. For example trying to delete non-existing characters in system editor. The guest will lock up with sometimes partial error sound playing in the loop and the mouse cursor will disappear when over the guest window. Selecting machine close action will change the window to not responding state (message in the title bar) and the subsequently clicking on the close button will cause the guest state to show aborted.
",Rafcio
18554,systemd startup script not updated during guest additions install,Linux,VirtualBox 6.0.4,2019-04-09T21:12:47Z,2019-07-29T12:30:00Z,2019-07-29T12:30:00Z,"Environment:[[BR]]
Host: Windows 10 Enterprise[[BR]]
Guest: Linux Mint 19.1[[BR]]

I upgraded my host Virtualbox install from version 5.2.26 to 6.0.4[[BR]]
 
After booting the Linux Mint guest I was prompted to update the virtualbox guest additions.

This appears to install correctly, however when rebooting the guest, vbox shared folders don't appear to mount.

I eventually traced the issue down to the systemd startup script located in /etc/systemd/system/vboxadd-service.service 

When querying the status of the service startup after updating to guest additions version 6.0.4 this error is shown:

Apr 09 14:06:21 Mint-19 systemd[4423]: vboxadd-service.service: Failed at step EXEC spawning /opt/VBoxGuestAdditions-5.2.26/init/vboxadd-service: No such file or directory


I then manually edited the /etc/systemd/system/vboxadd-service.service service file and changed all entries for the path /opt/VBoxGuestAdditions-5.2.26/ to the path /opt/VBoxGuestAdditions-6.0.4/

I then reloaded systemd and started up the vboxadd-service successfully, with host shared folders mounting on the guest as expected",Chuck Donahue
18379,New OS/2 shared folders feature locks up the guest => Fixed in SVN,other,VirtualBox 6.0.4,2019-01-29T05:44:57Z,2019-05-19T05:04:23Z,2019-05-19T05:04:23Z,"After adding the new shared folders installable file system (VBoxSF.IFS) the guest GUI started to lock up just a second after VBoxService is executed from STARTUP.CMD. The mouse cursor still moves, so this is not a hard lock, but any interaction with GUI is impossible. The guest has to be powered off. The only workaround is to comment out the IFS statement in CONFIG.SYS.
",Rafcio
18508,Re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset,Linux,VirtualBox 6.0.4,2019-03-19T17:40:12Z,2019-04-18T19:06:00Z,2019-04-18T19:06:00Z,"System Information:
 * Host: Windows 10 Enterprise:
 * VirtualBox 6.0.4
 * VirtualBox Extension Pack 6.0.4
 * Guest: Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso)
 * VirtualBox Guest Additions: 6.0.4

Issue:
Upon installation of the VirtualBox Guest Additions 6.0.4 in Ubuntu 18.04.2 whenever you attempt to re-size VirtualBox Ubuntu Guest Window Causes Black Guest Screen Until Machine is Reset.

Steps to Reproduce:
I have tested this various times by performing the following:
1. Performing a fresh installation of Ubuntu 18.04.2 (ubuntu-18.04.2-desktop-amd64.iso) in VirtualBox with the following specifications:
 * Base Memory:  2048 MB (2 GB)
 * Processors: 2
 * Disk Space: 25 GB
 * Encryption Enabled: Yes (via the graphical Ubuntu installer prompts)

2. Navigating to “Devices -> Insert Guest Additions CD image”

3. Ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

4. Received the “Please install the gcc make perl packages from your distribution.” error message

5. Ran the “sudo apt-get update” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

6. Ran the “sudo apt-get install build-essential gcc make perl dkms” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

7. Ran the “reboot” command per https://askubuntu.com/questions/1035030/virtualbox-guest-additions-installation-problem

8. Re-ran the VirtualBox Guest Additions 6.0.4 Install via the “Run” pop-up button

9. Attempted to re-size the VirtualBox Ubuntu Guest Window which created a black Ubuntu Guest screen

10. Navigate to “Machine -> Reset”

If I ever re-attempted to re-size the VirtualBox Ubuntu Guest Window then it would re-create black Ubuntu Guest screen

To resolve this issue I would manual uninstall VirtualBox Guest Additions 6.0.4 from the Ubuntu Guest via the Command Line Interface (CLI) by performing the following steps:
 1) Ensure the “Guest Additions CD image” is still mounted to the Ubuntu Guest
 2) Run the “sudo sh /<USERNAME>/media/<VIRUTALBOXNAME>/VBoxLinuxAdditions.run uninstall” command

Outcome:
This issue needs to be resolved so that one can re-size the a Ubuntu 18.04.2+ Guest window",elyons
18560,Guest Windows hangs on startup with guest additions installed,Windows,VirtualBox 6.0.4,2019-04-15T08:17:20Z,2019-04-15T08:26:48Z,2019-04-15T08:26:48Z,"Host: Windows 10 1803 prof
Guest: Windows 7 x86 prof

Today I found that my old VM hangs on startup: black screen with ""Starting Windows"" message.
It doesn't connect to debugger (the debugging was turned on in the guest etc; in previous version of VirtualBox it worked).
I reinstalled Windows fresh in the guest.
It worked normally for a while.
I installed Guest Additions, rebooted and it hung.
Log file contains nothing interesting. The last message is:
00:05:11.555304 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
",iakovk
18460,Windows 10 guest works very slowly. This defect appeared with 6.0.x versions.,Windows,VirtualBox 6.0.4,2019-02-28T12:34:32Z,2019-04-15T01:51:59Z,2019-04-15T01:51:59Z,"Host: Win10 Pro x64 1809 17763.316

Guest: Win10 Pro x86 1809 17763.316

Guest works correctly on 5.2.24.

This defect with guest performance appeared with 6.0.x versions. 

I have tested on 6.0.5 revision 128999 test build because I previously created ticket #18319. The defect of serial ports has probably been fixed.  

There is a performance problem with the guest machine.
It utilizes 50% of host CPU (4 cores), the guest works very slowly.
The log file is full of 
""TM: Giving up catch-up attempt at a ""x"" ns lag; new total: ""y"" ns""

The guest has a delay in every operation. Sometimes it freezes and suddenly unfreezes, makes some operations and freezes again.

Guest virtual hard disc blinks red/green dot on status bar most of the time but host hard disc is not active.  
",Vonkaz
18472,VirtualBox no longer working after latest set of Windows 10 security patches.,Windows,VirtualBox 6.0.4,2019-03-05T02:54:29Z,2019-04-14T21:24:06Z,2019-04-14T21:24:06Z,"  I already submitted a Windows 10 feedback on this, as I'm not sure if it's a Windows 10 bug or a VirtualBox issue.
  
  After last week's Windows 10 Pro security patches, I can no longer start a VirtualBox virtual machine. On version 5.26, it gives the error
    verr_intnet_flt_if_not_found
when using a Windows 7 machine with a bridged wifi and Ethernet network. On
VirtualBox version 6.04, it just hangs forever at the ""Starting virtual machine"" screen, and I have to kill the process to cancel it.

    Even before this set of patches, it had run fine on 5.22 and 5.26, but 
6.04 would always hang after getting almost all the way through the boot process, up to starting most of the commands in the startup folder. That would happen from Windows 10 to Windows 7 or 10 VMs, and from Linux Ubuntu 18 to Windows 10 VMs with a similar set of startups, but not from Mac OSX to Windows 10; that one ran fine.",baseballbob
18556,I can´t able to start a virtual machine,other,VirtualBox 6.0.4,2019-04-10T18:05:20Z,2019-04-10T21:59:36Z,2019-04-10T21:59:36Z,"When I want to start a virtual machine whit Sas Univertisty, Virtual Box indicated me that is necessary to reinstall the program. I have done it several times, but the problem persists.  ",couttolenc
18540,PPTP not connecting from Windows guest in 6.0.4,Windows,VirtualBox 6.0.4,2019-04-03T09:00:09Z,2019-04-09T14:35:06Z,2019-04-09T14:35:06Z,"Hi,

Running Virtualbox 6.0.4 on Windows 10 x64 host, guests cannot connect to PPTP VPN. Tried with both Windows 7 x64 and Windows 10 32bits guests.

Connection hangs at ""checking username and password"" and finally disconnects with ""Error 734: The PPP Link Control Protocol Was Terminated""

Downgrade to 6.0.2 solves the issue, guests can connect again to PPTP.

Using bridged networking :-)

I will be happy to provide any log or test you may need.

PKX.",pkx232c
18546,If a rootFolder of a Novell eDir is Shared it can not be accessed,Windows,VirtualBox 6.0.4,2019-04-05T08:53:10Z,2019-04-05T08:53:10Z,2019-04-05T08:53:10Z,"This happens since Oracle VirtualBox version 5.2.2 (so 5.2.0 is the last version where access to a Novell eDirectory Root Folder is possible!)

If you share a subdirectory of the eDir-Root it works!

This happens with Shared Server-Directorys from:
Novell E-Directrory Version 8.8. SP5
NDS Version: 20219.15

Host = Windows 7 Pro x64
Guest = Windows 10 LTSB x64",SO4620
18541,Memory Reference,Windows,VirtualBox 6.0.4,2019-04-03T16:12:40Z,2019-04-04T16:55:43Z,2019-04-04T16:55:43Z,"""The Instruction at 0x... referenced memory at 0x... The memory could not be read.""
IDK what happened?
Help please.",HadeedTheError
18542,Windows 8.1 Pro host freezes and reboots,Windows,VirtualBox 6.0.4,2019-04-03T20:11:51Z,2019-04-03T20:49:53Z,2019-04-03T20:49:53Z,The Windows 8.1 Pro host freezes and reboots at random times with the Windows Server 2003 guest I had. I'm not sure whether this is related to VirtualBox or not. I have OpenShell/ClassicShell installed on the host computer and I don't know whether that's relevant. I without thinking deleted the virtual machine. I'll be creating a new virtual machine with the same setup and uploading the logs.,Eddy Smith
18538,Launching Firefox crashes VM with The memory could not be read.,Linux,VirtualBox 6.0.4,2019-04-02T23:36:48Z,2019-04-03T00:49:12Z,2019-04-03T00:49:12Z,"Installed Virtual Box 6.0.4 on Windows 10 1803 64 bit. Installed Red Hat Linux
6.10 Guest OS. 

After all the updates to Firefox and OS, launching the firefox
gives the message

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFBEA84E889 referenced memory at 0x000000000000001C. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------

Please fix this issue. 
",ketan
18534,Mouse Misalignment,Windows,VirtualBox 6.0.4,2019-04-01T17:29:32Z,2019-04-02T16:30:45Z,2019-04-02T16:30:45Z,"When returning from full screen via the Guest mouse is off by a significant amount.

In the screen shot attached the mouse is where the red arrow is.  Clicked and line that highlights is off by 1-2 rows.",isgdre
18531,Vbox 6.0.4 / HOST - Windows 10 ( 1809 ) / GUEST - Raspbian Stretch Kernal v4.14 / Surface Pro 6,Linux,VirtualBox 6.0.4,2019-03-29T21:38:24Z,2019-03-30T09:25:11Z,2019-03-30T09:25:11Z,"Bug noted regarding Mouse Visibility in reagrds to Virtual Machine Suspend as oposed to Shut Down.

Mouse integration on the Guest is Visible and Function upon Machine Startup.

If the machine is Shut Down ( Power off the machine ) then the mouse is Visible and Functional when restarted.

If the machine is Suspended ( Save the machine state ) then the mouse is Not Visible but Functional when restarted.

The condition is Repeatable and Consistent regardless of any changes in settings ( ie: PS2 Mouse vs Tablet ... )

NOTE: With the machine having been Resumed from a Suspended ( Saved State ) the mouse is visible on the host system and when hovering over the guest window. Once any region of the guest window is clicked on, then the mouse pointer disappears and only the effects of izems on the guest being hovered over is present. Mouse functionality is present, Only the Pointer is Not Visible.",ZAR
18526,Error warning at the boot,Windows,VirtualBox 6.0.4,2019-03-27T13:37:20Z,2019-03-27T13:37:20Z,2019-03-27T13:37:20Z,"When i start the system, i get a warning about a bug and an option to ignore it  or turn of the machine. If i ignore it i cant capture input on my system and when i press right ctrl to do so it does nothing, just highlights the input capture botton in the bottom left corner.",ceca
18520,Guest seems to be unresponsive,Windows,VirtualBox 6.0.4,2019-03-25T10:16:37Z,2019-03-26T19:16:09Z,2019-03-26T19:16:09Z,My system freezes after running for a few moments. I start and application and it freezes. The log details that the Guest is unresponsive. This is a regular occurrence for me. I've checked previous tickets and comments on the forum and made changes accordingly but I'm still having the problem. If someone could point out what the issue may be I could fix it myself and should it occur again on another machine I would know how to resolve the problem. Any help would be greatly appreciated. I don't want to have to delete the machine again.,GavEB
18514,Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).,Linux,VirtualBox 6.0.4,2019-03-22T06:40:12Z,2019-03-24T03:45:44Z,2019-03-24T03:45:44Z,"Failed to open a session for the virtual machine Ubuntu.

Failed to load unit 'HGCM' (VERR_TOO_MUCH_DATA).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",SChernolyas
18502,"VBOXSVGA driver not update screen on ""Microsoft Store"" when scrolling.",Windows,VirtualBox 6.0.4,2019-03-17T06:56:47Z,2019-03-24T01:42:01Z,2019-03-24T01:42:01Z,"VBOXSVGA driver not update screen on ""Microsoft Store"" when scrolling.

VBOXVGA will draw correctly.

This problem occurs with VBOXSVGA.

",0o0o
18510,#GP when Windows guest driver tries to write X86_CR4_PCIDE in non-HyperV environment,Linux,VirtualBox 6.0.4,2019-03-21T01:13:34Z,2019-03-21T01:13:34Z,2019-03-21T01:13:34Z,"Change 70917 [1] introduced code to check whether CR4 can be modified. The code might work on Hyper-V, but not on other VMMs, as the code may set the X86_CR4_PCIDE bit in CR4 while CR3[11:0] is not zero, which generates a #GP according to Intel SDM:

""MOV to CR4 causes a general-protection exception (#GP) if it would change CR4.PCIDE from 0 to 1 and either IA32_EFER.LMA = 0 or CR3[11:0] ≠ 000H""

This issue can be triggered by installing a VM on VirtualBox 6.0.4 installed on a Windows _virtual_ machine that runs on top of other VMM platforms, such as VMware ESX. 

[1] https://www.virtualbox.org/changeset/70917/vbox/trunk/src/VBox/HostDrivers/Support/win/SUPDrv-win.cpp",jiajun
18493,Guest W7-32Bit hanging with 6.4.0,Windows,VirtualBox 6.0.4,2019-03-14T10:16:54Z,2019-03-15T14:45:17Z,2019-03-15T14:45:17Z,"After upgrading to 6.0.4, my long used Windows 7 32Bit guest hangs after a few minutes or sometimes hours. It seems to work allright at first.

No specific action has been identified which leads to it hanging. It happend while browsing the internet, using the file-explorer and even during logout or shutdown.

The VM has to be killed - no other ways to shut it down. It happend 4 times now, definitively too often for my understanding - and it never happened with 5.2.

I have already upgraded the Guest-Additions, to no avail.

Other guests (e.g. W10 64Bit) work fine on the same host - even more stable in terms of audio I dare say.

I do use dual-screen, which is a very useful feature - one reason for having upgraded from the very stable former versions.
",ufotech
18486,Black screen when trying to use Kali Linux,other,VirtualBox 6.0.4,2019-03-10T16:01:31Z,2019-03-14T09:30:58Z,2019-03-14T09:30:58Z,A Black Screen appears after I click the install button in Kali Linux first menu. I  cannot use it as a live system neither.,Rafael1548
18483,Failed to open session,Linux,VirtualBox 6.0.4,2019-03-09T19:56:15Z,2019-03-09T21:02:07Z,2019-03-09T21:02:07Z,"Hi!

I saved state of my virtual machine.
Sometimes I get error:
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
",SChernolyas
18481,Upgraded to 6.x and now VB is broken,other,VirtualBox 6.0.4,2019-03-08T14:49:07Z,2019-03-09T05:16:02Z,2019-03-09T05:16:02Z,"I had as good running system with v 5.2 installed and several VMs 
1) Win 10 64 bit / Win Defender off except for Fire wall / Malware bytes 
2) I have downgraded and removed all ""User"" files and program files several times
3) I have tried in safe mode and also disabled malware bytes / same error 
4) I do not have any new Windows Updates installed 

System was fully functioning until I ran the 6.x update which took 15 minutes and hung / now system is 
dead 
Will attach hardening log and screenshot / I have read the forums on this and none of the ""fixes"" work 

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
",brentd36
18479,Can't restart saved state on Windows 10. Exception breakpoint 0x80000003,Windows,VirtualBox 6.0.4,2019-03-07T09:50:31Z,2019-03-08T06:02:22Z,2019-03-08T06:02:22Z,"Hi,

I'm running Virtualbox on a Windows 10 64b Pro 1803, and operating with a ""IE 10 - Win 7"" VM (downloaded on Virtualbox site a long time ago), NAT connection and Guest Add-ons installed.
The VM runs perfectly well, but if I stop it via Saving State and try to re-open it I systematically have a crash error. The session is then marked as Aborted and If I start it again it works (I have to start Windows via the ""BIOS"" ""Start windows normally"" menu option, though).
Is there any way I can solve this ?

I've seen in the tickets some which refer to that same breakpoint but they don't seem to apply to my case.

I attached :
- VBox.log
- VBoxHardening.log
- Screenshots of the various error messages I get

Thanks in advance.",jeanmiraptor
18478,"Impossible to copy files or dir beginning with a dot from guest to host, the 2 ones being Windows machines.",Windows,VirtualBox 6.0.4,2019-03-06T10:05:14Z,2019-03-08T05:04:48Z,2019-03-08T05:04:48Z,"Impossible to copy '''files or dir beginning with a dot''' from guest to host, the 2 ones being Windows machines. 

This is the summary of several existing tickets : #17859, #17067, #16762.

",JLB
18469,Version 6.0.4 r128413 (Qt5.6.2) Shared Folders not Accessible,Windows,VirtualBox 6.0.4,2019-03-04T07:37:36Z,2019-03-05T09:47:01Z,2019-03-05T09:47:01Z,"When the save machine state on Version 6.0.4 r128413 (Qt5.6.2) shared folders disconnected and is not reconnect until system complete restart. Saved state is not possible with shared folders.
Shared folders drive letter seems in Win7 Explorer but not connected. User is not enter to the drive. 

Host: Windows 7 Ultimate 64 Bit
Guest: Windows 7 Ultimate 64 Bit
All extension package and VirtualBox Guest Additions installed.
",Flu
18473,Windows7 VM keeps crashing,Windows,VirtualBox 6.0.4,2019-03-05T05:54:26Z,2019-03-05T08:55:24Z,2019-03-05T08:55:24Z,"Good Day. Since I upgraded to V6.04 my Windows7(32bit) VMs keep crashing/freezing. It sometimes happens while I'm using one of my apps and almost all the time when I'm working in windows explorer. It is extremely frustrating and corrupts my projects, which means engineering time lost.

I though it is a problem on only one VM but I started working on another VM wit the same OS and it does exactly the same. At the moment it is unbearable and causes a lot of lost time.",Omega
18464,Virtual box 6.x hangs VM,Windows,VirtualBox 6.0.4,2019-03-01T08:22:31Z,2019-03-01T11:17:35Z,2019-03-01T11:17:35Z,"Hello.
I'm running VirtualBox 6.0.4 in the following environment:
Host: Ms-Win10_64
Guests: Ms-Win10_64 Ms-Win7_64

After update to 6.x release, VM hangs after a few minutes ! ",Kotekino
18457,BSOD on Windows 7 host,other,VirtualBox 6.0.4,2019-02-27T02:38:18Z,2019-02-27T02:38:18Z,2019-02-27T02:38:18Z,VirtualBox recently started to cause a crash of my host Win7 when I start any VM. log file and minidump are attached.,rgazizov
18456,Corrupted UI under Windows 7 with classic theme,Windows,VirtualBox 6.0.4,2019-02-26T13:48:47Z,2019-02-26T13:48:47Z,2019-02-26T13:48:47Z,"Under Windows 7 with classic theme (144 dpi) the VirtualBox UI is corrupted: invalid checkbox size in the scrollable list of checkboxes, the checkmark is larger than the checkbox frame - see the picture.
",Codemaster
18450,Main Window closes when second display has 150% scale,other,VirtualBox 6.0.4,2019-02-23T18:54:38Z,2019-02-23T18:54:38Z,2019-02-23T18:54:38Z,"OS: Windows 10 Po x64[[BR]]
Main display: 1920x1280, scale: 100%[[BR]]
Second display (extends to the left of main display): 1920x1080, scale: 150%

Steps to reproduce the bug:[[BR]]
Launch VirtualBox, its window appears on main display;[[BR]]
Move the window to the second display and '''resize''' it;[[BR]]
Close the window;[[BR]]
Launch VirtualBox again: the window appears and closes in several seconds;[[BR]]
Now you can't use VirtualBox: its window just closes after launch.


To get it working again change scale factor of the second display to 100%, launch VirtualBox, move its window to the main display.",mjohn
18434,Mouse Integration Issue version 6.0.4 r128413,Windows,VirtualBox 6.0.4,2019-02-13T12:38:11Z,2019-02-14T09:51:44Z,2019-02-14T09:51:44Z,"Hi, 

I'm experiencing an issue with the mouse pointer in the latest release. When mouse integration is enabled the mouse pointer is distorted and very difficult to use. If I disable the mouse integration it looks and behaves as expected. I have looked on the forums and can't see any bugs logged for this version. 

Regards
James ",JamestheOracle
18433,Application Error - The instruction xxx referenced memory at xxx. The memory could not be read.,Windows,VirtualBox 6.0.4,2019-02-12T23:38:53Z,2019-02-12T23:38:53Z,2019-02-12T23:38:53Z,"Intermittently, a running Windows guest VM will crash and display the following error. The console window will then close on its own and return you to the VM manager.
Once it occurred during install of Windows 10 1809 and once after install and installing programs. I have rebooted the host in between the two occurrences.
Afterwards the VM is left in an Aborted state.
This has only appearing since installing VirtualBox 6.x, it has not occured before on v5.x.
The host is running Windows 10 1809 x64.",rjcuk
18430,DnD does work from Host to Guest but not the reverse,Windows,VirtualBox 6.0.4,2019-02-11T22:27:26Z,2019-02-11T22:27:26Z,2019-02-11T22:27:26Z,"Hi, I'm kind of new with VirtualBox and I recently install VirtualBox 6.0.4 version with Win 7 OS as my guest machine, with my Win 7 pro host machine. As I did some searches before, I of course did follow all of the usual common recommandations about:(i) ""Setting>General>Advanced>Bidirectional"" stuff, as well as (ii) I did install the ""Guest Additions"" with the Devices recommanded procedure. Now, I can copy/paste text (ex. https sites adresses) both ways. I can also drag n drop pdf, zip files/docs (like the one attached hereto) from host to guest machine. Now, the only thing missing, is drag n drop from guest to host!! I attached the log files of both host and guest, as per recommandations of your collegue in previous ""Investigating drag and drop (DnD) problems"" (https://www.virtualbox.org/wiki/DnDDebug). Thanks for any kind of help from anybody.",TrueGeek
18416,Each time VirtualBox starts VM from the saved state it hangs up with error E_FAIL (0x80004005),all,VirtualBox 6.0.4,2019-02-06T13:26:41Z,2019-02-11T08:05:44Z,2019-02-11T08:05:44Z,"This problem occurs each time I start virtual machine from the saved state.

This problem occurs on VirtualBoX versions 6.03, 6.04 and 6.05 r128628

This problem occurs on any kind of virtual machines (Windows XP, Windows 7, Ubuntu etc)
",gastor
18399,restore an acronis (.tib )backup of solaris10 OS into VM,Solaris,VirtualBox 6.0.4,2019-01-31T06:34:04Z,2019-02-10T08:23:57Z,2019-02-10T08:23:57Z,"hello
i got a backup of my solaris10 OS with acronis 2018 and restored in VirtualBox.
the system comes up and restart periodictly !
please help",bakia
18403,Linux Host and Windows guest both consume same input event (windows/action key),Linux,VirtualBox 6.0.4,2019-02-01T07:25:55Z,2019-02-07T09:08:40Z,2019-02-07T09:08:40Z,"Windows 10 Host
Linux Guest (Fedora 29 Workstation) 

Steps to reproduce:
Boot Fedora guest,
Press Windows Key

Observed behavior:
Windows start menu is opened and Gnome Activities is triggered at the same time

Expected behavior:
Only the guest receives the key event and the Gnome Activities is triggered without triggering the Windows start menu

Note:
This Problem did not exist in VirtualBox 5. ",nopaste
18417,USB thumb drive is persistent.  It does not disappear while removed,Linux,VirtualBox 6.0.4,2019-02-06T17:34:03Z,2019-02-06T17:34:03Z,2019-02-06T17:34:03Z,"SanDisk drive showed correctly in Devices, and was gone when I removed the drive.  That was then!  

Now, it does not disappear when removed, and in fact shows twice when I again install it.

Underlying Windows 10 device does come and go as expected.

Comment: is there a way to refresh devices (USB devices)?",Derick Moore
18409,Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) after experimental WDDM video driver installation.,Windows,VirtualBox 6.0.4,2019-02-05T07:41:44Z,2019-02-05T07:41:44Z,2019-02-05T07:41:44Z,"I have Windows 7 x86 guest on Windows 8 x64 host. Because of my issues (#18359) with SVGA adapter driver (not the current version is used even if current version of non-WDDM driver was previously installed) I tried the new approach. The new version of experimental (WDDM) driver was installed before the switch from the VGA to SVGA, after the non-experimental driver was already installed previously from the safe mode boot. As a result after the required restart of the guest OS I got the guru meditation. 

Side note: I installed the experimental driver in the normal mode, I didn’t boot the OS in the safe mode,because for the experimental drivers this isn’t a requirement. Other note: if I install the experimental driver (I say no to the standard one after activating the Direct3D support during the guest addition installation) in the safe mode, I have no issues with my desktop Java application, [https://forums.virtualbox.org/viewtopic.php?f=2&t=85458 TV Browser]. They appear as soon as I installed them in normal OS boot mode.",boxer01
18395,animations and mouse movement flicker [OS/2 guest],other,VirtualBox 6.0.4,2019-01-30T21:54:38Z,2019-01-30T21:54:38Z,2019-01-30T21:54:38Z,"On OS/2 guests animations on the desktop flicker. E.g. the mouse pointer is flickering while you move it. Same as the full window drag.

This occurs with and without guest additions, in windows as well as in fullscreen mode.

For testcase I installed Linux Mint on the same maschine and same vbox environement. There the mouse moves very smooth without flickering.",Frank.os2.org
18384,Cursor disappears during Linux installation,Linux,VirtualBox 6.0.4,2019-01-29T10:20:20Z,2019-01-29T10:20:20Z,2019-01-29T10:20:20Z,"When using 6.0.2 and 6.0.4 to install Oracle Enterprise Linux 7.5 the cursor disappears and is replaced by a smudge-like object. However that object is displaced by random factor of pixels in the X and Y direction making it unusable.
On version 5.X the smudge was also there, but so was the cursor - so I lived with it, but now I can not install the OEL 7.5.",htx
18382,Cursor scaling - cursor becomes very small or sometimes almost invisible,Windows,VirtualBox 6.0.4,2019-01-29T07:16:02Z,2019-01-29T07:16:02Z,2019-01-29T07:16:02Z,"This bug is not new to version 6 as I've seen it in 5.2 also. The mouse pointer (hardware cursor) depending on the application can become very small or even almost disappear. The cursor becomes much smaller in the RDP session started from the guest. Also it is smaller and with weird shapes in MS Office applications like Excel or Word. In Word or any other text editor (like Notepad++) where the cursor should be an I-beam it pretty much disappears. What is left of it when the mouse pointer is over an editor window are literally 2 pixels. Almost impossible to see.
This bug has been on and off over the last few months. I suspect although have no proof that Microsoft patches to the host or guest OS cause this change of behavior. Right now the bug is fully ""visible"" (pun intended).",Rafcio
18594,Ubuntu 18.04 (guest) audio stops working (stuck) after Windows 10 (host) sleeps,Linux,VirtualBox 6.0.6,2019-04-23T11:32:33Z,2021-06-05T11:04:24Z,2021-06-05T11:04:24Z,"'''Host:'''  Windows 10 Pro, 1809, 17763.437

'''Guest:''' Ubuntu 18.04

'''VirtualBox:''' 6.0.6

'''Sound card:''' either '''Intel HD''' or '''AC97'''.

All updates are installed. Guest additions are installed.

'''Problem:''' Ubuntu 18.04 (guest) sound works until Windows 10 (host) goes to sleep. For example, you're listening to YouTube music but after suspension the video and sound stucks forever.

'''Quick dirty workaround:''' Shutdown virtual machine, then launch again. ''Hot reboot doesn't work''!

Resetting of pulseaudio and alsa inside the guest ''doesn't work''!
{{{
sudo killall pulseaudio; sudo alsa force-reload;

Unloading ALSA sound driver modules: snd-hda-codec-idt snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer (failed: modules still loaded: snd-hda-codec-idt snd-hda-codec-generic snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer).
Loading ALSA sound driver modules: snd-hda-codec-idt snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-seq-midi snd-seq-midi-event snd-rawmidi snd-seq snd-seq-device snd-timer.

}}}

'''Any action inside the guest doesn't work.''' Only kill the guest and start again (not hot reboot!).

If audio has been playing during the getting sleep, then after system wakes up the 1 second of sound will be repeated infinitely from the guest (like a ""cla-cla-cla-cla-cla-cla...."").",James Fade
18629,Failed to open a session for the virtual machine vm1.,other,VirtualBox 6.0.6,2019-05-08T17:58:12Z,2020-04-06T15:13:19Z,2020-04-06T15:13:19Z,"win 10 - pro version 1903 - fast ring updates

Failed to open a session for the virtual machine vm1.

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",rolevsky
18592,OpenGL has performance and drawing issues after 6.0.6 update.,Windows,VirtualBox 6.0.6,2019-04-21T17:59:29Z,2019-08-12T05:35:00Z,2019-08-12T05:35:00Z,"After update to the aforementioned version my Windows 10 1809 host and guest got some problems. First of all the startup time is now double or triple as much as before. One can see the system starting as one would moved back from SSD to plain old HDD. Even if one see something there is a slow reaction on the keyboard and mouse events. So it takes more time from the start of the VM till the moment where you can do something with it.

The other one: as soon as host try to dime the display or turn it off, the content of the VM turns black. The programs work fine and you can hear the sound, but you can’t see anything, just black square. The mouse cursor changes itself in case you move it over some places (like border of the program’s window or the link in the browser). I could blindly shutdown the VM through keyboard commands directly in VM. There are some topics ([https://forums.virtualbox.org/viewtopic.php?f=6&t=92756 92756],[https://forums.virtualbox.org/viewtopic.php?f=2&t=92757 92757]) in the forum describing the same behavior. Some other tickets (#18564, #18582) are probably depends on this issue.

I tested with 5.2.28, current 5.2.29 and 6.0.7 with the same result. Going back to the 6.0.4, 5.2.26 or 5.2.22 solves this. I saw some changes in the OpenGL using code in the last to weeks, maybe this causing this behavior? I put my logs here, I could see some OpenGL warnings and errors here just 12 minutes after the VM start.

Funny enough this not happens on my older Windows 7 guest — Windows 8.1 host system. The Windows 10 systems are all Core i5 3xxx with build-in graphics, also not the youngest ones, but not as old as Windows 8.1 system.",boxer01
18637,"HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter WIn10 host, v6.0",all,VirtualBox 6.0.6,2019-05-13T01:05:31Z,2019-06-26T20:47:30Z,2019-06-26T20:47:30Z,"Had VMs working.  Win10 1809 update, then stopped working on all VMs.  Now get ""Failed to open a session for the virtual machine KubuntuVM.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""

of course removed existing adapter.  Added a new one.  It was manually configured.  I did have to click Enable box.  And still get this message.",RoryGriffin
18727,Problem when boot a VM,Windows,VirtualBox 6.0.6,2019-06-25T21:11:35Z,2019-06-26T20:44:59Z,2019-06-26T20:44:59Z,I instal a Virtual Box to another PC and copy a VMs Folder. I add the VM. When i start the VM after few minute an error occurred,Giampiero1972
18614,Windows clipboard borked (regression),Linux,VirtualBox 6.0.6,2019-05-01T17:26:30Z,2019-06-06T17:50:14Z,2019-06-06T17:50:14Z,"VMs running under 6.0.6 with the bidirectional clipboard enabled break all cut & paste, whether within the VM itself or between Windows apps.",vboxsf
18659,Virtual Machine Freezes after host desktop switched,Windows,VirtualBox 6.0.6,2019-05-19T13:50:32Z,2019-05-19T14:24:43Z,2019-05-19T14:24:43Z,"I have a Windows 2000 VM running under VirtualBox 6.0.6 r130049 (Qt5.6.2)

This is upon a fully up-to-date Windows 7 Ultimate host machine, using a  tool called Dexpot to switch host desktops upon a three-monitor system.

When I switch back to the desktop upon which the previously functional and running VM is displayed, the VM is locked up.  The only way to recover it is to pause and snapshot the VM, close it and then start it up again (not always successful in such cases).

As I have been using Dexpot for some years and can definitely say that the only software on the host affected by this problem (out of literally hundreds of software engineering tools, including VMWare, and office applications) is VirtualBox.

Is this a known problem and can it be fixed?
",Alex Tidmarsh
18642,Screen Video Recorder,other,VirtualBox 6.0.6,2019-05-14T23:51:32Z,2019-05-18T11:52:21Z,2019-05-18T11:52:21Z,"Create a ReactOS VM, or Ubuntu WM, all standard config, and activate the Screen Recorder.

VirtualBox Aditions Intalled, same version.

In the first start, select ISO of ReactOS, and no boot, crash in start VM splash.

In the VirtualBox 6.0.4, with VB Additions, works fine.",wgtapia84
18631,Win10/Win 10 Error 0x80070032: Can't copy file from VM to Host through Shared Folders,Windows,VirtualBox 6.0.6,2019-05-08T23:07:38Z,2019-05-08T23:07:38Z,2019-05-08T23:07:38Z,"This looks a lot like https://forums.virtualbox.org/viewtopic.php?f=2&t=84800&sid=99e7dde8811ab1c34e06e7a4e5057507 except for VirtualBox 6.0.6 r130049 (Qt5.6.2)

 Windows 10 Host (Surfacebook Laptop) [Version 10.0.17763.475][[BR]]

 Windows 10 VM [Version 10.0.17763.437][[BR]]

 VirtualBox 6.0.6 r130049 (Qt5.6.2)

The issue is I can't copy a file from the VM to the Host through the Shared folders path, both from the GUI and the command line with Host filesystems permissions set to [Everyone - Full Access].

Command Line Example:[[BR]]

C:\Users\v-crarno>copy C:\Users\v-crarno\Desktop\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM\Debug\Microsoft.Maker.Sparkfun.WeatherShield.winmd Z:\Users\craig\Documents\Redcley\iotil-hanford-rpi-core\c-sharp\EnvironmentMonitoringApp\EnvironmentMonitoringApp\bin\ARM[[BR]]

'''The request is not supported.'''
        0 file(s) copied.

C:\Users\v-crarno>ver

Microsoft Windows [Version 10.0.17763.437]

From the GUI I get the File Copy Error 0x80070032.

What I -can- do from the VM on the Shared folder is ""Create a file"", and ""Delete a file"".  And I can make a copy of a remote file [copy z:\... z:\...].  I just can't copy from C:\... to Z:\... [VM to Host]

Another important difference is I'm logged into a Domain Joined system in the VM, and Windows Networking with a different userID on the host system. I opened up security on the destination folder to [Everyone-Full Access]",craiga
18623,Kernel modules doesn't build with linux kernel 4.4.176 on openSuse 42.3,Linux,VirtualBox 6.0.6,2019-05-06T08:14:19Z,2019-05-06T08:14:19Z,2019-05-06T08:14:19Z,"On openSuse 42.3 kernel modules doesn't build, error message is:

VirtualBox Guest Additions: Building the modules for kernel 4.4.176-96-default.
VirtualBox Guest Additions: Look at /var/log/vboxadd-setup.log to find out what went wrong

Error message in log file is:

/tmp/vbox.0/regops.c:1440:52: error: too many arguments to function ‘get_user_pages_unlocked’
fWrite ? FOLL_WRITE | FOLL_FORCE : FOLL_FORCE);


Problem exist in version 6.0.4, 6.0.6 and latest testbuild 6.0.7 with proper VB guest extensions installed. Guest OS is updated.
",regnotyp
18601,Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack error,other,VirtualBox 6.0.6,2019-04-26T10:28:20Z,2019-04-26T10:34:02Z,2019-04-26T10:34:02Z,"Fallo al instalar el paquete de extensión D:/Downloads/www.virtualbox.og/Oracle_VM_VirtualBox_Extension_Pack-6.0.6.vbox-extpack.

The installer failed with exit code 1: VBoxExtPackHelperApp.exe: error: Membership in the Administrators group is required to perform this action.

Código resultado: E_FAIL (0x80004005)
Componente: ExtPackManagerWrap
Interfaz: IExtPackManager {70401eef-c8e9-466b-9660-45cb3e9979e4}

",jfuente
18599,Virtual machines VBOX 6 works extremely slowly on iscsi.,Windows,VirtualBox 6.0.6,2019-04-26T04:34:35Z,2019-04-26T04:34:35Z,2019-04-26T04:34:35Z,"After updating virtualbuox for version 6, virtual machines with 
disks, connected via a protocol iscsi, began to work extremely slowly.
Network storage, showed that the iscsi-target opens 4 connections
at once.",Bigfut
18595,No drag and drop between guest and host,Windows,VirtualBox 6.0.6,2019-04-23T14:16:30Z,2019-04-23T14:16:30Z,2019-04-23T14:16:30Z,"Hello all
There is the following problem since version 6.0.4.
After installing 6.0.6. there is still no Drag and Drop from Guest to Host.
Works only from Host To Guest.

OS Tested Windows XP and Windows 7 64 Bit.

Drag and drop services started (see log)

Thanks
Michele",MicheleGo
18580,Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.,Windows,VirtualBox 6.0.6,2019-04-19T09:50:35Z,2019-04-21T13:19:53Z,2019-04-21T13:19:53Z,"Deleting a snapshot doesn't show estimated time and operation progress bar always starts from 99%.
Host: Windows 10 1809 (64-bit).

Quote from VirtualBox 6.0.6 Release Notes:
''""This is a maintenance release. The following items were fixed and/or added:
[...]
User interface: fixed operation progress when deleting snapshots""
''",MisVin
18590,keyboard losing functionality in guest,other,VirtualBox 6.0.6,2019-04-21T13:14:24Z,2019-04-21T13:14:24Z,2019-04-21T13:14:24Z,"host: Windows 10, guest: OS/2
HW: notebook, built in keyboard.

In the guest, I am regularily losing keyboard functionality. Once I hit the ""Windows"" key (which brings up the Windows menu) I regain keyboard functionality in the guest. The guest is set to automatically ""catch"" the keyboard. I did also have this problem with 6.0.4 but I did not have this problem with older VirtualBox versions.",lerdmann
18589,I am experiencing an issue starting my Windows 10 virtual machine,Linux,VirtualBox 6.0.6,2019-04-21T12:38:16Z,2019-04-21T12:38:16Z,2019-04-21T12:38:16Z,"I downloaded a windows 10 virtual machine from their website and extracted the VM, I imported the virtual machine using the default settings and I received the error in the picture, I have increased my RAM dedicated to the machine and given it higher processing power, I use many VM's but only experiencing the issue with this virtual machine.",Erynh777
18587,Host-Only Adapter reverse to 0.0.0.0,Windows,VirtualBox 6.0.6,2019-04-20T20:15:20Z,2019-04-21T07:18:50Z,2019-04-21T07:18:50Z,"Hello, i was using Host-Only Adapter and when i try to configure adapter, it change back to 0.0.0.0 . I was searching but i only got sites without solution. Any help will be good.",SCr
18575,Virtualbox Graphics Adapter for Windows 8+ incompatible with AnyDesk,Windows,VirtualBox 6.0.6,2019-04-18T16:11:23Z,2019-04-18T16:11:23Z,2019-04-18T16:11:23Z,AnyDesk show black screen when connect with Virtualbox Graphics Adapter for Windows 8+ installed,Prisma
18574,Enhancement Dual Screen Single Click activation,Linux,VirtualBox 6.0.6,2019-04-18T15:56:53Z,2019-04-18T15:56:53Z,2019-04-18T15:56:53Z,"Hi,
I am on Linux with dual screen and when I activate my Virtual Box (which has two screen) I have to manually click each Virtual box windows to bring them on top.
Expected enhancement would make one click on a Virtual Machine having two monitor to become on top.
regards",JGWill
18565,"Windows 8.1 host, Linux Mint 19 Cinnamon guest, seamless mode: no menu bar, no host key",Linux,VirtualBox 6.0.6,2019-04-16T23:09:09Z,2019-04-17T09:36:27Z,2019-04-17T09:36:27Z,"On the lastest release of Virtual Box (6.0.6), and the one before that, I see the VirtualBox menu bar when booting Mint on my Windows 8.1 machine but, once Mint Cinnamon has finished booting, the menu bar disappears, seemingly never to return. Nor do the host keys (e.g. <host>+a) do anything. Thus, since I have the VM set to run in seamless mode, the only way to move outside the VM is to shut it down.

The version of Mint Cinnamon that I am booting is fairy vanilla: I have not customised it much or installed much software on it. It is running a 4.15 Linux kernel.

I do not seem to have the latest Guest Additions installed. I did, via Windows, download them and run them, but then my guest tells me they are not installed - and, it's the case that, because of the aforementioned problems, I cannot install them from within the guest.",JN
18695,Guest’s audio output is stuck after the host output device was changed.,Windows,VirtualBox 6.0.8,2019-06-07T06:36:04Z,2022-12-06T02:39:19Z,2022-12-06T02:39:19Z,"This is a new issue caused by some changes in November 2018. Those changes were done because of the issues in ticket #17225. Because the issues of the other ticket are solved and this is just follow-up issues caused by the changes in the other ticket, I open this one just for those issues.

The issue was already described in the old ticket, I also put some logs there, so I kinda link there for further information and logs (see comment 74 and some previous ones in #17225 for example). Some brief description: as soon as one changes the audio output device on the host (speakers to head phone or Bluetooth; or in the other direction), the guest’s audio output is simply stuck forever in the last second on the old device. The solution is always tricky, I described some of the working ones in the comments of ticket #17225. Sometimes only help is the guest’s reboot.",boxer01
18680,Create symbolic links in shared folders without administrator priviledges using new Windows 10 Developer Mode,Linux,VirtualBox 6.0.8,2019-05-29T13:27:20Z,2022-04-02T12:16:40Z,2022-04-02T12:16:40Z,"Starting with [https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/#jiIm1mzyjuXxAFXr.97 Windows 10 Insiders build 14972] symlinks can be created without needing to elevate the console as administrator. The prerequisite is to enable ''Developer Mode'', and after that any user on the machine can
1. Run the `mklink` command without elevating a command-line console
2. Use CreateSymbolicLink API '''if''' additional ''dwFlags'' option `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` is set to `0x2`.

Since even after enabling the ''Developer Mode'' VirtualBox has to be run as Administrator in order to create symlinks in shard folders, I assume the method 2 i.e. API calls are used to create them.

My enhancement request: Please add the `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE` to the API call when creating symlinks to shared folders under Windows 10 so Administrator priviledges are not required when ''Developer Mode'' is enabled.",asmala
18668,Problem with sharing serial port after upgrade from 5.2.28 to 6.0.X,other,VirtualBox 6.0.8,2019-05-22T12:00:47Z,2021-12-05T20:33:25Z,2021-12-05T20:33:25Z,"When I try to use a shared COM port (host device) on a guest running DOS 6.22 (using a legacy software for PLCs), on VirtualBox 6.0.8 (and also 6.0.6) I get errors like:
Serial#0: Failed to change parameters to 2400,NONE,5,1 -> VERR_INVALID_PARAMETER
and the software cannot communicate.

Everything works fine if I use VirtualBox 5.2.28 instead, with the same virtual machine.

The full log is attached.",stagadet
19169,"CVE-2019-11135 causes Win10 Guests with Q2'19 Intel CPUs to get stuck with ""IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)""",Windows,VirtualBox 6.0.8,2019-12-17T19:13:19Z,2020-07-09T13:03:59Z,2020-07-09T13:03:59Z,"When applying the [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135 CVE-2019-11135] microcode update via Microsoft's [https://support.microsoft.com/en-us/help/4524570/windows-10-update-kb4524570 2019-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4524570)], a Win10 (64-bit) guest will not boot completely, but will rather get stuck with:
{{{
00:00:07.800331 IEM: wrmsr(0x122,0x0`00000003) -> #GP(0)
}}}
Intel CPUs that have been affected so far are all Q2'19:
* [https://ark.intel.com/content/www/us/en/ark/products/193563/intel-core-i7-8665u-processor-8m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192987/intel-core-i9-9880h-processor-16m-cache-up-to-4-80-ghz.html Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz]
* [https://ark.intel.com/content/www/us/en/ark/products/192993/intel-xeon-e-2286m-processor-16m-cache-2-40-ghz.html Intel(R) Xeon(R) E-2286M  CPU @ 2.40GHz]

This affects all !VirtualBox > 6.0.8, hence the 6.0.10 version assigned.

Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=2&t=95783",Socratis
18751,Very low upload throuput in NAT adapter - Windows 10 x64 1903 host/guest,Windows,VirtualBox 6.0.8,2019-07-11T21:52:11Z,2019-10-20T23:57:16Z,2019-10-20T23:57:16Z,"Virtualbox 6.0.8+Extensions+VBoxGuestAdditions

Upload throuput using NAT is so extremaly bad, as compared to what Bridged provides, that I wonder if a bug could be there.

Full details explained here https://forums.virtualbox.org/viewtopic.php?f=2&t=93707

As workaround I switch on/off one or the other interface in the guest.",caspertone2003
18704,Windows-KB890830-x64-V5.73 (current Windows malicious software removal tool) in the shared folder causes crush  of the guest OS,Windows,VirtualBox 6.0.8,2019-06-12T07:29:21Z,2019-08-17T06:43:06Z,2019-08-17T06:43:06Z,"As I wrote, during the today’s Windows updates I downloaded the current version of t x64 MSRT and put it in the shared folder. As soon as I access the shared folder afterwards, the shared folder is shown empty. Shortly after that, the display (not the window) of the guest resizes to something very small like 640 × 480; couple of seconds later the BSOD happens and guest would be restarted.

I put my logs, directory listing of the shared folders and BSOD numbers in the archive. If something else is needed, just let me know. The logs clearly shows the detection of the critical condition. As soon as this file is removed from the shard folders, everything works as it should. This is Windows 10 1809 x64 guest and host combination.",boxer01
18756,Adding permanent shared folder through VBoxManage,all,VirtualBox 6.0.8,2019-07-15T11:01:23Z,2019-07-15T15:18:49Z,2019-07-15T15:18:49Z,It is not possible to add a permanent shared folder while the VM is running with VBoxManage whereas it is possible from the GUI.,Luc123
18752,BSOD When Running VM in Windows 7,other,VirtualBox 6.0.8,2019-07-11T22:44:34Z,2019-07-11T22:57:54Z,2019-07-11T22:57:54Z,"Upgraded from 5.2.26 to 5.2.30 and installed as admin. VBox will start fine but when I start a VM within a few seconds I get BSOD. Ran fdisk /F, looks fine. Uninstalled 5.2.30 and reinstalled 6.0.8, as admin, same issue. Uninstalled and reinstalled 5.2.26, same issue. See attache dump files. OS is Windows7 service pack 1",subrag
18749,vbox VERR_BUFFER_OVERFLOW GTX 1650,Linux,VirtualBox 6.0.8,2019-07-09T01:50:10Z,2019-07-09T03:32:08Z,2019-07-09T03:32:08Z,"Good day,

Any time I run anything that uses OpenGL, and I run with the 3D checkbox enabled, I receive this error...

OpenGL Warning: vbox Call failed with VBox status code VERR_BUFFER_OVERFLOW

I am running VB 6.0.8.

I recently moved my hard drive from an old machine to a new machine with...
i9 9900k with ROG-STRIX-Z390-E-GAMING.  If you need the full specs of the machine, just let me know.  Anyhow, I simply moved it and re-activated windows 10.

Unchecking the 3D box fixes the problem, albeit at a generally reduced performance for Google Chrome, my development IDE, etc.

I have attempted a re-install of virtualbox, as well as a re-install of the vbox client drivers, to no avail.

If someone wants me to run a special GTX 1650 build to try, just let me know.

Thanks.",Trent
18744,Virtualbox causes an abend Windows when it opens a Linux VM,Linux,VirtualBox 6.0.8,2019-07-05T14:24:23Z,2019-07-05T16:51:53Z,2019-07-05T16:51:53Z,"I Use Virtualbox since several years. My host is a Windows seven with 8 Go RAM. I tried several linux with success until some days. 
I had Linux Mint Plasma, Windows 10 as VM. Windows 10 works ithout problem. But when i tried to access Linux Mint, it abends Windows Seven. I get out Linux Mint from Virtualbox, and tried to re-install it. No success. Each try Abends Windows. 
I tried the Virtualbox 6.0.6 .... : same effects.

'''The message in Windows events is :
'''
Nom du journal :System
Source :       VBoxNetLwf
Date :         05/07/2019 16:08:37
ID de l’événement :12
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   Daniel-PC
Description :
Le pilote a détecté une erreur de pilote interne sur \Device\VBoxNetLwf.
XML de l’événement :
<Event xmlns=""http://schemas.microsoft.com/win/2004/08/events/event"">
  <System>
    <Provider Name=""VBoxNetLwf"" />
    <EventID Qualifiers=""49156"">12</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=""2019-07-05T14:08:37.444012300Z"" />
    <EventRecordID>794248</EventRecordID>
    <Channel>System</Channel>
    <Computer>Daniel-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\VBoxNetLwf</Data>
    <Binary>0000080001000000000000000C0004C0080000000000000000000000000000000000000000000000BCAEC55CB4500000</Binary>
  </EventData>
</Event>

I Hope to understand this problem, and resolve it !
Thanks.",Speedycool
18736,attach two similar usb device always fail,Linux,VirtualBox 6.0.8,2019-07-02T10:55:38Z,2019-07-05T12:10:22Z,2019-07-05T12:10:22Z,"Hi,
I want to attach two generic usb card reader, there is 3 problems :
- I can't differenciate which card in the menu (peripheral -> usb show me the same device twice)
- attaching the first device work, the second always fail
- once an attachement fail, the device will always be listed in peripheral -> usb, ejecting the device still show it, pluging the device again will create a new entry, trying to attach the device again will fail and so on...",JLM
18733,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Linux,VirtualBox 6.0.8,2019-07-01T09:46:33Z,2019-07-05T12:06:57Z,2019-07-05T12:06:57Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
18731,Fatal No bootable medium found system halting (with iso inserted),all,VirtualBox 6.0.8,2019-06-29T14:45:12Z,2019-07-05T11:57:35Z,2019-07-05T11:57:35Z,"Error:
When trying to start a new vm with the disk and iso inserted into sata receiving error: Fatal No bootable medium found system halting. Solutions already attempted: changing from sata to ide, making it a live cd/dvd and hot pluggable, and updating to the most recent version (stable or not stable).",28202
18734,[usb_camera] Can't not support 2 camera(rgb+depth) in one module on usb 3.0,Linux,VirtualBox 6.0.8,2019-07-01T09:46:42Z,2019-07-01T09:46:42Z,2019-07-01T09:46:42Z,"There is a module that can record video. It has 2 components, rgb and depth camera.

usb 2.0 does not have enough bandwidth. Hence, it adopts usb 3.0 to support 2 camera output.

When I select ""Device"" -> ""Webcams"" or ""USB"", I can see /dev/video0 and video1, but only one component is passed to virtual box. (I only can attach one from windows to ubuntu, not two).",fugitive666
18728,ntoskrnl.exe+939a0  error when i started virtual machines,all,VirtualBox 6.0.8,2019-06-26T16:01:36Z,2019-06-26T16:01:36Z,2019-06-26T16:01:36Z,my virtualbox crash my windows7 when i start any virtual machine,luizprogrammer
18718,VBox crashes using 32 bit Linux guest on a 64 bit Windows 10 host,Linux,VirtualBox 6.0.8,2019-06-20T14:38:24Z,2019-06-22T17:04:28Z,2019-06-22T17:04:28Z,"I've created a virtual machine with a 32 bit Linux on a Windows 7 64 bit host.
Now I tried to use the same VDI disk file on a Windows 10 64 bit host computer.
But when I created a new virtual machine in the current Version of VirtualBox
using the existing VDI disk Image an exactly the same settings as on the
Windows 7 host the virtual machine crashes (""Guru Meditation"" - Fatal error)
immediately after selecting the GRUB boot options in the guest.

This problem could be fixed by choosing ""Linux 2.6 / 3.x / 4.x ('''64 bit''')"" as
the guest OS in the ""general settings"" for the virtual machine -- although the
Linux guest has only 32 bit (80386 32 bit ELF binaries).
",Martin_G
18710,sharing folders from windows 10 host to win xp pro 64 bits doesn't work,Windows,VirtualBox 6.0.8,2019-06-15T00:58:12Z,2019-06-21T21:51:44Z,2019-06-21T21:51:44Z,"Hello,

i've tried to share two folders from windows 10 host system to win xp pro 64 bits (virtual machione) without success. i'm using oracle vm virtualbox 6.0.3 with guest additions.

is it a known issue and how can I solve it ? should i use an older version of virtualbox to make it work ?",Harlock59
18715,Resolutions >= 4096px wide break VboxVGA and VboxSVGA,Linux,VirtualBox 6.0.8,2019-06-19T17:22:15Z,2019-06-19T17:22:15Z,2019-06-19T17:22:15Z,"When trying to use a DCI 4k monitor (4096x2160) in fullscreen mode, the resolution kept being set to 1024x2160. VMSVGA correctly supports the resolution, but with a huge performance hit.

With more investigation, it seems like the resolution width is being calculated as `resolution_width = requested_resolution_width mod 4096` with it falling back to 1024 if the result is 0.",SinisterMinister
18707,Windows 1903 - Host Only Adapter - VM not starting,Linux,VirtualBox 6.0.8,2019-06-14T08:08:27Z,2019-06-14T08:52:54Z,2019-06-14T08:52:54Z,"Problem with Windows 1903 and latest VirtualBox / Extension Package
VM won't start when a Host-Only Adapter was attached.

Removal and a new fresh install of VirtualBox did not solve this issue.
Under Windows 1809 the VM runs fine but not under 1903 it crashes.

This error occurs also by the newly created machine. Recreating a new Host-Only-Adapter with DHCP enabled don't do the trick, too.

* Version 6.0.8 r130520 (Qt5.6.2)
* Latest Ext Pack installed

Error Message:[[BR]]
{{{
Für die virtuelle Maschine Cacti konnte keine neue Sitzung eröffnet werden.

Failed to open/create the internal network 'HostInterfaceNetworking-
VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Technical details:
{{{
sc query vboxdrv

SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}
",Cookie
18696,Host-only interface does not support IPv6 NDP properly?,Linux,VirtualBox 6.0.8,2019-06-07T17:33:12Z,2019-06-07T17:33:12Z,2019-06-07T17:33:12Z,"I'm having some issues with IPv6 networking via a host-only interface between a Windows 10 1803 host and Arch Linux guest...

Without configuring any additional addresses and just using IPv6 link-local addresses, I'm able to ping the guest intermittently from the host but the reverse does not work at all. It appears the host doesn't respond to neighbor solicitations...

IPv4 on the same interface works fine with the RFC1918 address and ARP...

See the attachments for command line output on both sides. Not included from the Windows side is the firewall rules from Windows Firewall but core stuff is allowed by default and I allowed incoming Echo Requests for ping testing.",vbutilizer
18655,Release of shift key not recognised in Guest when Hostkey is Shift-Ctrl,all,VirtualBox 6.0.8,2019-05-17T19:30:06Z,2019-05-17T19:30:06Z,2019-05-17T19:30:06Z,"When the Host Key is set to Right-Shift+Right-Ctrl, the release of the right shift key is not recognised when both shift keys are pressed and released. This leads to a behavior as if Caps Lock is active. Pressing and releasing the right shift key again ends this Caps Lock behavior.

The behavior has been observed with a Linux (Debian) Guest in an X11-Session as well as on the Linux Console. Even on the Grub Command Line this behavior occurred.

Using xev I could observe that there was no release event for the right shift key after pressing and releasing both shift keys.

Choosing a different Host Key solved the problem for me.",vbu
18647,E_FAIL (0x80004005),other,VirtualBox 6.0.8,2019-05-15T18:28:56Z,2019-05-15T18:28:56Z,2019-05-15T18:28:56Z,"https://youtu.be/W1SR-SZixI8

Графический интерфейс VirtualBox
Версия 6.0.8 r130520 (Qt5.6.2)
Copyright © 2019 Oracle Corporation and/or its affiliates. All rights reserved.


My email: alex@finogenov.ru",Alexander
19168,Error [drm:vmw_host_log [vmwgfx]] in version 6.1.0,Linux,VirtualBox 6.1.0,2019-12-17T06:21:18Z,2022-11-18T13:08:19Z,2022-11-18T13:08:19Z,"When booting my Oracle Linux 7 (4.14.35-1902.8.4.el7uek.x86_64) system I get the message: (Twice)
{{{
 [drm:vmw_host_log [vmwgfx]] *ERROR* Failed to send log
}}} 

This is when I select VMSVGA as the Graphics Controller. This message does not happen if I use the old VBOXVGA. I am unsure what, if anything, this effects.

I have included the machine log to this report.
",DonC
19199,Mouse Integration Not working,Windows,VirtualBox 6.1.0,2020-01-06T15:35:40Z,2022-04-11T10:28:29Z,2022-04-11T10:28:29Z,Updated to VirtualBox 6.1 this morning and mouse integration is no longer working.  The Mouse Integration option is checked and grayed out.  Mouse integration is not working at all.,cmccarron
19154,Using VMSVGA crashes VirtualBoxVM.exe,Linux,VirtualBox 6.1.0,2019-12-13T12:05:50Z,2022-01-15T23:44:46Z,2022-01-15T23:44:46Z,"Using VirtualBox on a Windows 10 host. Guest is Fedora 31 running Cinnamon UI.

After booting up guest, logging in, things work fine for a few minutes. But eventually, the guest crashes with an alert, title ""VirtualBoxVM.exe - Application Error"". 

Message is: ""The instruction at 0x00007FF95B82489D referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program.""

This is using the suggested VMSVGA Graphics Controller for 3D Acceleration. Backing off to VBoxSVGA causes things to not crash, but I lose 3D.


I have had this problem in the past with previous VirtualBox versions, but it persists in 6.1.0",Paul A Sand
19158,VirtualBox and bluetooth earbuds,Windows,VirtualBox 6.1.0,2019-12-14T15:31:06Z,2020-11-03T00:16:08Z,2020-11-03T00:16:08Z,"Host: Windows 10 (all updates)
Guest: Windows 10 (all updates)
Earbuds: Bluetooth Sony wf-1000xm3 (firmware 2.03)

Connected earbuds to host, guests detect and no issues.
Once earbuds disconnected from host and connected again, guest can not detect the audio coming from host via earbuds (sound via speakers and wired earnphones works well)",superme
19220,Edit Machine Settings - Error in UI,all,VirtualBox 6.1.0,2020-01-12T23:52:51Z,2020-03-02T18:32:53Z,2020-03-02T18:32:53Z,"PROBLEM:

I've imported some VBoxes from an older PC.  It had a saved state at the time and I cleared it.
I still can not start because of the system acceleration message.  
Clearing the SYSTEM->ACCELERATION->Hardware Virtualization check box does not clear the message and I can not click ""OK"" at the bottom to save the change.


MESSGE: 

System: Acceleration page:
The hardware virtualization is enabled in the Acceleration section of the System page although it is not supported by the host system.  It should be disabled in order to start the virtual system.

",Gereral.2018
19200,"Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU",Windows,VirtualBox 6.1.0,2020-01-06T20:48:17Z,2020-03-02T04:57:12Z,2020-03-02T04:57:12Z,"==============================================[[BR]]
Problem:

Windows 10 Guest wastes (constantly uses) a full CPU core on the Host, non-stop, even when Guest is not using CPU.[[BR]]
Windows 8.1 Guest does not waste a full CPU core on the Host.[[BR]]

==============================================[[BR]]
VMs: [https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/][[BR]]

==============================================[[BR]]
Problem Behavior:[[BR]][[BR]]
Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> Guest used CPU non-stop for ~30 mins (mscorsvw, ngen, wsappx, Windows Update, Antimalware Service Executable)[[BR]]
-> Host showed VirtualBox.exe/VirtualBoxVM.exe using a full core non-stop[[BR]]
-> Even after ~30 mins, when Guest stopped using CPU, host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Guest - Went to Windows Update and clicked Restart, which updated to: v1809 Build 17763.379[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Repeated for another Windows Update, updating to v1809 Build 17763.914[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]
-> Tried Shutdown then Start -> Normal Start[[BR]]
-> Host STILL showed a full core being used by VirtualBox.exe/VirtualBoxVM.exe[[BR]]

For all tests:[[BR]]
Paravirtualization Interface: Hyper-V[[BR]]

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Insider Fast v2004 Build 19041.1, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v5.2.35 Test Build 135314[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBox.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBox.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.0.15 Test Build 135299[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)

==============================================[[BR]]
Host: Windows 10 Release v1909 Build 18363.535, Oracle VirtualBox v6.1.0 Build 135406[[BR]]

Guest: MSEdge.Win10.VirtualBox - v1809 - Build 17763.379 - October 2018 Update (VM Build 20190311)[[BR]]
-> VirtualBoxVM.exe using a full core non-stop!

Guest: IE11.Win81.VirtualBox (VM Build 20180102)[[BR]]
-> VirtualBoxVM.exe does NOT use a full core! (Guest uses some CPU, but when Guest stops using it, host stops using it)
",Jacob Klein
19215,Fedora 31 Workstation - Hang and Crash,Linux,VirtualBox 6.1.0,2020-01-09T21:43:16Z,2020-01-20T13:46:23Z,2020-01-20T13:46:23Z,"The  laptop lid was closed but the PC was still running and when I opened up the lid and tried to access the Fedora 31 Workstation VM, the UI didnt response to keyboard/mouse.   I tried to select from the menu ACPI Shutdown and there was no reponse and finally tried Input->Keyboard->Insert CTRL+ALT+DEL.  The VM started shutting down and crashed either coming back up.",Aquis7
19224,get_Machines not working in 6.1 API,all,VirtualBox 6.1.0,2020-01-15T04:55:23Z,2020-01-15T04:55:23Z,2020-01-15T04:55:23Z,"Originally posted to forum (here: https://forums.virtualbox.org/viewtopic.php?f=34&t=96233), lodging as a bug report since not resolved....

---

I'm the developer of VBoxHeadlessTray (see here: https://www.toptensoftware.com/vboxheadlesstray). I'm trying to get it working with the latest 6.1 SDK but I'm finding that after calling get_Machines and going through the returned array, the IUnknown for the objects are returned correctly from SafeArrayGetElement, however calling QueryInterface for IMachine fails with E_NOINTERFACE.

The IID_IMachine I'm using is {85632C68-B5BB-4316-A900-5EB28D3413DF}

Running on Windows 10, guest OS is not applicable.
",toptensoftware
19219,Serial port access via USB dropping lots of data...,Linux,VirtualBox 6.1.0,2020-01-12T12:51:34Z,2020-01-15T04:44:08Z,2020-01-15T04:44:08Z,"Receiving data from a serial uart device seems to drop lots of data.

* Host: Windows 10 with VirtualBox 6.1 with extension pack
* Guest: Xubuntu 18.04 with guest additions
* FTDI serial USB module connected to USB port and passed through to Xubuntu
* FPGA connected to the FTDI module sending serial data at 115200 baud. The data is sent in 64-byte chunks, one chunk per second (it's a test project and that's just what I've selected for testing).

I'm finding that:

* Xubuntu on a real machine - works fine.
* Xubuntu in a VirtualBox VM - fails.

Under VirtualBox, I get maybe 16 bytes out of every 64 byte chunk and occasional data corruption (as in bytes that I know aren't being transmitted showing up).

The commands I'm using the dump the serial port are:

$ sudo ssty -F /dev/ttyACM1 115200 raw -echo
$ sudo xxd /dev/ttyACM1

Attached screen shot shows correct serial dump (under windows), on the right, the messed up data via VirtualBox.

VirtualBox Log also attached",toptensoftware
19187,"USB crashes VBox 6.0, 6.1",Windows,VirtualBox 6.1.0,2019-12-26T20:40:28Z,2020-01-13T12:15:06Z,2020-01-13T12:15:06Z,"When enabling USB filter for:
 Busch-Jaeger Elektro GmbH KNX-USB Interface (Flush mounted) [0101]
 vendor id 145c
 product id 1330
 revision 0101
on host W7 home premium sp1, guest W7 home premium sp1, with vbox 6.0, and latest 6.1. Vbox 6.1 at least sends application error message: ""the guest machine crashes with instruction at 0xdd0069fe referenced memory at 0x00000146. The memory could not be read."" whereas vbox 6.0 was simply aborting the guest machine without message.

It worked in Vbox 5.2.2 with same host, guest Windows XP.

",Yves P
19218,The driver detected an internal driver error on \Device\VBoxNetLwf.,other,VirtualBox 6.1.0,2020-01-12T09:57:19Z,2020-01-12T09:57:19Z,2020-01-12T09:57:19Z,"I have been having some BSOD issues and as part of investigating I found this in my event viewer. Please help with troubleshooting this problem
Event[30748]:
  Log Name: System
  Source: VBoxNetLwf
  Date: 2020-01-11T16:51:45.998
  Event ID: 12
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MICHAEL-10
  Description: 
The driver detected an internal driver error on \Device\VBoxNetLwf.",microbe
19217,Mouse integration setting is not persistent,Linux,VirtualBox 6.1.0,2020-01-11T16:11:52Z,2020-01-11T16:14:00Z,2020-01-11T16:14:00Z,"Mouse integration is re-enabled at every VM boot. The setting is not persistent and can not be disabled by default.

Host is Windows 10 Professional
Guest is Ubuntu 18.04 LTS

Oracle VM VirtualBox Extension Pack is installed on host.
Guest Additions Pack is installed on guest.

To reproduce:
  1. Boot Ubuntu 18.04 LTS guest.
  2. Disable mouse integration through view menu.
  3. Reboot guest.

Expected: Mouse integration remains disabled.

Actual: Mouse integration is enabled.

I do not know of a workaround. Mouse integration must be manually disabled every time the VM is started.",XK
19193,Opening a photo using Windows Photo app crashes VirtualBox,Windows,VirtualBox 6.1.0,2020-01-01T20:56:44Z,2020-01-01T20:56:44Z,2020-01-01T20:56:44Z,"If I double click on a .png file in Windows Explorer, VirtualBox crashes. This happens every time I try it, so I switched to using Irfan View to view photos for now.

Host Windows 7 Pro SP1
Guest Windows 10 Pro Build 1909 (18363.535)",Iain Waddell
19179,VirtualBox Application Error,Linux,VirtualBox 6.1.0,2019-12-22T09:22:17Z,2019-12-22T10:01:39Z,2019-12-22T10:01:39Z,"When I try to enable the 3D acceleration on VMSVGA the VM would be instable and eventually crashes with Application Error. 

Example Error message: 

{{{
The instruction at 0x00007FF9A50C019A referenced memory at 0x0000000000000010. The memory could not be read. Click on OK to terminate the program
}}}

When I disabled the 3D acceleration, the VM works fine.
It would be great if I could enable 3D support, so the UI would render much faster. 
",vboxfan66
19175,Getting blank screen while running virtual box session in windows 10 pro,Windows,VirtualBox 6.1.0,2019-12-20T04:08:42Z,2019-12-20T04:08:42Z,2019-12-20T04:08:42Z,"My VM session is getting stuck at blank screen during startup in windows 10. I can able to run it windows 7 with out any issues but not in windows 10.  

Can someone help me on this.

",amars404
19663,VBox on Windows 10 Pro: Dialog boxes too big for screen,all,VirtualBox 6.1.10,2020-06-12T11:07:37Z,2022-06-22T08:34:13Z,2022-06-22T08:34:13Z,"The dialog windows for VBox running on Windows 10 Pro (Lenovo T480 ThinkPad) overflow the screen and cannot be resized because the lower corners for resizing cannot be accessed.

Windows 10 Pro is set with defaults:
Display resolution: 1920 x 1080 (recommended)
Scale and layout: 150% (recommended)

Temporary solution to the problem is to change scale and layout to 125%; however, at that point the dialog box text becomes virtual unreadable.

Ideally, VBox should set a size limit on the dialog windows or allow resize from the upper corners as well as the lower.

Attachments are screen shots showing the original problem and the dialog window after adjusting windows screen setting.
",husbear
19851,Drag and Drop not working: VERR_ACCESS_DENIED,Linux,VirtualBox 6.1.10,2020-09-03T07:29:18Z,2022-02-04T10:34:54Z,2022-02-04T10:34:54Z,"Hi there,

I am working with VirtualBox 6.1.12 with a Windows 10 (1909) host and a Debian 10.5 guest.
Guest Additions are seemingly installed correctly (incl. perl, etc.). Clipboard is working fine bidirectionally.
Drag and drop is not working in any direction.

I try to d&d files from Debian GNOME Files application (3.30.5-stable) to Windows Explorer and vise versa.

I am working through this:
https://www.virtualbox.org/wiki/DnDDebug

..and thus generated the two following logfile sets for 6.1.12 (originally used version) and also for 6.1.10, after I did not find 6.1.12 in the bug ticket version list and thought: 
Might not harm to test the previous version, too.

In none of the logs I could identify helpful DnD-debug msgs except in the guest log of the 6.1.12 tests:

{{{
06:03:11.674153 00007f9c03e84640 main     New guest source window 0x200005 ('<No name>')
06:03:11.777268 00007f9c03e84640 main     Error reporting pending drag and drop operation status to host: VERR_ACCESS_DENIED
06:03:11.777307 00007f9c03e84640 main     Processing message 101 failed with VERR_ACCESS_DENIED
06:03:11.790000 00007f9c03e84640 main     New guest source window 0x200005 ('<No name>')
}}}

I tried to find suitable solutions here and in the www, but was not successful.

This bug ticket is configured to 6.1.10 but was originally intended to be assigned to 6.1.12, which seems not to be possible.


Thanks in advance and best regards
Claus",ClausG
19716,Total freeze VM after resume PC from sleep with multi-display,Linux,VirtualBox 6.1.10,2020-07-11T12:03:15Z,2021-06-05T22:35:10Z,2021-06-05T22:35:10Z,"I have notebook with additional display connected. After resume PC from sleep i have grayscaled VM (not resumed). After any manipulation (manual click to resume or power off) i have total freeze VM, any keys and menus do not work, I can stop it only from windows process manager. I see this bug only if I use additional display, and not always. Host - Windows 10 Pro. Guest - Ubuntu 20.04.

Last log messages:
{{{
19:20:59.444238 Pausing VM execution, reason 'host suspend'
19:20:59.445534 Changing the VM state from 'RUNNING' to 'SUSPENDING'
19:20:59.455506 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0781) created successfully
19:20:59.459381 AIOMgr: Async flushes not supported
19:20:59.460061 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0781) created successfully
19:21:00.435103 PDMR3Suspend: 988 580 745 ns run time
19:21:00.435115 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
19:21:00.435665 Console: Machine state changed to 'Paused'
19:21:01.289288 Audio: Device configuration of driver 'DSoundAudio' has changed
35:23:09.706882 Resuming VM execution, reason 'host resume'
35:23:09.706982 Changing the VM state from 'SUSPENDED' to 'RESUMING'
35:23:09.708188 AIOMgr: Endpoint for file 'D:\VM\u20d\u20d.vdi' (flags 000c0723) created successfully
35:23:09.716841 AIOMgr: Endpoint for file 'D:\VM\minerdev.vhd' (flags 000c0723) created successfully
35:23:27.908281 GUI: UIMachineLogic: Host-screen count changed
35:23:28.567910 GUI: UIMachineLogic: Host-screen count changed
35:23:28.921678 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: 0x0 x 1920x1080
35:23:28.921702 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.971593 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: 0x0 x 1920x1080
35:23:28.971614 GUI: UIMachineLogic: Host-screen available-area changed
35:23:28.972004 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenResized: Screen 1 is formally resized to: -1920x1072 x 1920x1080
35:23:28.972039 GUI: UIMachineLogic: Host-screen geometry changed
35:23:28.972572 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1080
35:23:28.972590 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.526775 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 3840x2130
35:23:33.526800 GUI: UIMachineLogic: Host-screen available-area changed
35:23:33.527365 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 1 work area is formally resized to: -1920x1072 x 1920x1050
35:23:33.527380 GUI: UIMachineLogic: Host-screen available-area changed
35:23:37.709638 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:41.938981 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
35:23:43.170192 GUI: Request for close-action to power VM off.
35:23:43.170209 GUI: Passing request to power VM off from machine-logic to UI session.
35:23:43.170453 GUI: Powering VM down on UI session power off request...
35:23:43.173091 Console: Machine state changed to 'Stopping'
35:23:43.174650 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
}}}

{{{
19:20:59.444238 - I sleep (or hibernate) PC.
35:23:09.706882 - Resume PC - VM is grayscaled, after any manipulation - total freeze.
}}}",PDZ
19729,VM failed to start with enabled EFI,Linux,VirtualBox 6.1.10,2020-07-17T11:44:12Z,2021-03-18T09:25:50Z,2021-03-18T09:25:50Z,"Approx. every tenth start/boot of the vm failed due to enabled EFI.
Failed means: the vm window opens and not output occurs.
This behavior can be seen on VBox version 6.1.10 r138449 (Qt5.6.2) and on older 
version 6.0.8 r130520 (Qt5.6.2).


",benni
19686,Guest audio loss following Windows host suspend,Linux,VirtualBox 6.1.10,2020-06-27T15:50:21Z,2021-01-26T00:17:35Z,2021-01-26T00:17:35Z,"(Similar to, but distinct from, https://www.virtualbox.org/ticket/19267)

Background is here: https://forums.virtualbox.org/viewtopic.php?f=6&t=98365 but I'll put everything important in this ticket.

The bug only occurs on Windows hosts (W10 1909 tested) - Linux hosts are fine.

No amount of disabling/re-enabling Audio in the Manager will return the VM to a working state, but suspending the guest via its own mechanism and then resuming it generally effects recovery, so my (ignorant) gut feel is that something has changed in the timing or behavior VBox's handling of suspend/resume that's caused the audio pieces to not quite sync up (i.e. resumed before ready or etc).

I have some potentially-useful endpoints to reduce the bisection, in the 6.0 branch: LKG is 6.0.12, FKB is 6.0.22. (The bug is also in the 6.1 branch since at least 6.1.6, through to 6.1.10, but I don't have any working versions of 6.1 to provide the other end).

I've posted a VBox.log in the forums, which I can duplicate here (or recreate with 6.1.10 if you prefer) - I'm not sure what the preference is for attachments.

Cheers.",arQon
19766,Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?,other,VirtualBox 6.1.10,2020-07-25T18:19:39Z,2020-12-01T13:33:35Z,2020-12-01T13:33:35Z,"Why can't I install Ubunut 20.04 (Mate) when WSL2 and Hyper-V is enabled?

Windows 10 Pro, Insider, 2004, 20175.1000
VirtualBox 6.1.12
Ubuntu Mate 20.04 ISO

When the ISO boots, it runs a disk check which fails with 1 error.
This error has been like this for many months now.
It's not the ISO, as same ISO installs perfectly well with with VMWare Player 15.5.6

VB very nearly works - it boots to Try/Install screen. Quiting that screen allows the ISO to be ""tried"".
But starting the Install, it fails with a read-error.

",jradxl
19662,Upgrade to 6.1.10 breaks all VMs on Windows 10,all,VirtualBox 6.1.10,2020-06-12T09:46:24Z,2020-11-16T08:53:58Z,2020-11-16T08:53:58Z,"Just upgraded from to 6.1.10 on Windows 10 and am not unable to start any VM, the error received is:
More specifically, the error is:

{{{
NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0xa34e2 and 0xa34ec in #1 (.text), first 8b != b8 (rc=-5600)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification Failure: The memory content does not match the image file.
}}}
",Twisted Lucidity
19741,Seamless mode is all-or-nothing,all,VirtualBox 6.1.10,2020-07-20T16:40:57Z,2020-11-10T21:00:39Z,2020-11-10T21:00:39Z,"Bringing //one// guest-window to the foreground in seamless mode, brings //all// guest-windows to the foreground, obscuring the natively-running apps.

For example, if I have:

1. An xterm running in the upper left corner,
1. Another xterm in the lower right corner,
1. Microsoft Outlook in the center,

clicking on the first xterm's titlebar will bring both X11-programs to the foreground, obscuring not only the upper-left portion of Outlook, but also the bottom-right segment...

This is both undesired and unexpected. Though my current VB-version is 6.1.10, the problem is not new -- I've had it since my first encounter with VirtualBox years ago.

My guests are all X11-based (FreeBSD and Linux), but someone else told me, they have the same problem with a Windows guest.",mi
19743,Hardening rejects DLL because of expired certificate nvldumdx.dll,Linux,VirtualBox 6.1.10,2020-07-21T13:04:30Z,2020-10-18T10:05:42Z,2020-10-18T10:05:42Z,"Im using a Nvidia GTX960 video card and it seems like the driver loader dll gets rejected because of an expired certificate.

The thing is that nvldumdx.dll is signed 2 times:
1. by Nvidia SHA1  (expired cert, was valid from 2018-2019)
2. by Microsoft SHA256  (valid cert)

Since Nvidia releases the file like that, I assume it's ok that only one of the signatures is valid, which is the case. But VirtualBox complains about the expired cert in the hardening log and rejects the file.

(VBox and video drivers are both the most recent releases)

{{{
2bc0.d1c: supHardenedWinVerifyImageByHandle: -> -23033 (\Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll) WinVerifyTrust
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll: Certificate is not valid (ValidTime=2020-07-05T18:39:56.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll' (C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll): rcNt=0xc0000190
2bc0.d1c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll'
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23033 (0xffffa607)) on \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):
2bc0.d1c: supR3HardenedScreenImage/LdrLoadDll: cached rc=Unknown Status -23033 (0xffffa607) fImage=1 fProtect=0x0 fAccess=0x0 cHits=1 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvldumdx.dll
2bc0.d1c: Error (rc=0):

}}}
",Peter B
19793,VM Guest Windows-7 Freezes after loading Operating System,Windows,VirtualBox 6.1.10,2020-08-05T11:50:31Z,2020-09-22T16:36:38Z,2020-09-22T16:36:38Z,"I have Laptop with this configuration AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx, 2100 Mhz, 4 Core(s), 8 Logical Processor(s) Installed Windows-10 on  it. Installed latest Virtual Box 6.1.12r Installed Windows-7 as VM guest frequently operating system crashes with in 2-3 days and need to get a new copy of it and observed that after load operating system VM freezes with no activity for 20-30 Min than starts responds. If I reboot laptop same issue reports. More issue in setting up Display settings adjustments. Can any one help me out it. 2 CPU's and 4 GB memory allocated.",Madhava
19646,Windows XP Machine freeze,Windows,VirtualBox 6.1.10,2020-06-08T20:04:10Z,2020-09-22T16:35:58Z,2020-09-22T16:35:58Z,"My XP machine always freezes without any visible reason. I tried a few things but don't know what to do now....

Please can you help me?

Best regards
Herbert",Herby_ITS
19844,hangul keyboard problem,Windows,VirtualBox 6.1.10,2020-08-30T05:44:13Z,2020-09-17T12:22:33Z,2020-09-17T12:22:33Z,"Hi.

In VB 6.0, Hangul & Hanja key is working.(guest Windows, Ubuntu, etc.)

In VB 6.1, Hangul & Hanja key is not working. (guest Winwods, Ubuntu, etc.)

In both, VB SoftKeyboard is working.

Please correct it.",test2020
19887,frequently the app(VM VirtualBox) does not respond,Linux,VirtualBox 6.1.10,2020-09-13T04:35:10Z,2020-09-16T12:59:25Z,2020-09-16T12:59:25Z,"Whenever I open the app, it hangs for sure and also when I open any virtual OS it does the same kind of thing.
I am doubtful that it is causing my system to slow down
Help me asap",jishu
19859,After executing a tutorial virtualbox is becoming super slow to run a Windows 10 instance,other,VirtualBox 6.1.10,2020-09-04T15:12:27Z,2020-09-04T15:12:27Z,2020-09-04T15:12:27Z,"I wanted to find out how to do this task : https://www.youtube.com/watch?v=6wVJUimaq2U

I executed it without trouble up until 08:40 ... which means that I didn't need to go to execute the following steps since VirtualBox recognized the UEFI drive and start the Windows from the boot manager.

Version : [https://pasteboard.co/JpxlUmV.png]

Running screenshot : [https://pasteboard.co/JpxldMc.png]

So the problem is VirtualBox is running at 40% CPU usage, I have enable UEFI and 16 GB RAM with 8 cores but it is hanging in the screenshot which I sent.

It seems that there is a bug.",vritual-boxer
19853,Linux instalation during boot instalation ISO,Linux,VirtualBox 6.1.10,2020-09-03T11:01:37Z,2020-09-03T11:01:37Z,2020-09-03T11:01:37Z,critical error occured while running the virtual machine. The issue is probably related to windows ,jtach
19848,Ubuntu new installation not booting,Linux,VirtualBox 6.1.10,2020-08-31T20:18:24Z,2020-08-31T20:18:24Z,2020-08-31T20:18:24Z,Ubuntu 20.04.1 new installation not booting sometimes. Logs attached for two incidents.,009
19842,Settings' 'OK' button not working.,other,VirtualBox 6.1.10,2020-08-29T06:53:59Z,2020-08-29T06:53:59Z,2020-08-29T06:53:59Z,The 'OK' button in settings is not working for the Virtual Box Manager,H3
19642,Virtualbox UI freezes after clicking VM in list and corresponding VM is not properly booting,Linux,VirtualBox 6.1.10,2020-06-07T10:29:01Z,2020-08-28T14:35:15Z,2020-08-28T14:35:15Z,"Observed behaviour:
--------------------

When I start the VM with ""vagrant up"" (while having Virtualbox GUI open), the VM is created and booted in Virtualbox. Then vagrant hangs at the point, when it tries to access the VM via SSH in order to configure the VM. At the same time in Virtualbox, when I click on the VM in the list, the GUI of Virtualbox freezes and does not unfreeze anymore. I need to end the Virtualbox Manager Process in Windows Task manager in order to make Virtualbox work again.
The Problem occurs with several Vagrant Boxes with recent Ubuntu versions (e.g. ubuntu/focal64, ubuntu/eoan64). It seems to work (at least most of the time) with older Ubuntu versions (e.g. ubuntu/trusty64).

I have the feeling that I experience problems with Virtualbox since upgrading Windows to 2004 (Spring 2020 Update) and/or enabling WSL2, but I cannot prove since I haven't used Virtualbox immediately before the upgrade / WSL 2 enabling.

Expected bahaviour:
-------------------

The Virtualbox GUI does not freeze when I click on the VM in the list of VMs and Vagrant is able to finish the prozess of configuring the VM.


Additional Information:
-----------------------

- Windows 10 Pro (2004, Spring 2020 Update)
- Windows Subsystem for Linux (WSL) 2 enabled 
- Virtualbox 6.1.10 r138449 (Qt5.6.2)
- Vagrant 2.2.9
- Vagrant Box: ubuntu/focal64, 20200605.1.0",chrizzzt
19837,Forwarded ports are blocked,Linux,VirtualBox 6.1.10,2020-08-27T13:42:17Z,2020-08-27T13:42:17Z,2020-08-27T13:42:17Z,"It can happen that ports which are forwarded to the guest are blocked on the host and therefore you are unable to open those ports on the host. Then you have to remove the forwarding, open the ports and then re-add the forwarding.

Expected behaviour:
Forwarded ports should not be blocked.",jnevada
19831,VB Virtual Monitor Setting,Windows,VirtualBox 6.1.10,2020-08-25T09:08:20Z,2020-08-25T09:08:20Z,2020-08-25T09:08:20Z,"I am using high resolution screen (3840 x 2560).
When I start my VM I can use the virtual monitor to force the guest to switch the resoution to up to 1600x900. The pull down menu however offers also 1920x1080 and 1920 x 1200. Nothing happens if select them from a lower current guest resultion. 
When expand the guest to maxumum from the host window (auto resizing) I can use the full screen resolution (Great !).
If I click now on in the virtual monitor menu on 1920 x1200 the guest resizes (virtualbox window however remanis maximize).
So there are some issues here on handling the virtual monitor I guess. 
Would be greast offer higher ressultions in the virtual monitor menu for up to the maximum host physical screen resolution (maximizing the host window proofs that the resultions are achievable) but at least that the offered screen resultions in the virtual screen resoltion work properly.",Andreas S
19830,VB 6.1.12 Windows 10 host BSOD NDU.SYS,Linux,VirtualBox 6.1.10,2020-08-24T19:53:03Z,2020-08-24T19:53:03Z,2020-08-24T19:53:03Z,"No issues with previous VB version. After install BSOD  usually within an hour after Win10 host boot. VB does not have to be running though if so the BSOD seems quicker to result. The minidump indicates NDU.SYS faulting with KMODE_UNHANDLED.

Uninstalling VB 6.1.12 results with NO host BSOD for 4 days. Reinstalling results in BSOD within 1 hour of host boot. Currently uninstalled with no host BSOD since.

2 decyphered minidumps below:

==================================================
Dump File         : 082220-8750-01.dmp
Crash Time        : 8/22/2020 9:41:05 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff802`317b4540
Parameter 3       : ffff9d89`fb53d4a8
Parameter 4       : ffff8d80`e29df930
Caused By Driver  : Ndu.sys
Caused By Address : Ndu.sys+4540
File Description  : Windows Network Data Usage Monitoring Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.18362.1 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+1c23c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\082220-8750-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 742,612
Dump File Time    : 8/22/2020 9:42:40 PM
==================================================

==================================================
Dump File         : 082020-10078-01.dmp
Crash Time        : 8/20/2020 9:46:39 PM
Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x0000001e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff805`7a723df9
Parameter 3       : 00000000`00000001
Parameter 4       : ffff8b0d`b5deb9c0
Caused By Driver  : Ndu.sys
Caused By Address : Ndu.sys+3df9
File Description  : Windows Network Data Usage Monitoring Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.18362.1 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+1c23c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\082020-10078-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 1,545,378
Dump File Time    : 8/20/2020 9:47:24 PM
==================================================

",psionprime
19828,Bug virtualización por hardware,Windows,VirtualBox 6.1.10,2020-08-21T22:41:54Z,2020-08-21T22:41:54Z,2020-08-21T22:41:54Z,"en maquinas donde la virtualización no es compatible, aunque no este activada no te deja guardar la configuración",MaurOwO
19815,Extremely low performance and high CPU consumption on Ryzen 3600X,Windows,VirtualBox 6.1.10,2020-08-15T21:29:08Z,2020-08-15T21:29:08Z,2020-08-15T21:29:08Z,"I started having this problem after migrating my VMs to the new hardware - i.e. Ryzen 3600X and Asus B550 motherboard. Simply booting a VM takes about 6 minutes with 30-40% CPU utilization, and running a VM in idle mode consumes about 10-20% CPU.
Host and guest - Windows 10 both.
See the logs.",fandrei
19813,Instalation Windows2019,Windows,VirtualBox 6.1.10,2020-08-14T15:03:20Z,2020-08-14T15:52:02Z,2020-08-14T15:52:02Z,"When I try to install Windows2019 I get Error

Versión 6.1.12.r

The host is Windows 2008R2 Server 64 bits",LluisG
19814,I can't install Windows 2019 in a virtualbox machine,Windows,VirtualBox 6.1.10,2020-08-14T15:31:32Z,2020-08-14T15:50:11Z,2020-08-14T15:50:11Z,"When I try to add a virtualbox machine and start the instalation from The ISO image, I get ERROR

The Host where it runs virtualbox is Windows 2008R2 64bits with lasts updates",LluisG
19809,Very bad latency numbers with more than 1 vCPU,Linux,VirtualBox 6.1.10,2020-08-12T23:22:25Z,2020-08-13T22:11:28Z,2020-08-13T22:11:28Z,"VirtualBox 6.1.12 verified on Win10 host (or openSUSE TW host), with Linux guests Ubuntu 16/18 or openSUSE TW.

Basically, I have distilled this down to a small perl script, that sleeps for 1ms for 1000 times.  Ideally, this would be 1000ms total -- but on real hardware, the script takes just a shade under 1100ms per iteration (perl overhead, etc), and when VirtualBox is behaving, about 1350-1425ms per iteration.

On real hardware, 100% of 1ms sleeps are <2ms.  When VirtualBox is behaving, 99% of 1ms sleeps are <2ms, and the upper bound is around 10-15ms for a few outliers.

The problem is when vCPU is 2+ ... the more added, the worse latency gets.  1ms sleeps start taking 100ms, 300ms, 500ms, occasionally even 900ms to return.",JasonM
19802,Cannot start any VM guest: Make sure the kernel module has been loaded successfully. VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH -Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3),other,VirtualBox 6.1.10,2020-08-09T10:52:08Z,2020-08-09T11:15:46Z,2020-08-09T11:15:46Z,"Hello,

I got an issue after upgrading from 6.0.22r 137980 to 6.1.12r 139181.
[[Image()]]

{{{When starting a VM-guest, I receive an error message
NtCreateFile(\Device\VBoxDrvStub) failed: unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
CBoxDrvStub error: ntdll.dll: 11 difference between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8(rc=-5600)

Make sure the kernel module has been loaded successfully.

where supR3HardenedWinReSpawn what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification
Failure: The memory content does not match the image file.}}}
[[Image()]]

I may run into this, because I didn't instantly restarted the Windows 10 (2004) host after Installation? Also the installer complained the first try, that something (i don't remember, what) was in use by virtualBox. I then restarted the installer and everything went just fine on the second try. But I didn't saw the message box that instructed to reboot, and the installer offered to start virtualbox instead immediately! The virualbox management Window got focus and covered the prompt ""You must reboot your computer!"".

The VirtualBox Window popped up a message box that prompted for updating the VirtualBox 6.1.12 Oracle VM VirtualBox Extension Pack! 

So I just installed it and THEN I rebooted (maybe this is the culprit? If so, the installer shouldn't allow to start VirtualBox instantly, if in the fierst place it should restart the host to install virtual box first completely before updating the extension pack! Not to mention the focus issue of the covered prompt to reboot to fully perform the installation and complete the process ...

I found an outdated bug report (5 years ago) somewhat related:

VirtualBox 4.3.26
https://www.virtualbox.org/query?status=%21closed&version=VirtualBox+4.3.26
(closed defect: fixed)
Opened 5 years ago Last modified 4 years ago
VirtualBox fails to launch any virtual machine: NtCreateFile failed
https://www.virtualbox.org/ticket/14052

Now the errors:


{{{
The virtual machine 'Debian pv10' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'L:\Data\VirtualBox VMs\Debian pv10\Logs\VBoxHardening.log'.

Fehlercode: E_FAIL (0x80004005)
Komponente: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
}}}



{{{
35e8.550c: supR3HardNtChildPurify: Done after 517 ms and 0 fixes (loop #0).
384c.548c: Log file opened: 6.1.12r139181 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa047bb00
384c.548c: supR3HardenedVmProcessInit: uNtDllAddr=00007ffc7dac0000 g_uNtVerCombined=0xa047bb00 (stack ~00000000010ffa48)
384c.548c: ntdll.dll: timestamp 0xb29ecf52 (rc=VINF_SUCCESS)
384c.548c: New simple heap: #1 0000000001200000 LB 0x400000 (for 2031616 allocation)
384c.548c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume17\Program Files\Oracle\VirtualBox'
384c.548c: System32:  \Device\HarddiskVolume17\Windows\System32
384c.548c: WinSxS:    \Device\HarddiskVolume17\Windows\WinSxS
384c.548c: KnownDllPath: C:\Windows\System32
384c.548c: supR3HardenedVmProcessInit: Opening vboxdrv stub...
35e8.550c: supR3HardNtEnableThreadCreationEx:
384c.548c: supR3HardenedWinReadErrorInfoDevice: 'ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8'
384c.548c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
384c.548c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
35e8.550c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5600 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
384c.548c: KiUserExceptionDispatcher: 0xc0000005 (0000000000000001, 0000000000000024) @ 00007ffc7dac72a6 (flags=0x0)
  rax=0000000000000000 rbx=00007ffc7dc252c0 rcx=00007ffc7dc252c0 rdx=00000000fffffffa
  rsi=0000000000000000 rdi=00007ffc7dc24f00 r8 =0000000000000000 r9 =00007ffc7dc25200
  r10=0000000000000000 r11=00000000010f92e0 r12=0000000000000000 r13=0000000000f34000
  r14=0000000000000001 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffc7dac72a6 rsp=00000000010f9140 rbp=00000000ffffea00    ctxflags=0010005f
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b    eflags=00010213   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=00000000010f9368  P6=00007ff7fa73a900
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=00007ff7fa6d47f0 dcr=00000000010f9300
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
35e8.550c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
35e8.550c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 11 differences between 0x9fe12 and 0x9fe1c in #1 (.text), first: 8b != b8
}}}

I'll attach the complete VBox Hardening.log

Thanks in Advance

floogy  

",floogy
19799,Incorrect DHCP lease command output,Linux,VirtualBox 6.1.10,2020-08-07T07:18:51Z,2020-08-07T07:18:51Z,2020-08-07T07:18:51Z,"VirtualBox 6.1.12r139181

Please, take a look at leases file fragment below:

{{{#!xml
<?xml version=""1.0""?>
<Leases version=""1.0"">
  <Lease mac=""08:00:27:6a:51:e9"" id=""010800276a51e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.254""/>
    <Time issued=""1596783415"" expiration=""600""/>
  </Lease>
  <Lease mac=""08:00:27:6a:51:e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.252""/>
    <Time issued=""1596783702"" expiration=""600""/>
  </Lease>
}}}

Command output:

{{{#!python
C:\Users\User>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       acked
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 10 sec left
}}}

Should return the latest lease, not the first one I assume.

And it didn't return the correct lease even when first one expired:

{{{#!python
C:\Users\user>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       expired
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 0 sec left
}}}

Expected behaviour: return the last lease for MAC address.",imort
19796,Server 2019 Virtualbox host - Guest with any type of GUI causing Windows RDP to crash forcing reboot,all,VirtualBox 6.1.10,2020-08-06T01:23:16Z,2020-08-06T01:23:16Z,2020-08-06T01:23:16Z,"When RDP'ing to a server 2019 Host with virtualbox installed, attempting to run a guest with a GUI (EG: Ubuntu Desktop, Windows 7 /10) causes RDP to crash and unable to reconnect. Appears to take down whole server as unable to connect to other services either. 

Have been unable to find any details of crash in windows event log. 

Last crash occurred when trying to run windows7 installer ISO. ",ranvens
19787,Virtual Machine goes into error after few days,Windows,VirtualBox 6.1.10,2020-08-03T11:25:34Z,2020-08-03T11:25:34Z,2020-08-03T11:25:34Z,"Hi,
I am using Virtual Box 6.1.12 on Windows 10 as a host. I am facing a issue of error on my VB which is attached. This is happening after few days and to overcome this I have to uninstall it, delete the .exe file from PC and then restart the PC and download again the new Vbox from Website. I don't know what to call this error. I have attached couple of pics and the Log.
Can anyone help me in this ti resolve the issue. By the way, it doesn't matter which version of Vbox I have installed. This error occurs after few days 

Thanks
Manoj",Montu
19761,VirtualBox guest OpenWrt OS crashed when using the nmap to scan the wireless network through the USB port,Linux,VirtualBox 6.1.10,2020-07-25T06:04:07Z,2020-07-31T02:05:45Z,2020-07-31T02:05:45Z,"Guest OpenWrt OS crashed with the following configuration and operation
Host is the Lenovo ThinkCentre M920t desktop PC, WIN 10 professional OS.
The VirtualBox v6.1.12 with extension pack 6.1.12 is installed. 
The Guest OS is Linux 64bit(OpenWrt Lede 17.01). Using the MediaTek USB wifi dongle MT7601U to act as a AP(AccessPoint). It works well, I can connct it by my mobile phone and surf the Internet without problem, but it will be crashed once I use the nmap(v7.31) to scan the wifi network. I have the exactly same configuration with my HP laptop and the sympton won't happen in it, don't why it's crashed with my Lenovo desktop PC.",MercyLin
19773,Cannot see Host Only Adapter in Windows 10 adapters,Linux,VirtualBox 6.1.10,2020-07-28T08:51:40Z,2020-07-28T08:51:40Z,2020-07-28T08:51:40Z,"After some wailing and gnashing of teeth, I got host only networking to work with Uvuntu 20.04. I was expecting to see the adapter in the Control Panel\Network and Internet\Network Connections but it doesn't show up. It does appear in the Device Manager.
",d0325mgray
19771,Windows 7 Guest Goes BSOD upon rebooting after install of Guest Additions for 6.1.12,Windows,VirtualBox 6.1.10,2020-07-27T04:46:05Z,2020-07-27T04:46:05Z,2020-07-27T04:46:05Z,"Windows 7 Client runs fine under version 6.1.10,  I performed the upgrade to 6.1.12.  After rebooting I installed the guest additions and rebooted as requested.  I could no longer successfully reboot.  I could reboot into safe mode only.  I kept getting the BSOD message.  I rolled back to version 6.1.10 and everything is working again.",Yogi2
19754,Cannot use VM due to Guru Meditation Error,Linux,VirtualBox 6.1.10,2020-07-23T09:16:33Z,2020-07-24T07:48:08Z,2020-07-24T07:48:08Z,"when starting a VM it asks me to choose from four options: ubuntu, advances options for ubuntu and two memtests. In the logs the error shows as "" VCPU0: Guru Meditation -1149 (VERR_EM_INTERNAL_ERROR)"".
updated the version from 6.1.10 to 6.1.12 but the problem remains 

after creating new VMs also has the same error

",virgo
19752,Linux VMs are not running with MS Defender Application Guard,Linux,VirtualBox 6.1.10,2020-07-22T18:57:43Z,2020-07-22T18:57:43Z,2020-07-22T18:57:43Z,"If you install/activate this Microsoft feature, all Linux VMs will stay stuck with a black screen.
I was just able to start without issue a Win 7 VM.

After removing the MS feature, all Linux VMs (and Windows)are running fine.

Regards,",Cruzzy54
19750,Changing from guided to expert mode deletes,Windows,VirtualBox 6.1.10,2020-07-22T12:48:02Z,2020-07-22T12:48:02Z,2020-07-22T12:48:02Z,"Good afternoon,

By the time you add a new machine, the program detects the operating system when you type VM's name. If you change from guided to expert mode, it deletes VM's name and detected OS.

You can see it in [https://streamable.com/cd8btm this video].

Regards.",Antonio López Fernández
19746,while installing os it stucks at black screen,all,VirtualBox 6.1.10,2020-07-22T06:20:18Z,2020-07-22T06:20:18Z,2020-07-22T06:20:18Z,"I checked off Hyper-V and 3D acceleration but still, it's stuck at the black screen I waited for half-hour its shows running and stuck at the black screen",promethius
19744,Critical Error,Linux,VirtualBox 6.1.10,2020-07-21T19:42:00Z,2020-07-21T19:42:00Z,2020-07-21T19:42:00Z,Critical error ocurs while compiling with GCC. All my woes seems to have started after upgrading windows 10 (the host) to version 2004 and virtualbox to 6.1.12 r139181 (Qt5.6.2). I often also get program referenced illeegal memory at 0x000000 warra warra warra.,Tiaan
19739,Menu opens on wron place,Windows,VirtualBox 6.1.10,2020-07-20T08:26:15Z,2020-07-20T08:26:15Z,2020-07-20T08:26:15Z,"VirtualBox 6.1.12 r139181 (Qt5.6.2)

When I click on a menu the menu opens on the wrong place.",Eistee
19738,Virtualbox aborting on resume,Linux,VirtualBox 6.1.10,2020-07-19T23:33:42Z,2020-07-20T04:28:10Z,2020-07-20T04:28:10Z,"Windows 10 2004 19041.388
Virtualbox 6.1.12

This happens in three ways
1) save-state -> resume vm
2) running -> pause -> resume vm
3) start as hidden -> show -> close-window and continue running in the background

a popup box appears
VBoxHeadless.exe - Application Error
The instruction at 0x... referenced memory at 0x0000..000C. The memory could no be read
Click OK to terminate the program

00:00:25.871086 VMMDev: Guest Additions capability report: (0x0 -> 0x4) seamless: no, hostWindowMapping: no, graphics: yes
00:00:26.335303 VMMDev: Guest Log: 22:32:02.516677 main     VBoxService 6.1.10_Fedora r138449 (verbosity: 0) linux.amd64 (Jun  8 2020 00:00:00) release log
00:00:26.335670 VMMDev: Guest Log: 22:32:22:32:02.517571 main     OS Product: Linux
00:00:26.337367 VMMDev: Guest Log: 22:32:02.519165 main     OS Release: 5.7.8-200.fc32.x86_64
00:00:26.338250 VMMDev: Guest Log: 22:32:02.519954 main     OS Version: #1 SMP Thu Jul 9 14:34:51 UTC 2020
00:00:26.339013 VMMDev: Guest Log: 22:32:02.520828 main     Executable: /usr/sbin/VBoxService
00:00:26.339255 VMMDev: Guest Log: 22:32:02.520828 main     Process ID: 421
00:00:26.342033 VMMDev: Guest Log: 22:32:02.520829 main     Pa22:32:02.523773 main     6.1.10_Fedora r138449 started. Verbose level = 0
00:00:26.344597 VMMDev: Guest Log: 22:32:02.526267 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:26.345107 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:00:37.138464 IEM: rdmsr(0x122) -> #GP(0)
00:49:57.970214 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:49:57.970344 PDMR3Suspend: after     0 ms, 1 loops: 1 async tasks - virtio-scsi/0
00:49:59.069354 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0781) created successfully
00:49:59.426309 AIOMgr: Async flushes not supported
00:49:59.505913 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0781) created successfully
00:49:59.541990 PDMR3Suspend: 1 571 708 931 ns run time
00:49:59.542009 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:49:59.542021 Console: Machine state changed to 'Paused'
00:50:04.490337 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:50:04.490657 AIOMgr: Endpoint for file 'E:\groot\vdisks\fedoraminimalm13_sys.vdi' (flags 000c0723) created successfully
00:50:04.495647 AIOMgr: Endpoint for file 'Y:\tmp\space.vdi' (flags 000c0723) created successfully
00:50:04.500963 Changing the VM state from 'RESUMING' to 'RUNNING'
00:50:04.500977 Console: Machine state changed to 'Running'
00:50:04.501069 
00:50:04.501070 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002f58!!!
00:50:04.501075 
00:50:04.501075 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501079 ExceptionInformation[0]=0000000000000000
00:50:04.501082 ExceptionInformation[1]=000000000000000c
00:50:04.501085 
00:50:04.501085 cs:rip=0033:00007ffa18bb0023
00:50:04.501089 ss:rsp=002b:0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501093 rax=00000000000022e0 rcx=00000000064b0000 rdx=00000000064b3340 rbx=00000000064b0000
00:50:04.501096 rsi=00000000064b3340 rdi=0000000000000000 rsp=0000000008f4d7f0 rbp=0000000008f4d8f0
00:50:04.501102 r8 =00000000064b0140 r9 =0000000000000004 r10=0000000008f4fb10 r11=0000000008f4fb10
00:50:04.501107 r12=00000000064b3340 r13=0000000000000000 r14=0000000000000020 r15=0000000000000060
00:50:04.501110 ds=002b es=002b fs=0053 gs=002b eflags=00010287
00:50:04.501113 p1home=0000000000000000 p2home=0000000000000000 pe3home=00000000064b0000
00:50:04.501117 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
00:50:04.501126 
00:50:04.501126 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000456c!!!
00:50:04.501137    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
00:50:04.501147 
00:50:04.501148 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffa18bb0023
00:50:04.501176 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
00:50:04.501190 ExceptionInformation[0]=0000000000000000
00:50:04.501202 
00:50:04.501203 Stack 0000000008f4c740, dumping 0x38c0 bytes (low=0000000008e50000, high=0000000008f50000)
00:50:04.501215 ExceptionInformation[1]=000000000000000c

Though VMSVGA display adapter is configured, it does not matter which display-adapter is configured, same effect for each.
No sound device is enabled.
I have ensured that hyper-V hypervisor is not enabled

There is a intel haxm type-2 hypervisor, which occasionally is run with android-emulator/qemu. My understanding is that it should not interfere. The joint installtion has worked before. Plus no qemu-VM is running. 

Save/Resume/Show/Hide has worked before.  


",gkamathh
19725,my VM Centos 8 starting kicking me out,Linux,VirtualBox 6.1.10,2020-07-15T18:35:09Z,2020-07-15T18:49:56Z,2020-07-15T18:49:56Z,"This morning I  had a pop up to reboot my Window server for updates.

Before I rebooted Windows,  I went over to my Linux CentOS 8 VM and gracefully shut it down.

After it was completely down, I rebooted Windows.

After windows came backup, I started my Centos 8 VM,  it took a very long time to start, but eventually my sing on GUI was up, I was able to login and open a terminal and ran a few commands,  suddenly  it closed my terminal and went back to the sing on GUI.

I went to Oracle VM VirtualBox Manager, clicked on File, then clicked on Check for updates,  I received ""You are already running the most recent version..."". Since the version number did not show, I looked at Help - About VirtualBox - I was running 6.1.8.

I starting googling and found that the latest version is 6.1.12, so I downloaded and installed it.  I also install the latest extpack and the latest guest additions.

After the CentOS 8 reboot, I was able to login and work for about 15 minutes before it kicked me out again, back to the sign on GUI.

",Saca
19722,Windows server 2019 Seamless Graphical problem,Windows,VirtualBox 6.1.10,2020-07-15T07:30:28Z,2020-07-15T07:30:28Z,2020-07-15T07:30:28Z,"Hello, There is annoying bug in Virtualbox 6.1.12
Steps to reproduce :

1-Install a clean Windows server 2019 x64 DataCenter With Desktop Experience (Personally tested 1809 and 1903)
2-Install VirtualBox Guest Additions 6.1.12, reboot pc.
3-Enter seamless mode.
4-Click on virtual machine Start Menu.
5-there is no start menu from guest on host.

[[Image(https://img.techpowerup.org/200715/annotation-2020-06-12-174715.png)]]

[[Image(https://img.techpowerup.org/200715/annotation-2020-06-12-174740.png)]]

problem exist in all UWP apps.
tested with VBOXVGA and VBOXSVGA.",VBuser1
19720,Rebooting causes colored stripes in the VM and a Guru meditation,all,VirtualBox 6.1.10,2020-07-15T02:15:48Z,2020-07-15T02:15:48Z,2020-07-15T02:15:48Z,"Every time I reboot my guest it has colored stripes on the top of the VM's screen then goes into guru meditation, this happens less on BIOS VMs, mostly happens on linux but also happens on Windows (Mostly 7,8,8.1)",OakBricks
19693,Failed to open a session the virtual machine in Win 7 Enterprise SP 1 64 Bit,Linux,VirtualBox 6.1.10,2020-07-02T04:10:29Z,2020-07-13T14:52:43Z,2020-07-13T14:52:43Z,"Dear all,

My windows:

Win 7 Enterprise 64 bit, SP1
Ram 8Gb
Virtualbox Latest ( 6.1.10 r138449 Qt5.6.2 )

when running to install Linux Mint, error show is below :

Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


please fix this is.

note: All my virtual already installed, error same.. could not run and failed session.


Thanks
",n3wkid2019
19692,not compatible with dual display with different dpi scaling,OSX Server,VirtualBox 6.1.10,2020-07-01T01:11:30Z,2020-07-09T03:26:34Z,2020-07-09T03:26:34Z,"I launched virtualbox in display 1 with 200% dpi scaling, when I drag the window to second screen with 100% dpi scaling the title of the window become very large.
instead, when drag from 100% to 200% every thing in 200% become very small.",liurunliang
19708,Memory Reference Error,Linux,VirtualBox 6.1.10,2020-07-08T21:04:33Z,2020-07-08T21:04:33Z,2020-07-08T21:04:33Z,"When running Ubuntu 20 (Linux Mint AND Budgie) I get a memory reference error.  Seems something is trying to write to 0x0000.

I've reproduced this in 6.1.9 and 6.1.10.  Host os is Windows 10.  HW is HP ZBook G5, 48GB RAM and 800+ GB disk.  ",grpark
19705,E_FAIL (0x80004005)-IMachine {85632c68-b5bb-4316-a900-5eb28d3413df},all,VirtualBox 6.1.10,2020-07-07T14:20:55Z,2020-07-07T14:23:19Z,2020-07-07T14:23:19Z,"Dear all,

Host : Windows 7 Enterprise 64bit,
Laptop Toshiba Satellite L645
Virtual box Version 6.1.10 r138449 (Qt5.6.2)
Avast AV already uninstall
Firewall already setup to allow this virtualbox
VT-X already disable (when the VT-X was enabled,that still error found on virtualbox)


when I was going running  the Windows 7 or Linux , error


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}.



I was forgot what is old version of Virtual box that installed before.
and with old version, virtual box is normal and not found error


Please fix it and help me....Thanks

",n3wkid2019
19690,Update for Microsoft Windows KB4560960 creates issues with VBox Guest,Windows,VirtualBox 6.1.10,2020-06-30T06:23:03Z,2020-07-06T14:11:29Z,2020-07-06T14:11:29Z,"Host: Windows 10
Guest: Windows 7 

After installing recent windows update on host, VBox guests started malfunctioning and could boot.

We then troubleshooted the issue and found that one of the windows update is creating issue which we uninstalled and now guests working smoothly

Here is the update created the issue.
Update for Microsoft Windows KB4560960

I request to test and release the fix for the same.

Thank you
Harsh",hsparekh
19702,在开启了  Hyper-V  的  Windows 10 上运行  VirtualBox  虚拟机，会发生崩溃,Linux,VirtualBox 6.1.10,2020-07-04T08:56:06Z,2020-07-04T12:39:53Z,2020-07-04T12:39:53Z,"我在  VirtualBox  上运行  Arch  Linux  操作系统时，虚拟机出现错误，导致我无法安装  Arch  Linux  操作系统。  

具体现象：虚拟机能够成功启动，但是尝试运行位于  Live  CD  的操作系统时，会发生崩溃

镜像源：  https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-10.4.0-amd64-DVD-3.iso

",FANminiworld
19699,Error opening virtual box after upgrade to 6.1,Windows,VirtualBox 6.1.10,2020-07-03T14:48:01Z,2020-07-03T14:48:01Z,2020-07-03T14:48:01Z,"Hello,

After upgrade to 6.1 i can no longer open my virtual box image that was working perfectly before this version. How can i make my Virtual box working again with the new version ? 

I will add the logfilesthat were created. 

Thanks",Johan1974
19680,Clipboard doesn't work for 6.1.10-138449 and Solaris 11.4,Solaris,VirtualBox 6.1.10,2020-06-25T12:03:23Z,2020-06-30T15:18:30Z,2020-06-30T15:18:30Z,"I've installed multiple times and the clipboard never works despite having enabled bidirectional. I have installed successfully before on a different laptop, earlier vbox and Linux Guest and the clipboard worked.
I don't know if it matters, but I get signature errors when installing the guest additions. See attached.",J_Nicholas
19665,OpenWRT locks up early in the kernel sequence on 6.1,Linux,VirtualBox 6.1.10,2020-06-14T18:50:19Z,2020-06-27T15:31:19Z,2020-06-27T15:31:19Z,"Tried in latest(r128535) build same thing. Something to do with # of CPUs - console log from kernel looks different between 2 vCPU and 1, but locks up regardless.
I'll attach the log and vdi, as it's reasonably small. Just in case something is wrong there, the vdi was built via ""convertfromraw"" of sourced from https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/openwrt-19.07.3-x86-64-combined-ext4.img.gz, which is the latest released openwrt distro.

The image boots fine on hyper-V, vmware and physical.
",novitk
19683,Window guest display glitch in VBoxSVGA with 3D acceleration mode,Windows,VirtualBox 6.1.10,2020-06-26T01:28:25Z,2020-06-26T01:28:25Z,2020-06-26T01:28:25Z,"Win7 host, nvidia gtx1650, Win7 guest, vbox v6.1.10 r138449, guest additions updated, VBoxSVGA with 3D acceleration mode on

The desktop of the VM is glitched, and the GUI some software don't work too.

https://youtu.be/GBEkxST6t-g

{{{
00:00:01.554556 VirtualBox VM 6.1.10 r138449 win.amd64 (Jun  4 2020 17:22:00) release log
00:00:01.554559 Log opened 2020-06-26T00:57:08.016600100Z
00:00:01.554560 Build Type: release
00:00:01.554562 OS Product: Windows 7
00:00:01.554563 OS Release: 6.1.7601
00:00:01.554564 OS Service Pack: 1
00:00:01.589427 DMI Product Name: To Be Filled By O.E.M.
00:00:01.598490 DMI Product Version: To Be Filled By O.E.M.
00:00:01.598834 Firmware type: BIOS
00:00:01.598838 Host RAM: 16313MB (15.9GB) total, 10592MB (10.3GB) available
00:00:01.598840 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:01.598840 Process ID: 5640
00:00:01.598841 Package type: WINDOWS_64BITS_GENERIC
00:00:01.602253 Installed Extension Packs:
00:00:01.602291   Oracle VM VirtualBox Extension Pack (Version: 6.1.10 r138449; VRDE Module: VBoxVRDP)
00:00:01.603077 Console: Machine state changed to 'Starting'
00:00:01.630079 Qt version: 5.6.2
00:00:01.632115 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:01.681454 SUP: Loaded VMMR0.r0 (C:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:01.681465 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:01.681466 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:01.682637 Guest OS type: 'Windows7_64'
00:00:01.683918 fHMForced=true - No raw-mode support in this build!
00:00:01.689061 File system of 'V:\VBox\Asteroid-7\Snapshots' (snapshots) is ntfs
00:00:01.689066 File system of 'V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi' is ntfs
00:00:01.694215 File system of 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (DVD) is ntfs
00:00:01.706365 Shared Clipboard: Service loaded
00:00:01.706371 Shared Clipboard: Mode: Bidirectional
00:00:01.706520 Shared Clipboard: Service running in normal mode
00:00:01.711359 Drag and drop service loaded
00:00:01.711364 Drag and drop mode: Host to Guest
00:00:01.718761 ************************* CFGM dump *************************
00:00:01.718763 [/] (level 0)
00:00:01.718765   CpuExecutionCap   <integer> = 0x0000000000000064 (100)
00:00:01.718767   EnablePAE         <integer> = 0x0000000000000001 (1)
00:00:01.718768   HMEnabled         <integer> = 0x0000000000000001 (1)
00:00:01.718768   MemBalloonSize    <integer> = 0x0000000000000000 (0)
00:00:01.718769   Name              <string>  = ""Asteroid-7"" (cb=11)
00:00:01.718770   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:01.718770   PageFusionAllowed <integer> = 0x0000000000000000 (0)
00:00:01.718771   RamHoleSize       <integer> = 0x0000000020000000 (536 870 912, 512 MB)
00:00:01.718772   RamSize           <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:01.718773   TimerMillies      <integer> = 0x000000000000000a (10)
00:00:01.718774   UUID              <bytes>   = ""39 73 89 c4 c7 e4 e2 45 9e 93 b0 52 54 ca 40 84"" (cb=16)
00:00:01.718779 
00:00:01.718780 [/CPUM/] (level 1)
00:00:01.718780   GuestCpuName       <string>  = ""host"" (cb=5)
00:00:01.718781   NestedHWVirt       <integer> = 0x0000000000000000 (0)
00:00:01.718781   PortableCpuIdLevel <integer> = 0x0000000000000000 (0)
00:00:01.718782   SpecCtrl           <integer> = 0x0000000000000000 (0)
00:00:01.718783 
00:00:01.718783 [/CPUM/IsaExts/] (level 2)
00:00:01.718783 
00:00:01.718784 [/DBGC/] (level 1)
00:00:01.718784   GlobalInitScript <string>  = ""C:\Users\Mercury\.VirtualBox/dbgc-init"" (cb=39)
00:00:01.718785   HistoryFile      <string>  = ""C:\Users\Mercury\.VirtualBox/dbgc-history"" (cb=42)
00:00:01.718786   LocalInitScript  <string>  = ""V:\VBox\Asteroid-7/dbgc-init"" (cb=29)
00:00:01.718786 
00:00:01.718787 [/DBGF/] (level 1)
00:00:01.718787   Path <string>  = ""V:\VBox\Asteroid-7/debug/;V:\VBox\Asteroid-7/;cache*V:\VBox\Asteroid-7/dbgcache/;C:\Users\Mercury\"" (cb=99)
00:00:01.718788 
00:00:01.718788 [/Devices/] (level 1)
00:00:01.718788 
00:00:01.718789 [/Devices/8237A/] (level 2)
00:00:01.718789 
00:00:01.718789 [/Devices/8237A/0/] (level 3)
00:00:01.718790   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718791 
00:00:01.718791 [/Devices/GIMDev/] (level 2)
00:00:01.718791 
00:00:01.718791 [/Devices/GIMDev/0/] (level 3)
00:00:01.718792   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718792 
00:00:01.718792 [/Devices/VMMDev/] (level 2)
00:00:01.718793 
00:00:01.718793 [/Devices/VMMDev/0/] (level 3)
00:00:01.718794   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718795   PCIDeviceNo   <integer> = 0x0000000000000004 (4)
00:00:01.718795   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718796   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718796 
00:00:01.718796 [/Devices/VMMDev/0/Config/] (level 4)
00:00:01.718797   GuestCoreDumpDir <string>  = ""V:\VBox\Asteroid-7\Snapshots"" (cb=29)
00:00:01.718798 
00:00:01.718798 [/Devices/VMMDev/0/LUN#0/] (level 4)
00:00:01.718798   Driver <string>  = ""HGCM"" (cb=5)
00:00:01.718799 
00:00:01.718799 [/Devices/VMMDev/0/LUN#0/Config/] (level 5)
00:00:01.718800   Object <integer> = 0x0000000006f1e190 (116 515 216)
00:00:01.718801 
00:00:01.718801 [/Devices/VMMDev/0/LUN#999/] (level 4)
00:00:01.718801   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718802 
00:00:01.718802 [/Devices/VMMDev/0/LUN#999/Config/] (level 5)
00:00:01.718803   First   <integer> = 0x0000000000000000 (0)
00:00:01.718803   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718804   papLeds <integer> = 0x0000000003bf5250 (62 870 096)
00:00:01.718804 
00:00:01.718805 [/Devices/acpi/] (level 2)
00:00:01.718805 
00:00:01.718805 [/Devices/acpi/0/] (level 3)
00:00:01.718806   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718806   PCIDeviceNo   <integer> = 0x0000000000000007 (7)
00:00:01.718807   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718807   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718808 
00:00:01.718808 [/Devices/acpi/0/Config/] (level 4)
00:00:01.718808   CpuHotPlug          <integer> = 0x0000000000000000 (0)
00:00:01.718809   FdcEnabled          <integer> = 0x0000000000000000 (0)
00:00:01.718809   HostBusPciAddress   <integer> = 0x0000000000000000 (0)
00:00:01.718810   HpetEnabled         <integer> = 0x0000000000000000 (0)
00:00:01.718810   IOAPIC              <integer> = 0x0000000000000001 (1)
00:00:01.718811   IocPciAddress       <integer> = 0x0000000000010000 (65 536)
00:00:01.718812   NumCPUs             <integer> = 0x0000000000000002 (2)
00:00:01.718812   Parallel0IoPortBase <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel0Irq        <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel1IoPortBase <integer> = 0x0000000000000000 (0)
00:00:01.718813   Parallel1Irq        <integer> = 0x0000000000000000 (0)
00:00:01.718814   Serial0IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:01.718814   Serial0Irq          <integer> = 0x0000000000000000 (0)
00:00:01.718815   Serial1IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:01.718815   Serial1Irq          <integer> = 0x0000000000000000 (0)
00:00:01.718816   ShowCpu             <integer> = 0x0000000000000001 (1)
00:00:01.718816   ShowRtc             <integer> = 0x0000000000000000 (0)
00:00:01.718817   SmcEnabled          <integer> = 0x0000000000000000 (0)
00:00:01.718817 
00:00:01.718817 [/Devices/acpi/0/LUN#0/] (level 4)
00:00:01.718818   Driver <string>  = ""ACPIHost"" (cb=9)
00:00:01.718818 
00:00:01.718819 [/Devices/acpi/0/LUN#0/Config/] (level 5)
00:00:01.718819 
00:00:01.718819 [/Devices/acpi/0/LUN#1/] (level 4)
00:00:01.718820   Driver <string>  = ""ACPICpu"" (cb=8)
00:00:01.718820 
00:00:01.718821 [/Devices/acpi/0/LUN#1/Config/] (level 5)
00:00:01.718821 
00:00:01.718821 [/Devices/ahci/] (level 2)
00:00:01.718822 
00:00:01.718822 [/Devices/ahci/0/] (level 3)
00:00:01.718823   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718823   PCIDeviceNo   <integer> = 0x000000000000000d (13)
00:00:01.718824   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718824   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718825 
00:00:01.718825 [/Devices/ahci/0/Config/] (level 4)
00:00:01.718825   Bootable  <integer> = 0x0000000000000001 (1)
00:00:01.718826   PortCount <integer> = 0x0000000000000002 (2)
00:00:01.718826 
00:00:01.718826 [/Devices/ahci/0/Config/Port0/] (level 5)
00:00:01.718827   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:01.718827 
00:00:01.718828 [/Devices/ahci/0/Config/Port1/] (level 5)
00:00:01.718828   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:01.718829 
00:00:01.718829 [/Devices/ahci/0/LUN#0/] (level 4)
00:00:01.718829   Driver <string>  = ""VD"" (cb=3)
00:00:01.718830 
00:00:01.718830 [/Devices/ahci/0/LUN#0/Config/] (level 5)
00:00:01.718831   BlockCache <integer> = 0x0000000000000001 (1)
00:00:01.718831   Format     <string>  = ""VDI"" (cb=4)
00:00:01.718832   Mountable  <integer> = 0x0000000000000000 (0)
00:00:01.718832   Path       <string>  = ""V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi"" (cb=72)
00:00:01.718833   Type       <string>  = ""HardDisk"" (cb=9)
00:00:01.718834   UseNewIo   <integer> = 0x0000000000000001 (1)
00:00:01.718834 
00:00:01.718834 [/Devices/ahci/0/LUN#0/Config/Parent/] (level 6)
00:00:01.718835   Format <string>  = ""VDI"" (cb=4)
00:00:01.718835   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{13d95ad9-6645-4a1a-a124-92c2acdf50aa}.vdi"" (cb=72)
00:00:01.718836 
00:00:01.718836 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/] (level 7)
00:00:01.718837   Format <string>  = ""VDI"" (cb=4)
00:00:01.718837   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{7d214b65-fb63-4e15-8517-9a4917deb9f7}.vdi"" (cb=72)
00:00:01.718838 
00:00:01.718838 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/] (level 8)
00:00:01.718839   Format <string>  = ""VDI"" (cb=4)
00:00:01.718839   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{3476a280-0799-4492-b80a-3f49e19328d1}.vdi"" (cb=72)
00:00:01.718840 
00:00:01.718840 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/] (level 9)
00:00:01.718841   Format <string>  = ""VDI"" (cb=4)
00:00:01.718842   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{5e7c1acb-8345-4fd8-8230-07cc65b4a7c1}.vdi"" (cb=72)
00:00:01.718842 
00:00:01.718842 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/] (level 10)
00:00:01.718843   Format <string>  = ""VDI"" (cb=4)
00:00:01.718844   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{d06b5feb-30d7-4c80-86f1-089b0159c660}.vdi"" (cb=72)
00:00:01.718844 
00:00:01.718844 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/] (level 11)
00:00:01.718845   Format <string>  = ""VDI"" (cb=4)
00:00:01.718846   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{00d317fd-75eb-4e52-bc4c-cd16a0cd44c6}.vdi"" (cb=72)
00:00:01.718846 
00:00:01.718846 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 12)
00:00:01.718847   Format <string>  = ""VDI"" (cb=4)
00:00:01.718848   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{702c5788-4b07-4854-afaa-11069398a139}.vdi"" (cb=72)
00:00:01.718848 
00:00:01.718848 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 13)
00:00:01.718850   Format <string>  = ""VDI"" (cb=4)
00:00:01.718850   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{bd5df2b9-1b74-4058-b5dc-de9c354c23c5}.vdi"" (cb=72)
00:00:01.718850 
00:00:01.718851 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 14)
00:00:01.718852   Format <string>  = ""VDI"" (cb=4)
00:00:01.718852   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{e14a6301-e7ab-4f38-919a-474ba2d2224f}.vdi"" (cb=72)
00:00:01.718853 
00:00:01.718853 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 15)
00:00:01.718854   Format <string>  = ""VDI"" (cb=4)
00:00:01.718854   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{bbae5348-a1c8-4eb7-801e-5a75b173af2f}.vdi"" (cb=72)
00:00:01.718855 
00:00:01.718855 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 16)
00:00:01.718857   Format <string>  = ""VDI"" (cb=4)
00:00:01.718857   Path   <string>  = ""V:\VBox\Asteroid-7\Snapshots/{281e38e5-ff1b-4d6c-9523-3794348b861e}.vdi"" (cb=72)
00:00:01.718857 
00:00:01.718858 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/] (level 17)
00:00:01.718859   Format <string>  = ""VDI"" (cb=4)
00:00:01.718859   Path   <string>  = ""V:\VBox\Asteroid-7\Asteroid-7.vdi"" (cb=34)
00:00:01.718860 
00:00:01.718860 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 18)
00:00:01.718862   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718862 
00:00:01.718862 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 17)
00:00:01.718864   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718864 
00:00:01.718864 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 16)
00:00:01.718865   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718866 
00:00:01.718866 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 15)
00:00:01.718867   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718868 
00:00:01.718868 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 14)
00:00:01.718869   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718869 
00:00:01.718870 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 13)
00:00:01.718871   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718871 
00:00:01.718871 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 12)
00:00:01.718872   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718873 
00:00:01.718873 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/Parent/VDConfig/] (level 11)
00:00:01.718874   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718874 
00:00:01.718875 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/Parent/VDConfig/] (level 10)
00:00:01.718876   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718876 
00:00:01.718876 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/Parent/VDConfig/] (level 9)
00:00:01.718877   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718877 
00:00:01.718878 [/Devices/ahci/0/LUN#0/Config/Parent/Parent/VDConfig/] (level 8)
00:00:01.718878   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718879 
00:00:01.718879 [/Devices/ahci/0/LUN#0/Config/Parent/VDConfig/] (level 7)
00:00:01.718880   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718880 
00:00:01.718880 [/Devices/ahci/0/LUN#0/Config/Plugins/] (level 6)
00:00:01.718881 
00:00:01.718881 [/Devices/ahci/0/LUN#0/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:01.718882   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:01.718883 
00:00:01.718883 [/Devices/ahci/0/LUN#0/Config/VDConfig/] (level 6)
00:00:01.718883   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:01.718884 
00:00:01.718884 [/Devices/ahci/0/LUN#1/] (level 4)
00:00:01.718885   Driver <string>  = ""SCSI"" (cb=5)
00:00:01.718885 
00:00:01.718885 [/Devices/ahci/0/LUN#1/AttachedDriver/] (level 5)
00:00:01.718886   Driver <string>  = ""VD"" (cb=3)
00:00:01.718886 
00:00:01.718886 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:01.718887   Format    <string>  = ""RAW"" (cb=4)
00:00:01.718888   Mountable <integer> = 0x0000000000000001 (1)
00:00:01.718888   Path      <string>  = ""C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso"" (cb=58)
00:00:01.718889   ReadOnly  <integer> = 0x0000000000000001 (1)
00:00:01.718889   Type      <string>  = ""DVD"" (cb=4)
00:00:01.718889   UseNewIo  <integer> = 0x0000000000000001 (1)
00:00:01.718890 
00:00:01.718890 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/Plugins/] (level 7)
00:00:01.718891 
00:00:01.718891 [/Devices/ahci/0/LUN#1/AttachedDriver/Config/Plugins/VDPluginCrypt/] (level 8)
00:00:01.718892   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:01.718892 
00:00:01.718893 [/Devices/ahci/0/LUN#999/] (level 4)
00:00:01.718893   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718894 
00:00:01.718894 [/Devices/ahci/0/LUN#999/Config/] (level 5)
00:00:01.718894   DeviceInstance        <string>  = ""ahci/0"" (cb=7)
00:00:01.718895   First                 <integer> = 0x0000000000000000 (0)
00:00:01.718895   Last                  <integer> = 0x0000000000000001 (1)
00:00:01.718896   pConsole              <integer> = 0x0000000003bf4990 (62 867 856)
00:00:01.718897   papLeds               <integer> = 0x0000000003bf4dd0 (62 868 944)
00:00:01.718898   pmapMediumAttachments <integer> = 0x0000000003bf5270 (62 870 128)
00:00:01.718898 
00:00:01.718899 [/Devices/apic/] (level 2)
00:00:01.718899 
00:00:01.718899 [/Devices/apic/0/] (level 3)
00:00:01.718900   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718900 
00:00:01.718900 [/Devices/apic/0/Config/] (level 4)
00:00:01.718901   IOAPIC  <integer> = 0x0000000000000001 (1)
00:00:01.718901   Mode    <integer> = 0x0000000000000002 (2)
00:00:01.718902   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.718902 
00:00:01.718902 [/Devices/e1000/] (level 2)
00:00:01.718903 
00:00:01.718903 [/Devices/e1000/0/] (level 3)
00:00:01.718904   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718904   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:01.718905   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718905   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718905 
00:00:01.718906 [/Devices/e1000/0/Config/] (level 4)
00:00:01.718906   AdapterType    <integer> = 0x0000000000000000 (0)
00:00:01.718907   CableConnected <integer> = 0x0000000000000001 (1)
00:00:01.718907   LineSpeed      <integer> = 0x0000000000000000 (0)
00:00:01.718907   MAC            <bytes>   = ""08 00 27 07 bb b0"" (cb=6)
00:00:01.718908 
00:00:01.718909 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:01.718909   Driver <string>  = ""NAT"" (cb=4)
00:00:01.718910 
00:00:01.718910 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:01.718911   AliasMode       <integer> = 0x0000000000000000 (0)
00:00:01.718911   BootFile        <string>  = ""Asteroid-7.pxe"" (cb=15)
00:00:01.718912   DNSProxy        <integer> = 0x0000000000000000 (0)
00:00:01.718912   Network         <string>  = ""10.0.2.0/24"" (cb=12)
00:00:01.718913   PassDomain      <integer> = 0x0000000000000001 (1)
00:00:01.718913   TFTPPrefix      <string>  = ""C:\Users\Mercury\.VirtualBox\TFTP"" (cb=34)
00:00:01.718914   UseHostResolver <integer> = 0x0000000000000000 (0)
00:00:01.718914 
00:00:01.718914 [/Devices/e1000/0/LUN#999/] (level 4)
00:00:01.718915   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718915 
00:00:01.718915 [/Devices/e1000/0/LUN#999/Config/] (level 5)
00:00:01.718916   First   <integer> = 0x0000000000000000 (0)
00:00:01.718917   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718917   papLeds <integer> = 0x0000000003bf5130 (62 869 808)
00:00:01.718918 
00:00:01.718918 [/Devices/hda/] (level 2)
00:00:01.718918 
00:00:01.718918 [/Devices/hda/0/] (level 3)
00:00:01.718919   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718919   PCIDeviceNo   <integer> = 0x0000000000000005 (5)
00:00:01.718920   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718920   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718921 
00:00:01.718921 [/Devices/hda/0/AudioConfig/] (level 4)
00:00:01.718922 
00:00:01.718922 [/Devices/hda/0/Config/] (level 4)
00:00:01.718922   DebugEnabled <integer> = 0x0000000000000000 (0)
00:00:01.718923 
00:00:01.718923 [/Devices/hda/0/LUN#0/] (level 4)
00:00:01.718923   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718924 
00:00:01.718924 [/Devices/hda/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.718925   Driver <string>  = ""DSoundAudio"" (cb=12)
00:00:01.718925 
00:00:01.718925 [/Devices/hda/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.718926   StreamName <string>  = ""Asteroid-7"" (cb=11)
00:00:01.718926 
00:00:01.718927 [/Devices/hda/0/LUN#0/Config/] (level 5)
00:00:01.718927   BufferSizeMs    <integer> = 0x0000000000000000 (0)
00:00:01.718928   DriverName      <string>  = ""DSoundAudio"" (cb=12)
00:00:01.718928   InputEnabled    <integer> = 0x0000000000000000 (0)
00:00:01.718929   OutputEnabled   <integer> = 0x0000000000000001 (1)
00:00:01.718929   PeriodSizeMs    <integer> = 0x0000000000000000 (0)
00:00:01.718930   PreBufferSizeMs <integer> = 0x00000000ffffffff (4 294 967 295)
00:00:01.718930 
00:00:01.718931 [/Devices/hda/0/LUN#1/] (level 4)
00:00:01.718931   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718932 
00:00:01.718932 [/Devices/hda/0/LUN#2/] (level 4)
00:00:01.718932   Driver <string>  = ""AUDIO"" (cb=6)
00:00:01.718933 
00:00:01.718933 [/Devices/i8254/] (level 2)
00:00:01.718933 
00:00:01.718934 [/Devices/i8254/0/] (level 3)
00:00:01.718934 
00:00:01.718935 [/Devices/i8254/0/Config/] (level 4)
00:00:01.718935 
00:00:01.718935 [/Devices/i8259/] (level 2)
00:00:01.718936 
00:00:01.718936 [/Devices/i8259/0/] (level 3)
00:00:01.718937   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718937 
00:00:01.718937 [/Devices/i8259/0/Config/] (level 4)
00:00:01.718938 
00:00:01.718938 [/Devices/ioapic/] (level 2)
00:00:01.718938 
00:00:01.718938 [/Devices/ioapic/0/] (level 3)
00:00:01.718939   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718939 
00:00:01.718940 [/Devices/ioapic/0/Config/] (level 4)
00:00:01.718940   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.718941 
00:00:01.718941 [/Devices/mc146818/] (level 2)
00:00:01.718941 
00:00:01.718941 [/Devices/mc146818/0/] (level 3)
00:00:01.718942 
00:00:01.718942 [/Devices/mc146818/0/Config/] (level 4)
00:00:01.718943   UseUTC <integer> = 0x0000000000000000 (0)
00:00:01.718943 
00:00:01.718943 [/Devices/parallel/] (level 2)
00:00:01.718944 
00:00:01.718944 [/Devices/pcarch/] (level 2)
00:00:01.718944 
00:00:01.718944 [/Devices/pcarch/0/] (level 3)
00:00:01.718945   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718945 
00:00:01.718946 [/Devices/pcarch/0/Config/] (level 4)
00:00:01.718946 
00:00:01.718946 [/Devices/pcbios/] (level 2)
00:00:01.718947 
00:00:01.718947 [/Devices/pcbios/0/] (level 3)
00:00:01.718948   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718948 
00:00:01.718948 [/Devices/pcbios/0/Config/] (level 4)
00:00:01.718950   APIC               <integer> = 0x0000000000000001 (1)
00:00:01.718950   BootDevice0        <string>  = ""IDE"" (cb=4)
00:00:01.718951   BootDevice1        <string>  = ""DVD"" (cb=4)
00:00:01.718951   BootDevice2        <string>  = ""NONE"" (cb=5)
00:00:01.718951   BootDevice3        <string>  = ""NONE"" (cb=5)
00:00:01.718952   FloppyDevice       <string>  = ""i82078"" (cb=7)
00:00:01.718952   HardDiskDevice     <string>  = ""piix3ide"" (cb=9)
00:00:01.718953   IOAPIC             <integer> = 0x0000000000000001 (1)
00:00:01.718953   LanBootRom         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom"" (cb=100)
00:00:01.718954   McfgBase           <integer> = 0x0000000000000000 (0)
00:00:01.718954   McfgLength         <integer> = 0x0000000000000000 (0)
00:00:01.718955   NumCPUs            <integer> = 0x0000000000000002 (2)
00:00:01.718955   PXEDebug           <integer> = 0x0000000000000000 (0)
00:00:01.718956   SataHardDiskDevice <string>  = ""ahci"" (cb=5)
00:00:01.718956   SataLUN1           <integer> = 0x0000000000000000 (0)
00:00:01.718957   UUID               <bytes>   = ""39 73 89 c4 c7 e4 e2 45 9e 93 b0 52 54 ca 40 84"" (cb=16)
00:00:01.718958   UuidLe             <integer> = 0x0000000000000000 (0)
00:00:01.718958 
00:00:01.718959 [/Devices/pcbios/0/Config/NetBoot/] (level 5)
00:00:01.718960 
00:00:01.718960 [/Devices/pcbios/0/Config/NetBoot/0/] (level 6)
00:00:01.718961   NIC           <integer> = 0x0000000000000000 (0)
00:00:01.718961   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718961   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:01.718962   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718962 
00:00:01.718963 [/Devices/pci/] (level 2)
00:00:01.718963 
00:00:01.718963 [/Devices/pci/0/] (level 3)
00:00:01.718964   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718964 
00:00:01.718964 [/Devices/pci/0/Config/] (level 4)
00:00:01.718965   IOAPIC <integer> = 0x0000000000000001 (1)
00:00:01.718965 
00:00:01.718965 [/Devices/pcibridge/] (level 2)
00:00:01.718966 
00:00:01.718966 [/Devices/pckbd/] (level 2)
00:00:01.718967 
00:00:01.718967 [/Devices/pckbd/0/] (level 3)
00:00:01.718967   Trusted <integer> = 0x0000000000000001 (1)
00:00:01.718968 
00:00:01.718968 [/Devices/pckbd/0/Config/] (level 4)
00:00:01.718968 
00:00:01.718969 [/Devices/pckbd/0/LUN#0/] (level 4)
00:00:01.718969   Driver <string>  = ""KeyboardQueue"" (cb=14)
00:00:01.718970 
00:00:01.718970 [/Devices/pckbd/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.718971   Driver <string>  = ""MainKeyboard"" (cb=13)
00:00:01.718971 
00:00:01.718971 [/Devices/pckbd/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.718972   Object <integer> = 0x0000000003b869e0 (62 417 376)
00:00:01.718973 
00:00:01.718973 [/Devices/pckbd/0/LUN#0/Config/] (level 5)
00:00:01.718974   QueueSize <integer> = 0x0000000000000040 (64)
00:00:01.718974 
00:00:01.718975 [/Devices/pckbd/0/LUN#1/] (level 4)
00:00:01.718975   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:01.718976 
00:00:01.718976 [/Devices/pckbd/0/LUN#1/AttachedDriver/] (level 5)
00:00:01.718977   Driver <string>  = ""MainMouse"" (cb=10)
00:00:01.718977 
00:00:01.718977 [/Devices/pckbd/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:01.718978   Object <integer> = 0x0000000003c5bed0 (63 291 088)
00:00:01.718978 
00:00:01.718979 [/Devices/pckbd/0/LUN#1/Config/] (level 5)
00:00:01.718979   QueueSize <integer> = 0x0000000000000080 (128)
00:00:01.718980 
00:00:01.718980 [/Devices/pcnet/] (level 2)
00:00:01.718981 
00:00:01.718981 [/Devices/serial/] (level 2)
00:00:01.718981 
00:00:01.718981 [/Devices/usb-ohci/] (level 2)
00:00:01.718982 
00:00:01.718982 [/Devices/usb-ohci/0/] (level 3)
00:00:01.718983   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718983   PCIDeviceNo   <integer> = 0x0000000000000006 (6)
00:00:01.718984   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718984   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718985 
00:00:01.718985 [/Devices/usb-ohci/0/Config/] (level 4)
00:00:01.718985 
00:00:01.718985 [/Devices/usb-ohci/0/LUN#0/] (level 4)
00:00:01.718986   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:01.718986 
00:00:01.718987 [/Devices/usb-ohci/0/LUN#0/Config/] (level 5)
00:00:01.718987 
00:00:01.718987 [/Devices/usb-ohci/0/LUN#999/] (level 4)
00:00:01.718988   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.718988 
00:00:01.718989 [/Devices/usb-ohci/0/LUN#999/Config/] (level 5)
00:00:01.718989   First   <integer> = 0x0000000000000000 (0)
00:00:01.718990   Last    <integer> = 0x0000000000000000 (0)
00:00:01.718990   papLeds <integer> = 0x0000000003bf5258 (62 870 104)
00:00:01.718991 
00:00:01.718991 [/Devices/vga/] (level 2)
00:00:01.718991 
00:00:01.718992 [/Devices/vga/0/] (level 3)
00:00:01.718992   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:01.718993   PCIDeviceNo   <integer> = 0x0000000000000002 (2)
00:00:01.718993   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:01.718993   Trusted       <integer> = 0x0000000000000001 (1)
00:00:01.718994 
00:00:01.718994 [/Devices/vga/0/Config/] (level 4)
00:00:01.718995   3DEnabled        <integer> = 0x0000000000000001 (1)
00:00:01.718995   CustomVideoModes <integer> = 0x0000000000000000 (0)
00:00:01.718996   FadeIn           <integer> = 0x0000000000000001 (1)
00:00:01.718996   FadeOut          <integer> = 0x0000000000000001 (1)
00:00:01.718997   HeightReduction  <integer> = 0x0000000000000000 (0)
00:00:01.718997   LogoFile         <string>  = """" (cb=1)
00:00:01.718998   LogoTime         <integer> = 0x0000000000000000 (0)
00:00:01.718998   MonitorCount     <integer> = 0x0000000000000001 (1)
00:00:01.718998   ShowBootMenu     <integer> = 0x0000000000000002 (2)
00:00:01.718999   VMSVGA3dEnabled  <integer> = 0x0000000000000001 (1)
00:00:01.718999   VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:01.719000   VRamSize         <integer> = 0x0000000010000000 (268 435 456, 256 MB)
00:00:01.719001 
00:00:01.719001 [/Devices/vga/0/LUN#0/] (level 4)
00:00:01.719002   Driver <string>  = ""MainDisplay"" (cb=12)
00:00:01.719002 
00:00:01.719002 [/Devices/vga/0/LUN#0/Config/] (level 5)
00:00:01.719003   Object <integer> = 0x0000000003c397b0 (63 150 000)
00:00:01.719003 
00:00:01.719004 [/Devices/vga/0/LUN#999/] (level 4)
00:00:01.719004   Driver <string>  = ""MainStatus"" (cb=11)
00:00:01.719005 
00:00:01.719005 [/Devices/vga/0/LUN#999/Config/] (level 5)
00:00:01.719006   First   <integer> = 0x0000000000000000 (0)
00:00:01.719006   Last    <integer> = 0x0000000000000000 (0)
00:00:01.719006   papLeds <integer> = 0x0000000003bf5268 (62 870 120)
00:00:01.719007 
00:00:01.719007 [/Devices/virtio-net/] (level 2)
00:00:01.719008 
00:00:01.719008 [/EM/] (level 1)
00:00:01.719008   TripleFaultReset <integer> = 0x0000000000000000 (0)
00:00:01.719009 
00:00:01.719009 [/GIM/] (level 1)
00:00:01.719009   Provider <string>  = ""HyperV"" (cb=7)
00:00:01.719010 
00:00:01.719010 [/HM/] (level 1)
00:00:01.719011   64bitEnabled       <integer> = 0x0000000000000001 (1)
00:00:01.719011   EnableLargePages   <integer> = 0x0000000000000001 (1)
00:00:01.719012   EnableNestedPaging <integer> = 0x0000000000000001 (1)
00:00:01.719012   EnableUX           <integer> = 0x0000000000000001 (1)
00:00:01.719013   EnableVPID         <integer> = 0x0000000000000001 (1)
00:00:01.719013   Exclusive          <integer> = 0x0000000000000000 (0)
00:00:01.719013   HMForced           <integer> = 0x0000000000000001 (1)
00:00:01.719014   IBPBOnVMEntry      <integer> = 0x0000000000000000 (0)
00:00:01.719014   IBPBOnVMExit       <integer> = 0x0000000000000000 (0)
00:00:01.719015   L1DFlushOnSched    <integer> = 0x0000000000000001 (1)
00:00:01.719015   L1DFlushOnVMEntry  <integer> = 0x0000000000000000 (0)
00:00:01.719016   MDSClearOnSched    <integer> = 0x0000000000000001 (1)
00:00:01.719016   MDSClearOnVMEntry  <integer> = 0x0000000000000000 (0)
00:00:01.719017   SpecCtrlByHost     <integer> = 0x0000000000000000 (0)
00:00:01.719017   UseNEMInstead      <integer> = 0x0000000000000000 (0)
00:00:01.719017 
00:00:01.719018 [/MM/] (level 1)
00:00:01.719018   CanUseLargerHeap <integer> = 0x0000000000000000 (0)
00:00:01.719018 
00:00:01.719019 [/NEM/] (level 1)
00:00:01.719019   Allow64BitGuests <integer> = 0x0000000000000001 (1)
00:00:01.719019 
00:00:01.719020 [/PDM/] (level 1)
00:00:01.719020 
00:00:01.719020 [/PDM/AsyncCompletion/] (level 2)
00:00:01.719021 
00:00:01.719021 [/PDM/AsyncCompletion/File/] (level 3)
00:00:01.719022 
00:00:01.719022 [/PDM/AsyncCompletion/File/BwGroups/] (level 4)
00:00:01.719022 
00:00:01.719022 [/PDM/BlkCache/] (level 2)
00:00:01.719023   CacheSize <integer> = 0x0000000000500000 (5 242 880, 5 MB)
00:00:01.719024 
00:00:01.719024 [/PDM/Devices/] (level 2)
00:00:01.719024 
00:00:01.719025 [/PDM/Devices/VBoxEhci/] (level 3)
00:00:01.719025   Path         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR3.DLL"" (cb=111)
00:00:01.719026   R0SearchPath <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:01.719027 
00:00:01.719027 [/PDM/Devices/VBoxNvme/] (level 3)
00:00:01.719027   Path         <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxNvmeR3.DLL"" (cb=111)
00:00:01.719028   R0SearchPath <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:01.719029 
00:00:01.719029 [/PDM/Drivers/] (level 2)
00:00:01.719029 
00:00:01.719030 [/PDM/Drivers/DrvHostWebcam/] (level 3)
00:00:01.719030   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL"" (cb=115)
00:00:01.719031 
00:00:01.719031 [/PDM/Drivers/VBoxC/] (level 3)
00:00:01.719031   Path <string>  = ""VBoxC"" (cb=6)
00:00:01.719032 
00:00:01.719032 [/PDM/NetworkShaper/] (level 2)
00:00:01.719032 
00:00:01.719033 [/PDM/NetworkShaper/BwGroups/] (level 3)
00:00:01.719033 
00:00:01.719033 [/PDM/USB/] (level 2)
00:00:01.719034 
00:00:01.719034 [/PDM/USB/VBoxUsbCardReader/] (level 3)
00:00:01.719035   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbCardReaderR3.DLL"" (cb=120)
00:00:01.719035 
00:00:01.719035 [/PDM/USB/VBoxUsbWebcam/] (level 3)
00:00:01.719036   Path <string>  = ""C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbWebcamR3.DLL"" (cb=116)
00:00:01.719036 
00:00:01.719036 [/TM/] (level 1)
00:00:01.719037   UTCOffset <integer> = 0x0000000000000000 (0)
00:00:01.719037 
00:00:01.719037 [/USB/] (level 1)
00:00:01.719038 
00:00:01.719038 [/USB/HidMouse/] (level 2)
00:00:01.719038 
00:00:01.719039 [/USB/HidMouse/0/] (level 3)
00:00:01.719039 
00:00:01.719039 [/USB/HidMouse/0/Config/] (level 4)
00:00:01.719040   Mode <string>  = ""absolute"" (cb=9)
00:00:01.719040 
00:00:01.719041 [/USB/HidMouse/0/LUN#0/] (level 4)
00:00:01.719041   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:01.719042 
00:00:01.719042 [/USB/HidMouse/0/LUN#0/AttachedDriver/] (level 5)
00:00:01.719043   Driver <string>  = ""MainMouse"" (cb=10)
00:00:01.719043 
00:00:01.719043 [/USB/HidMouse/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:01.719044   Object <integer> = 0x0000000003c5bed0 (63 291 088)
00:00:01.719045 
00:00:01.719045 [/USB/HidMouse/0/LUN#0/Config/] (level 5)
00:00:01.719046   QueueSize <integer> = 0x0000000000000080 (128)
00:00:01.719046 
00:00:01.719046 [/USB/USBProxy/] (level 2)
00:00:01.719047 
00:00:01.719047 [/USB/USBProxy/GlobalConfig/] (level 3)
00:00:01.719048 
00:00:01.719048 ********************* End of CFGM dump **********************
00:00:01.719154 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:01.719199 MM: cbHyperHeap=0x240000 (2359296)
00:00:01.720617 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:01.721430 CPUM: Matched host CPU INTEL 0x6/0x9e/0xd Intel_Core7_WhiskeyLake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:01.721460 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:01.721467 CPUM: Microcode revision 0x000000B4
00:00:01.721473 CPUM: Changing leaf 13[0]: EBX=0x340 -> 0x340, ECX=0x440 -> 0x340
00:00:01.721480 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD
00:00:01.721483 CPUM: MSR/CPUID reconciliation insert: 0x0000010a IA32_ARCH_CAPABILITIES
00:00:01.721487 CPUM: MSR fudge: 0x00000122 IA32_TSX_CTRL
00:00:01.721498 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:01.721588 PGM: Host paging mode: AMD64+PGE+NX
00:00:01.721592 PGM: PGMPool: cMaxPages=2304 (u64MaxPages=2084)
00:00:01.721594 PGM: pgmR3PoolInit: cMaxPages=0x900 cMaxUsers=0x1200 cMaxPhysExts=0x1200 fCacheEnable=true 
00:00:01.726617 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=100 u32UpdateIntervalNS=10000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x11 cCpus=6
00:00:01.726632 TM: GIP - u64CpuHz=2 904 021 402 (0xad17d99a)  SUPGetCpuHzFromGip => 2 904 021 402
00:00:01.726635 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2905911935(*) cErrors=0
00:00:01.726684 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x2 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2904184923(*) cErrors=0
00:00:01.726687 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2904021402(*) cErrors=0
00:00:01.726689 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x6 iGipCpu=0x5 i64TSCDelta=0 enmState=3 u64CpuHz=2904065034(*) cErrors=0
00:00:01.726691 TM: GIP - CPU: iCpuSet=0x4 idCpu=0x4 idApic=0x8 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2904574105(*) cErrors=0
00:00:01.726692 TM: GIP - CPU: iCpuSet=0x5 idCpu=0x5 idApic=0xa iGipCpu=0x4 i64TSCDelta=0 enmState=3 u64CpuHz=2904101058(*) cErrors=0
00:00:01.726723 TM: cTSCTicksPerSecond=2 904 021 402 (0xad17d99a) enmTSCMode=1 (VirtTscEmulated)
00:00:01.726724 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:01.727183 EMR3Init: fIemExecutesAll=false fGuruOnTripleFault=true 
00:00:01.727347 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_WhiskeyLake
00:00:01.727410 GIM: Using provider 'HyperV' (Implementation version: 0)
00:00:01.727415 GIM: HyperV: Reporting vendor as 'VBoxVBoxVBox'
00:00:01.727418 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:01.727522 AIOMgr: Default manager type is 'Async'
00:00:01.727525 AIOMgr: Default file backend is 'NonBuffered'
00:00:01.727685 BlkCache: Cache successfully initialized. Cache size is 5242880 bytes
00:00:01.727688 BlkCache: Cache commit interval is 10000 ms
00:00:01.727690 BlkCache: Cache commit threshold is 2621440 bytes
00:00:01.961806 PcBios: [SMP] BIOS with 2 CPUs
00:00:01.961820 PcBios: Using the 386+ BIOS image.
00:00:01.961866 PcBios: MPS table at 000e1300
00:00:01.962692 PcBios: Using LAN ROM 'C:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom' with a size of 0xc000 bytes
00:00:01.962730 PcBios: fCheckShutdownStatusForSoftReset=true   fClearShutdownStatusOnHardReset=true 
00:00:01.970013 SUP: Loaded VBoxDDR0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:01.970018 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xXXXXXXXXXXXXXXXX
00:00:01.970163 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:01.970312 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:01.970344 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:01.977390 Shared Folders service loaded
00:00:01.982206 Guest Control service loaded
00:00:02.018512 VGA: Using the 386+ BIOS image.
00:00:02.019790 VD: VDInit finished with VINF_SUCCESS
00:00:02.028356 DrvVD: Flushes will be ignored
00:00:02.028360 DrvVD: Async flushes will be passed to the disk
00:00:02.045804 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Asteroid-7.vdi' (flags 000c0781) created successfully
00:00:02.066049 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{281e38e5-ff1b-4d6c-9523-3794348b861e}.vdi' (flags 000c0781) created successfully
00:00:02.083186 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{bbae5348-a1c8-4eb7-801e-5a75b173af2f}.vdi' (flags 000c0781) created successfully
00:00:02.087823 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{e14a6301-e7ab-4f38-919a-474ba2d2224f}.vdi' (flags 000c0781) created successfully
00:00:02.090770 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{bd5df2b9-1b74-4058-b5dc-de9c354c23c5}.vdi' (flags 000c0781) created successfully
00:00:02.096234 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{702c5788-4b07-4854-afaa-11069398a139}.vdi' (flags 000c0781) created successfully
00:00:02.099833 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{00d317fd-75eb-4e52-bc4c-cd16a0cd44c6}.vdi' (flags 000c0781) created successfully
00:00:02.104616 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{d06b5feb-30d7-4c80-86f1-089b0159c660}.vdi' (flags 000c0781) created successfully
00:00:02.167689 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{5e7c1acb-8345-4fd8-8230-07cc65b4a7c1}.vdi' (flags 000c0781) created successfully
00:00:02.174179 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{3476a280-0799-4492-b80a-3f49e19328d1}.vdi' (flags 000c0781) created successfully
00:00:02.178266 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{7d214b65-fb63-4e15-8517-9a4917deb9f7}.vdi' (flags 000c0781) created successfully
00:00:02.183277 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{13d95ad9-6645-4a1a-a124-92c2acdf50aa}.vdi' (flags 000c0781) created successfully
00:00:02.189513 AIOMgr: Endpoint for file 'V:\VBox\Asteroid-7\Snapshots/{b35874c1-7329-4e59-94c2-693b26901b38}.vdi' (flags 000c0723) created successfully
00:00:02.191429 VD: Opening the disk took 161860523 ns
00:00:02.191492 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 211812352
00:00:02.191693 DrvVD: Flushes will be ignored
00:00:02.191698 DrvVD: Async flushes will be passed to the disk
00:00:02.193048 AIOMgr: Endpoint for file 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' (flags 000c0781) created successfully
00:00:02.193059 VD: Opening the disk took 104171 ns
00:00:02.193101 AHCI: LUN#1: CD/DVD
00:00:02.193244 AHCI#0: Reset the HBA
00:00:02.193248 VD#0: Cancelling all active requests
00:00:02.193287 E1000#0: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled RC=disabled
00:00:02.199074 NAT: Guest address guess set to 10.0.2.15 by initialization
00:00:02.207129 NAT: DNS#0: 119.29.29.29
00:00:02.207136 NAT: DNS#1: 223.6.6.6
00:00:02.207683 HDA: Asynchronous I/O enabled
00:00:02.207702 Audio: Initializing DirectSound audio driver
00:00:02.276547 DSound: Capture device currently is unavailable
00:00:02.276554 DSound: Error enumeration capture device '主声音捕获驱动程序', rc=VERR_GENERAL_FAILURE
00:00:02.290582 DSound: Capture device currently is unavailable
00:00:02.290589 DSound: Error enumeration capture device '主声音捕获驱动程序', rc=VERR_GENERAL_FAILURE
00:00:02.290594 Audio: Found 3 devices for driver 'DSoundAudio'
00:00:02.290597 Audio: Device '主声音驱动程序':
00:00:02.290599 Audio: 	Usage           = Output
00:00:02.290600 Audio: 	Flags           = DEFAULT
00:00:02.290602 Audio: 	Input channels  = 0
00:00:02.290603 Audio: 	Output channels = 2
00:00:02.290604 Audio: Device '扬声器 (Realtek High Definition Audio)':
00:00:02.290605 Audio: 	Usage           = Output
00:00:02.290606 Audio: 	Flags           = NONE
00:00:02.290608 Audio: 	Input channels  = 0
00:00:02.290609 Audio: 	Output channels = 2
00:00:02.290610 Audio: Device 'EB243Y A (NVIDIA High Definition Audio)':
00:00:02.290612 Audio: 	Usage           = Output
00:00:02.290613 Audio: 	Flags           = NONE
00:00:02.290614 Audio: 	Input channels  = 0
00:00:02.290615 Audio: 	Output channels = 2
00:00:02.290659 HDA: Codec reset
00:00:02.290665 HDA: Reset
00:00:02.290863 GIMDev: Registered Hyper-V hypercall page
00:00:02.290870 GIMDev: Registered Hyper-V TSC page
00:00:02.291047 VUSB: Attached 'HidMouse' to port 1 on RootHub#0 (FullSpeed)
00:00:02.291065 PGM: The CPU physical address width is 39 bits
00:00:02.291068 PGM: PGMR3InitFinalize: 4 MB PSE mask 0000007fffffffff -> VINF_SUCCESS
00:00:02.291190 TM: TMR3InitFinalize: fTSCModeSwitchAllowed=true 
00:00:02.291294 VMM: Thread-context hooks unavailable
00:00:02.291297 VMM: Warning! RTThreadPreemptIsPending() cannot be trusted!  Need to update kernel info?
00:00:02.291298 VMM: Kernel preemption is possible
00:00:02.291978 HM: fWorldSwitcher=0x0 (fIbpbOnVmExit=false fIbpbOnVmEntry=false fL1dFlushOnVmEntry=false); fL1dFlushOnSched=false fMdsClearOnVmEntry=false
00:00:02.291982 HM: Using VT-x implementation 3.0
00:00:02.291984 HM: Max resume loops                  = 1024
00:00:02.291984 HM: Host CR4                          = 0x506f8
00:00:02.291985 HM: Host EFER                         = 0xd01
00:00:02.291986 HM: MSR_IA32_SMM_MONITOR_CTL          = 0x0
00:00:02.291986 HM: MSR_IA32_FEATURE_CONTROL          = 0x5
00:00:02.291986 HM:   LOCK
00:00:02.291987 HM:   VMXON
00:00:02.291988 HM: MSR_IA32_VMX_BASIC                = 0xda040000000004
00:00:02.291988 HM:   VMCS id                           = 0x4
00:00:02.291989 HM:   VMCS size                         = 1024 bytes
00:00:02.291989 HM:   VMCS physical address limit       = None
00:00:02.291990 HM:   VMCS memory type                  = Write Back (WB)
00:00:02.291990 HM:   Dual-monitor treatment support    = true 
00:00:02.291991 HM:   OUTS & INS instruction-info       = true 
00:00:02.291991 HM:   Supports true-capability MSRs     = true 
00:00:02.291991 HM:   VM-entry Xcpt error-code optional = false
00:00:02.291992 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x7f00000016
00:00:02.291992 HM:   EXT_INT_EXIT
00:00:02.291992 HM:   NMI_EXIT
00:00:02.291993 HM:   VIRTUAL_NMI
00:00:02.291993 HM:   PREEMPT_TIMER
00:00:02.291993 HM:   POSTED_INT (must be cleared)
00:00:02.291994 HM: MSR_IA32_VMX_PROCBASED_CTLS       = 0xfff9fffe0401e172
00:00:02.291995 HM:   INT_WINDOW_EXIT
00:00:02.291995 HM:   USE_TSC_OFFSETTING
00:00:02.291995 HM:   HLT_EXIT
00:00:02.291996 HM:   INVLPG_EXIT
00:00:02.291996 HM:   MWAIT_EXIT
00:00:02.291996 HM:   RDPMC_EXIT
00:00:02.291997 HM:   RDTSC_EXIT
00:00:02.291997 HM:   CR3_LOAD_EXIT (must be set)
00:00:02.291997 HM:   CR3_STORE_EXIT (must be set)
00:00:02.291997 HM:   CR8_LOAD_EXIT
00:00:02.291998 HM:   CR8_STORE_EXIT
00:00:02.291998 HM:   USE_TPR_SHADOW
00:00:02.291998 HM:   NMI_WINDOW_EXIT
00:00:02.291998 HM:   MOV_DR_EXIT
00:00:02.291999 HM:   UNCOND_IO_EXIT
00:00:02.291999 HM:   USE_IO_BITMAPS
00:00:02.291999 HM:   MONITOR_TRAP_FLAG
00:00:02.291999 HM:   USE_MSR_BITMAPS
00:00:02.292000 HM:   MONITOR_EXIT
00:00:02.292000 HM:   PAUSE_EXIT
00:00:02.292000 HM:   USE_SECONDARY_CTLS
00:00:02.292000 HM: MSR_IA32_VMX_PROCBASED_CTLS2      = 0x5ffcff00000000
00:00:02.292001 HM:   VIRT_APIC_ACCESS
00:00:02.292001 HM:   EPT
00:00:02.292002 HM:   DESC_TABLE_EXIT
00:00:02.292002 HM:   RDTSCP
00:00:02.292002 HM:   VIRT_X2APIC_MODE
00:00:02.292002 HM:   VPID
00:00:02.292003 HM:   WBINVD_EXIT
00:00:02.292003 HM:   UNRESTRICTED_GUEST
00:00:02.292003 HM:   APIC_REG_VIRT (must be cleared)
00:00:02.292004 HM:   VIRT_INT_DELIVERY (must be cleared)
00:00:02.292005 HM:   PAUSE_LOOP_EXIT
00:00:02.292005 HM:   RDRAND_EXIT
00:00:02.292005 HM:   INVPCID
00:00:02.292005 HM:   VMFUNC
00:00:02.292006 HM:   VMCS_SHADOWING
00:00:02.292006 HM:   ENCLS_EXIT
00:00:02.292006 HM:   RDSEED_EXIT
00:00:02.292006 HM:   PML
00:00:02.292007 HM:   EPT_VE
00:00:02.292007 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292007 HM:   XSAVES_XRSTORS
00:00:02.292008 HM:   MODE_BASED_EPT_PERM
00:00:02.292008 HM:   SPPTP_EPT (must be cleared)
00:00:02.292008 HM:   PT_EPT (must be cleared)
00:00:02.292008 HM:   TSC_SCALING (must be cleared)
00:00:02.292009 HM:   USER_WAIT_PAUSE (must be cleared)
00:00:02.292009 HM:   ENCLV_EXIT (must be cleared)
00:00:02.292009 HM: MSR_IA32_VMX_ENTRY_CTLS           = 0x3ffff000011ff
00:00:02.292010 HM:   LOAD_DEBUG (must be set)
00:00:02.292010 HM:   IA32E_MODE_GUEST
00:00:02.292010 HM:   ENTRY_TO_SMM
00:00:02.292010 HM:   DEACTIVATE_DUAL_MON
00:00:02.292011 HM:   LOAD_PERF_MSR
00:00:02.292011 HM:   LOAD_PAT_MSR
00:00:02.292011 HM:   LOAD_EFER_MSR
00:00:02.292011 HM:   LOAD_BNDCFGS_MSR
00:00:02.292011 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292012 HM:   LOAD_RTIT_CTL_MSR (must be cleared)
00:00:02.292012 HM: MSR_IA32_VMX_EXIT_CTLS            = 0x1ffffff00036dff
00:00:02.292013 HM:   SAVE_DEBUG (must be set)
00:00:02.292013 HM:   HOST_ADDR_SPACE_SIZE
00:00:02.292013 HM:   LOAD_PERF_MSR
00:00:02.292013 HM:   ACK_EXT_INT
00:00:02.292014 HM:   SAVE_PAT_MSR
00:00:02.292014 HM:   LOAD_PAT_MSR
00:00:02.292014 HM:   SAVE_EFER_MSR
00:00:02.292014 HM:   LOAD_EFER_MSR
00:00:02.292015 HM:   SAVE_PREEMPT_TIMER
00:00:02.292015 HM:   CLEAR_BNDCFGS_MSR
00:00:02.292015 HM:   CONCEAL_VMX_FROM_PT
00:00:02.292015 HM:   CLEAR_RTIT_CTL_MSR (must be cleared)
00:00:02.292016 HM: MSR_IA32_VMX_TRUE_PINBASED_CTLS   = 0x7f00000016
00:00:02.292016 HM: MSR_IA32_VMX_TRUE_PROCBASED_CTLS  = 0xfff9fffe04006172
00:00:02.292017 HM: MSR_IA32_VMX_TRUE_ENTRY_CTLS      = 0x3ffff000011fb
00:00:02.292018 HM: MSR_IA32_VMX_TRUE_EXIT_CTLS       = 0x1ffffff00036dfb
00:00:02.292019 HM: MSR_IA32_VMX_MISC                 = 0x7004c1e7
00:00:02.292020 HM:   PREEMPT_TIMER_TSC                 = 0x7
00:00:02.292020 HM:   EXIT_SAVE_EFER_LMA                = true 
00:00:02.292020 HM:   ACTIVITY_STATES                   = 0x7 ( HLT SHUTDOWN SIPI_WAIT )
00:00:02.292021 HM:   INTEL_PT                          = true 
00:00:02.292021 HM:   SMM_READ_SMBASE_MSR               = true 
00:00:02.292021 HM:   CR3_TARGET                        = 0x4
00:00:02.292022 HM:   MAX_MSR                           = 0x0 ( 512 )
00:00:02.292022 HM:   VMXOFF_BLOCK_SMI                  = true 
00:00:02.292023 HM:   VMWRITE_ALL                       = true 
00:00:02.292023 HM:   ENTRY_INJECT_SOFT_INT             = 0x1
00:00:02.292023 HM:   MSEG_ID                           = 0x0
00:00:02.292023 HM: MSR_IA32_VMX_VMCS_ENUM            = 0x2e
00:00:02.292024 HM:   HIGHEST_IDX                       = 0x17
00:00:02.292024 HM: MSR_IA32_VMX_EPT_VPID_CAP         = 0xf0106734141
00:00:02.292025 HM:   RWX_X_ONLY
00:00:02.292025 HM:   PAGE_WALK_LENGTH_4
00:00:02.292025 HM:   EMT_UC
00:00:02.292025 HM:   EMT_WB
00:00:02.292026 HM:   PDE_2M
00:00:02.292026 HM:   PDPTE_1G
00:00:02.292026 HM:   INVEPT
00:00:02.292026 HM:   EPT_ACCESS_DIRTY
00:00:02.292026 HM:   ADVEXITINFO_EPT
00:00:02.292027 HM:   INVEPT_SINGLE_CONTEXT
00:00:02.292027 HM:   INVEPT_ALL_CONTEXTS
00:00:02.292027 HM:   INVVPID
00:00:02.292027 HM:   INVVPID_INDIV_ADDR
00:00:02.292028 HM:   INVVPID_SINGLE_CONTEXT
00:00:02.292028 HM:   INVVPID_ALL_CONTEXTS
00:00:02.292028 HM:   INVVPID_SINGLE_CONTEXT_RETAIN_GLOBALS
00:00:02.292028 HM: MSR_IA32_VMX_VMFUNC               = 0x1
00:00:02.292029 HM:   EPTP_SWITCHING
00:00:02.292029 HM: MSR_IA32_VMX_CR0_FIXED0           = 0x80000021
00:00:02.292029 HM: MSR_IA32_VMX_CR0_FIXED1           = 0xffffffff
00:00:02.292030 HM: MSR_IA32_VMX_CR4_FIXED0           = 0x2000
00:00:02.292030 HM: MSR_IA32_VMX_CR4_FIXED1           = 0x3727ff
00:00:02.292031 HM: APIC-access page physaddr         = 0x0000000026f73000
00:00:02.292031 HM: VCPU  0: MSR bitmap physaddr      = 0x00000004682e6000
00:00:02.292032 HM: VCPU  0: VMCS physaddr            = 0x00000004682e3000
00:00:02.292033 HM: VCPU  1: MSR bitmap physaddr      = 0x00000004682ea000
00:00:02.292033 HM: VCPU  1: VMCS physaddr            = 0x00000004682e7000
00:00:02.292034 HM: Guest support: 32-bit and 64-bit
00:00:02.292038 HM: Supports VMCS EFER fields         = true 
00:00:02.292038 HM: Enabled VMX
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:02.292042 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:02.292043 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:02.292044 HM: Enabled nested paging
00:00:02.292044 HM:   EPT flush type                  = Single context
00:00:02.292044 HM: Enabled unrestricted guest execution
00:00:02.292045 HM: Enabled large page support
00:00:02.292045 HM: Enabled VPID
00:00:02.292045 HM:   VPID flush type                 = Single context
00:00:02.292045 HM: Enabled VMX-preemption timer (cPreemptTimerShift=7)
00:00:02.292046 HM: VT-x/AMD-V init method: Local
00:00:02.292046 EM: Exit history optimizations: enabled=true  enabled-r0=true  enabled-r0-no-preemption=false
00:00:02.292088 PcBios: SATA LUN#0 LCHS=1024/255/63
00:00:02.292096 APIC: fPostedIntrsEnabled=false fVirtApicRegsEnabled=false fSupportsTscDeadline=false
00:00:02.292099 TMR3UtcNow: nsNow=1 593 133 028 754 100 100 nsPrev=0 -> cNsDelta=1 593 133 028 754 100 100 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 593 133 028 754 100 100)
00:00:02.292105 VMM: fUsePeriodicPreemptionTimers=false
00:00:02.292112 APIC: Enabling Hyper-V x2APIC compatibility mode
00:00:02.292177 CPUM: Logical host processors: 6 present, 6 max, 6 online, online mask: 000000000000003f
00:00:02.292178 CPUM: Physical host cores: 6
00:00:02.292178 ************************* CPUID dump ************************
00:00:02.292182          Raw Standard CPUID Leaves
00:00:02.292182      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:02.292183 Gst: 00000000/0000  00000016 756e6547 6c65746e 49656e69
00:00:02.292185 Hst:                00000016 756e6547 6c65746e 49656e69
00:00:02.292185 Gst: 00000001/0000  000906ed 00020800 d6da2203 178bfbff
00:00:02.292186 Hst:                000906ed 04100800 7ffafbbf bfebfbff
00:00:02.292187 Gst: 00000002/0000  76036301 00f0b6ff 00000000 00c30000
00:00:02.292188 Hst:                76036301 00f0b6ff 00000000 00c30000
00:00:02.292188 Gst: 00000003/0000  00000000 00000000 00000000 00000000
00:00:02.292189 Hst:                00000000 00000000 00000000 00000000
00:00:02.292189 Gst: 00000004/0000  04000121 01c0003f 0000003f 00000000
00:00:02.292190 Hst:                1c004121 01c0003f 0000003f 00000000
00:00:02.292191 Gst: 00000004/0001  04000122 01c0003f 0000003f 00000000
00:00:02.292191 Hst:                1c004122 01c0003f 0000003f 00000000
00:00:02.292192 Gst: 00000004/0002  04000143 00c0003f 000003ff 00000000
00:00:02.292193 Hst:                1c004143 00c0003f 000003ff 00000000
00:00:02.292193 Gst: 00000004/0003  04000163 02c0003f 00002fff 00000006
00:00:02.292194 Hst:                1c03c163 02c0003f 00002fff 00000006
00:00:02.292195 Gst: 00000004/0004  04000000 00000000 00000000 00000000
00:00:02.292195 Hst:                00000000 00000000 00000000 00000000
00:00:02.292196 Gst: 00000005/0000  00000000 00000000 00000000 00000000
00:00:02.292196 Hst:                00000040 00000040 00000003 11142120
00:00:02.292197 Gst: 00000006/0000  00000000 00000000 00000000 00000000
00:00:02.292198 Hst:                000027f7 00000002 00000009 00000000
00:00:02.292198 Gst: 00000007/0000  00000000 00842421 00000000 30000400
00:00:02.292199 Hst:                00000000 029c67af 40000000 bc000400
00:00:02.292199 Gst: 00000007/0001  00000000 00000000 00000000 00000000
00:00:02.292200 Hst:                00000000 00000000 00000000 00000000
00:00:02.292200 Gst: 00000008/0000  00000000 00000000 00000000 00000000
00:00:02.292201 Hst:                00000000 00000000 00000000 00000000
00:00:02.292201 Gst: 00000009/0000  00000000 00000000 00000000 00000000
00:00:02.292202 Hst:                00000000 00000000 00000000 00000000
00:00:02.292202 Gst: 0000000a/0000  00000000 00000000 00000000 00000000
00:00:02.292203 Hst:                07300804 00000000 00000000 00000603
00:00:02.292203 Gst: 0000000b/0000  00000000 00000001 00000100 00000000
00:00:02.292204 Hst:                00000001 00000001 00000100 00000004
00:00:02.292204 Gst: 0000000b/0001  00000001 00000002 00000201 00000000
00:00:02.292205 Hst:                00000004 00000006 00000201 00000004
00:00:02.292205 Gst: 0000000b/0002  00000000 00000000 00000002 00000000
00:00:02.292205 Hst:                00000000 00000000 00000002 00000004
00:00:02.292206 Gst: 0000000c/0000  00000000 00000000 00000000 00000000
00:00:02.292206 Hst:                00000000 00000000 00000000 00000000
00:00:02.292207 Gst: 0000000d/0000  00000007 00000340 00000340 00000000
00:00:02.292207 Hst:                0000001f 00000340 00000440 00000000
00:00:02.292208 Gst: 0000000d/0001  00000000 00000340 00000000 00000000
00:00:02.292208 Hst:                0000000f 00000340 00000100 00000000
00:00:02.292209 Gst: 0000000d/0002  00000100 00000240 00000000 00000000
00:00:02.292209 Hst:                00000100 00000240 00000000 00000000
00:00:02.292210 Gst: 0000000d/0003  00000000 00000000 00000000 00000000
00:00:02.292210 Hst:                00000040 000003c0 00000000 00000000
00:00:02.292211 Gst: 0000000d/0004  00000000 00000000 00000000 00000000
00:00:02.292211 Hst:                00000040 00000400 00000000 00000000
00:00:02.292212 Gst: 0000000d/0005  00000000 00000000 00000000 00000000
00:00:02.292212 Hst:                00000000 00000000 00000000 00000000
00:00:02.292212 Gst: 0000000d/0006  00000000 00000000 00000000 00000000
00:00:02.292213 Hst:                00000000 00000000 00000000 00000000
00:00:02.292213 Gst: 0000000d/0007  00000000 00000000 00000000 00000000
00:00:02.292214 Hst:                00000000 00000000 00000000 00000000
00:00:02.292214 Gst: 0000000d/0008  00000000 00000000 00000000 00000000
00:00:02.292215 Hst:                00000080 00000000 00000001 00000000
00:00:02.292215 Gst: 0000000d/0009  00000000 00000000 00000000 00000000
00:00:02.292216 Hst:                00000000 00000000 00000000 00000000
00:00:02.292230 Gst: 0000000e/0000  00000000 00000000 00000000 00000000
00:00:02.292231 Hst:                00000000 00000000 00000000 00000000
00:00:02.292231 Gst: 0000000f/0000  00000000 00000000 00000000 00000000
00:00:02.292232 Hst:                00000000 00000000 00000000 00000000
00:00:02.292232 Gst: 00000010/0000  00000000 00000000 00000000 00000000
00:00:02.292233 Hst:                00000000 00000000 00000000 00000000
00:00:02.292233 Gst: 00000011/0000  00000000 00000000 00000000 00000000
00:00:02.292234 Hst:                00000000 00000000 00000000 00000000
00:00:02.292234 Gst: 00000012/0000  00000000 00000000 00000000 00000000
00:00:02.292234 Hst:                00000000 00000000 00000000 00000000
00:00:02.292235 Gst: 00000013/0000  00000000 00000000 00000000 00000000
00:00:02.292235 Hst:                00000000 00000000 00000000 00000000
00:00:02.292236 Gst: 00000014/0000  00000000 00000000 00000000 00000000
00:00:02.292236 Hst:                00000001 0000000f 00000007 00000000
00:00:02.292237 Hst: 00000015/0000  00000002 000000f2 00000000 00000000
00:00:02.292237 Hst: 00000016/0000  00000b54 00001004 00000064 00000000
00:00:02.292238                                Name: GenuineIntel
00:00:02.292239                            Supports: 0x00000000-0x00000016
00:00:02.292241                              Family:  6 	Extended: 0 	Effective: 6
00:00:02.292241                               Model: 14 	Extended: 9 	Effective: 158
00:00:02.292242                            Stepping: 13
00:00:02.292243                                Type: 0 (primary)
00:00:02.292243                             APIC ID: 0x00
00:00:02.292244                        Logical CPUs: 2
00:00:02.292244                        CLFLUSH Size: 8
00:00:02.292245                            Brand ID: 0x00
00:00:02.292245 Features
00:00:02.292246   Mnemonic - Description                                  = guest (host)
00:00:02.292247   FPU - x87 FPU on Chip                                   = 1 (1)
00:00:02.292248   VME - Virtual 8086 Mode Enhancements                    = 1 (1)
00:00:02.292248   DE - Debugging extensions                               = 1 (1)
00:00:02.292249   PSE - Page Size Extension                               = 1 (1)
00:00:02.292250   TSC - Time Stamp Counter                                = 1 (1)
00:00:02.292250   MSR - Model Specific Registers                          = 1 (1)
00:00:02.292251   PAE - Physical Address Extension                        = 1 (1)
00:00:02.292252   MCE - Machine Check Exception                           = 1 (1)
00:00:02.292252   CX8 - CMPXCHG8B instruction                             = 1 (1)
00:00:02.292253   APIC - APIC On-Chip                                     = 1 (1)
00:00:02.292253   SEP - SYSENTER and SYSEXIT Present                      = 1 (1)
00:00:02.292254   MTRR - Memory Type Range Registers                      = 1 (1)
00:00:02.292255   PGE - PTE Global Bit                                    = 1 (1)
00:00:02.292255   MCA - Machine Check Architecture                        = 1 (1)
00:00:02.292256   CMOV - Conditional Move instructions                    = 1 (1)
00:00:02.292256   PAT - Page Attribute Table                              = 1 (1)
00:00:02.292257   PSE-36 - 36-bit Page Size Extension                     = 1 (1)
00:00:02.292258   PSN - Processor Serial Number                           = 0 (0)
00:00:02.292258   CLFSH - CLFLUSH instruction                             = 1 (1)
00:00:02.292259   DS - Debug Store                                        = 0 (1)
00:00:02.292259   ACPI - Thermal Mon. & Soft. Clock Ctrl.                 = 0 (1)
00:00:02.292260   MMX - Intel MMX Technology                              = 1 (1)
00:00:02.292261   FXSR - FXSAVE and FXRSTOR instructions                  = 1 (1)
00:00:02.292261   SSE - SSE support                                       = 1 (1)
00:00:02.292262   SSE2 - SSE2 support                                     = 1 (1)
00:00:02.292262   SS - Self Snoop                                         = 0 (1)
00:00:02.292263   HTT - Hyper-Threading Technology                        = 1 (1)
00:00:02.292264   TM - Therm. Monitor                                     = 0 (1)
00:00:02.292264   PBE - Pending Break Enabled                             = 0 (1)
00:00:02.292265   SSE3 - SSE3 support                                     = 1 (1)
00:00:02.292265   PCLMUL - PCLMULQDQ support (for AES-GCM)                = 1 (1)
00:00:02.292266   DTES64 - DS Area 64-bit Layout                          = 0 (1)
00:00:02.292267   MONITOR - MONITOR/MWAIT instructions                    = 0 (1)
00:00:02.292267   CPL-DS - CPL Qualified Debug Store                      = 0 (1)
00:00:02.292268   VMX - Virtual Machine Extensions                        = 0 (1)
00:00:02.292268   SMX - Safer Mode Extensions                             = 0 (0)
00:00:02.292269   EST - Enhanced SpeedStep Technology                     = 0 (1)
00:00:02.292269   TM2 - Terminal Monitor 2                                = 0 (1)
00:00:02.292270   SSSE3 - Supplemental Streaming SIMD Extensions 3        = 1 (1)
00:00:02.292271   CNTX-ID - L1 Context ID                                 = 0 (0)
00:00:02.292271   SDBG - Silicon Debug interface                          = 0 (1)
00:00:02.292272   FMA - Fused Multiply Add extensions                     = 0 (1)
00:00:02.292272   CX16 - CMPXCHG16B instruction                           = 1 (1)
00:00:02.292273   TPRUPDATE - xTPR Update Control                         = 0 (1)
00:00:02.292274   PDCM - Perf/Debug Capability MSR                        = 0 (1)
00:00:02.292274   PCID - Process Context Identifiers                      = 1 (1)
00:00:02.292275   DCA - Direct Cache Access                               = 0 (0)
00:00:02.292275   SSE4_1 - SSE4_1 support                                 = 1 (1)
00:00:02.292276   SSE4_2 - SSE4_2 support                                 = 1 (1)
00:00:02.292276   X2APIC - x2APIC support                                 = 0 (1)
00:00:02.292277   MOVBE - MOVBE instruction                               = 1 (1)
00:00:02.292278   POPCNT - POPCNT instruction                             = 1 (1)
00:00:02.292278   TSCDEADL - Time Stamp Counter Deadline                  = 0 (1)
00:00:02.292279   AES - AES instructions                                  = 1 (1)
00:00:02.292279   XSAVE - XSAVE instruction                               = 1 (1)
00:00:02.292280   OSXSAVE - OSXSAVE instruction                           = 0 (1)
00:00:02.292281   AVX - AVX support                                       = 1 (1)
00:00:02.292281   F16C - 16-bit floating point conversion instructions    = 0 (1)
00:00:02.292282   RDRAND - RDRAND instruction                             = 1 (1)
00:00:02.292282   HVP - Hypervisor Present (we're a guest)                = 1 (0)
00:00:02.292283 Structured Extended Feature Flags Enumeration (leaf 7):
00:00:02.292283   Mnemonic - Description                                  = guest (host)
00:00:02.292284   FSGSBASE - RDFSBASE/RDGSBASE/WRFSBASE/WRGSBASE instr.   = 1 (1)
00:00:02.292284   TSCADJUST - ",Mercury233
19676,Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel,Linux,VirtualBox 6.1.10,2020-06-20T12:35:32Z,2020-06-20T12:35:32Z,2020-06-20T12:35:32Z,"Crashes Program after pressing Ctrl+R(Restart) and using the bottom panel
Video: https://youtu.be/MdocMGLR2_M
Restarting W/O crashes on Windows 95.
Bliss OS (Linux Android) Restarting Crashes.
Bottom Panel crashes on all systems and many Virtual Box versions (6.X.X) (MS-DOS,Linux,OS/2 e.t.c)",Danik2343
19675,DHCP server mac address conflicts with nat-host mac-address,Linux,VirtualBox 6.1.10,2020-06-19T19:56:40Z,2020-06-19T19:56:40Z,2020-06-19T19:56:40Z,"
https://gitlab.alpinelinux.org/alpine/aports/-/issues/11669

When the two mac-addresses of the dhcp server and the emulated-host interface in NatNetwork are different, the arp cache may end up with the mac address of host entered as that from the dhcp. WHen that happens further communcation with host (CIFS/ssh) fails.

The eesolution was to set the dhcp server from the default 10.1.x.2 to 10.1.x.5. Then mac addresses don't clash

There should be a vboxmanage setting to set the mac address of the 
host-ip and of the dhcp-server-ip ",gkamathh
19671,"VirtualBoxVM crash, rtR3WinUnhandledXcptFilter caught an exception",Linux,VirtualBox 6.1.10,2020-06-19T08:48:49Z,2020-06-19T08:48:49Z,2020-06-19T08:48:49Z,"At time VirtualBoxVM.exe crashes with a pop-up, ""The instruction at '0xXX' referenced memory at '0xXX'. The memory could not be read.

And this issue can be easily reproduced if I use Google chrome within VM.

Vbox is installed in Window 10 & Ubuntu 18.04 is installed Vbox.

Hereby I'm attaching the log file as well.",pearleye
19668,Result Code: E_INVALIDARG (0x80070507),other,VirtualBox 6.1.10,2020-06-16T01:04:22Z,2020-06-16T01:04:22Z,2020-06-16T01:04:22Z,"Hi,

im having trouble installing the pyimagesearch ova file. i have installed and reinstalled VM box a few times now and have used different unzip programmes ( currently recommended to use 7 zip). i get the same message which i understand could be to do with disk spare capacity. i made space and reinstalled with the same output. it took maybe 45 seconds to come up with the error code. I moved the installation to my D drive and now the error message comes up instantaneously. Same error. Copy of settings in the attached file,

Any ideas?

Matt",Matt Lumb
19655,Linux guest crashes if VboxAdditions are installed,Linux,VirtualBox 6.1.10,2020-06-11T03:46:53Z,2020-06-15T07:31:06Z,2020-06-15T07:31:06Z,"Installing guest additions on LinuxMint 19.3 and Debian 10 results in a crash on startup of the VM.
The vboxadd.service will not start.
If the guest additions are removed the guest starts successfully.",S.Pendl
19666,I tried to install Latest Kali linux on Latest Virtual Box. i am not able to get installed on to my Windows laptop,Linux,VirtualBox 6.1.10,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,,Universal007
19643,Shift key status leaking from Guest to Host,Windows,VirtualBox 6.1.10,2020-06-08T02:26:20Z,2020-06-11T10:28:15Z,2020-06-11T10:28:15Z,"If a VBox session is running and has focus, and an app in that guest session has focus, e.g. TextPad, and the shift key is pushed, you can push say a and TextPad displays A, so it has responded to the shift. 

An app running in the host that is monitoring for the shift using the standard GetAsyncKeyState function receives notification that the shift key is down and thus will respond to it.

I believed the keybard, when captured, should act on all keyboard actions, and not be left for the host (I guess certain reserved keystrokes would be exempt).

This same scenario works fine on VMWare, which is what I am changing from - has worked for many years.

I cannot provide a workaround.

I can provide a program if required to monitor the shift status on the host.",Ken S
19651,DNS not working with NAT on some networks.,Linux,VirtualBox 6.1.10,2020-06-09T12:39:59Z,2020-06-09T12:39:59Z,2020-06-09T12:39:59Z,"Host is Win10, Guest is Debian 10.  Network set to NAT with TCP port 22 forwarded (though ssh will not work either)

Internet access worked fine until I changed WIFI networks. DNS does not seem to work. I can ping the DNS server, but DNS resolving does not work.  I've noticed some strange patterns.  At home it works fine. When I connect to my cellphone hotspot while at home everything worked too. At my hotel, at first it would not work. Then trying at my remote office guest wifi network, it also would not work. Then trying my cellphone hotspot mode, it also would not work. However, upon returning back to my hotel, it suddenly worked. I have the exact same pattern with trying to connect my wireguard vpn. Note back at the hotel, once I connect the vpn, dns stops working, it is unable to contact the dns server on my vpn, eventhough the host is able to.  Virtualbox sees the network changes, debian updates the network configuration, I can ping addresses outside, but dns fails with the ICMP issue. I've noticed that the DNS issue is ok if I switch to a bridged network. Unfortunately, some networks will only give me one IP so getting it to work with NAT is preferred.


In the VM log, I see:
{{{
00:00:18.130180 NAT: Link up
00:00:19.424766 NAT: DHCP offered IP address 10.0.2.15
}}}
On the guest, in network manager, it has a 10.0.2.15 IP address and is able to get DNS servers matching what I have on the host. /etc/resolv.conf has the correct servers
I have tried rebooting the VM. I've tried turning off the firewall on the host.


/etc/resolv.conf:
{{{
nameserver 1.1.1.1
}}}
ping 1.1.1.1 works
{{{
11:38:39.397764 IP 10.0.2.15 > 1.1.1.1: ICMP echo request, id 2960, seq 2, length 64
11:38:39.436573 IP 1.1.1.1 > 10.0.2.15: ICMP echo reply, id 2960, seq 2, length 64
}}}
dig @1.1.1.1 google.com does not work
{{{
11:38:43.814134 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:43.814861 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
11:38:45.697058 IP 10.0.2.15.50263 > 172.30.0.27.53: 32978+ AAAA? clients3.google.com. (37)
11:38:45.697650 IP 10.0.2.15.46410 > 172.30.0.27.53: 56459+ A? clients3.google.com. (37)
11:38:45.698116 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:45.698446 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:48.814785 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:48.816463 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
}}}",eng3
19645,Win7 VM (from p2v) freezes at random intervals,Windows,VirtualBox 6.1.10,2020-06-08T12:04:53Z,2020-06-08T12:46:06Z,2020-06-08T12:46:06Z,"I have a Win7 VM which is a P2V result from a laptop (i used VMWare Converter Standalone for the task). I then created a new VBox VM and used the .VMDK as a HDD.

I turned on the VM, let it discover all the drivers it wanted, restarted, etc. Finally i installed VBox drivers from the VM, restarted and everything seemed to work OK. Also performed several old drivers cleanup (uninstallations and removals from device driver), to minimize possible issues.

The VM works fine, except that after some time (randomly, usually 10-20 minutes), it just freezes. VBox's window is responsive but the guest OS is completely frozen. Trying to close the VM from the VBox's close window button, i select ""Send the shutdown signal"" and then press OK. It waits a few seconds and then it just closes the window.

Of course, the next time i start it, Windows report they had not been shutdown properly the last time. Also, the original laptop works just fine.",Wand
21023,Trying to run bluestacks in  vbox - cant increase cpu cores inside my bluestacks,other,VirtualBox 6.1.14,2022-07-18T04:39:22Z,2022-07-18T04:39:22Z,2022-07-18T04:39:22Z,"'''vbox is running win 10 home
 vbox is hyper v enabled in settings 
 cpu is 6 and ram is 8000'''


'''I am unable to increase my CPU cores in msi app player''' ( a bluestacks emulator) using windows 10 both in host and inside my virtual box to run msi app player

when i enable hyper v settings from app and features settings in windows 10 i get an error your pc doesn't support hardware assisted virtualization.

Attachment screen shots of my vbox and msi app player)
[https://drive.google.com/drive/folders/1uyX9agIlk3C0wjAKJe3tmf3g4tqKZWZq?usp=sharing]",adamya
20004,Windows Server 2012 R2 guest freezes after each resume and some reboots,Windows,VirtualBox 6.1.14,2020-10-27T19:54:38Z,2020-12-29T15:14:03Z,2020-12-29T15:14:03Z,"I have a Windows Server 2012 R2 guest I have used for several months, within the last month I began experiencing intermittent freeze ups of the guest.  I would have to power it down and restart.  Sometimes it would be stable the rest of the day but freeze after resuming it the next day.  Now it is freezing after every resume and sometime after restart.  I've gone back a few snapshots but not change.  Checking for updates says I am on the latest version.  No 3D acceleration enabled.  Host is Windows 10 Pro fully patched.  Guest if fully patched.  Minidump and log attached.",David Shower
20061,"""Permission denied"" error at linux-guest on Windows10-host when execute a file on a shared folders immediately after creation or 'chmod +x'",Linux,VirtualBox 6.1.14,2020-11-24T10:45:10Z,2020-11-24T10:45:10Z,2020-11-24T10:45:10Z,"
Following script reproduces the error on my virtual linux-machine when working on a share folder (in my case the '/vagrant'):

Script:


{{{

set -x

# switch to shared folder
cd /vagrant/ || exit 1

# create simple script
echo ""echo 'Hello World'"">PrintHelloWorld.sh
cat PrintHelloWorld.sh || exit 1
ls -l PrintHelloWorld.sh || exit 1

echo ""start failing tests...""
touch PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +x PrintHelloWorld.sh
./PrintHelloWorld.sh

chmod +r PrintHelloWorld.sh
./PrintHelloWorld.sh
}}}


Output:


{{{
++ cd /vagrant/
++ echo 'echo '\''Hello World'\'''
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ls -l PrintHelloWorld.sh
-rwxrwxrwx 1 vagrant vagrant 19 Nov 24  2020 PrintHelloWorld.sh
++ echo 'start failing tests...'
start failing tests...
++ touch PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 14: ./PrintHelloWorld.sh: Permission denied
++ chmod +x PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 17: ./PrintHelloWorld.sh: Permission denied
++ chmod +r PrintHelloWorld.sh
++ ./PrintHelloWorld.sh
/vagrant/RunCommands.sh: line 20: ./PrintHelloWorld.sh: Permission denied
}}}


The second part of the script shows some 'workarounds' to the problem:


{{{
echo ""start successful tests...""
touch PrintHelloWorld.sh
sleep 1
./PrintHelloWorld.sh

touch PrintHelloWorld.sh
cat PrintHelloWorld.sh
./PrintHelloWorld.sh

echo ""echo 'Hello World'"">PrintHelloWorld2.sh
./PrintHelloWorld2.sh

echo ""cleanup...""
rm PrintHelloWorld.sh
rm PrintHelloWorld2.sh

}}}


and creates following output:


{{{
++ echo 'start successful tests...'
start successful tests...
++ touch PrintHelloWorld.sh
++ sleep 1
++ ./PrintHelloWorld.sh
Hello World
++ touch PrintHelloWorld.sh
++ cat PrintHelloWorld.sh
echo 'Hello World'
++ ./PrintHelloWorld.sh
Hello World
++ echo 'echo '\''Hello World'\'''
++ ./PrintHelloWorld2.sh
Hello World
++ echo cleanup...
cleanup...
++ rm PrintHelloWorld.sh
++ rm PrintHelloWorld2.sh
}}}

The complete repro-environment including script and logs are attached.



",progger98
20045,Install Debian not run,Linux,VirtualBox 6.1.14,2020-11-17T08:18:35Z,2020-11-17T08:18:35Z,2020-11-17T08:18:35Z,Installation of Debian will not run with VirtualBox 6.1.14r140239,christophedlr34
19948,VirtualBox 6.1.14 Stop responding.,Windows,VirtualBox 6.1.14,2020-10-08T09:10:03Z,2020-11-09T16:27:35Z,2020-11-09T16:27:35Z,"The program VirtualBox.exe version 6.1.14.40239 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 1658
 Start Time: 01d69d5160d6c373
 Termination Time: 31
 Application Path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
 Report Id: ae63b5da-a309-46c2-aad5-d4d1807b745e
 Faulting package full name: 
 Faulting package-relative application ID: 
 Hang type: Unknown",sakurayz
19907,"Starting VM causes 100% load on one cpu in NT-Kernel, even after VM exit",all,VirtualBox 6.1.14,2020-09-21T16:50:07Z,2020-11-03T21:15:43Z,2020-11-03T21:15:43Z,"Observe in Host task manager, that ""System"" process works normally. Everything idle.

Simply start some VM (tested Fedora 32 and Windows 10 1909 guest). Wait until its booted and logged in (Guest additions installed and loaded).

Observe in Host task manager, that ""System"" (ntoskrnl.exe) process fully loads 1 core. This is in addition to the VM process itself.

Shutdown VM.

High load can still be observed and is persistent until host is rebooted.

I tried to reproduce this with same VMs imported to another host, but failed. Seemingly its somehow connected to specific host configuration/hardware. host hardware also is relatively new.
However it is 100% reproducible on this host and always triggered by staring some VM.",theRman
19997,"Nested virtualization, Windows 8.1 64bit, multiple CPUs lead to crash",Windows,VirtualBox 6.1.14,2020-10-25T14:03:56Z,2020-10-25T14:03:56Z,2020-10-25T14:03:56Z,"Forum topic:[https://forums.virtualbox.org/viewtopic.php?f=6&t=100373]
Host Machie: Windows 10 64bit (i9 9900K 8core)
Guest Machine1: Debian 10 64bit (4core allocated)
Guest Machine2: Windows 8.1 64bit

Host Machie contains Guest Machine1, and Guest Machine1 contains Guest Machine2, it's nested virtualization.

When I run Windows 8.1 64bit in Host Machie with multiple CPUs, no crash, everything is fine.
But when I run Windows 8.1 64bit in Guest Machine1, I can only allocate 1 cpu, if more then 1 cpu are allocated, it will crash after I click start.",larisa_serova
19873,VMSVGA: 1920x1080 resolution not available at boot (?),Linux,VirtualBox 6.1.14,2020-09-09T12:46:39Z,2020-10-23T01:45:38Z,2020-10-23T01:45:38Z,"As I've reported in some other tickets, I have a ''Oracle Linux Server release 7.8'' VM running on ''Windows 10''.[[br]]
The ''Video Memory'' is set to ''128MB'' and the ''Graphics Controller'' to ''VMSVGA''.[[br]]
The VM starts in ''Full-screen Mode'' on my second display which is set to 1920x1080.

After upgrading from ''6.1.6'' to ''6.1.10'' (I've skipped ''6.1.8'') I have the following problem: the greeter (lightdm) doesn't span the whole maximized VM window because the resolution is lower, but that should not be the problem, as far as I can remember this always happened on the first display of the greeter after boot.[[br]]
But after logging in the screen remains black with a visible mouse cursor instead of displaying my desktop at 1920x1080.

The workaround I'm using is sending the guest into runlevel 3 and then again into runlevel 5 so Xorg gets restarted and after doing that I can login successfully into my desktop at the desired resolution.[[br]]
So I tool a look at Xorg.0.log soon after boot and then after the telinit workaround.[[br]]
I think that the relevant differences are:
{{{
94c94
<  (II) vmware(0): Modeline ""800x600""x60.0   42.75  800 850 900 950  600 650 700 750 -hsync +vsync (45.0 kHz eP)
---
>  (II) vmware(0): Modeline ""1920x1080""x60.0  152.77  1920 1970 2020 2070  1080 1130 1180 1230 -hsync +vsync (73.8 kHz eP)
129c129
<  (II) vmware(0): Output Virtual1 using initial mode 800x600 +0+0
---
>  (II) vmware(0): Output Virtual1 using initial mode 1920x1080 +0+0
}}}

So it seems that 800x600 is available soon after boot while 1920x1080 is not and, after restarting Xorg, the other way around.[[br]]
I've tried with Acceleration enabled and disabiled with the same result.

I also tried with VBOXSVGA but it has far more Modeline than VMSVGA, including 1920x1080, so there is no such problem with in this case.[[br]]


P.S.[[br]]
I don't know if it's something related to the problem, since I moved to 6.1 and switched to VMSVGA if missing with the following two commands (see also Ticket #19392), but it seems they aren't working anymore:
{{{
VBoxManage.exe setextradata ''<vmname>'' CustomVideoMode1 1920x1080x32
VBoxManage controlvm ''<vmname>'' setvideomodehint 1920 1080 32
}}}
anyway the screen was set to the higher resolution available after login and not black.",alealeale
19982,Crash when using vscode on linux guest,Linux,VirtualBox 6.1.14,2020-10-20T17:19:14Z,2020-10-20T17:19:14Z,2020-10-20T17:19:14Z,"Hello,

VB crashes when I use vscode on a linux ( Ubuntu ) guest. It crashes when I right click to display a menu.
I join the crash  logs and a copy of the error message ( ""memory state cannot be written"" ). Is this enough to start to debug or do you need more information ? 

Thanks !

Crash logs : 

151:19:24.402862 AIOMgr: Async flushes not supported
152:49:24.051989 
152:49:24.051991 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000004184!!!
152:49:24.053107 
152:49:24.053108 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffc189728c2
152:49:24.053118 ExceptionInformation[0]=0000000000000001
152:49:24.053124 ExceptionInformation[1]=0000000000000000
152:49:24.053128 
152:49:24.053129 cs:rip=0033:00007ffc189728c2
152:49:24.053149 ss:rsp=002b:00000000cacbf560 rbp=00000000cacbf610
152:49:24.053154 rax=00000000cdeb87c0 rcx=0000000000000000 rdx=0000000082751090 rbx=0000000082751070
152:49:24.053159 rsi=0000000219a24c00 rdi=0000000219a24c00 rsp=00000000cacbf560 rbp=00000000cacbf610
152:49:24.053165 r8 =0000000000000000 r9 =0000000082751450 r10=0000000000000000 r11=00000000cacbf6a0
152:49:24.053170 r12=000000026a000770 r13=0000000000000000 r14=000000026a000080 r15=00000000cd680f40
152:49:24.053175 ds=002b es=002b fs=0053 gs=002b eflags=00010206
152:49:24.053180 p1home=0000000000000000 p2home=0000000000000000 pe3home=0000000082751070
152:49:24.053185 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
152:49:24.053189    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
152:49:24.053194 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
152:49:24.053202 
152:49:24.053203 Stack 00000000cacbe440, dumping 0x1bc0 bytes (low=00000000cabc0000, high=00000000cacc0000)
152:49:24.054088 00000000cacbe440/0000: 40 e4 cb ca 00 00 00 00-73 74 61 63 6b 6d 61 72 @.......stackmar
152:49:24.054818 00000000cacbe450/0010: 6b 65 72 00 00 00 00 00-00 10 02 00 00 00 00 00 ker.............
152:49:24.054825 00000000cacbe460/0020: 00 00 00 00 00 00 00 00-80 d7 75 54 fc 7f 00 00 ..........uT....
152:49:24.054831 00000000cacbe470/0030: 01 00 00 00 00 00 00 00-ff ff ff ff ff ff ff ff ................
152:49:24.054839 00000000cacbe480/0040: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054845 00000000cacbe490/0050: d0 59 c2 fa fb 7f 00 00-50 f8 cb ca 00 00 00 00 .Y......P.......
152:49:24.054848 00000000cacbe4a0/0060: 00 00 00 00 00 00 00 00-aa 08 5f 54 fc 7f 00 00 .........._T....
152:49:24.054849 00000000cacbe4b0/0070: 40 e6 cb ca 00 00 00 00-c2 28 97 18 fc 7f 00 00 @........(......
152:49:24.054851 00000000cacbe4c0/0080: 00 00 cc ca 00 00 00 00-00 00 bc ca 00 00 00 00 ................
152:49:24.054852 00000000cacbe4d0/0090: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054854 00000000cacbe4e0/00a0: 06 00 00 00 04 00 00 00-00 00 00 00 01 00 00 00 ................
152:49:24.054855 00000000cacbe4f0/00b0: 08 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054857 00000000cacbe500/00c0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054858 00000000cacbe510/00d0: 40 e6 cb ca 00 00 00 00-00 00 00 00 00 00 00 00 @...............
152:49:24.054860 00000000cacbe520/00e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054862 **************** ****  <ditto x 6>
152:49:24.054862 00000000cacbe590/0150: 25 f0 25 10 04 1a 00 00-00 00 00 00 00 00 00 00 %.%.............
152:49:24.054864 00000000cacbe5a0/0160: 00 00 b4 56 fc 7f 00 00-40 ec cb ca 00 00 00 00 ...V....@.......
152:49:24.054866 00000000cacbe5b0/0170: 50 f8 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 P...............
152:49:24.054868 00000000cacbe5c0/0180: 00 00 00 00 00 00 00 00-b2 4a be 56 fc 7f 00 00 .........J.V....
152:49:24.054869 00000000cacbe5d0/0190: 00 00 00 00 00 00 00 00-20 44 c8 56 fc 7f 00 00 ........ D.V....
152:49:24.054871 00000000cacbe5e0/01a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054872 00000000cacbe5f0/01b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054882 00000000cacbe600/01c0: 51 ce 06 00 00 00 00 00-56 c6 bc 56 fc 7f 00 00 Q.......V..V....
152:49:24.054883 00000000cacbe610/01d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054885 00000000cacbe620/01e0: 08 ec cb ca 00 00 00 00-90 ec cb ca 00 00 00 00 ................
152:49:24.054886 00000000cacbe630/01f0: a4 0e c0 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054902 00000000cacbe640/0200: b0 f2 cb ca 00 00 00 00-c0 ed cb ca 00 00 00 00 ................
152:49:24.054903 00000000cacbe650/0210: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.054905 00000000cacbe660/0220: c0 ed cb ca 00 00 00 00-c0 c5 bc 56 fc 7f 00 00 ...........V....
152:49:24.054906 00000000cacbe670/0230: 00 00 00 00 00 00 00 00-cf 11 be 56 fc 7f 00 00 ...........V....
152:49:24.054908 00000000cacbe680/0240: 00 00 00 00 00 00 00 00-f0 eb cb ca 00 00 00 00 ................
152:49:24.054909 00000000cacbe690/0250: b0 f2 cb ca 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.054924 00000000cacbe6a0/0260: 40 ec cb ca 00 00 00 00-09 a2 ba 56 fc 7f 00 00 @..........V....
152:49:24.054926 00000000cacbe6b0/0270: 01 00 00 00 00 00 00 00-00 00 b4 56 fc 7f 00 00 ...........V....
152:49:24.054928 00000000cacbe6c0/0280: 00 00 00 00 00 00 00 00-f0 e9 ca 56 fc 7f 00 00 ...........V....
152:49:24.054929 00000000cacbe6d0/0290: f0 e6 cb ca 00 00 00 00-10 ec cb ca 00 00 00 00 ................
152:49:24.054931 00000000cacbe6e0/02a0: 00 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.054932 00000000cacbe6f0/02b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055264 **************** ****  <ditto x 2>
152:49:24.055266 00000000cacbe720/02e0: 0f 00 10 00 a0 1f 00 00-33 00 00 00 00 00 00 00 ........3.......
152:49:24.055268 00000000cacbe730/02f0: 00 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 ..+.............
152:49:24.055270 00000000cacbe740/0300: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055272 **************** ****  <ditto x 3>
152:49:24.055273 00000000cacbe780/0340: 00 00 00 00 00 00 00 00-d0 f8 cb ca 00 00 00 00 ................
152:49:24.055275 00000000cacbe790/0350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055276 **************** ****  <ditto x 5>
152:49:24.055277 00000000cacbe7f0/03b0: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055279 00000000cacbe800/03c0: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055280 00000000cacbe810/03d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055282 **************** ****  <ditto x 23>
152:49:24.055283 00000000cacbe990/0550: c0 ed cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055284 00000000cacbe9a0/0560: ff ff ff ff ff ff ff ff-00 00 00 00 00 00 00 00 ................
152:49:24.055286 00000000cacbe9b0/0570: 80 ea cb ca 00 00 00 00-2b 2e f3 15 f7 7f 00 00 ........+.......
152:49:24.055288 00000000cacbe9c0/0580: 40 94 fa 15 f7 7f 00 00-c0 eb cb ca 00 00 00 00 @...............
152:49:24.055290 00000000cacbe9d0/0590: c0 87 eb cd 00 00 00 00-70 10 75 82 00 00 00 00 ........p.u.....
152:49:24.055291 00000000cacbe9e0/05a0: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055293 00000000cacbe9f0/05b0: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055295 00000000cacbea00/05c0: 00 00 00 00 00 00 00 00-50 14 75 82 00 00 00 00 ........P.u.....
152:49:24.055296 00000000cacbea10/05d0: 00 00 00 00 00 00 00 00-a0 f6 cb ca 00 00 00 00 ................
152:49:24.055298 00000000cacbea20/05e0: 70 07 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 p..j............
152:49:24.055300 00000000cacbea30/05f0: 80 00 00 6a 02 00 00 00-40 0f 68 cd 00 00 00 00 ...j....@.h.....
152:49:24.055301 00000000cacbea40/0600: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055303 00000000cacbea50/0610: c2 28 97 18 fc 7f 00 00-60 f5 cb ca 00 00 00 00 .(......`.......
152:49:24.055305 00000000cacbea60/0620: 10 f6 cb ca 00 00 00 00-5f 00 10 00 00 00 00 00 ........_.......
152:49:24.055306 00000000cacbea70/0630: 33 00 00 00 00 00 00 00-2b 00 00 00 00 00 00 00 3.......+.......
152:49:24.055308 00000000cacbea80/0640: 2b 00 00 00 37 66 66 63-2b 00 00 00 32 38 63 32 +...7ffc+...28c2
152:49:24.055310 00000000cacbea90/0650: 53 00 00 00 00 00 00 00-2b 00 00 00 fc 7f 00 00 S.......+.......
152:49:24.055311 00000000cacbeaa0/0660: 06 02 01 00 00 00 00 00-a0 1f 00 00 02 00 00 00 ................
152:49:24.055313 00000000cacbeab0/0670: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055314 **************** ****  <ditto x 7>
152:49:24.055315 00000000cacbeb30/06f0: 00 4c a2 19 02 00 00 00-d6 2f f3 15 f7 7f 00 00 .L......./......
152:49:24.055317 00000000cacbeb40/0700: 02 00 00 00 00 00 00 00-00 70 cf 00 00 00 00 00 .........p......
152:49:24.055318 00000000cacbeb50/0710: 20 97 fa 15 f7 7f 00 00-05 00 00 c0 00 00 00 00  ...............
152:49:24.055320 00000000cacbeb60/0720: 01 00 00 00 00 00 00 00-40 0f 68 cd 00 00 00 00 ........@.h.....
152:49:24.055322 00000000cacbeb70/0730: 80 00 00 6a 02 00 00 00-f2 ec b5 56 fc 7f 00 00 ...j.......V....
152:49:24.055323 00000000cacbeb80/0740: 70 07 00 6a 02 00 00 00-00 4c a2 19 02 00 00 00 p..j.....L......
152:49:24.055325 00000000cacbeb90/0750: b0 f2 cb ca 00 00 00 00-0b 00 10 00 00 00 00 00 ................
152:49:24.055327 00000000cacbeba0/0760: 10 00 00 00 00 00 00 00-dc a0 ba 56 fc 7f 00 00 ...........V....
152:49:24.055329 00000000cacbebb0/0770: 00 00 00 00 00 00 00 00-b0 f2 cb ca 00 00 00 00 ................
152:49:24.055330 00000000cacbebc0/0780: 30 fb ff ff e8 04 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055335 00000000cacbebd0/0790: 19 00 00 00 00 00 00 00-72 3a 20 30 78 63 30 30 ........r: 0xc00
152:49:24.055336 00000000cacbebe0/07a0: 30 30 30 30 35 20 28 30-30 30 30 30 30 30 30 30 00005 (000000000
152:49:24.055338 00000000cacbebf0/07b0: 00 30 30 30 30 30 31 2c-90 ec cb ca 00 00 00 00 .000001,........
152:49:24.055339 00000000cacbec00/07c0: 50 f8 cb ca 00 00 00 00-00 00 b4 56 fc 7f 00 00 P..........V....
152:49:24.055341 00000000cacbec10/07d0: 20 44 c8 56 fc 7f 00 00-00 00 00 00 00 00 00 00  D.V............
152:49:24.055343 00000000cacbec20/07e0: 00 00 cc ca 00 00 00 00-00 d0 cb ca 00 00 00 00 ................
152:49:24.055344 00000000cacbec30/07f0: c0 ed cb ca 00 00 00 00-80 51 9d 18 fc 7f 00 00 .........Q......
152:49:24.055346 00000000cacbec40/0800: 51 ce ba 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 Q..V.......V....
152:49:24.055348 00000000cacbec50/0810: f0 e9 ca 56 fc 7f 00 00-50 f8 cb ca 00 00 00 00 ...V....P.......
152:49:24.055349 00000000cacbec60/0820: 00 00 00 00 00 00 00 00-f0 e6 cb ca 00 00 00 00 ................
152:49:24.055351 00000000cacbec70/0830: c0 c5 bc 56 fc 7f 00 00-20 44 c8 56 fc 7f 00 00 ...V.... D.V....
152:49:24.055352 00000000cacbec80/0840: 90 ec cb ca 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055354 00000000cacbec90/0850: 0a 00 00 00 00 00 00 00-80 38 8f 18 fc 7f 00 00 .........8......
152:49:24.055355 00000000cacbeca0/0860: 78 ce ba 56 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x..V............
152:49:24.055357 00000000cacbecb0/0870: 80 4b a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .K..............
152:49:24.055358 00000000cacbecc0/0880: b0 48 a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 .H..............
152:49:24.055360 00000000cacbecd0/0890: a4 0f a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055362 00000000cacbece0/08a0: 78 fc a2 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 x...............
152:49:24.055363 00000000cacbecf0/08b0: b4 1d a3 18 fc 7f 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055365 00000000cacbed00/08c0: b8 1c a3 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055366 00000000cacbed10/08d0: d4 0e c0 18 fc 7f 00 00-00 00 a4 18 fc 7f 00 00 ................
152:49:24.055368 00000000cacbed20/08e0: a4 0e c0 18 fc 7f 00 00-00 00 31 56 fc 7f 00 00 ..........1V....
152:49:24.055369 00000000cacbed30/08f0: d8 ac 3b 56 fc 7f 00 00-00 00 b4 56 fc 7f 00 00 ..;V.......V....
152:49:24.055371 00000000cacbed40/0900: f0 e9 ca 56 fc 7f 00 00-08 c0 f3 15 f7 7f 00 00 ...V............
152:49:24.055373 00000000cacbed50/0910: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055374 00000000cacbed60/0920: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055376 00000000cacbed70/0930: e0 41 c3 4b 97 74 00 00-a0 f6 cb ca 00 00 00 00 .A.K.t..........
152:49:24.055377 00000000cacbed80/0940: 40 0f 68 cd 00 00 00 00-80 00 00 6a 02 00 00 00 @.h........j....
152:49:24.055379 00000000cacbed90/0950: 00 00 00 00 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055380 00000000cacbeda0/0960: 00 4c a2 19 02 00 00 00-00 4c a2 19 02 00 00 00 .L.......L......
152:49:24.055382 00000000cacbedb0/0970: 10 f6 cb ca 00 00 00 00-3e fe bd 56 fc 7f 00 00 ........>..V....
152:49:24.055384 00000000cacbedc0/0980: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055385 00000000cacbedd0/0990: 70 10 75 82 00 00 00 00-00 00 00 00 00 00 00 00 p.u.............
152:49:24.055387 00000000cacbede0/09a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055388 00000000cacbedf0/09b0: 5f 00 10 00 a0 1f 00 00-33 00 2b 00 2b 00 53 00 _.......3.+.+.S.
152:49:24.055390 00000000cacbee00/09c0: 2b 00 2b 00 06 02 01 00-00 00 00 00 00 00 00 00 +.+.............
152:49:24.055391 00000000cacbee10/09d0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055393 00000000cacbee20/09e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055396 00000000cacbee30/09f0: 00 00 00 00 00 00 00 00-c0 87 eb cd 00 00 00 00 ................
152:49:24.055398 00000000cacbee40/0a00: 00 00 00 00 00 00 00 00-90 10 75 82 00 00 00 00 ..........u.....
152:49:24.055399 00000000cacbee50/0a10: 70 10 75 82 00 00 00 00-60 f5 cb ca 00 00 00 00 p.u.....`.......
152:49:24.055401 00000000cacbee60/0a20: 10 f6 cb ca 00 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055403 00000000cacbee70/0a30: 00 4c a2 19 02 00 00 00-00 00 00 00 00 00 00 00 .L..............
152:49:24.055404 00000000cacbee80/0a40: 50 14 75 82 00 00 00 00-00 00 00 00 00 00 00 00 P.u.............
152:49:24.055406 00000000cacbee90/0a50: a0 f6 cb ca 00 00 00 00-70 07 00 6a 02 00 00 00 ........p..j....
152:49:24.055407 00000000cacbeea0/0a60: 00 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055409 00000000cacbeeb0/0a70: 40 0f 68 cd 00 00 00 00-c2 28 97 18 fc 7f 00 00 @.h......(......
152:49:24.055410 00000000cacbeec0/0a80: 7f 02 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055412 00000000cacbeed0/0a90: 00 00 00 00 00 00 00 00-a0 1f 00 00 ff ff 00 00 ................
152:49:24.055413 00000000cacbeee0/0aa0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055415 **************** ****  <ditto x 58>
152:49:24.055416 00000000cacbf290/0e50: 30 fb ff ff a0 07 00 00-30 fb ff ff d0 04 00 00 0.......0.......
152:49:24.055417 00000000cacbf2a0/0e60: f0 00 00 00 e0 01 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055419 00000000cacbf2b0/0e70: 05 00 00 c0 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055421 00000000cacbf2c0/0e80: c2 28 97 18 fc 7f 00 00-02 00 00 00 00 00 00 00 .(..............
152:49:24.055422 00000000cacbf2d0/0e90: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055438 00000000cacbf2e0/0ea0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055440 **************** ****  <ditto x 5>
152:49:24.055440 00000000cacbf340/0f00: 00 00 00 00 00 00 00 00-c6 2b 97 18 fc 7f 00 00 .........+......
152:49:24.055442 00000000cacbf350/0f10: c2 28 97 18 fc 7f 00 00-00 00 00 00 00 00 00 00 .(..............
152:49:24.055443 00000000cacbf360/0f20: 00 00 00 00 00 00 00 00-60 f5 cb ca 00 00 00 00 ........`.......
152:49:24.055445 00000000cacbf370/0f30: f8 37 00 6a 02 00 00 00-87 c9 9a 18 fc 7f 00 00 .7.j............
152:49:24.055446 00000000cacbf380/0f40: 00 00 00 00 00 00 00 00-1c 00 00 00 00 00 00 80 ................
152:49:24.055448 00000000cacbf390/0f50: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055449 **************** ****  <ditto x 2>
152:49:24.055450 00000000cacbf3c0/0f80: 00 82 2f 7c 00 00 00 00-00 00 00 00 02 00 00 00 ../|............
152:49:24.055451 00000000cacbf3d0/0f90: 00 01 00 00 00 00 00 00-c0 81 2f 7c 00 00 00 00 ........../|....
152:49:24.055453 00000000cacbf3e0/0fa0: 17 03 00 00 00 00 00 00-1e 00 00 00 e0 01 00 00 ................
152:49:24.055455 00000000cacbf3f0/0fb0: 17 03 00 00 00 00 00 00-00 00 00 00 17 03 00 00 ................
152:49:24.055456 00000000cacbf400/0fc0: 17 03 00 00 00 00 00 00-00 02 00 00 00 00 00 00 ................
152:49:24.055458 00000000cacbf410/0fd0: 80 79 72 64 02 00 00 00-80 00 00 6a 02 00 00 00 .yrd.......j....
152:49:24.055459 00000000cacbf420/0fe0: 00 00 00 00 01 00 00 00-00 00 00 00 00 02 00 00 ................
152:49:24.055461 00000000cacbf430/0ff0: 00 00 00 00 00 00 00 00-b0 50 3e 44 02 00 00 00 .........P>D....
152:49:24.055462 00000000cacbf440/1000: 50 b2 49 6a 02 00 00 00-a9 57 92 18 fc 7f 00 00 P.Ij.....W......
152:49:24.055464 00000000cacbf450/1010: 10 f6 cb ca 00 00 00 00-b0 f5 cb ca 00 00 00 00 ................
152:49:24.055465 00000000cacbf460/1020: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055467 00000000cacbf470/1030: 00 00 f0 41 00 c0 45 44-00 00 80 3f 00 00 80 3f ...A..ED...?...?
152:49:24.055469 00000000cacbf480/1040: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055473 00000000cacbf490/1050: 28 31 00 6a 02 00 00 00-00 00 80 3f 00 00 80 3f (1.j.......?...?
152:49:24.055488 00000000cacbf4a0/1060: 00 00 00 00 00 c0 45 44-00 00 00 00 00 00 00 00 ......ED........
152:49:24.055490 00000000cacbf4b0/1070: 00 00 00 00 00 00 00 00-00 00 80 3f 00 00 80 3f ...........?...?
152:49:24.055491 00000000cacbf4c0/1080: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055493 00000000cacbf4d0/1090: 32 ac a9 1f bb e0 00 00-00 00 00 00 00 00 00 00 2...............
152:49:24.055497 00000000cacbf4e0/10a0: d2 ab a9 1f bb e0 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055500 00000000cacbf4f0/10b0: 00 00 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055504 00000000cacbf500/10c0: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055509 00000000cacbf510/10d0: 04 00 00 00 00 00 00 00-80 00 00 6a 02 00 00 00 ...........j....
152:49:24.055512 00000000cacbf520/10e0: 30 f6 cb ca 00 00 00 00-00 da 9a 18 fc 7f 00 00 0...............
152:49:24.055519 00000000cacbf530/10f0: 80 00 00 6a 02 00 00 00-28 f7 cb ca 00 00 00 00 ...j....(.......
152:49:24.055523 00000000cacbf540/1100: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055526 00000000cacbf550/1110: 00 00 00 00 00 00 00 00-40 f8 95 18 fc 7f 00 00 ........@.......
152:49:24.055529 00000000cacbf560/1120: 00 00 00 00 00 00 00 00-68 95 d0 cb 00 00 00 00 ........h.......
152:49:24.055533 00000000cacbf570/1130: 01 00 00 00 01 00 00 00-00 4c a2 19 02 00 00 00 .........L......
152:49:24.055536 00000000cacbf580/1140: 80 00 00 6a 02 00 00 00-df 06 97 18 fc 7f 00 00 ...j............
152:49:24.055540 00000000cacbf590/1150: 00 00 00 00 02 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055543 00000000cacbf5a0/1160: 80 4b 6c 64 02 00 00 00-b0 50 3e 44 02 00 00 00 .Kld.....P>D....
152:49:24.055546 00000000cacbf5b0/1170: b0 50 3e 44 02 00 00 00-00 00 00 00 00 00 00 00 .P>D............
152:49:24.055549 00000000cacbf5c0/1180: 00 00 00 00 00 00 00 00-00 f6 cb ca 00 00 00 00 ................
152:49:24.055553 00000000cacbf5d0/1190: 80 4b 6c 64 02 00 00 00-00 00 00 00 00 00 00 00 .Kld............
152:49:24.055556 00000000cacbf5e0/11a0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055560 00000000cacbf5f0/11b0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055563 00000000cacbf600/11c0: 00 00 00 00 00 00 00 00-1e 00 00 00 17 03 00 00 ................
152:49:24.055564 00000000cacbf610/11d0: 00 00 00 00 00 00 00 00-00 00 8e 18 fc 7f 00 00 ................
152:49:24.055566 00000000cacbf620/11e0: 70 07 00 6a 02 00 00 00-03 00 00 00 00 00 00 00 p..j............
152:49:24.055568 00000000cacbf630/11f0: 00 00 00 00 00 00 00 00-b0 4b ef 7b 00 00 00 00 .........K.{....
152:49:24.055569 00000000cacbf640/1200: b8 0b 00 00 00 00 00 00-ed 1b 91 18 fc 7f 00 00 ................
152:49:24.055571 00000000cacbf650/1210: b0 4b ef 7b 00 00 00 00-00 00 00 00 00 00 00 00 .K.{............
152:49:24.055573 00000000cacbf660/1220: 04 00 00 7a 00 00 00 01-01 00 00 00 00 00 00 00 ...z............
152:49:24.055574 00000000cacbf670/1230: 00 00 00 00 00 00 00 00-04 00 00 7a 98 04 00 01 ...........z....
152:49:24.055576 00000000cacbf680/1240: 60 00 00 00 00 00 00 00-5c 99 dc cb 00 00 00 00 `.......\.......
152:49:24.055577 00000000cacbf690/1250: 00 00 8e 18 fc 7f 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055579 00000000cacbf6a0/1260: 80 00 00 6a 02 00 00 00-79 3a 8f 18 fc 7f 00 00 ...j....y:......
152:49:24.055580 00000000cacbf6b0/1270: b0 4b ef 7b 00 00 00 00-04 00 00 00 00 00 00 00 .K.{............
152:49:24.055582 00000000cacbf6c0/1280: d8 65 91 26 02 00 00 00-38 cf 8a 19 02 00 00 00 .e.&....8.......
152:49:24.055583 00000000cacbf6d0/1290: a0 f7 cb ca 00 00 00 00-7c 91 92 18 fc 7f 00 00 ........|.......
152:49:24.055585 00000000cacbf6e0/12a0: 04 00 00 00 00 00 00 00-04 00 00 00 00 00 00 00 ................
152:49:24.055586 00000000cacbf6f0/12b0: 80 00 00 6a 02 00 00 00-17 53 90 18 fc 7f 00 00 ...j.....S......
152:49:24.055591 00000000cacbf700/12c0: 88 14 00 6a 02 00 00 00-6f 7e 92 18 fc 7f 00 00 ...j....o~......
152:49:24.055593 00000000cacbf710/12d0: 80 00 00 6a 02 00 00 00-80 00 00 6a 02 00 00 00 ...j.......j....
152:49:24.055594 00000000cacbf720/12e0: 98 14 00 6a 02 00 00 00-00 00 00 00 00 00 00 00 ...j............
152:49:24.055596 00000000cacbf730/12f0: f0 43 3e 44 02 00 00 00-88 14 00 6a 02 00 00 00 .C>D.......j....
152:49:24.055598 00000000cacbf740/1300: 01 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055599 00000000cacbf750/1310: 5c 99 dc cb 00 00 00 00-d0 95 dc cb 00 00 00 00 \...............
152:49:24.055601 00000000cacbf760/1320: 01 00 00 00 00 00 00 00-60 90 d0 cb 00 00 00 00 ........`.......
152:49:24.055602 00000000cacbf770/1330: 8c 03 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055604 00000000cacbf780/1340: 00 00 00 00 00 00 00 00-c6 53 b7 18 fc 7f 00 00 .........S......
152:49:24.055605 00000000cacbf790/1350: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055607 00000000cacbf7a0/1360: 00 00 00 00 00 00 00 00-01 00 00 00 00 00 00 00 ................
152:49:24.055608 00000000cacbf7b0/1370: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055610 **************** ****  <ditto x 2>
152:49:24.055610 00000000cacbf7e0/13a0: 01 00 00 00 00 00 00 00-a3 4f b7 18 fc 7f 00 00 .........O......
152:49:24.055612 00000000cacbf7f0/13b0: 60 90 d0 cb 00 00 00 00-00 00 00 00 00 00 00 00 `...............
152:49:24.055614 00000000cacbf800/13c0: 00 00 a4 18 fc 7f 00 00-1c 19 00 00 00 00 00 00 ................
152:49:24.055615 00000000cacbf810/13d0: 00 00 00 00 00 00 00 00-d4 7b 32 56 fc 7f 00 00 .........{2V....
152:49:24.055617 00000000cacbf820/13e0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055618 00000000cacbf830/13f0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055620 00000000cacbf840/1400: 00 00 00 00 00 00 00 00-51 ce ba 56 fc 7f 00 00 ........Q..V....
152:49:24.055621 00000000cacbf850/1410: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055623 **************** ****  <ditto x 2>
152:49:24.055623 00000000cacbf880/1440: 00 00 00 00 1e 91 8b 62-00 00 00 00 00 00 00 00 .......b........
152:49:24.055625 00000000cacbf890/1450: 00 00 00 00 00 00 00 00-c0 06 5f 54 fc 7f 00 00 .........._T....
152:49:24.055626 00000000cacbf8a0/1460: 40 e6 cb ca 00 00 00 00-f0 ff 01 00 78 5f 52 db @...........x_R.
152:49:24.055628 00000000cacbf8b0/1470: de 97 d4 36 fc 7f 00 00-40 e6 cb ca 00 00 00 00 ...6....@.......
152:49:24.055629 00000000cacbf8c0/1480: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055632 **************** ****  <ditto x 114>
152:49:24.055632 00000000cacbfff0/1bb0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
152:49:24.055881 Thread ID:   0000000000004184
152:49:24.055891 Thread name: <NULL>
152:49:24.055896 Thread IPRT: 0000000000000000
152:49:24.055901 
152:49:24.055901 Loaded Modules:
152:49:24.055901 Address range                    [*] Timestamp Path
152:49:24.055907 00007ff715f30000..00007ff716045fff   5f51ed66  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
152:49:24.055914 00007ffc56b40000..00007ffc56d2ffff   b5beef21  C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.055920 00007ffc56310000..00007ffc563c1fff   53a32b86  C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.055926 00007ffc544f0000..00007ffc54794fff   1b835a75  C:\WINDOWS\System32\KERNELBASE.dll
152:49:24.055932 00007ffc2f520000..00007ffc2f524fff   5f51ecdc  C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL
152:49:24.055937 00007ffc54410000..00007ffc5446bfff   ad0f5fb3  C:\WINDOWS\System32\Wintrust.dll
152:49:24.055943 00007ffc56560000..00007ffc565fdfff   f5bdefd7  C:\WINDOWS\System32\msvcrt.dll
152:49:24.055949 00007ffc53a90000..00007ffc53aa1fff   e4c2641f  C:\WINDOWS\System32\MSASN1.dll
152:49:24.055954 00007ffc548d0000..00007ffc54a18fff   0e128cc8  C:\WINDOWS\System32\CRYPT32.dll
152:49:24.055960 00007ffc547d0000..00007ffc548c9fff   32a6df9a  C:\WINDOWS\System32\ucrtbase.dll
152:49:24.055966 00007ffc55970000..00007ffc55a8ffff   ee94cb53  C:\WINDOWS\System32\RPCRT4.dll
152:49:24.055971 00007ffc547a0000..00007ffc547c5fff   b59ada57  C:\WINDOWS\System32\bcrypt.dll
152:49:24.055984 00007ffc54470000..00007ffc544effff   bf9ade76  C:\WINDOWS\System32\bcryptprimitives.dll
152:49:24.055990 00007ffc543f0000..00007ffc54406fff   a51023f1  C:\WINDOWS\System32\CRYPTSP.dll
152:49:24.055996 00007ffc526e0000..00007ffc52712fff   fa3c3542  C:\WINDOWS\system32\rsaenh.dll
152:49:24.056001 00007ffc52d40000..00007ffc52d4bfff   fef011a6  C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
152:49:24.056007 00007ffc56540000..00007ffc5655cfff   13bffc39  C:\WINDOWS\System32\imagehlp.dll
152:49:24.056013 00007ffc54ce0000..00007ffc54d76fff   f222d51c  C:\WINDOWS\System32\sechost.dll
152:49:24.056018 00007ffc51900000..00007ffc51921fff   0ab6ed3a  C:\WINDOWS\SYSTEM32\gpapi.dll
152:49:24.056024 00007ffc53a60000..00007ffc53a82fff   ca538c5d  C:\WINDOWS\System32\profapi.dll
152:49:24.056030 00007ffc52240000..00007ffc5226efff   b35f039c  C:\WINDOWS\System32\cryptnet.dll
152:49:24.056049 00007ffc54d80000..00007ffc54e22fff   502aaa11  C:\WINDOWS\System32\advapi32.dll
152:49:24.056055 00007ffbfaab0000..00007ffbfb08ffff   5f51ed67  C:\Program Files\Oracle\VirtualBox\VBoxRT.dll
152:49:24.056061 00007ffc55880000..00007ffc558eefff   50866107  C:\WINDOWS\System32\WS2_32.dll
152:49:24.056066 00000000502b0000..0000000050381fff   4d5f034a  C:\Program Files\Oracle\VirtualBox\MSVCR100.dll
152:49:24.056072 0000000050210000..00000000502a7fff   4d5f035c  C:\Program Files\Oracle\VirtualBox\MSVCP100.dll
152:49:24.056077 00007ffbf6a50000..00007ffbf6c17fff   5f51ed81  C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.dll
152:49:24.056083 00007ffc550b0000..00007ffc55244fff   57629574  C:\WINDOWS\System32\USER32.dll
152:49:24.056088 00007ffc54bc0000..00007ffc54be0fff   5343f4fb  C:\WINDOWS\System32\win32u.dll
152:49:24.056093 00007ffc563d0000..00007ffc563f5fff   90b22122  C:\WINDOWS\System32\GDI32.dll
152:49:24.056098 00007ffc53ad0000..00007ffc53c65fff   7ea30dec  C:\WINDOWS\System32\gdi32full.dll
152:49:24.056104 00007ffc54a20000..00007ffc54abdfff   2085286c  C:\WINDOWS\System32\msvcp_win.dll
152:49:24.056109 00007ffc56600000..00007ffc56756fff   3340c819  C:\WINDOWS\System32\ole32.dll
152:49:24.056114 00007ffc567c0000..00007ffc56af4fff   8349657a  C:\WINDOWS\System32\combase.dll
152:49:24.056119 00007ffc557b0000..00007ffc55874fff   6ac977e7  C:\WINDOWS\System32\OLEAUT32.dll
152:49:24.056126 00007ffc25480000..00007ffc255d5fff   c7cf39ed  C:\WINDOWS\SYSTEM32\OPENGL32.dll
152:49:24.056132 00007ffbf8790000..00007ffbfaaa6fff   5f51ed79  C:\Program Files\Oracle\VirtualBox\UICommon.dll
152:49:24.056137 0000000077a90000..0000000077ff4fff   58e2613b  C:\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll
152:49:24.056142 00007ffc55a90000..00007ffc56176fff   37e737cc  C:\WINDOWS\System32\SHELL32.dll
152:49:24.056148 00007ffc54ac0000..00007ffc54b09fff   afaaabaa  C:\WINDOWS\System32\cfgmgr32.dll
152:49:24.056153 00007ffc54bf0000..00007ffc54c98fff   bd8b0e7d  C:\WINDOWS\System32\shcore.dll
152:49:24.056158 00007ffc53c70000..00007ffc543effff   a8db3b62  C:\WINDOWS\System32\windows.storage.dll
152:49:24.056163 00007ffc53a10000..00007ffc53a59fff   fdc4588a  C:\WINDOWS\System32\powrprof.dll
152:49:24.056169 00007ffc53a00000..00007ffc53a0ffff   a2ccd413  C:\WINDOWS\System32\UMPDC.dll
152:49:24.056174 00007ffc562b0000..00007ffc56301fff   f8807ba1  C:\WINDOWS\System32\shlwapi.dll
152:49:24.056179 00007ffc53ab0000..00007ffc53ac0fff   05bef372  C:\WINDOWS\System32\kernel.appcore.dll
152:49:24.056184 00007ffbf8190000..00007ffbf8786fff   58e261e1  C:\Program Files\Oracle\VirtualBox\Qt5GuiVBox.dll
152:49:24.056190 0000000077520000..0000000077a80fff   58e2628d  C:\Program Files\Oracle\VirtualBox\Qt5WidgetsVBox.dll
152:49:24.056195 00000000501b0000..0000000050203fff   58e262df  C:\Program Files\Oracle\VirtualBox\Qt5OpenGLVBox.dll
152:49:24.056200 00007ffc4d690000..00007ffc4d6b3fff   d238be3c  C:\WINDOWS\SYSTEM32\WINMM.dll
152:49:24.056205 00007ffc25450000..00007ffc2547bfff   f93070ee  C:\WINDOWS\SYSTEM32\GLU32.dll
152:49:24.056211 00007ffc2ba80000..00007ffc2ba9afff   57b24d2b  C:\WINDOWS\SYSTEM32\MPR.dll
152:49:24.056216 00007ffc4d660000..00007ffc4d68cfff   d6bb9be2  C:\WINDOWS\SYSTEM32\WINMMBASE.dll
152:49:24.056221 00007ffc51950000..00007ffc5196ffff   bc0e8e8e  C:\WINDOWS\SYSTEM32\dxcore.dll
152:49:24.056227 00007ffc54cb0000..00007ffc54cddfff   4be57136  C:\WINDOWS\System32\IMM32.DLL
152:49:24.056232 00007ffbf8060000..00007ffbf818dfff   58e2632b  C:\Program Files\Oracle\VirtualBox\platforms\qwindows.dll
152:49:24.056237 00007ffc509e0000..00007ffc50a78fff   6eb90ac0  C:\WINDOWS\system32\uxtheme.dll
152:49:24.056242 00007ffc538e0000..00007ffc53904fff   dbb466d6  C:\WINDOWS\system32\userenv.dll
152:49:24.056248 00007ffc56200000..00007ffc562a1fff   9506208f  C:\WINDOWS\System32\clbcatq.dll
152:49:24.056253 00007ffbf7bb0000..00007ffbf7f6ffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxC.dll
152:49:24.056258 00007ffbf7f70000..00007ffbf805efff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll
152:49:24.056264 00007ffc56400000..00007ffc56534fff   8776e62f  C:\WINDOWS\System32\MSCTF.dll
152:49:24.056269 00007ffc26a40000..00007ffc26a79fff   5c8c75fa  C:\WINDOWS\system32\dataexchange.dll
152:49:24.056274 00007ffc4ca70000..00007ffc4cccafff   7e72d1cb  C:\WINDOWS\system32\d3d11.dll
152:49:24.056280 00007ffc4ccd0000..00007ffc4ceacfff   2ba0a53f  C:\WINDOWS\system32\dcomp.dll
152:49:24.056285 00007ffc51a10000..00007ffc51afafff   4029f10d  C:\WINDOWS\system32\dxgi.dll
152:49:24.056290 00007ffc50ad0000..00007ffc50d31fff   eeb9f7a6  C:\WINDOWS\system32\twinapi.appcore.dll
152:49:24.056296 00007ffc50f10000..00007ffc50f38fff   5be0eb17  C:\WINDOWS\system32\RMCLIENT.dll
152:49:24.056301 00007ffc41fd0000..00007ffc4206dfff   66a372e8  C:\WINDOWS\System32\TextInputFramework.dll
152:49:24.056306 00007ffc4a6f0000..00007ffc4aa19fff   d02b205d  C:\WINDOWS\System32\CoreUIComponents.dll
152:49:24.056312 00007ffc4ceb0000..00007ffc4cf83fff   99046ad7  C:\WINDOWS\System32\CoreMessaging.dll
152:49:24.056317 00007ffc53450000..00007ffc53480fff   d95e6299  C:\WINDOWS\SYSTEM32\ntmarta.dll
152:49:24.056322 00007ffc4b1d0000..00007ffc4b322fff   571c81a7  C:\WINDOWS\SYSTEM32\wintypes.dll
152:49:24.056327 00007ffc40a70000..00007ffc40d15fff   156c7509  C:\WINDOWS\System32\iertutil.dll
152:49:24.056333 00007ffc3e0f0000..00007ffc3e100fff   6e82a406  C:\WINDOWS\system32\wbem\wbemprox.dll
152:49:24.056339 00007ffc3eb30000..00007ffc3ebb3fff   6af5c06d  C:\WINDOWS\SYSTEM32\wbemcomn.dll
152:49:24.056345 00007ffc3d770000..00007ffc3d783fff   f9651a38  C:\WINDOWS\system32\wbem\wbemsvc.dll
152:49:24.056350 00007ffc3d890000..00007ffc3d990fff   65ead981  C:\WINDOWS\system32\wbem\fastprox.dll
152:49:24.056356 00007ffc33850000..00007ffc33864fff   b26a0aaf  C:\WINDOWS\System32\amsi.dll
152:49:24.056361 00007ffc31bd0000..00007ffc31c48fff   c930d9ac  C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2009.7-0\MpOav.dll
152:49:24.056367 00007ffc47f20000..00007ffc47f29fff   927b71e6  C:\WINDOWS\system32\version.dll
152:49:24.056372 00007ffbf66d0000..00007ffbf6a4dfff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
152:49:24.056378 00007ffc534b0000..00007ffc534bffff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedClipboard.DLL
152:49:24.056383 00007ffc534a0000..00007ffc534acfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxDragAndDropSvc.DLL
152:49:24.056389 00007ffbf5ce0000..00007ffbf66c5fff   5f51ef9a  C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
152:49:24.056394 00007ffc55340000..00007ffc557affff   a7d94c0a  C:\WINDOWS\System32\SETUPAPI.dll
152:49:24.056400 00007ffbf7b40000..00007ffbf7ba6fff   5f51ed6c  C:\Program Files\Oracle\VirtualBox\VBoxDDU.dll
152:49:24.056405 00007ffbf5480000..00007ffbf5cdbfff   5f51ef98  C:\Program Files\Oracle\VirtualBox\VBoxDD2.dll
152:49:24.056411 00007ffc52880000..00007ffc528b9fff   50afe730  C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
152:49:24.056416 00007ffc2f500000..00007ffc2f513fff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxSharedFolders.DLL
152:49:24.056421 00007ffc53490000..00007ffc5349bfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestControlSvc.DLL
152:49:24.056427 00007ffc14a70000..00007ffc14a7cfff   5f51ed74  C:\Program Files\Oracle\VirtualBox\VBoxGuestPropSvc.DLL
152:49:24.056433 00007ffc4b100000..00007ffc4b10afff   3f83c149  C:\WINDOWS\SYSTEM32\WINNSI.DLL
152:49:24.056438 00007ffc55960000..00007ffc55967fff   76a581c8  C:\WINDOWS\System32\NSI.dll
152:49:24.056443 00007ffc4ab20000..00007ffc4ab35fff   1c3a0614  C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
152:49:24.056448 00007ffc4ab00000..00007ffc4ab1bfff   3c1facb4  C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
152:49:24.056454 00007ffc528c0000..00007ffc5298afff   6d09021f  C:\WINDOWS\SYSTEM32\DNSAPI.dll
152:49:24.056459 00007ffc426e0000..00007ffc42751fff   1626851d  C:\WINDOWS\System32\MMDevApi.dll
152:49:24.056464 00007ffc537f0000..00007ffc53819fff   73cca382  C:\WINDOWS\System32\DEVOBJ.dll
152:49:24.056470 00007ffc1fa50000..00007ffc1fae8fff   0f4dfe70  C:\WINDOWS\System32\dsound.dll
152:49:24.056509 00007ffc3ff90000..00007ffc400ecfff   7e935799  C:\WINDOWS\System32\AUDIOSES.DLL
152:49:24.056523 00007ffc18d80000..00007ffc18dc3fff   2c6931f6  C:\WINDOWS\System32\wdmaud.drv
152:49:24.056536 00007ffc2f8c0000..00007ffc2f8c8fff   9b72df6f  C:\WINDOWS\SYSTEM32\ksuser.dll
152:49:24.056546 00007ffc4ad50000..00007ffc4ad59fff   f97bfee2  C:\WINDOWS\SYSTEM32\AVRT.dll
152:49:24.056555 00007ffc2e910000..00007ffc2e91cfff   4d3c7e92  C:\WINDOWS\System32\msacm32.drv
152:49:24.056564 00007ffc2ded0000..00007ffc2deebfff   6a4add8d  C:\WINDOWS\SYSTEM32\MSACM32.dll
152:49:24.056574 00007ffc2e730000..00007ffc2e739fff   5a70c191  C:\WINDOWS\System32\midimap.dll
152:49:24.056583 00007ffc18a40000..00007ffc18c06fff   c808fce5  C:\WINDOWS\system32\d3d9.dll
152:49:24.056592 00007ffc50e30000..00007ffc50e5cfff   7cd7bb0f  C:\WINDOWS\SYSTEM32\dwmapi.dll
152:49:24.056602 00007ffc188e0000..00007ffc18a3cfff*  5eb1b78e  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056615 00007ffc14fd0000..00007ffc188d8fff   5eb1b648  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igd9dxva64.dll
152:49:24.056630 00007ffc451c0000..00007ffc45363fff   5eb1b356  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdgmm64.dll
152:49:24.056643 00007ffc51e70000..00007ffc51e95fff   5eb1b301  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdinfo64.dll
152:49:24.056659 00007ffc42bb0000..00007ffc451b3fff   5eb1b815  C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igc64.dll
152:49:24.056677 00007ffc4bba0000..00007ffc4bc8ffff   e593a459  C:\Windows\System32\PROPSYS.dll
152:49:24.056688 00007ffc52b70000..00007ffc52bd6fff   65b356bc  C:\WINDOWS\system32\mswsock.dll
152:49:24.056702 00007ffc50d40000..00007ffc50d53fff   c19b74f1  C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
152:49:24.056713 
152:49:24.056713 Potential code addresses on the stack:
152:49:24.056719 Xcpt PC         : 00007ffc189728c2 - 0x000928c2 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056740 00000000cacbf588: 00007ffc189706df - 0x000906df bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056759 00000000cacbf618: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056770 00000000cacbf648: 00007ffc18911bed - 0x00031bed bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056777 00000000cacbf690: 00007ffc188e0000 - 0x00000000 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056784 00000000cacbf6a8: 00007ffc188f3a79 - 0x00013a79 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056791 00000000cacbf6d8: 00007ffc1892917c - 0x0004917c bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056798 00000000cacbf6f8: 00007ffc18905317 - 0x00025317 bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056804 00000000cacbf708: 00007ffc18927e6f - 0x00047e6f bytes into C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_968d2e53c8174e28\igdumdim64.dll
152:49:24.056813 00000000cacbf788: 00007ffc18b753c6 - 0x001353c6 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056820 00000000cacbf7e8: 00007ffc18b74fa3 - 0x00134fa3 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056829 00000000cacbf800: 00007ffc18a40000 - 0x00000000 bytes into C:\WINDOWS\system32\d3d9.dll
152:49:24.056836 00000000cacbf818: 00007ffc56327bd4 - 0x00017bd4 bytes into C:\WINDOWS\System32\KERNEL32.DLL
152:49:24.056841 00000000cacbf848: 00007ffc56bace51 - 0x0006ce51 bytes into C:\WINDOWS\SYSTEM32\ntdll.dll
152:49:24.056860 00000000cacbf898: 00007ffc545f06c0 - 0x001006c0 bytes into C:\WINDOWS\System32\KERNELBASE.dll",paulcad
19981,"GNOME issue, Suspected but unsure",Linux,VirtualBox 6.1.14,2020-10-20T15:08:11Z,2020-10-20T15:08:11Z,2020-10-20T15:08:11Z,the vm will start but not get past the command line.,eryktyler26
19976,Any types of VM cannot be started by hardenedwinrespawn,Windows,VirtualBox 6.1.14,2020-10-16T19:22:11Z,2020-10-19T21:39:58Z,2020-10-19T21:39:58Z,"I was trying to create vms on my machine, I also enabled virtualization through bios, installed hyper-v (Just in case) on windows 10 home and also I did modified the owner of every hardrive to be my user, it seems it has problem with permission but i used administrator mode and gave all the acording permissions.",Valkiria
19978,Crash reboot VM UEFI Windows Server,Windows,VirtualBox 6.1.14,2020-10-18T13:01:23Z,2020-10-19T10:54:03Z,2020-10-19T10:54:03Z,"A VM configured for Windows Server 2019 UEFI with VM VirtualBox Extension Pack 6.1.14, hangs on reboot (random). Windows 10 2004 host. This problem has occurred since the first version 6.0.",tiagocoelho2
19979,"Virtualbox 6.1.14 crashes on Windows 10 Home, 6.1.4 does not",Linux,VirtualBox 6.1.14,2020-10-18T16:58:38Z,2020-10-18T17:04:31Z,2020-10-18T17:04:31Z,"I've been using 6.1.4 about 10 hours a day for 6 months on my Windows 10 Pro laptop, without *any* crashes (ok maybe once once but I'm not going to complain, awesome software). Recently I got a new laptop with Windows 10 Home and installed VirtualBox 6.1.14. VM crashed several times and behaved strangely, like Firefox in the VM would crash, or after being in ""screensave"" mode then login would crash and once re-logged in my apps would be gone I would have to restart them, that kind of stuff. I tried a few things, like upgrading Windows 10 to Pro, turning off audio etc. But the only that worked was to rollback to VirtualBox 6.1.4. I did not try 6.1.6, 8, 10 or 12, but clearly a bug got introduced in one of those or in 6.1.14.  ",schollii
19977,USB3 UASP SATA SSD support,Windows,VirtualBox 6.1.14,2020-10-17T17:43:27Z,2020-10-17T17:43:27Z,2020-10-17T17:43:27Z,"Hi,

I connected my Usb 3 Sata Ssd Mx500 to the host. I can see UASP is supported and enabled in CrystalDisk Info, in Windows 10. However, it is not in the guest (same OS). I have of course installed Virtualbox extension pack.

The difference in speed is high: with CrystalDiskMark, I have around 320MB/s in guest and 450MB/s in host.

Workaround:
Mount the drive in guest. The benchmark shows similar result that in host.

This is a good improvement I think, but no a priority.

Env: Windows 10 in host/guest
Virtualbox 6.1.14 with guest additions in guest + extension pack.",myroad
19968,File transfers to / from guest corrupted,Linux,VirtualBox 6.1.14,2020-10-14T16:03:34Z,2020-10-15T18:02:39Z,2020-10-15T18:02:39Z,I have a Centos guest OS running on Win10 host. I am unable to reliably transfer files or perform a Yum update on the guest OS. With Yum update the checksums consistently fail - but always different values for the downloaded file. Mozilla FTP and WinSCP to the guest also fail. Makes no difference whether using bridged network or local host. Seems to occur on all VM's I have running. What can be causing this? Seems everything else runs ok.,VicK
19965,Windows7 virtual machine stops,Windows,VirtualBox 6.1.14,2020-10-14T07:12:21Z,2020-10-14T07:12:21Z,2020-10-14T07:12:21Z,"I tried to start Beckhoff plc in run mode, it has been running earlier in this VM. But now in this version i onlny come to this stop mode of the VM.",GoranP
19955,VirtualBox Manager crashes when opening,other,VirtualBox 6.1.14,2020-10-10T18:08:05Z,2020-10-10T18:09:03Z,2020-10-10T18:09:03Z,"Occasionally, the VirtualBox Manager crashes when starting. Host - Windows 10 x64.

Stack trace:


{{{
>	Qt5GuiVBox.dll!QPainter::PixmapFragment::create() + 2312 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::wheelEvent() + 1864 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::removeItem() + 2447 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsScene::destroyItemGroup() + 823 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsView::paintEvent() + 1570 bytes	Unknown
 	Qt5WidgetsVBox.dll!QAbstractSlider::event() + 1439 bytes	Unknown
 	Qt5WidgetsVBox.dll!QFrame::event() + 55 bytes	Unknown
 	Qt5WidgetsVBox.dll!QGraphicsView::viewportEvent() + 164 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters() + 222 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 254 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2267 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 678 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::paintSiblingsRecursive() + 913 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::drawWidget() + 2731 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::invalidateBuffer_resizeHelper() + 7691 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::invalidateBuffer_resizeHelper() + 8246 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidgetPrivate::syncBackingStore() + 71 bytes	Unknown
 	Qt5WidgetsVBox.dll!QWidget::underMouse() + 14914 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 274 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5GuiVBox.dll!QGuiApplicationPrivate::processExposeEvent() + 277 bytes	Unknown
 	Qt5GuiVBox.dll!QGuiApplicationPrivate::processWindowSystemEvent() + 306 bytes	Unknown
 	Qt5GuiVBox.dll!QWindowSystemInterface::sendWindowSystemEvents() + 153 bytes	Unknown
 	Qt5GuiVBox.dll!QWindowSystemInterface::flushWindowSystemEvents() + 374 bytes	Unknown
 	qwindows.dll!00007ffba0e161b9()	Unknown
 	qwindows.dll!00007ffba0e20cf5()	Unknown
 	qwindows.dll!00007ffba0e2134c()	Unknown
 	user32.dll!CallWindowProcW() + 1016 bytes	Unknown
 	user32.dll!DispatchMessageW() + 924 bytes	Unknown
 	user32.dll!SendMessageTimeoutW() + 323 bytes	Unknown
 	ntdll.dll!KiUserCallbackDispatcher() + 36 bytes	Unknown
 	win32u.dll!NtUserDispatchMessage() + 20 bytes	Unknown
 	user32.dll!DispatchMessageW() + 682 bytes	Unknown
 	combase.dll!RoClearError() + 1131 bytes	Unknown
 	combase.dll!RoGetAgileReference() + 11354 bytes	Unknown
 	combase.dll!RoGetAgileReference() + 10555 bytes	Unknown
 	combase.dll!CoWaitForMultipleHandles() + 4854 bytes	Unknown
 	combase.dll!WindowsCompareStringOrdinal() + 2051 bytes	Unknown
 	combase.dll!CoInitializeEx() + 9499 bytes	Unknown
 	combase.dll!CoGetStandardMarshal() + 3028 bytes	Unknown
 	combase.dll!CStdStubBuffer_Invoke() + 366 bytes	Unknown
 	rpcrt4.dll!Ndr64AsyncServerCallAll() + 2884 bytes	Unknown
 	combase.dll!PropVariantClear() + 3080 bytes	Unknown
 	combase.dll!00007ffbc8239082()	Unknown
 	UICommon.dll!CVirtualBox::GetVersion() + 89 bytes	Unknown
 	VirtualBox.exe!00007ff72a8c9e55()	Unknown
 	Qt5CoreVBox.dll!QAbstractAnimation::event() + 201 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplicationPrivate::notify_helper() + 274 bytes	Unknown
 	Qt5WidgetsVBox.dll!QApplication::notify() + 7243 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::notifyInternal2() + 168 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplicationPrivate::sendPostedEvents() + 561 bytes	Unknown
 	qwindows.dll!qt_plugin_instance() + 9871 bytes	Unknown
 	Qt5CoreVBox.dll!QEventDispatcherWin32::registerEventNotifier() + 1330 bytes	Unknown
 	user32.dll!CallWindowProcW() + 1016 bytes	Unknown
 	user32.dll!DispatchMessageW() + 601 bytes	Unknown
 	Qt5CoreVBox.dll!QEventDispatcherWin32::processEvents() + 1172 bytes	Unknown
 	qwindows.dll!qt_plugin_instance() + 9833 bytes	Unknown
 	Qt5CoreVBox.dll!QEventLoop::exec() + 461 bytes	Unknown
 	Qt5CoreVBox.dll!QCoreApplication::exec() + 338 bytes	Unknown
 	VirtualBox.exe!TrustedMain() + 821 bytes	Unknown
 	VirtualBox.exe!TrustedMain() + 1489 bytes	Unknown
 	VirtualBox.exe!00007ff72a9b8a5e()	Unknown
 	VirtualBox.exe!00007ff72a9b6d97()	Unknown
 	kernel32.dll!BaseThreadInitThunk() + 20 bytes	Unknown
 	ntdll.dll!RtlUserThreadStart() + 33 bytes	Unknown

}}}
",fandrei
19947,Full Screen does not come up when using the latest version of Guest Additions,Linux,VirtualBox 6.1.14,2020-10-07T13:00:24Z,2020-10-08T09:52:02Z,2020-10-08T09:52:02Z,"Hello! 

I am working with the https://images.apertis.org/release/v2021dev3/v2021dev3.0/amd64/sdk/apertis_v2021dev3-sdk-amd64-sdk_v2021dev3.0.vdi.gz SDK which is based on the Debian 10 Buster distribution. I tried to enable the full screen mode on the same SDK by installing the v6.1.14 guest additions from Oracle [https://download.virtualbox.org/virtualbox/6.1.14/]

After installing the same and on rebooting the SDK, it does not boot in the Full screen mode and instead the window shrinks. 

I also performed the same operations on the Debian_10.1.0_VirtualBox_Image_LinuxVMImages.ova image [https://www.linuxvmimages.com/images/debian-10/] 

The Debian VM starts with 6.0.14r133895 GA and fullscreen worked, then after upgrading to 6.1.14r140239 GA it is no more going to fullscreen
and it boots with a smaller screen.

I will attach the log files for the same. ",sagar123
19943,"""Invalid Settings Detected"" System : Acceleration page",Linux,VirtualBox 6.1.14,2020-10-06T10:43:35Z,2020-10-06T10:43:35Z,2020-10-06T10:43:35Z,"I tried to use ""old"" machine (created in previous versions of virtualbox) with the actual Virtualbox 6.1.14. But I got a problem described by other people

https://www.reddit.com/r/virtualbox/comments/efffap/i_have_a_problem_invalid_settings_detected/

https://www.reddit.com/r/virtualbox/comments/eig7f4/invalid_settings_detected/


It looks like there was a checkbox ""Enable VT-x|AMD-V"" in Settings>System>Acceleration in 6.0.x linked to the ""Invalid Settings Detected"" alert.

And it looks like in 6.1.x the checkbox was removed but the requirement to unset it was left somehow. 
",jekka
19940,Nested Virtualization makes guest os freeze,Linux,VirtualBox 6.1.14,2020-10-05T13:57:58Z,2020-10-05T13:57:58Z,2020-10-05T13:57:58Z,"I have the last version of virtualbox and I have Kali Linux virtual machine and I want to start android virtual machine on it and I have done the setup for everything and enabled Nested virtualization in virtualbox and installed kvm on guest os for acceleration but every time I try to start the emulator, It appears with the message:-


""Emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.""


and the guest os suddenly freezes totally and no longer responds.

My PC's CPU is Intel core I7-8750H (6 cores) and 16GB ram.
What is the problem? How can I solve it?",MINE
19927,"Audio: garbled and hanging audio is caused by a ""bug"" in VirtualBox 5.x and up",other,VirtualBox 6.1.14,2020-09-29T03:58:05Z,2020-10-04T01:29:11Z,2020-10-04T01:29:11Z,"Tested in Reactos

source :  https://github.com/reactos/reactos/pull/3141

https://github.com/reactos/reactos/files/5210800/ac97-crash-reactos-msvc.log

",Blackcrack
19921,VirtualBox Version 6.1.14 r140239 (Qt5.6.2) will not work with Windows Preview,Windows,VirtualBox 6.1.14,2020-09-27T11:31:44Z,2020-09-29T08:32:15Z,2020-09-29T08:32:15Z,"Edition	Windows 10 Pro Insider Preview
Version	2004
Installiert am	‎24.‎09.‎2020
Betriebssystembuild	20221.1000
Leistung	Windows Feature Experience Pack 120.22800.0.0
",DKKABG
19922,Fedora 32 Workstation official ISO fails to install stating integrity problems,Linux,VirtualBox 6.1.14,2020-09-27T19:29:36Z,2020-09-27T19:29:36Z,2020-09-27T19:29:36Z,"I download https://torrent.fedoraproject.org/torrents/Fedora-Workstation-Live-x86_64-32.torrent from https://torrent.fedoraproject.org/ . While torrent guarantees file isn't corrupt, I also check the file per vendor instructions.

 sha256sum -c Fedora-Workstation-32-1.6-x86_64-CHECKSUM
Fedora-Workstation-Live-x86_64-32-1.6.iso: OK

When I try to install this specific image, its media check stops at exactly 4.8% and suggests not to use this image. If you ignore (e.g. disable check), it doesn't succeed booting anyway.

Today, I installed VMWare Workstation Player 16 and amazingly, very same ISO passed every test and installed fine. I think I may have triggered a Virtualbox (or windows?) bug.",Ilgaz
19920,/bin/ls: reading directory : Protocol error for asian fonts,Linux,VirtualBox 6.1.14,2020-09-26T09:37:26Z,2020-09-26T09:37:26Z,2020-09-26T09:37:26Z,"On my Windows 10 host I am not able to 'ls' a directory with these Asian characters: 

HID_Miniport_Device_￿࿘낖彴.hid

These characters appear in the ProtableApps version of Mixxx.
This is my error message.

neo:~/PortableApps/MixxxPortable/Data/MixxxSettings$ ls controller
/bin/ls: reading directory 'controller': Protocol error

After I delete such files 'ls' works well again.",Frank Breitling
19913,linux guest processes terminated after win10 host sleep,Linux,VirtualBox 6.1.14,2020-09-24T14:48:43Z,2020-09-24T14:48:43Z,2020-09-24T14:48:43Z,"(similar to https://www.virtualbox.org/ticket/19131)

Windows 10 1904 host
Ubuntu 20.04-LTS guest (created with 6.1.10 IIRC)
virtualbox-6.1.14 with 6.1.14 extension pack

situation occurs when host goes into sleep on its own (my power settings are set never to hibernate when on line power)

result:
- running apps and windows in guest are all exited
- docker containers are exited
- system uptime seems to be correct

in attached log, the situation likely occurred starting at ""07:39:12.135290"" as this delta from the log opened time corresponds to the time docker reports my container exited
",DanielH_
19911,Fresh VM always crashing due to RAM issue,Linux,VirtualBox 6.1.14,2020-09-23T08:31:44Z,2020-09-23T08:31:44Z,2020-09-23T08:31:44Z,"Hey,

recently I built a new computer with 16 GB of DDR4 ram, a Ryzen 7 3700X and a Nvidia RTX 2060 Super. On my old one I never experienced any problems with Virtualbox but now any new VM I create crashes right after I reboot it after installation (Every driver I can think of is up-to-date). 

Of course I will supply more information if you need any. Maybe the log files can already help a lot with this problem.

Thanks in advance

PT400C",PT400C
19899,Virtualbox 6.1.14 shared paper press and drag and drop don't work,Linux,VirtualBox 6.1.14,2020-09-18T19:04:32Z,2020-09-18T19:04:32Z,2020-09-18T19:04:32Z,"Hello,
With the latest version of virtualbox (6.1.14) on a type of Windows10
host and a type of Linux ubuntu v 19.10 guest 
I have a problem with the shared paper press and the drag and drop 
(In Bi-directionnel position)that don't work.
VBox Guest Additions Linux v 6.1.14 installed

Can you help me solve this problem?
Thanks.Regards.
KAT",KAT66
19893,Plantage de la VM : Code d’arrêt : CRITICAL STRUCTURE CORRUPTION,Windows,VirtualBox 6.1.14,2020-09-18T09:14:21Z,2020-09-18T09:18:27Z,2020-09-18T09:18:27Z,"Depuis le passage en 6.1.14 sur en un hôte en Windows 10 2004 et de l'invité en Windows 10 2004, plantage régulier de l'invité avec l'erreur -> Code d’arrêt : CRITICAL STRUCTURE CORRUPTION",LFX_LFX
19881,AltGr not working most of the time,Linux,VirtualBox 6.1.14,2020-09-10T16:11:59Z,2020-09-11T07:33:32Z,2020-09-11T07:33:32Z,"Setup is a Linux (nixos 20.03) VM on a Windows 10 laptop, usually with 2 screens attached. The VM gets 3 virtual screens.
Both host and guest use a german (qwertz) keyboard layout.

Most of the time, the AltGr key and with it many symbols are not working on the guest. According to xev pressing the key does not trigger anything at all.

Often, but not always, changing from one virtual display to another will make the AltGr key work for a few times before falling back to not doing anything at all.

Sometimes, when changing to another screen and beginning to type, the first letter will be greek and I don't even know how to type those deliberately (it's not AltGr+something).

There have been days where it worked the whole time but those are rare.

Turning automatic keyboard capturing off as some related incidents suggested as solution does not help.

Suspending (save execution state) and restarting does also not help reliably.


To me it seems as if somehow the modifier gets stuck or a wrong keycode is sent or it gets out of sync between host and guest or between the virtual screens?
I can't really find any 100% reliable way to trigger or fix this behaviour.


I'll gladly provide any additional info or perform tests that could help this issue.",Nervengift
19876,guest language change changes host,Windows,VirtualBox 6.1.14,2020-09-10T00:24:37Z,2020-09-10T00:24:37Z,2020-09-10T00:24:37Z,"i am learning german, and though useing a computer in german would help, but when i setup a windows 10 guest on a windows 10 host, and install a new language, it also installs on the host, and changed my time, and language, on top of adding it to the host. when i delete the forein language from the host, it dissapears on the guest as well",devsch
19867,Unable to run Windows 7 64 Bit OS Virtual Machine,Windows,VirtualBox 6.1.14,2020-09-07T10:15:34Z,2020-09-07T10:29:53Z,2020-09-07T10:29:53Z,Unable to run Windows 7 64 Bit OS Virtual Machine,rdua
20132,Guest Windows XP x86 Does Not Shutdown with Serial Ports Enabled,Windows,VirtualBox 6.1.16,2021-01-17T21:44:24Z,2021-10-02T09:33:32Z,2021-10-02T09:33:32Z,"Host is Windows 10 x64. Serial ports COM 1-4 are from PCI-E Moxa CP-144EL Series card running the version 3.00 driver. All COM ports are working properly on host OS.

Guest OS Windows XP x86 recognizes COM ports 1-4 through the Host Device port mode. Port path on !VirtualBox is set to the identical port on host PC. Communication with a connected device is successful.

Upon shutdown of guest OS the shutdown process hangs with:

{{{
00:05:15.665094 HostSerial#0: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665170 HostSerial#1: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665256 HostSerial#2: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
00:05:15.665307 HostSerial#3: The underlying host device run into a fatal error condition VINF_SUCCESS, any data transfer is disabled
}}}

Host has to be rebooted afterwards or rarely BSOD error happens upon shutdown.",yordan
20461,Can not drag and drop from host to guest,Windows,VirtualBox 6.1.16,2021-07-17T00:32:15Z,2021-08-24T13:51:59Z,2021-08-24T13:51:59Z,"Host Windows 10
Guest Windows 8.1
VirtualBox 6.1.16-140961
Guest Additions 6.1.16
VirtualBox Extension Pack 6.1.16-140961

Copy and paste bidirectional works fine.
Drag and drop from Guest to Host works fine.

Drag and drop from Host to Guest is not working.",ewsaracco
20022,VM is causing Guest OS applications ( Slack/Intelli J ) hung,Linux,VirtualBox 6.1.16,2020-11-06T05:43:17Z,2021-07-06T07:20:41Z,2021-07-06T07:20:41Z,"I have windows machine with 32 Gigs RAM and core i7 with 8th Gen. I have installed Ubuntu inside my Oracle VM with 2 cores(Out of 8 Cores) and 8 Gigs RAM (Out of 32 Gigs RAM).

Guest OS application slack or IntelliJ works fine without any issues until I start the Ubuntu using Oracle VM 6.1

As soon I start my Ubuntu on my VM, slack and IntelliJ freezes for every 10 minutes and I need to wait for 2 to 3 minutes to respond and do my work, it became a routine for every 15 minutes.

Unfortunately I do not have any logs because I do not see any network/cpu/disk usage spike, when these applications get hung. ",Sandeep Reddy
20217,Xmodmap needs several executions on Windows 10 host,Linux,VirtualBox 6.1.16,2021-02-21T23:19:23Z,2021-02-21T23:19:23Z,2021-02-21T23:19:23Z,"This is my .Xmodmap in a GNU/Linux guest:

{{{
! Use Menu as a slash
keycode 135 = slash

! Swap Esc and Alt under VirtualBox guest
remove mod1 = Alt_L
keysym Escape = Alt_L
keysym Alt_L = Escape
add mod1 = Alt_L
}}}

This is an excerpt from my .xinitrc:
{{{
usermodmap=""${HOME}/.Xmodmap""
[[ -r ""${usermodmap}"" ]] && xmodmap ""${usermodmap}""
}}}

After startx my desired key bindings are not active. On average I have to execute the following command twice more in a terminal emulator for it to take effect: xmodmap ~/.Xmodmap 

I created a menu item in the TWM window manager that executes: ""xmodmap ~/.Xmodmap ; xmodmap ~/.Xmodmap ; xmodmap ~/.Xmodmap"". 

But even with this usable workaround it is certainly annoying, and I frequently forget to run it from the menu on boot.


Extra information,

Host: Windows 10 19042 

virtualbox extension pack: 6.1.16r140961


Guest: Arch Linux 

virtualbox-guest-utils: 6.1.16 

xorg-server: 1.20.10 

xf86-input-libinput: 0.30.0 

libinput: 1.16.4

X.org configuration:
{{{
Section ""InputClass""
    Identifier      ""keyboard""
    MatchIsKeyboard ""on""
    Option     ""XkbLayout""   ""hr,us""
    # XkbOptions list: /usr/share/X11/xkb/rules/base.lst
    Option     ""XkbOptions""  ""grp:shifts_toggle,terminate:ctrl_alt_bksp""
EndSection
}}}
",anrxc
20205,OL8 VM aborted - appears screen resize or USB related,Linux,VirtualBox 6.1.16,2021-02-19T12:24:44Z,2021-02-19T12:24:44Z,2021-02-19T12:24:44Z,"Two suspects for my VM aborting:

1. USB. I use a USB dongle and regularly attach/detach via the VBox device menu.

2. Screen resize.  I frequently resize my VM window as I shuffle windows around to different displays, snap to one side of the screen, etc.",mocooern
20188,"Network change cause bridged network broken, no adapters in bridged adapter.",all,VirtualBox 6.1.16,2021-02-14T15:20:32Z,2021-02-14T15:20:32Z,2021-02-14T15:20:32Z,"OS: Windows 10 1909 18363.1316[[BR]]
VBox version: 6.1.16 r140961
----
Problem: (I guess) network changes might cause bridged network broken, like this:
[[Image(https://i.imgur.com/dtOqgNm.png)]]

All interfaces are gone in the bridged adapter. Only showing ""not selected""

----
How to reproduce:

Install/run/upgrade Nox player(a Android simulator, it's a VM that running android) while running the VirtualBox.

And I recorded a video to reproduce this bug: https://www.youtube.com/watch?v=RzTA-qMp3Uk

----
The only way to get bridged network back is upgrade VirtualBox or reinstall.
If I am using the latest VirtualBox, I have to uninstall it, then install it again. Very annoying.
Repair VirtualBox/reboot PC doesn't work.

I guess the installation/running process of Nox player changed some network setting, cause VirtualBox lost all of the network setting. And repair doesn't reconfigure it.

Is there any other way I can reconfigure network settings without reinstall? 
The only way to reconfigure it that I found is uninstall and install again, which makes me reboot my PC twice and reconfigure all vm again.

And pleasse fix this bug,thank you. The network of VM always crash after I running the Nox player. I can't use VirtualBox at all.",HuJK
20081,Installing Linux subsystem on windows 10 caused read/write error inside running linux mint (in virtual box),Linux,VirtualBox 6.1.16,2020-12-05T10:00:50Z,2021-01-24T12:07:45Z,2021-01-24T12:07:45Z,"I'm not used to write these, but if this is a real but, it's a serious one.

I don't have any log files, because during the search for a solution, things have been purged and reinstall many times.

but I'll try to describe as good as I can.

 Basically, I installed Linux subsystem on my windows 10 2004 machine.

Then I upgraded the wsl1 to wsl2 on windows.

Now after the night, I had some scripts running on my linux, scanning and identifying images /copying/sorting.

on the morning it had crashed, and in the terminal running the script it said something about ""segmentation fault core dumped""

I didn't realize it was so serious so I only restarted it. 

I got a few screenshots from a boot, don't remember what I booted, if it was a rescue disc or linux mint installation disc, but it shows some error info.

I uninstalled linux subsystem and Ubuntu 20 that I had installed on Windows, and tried to install linux mint on a new  virtual box, but after a while updates started to fail, and installation of software resulted in read/write error.

after a while I remembered that I didn't uninstall the wsl2 update from windows.

I uninstalled it, tried to reinstall linux mint, an now everything worked fine, no issues,  no errors, everything worked as it should.

so apparently did the wsl2 update interfere with how virtual box was accessing the .vdi files?

well, that's basically what happened.. sorry I can't give any logs, but this issue might be worth investigating..",Nemesis 77
20102,Unable to compile Guest Additions on Linux Kernel 5.4.80.,Linux,VirtualBox 6.1.16,2020-12-26T22:21:43Z,2021-01-22T15:47:46Z,2021-01-22T15:47:46Z,"I am trying to install the guest additions for Linux, and I'm encountering a problem. I have Gentoo Linux with the 5.4.80 kernel, and I get MANY missing symbols. They are:

{{{
ERROR: ""ttm_bo_eviction_valuable"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_tt_fini"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_put"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_move_to_lru_tail"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_validate"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_add_to_lru"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_kmap"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_tt_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_dma_acc_size"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_init_mm"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_device_init"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_del_sub_from_lru"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_kunmap"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_device_release"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_manager_func"" [/tmp/vbox.0/vboxvideo.ko] undefined!
ERROR: ""ttm_bo_mmap"" [/tmp/vbox.0/vboxvideo.ko] undefined! 
}}}

Notice that all are in the vboxvideo.ko module.

Any tips are most appreciated.
",TheStudent
20145,BSOD when a VM is shut down,Windows,VirtualBox 6.1.16,2021-01-21T07:14:05Z,2021-01-22T04:38:45Z,2021-01-22T04:38:45Z,"This issue is not new, but finally I'm fed up. I thought that you get crash reports from Microsoft, but perhaps this is not the case. It's been perhaps a year that this been happening and no solution still.
At least 4 out of 5 times when a particular Windows 7 VM is shut down (not when it's restarted only), it causes the BSOD (memory corruption) on the Windows 10 host. It's more likely to happen when the VM has been running at least several hours, but this is not a requirement. The below info is from the debugger, but I don't know how to debug that, only providing this as a proof it's !VirtualBox (VBoxDrv.sys) that causes the crash.

{{{
BugCheck 1A, {1236, ffff8a871b92b000, ffff8a871b92b308, 242513}

* ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxDrv.sys - 
* ERROR: Symbol file could not be found.  Defaulted to export symbols for VMMR0.r0 - 
Probably caused by : memory_corruption


BUGCHECK_STR:  0x1a_1236

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80782747406 to fffff807827f5780

STACK_TEXT:  
fffff98f`33cdf518 fffff807`82747406 : 00000000`0000001a 00000000`00001236 ffff8a87`1b92b000 ffff8a87`1b92b308 : nt!KeBugCheckEx
fffff98f`33cdf520 fffff807`8271fc5b : ffff8a87`1b92b000 ffff87f2`00000000 ffffed80`06c6f390 ffff8a87`00000001 : nt!MiFreePagesFromMdl+0x4c2
fffff98f`33cdf5b0 fffff807`881be341 : ffff8a87`19ae7010 ffff8a87`1b530aa0 ffff8a87`1b931010 01000000`00100000 : nt!MmFreePagesFromMdl+0xb
fffff98f`33cdf5e0 fffff807`8818347b : ffff8a87`1b92d010 ffff8a87`1b530aa0 ffff8a87`1b931010 00000000`0d846602 : VBoxDrv!g_abRTZero4K+0x12bf1
fffff98f`33cdf610 fffff807`7ebd5f15 : ffff8a87`19ae7010 ffff8a87`19ae7010 ffff8a87`19ae7010 fffff807`8270f2b9 : VBoxDrv!RTR0MemObjFree+0xfb
fffff98f`33cdf640 fffff807`7ebd6a8f : ffff8a87`1b931010 ffff8a87`19ae7260 ffff8a87`16625000 fffff807`8818227c : VMMR0!GMMR0Term+0x645
fffff98f`33cdf6c0 fffff807`7ebd856a : 00000000`00002000 ffff8a87`19ae7018 ffff8a87`19e02010 ffff8a87`16625000 : VMMR0!GMMR0CleanupVM+0x25f
fffff98f`33cdf720 fffff807`7ebd8794 : ffff8a87`19e02030 ffff8a87`16625000 ffff8a87`19e02010 ffff8a87`19e02030 : VMMR0!GVMMR0DestroyVM+0x39a
fffff98f`33cdf750 fffff807`88161cc1 : ffff8a87`1100c8d0 00000000`00000055 ffff8a87`19e02030 ffff8a87`09e02000 : VMMR0!GVMMR0DestroyVM+0x5c4
fffff98f`33cdf7a0 fffff807`7ebd8465 : ffff8a87`16625000 00000000`00000003 00000000`00042000 fffff807`826501c1 : VBoxDrv!SUPR0ObjRelease+0x171
fffff98f`33cdf7d0 fffff807`7ebfe2a1 : 00000000`00000000 00000000`00000000 ffff8a87`171e07c0 00000000`00000000 : VMMR0!GVMMR0DestroyVM+0x295
fffff98f`33cdf840 fffff807`7ebff4ff : 00000000`00000021 00000000`00000000 00000000`00000000 fffff807`8266119e : VMMR0!ModuleInit+0x6e1
fffff98f`33cdf8a0 fffff807`88167bfb : ffff8a87`1d9e7010 ffff8a87`0f8331a0 00000000`00000000 ffff8a87`171e07c0 : VMMR0!VMMR0EntryEx+0x9f
fffff98f`33cdf910 fffff807`881760d4 : 00000000`00000030 fffff98f`33cdfcc0 00000000`00000030 ffff8a87`00000000 : VBoxDrv!SUPR0PageFree+0x296b
fffff98f`33cdf980 fffff807`829fcb82 : 00000000`0022821c fffff807`88175df0 00000000`09a3f848 ffff8a87`00000030 : VBoxDrv!SUPR0IoCtlPerform+0x25a4
fffff98f`33cdfa20 fffff807`829fc7e6 : ffff8a87`189897c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
fffff98f`33cdfb60 fffff807`828071b5 : ffff8a87`178f9080 fffff98f`33cdfcc0 00000000`09a3e4f8 fffff98f`33cdfbe8 : nt!NtDeviceIoControlFile+0x56
fffff98f`33cdfbd0 00007ffa`ad14c094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`09a3f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffa`ad14c094
}}}

I can provide more info (just ask), perhaps even upload the memory dump for analysis, but I don't have the skills to analyze the crash dump myself.
",Rafcio
20136,"upon resume getting ""VBoxClient: Crtc disable failed 63""",Linux,VirtualBox 6.1.16,2021-01-19T17:15:10Z,2021-01-19T17:15:10Z,2021-01-19T17:15:10Z,"6.1.16 r140961 (Qt 5.6.2)

Sometime reactivating the ""full screen"" fixes it, sometimes I have to reboot",ralfhauser
20135,After installing Centos OS the VM is failing to reboot,Linux,VirtualBox 6.1.16,2021-01-18T21:52:15Z,2021-01-18T21:52:15Z,2021-01-18T21:52:15Z,"The Host PC is Windows 10, after installing a Centos minimal image using vagrant the image fails to boot. There are obvious errors that in the log file.
I have installed an ubuntu vm and that works fine.

",harryv
20134,Guest OS will not boot,all,VirtualBox 6.1.16,2021-01-18T18:45:00Z,2021-01-18T18:45:00Z,2021-01-18T18:45:00Z,"Whenever I try to boot ''any'' guest OS, it will freeze and enter guru meditation. This happens on MBR and UEFI based guest OS.
",Pupilliam
20127,Finalize File System fails,Linux,VirtualBox 6.1.16,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,2021-01-14T18:45:16Z,"Failed to finalize file system
",MikeTheBike
20124,Unable to add Guest Addition in macOS Big Sur 11.1,other,VirtualBox 6.1.16,2021-01-12T09:45:29Z,2021-01-12T09:45:29Z,2021-01-12T09:45:29Z,"Host - Windows 10 20H2
Guest - macOS Big Sur 11.1

Unable to add Guest Addition. After double-clicking VBoxDarwinAdditions.pkg installer fails with the message - The installation failed. The installation encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.",hrk
20111,"Drag and Drop not working: Windows 10(host), Fedora 33(guest)",Linux,VirtualBox 6.1.16,2020-12-31T15:26:22Z,2020-12-31T15:26:22Z,2020-12-31T15:26:22Z,"Hi there,

I am working with VirtualBox 6.1.16 r140961 with a Windows 10 (1909) host and a Fedora 33 guest. Guest Additions are seemingly installed correctly. The clipboard is working fine bidirectionally.
Files drag and drop doesn't work in any direction.

Attached log files made as described here: https://www.virtualbox.org/wiki/DnDDebug

Thanks in advance and best regards
Pavel",nashoboima
20110,Virtualbox looses track of USB SSD,Linux,VirtualBox 6.1.16,2020-12-31T06:45:36Z,2020-12-31T06:45:36Z,2020-12-31T06:45:36Z,"I've encountered a big glitch. If I create a virtual machine with no virtual drive, and then use a USB filter to attach a USB SSD (WD Passport if it matters) to the virtual machine, then it will find that drive no problem for ONLY the first powercycle. Rebooting without powering down the machine makes no difference. But if you power the machine down (not save state, actually set the machine as turned off), then try to turn it on again, it won't find the SSD. It boots into the EFI shell, and the EFI shell reports no file systems, or it reports the Optical Disc file system if there is one. But it doesn't see the USB drive. The only way I've been able to fix this is to completely delete the machine and re-create from scratch. That's annoying and stupid!
",TheStudent
20109,Guest Bridged Networking Stops Working After Host Link Was Down,Windows,VirtualBox 6.1.16,2020-12-31T00:11:39Z,2020-12-31T00:11:39Z,2020-12-31T00:11:39Z,"I tested bridged networking on a Windows 10 Host with a Windows 7 64-bit Guest and a Windows XP 32-bit Guest.  They both exhibit the same problem with a bridged network adapter.  If the host's bridged link was down when the virtual machine was started, or goes down temporarily after the virtual machine is started, communication is lost through the bridged adapter on the host.  It is still possible to ping the host's address assigned to the real adapter, but no devices connected to the LAN on the real host adapter will communicate.

Virtual Network Adapter
Windows 7 64-bit Intel PRO/1000 MT
Windows XP 32-bit PCnet-FAST III

Host LAN Adapter Intel I219-V (1 Gb) VEN 0x8086 DEV 0x15B8
Host OS Windows 10 64-bit 10.0.19042

The work around for the problem is to temporarily disable and then enable the host LAN adapter using the Network Connections in the Control Panel.  Then disable and enable the virtual network adapter in the devices menu for the virtual machine.  After doing both of those things, the bridged adapter will communicate again.  I have noticed that it sometimes recovers if I just temporarily disable the network adapter for the virtual machine, but that seems to depend on whether the host adapter was up when the virtual machine was started.

I noticed this problem on a LAN port connected to a test network that normally has the switch powered off until I need to run tests.  If I power up the switch after starting the virtual machine then there is no communication to the network switch until I perform the steps that I outlined.",ErikWlfn
20100,BSOD caused by VirtualBox and USBNetworkGate,other,VirtualBox 6.1.16,2020-12-24T19:17:27Z,2020-12-24T19:17:27Z,2020-12-24T19:17:27Z,"Hi,

I'd like to report a bug relating to the VirtualBox and USB Network Gate software by Eltima/Electronic Team.

The below set of circumstances cause a BSOD in Windows 10. Tested on Win10 Pro 1909, 2004 and 20H2 updates on Intel and AMD CPUs and Lenovo and MSI hardware (available at the time of testing). Guest type did not seem to matter, they were not running or on some devices not even setup.

USBNetGate is installed
VirtualBox is installed AND running (extension pack and no extension pack does not make a difference, different USB controller settings VMs do not make a difference)
USB device is physically being plugged in - at this point machine will crash with blue screen.

Unplugging a device does not cause a crash.
Unplugging or plugging in a device while VirtualBox is not running does not cause a crash
Unplugging or plugging a device while VirtualBox is running and USBNetGate is not installed does not cause a crash.

It is unclear which software is the cause, it only happens with both active at the same time.",JP-BC-Can
20096,Crash when powering off guest OS,Linux,VirtualBox 6.1.16,2020-12-19T01:59:57Z,2020-12-19T01:59:57Z,2020-12-19T01:59:57Z,"Host: Windows 10 build 17763 amd64
Guest: Ubuntu 18
1. Start guest OS
2. Sleep/resume host computer (not sure if this is necessary but seems related)
3. From within the guest OS, select the power off setting.
Message box appears: The instruction at 0x0000&FF9E4808561 referenced memory at 0x0000000000000021. The memory could not be written.

This crash is intermittent and happens prior to the screen resizing to the linux text-based shutdown screen (i.e. guest is still running X)",jkriegshauser
20094,VB Blank screen after one day.,Linux,VirtualBox 6.1.16,2020-12-16T21:46:23Z,2020-12-17T14:52:09Z,2020-12-17T14:52:09Z,"
While running VB version Versie 6.1.16 r140961 (Qt5.6.2) on Windows host computer (windows 10 pro) after one day the VB screen will turn blank.

Only closing the program and restarting it will show the regular screen again.

Is there a fix ?

[img]https://imgur.com/3s39bcD[/img]
",VB-box
20023,After Update to 6.1.16: Black screen after booting Ubuntu in fullscreen,Linux,VirtualBox 6.1.16,2020-11-06T08:01:30Z,2020-12-11T08:01:49Z,2020-12-11T08:01:49Z,"I use Ubuntu 18.04.5 LTS (64-bit) as guest and Windows 10 as host and always do all VirtualBox-, Ubuntu and Windows-updates available. 

I boot into fullscreen mode. Since Upgrading to 6.1.16 after booting the screen is black. The boot screen-sequence (purple screen with Ubuntu logo and some text output) appears. But once the desktop should appear the entire display is black. Not the entire: At the bottom the VirtualBox-toolbar is available and accessable. Once I use it to switch to window-mode the screen refreshes and I can see and use the desktop. After that I'm able to re-activate the fullscreen mode and fullscreen works as expected.

If I boot in window-mode then the desktop is shown as expected. I also tried to boot without 3D acc. but the screen is also black without this setting.

Settings:
Mem: 24576 MB (host 32 GB)
CPUs: 12 (host 12)
CPU-limit: 95%
options: VT-x/AMD-V, Nested Paging, PAE/NX, KVM
Graphics: 128 MB, VMSVGA, 3D acc.
Storage: IDE: VBoxGuestAdditions.iso, SATA: mydisk.vdi (SSD enabled)
Audio: disabled
Network: 1 adapter Intel PRO/1000 MT Desktop (NAT)
USB: xHCI
Shared folders: 1

Host-OS: Windows 10
Host-graphics: GeForce RTX 2060, set NVIDIA 3D to use GeForce for virtualboxvm.exe instead of internal graphics of the laptop.",stevep
20088,Soft reset from guest does not reliably restart VM,Linux,VirtualBox 6.1.16,2020-12-09T08:43:00Z,2020-12-09T08:43:00Z,2020-12-09T08:43:00Z,"On a Windows host with a Linux Debian 10 guest, issuing a ""reboot"" command to the guest OS does not seem to reliably restart the VM (although it does most of the time). When this fails, it results in a blank/black screen on the guest VM and nothing further happens. It is required that the user manually power off the VM and restart it from scratch.

For example, at this point the reboot trigger seems to be recognised from the logs:
00:01:48.843711 OHCI: Software reset
However, nothing further happens until 5 minutes later when I forcibly power it off:
00:06:59.972369 Console: Machine state changed to 'Stopping'

Logs are attached.",rdghickman
20087,Sending multiple VBoxManage commands can cause VBox GUI to hang,Linux,VirtualBox 6.1.16,2020-12-09T08:37:53Z,2020-12-09T08:37:53Z,2020-12-09T08:37:53Z,"We have scripts that issue multiple VBoxManage commands to start/stop VMs. Very often if multiple commands are sent and you interact with the UI (mostly with the VM that VBoxManage is acting upon) the GUI will freeze/hang indefinitely and often VBoxManage will as well. Terminating the GUI forcibly and restarting it makes it fine until you again single left-click on the VM in the UI upon which time it freezes again. Rebooting Windows makes VBox usable again but leaves the VMs in state aborted.

Staggering VBoxManage commands seems to be a workaround with at least partial success.",rdghickman
20070,audio only works every other startup,Windows,VirtualBox 6.1.16,2020-11-29T02:41:08Z,2020-12-09T00:12:07Z,2020-12-09T00:12:07Z,"If I have a VM with Windows 7 and I close and ""save the machine state"", then start it up again later, every other time I do that the audio/sound works. Every other time, it does not work. Occasionally, I can disable the virtual sound card within Windows and reenable it and it will work. Otherwise, I have to close the VM and restart it.
This happens with the current latest version of VirtualBox and has happened with multiple VMs and across several versions of VirtualBox.",RAR
20085,MachineWrap,all,VirtualBox 6.1.16,2020-12-07T19:21:45Z,2020-12-07T19:21:45Z,2020-12-07T19:21:45Z,"Hi Team,

For somewhat, I have had an issue with Virtualbox. This message has appeared when I start the VM. 

Here is the message:

'''''The virtual machine 'AppDynamics' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\ferna\VirtualBox VMs\AppDynamics\Logs\VBoxHardening.log'.


Código de Resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}'''''


Could you help me? I attached the logs here.

I already tried to uninstall and install again, but I haven't a success.

Kind Regards,
Fernando",fernandofot
20080,Problem running Ubuntu VM,Linux,VirtualBox 6.1.16,2020-12-05T00:34:02Z,2020-12-05T00:34:02Z,2020-12-05T00:34:02Z,"I was trying to set up Windows Subsystem for Linux on my laptop running on Windows 10. I switched on WSL options and restarted the machine. After that I started my Ubuntu VM on VirtualBox. It causes some errors and close the VM. I, then switches off the WLS which started the Ubuntu VM but recommended turning it off. Log file is attached herewith.",mshahin
20079,VRDP Forwarding Touchscreen Events (scrolling in Webbrowser),all,VirtualBox 6.1.16,2020-12-04T21:10:24Z,2020-12-04T21:10:24Z,2020-12-04T21:10:24Z,"Hello, I tried to connect via VRDP into two machines (Ubuntu and Windows Server 2019). Both connections are working except of forwarding the touchscreen events form the host system. Both machines are configured as USB-Multitouch-Tablet. This problem only appears via VRDP. If I connect for example to the Windows Server 2019 with RDP (RDP Service form Guest OS), the touch events (for example one finger scrolling) are working as expected. Also if I start the machines normal (with GUI) die touch events are working. 

Is this a known issue?
Can I solve this with some additional config?

Thanks",strgey07
20033,"In Windows 10 Host with Hyper-V, setting processor to 2 CPU, installation of Windows 2004 guest stuck at Windows logo",Windows,VirtualBox 6.1.16,2020-11-12T04:48:06Z,2020-12-01T13:34:33Z,2020-12-01T13:34:33Z,"In Windows 10 Host (Windows 10 Home 20H2 and Windows 10 Home 2004), when setting processor to 2 CPU, installation of Windows 10 2004 guest stuck at Windows logo.

I have Hyper-V enabled, because I need to use WSL2 (which requires Hyper-V) and docker desktop (which requires WSL2).

Default processor is set to 1 CPU, Installation of Windows 2004 guest succeeded under 1 CPU, but it won't work with 2 CPU.

I have tested it in MacBook Pro 2020 Bootcamp and a Lenovo desktop PC, same results.",liuzhiyuan1225
20054,network problems under bigsur macOS version,OSX Server,VirtualBox 6.1.16,2020-11-20T14:05:49Z,2020-12-01T11:59:52Z,2020-12-01T11:59:52Z,"I have problems getting a working network connection when I transferred from Catalina to Bigsur

Sometimes VBOX crashes when I use NAT option for the adapter, normally use bridged option",pbvbox
20069,Error,Windows,VirtualBox 6.1.16,2020-11-26T12:27:18Z,2020-11-26T12:27:18Z,2020-11-26T12:27:18Z,"Hey, 
I have got problem with virtual box. It whount start or install system. Only system i can install is windows xp but its very, very slow. I have got Windows 10 Pro 2004.",Daniel_Mandinec
20068,Guru Meditation,Linux,VirtualBox 6.1.16,2020-11-26T06:12:00Z,2020-11-26T06:12:00Z,2020-11-26T06:12:00Z,Guru Meditation Error in windows host and Kali guest,Aqua
20064,Vista VM not functioning properly.,Windows,VirtualBox 6.1.16,2020-11-24T20:19:09Z,2020-11-24T20:19:09Z,2020-11-24T20:19:09Z,"I have my windows Vista VM set up following the instructions of someone who’s been successful with vms, however, I can’t get past the loading screen before the vm gets a BSOD. [[Image()]]",MetaKnightmare
20062,Guru Meditation Fault,Linux,VirtualBox 6.1.16,2020-11-24T13:18:39Z,2020-11-24T13:18:39Z,2020-11-24T13:18:39Z,"Received a Guru Meditation fault while running git status from the guest.
The Win 10 host was in the middle of its own startup activity and was quite busy. The Ubuntu 18.04 client had just started and was in the middle of an update when the fault occurred. Please see attachments.",TFR
20038,Linux guest GUI freeze or full VM hang after not being interracted with for some time,Linux,VirtualBox 6.1.16,2020-11-15T14:48:40Z,2020-11-24T11:17:52Z,2020-11-24T11:17:52Z,"
== Linux guest GUI freeze or full VM hang after not being interacted with for some time ==


'''Terms in use:'''

 - '''GUI Freeze''': The ''GUI inside the VM, XFCE, is not responsive''. ''The VM is still active, as can be seen by the activity indicators'' (disk, network, etc). A console can be brought up (ctl-alt-F2 for example), logged into, and all of my users processes killed with ""pkill -u myusername"". This causes the GUI to become responsive, giving me the fresh login screen. This is not optimal, however, at least it's a clean shutdown of programs. Alternately I can perform an ACPI shutdown and the system will shut down cleanly.
 
 - '''Full VM Hang''': The ''GUI inside the VM, XFCE, is not responsive. The VM is NOT active, as the activity indicators are inactive.'' A console can NOT be brought up (ctl-alt-F2 for example). Using the soft keyboard and trying the same has no effect. Sending ACPI shutdown signals has no effect. At the same time as this, ''sometimes the virtualbox GUI for managing the virtual machines hangs''. This can only be resolved by manually killing off the VM and anything virtualbox related, and rebooting the host.
 

'''VirtualBox information:'''

 - Version 6.1.16
 - Extension pack 6.1.16

'''Host information:'''

 - Windows 10 pro
 - Intel 4GHz corex CPU
 - 128GB RAM
 - Samsung SSD Disks
 - Nvidia GeForce RTX 2080 Ti using Nvidias drivers

'''Guest information:'''

 - Linux Mint 20
 - GUI: XFCE
 - Guest additions: 6.1.16
 - Virtual RAM: 9240 MB
 - Virtual processors: 6
 - Acceleration: default
 - Display: 128MB RAM, VMSVGA, Enable 3D Acceleration
 - Storage: SATA: Disk 1: Linux_Mint_19.vdi | Virtual size: 300GB | Actual size: 91GB
 - Storage: SATA: Disk 2: Linux_Mint_19_swap.vdi | Virtual size: 16GB | Actual size: 9GB
 
===

'''Issue Details:'''

Frequently after being away at least 10 or 15 minutes the guest will either experience a GUI freeze (see above for a description), or a full VM hang. The first situation can be recovered from, however in the second situation nothing can be done. For this reason I take frequent snapshots while the VM is powered on so that I can use them to restore from as setting everything back up again and again and again gets frustrating.

===

'''Solutions attempted:'''

Disable the screen saver / screen lock etc inside of the guest: The prior night I did this and returned in the morning to find that a full VM hang had taken place shortly after I had left to go to sleep. I know when it took place because of the time shown in the GUI (stuck).

Restore the latest snapshot, cleanly shut down, and power the VM on again: The issue still frequently occurs.

Disable 3D Acceleration: The issue still frequently occurs.


===

'''Logs:'''

''Note: For each of the logs, I prefix a string like ""round1"" and then refer to them that way. Please be sure to refer to them that way to me as well.''

The last log in round1 Vbox.log for this VM is: 
{{{
14:38:47.761976 GUI: UIMediumEnumerator: Medium-enumeration finished!
}}}


The full round1 Vbox.log will be attached. In addition I'll attach round1 VBox.log.1 , VBox.log.2 and VBox.log.3 .

round1 VBoxHardening.log doesn't really make sense to me so I'll just attach it.

Windows event log upon shutting down the host for round1, since it was both a full VM hang AND the virtualbox management interface became unresponsive:

{{{winlog.event_data.Caption:
    VirtualBox: VirtualBox.exe - Application Error
message:
    '''Application popup: VirtualBox: VirtualBox.exe - Application Error : The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
agent.hostname:
    MY-SYSTEM-NAME
agent.name:
    MY-SYSTEM-NAME
agent.id:
    130ce1c1-0e0a-419c-9b7f-f4bf70a6c377
agent.type:
    winlogbeat
agent.ephemeral_id:
    002ca6d2-1396-44b0-9a31-ec9b95be97bc
agent.version:
    7.9.0
winlog.record_id:
    2,049
winlog.computer_name:
    MY-SYSTEM-NAME
winlog.process.pid:
    16,852
winlog.process.thread.id:
    2,196
winlog.event_id:
    26
winlog.task:
winlog.provider_guid:
    {47bfa2b7-bd54-4fac-b70b-29021084ca8f}
winlog.channel:
    System
winlog.event_data.Message:
    '''The instruction at 0x0000000061F0162F referenced memory at 0x0000000000000008. The memory could not be read. Click on OK to terminate the program'''
winlog.api:
    wineventlog
winlog.provider_name:
    Application Popup
winlog.opcode:
    Info
winlog.user.identifier:
    S-1-5-18
winlog.user.domain:
    NT AUTHORITY
winlog.user.name:
    SYSTEM
winlog.user.type:
    User}}}

===

'''Follow up:'''

What more can I provide to assist?",Fieldy
20059,error in window vista,Windows,VirtualBox 6.1.16,2020-11-23T01:29:24Z,2020-11-23T01:29:24Z,2020-11-23T01:29:24Z,error in window vista,lev115
20058,Virtual Box encounters error while Ubuntu 20.04 VM is running,other,VirtualBox 6.1.16,2020-11-22T23:49:02Z,2020-11-22T23:49:02Z,2020-11-22T23:49:02Z,"I can't give an idea on how to reproduce it as it happenend as i was just browsing, was idle in a programm or was just starting it, tabbed out while waiting for it to be done and seeing the error message roght after boot was done.",zandatsu
20020,VirtualBox 6.1.16 Ubuntu 20.04 Guest freezes when windows 10 screensaver or screen lock,Linux,VirtualBox 6.1.16,2020-11-05T15:37:23Z,2020-11-22T10:54:59Z,2020-11-22T10:54:59Z,When I lock screen on Windows 10 host and then unlock and log back in my VirtualBox Ubuntu 20.04 Guest v6.1.16 freezes (I even have issues closing the main window of VirtualBox guest). Totally unresponsive. Only closing guest (after putting in some effort) main window with quite a few attempts including VirtualBox Manager on host freezing at the same time and restarting gets the VM back to life only to be unusable after host screen lock again...,SamH
20056,no mouse pointer or capture after login,Linux,VirtualBox 6.1.16,2020-11-21T15:17:33Z,2020-11-21T15:17:33Z,2020-11-21T15:17:33Z,"Until 11/17/20, my VM worked perfectly. Now, the mouse works UNTIL I login. But AFTER login, the capture is no longer working. There is NO mouse pointer on the virtual desktop, just the REAL mouse pointer, which moves anywhere, in or out of the Virtualbox.
The Vbox message (at the top of the window) saying the capture is effective shows and the capture icon indicates the mouse integration is on, but it is NOT being captured.
Using the CNTRL key to get the ""capture"" window and allowing capture, the mouse is NOT captured. 

I am using VBOX 6.1.16. My guest O/S is Ubuntu 20.04.1-AMD64. 
My HOST O/S is Windows 10 Pro 64-bit. I/O APIC was already on and I left it on.
I have tried:
*VMSVGA vs. VBOXSVGA vs VBOXVGA
*increase video memory to 128MB
*1 vs 2 CPUs
*USB tablet vs PS/2 Mouse
*paravirtualization: default vs minimal
*re-install Vbox extensions
* Enable PAE/NX
*3D accel on vs off
None of these make any difference. 
""File>send shutdown signal"" does NOT shut down the VM.

",Dennis Foreman
20051,Execution Cap fails in V 6.1.16,Windows,VirtualBox 6.1.16,2020-11-19T18:51:49Z,2020-11-19T18:51:49Z,2020-11-19T18:51:49Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
20050,Execution Cap fails in V 6.1.16,Windows,VirtualBox 6.1.16,2020-11-19T18:51:44Z,2020-11-19T18:51:44Z,2020-11-19T18:51:44Z,"We have a Win7 VBox client running Dbase IV  (yes, imagine)
Because indexing fails at nowadays CPU speeds, the VM has execution cap set to 10% 

This was working fine with V6.1.14 r140239. 

After upgrading to V6.1.16 indexing in Dbase started failing. 
Even bringing Execution Cap down to 1% made no difference. 
Actually it looked like changing the execution cap didn't have any effect at all. 

Reverting back to V6.1.14 brought things back to normal. 
",AlainDM
20047,VirtualBox not compatible with Windows Memory integrity feature,all,VirtualBox 6.1.16,2020-11-18T12:06:48Z,2020-11-18T12:06:48Z,2020-11-18T12:06:48Z,"https://docs.microsoft.com/windows/security/threat-protection/device-guard/memory-integrity

When Memory integrity is enabled all guest machines will become unusably slow.",fredd
20046,Host-Only Adapter not migrated during Windows 10 inplace upgrade,other,VirtualBox 6.1.16,2020-11-17T13:20:49Z,2020-11-17T13:20:49Z,2020-11-17T13:20:49Z,during an inplace upgrade of Windows 10 (doesn't matter which version) the VB Host-Only Adapter does not getting migrated (also it doesn't matter which VB version). Logfiles says driver is not supported and is therefore excluded from migration. (see screenshot attached) As consequence the adapter doesn't exist anymore after feature update and also cannot be created with the same IP settings since some keys remain in the registry (which can basically be deleted as a workaround).,csps
20044,IP Duplicate with MacOS 11.0.1 (Big Sur) and VBox 6.1.16,OSX Server,VirtualBox 6.1.16,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,"After installing MacOS X 11.0.1 and reinstalling VBox 6.1.16 to fix the kernel issue.

Now all Guest OS cannot connect to network (Bridged Adapter), since it detect a conflict IP address.

Looking in Windows Event Viewer and the duplication of 0.0.0.0 is identified with the MAC address of the Host MacOS server

I think we should have a new release to correct this issue in MacOSX Big Sur
Thank you",BDelorme
20042,VirtualBox.exe crash at start,Windows,VirtualBox 6.1.16,2020-11-16T06:30:02Z,2020-11-16T06:37:57Z,2020-11-16T06:37:57Z,"Sometimes (not always) VirtualBox GUI crashes at start. In such situation it is possible to successfully start GUI only at 2nd or 3rd attempt.

WinDbg bug analysis:

{{{
 SYMBOL_NAME:  Qt5GuiVBox!QRasterPaintEngine::transformChanged+1e
 MODULE_NAME: Qt5GuiVBox
 IMAGE_NAME:  Qt5GuiVBox.dll
 STACK_COMMAND:  ~0s ; .ecxr ; kb
 FAILURE_BUCKET_ID:  NULL_CLASS_PTR_WRITE_c0000005_Qt5GuiVBox.dll!QRasterPaintEngine::transformChanged
 OS_VERSION:  10.0.19041.1
 BUILDLAB_STR:  vb_release
 OSPLATFORM_TYPE:  x64
 OSNAME:  Windows 10
 IMAGE_VERSION:  5.6.2.0
 FAILURE_ID_HASH:  {c4d15f2c-b524-5704-6c40-ab527e5b6a72}
}}}
",ReapedBrain
20039,Snapshot remove from disk but still in logical path,Windows,VirtualBox 6.1.16,2020-11-15T14:50:31Z,2020-11-15T14:52:24Z,2020-11-15T14:52:24Z,"While the VM is running, I remove a snapshot. The removed snapshot is a parent snapshot of the running state. The snapshot is removed from disk but is still in the virtual media tree. 
In consequence the VM can't be started because the media (deleted) can't be read 

I tried to remove the media from the media manager, but the manager can't removed from the list because this media has 1 child.

How can I solve this problem and rescue the VM (the snapshot removed is a very old one and i need to restore on of his child).
 

 



 ",dingdingdong
20029,Solaris 10 Guest operating slowly on Windows 10 host running 6.1.16 and other recent releases,Solaris,VirtualBox 6.1.16,2020-11-09T17:00:04Z,2020-11-09T17:00:04Z,2020-11-09T17:00:04Z,"Running VBManagers earlier than 6.0, my Solaris 10 guest system operated with reasonable speed, but we had some problems with shared folders and creating/transferring data files to shared folders on the Windows 10 host system.
Now with 6.0.XX, the shared data folder problems seem to have been corrected, but the guest Solaris 10 system seems to run significantly slower than it did before.
Not sure if it is network issue - we have tried a variety of machine configuration options to optimize the guest system (more memory, more processors, anything else we could think of.)
Looking for ideas and suggestion, wondering if anyone else has seen this issue??",CJK
20019,Hosted VM is restarting unexpectedly which contains VirtualBox,Linux,VirtualBox 6.1.16,2020-11-05T08:16:49Z,2020-11-05T08:16:49Z,2020-11-05T08:16:49Z,"We've a Windows 10 Azure VM  which we have installed latest VirtualBox on it. After starting image on VB, everything is fine. But, when we try to login to guest vm via filezilla/putty from hosted vm, it's restarting hosted VM suddenly. 

Please check log that belongs to guest vm that we having problem.",alpercelerce
20018,BSOD when plugging (any) USB device to Windows 10 computer even when no VM is on,all,VirtualBox 6.1.16,2020-11-05T07:36:22Z,2020-11-05T07:36:22Z,2020-11-05T07:36:22Z,"For my windows laptop this issue occurs for at least couple of newest builds of VirtualBox 6.1.x versions. The issue haven't occurred on version 6.0.24 for me.

Every time I connect any USB device to my laptop AFTER starting VBox (but not necessarily any VMs) BSOD occurs.

VBoxUSBMon.sys seems to cause PNP_DETECTED_FATAL_ERROR.

Some of my colleagues are suffering from same issue.


Windows 10 Enterprise, 2004, 19041.572",SamuelH
20015,VBox commands via MS openssh on a windows 10 host system fail CO_E_RUNAS_LOGON_FAILURE,all,VirtualBox 6.1.16,2020-11-03T13:27:29Z,2020-11-03T13:27:29Z,2020-11-03T13:27:29Z,"Trying to run ""VBoxManage list vms"" on a Windows 10 host, when connected to the host via Microsoft OpenSSH server fails:

VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Completely failed to instantiate CLSID_VirtualBox: CO_E_RUNAS_LOGON_FAILURE
VBoxManage.exe: error: Details: code CO_E_RUNAS_LOGON_FAILURE (0x8000401a), component 
VirtualBoxClientWrap, interface IVirtualBoxClient

This works as soon as any user (it does not need to be the one who tries to run the command) connects via rdp to the system. If a user B is connected to the system and a VBox is started from user A, the VBoxHeadless process is running as user B...

Is it possible to avoid this behaviour and run VBoxManage commands and even start headless VMs connected via openssh?
What is the reason for this behaviour?


",mih
20013,VirtualBox locks up when host resumes from sleep,Windows,VirtualBox 6.1.16,2020-11-02T11:36:16Z,2020-11-02T11:36:16Z,2020-11-02T11:36:16Z,"I have had an issue with VirtualBox locking up on Host resume from sleep for years, but it seemed to be a bit random. However I did notice that in v6.1.14 it hardly occurred any more, perhaps once a fortnight.

Once I upgraded to v6.1.16, VirtualBox was locking up almost every time the Host resumed from sleep.

After a few days of these lockups I decided to revert to v6.1.14 (29th October) and since then I've not had a single lock up and I've probably resumed the Host from sleep a dozen times.

I've attached the logs from v6.1.16 but from my quick look, I don't think anything gets logged after the sleep as it locks up before that can happen.

The Host is Windows 10 Home 1909 Build 18363.1139
The Guest is Windows 10 Pro 1909 Build 18363.1139",Iain Waddell
20012,Externally zero null free space before compacting,all,VirtualBox 6.1.16,2020-10-31T05:22:37Z,2020-10-31T05:22:37Z,2020-10-31T05:22:37Z,Any way to apply sdelete function externally from GUI before compacting vdi?,necros
20011,Use Host I/O Cache as default option,all,VirtualBox 6.1.16,2020-10-31T05:15:53Z,2020-10-31T05:15:53Z,2020-10-31T05:15:53Z,subj,necros
20010,Update to Qt 5.15.1,all,VirtualBox 6.1.16,2020-10-31T05:07:43Z,2020-10-31T05:07:43Z,2020-10-31T05:07:43Z,subj,necros
20007,virtual screen can not ne resized over rdp,Windows,VirtualBox 6.1.16,2020-10-29T09:47:01Z,2020-10-29T09:47:01Z,2020-10-29T09:47:01Z,"I have a vm that i use on my home computer and a copy in the company over rdp.

At home it is no problem to change the virtual Monitor to my 1080p screen (windows 10 20h2) Nvidia 2060.
But when i remotely access the same(copy) vm i can not resize the screen. the only option i can access and change, is the screen is the scaling option (100 % 125 % and so on).

The remote Monitor has a screen size (1600x900) with an Intel(R) UHD Graphics 630

It is more an annoyance, to scroll the hole time, but as i need the hle screen, i have to do that fairly often.",nbk
20002,Crash when restoring machine state and launching or selecting program from favorites,Linux,VirtualBox 6.1.16,2020-10-27T14:38:16Z,2020-10-27T14:38:16Z,2020-10-27T14:38:16Z,"Windows 10 host and Ubuntu Desktop guest.

Whenever I save machine state with something running, I get a crash when I restore (the crash comes when I select a favorite, whether it was running or not). I have seen this in various scenarios (basically any other than shutting down with nothing running at all). I have attached logs for the following scenario.

1. Launch Ubuntu VM.
2. Start LibreOffice Writer (really can be anything, Visual Studio Code will do the same thing).
3. Click the 'X' in the far upper right to close VB. Select 'Save the machine state'.
4. In VB with the Ubuntu machine selected, click 'Start'.
5. The machine is restored, with the LibreOffice Writer document open.
6. Click on Chrome in the Favorites panel, trying to launch it (again, I'm not sure it matters what program you try to launch here).
7. The crash window immediately comes up (the one with the OK and IGNORE buttons telling me I have to shut down and where the logs are, etc.)

This behavior is consistent. It basically makes the program unusable because I have to shut down the machine whenever I close VB.
",mark6139
19999,no me deja aceptar las configuraciones que deseo aplicar en mi virtual box,Linux,VirtualBox 6.1.16,2020-10-26T04:21:42Z,2020-10-26T04:21:42Z,2020-10-26T04:21:42Z,,roldan0314
19996,Black Screen of Death,Linux,VirtualBox 6.1.16,2020-10-24T18:59:43Z,2020-10-24T18:59:43Z,2020-10-24T18:59:43Z,"I'm trying to get virtualbox running on a windows 10 pro (2004) machine and create a linuxmint vm.  When I start the VM I get the linux screen that says ""start linux"" and then after 10 seconds the screen goes black.  I have disabled hyper-v, i have unchecked 3d acceleration.  I was able to get VMWARE to work but not having any luck with virtualbox.  I've attached the log file",rsail
19994,Network Status Bar Icon always displays connect,Windows,VirtualBox 6.1.16,2020-10-23T17:00:16Z,2020-10-23T17:00:16Z,2020-10-23T17:00:16Z,Network Status Bar Icon always displays connect regardless of connected or disconnected.,irondude
19991,It is not possible to drag and drop files.,Windows,VirtualBox 6.1.16,2020-10-22T13:25:10Z,2020-10-22T13:25:10Z,2020-10-22T13:25:10Z,"Attached to the log file, Guets is windows 1064Bits and Host also windows 10 64Bits.

This feature is very important and does not work it would be interesting to implement a Ctrl + C and Ctrl + V feature I think it would be more and would not give so much problems because with each version that I update in the Virtual box to stop drag and drop even then marked as bidirectional",luciano_f
21039,Guest Windows firewall disable does disable internet on Windows Host,Windows,VirtualBox 6.1.16,2022-07-27T17:32:47Z,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"* Host/Guest: Windows 7 x64

I am trying to use shared MAC address on both Host and Guest, because ISP does block internet access by the MAC.

In that case if set Bridged network mode and try to disable the Windows 7 x64 firewall on the Guest, then the internet would be disabled on the Windows 7 x64 Host.",andry81
20202,"Win10 6.1.18 host hanging during guest startup / pausing / shutdown, excessive disk read seen",all,VirtualBox 6.1.18,2021-02-18T13:56:03Z,2022-06-16T01:16:21Z,2022-06-16T01:16:21Z,"When I upgrade from 6.1.16 on win10 to 6.1.18, 6.1.19-142777, or 6.1.97-142300 then my Linux and Win10 guests stop responding for a while during startup, shutdown and every time the VM is Paused.

During the entirity of the time the VM is not responding, Task Manager on the host shows Disk reads for the VirtualBox process jump to 600MBytes/sec. Writes stay at close to zero.   The duration of the non-responsiveness when Pausing both tested VMs corresponds with the size of the VM.  

IE every time I Pause the Ubuntu Linux guest, it take 15 seconds of reading @ 600MB/sec to Puase, while the VM size is ~=9GB.   Likewise it takes ~50 seconds to Pause my ~30GB Win10 VM.

From observing the Disk status on Task Manager, whatever triggers the hang/reads seems to happen 2-3 times during VM start up and 1-2 times during shutdown.

vbox.log on 6.1.18 (see attached) shows entries like:

- AsyncCompletion: Task 0x0000000762df00 completed after 16 seconds

- VD#0: Aborted read (0 bytes left) returned rc=VERR_PDM_MEDIAEX_IOREQ_CANCELED

However, during pausing of the VM no errors are seen in the log file - just that PDMR3Suspend took 15 seconds instead of 50 milliseconds.

The Ubuntu guest sometimes has a console message about disk that I couldn't capture.  One boot it came up with / readonly due to needing fs check.

I don't see the same issue occur using 6.1.18 on Win8.1.  It pauses (in well under 1 second), boots and shuts down swiftly as expected with minimum disk reads.
",Grrrrrrr
20237,BridgedInterface needs trailing blank,Linux,VirtualBox 6.1.18,2021-03-06T18:41:27Z,2021-12-22T03:54:56Z,2021-12-22T03:54:56Z,"My network interface card is a ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", host is Windows 10 20H2 build 19042.844. 
When selecting the NIC as bridged interface in the network settings, it is stored to the .vbox file as ""NVIDIA nForce 10/100/1000 Mbps Ethernet"", however when starting the related guest I get an error message that the virtual machine cannot be started as the network interface is not existing.
I can resolve this by adding a trailing blank to the BridgedInterface in the .vbox file as:
<BridgedInterface name=""NVIDIA nForce 10/100/1000 Mbps Ethernet ""/>
before starting VirtualBox.
But whenever I change some settings of the guest, the trailing blank is removed, so I must do this again and again. ",Phantom2398
20293,"Message Linux Mint 20.1 Cinnamon - ""Check your Video Drivers""",Linux,VirtualBox 6.1.18,2021-04-08T13:40:18Z,2021-10-25T14:58:25Z,2021-10-25T14:58:25Z,"Hi
I have used Virtualbox for quite sometime now but consider myself a newbie. I recently got a new Laptop which has NVIDIA GeForce GTX 1660 Ti Graphics Card. I have tried and tried to load Linux Mint Cinnamon 20.1 into Virtualbox but no matter what I do I continually receive ""Check Your Video Drivers - Your system is currently running without Video acceleration"".  
I have followed all the suggestions on the Forums regarding this issue and as you can see followed the suggestion to load a Beta version as it may solve the problem but all to no avail.  
I have loaded Linux Mint MATE 20.1 without any problems.  But more importantly I have installed VMware Workstation and installed Linux Mint 20.1 Cinnamon with no problems what so ever.
Also If I install Linux Mint Cinnamon 20.1 in a separate partition and dual boot it works OK.
So is there a problem with Virtuabox.
Please advise
Kind Regards 
Arthur Howard
",arfa
20167,Mouse pointer in MS Office is not working correctly.,Windows,VirtualBox 6.1.18,2021-02-01T03:36:59Z,2021-09-18T02:53:27Z,2021-09-18T02:53:27Z,"Microsoft uses special mouse pointers in MS Office (Excel, Word, Access). These mouse pointers don't work since VirtualBox 6.1.x. It has worked in VB 5.2 and maybe in 6.0 (not sure).
I assume it is a problem of the guest additions for Windows.
I am using Windows 10 on the host and Windows XP with Office 2003 in the VB guest with a scale factor of 1.2.",PeterE
20290,"VB Manager GUI ""move"" machine command",all,VirtualBox 6.1.18,2021-04-08T05:50:29Z,2021-09-17T08:27:38Z,2021-09-17T08:27:38Z,"use VB on my laptop and have numerous machines for projects with engneering software.
I want to keep only the current project VM on my laptop SSD (for speed and disc space reasons) and keep the other ones accessible on an external USB drive .
So I attach 5TB external HD to the laptop and create a ""machines"" folder.

I use the ""move"" command in the GUI (right-click on the VM) and can select slect basically any drive and folder and pont it to my external HD machine folder.

However the results are mixed and the feature is not working.

A folder for the machine is created but only the VM vbox file and the log folder is moved to the destination. The VDI and snapshot folder remain on Original location :cry:

If I move the VM on the same internal HD drive letter to another location it seems to work better and shifts also the VDI and snapshots.

Background why I need the move feature:
My problem is that I want to shift a VM (with it's VDI) which all reside in a folder (.vbox, .VDI, the Snapshot and log subfolders) and move it to another location either on my laptop or to an external HD over the network to a library (NAS). Reason behind it is that I work with many VM and I can't have all of them in my laptops SSD at the same time. I wanted to use the ""move"" feature from the VB GUI to move a complete VM (including its VDI, snapshots) to an external hard drive and keep those VM that I don't need immediately or only for a quick test on another drive (HDD) and easily move them between my internal SSD and an external drive. The GUI behaves inconsistent when it comes to applying the command on the same (internal) drive or on an external USB drive or a network drive. It doesn't make sense to use the ""move"" command when it only moves the VM definition and leaves the VDI in the old location or even worse when it only partially moves the files leaving some in the old location and some in then new location.
What I figured out is that apparently due to the way the move is implemented in the GUI it works (almost(!!) all the time) within the local drive because only the path informations needs to be updatted on the hard drive file system and files are not physically moved (copied and then deleted from old location). By selecting an external drive for the move command it works ""partially"" but mostly some files are not properly moved.
",Andreas S
20531,The CentOs screen is getting stuck after starting it,other,VirtualBox 6.1.18,2021-09-01T06:36:30Z,2021-09-07T09:57:41Z,2021-09-07T09:57:41Z,"After starting the CentOS in the virtual box, it buffers and gets stuck at this screen for a long time.
Windows was restarted, shutdown and started again and the same for the virtual box but the issue remains. I have a lot of data which i need to retain after this issue is fixed.
",ishwarya
20393,Linux Guest [vmwgfx] *ERROR* SVGA device lockup,Linux,VirtualBox 6.1.18,2021-06-10T19:29:19Z,2021-07-12T16:35:51Z,2021-07-12T16:35:51Z,"Hi,

I'm running a Linux guest on a Windows host and every so often the display will lock up. It's happened maybe 3 times in the last month and I haven't been able to correlate it with anything specific.

By lock up, I mean that it appears that the display stops updating. Input (at least mouse events) appear to work, but when it starts to lock-up, the display does not update in response to any input events until a few seconds go by. Pretty quickly, this behavior degrades to the point where it appears completely frozen and no more updates occur.

I can ssh in from my host and interact, so it seems it is just a display driver issue. dmesg shows the following:

[70545.554435] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70548.553727] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[70558.765785] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out
[73420.314255] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73423.314445] [drm:vmw_fallback_wait [vmwgfx]] *ERROR* SVGA device lockup.
[73433.384206] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] flip_done timed out

Not sure what else to check, but can do whatever is needed to debug next time it happens. Just let me know.

I also see these messages appearing occasionally before hand, but they look to occur fairly regularly in the log without any other symptoms, so I don't know if they are related or not.

[54955.536381] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

I can provide more detailed hardware info (it's a Dell XPS 9500 using an i7-10857H w/ 32GB), os specifics (Win10, Ubuntu 20.04), and system config (I run 2 external displays on which I use my linux guest) or whatever else is needed.

I will attach my VBOX.log

Thanks for any help,
Brian

",brian-vbox
20273,Troubles with audio in VBox 6.1.19-143492,Windows,VirtualBox 6.1.18,2021-03-25T02:29:50Z,2021-06-26T11:36:59Z,2021-06-26T11:36:59Z,"After testing the newly appeared version I immediately found a bug. If one stops audio playback, the last half second will still play over and over again, endlessly. This reminds me about an old good tickets with host audio output device change during the playback, like #17225 or [https://www.virtualbox.org/ticket/18594#comment:31 #18594#comment:31]. And some problems after audio backend rewrite back in 5.2. Those issues first appear in the new version and couldn't be found in 6.1.19-143292.

I put my logs and audio dump here. Both my host and my guest are Windows 10 20H2 with patches from March.",boxer01
20429,System crash on Windows 10 host when using vbox network adapter together with Windows 10 networking bridging feature,all,VirtualBox 6.1.18,2021-06-25T04:36:09Z,2021-06-25T04:36:09Z,2021-06-25T04:36:09Z,"Steps to reproduce the issue:

1) Install vbox on a Windows 10 device
2) Make sure to also enable the vbox network adapter
3) Set physical network adapter within the Windows 10 network settings to bridge mode (Control Panel\Network and Internet\Network Connections -> right click network connection -> bridge connection)
4) Leave device running as normal. In my case, the crashes seemed to happen fairly consistently after roughly 14 hours of system uptime, give or take a few hours.

Unfortunately my system settings were set to full crash dumps and not minidumps, so the full dump is likely too large to upload here. However, I will paste the information the Windows debugger was able to extract from my crash dump here:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8027f4580c3, The address that the exception occurred at
Arg3: fffffe8c1f2a2ab8, Exception Record Address
Arg4: ffffa400c67f5920, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-INRFD0B

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027f4580c3

BUGCHECK_P3: fffffe8c1f2a2ab8

BUGCHECK_P4: ffffa400c67f5920

EXCEPTION_RECORD:  fffffe8c1f2a2ab8 -- (.exr 0xfffffe8c1f2a2ab8)
ExceptionAddress: fffff8027f4580c3 (bridge+0x00000000000080c3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffa400c67f5920 -- (.cxr 0xffffa400c67f5920)
rax=0000000000000000 rbx=0000000000000000 rcx=b2a29e05584ac880
rdx=0000000000000000 rsi=ffffb8880f8ee2c0 rdi=ffffb888098a48e0
rip=fffff8027f4580c3 rsp=fffffe8c1f2a2cf0 rbp=fffffe8c1f2a2e00
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000002
r11=fffffe8c1f2a2b90 r12=0000000000000000 r13=0000000000000000
r14=ffffb8880f8ee4f0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
bridge+0x80c3:
fffff802`7f4580c3 488b4918        mov     rcx,qword ptr [rcx+18h] ds:002b:b2a29e05`584ac898=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS:  ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

BAD_STACK_POINTER:  ffffa400c67f50e8

STACK_TEXT:  
fffffe8c`1f2a2cf0 fffff802`7f458786 : 00000094`00000000 00000000`00000003 fffffe8c`1f2a2e80 00000000`00000003 : bridge+0x80c3
fffffe8c`1f2a2d80 fffff802`674f53b5 : ffffb888`08528040 ffffb888`08528040 fffff802`7f458550 00000000`00000003 : bridge+0x8786
fffffe8c`1f2a3c10 fffff802`675fe278 : ffffa400`c67b3180 ffffb888`08528040 fffff802`674f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe8c`1f2a3c60 00000000`00000000 : fffffe8c`1f2a4000 fffffe8c`1f29e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bridge+80c3

MODULE_NAME: bridge

IMAGE_NAME:  bridge.sys

STACK_COMMAND:  .cxr 0xffffa400c67f5920 ; kb

BUCKET_ID_FUNC_OFFSET:  80c3

FAILURE_BUCKET_ID:  AV_STACKPTR_ERROR_bridge!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}

Followup:     MachineOwner
---------
",Andazeus
20329,Connect bluetooth headset causes freeze,Linux,VirtualBox 6.1.18,2021-04-29T18:06:10Z,2021-04-29T18:06:10Z,2021-04-29T18:06:10Z,"Frequently, when I turn on or turn off my bluetooth headset, the Guest OS will freeze. It will no longer respond to any mouse clicks of keyboard presses.

Generally I am in full screen mode. I was recently in windowed mode when this happened and attempting to open the File menu was also unresponsive. Windows then marked the window as Not Responding.


Virtualbox Version 6.1.18 r142142 (Qt5.6.2)
Host: Windows 10 (10.0.18363 Build 18363)
Guest: Ubuntu 20.04


[This thread](https://forums.virtualbox.org/viewtopic.php?f=6&t=94233) contains other users reporting the same issue with slight different pairings of Virtualbox running on Windows10 host with a Linux Guest OS.",plannigan
20313,"CentOS7 poweroff BUG, Couldn't be written",Linux,VirtualBox 6.1.18,2021-04-22T07:17:06Z,2021-04-28T02:15:43Z,2021-04-28T02:15:43Z,"* Windows:  Win10 family Chinese version 20H2 19042.928 Mem 16GB
* CentOS: CentOS Linux release 7.9.2009 (Core) 
* Kernel: 3.10.0-1160.el7.x86_64
* Configuration
  * CPU：1cores
  * Mem: 1GB
  * Network Cards: 1 NAT
* Reproduce:

  Actually, every centos7 VM has the same problem, and it seems to have nothing to do with the virtual machine configuration. This problem occurs regardless of poweroff, shutdown, init 0 or ACPI shutdown commands. In addition, win10 1909 also has this problem.
  I wanna know is that a BUG, thank you!

* Error Message


{{{
VirtualBoxVM.exe - Application Error: 
The instruction at 0x00007FFED15D9B2C referenced memory at 0x00007FFED15D9B2C. The memory could not be written. 
Click on OK to terminate the program.
}}}
",Justin-Young
20226,Windows VBox dev. build 6.1.19 142917 host won't start VMs but 6.1.19 142777 does,Windows,VirtualBox 6.1.18,2021-02-25T09:39:35Z,2021-04-26T11:55:39Z,2021-04-26T11:55:39Z,"Bug report:

Am running Windows 8.1 Pro x64 fully patched (build 9600.19941).
Symantec Endpoint Protection: Version: 14.0.3929.1200 (14.0.3929.1200.105 to be exact)

With developer build Virtual Box 6.1.19 142917, I receive the following (or similar) when trying to start any VM 
(XP 32 bit, but also same for a 64 bit Windows 10 guest and 32 bit Windows 7 guests)
The previous developer build: 6.1.19 142777 was fine.
The only change is the build of Virtual Box, and indeed reverting back from 142917 to 142777 fixes the problem.

Error messages:

Failed to open a session for the virtual machine XP.

The virtual machine 'XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\VBoxMachines\XP\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Note: The following bug report against 142917 also looks relevant:
https://forums.virtualbox.org/viewtopic.php?f=38&t=101896",MikeDiack
20314,0x00007FF874BF9B2C address,other,VirtualBox 6.1.18,2021-04-22T12:49:41Z,2021-04-22T12:49:41Z,2021-04-22T12:49:41Z,"After closing the VM, the screen1.png popup. Nothing else. 
screen1.png : 
""0x00007FF874BF9B2C address refer to 0x00007FF874BF9B2C address direction. This can't be written. 
Press Ok... Ok""",Aec_A
20306,VirtualBox crashes on IO in FreeBSD 13,BSD,VirtualBox 6.1.18,2021-04-20T09:42:24Z,2021-04-20T10:01:34Z,2021-04-20T10:01:34Z,"I started up a FreeBSD 13 VM that I've had for a little bit on VB 6.1.16, started installing some packages, and suddenly the VM crashed and displayed ""Aborted"" on the management interface.

I upgraded VB to 6.1.18, booted the VM, started installing the same packages again, and lo and behold, it died again.

I've attached the log from the VM dying on 6.1.18.",rincebrain
20300,VM hung at installation,Windows,VirtualBox 6.1.18,2021-04-11T22:43:10Z,2021-04-11T22:43:10Z,2021-04-11T22:43:10Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20299,VM hung at installation,Windows,VirtualBox 6.1.18,2021-04-11T22:42:31Z,2021-04-11T22:42:31Z,2021-04-11T22:42:31Z,"starting udev wait for complete device initialization 
starting Device-Mapper Multipath Device controller",Beyond
20298,VBox Additions on Linux = Blackscreen after Boot,Linux,VirtualBox 6.1.18,2021-04-10T20:06:08Z,2021-04-10T20:06:08Z,2021-04-10T20:06:08Z,"I have a problem with VirtualBox on Windows 10 Professional 20H2. I want to run XFCE, KDE and other desktops on VirtualBox, but when I install the additions and I reboot, i just get a blackscreen. I can't provide logs from Linux (because the blackscreen happens), and in the VirtualBox logs is nothing special.",JeremyStarTM
20297,VM crashes after starting recording,Linux,VirtualBox 6.1.18,2021-04-10T09:31:42Z,2021-04-10T09:31:42Z,2021-04-10T09:31:42Z,"VM immediately crashes when starting recording:

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFE918E77E3 referenced memory at 0xFFFFFFFFFFFFFFFF. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK   
---------------------------


Host: Windows 10 x64
Guest: Arch Linux x64 (UEFI boot)

To reproduce:
1. Boot from Arch Linux iso
2. Start recording (View\Recording)

PS. Starting recording via command line works just fine.
",1ns
20279,Long-timeout TCP Sessions,Linux,VirtualBox 6.1.18,2021-03-28T20:53:11Z,2021-03-28T20:53:11Z,2021-03-28T20:53:11Z,"I have a case with long time-out TCP sessions that come from VirtualBox NAT network mode. When I created half-open TCP sessions from the VM to an external TCP Host (by sending SYN packets but not reply the SYN/ACK with ACK packets). After 10 seconds, the external TCP Host proceeded to close the connections by sending FIN packets. This put the port VirtualBox used for those connections to CLOSE_WAIT state. As I observed, the current VirtualBox's CLOSE_WAIT timeout is about 10 minutes.

I have a theory that, if I can generate enough number (maybe 40,000?) of CLOSE_WAIT state TCP sessions, I can occupy all of the port VirtualBox can use for transmitting, which make the internal VM can not create new connection with external hosts, for 10 minutes. 

I suggest that the CLOSE_WAIT timeout should be lowered to 2 minutes to counter the possible problem.",nds21
20276,Virtualbox6.1.18 don't work with Windows 10 (Failed to load R0 module),Linux,VirtualBox 6.1.18,2021-03-26T15:04:45Z,2021-03-26T15:14:09Z,2021-03-26T15:14:09Z,"Hello,
When I try to open my Ubunto VM the Virtual machine pop up the following error:

Failed to open a session for the virtual machine UbuntuES.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: SUP_IOCTL_LDR_OPEN failed (VERR_LDR_GENERAL_FAILURE).

Failed to load VMMR0.r0 (VERR_LDR_GENERAL_FAILURE).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}


I have already tried to reinstall the VM software with no Success;
I've tried to Disable Windows Hyper-V;

Please advise.",Fpedrosa
20274,VM's do not funtion on Win10,Linux,VirtualBox 6.1.18,2021-03-26T01:25:30Z,2021-03-26T01:25:30Z,2021-03-26T01:25:30Z,"I am running windows 10 pro on my pc. Two days ago I turned on a VM which I use regularly, but it gets stuck trying to ""Start VM."" The VM never starts, VirtualBox says that it is at 20%, so I kill it in task manager. However, I am not able to kill VBoxSVC.exe. I turned on Hyper-V and cloned that VM to it to make sure that it is not corrupt (I disabled Hyper-V after verifying). 

I downloaded two other VM's to see if they would function. These new VM's can start, but when I try to shut them down they freeze. Oddly enough, this event prevents me from being able to turn off my pc, so I have to unplug it from the wall. 

The logs I am including in this ticket are for the first VM I referenced. I have Virtualbox 6.1.18 installed on my pc (normally). During my troubleshooting I also installed the most recent 5.x.x version to see if it would have any effect (same symptoms).",GeneralKenobi
20270,Arch linux guest crash after windows 10 host resume from sleep,Linux,VirtualBox 6.1.18,2021-03-23T03:52:35Z,2021-03-25T09:27:40Z,2021-03-25T09:27:40Z,"I wrote a topic about this on the virtualbox forum[https://forums.virtualbox.org/viewtopic.php?f=6&t=102250&sid=f398ac48ffa5927918c82d13ef2c7ce8].

Here are how I reproduce the problem:

----
1. start Arch linux guest
2. Windows 10 host sleep
3. resume Windows 10 host
4. Arch linux guest is PAUSED, try to resume it
5. whole virtualbox interface freeze, crash (log ""carsh"")

----
However, if I pause and resume the guest manually once before the host go to sleep, the probelem is gone.

----
1. start Arch linux guest
2. pause guest and resume it immediately
3. Windows 10 host sleep
4. resume Windows 10 host
5. arch linux guest is RUNNING, everything works fine (log ""workfine"")

----

Additionally, I also have a windows 10 guest and a ubuntu 16.04 guest, neither of them have this problem.",lindeshun
20271,nested virtualisation with kvm cpu hits 100% then L2 guest crashes,Linux,VirtualBox 6.1.18,2021-03-23T13:57:56Z,2021-03-24T21:41:10Z,2021-03-24T21:41:10Z,"Hi,

It maybe that this is known not to work but in the 6.1 docs it mentions kvm as an L2 hypervisor so I thought I'd give it ago.

I have Intel I7 9th gen chip with 6 cores running windows 10 Enterprise build 18363 as my L0

I tried this originally on vbox 6.1.16 but upgraded to 6.1.18 after reading https://www.virtualbox.org/ticket/19315. This caused https://www.virtualbox.org/ticket/20199 so I'm currently running the 6.1.19 test build which fixes the crash but didnt resolve my problem first observed in 6.1.16 so I'm guessing its something different. 

Redhat mention they support some combinations in tech preview when the L0 is RHEL8.2. They say others eg: VMware, Xen, Amazon AWS, Nutanix AHV, Oracle VM are not. 

My use case for this is purely local lab environments mainly in vagrant so I'm more interested in if it work or not then support.

I'm trying to use packer inside a centos7 L1 VM to build with the qemu builder with kvm accelerator.

Packer is able to launch the VM and it starts the install. Its pretty slow but eventually fails installing this glibc.i686 package

{{{
Installing glibc.i686 (684/694)
[ 1354.721435] double fault: 0000 [#1] SMP
[ 1354.722093] Modules linked in: xfs fcoe libfcoe libfc scsi_transport_fc scsi_tgt zram sg pcspkr joydev i2c_piix4 parport_pc parport ext4 mbcache jbd2 loop nls_utf8 isofs sr_mod cdrom 8021q garp mrp stp llc virtio_net virtio_blk net_failover failover drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ata_generic pata_acpi drm ata_piix libata serio_raw virtio_pci virtio_ring virtio drm_panel_orientation_quirks sunrpc xts lrw gf128mul dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq libcrc32c async_xor xor async_tx raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs cramfs edd
[ 1354.722093] CPU: 0 PID: 17227 Comm: glibc_post_upgr Not tainted 3.10.0-1160.el7.x86_64 #1
[ 1354.722093] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.5.1 01/01/2011
[ 1354.722093] task: ffff9fa564fe8000 ti: ffff9fa562bdc000 task.ti: ffff9fa562bdc000
[ 1354.722093] RIP: 0010:[<00000000b5f97d80>]  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093] RSP: 0018:0000000000000000  EFLAGS: 00010082
[ 1354.722093] RAX: 000000000000007a RBX: 00000000ffcc49ca RCX: 0000000000000000
[ 1354.722093] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
[ 1354.722093] RBP: 00000000ffcc495c R08: 0000000000000000 R09: 0000000000000000
[ 1354.722093] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1354.722093] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 1354.722093] FS:  0000000000000000(0000) GS:ffff9fa5bcc00000(0000) knlGS:0000000000000000
[ 1354.722093] CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
[ 1354.722093] CR2: 00000000b5f97d80 CR3: 0000000022a7c000 CR4: 00000000000006f0
[ 1354.722093] Call Trace:
[ 1354.722093] Code:  Bad RIP value.
[ 1354.722093] RIP  [<00000000b5f97d80>] 0xb5f97d80
[ 1354.722093]  RSP <0000000000000000>
[ 1354.722093] ---[ end trace 6fd2b3e5f947f091 ]---
[ 1354.722093] Kernel panic - not syncing: Fatal exception
[ 1354.722093] Kernel Offset: 0x34800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
}}}

I see some people are able to get kvm to run fine in vbox. But I'm wondering if they have AMD chips on the L0 or some other fundamental difference.

Any suggestions on how to try to debug this further?


",aw125
20272,Windows 10 guest freezes randomly on Windows 10 host when accessing files on shared folders,Windows,VirtualBox 6.1.18,2021-03-24T12:53:05Z,2021-03-24T12:53:05Z,2021-03-24T12:53:05Z,"Weeks ago, after updating from 6.1.12 to 6.1.16 my VM started freezing when I accessed files from a shared host folder. It mostly happens when I trie to browse the shared folder from an application's open file dialog. Reverting back to 6.1.12 did not resolve the issue. This started to happened more frequently, so that I finally could no longer work with that VM and had to recover an older state from a backup. 
Now that some weeks have passed, the issues start again. I upgraded to 6.1.18 without success. Note that I already had issues with shared folders (e.g. can't start executables because they don't exist, copying several files will only copy some files etc) 
But now the issue completly freezes the client each time with increasing frequency.
",bartislartfass
20162,Crash when VM reboots due to null memory reference,all,VirtualBox 6.1.18,2021-01-29T19:03:17Z,2021-03-20T07:19:24Z,2021-03-20T07:19:24Z,"Hello there,

I've noticed lately that when VirtualBox reboots, either via VirtualBox (HOST+R or similar) or instructed by the guest, this fails entirely and crashes with a null memory reference.

* It impacts any guest VM.
* It doesn't impact ACPI shutdown or hard power off, these seem to close gracefully.
* It doesn't particularly matter what stage the guest is at, it'll occur seconds after powering on, or hours after running.
* This impacts running a VM normally and headlessly.

Specifically the error message is ""The instruction at 0x00007ffab544f3bc referenced memory at 0x0000000000000000. The memory could not be read.""

At this point I can power off the virtual machine and start it up again normally, but I worry if any pending storage writes will have been lost causing corruption. (I did very recently lose a guest due to storage corruption, unsure if this caused it.)

Unfortunately attaching a debugger never seems to succeed, so I'll attach some memory dumps of ""VirtualBoxVM.exe"" and ""VBoxHeadless.exe"" when the fatal error message was present.

I did attempt removing and reinstalling VirtualBox, including a whole reboot between, the only change was the memory address of the instruction. I can replicate this incredibly reliably though if further memory dumps are helpful.",Adam Reece
20238,VM Crashes at kernel loading on DELL Inspiron 7501,Linux,VirtualBox 6.1.18,2021-03-07T11:51:02Z,2021-03-18T12:46:30Z,2021-03-18T12:46:30Z,"Hi,
I tried to run Debian / Ubuntu 20.04 on the latest stable VM Virtualbox build (Version 6.1.18 r142142) on my brand new Dell Inspiron 7501 but after the grub menu, the VM systematically crashes (black screen with blinking white hyphen). Ubuntu is not really verbose, but the last thing that Debian echoes is ""Loading ram disk..."". It's probably not the reason why it crashes but it could maybe help to delimit the source of the problem.

I tried to generate a minidump but as VirtualBox doesn't crash it is useless...

I tried enabling/disabling Hyper-V but nothing changes

I forgot to say that those two VM used to work on my old HP Omen 15 of course.

Feel free to ask me tot test things out, it would be a pleasure to find why it crashes!",Striker209
20260,My virtual machines are running slower,Windows,VirtualBox 6.1.18,2021-03-17T14:22:53Z,2021-03-17T14:22:53Z,2021-03-17T14:22:53Z,"After a quick update to my computer, my virtual machines started to run slower, not sure why.",Guywithproblem
20249,When updated virtualbox. EVERY VIRTUAL MACHINE ARE NOT STARTING ANYMORE.,Windows,VirtualBox 6.1.18,2021-03-12T01:32:15Z,2021-03-12T22:21:14Z,2021-03-12T22:21:14Z,"i Updated virtualbox only too see if they fixed a bug. then.
No virtual machine wants to start!
IDK why but i am MAD that is happening
The thing is that I cant activate hypervisor partition. What do i do??
Here is the error that appears when i open a virtual machine

Fallo al abrir una sesión para la máquina virtual Windows 7 Ultimate.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Código resultado: E_FAIL (0x80004005)
Componente: ConsoleWrap
Interfaz: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Julian Gamer
20241,Windows 10 Vm always crashes on startup,Windows,VirtualBox 6.1.18,2021-03-09T12:30:21Z,2021-03-10T00:03:18Z,2021-03-10T00:03:18Z,"I downloaded the 20H2 windows 10 iso from Microsoft, and created a 64-bit Vm with that iso. However, every time the Vm starts up, I am told that a critical error has occurred and my Vm stops. I tried to increase Ram, and redownload the iso among other things, but I am not good at debugging. I would really appreciate if somebody could help me.
Thanks",ceddub
20239,Breakpoint When Starting 6.1.18,Windows,VirtualBox 6.1.18,2021-03-07T14:36:12Z,2021-03-07T14:36:12Z,2021-03-07T14:36:12Z,"I was asked to submit this bug report by scottgus1 as a result of my updated version of VirtualBox reaching a ""breakpoint"" when attempting to start it. I had no problems running version 6.1.16.

My original post is at:
https://forums.virtualbox.org/viewtopic.php?f=6&t=101947&p=495568#p495568

",SarcasticWit
20236,The mouse is hide on text fill area on the second monitor.,Windows,VirtualBox 6.1.18,2021-03-05T14:52:53Z,2021-03-05T14:52:53Z,2021-03-05T14:52:53Z,"Stand:
Host: Windows 10 20H2 (laptop)
Guest: Windows 7 (x64)

The mouse stay invisible when placed on any text fill place (notepad.exe for example). This problem reproduces only on second monitor when mouse in integration mode.

If change mouse mode as hooked, the problem disappears.",Nitron
20221,windows 10 unmountable boot volume,Windows,VirtualBox 6.1.18,2021-02-24T16:18:44Z,2021-02-24T16:48:37Z,2021-02-24T16:48:37Z,"I have an HP Envy 17 that has two disk drives, the original 1TB hard disk, and a second 480GB SSD. I have been running Windows 7 on the SSD with the hard drive as backup.

I just updated the hard disk to Windows 10 which I boot by popping out the SSD (which is in the DVD slot) so that Windows then boots from the second drive. 

I want to be able to run Windows 7 normally and use VirtualBox to boot up Windows 10 to run one application which won't run on Windows 7.

I have created a virtual raw disk for Drive 1 and when I attempt to boot it, I get the error message about the boot volume not being mountable. This happens after I get the windows logo and circle for a while.

Anyone have any suggestions how I can get this to work ? 
",Wewebb14
20219,VirtualBox starts up OK. Failed to open a session for the virtual machine. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine.,Linux,VirtualBox 6.1.18,2021-02-22T17:07:19Z,2021-02-22T17:07:19Z,2021-02-22T17:07:19Z,"I am experiencing the same problem as #20191. VirtualBox starts up fine. Existing VM fails to start with same error as this ticket describes. Failed to open a session for the virtual machine C7.
I have attached the log file, in addition to pasting it below.

The virtual machine 'C7' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VirtualBox VMs\C7\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

From VboxHardening.log:

16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'combase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'combase.dll' -> '\Device\HarddiskVolume3\Windows\System32\combase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\combase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDEVAPI.DLL (Input=MMDEVAPI.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDEVAPI.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcp_win.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #5 'rpcrt4.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #7 'oleaut32.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'mmdevapi.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\AudioSes.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\AudioSes.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'oleaut32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'oleaut32.dll' -> '\Device\HarddiskVolume3\Windows\System32\oleaut32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\oleaut32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcp_win.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcp_win.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcp_win.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcp_win.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\AUDIOSES.DLL (Input=AUDIOSES.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'rpcrt4.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\powrprof.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\powrprof.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffba0030000 LB 0x0004b000 C:\windows\SYSTEM32\powrprof.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\powrprof.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb99220000 LB 0x00185000 C:\windows\System32\AUDIOSES.DLL [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\AudioSes.dll [lacks WinVerifyTrust] 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\umpdc.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\umpdc.dll 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb9ffb0000 LB 0x00012000 C:\windows\SYSTEM32\UMPDC.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\umpdc.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99220000 'C:\windows\System32\AUDIOSES.DLL' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume3\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\wdmaud.drv (Input=wdmaud.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\wdmaud.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d5b0000 'C:\windows\System32\wdmaud.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #12 'mmdevapi.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #13 'msacm32.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\msacm32.drv) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.drv 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msacm32.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msacm32.dll' -> '\Device\HarddiskVolume3\Windows\System32\msacm32.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume3\Windows\System32\msacm32.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\msacm32.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'mmdevapi.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'mmdevapi.dll' -> '\Device\HarddiskVolume3\Windows\System32\mmdevapi.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d650000 LB 0x0001e000 C:\windows\SYSTEM32\MSACM32.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msacm32.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d9c0000 LB 0x0000d000 C:\windows\System32\msacm32.drv [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\msacm32.drv (Input=msacm32.drv, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\msacm32.drv [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d9c0000 'C:\windows\System32\msacm32.drv' 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'. 16e0.312c: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #1 'winmmbase.dll'. 16e0.312c: supHardenedWinVerifyImageByHandle: -> 22900 (\Device\HarddiskVolume3\Windows\System32\midimap.dll) 16e0.312c: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\midimap.dll 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'winmmbase.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'winmmbase.dll' -> '\Device\HarddiskVolume3\Windows\System32\winmmbase.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\winmmbase.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'... 16e0.312c: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume3\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008] 16e0.312c: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\msvcrt.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedDllNotificationCallback: load 00007ffb8d640000 LB 0x0000b000 C:\windows\System32\midimap.dll [fFlags=0x0] 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.312c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling] 16e0.312c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb8d640000 'C:\windows\System32\midimap.dll' 16e0.1aa0: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling] 16e0.1aa0: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffb99190000 'C:\windows\System32\MMDevApi.dll' 11a8.438: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 109337 ms, the end);

I have tried some suggestions found using Google and sometimes they help, but next reboot or start of VirtualBox results in same bad behavior. I also have uninstalled VirtualBox 6.1.18 and re-installed. It sometimes seems to let the VM start up and other times the same error appears. Both the install of VirtualBox 6.1.18 and the startup of VirtualBox 6.1.18 were done as administrator. Anti-Virus Used is: EseT Nod32 14.0.22.0 Windows Info: OS Name Microsoft Windows 10 Pro Version 10.0.19041 Build 19041 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-H70PDLJ System Manufacturer HP System Model HP EliteBook 855 G7 Notebook PC System Type x64-based PC System SKU 3E780AV Processor AMD Ryzen 7 PRO 4750U with Radeon Graphics, 1700 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date HP S77 Ver. 01.02.03, 11/27/2020 SMBIOS Version 3.2 Embedded Controller Version 7.44 BIOS Mode UEFI BaseBoard Manufacturer HP BaseBoard Product 8760 BaseBoard Version KBC Version 07.2C.00 Platform Role Mobile Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\windows System Directory C:\windows\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = ""10.0.19041.488"" User Name DESKTOP-H70PDLJ\willh Time Zone Central Standard Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.3 GB Available Physical Memory 27.9 GB Total Virtual Memory 36.1 GB Available Virtual Memory 32.6 GB Page File Space 4.75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes",WillH
20200,Guru Meditation 1155 with v6.1.18 on Windows 10 host running Windows 98 guest,Windows,VirtualBox 6.1.18,2021-02-17T22:55:24Z,2021-02-20T13:47:30Z,2021-02-20T13:47:30Z,"Hi,

I am running the 64bit Version of VirtualBox 6.1.18 r142142 on Windows 10 Pro (20H2) and installed a fresh Windows 98 Second Edition as Guest VM. I use the default Windows 98 configuration and only modified it to set 256MB RAM and 32MB Video RAM.

The first time everything was running fine (no additional programs installed) but since yesterday I get a Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT). This happens sporadically but only during login. Once the system startup is finished everything is fine. Sporadically means that it sometimes works 2-3 times but then the other 5 times I get the Guru.

Regards,
stauberix",stauberix
20209,Windows 10 host - ubuntu 20.10 guest crush,Linux,VirtualBox 6.1.18,2021-02-19T20:23:10Z,2021-02-19T21:15:26Z,2021-02-19T21:15:26Z,"When playing minecraft (KLauncher) on a guest ubuntu 20.10, the mouse behavior was tilted down or up, then the mouse stopped working in ubuntu altogether.",Дмитро
20181,WinVerifyTrust for MMDevAPI.dll,Linux,VirtualBox 6.1.18,2021-02-10T16:39:32Z,2021-02-19T13:00:07Z,2021-02-19T13:00:07Z,"Microsoft updated this dll on 09/02/2021 and since then all virtualbox guests are falling over unexpectedly during startup with exit code 1 (0x1). the cause in the VBoxHardening.log file is MMDevAPI.dll lacks WinVerifyTrust.
Attached is the VBoxHardening.log for a newly created Fedora Linux host.
Version of Windows is Windows 10 Pro Ver 20H2 OS build 19042.804",Tim_B
20194,Host-only card cannot be created,Windows,VirtualBox 6.1.18,2021-02-15T20:02:12Z,2021-02-15T20:02:12Z,2021-02-15T20:02:12Z,"Dear Team,

I should create an internal network for a uni project, but I cannot create host-only server for my debian virtual machine. Anything I do I keep receiving the below error message:

A gazda hálózati kártya létrehozása sikertelen.

Querying NetCfgInstanceId failed (0x00000002).

Eredmény kód: E_FAIL (0x80004005)
Komponens: HostNetworkInterfaceWrap
Interfész: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}


Virtualization is allowed, nothing is blocked.",Volodka91
20190,Temp files not deleted after drog-drop,Windows,VirtualBox 6.1.18,2021-02-15T08:54:05Z,2021-02-15T15:50:36Z,2021-02-15T15:50:36Z,"During dragging-dropping files from a (windows) VM to a (windows) host, a temporary directory is created in ""C:\Users\[USERNAME]\AppData\Local\Temp\VirtualBox Dropped Files""

After this, the files are copied to the selected destination dir. Unfortunately the temp dir is not being deleted after this action, causing the host drive to fill up (and potentionally crash the host because of a full system drive).

Could this deletion-after-coppying be included?",Gipster
20187,"Ubuntu 18.04 guest boots up 1 in 5 times. In other times, a cursor in blank screen blinking with no progress",Linux,VirtualBox 6.1.18,2021-02-14T15:03:42Z,2021-02-14T19:36:46Z,2021-02-14T19:36:46Z,"Host OS Info:
Windows 10 Pro 64 bit, Version 1909
OS Build 18363.1316

Guest OS Info:
Ubuntu 18.04 64 bit
Attached is VM_Settings.PNG

Steps to reproduce:
1. Start the guest

Expected outcome: (This happens 1 in every 5 trials)
The guest boots up. The guest OS shows its desktop. 

Observed outcome: (This happens 4 times in every 5 trials)
A blank screen with a blinking cursor shows up. After a while, blinking stops, and the guest bootup process wont proceed. The blank screen will show indefinitely. If we see this happening, the only option is to kill the guest OS in Windows and then re-boot the host OS. During shotdown & reboot of the host os, the host OS may say ""Referencing to an illegal memory in VMWare"" or something like that. 






",TeddyTeddy
20185,Crush VM and GUI,Windows,VirtualBox 6.1.18,2021-02-13T16:15:51Z,2021-02-13T16:15:51Z,2021-02-13T16:15:51Z,The program swore many windows about the error on each of the 2 running VMs.,Дмитро
20179,serial port freeze,other,VirtualBox 6.1.18,2021-02-10T08:51:46Z,2021-02-10T08:51:46Z,2021-02-10T08:51:46Z,"hello, I work with a PC under w10 (20H2) and a virtual image in OS/2 WARP. when I'm in version 5.2.44 the series communication between OS2 and my automaton works fine (full load without worries loading time about 10 minutes). when I migrate to version 6 (all versions), the communication no longer works (doesn't start at all or hangs after a while). if I go back to version 5, it works again. what I see is that the transfer speed is much faster as if it did not take into account the transfer speed. can you tell me what to do to make it work in version 6. Thank you",COLLAUDIN
20174,Installation of VMware Workstation Pro (might) have crippled my VirtualBox systems,Windows,VirtualBox 6.1.18,2021-02-08T14:44:59Z,2021-02-08T14:44:59Z,2021-02-08T14:44:59Z,"I have like 10-12 different VMs under Oracle VM VirtualBox. Have used this for many years now, and is very pleased with functionality and possibilities.
Some month ago I had to install VMware Workstation Pro. After that, none of my VirtualBox machines are working ok. Some hangs until I have to abort them others are so slow, they never get into action. Today I uninstalled the VMware Workstation, but the problem is still present under VirtualBox. Now, I do not know for sure that is was VMware that destroyed my VirtualBox. I uninstalled and reinstalled VirtualBox also today, didn't help. Any idea what I should do to make VirtualBox behave under Win-10 (64b) again ?
Martin",MaP
20146,"High CPU Kernel usage for any golang project, Windows 10 Host, Hyper-V turn on",Linux,VirtualBox 6.1.18,2021-01-22T05:20:12Z,2021-02-01T23:52:00Z,2021-02-01T23:52:00Z,"simple Vagrantfile for reproduce

{{{
# -*- mode: ruby -*-
# vi: set ft=ruby :

def total_cpus
  require 'etc'
  Etc.nprocessors
end


Vagrant.configure(2) do |config|
  config.vm.box = ""ubuntu/focal64""
  config.vm.box_check_update = false
  config.vm.synced_folder ""."", ""/vagrant""

  if Vagrant.has_plugin?(""vagrant-vbguest"")
    config.vbguest.auto_update = false
  end

  if Vagrant.has_plugin?(""vagrant-timezone"")
    config.timezone.value = ""UTC""
  end

  config.vm.provider ""virtualbox"" do |vb|
    vb.gui = false
    vb.cpus = total_cpus
    vb.memory = ""2048""
    vb.default_nic_type = ""virtio""
    vb.customize [""modifyvm"", :id, ""--uartmode1"", ""file"", File::NULL ]
    vb.customize [""modifyvm"", :id, ""--natdnshostresolver1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--natdnsproxy1"", ""on""]
    vb.customize [""modifyvm"", :id, ""--ioapic"", ""on""]
    vb.customize [""guestproperty"", ""set"", :id, ""/VirtualBox/GuestAdd/VBoxService/--timesync-set-threshold"", 10000]
  end

  config.vm.provision ""shell"", inline: <<-SHELL
    set -xeuo pipefail
    export DEBIAN_FRONTEND=noninteractive

    # docker
    curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -
    add-apt-repository ""deb https://download.docker.com/linux/ubuntu $(lsb_release -cs) test""
    apt-get install --no-install-recommends -y docker-ce
    apt-get install -y linux-tools-generic linux-tools-$(uname -r) 

    MINIKUBE_VERSION=1.16.0
    wget -c --progress=bar:force:noscroll -O /usr/local/bin/minikube https://github.com/kubernetes/minikube/releases/download/v${MINIKUBE_VERSION}/minikube-linux-amd64
    chmod +x /usr/local/bin/minikube
    # required for k8s 1.18+
    apt-get install -y conntrack

    minikube config set vm-driver none
    minikube config set kubernetes-version ${K8S_VERSION}
    minikube start --download-only=true
    /home/vagrant/.minikube/cache/linux/v${K8S_VERSION}/kubeadm config images pull
    minikube start --wait-timeout=20m
  SHELL
end

}}}

minikube fail with timeouts

during start docker containers  and kubelet systemd service
perf top -F 100 -p <kubelet_pid>
perf top -F 100 -p <dockerd_pid>

show following pictures (see attach)

https://monosnap.com/file/97lWTmuXbD9zVQqBpnFtz1B8YVbz8z
https://monosnap.com/file/iJPQK6YeTjVRsn3xziaY9h6LOS9cFi

any other daemons works fine",Slach
20161,"VM running Windows 10 20H2 guest, VM one time freeze",Windows,VirtualBox 6.1.18,2021-01-29T18:39:34Z,2021-01-29T18:39:34Z,2021-01-29T18:39:34Z,"Hi,
This hang occurred once. See attached for logs and minidumps for VirtualBoxVM processes in process tree. Host is Windows 10 20H2 64 bit
The guest was running a Remote Desktop Connection session and the Pulse Secure VPN application, which I left, then came back 50 minutes later to find it unresponsive, with black screen (that may be the last display from the RD client).",Mihai Hanor
20159,Reproducible fatal crash of a Linux Mint 20 XFCE VM (VirtBox running on Win10),Linux,VirtualBox 6.1.18,2021-01-29T10:47:30Z,2021-01-29T10:47:30Z,2021-01-29T10:47:30Z,"I have configured several virtual machines running the latest Linux Mint 20 XFCE4 edition. The display configuration is VMSVGA + 3D acceleration. After installing g++, make, and 6.1.8 guest additions I rebooted them. Then I installed the Atom editor. On every machine the same error occurred reproducibly: When I tore off a tab to attach it to another pane the vm crashed with an error message: 

The instruction at 0x00007FFE673EE652 referenced memory at 0x0000000000000000. 
The memory could not be written. 
Click OK to terminate the program. 

The error seems not to occur when I use another virtual graphics card, but due to the performance lack this is not solution to the problem. 

As I said: I have set up several machines from scratch, the error occurs everytime, absolutely reproducible within Atom. ",Dude McGee
20156,Windows BSOD,Windows,VirtualBox 6.1.18,2021-01-27T09:05:24Z,2021-01-27T09:21:00Z,2021-01-27T09:21:00Z,"Host: Windows 10 v1909, Hyper-V enabled, Intel i7-4790 [[BR]]

Guest Windows 10 v20H2 (newly install), 1 vCPU, 4 GB RAM, Nested Paging disabled[[BR]]

Symptoms: Random BSOD on guest OS, with something like following in Vbox.log


{{{
00:01:06.583527 GIM: HyperV: Guest indicates a fatal condition! P0=0xa P1=0x1 P2=0x2 P3=0x0 P4=0xfffff8002069dfa3
00:01:06.583631 GIMHv: BugCheck a {1, 2, 0, fffff8002069dfa3}
00:01:06.583632 IRQL_NOT_LESS_OR_EQUAL
00:01:06.583633 P1: 0000000000000001 - memory referenced
00:01:06.583633 P2: 0000000000000002 - IRQL
00:01:06.583634 P3: 0000000000000000 - bitfield
00:01:06.583634     b0: 0 - read operation
00:01:06.583634     b3: 0 - execute operation
00:01:06.583634 P4: fffff8002069dfa3 - EIP/RIP
00:01:10.260332 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:10.933294 AHCI#0: Reset the HBA
}}}

",ACH
20153,No audio output with Windows 10 host/guest,Windows,VirtualBox 6.1.18,2021-01-25T00:12:53Z,2021-01-26T10:18:47Z,2021-01-26T10:18:47Z,"Hello,
in the virtual machine no audio output is possible. The device manager doesn't show any missing drivers and everything looks normal.",OTonn
19427,windows 10 virtualbox 6.1.2 wierd cant copy / move webm files,other,VirtualBox 6.1.2,2020-03-24T11:05:34Z,2022-09-05T14:45:36Z,2022-09-05T14:45:36Z,"windows 10 virtualbox 6.1.2 wierd cant copy / move webm files out of vbox subdir 

windows 10 file manager just hangs !

is this a windows 10 bug or is virtualbox locking the files in some strange way ?
[[Image()]]",clive darra
19267,Guest audio loss on host display suspend,Windows,VirtualBox 6.1.2,2020-01-25T19:11:09Z,2021-08-04T08:46:40Z,2021-08-04T08:46:40Z,"Windows 7 guest audio ceases to function after host display is suspended if audio input is disabled for guest. 
The display is connected via HDMI interface. Sound in host is working without any issues. 
Issue is present at least since VB version 6.0 but possibly longer.
Workaround is the enable audio input for guest.
Related forum topic [https://forums.virtualbox.org/viewtopic.php?f=6&t=96411&p=468546 here]",Banana James
19314,Copy & paste patially broken in 6.1.2,Linux,VirtualBox 6.1.2,2020-02-14T18:26:19Z,2021-07-21T13:40:05Z,2021-07-21T13:40:05Z,"Host OS is Windows 8
Guest OS is Ubuntu 18.04
Other platforms not tested.

I upgraded from 6.0.14 to 6.1.2. Matching guest additions are also installed.
In Ubuntu the included guest toos are installed:
virtualbox-guest-dkms 5.2.34-dfsg-0~ubuntu18.04.1
Copy & Paste was working fine with 6.0.14 in both directions and I could copy & paste ""larger amounts"" of text characters. A few tens or hundred lines worked fine.
With 6.1.2 I can only copy & paste very view lines, about 4 to 8, depending on their length. This applies to both directions.
When the contents becomes to large, the paste target ""remembers"" the last clipboard content and pastes it instead.

No log currently available.",Megabreit
19235,GDM with (default) Wayland sessions are not usable,Linux,VirtualBox 6.1.2,2020-01-16T10:04:45Z,2021-01-28T09:09:25Z,2021-01-28T09:09:25Z,"When GDM uses Wayland for its login screen, the screen does not update after it is initially drawn. You can log in 'blind', so the login screen itself is working, it's just that the screen is never updated.

Resizing the VM's window on the host causes the screen to be redrawn once only.

If set `WaylandEnable=false` in GDMs config file then I get a traditional Xorg-based login screen and all is well again. And before GDM starts, the (plymouth-based) splash screen works fine, and after I log in then my (Xorg-based) session works OK.

My VM is using VboxSVGA with 3d disabled.",Sam Morris
19243,VMSVGA 3d get Crash while guest try to reboot,Linux,VirtualBox 6.1.2,2020-01-20T01:15:48Z,2021-01-25T23:31:53Z,2021-01-25T23:31:53Z,"Graphic Controller VMSVGA get Problem while 3d Acceleration Enabled. Error Message show while Guest do reboot procedure. 



",Aridu68
19382,Multiple Virtual Screen closes when changing a display,Linux,VirtualBox 6.1.2,2020-03-06T17:03:27Z,2020-03-06T17:06:26Z,2020-03-06T17:06:26Z,"I'm running Fedora 31 on Windows 10 with three monitors.
1. Dell XPS 15 (3840x2160 at 250% scaling which is recommended on Windows)
2. Dell Monitor (1920x1200 at 100% scaling)
3. Dell Monitor (1920x1200 at 100% scaling)
#2 and #3 are connected to XPS 15 via usb hub and daisy chained between #2 and #3.

These monitors are layout from left in above order.

I'm running the Fedora 31 using #2 and #3 monitors (so two virtual screens).

When I turn on the Auto-resize Guest Display option the second virtual screen crashes in a few operations.

Issue #1: When I drag and drop the second virtual screen window around above three monitors.  When I start the vm, the second virtual screen window appears in the monitor #1 (Dell XPS 15) and the first virtual screen windows appears in the monitor #2 (that is because I previously started in it).  I drag and drop the second virtual screen window to the monitor #3.  Then, the window blinks and planed in the monitor #1 and the windows is all grayed out.  Sometimes the window closes.  The first virtual screen window remains functional.

I can turn off the Auto-resize Guest Display options, and above issue does not happen.  After moving the second virtual screen window, I can turn on the option and use screens in the full screen mode.

Issue #2: After getting two virtual screens in the monitor #2 and #3 in the full screen mode.  The second virtual screen window closes if I getting out of the full screen mode.

There is the way around so not blocking issue, but this problem is annoying.",Takahiro
19324,"VM abort with error message, log has rtR3WinUnhandledXcptFilter",Windows,VirtualBox 6.1.2,2020-02-19T22:34:53Z,2020-02-23T22:44:02Z,2020-02-23T22:44:02Z,"At seemingly random times, my VM aborts with an error dialog:

VirtualBoxVM.exe - Application Error : The instruction at 0x00007FFD9D2E8201 referenced memory at 0x0000000000000021. The memory could not be written.

Log shows that the VM had started recording audio (no idea why), then shortly after aborted.",Mark Cranness
19334,VirtualBox version 6.1.2.,all,VirtualBox 6.1.2,2020-02-21T21:50:16Z,2020-02-21T21:50:16Z,2020-02-21T21:50:16Z,"Hello Oracle,

I have 2 complaints that I consider bugs in the new version of Virtual box.

but first I like to thank you so much for VirtualBox, I use it since 10 years and cannot live with out it, and this even I am specialized on Microsoft products since 1982!

Complaint/Problem-1: on the front page of ""Oracle VM VirtualBox Manager"" the virtual machine was showing the path including the drive where the VirtualBox guest is located, however with the new version it was taken away, which means that I have to press settings and then press storage and then press the *.vdi file to see where the file is located, and that is more than ammoying and delaying me, because4 I use over 30 Virtual Machines and cannot remember where is what and always need to know where it is located. Can you please place the full path back in the front page of the manager?

Complaint/Problem2: also on the front page of ""Oracle VM VirtualBox Manager"", they scrollbar is very annoying because I cannot see it and have a tough time to make it visible enable I can scroll up and down to see where is the Virtual Machine that I want to use. Can you please make the scroll bar always visible and therewith make my life easier as well as the lives of hundreds of thousands of others users?

I thank you for your understanding and I really hope you make these changes.

Should you require more information then please do not hesitate to contact me at M@Najar.eu.

Thank you and I wish you a very pleasant and most successful year 2020.

With my sincere regards,

Michael Najar
M@Najar.eu
0031-6-8442 6363
Erasmusplein 80
2532 RE The Hague",Najar
19328,Critical error pop up when starting machine,Linux,VirtualBox 6.1.2,2020-02-20T22:31:08Z,2020-02-20T22:31:08Z,2020-02-20T22:31:08Z,"When I try to load virtual machine after rebooting I get a pop up stating critical error and suggesting I post here with the logs. If it is relevant, Ubuntu had just performed updates.",tdsTPPS
19322,Unable to use text instalation of linux operating system with accessibility turned on in virtual box.,Linux,VirtualBox 6.1.2,2020-02-19T21:10:10Z,2020-02-19T21:10:10Z,2020-02-19T21:10:10Z,"When using the text installation of debian with accessibility features turned on it is impossible to use keyboard to perform any actions in a virtual machine after turning the speech on in the guest operating system. To reproduce these steps do the following steps: Run a debian64 bit full dvd installation iOs file in a virtual machine. You can find this file here: https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-10.3.0-amd64-DVD-1.iso
When you run a virtual machine, press the following keys: ""s"" and then press enter. You will turn on the speech support and the text installer. Then you will here speech synthesiser saying ""Select a language"". Try to press any keys on a keyboard, for example: numpad 7 and 9, 4 and 6, arrows up and down, any keys. You will notice that the virtual machine doesn't respond and you don't hear anything. That makes fully impossible to install debian for blind users to a virtual box. Blind people can only use text installer of debian with the speech support and now it is impossible to do in a virtual box. Please fix that issue! Thank you!",Vsevolod Popov
19280,"6.1.2 Installation failed, could not run required dll",other,VirtualBox 6.1.2,2020-01-30T16:23:51Z,2020-02-10T19:12:59Z,2020-02-10T19:12:59Z,"I'm attempting to install VBox 6.1.2 on a Windows 10 v1909 host OS and getting an error regarding dll failure which I've attached a screenshot of. Virtualization is enabled on BIOS, Hyper-V is fully enabled in Win10 settings, and there hasn't been a previous installation on this machine for me to try to finish wiping out first. I have tried older versions of VBox (6.0 and 5.2) and run into the same failure, and I couldn't find anything on the forum or general internet that pointed me in the right direction.

Any help is appreciated.",Fluxer
19298,Frequent crash when suspending virtual machine,Linux,VirtualBox 6.1.2,2020-02-10T09:36:41Z,2020-02-10T13:24:27Z,2020-02-10T13:24:27Z,"Most of the time when I pause (Host+P) my Linux virtual machines, VirtualBox crashes.
This behavior seems to getting worse with every new release.
I can't really remember when this started, but I'm pretty sure that I never had the issue with versions before 6.0.

After every crash, I see exception ""rtR3WinUnhandledXcptFilter caught an exception on thread"" in the log file.
I attached two of them.
",didier.martiny
19294,Frequent crashing with The Instruction at 0x... referenced memory at 0x... The memory could not be read,Linux,VirtualBox 6.1.2,2020-02-06T15:51:02Z,2020-02-07T17:27:51Z,2020-02-07T17:27:51Z,"I have read many similar posts and tried the recommended fixes, but I am still having the issue. 

Host: Windows 10 pro, 16Gb ram, updated the video drivers
Guest: Ubuntu, 8Gb, 256Mb video mem

Seems to happen most frequently when I am running VSCode and click on any menu or context menu.

Attaching logs",tdsTPPS
19284,Error when opening vscode file menu,Linux,VirtualBox 6.1.2,2020-02-03T08:14:44Z,2020-02-03T08:46:38Z,2020-02-03T08:46:38Z,"
The instruction 0x00000000 referenced memory at 0x00000000. The memory could not be written. Click OK to terminate the program""",china_liu
19282,Virtual Box Machine fails on startup,Linux,VirtualBox 6.1.2,2020-01-31T20:03:53Z,2020-02-01T00:03:17Z,2020-02-01T00:03:17Z,"When attempting to start a machine, on the newly upgraded Virtual Box, it does not start. It gives an error saying - 
Error launching Virtual Box VM Process 5
Please try reinstalling Virtual Box
(screenshot attached)
When I click on Ok, it then displays another dialog box with the following message - 

The virtual machine 'orarac1' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\*******\VirtualBox VMs\orarac1\Logs\VBoxHardening.log'.
Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}



I tried reinstalling virtualbox, but it still gives an error.
I tried looking at the hardening log. I have attached it in the ticket too.
I have already done an scf /scannow on the entire desktop computer c: drive and it has not returned any errors.
",FireExit
19281,VB issue with multiple cores for Xeon 5450,all,VirtualBox 6.1.2,2020-01-30T17:10:23Z,2020-01-30T17:10:23Z,2020-01-30T17:10:23Z,"I have an ""older"" server running a motherboard with two Xeon 5450 (4 cores each) with 16 Gb of ram running W2016. I have installed the current version of VB and installed W7, W10 and Ubuntu (all latest versions) in respective VMs. All settings in VB work OK (as expected), except when I add more than 2 CPU cores to any VM. When that happens, CPU utilization (for the VM) goes to 100% (all cores - after a little while) the VM slows down to a crawl and/or freezes. This is most certainly not the expected behavior.",globus999
19279,BSOD (DRIVER_OVERRAN_STACK_BUFFER ) in guest when trying to run nested virtual machine,Windows,VirtualBox 6.1.2,2020-01-29T18:33:43Z,2020-01-29T18:41:17Z,2020-01-29T18:41:17Z,"I am unable to make any 64 bit virtual machine to work in guest using nested virtualization provided by Virtualbox. I am using Vbox version 6.1.2 in both Host and Guest (guest have the vbox additions installed). As soon as I try to run any 64 bit VM in guest the guest OS crashes with BSOD (but Host is stable). I am using latest Windows 10 64 bit 1909 in both host and guest. Host is running AMD Ryzen 7 3700X CPU in ASUS x570 TUF Gaming PLUS motherboard.
I have attached logs of the Guest machine and the kernel memory dump from the guest OS that crashed.
The BSOD from guest is related to VMMR0.r0 driver with memory_corruption message. The bug check code is DRIVER_OVERRAN_STACK_BUFFER ",proboszcz
19264,Crash when 'un-pausing' paused VM on Win10 host,all,VirtualBox 6.1.2,2020-01-24T22:01:25Z,2020-01-24T22:01:25Z,2020-01-24T22:01:25Z,"I usually have 1 or 2 guests open on a Win10 host. When I'm not using the host system, I suspend or hibernate it. In addition, I manually pause a VM when not using it, in order to save host resources.

Sometimes I get crashes:
- I manually want to resume a paused VM. Crash! I then do a normal shutdown of the other VM as guest user (start button). The second VM crashes too. Conclusion: It's probably not a problem of a single VM instance, but rather of some component common to all guests.

- I suspend/resume the Windows host. On resume, I immediately get a VM crash, presumable because vbox does an implicit pause/resume of a VM.

These things happen with some probability. I can't reproduce it reliably. On vbox 6.0.12 the probability was so low that I didn't really mind. With 6.0.14 and 6.0.16 the probability seemed much higher, so I didn't use them. Now I have switched to 6.1.2 r135662 (Qt5.6.2) and I get it quite often.

I have already described my problems in https://forums.virtualbox.org/viewtopic.php?f=6&t=96538

I'm reporting now a case that seems to be typical. Here is what I did:


------------------------------------
1. Start Ubuntu guest.
2. Start WinXP guest.
3. Manually pause the Ubuntu, while WinXP keeps running.
4. Put host (Win 10) asleep.
5. Wake up the host. On wakeup, I immediately get a message notifying me of a VM crash. It turns out that the WinXP guest is gone, the paused Ubuntu guest is still there.
6. I try to manually resume the paused Ubuntu, but it crashes immediately.
------------------------------------

I attach logs of both VMs.
The following lines in the logs may be of interest:

20:58:02.032649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000163c!!! (Log of Ubuntu guest)

18:34:20.151649 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000002e00!!! (Log of WinXP guest)
",ueli
19233,No recent-items jumplist on windows10,Linux,VirtualBox 6.1.2,2020-01-16T09:38:24Z,2020-01-22T09:33:23Z,2020-01-22T09:33:23Z,"I am using virtualbox on Windows. On windows7, when I ""pinned"" it to start menu, it was shown at the top of unfolded start menu, and when hovered by mouse cursor, a sub-menu unfolded with recent virtual-machines. Same as recent documents for MS word or simillar. AFAIK theese are called ""jump-lists"".

After migrating on Windows10, I can see that mechanics are changed a bit - I can of course pin an item to start menu, and most of those pinned items also support some ""recent items"" thingies, but it now requires a right-click on the pinned item.. 
Unfortunately, for virtualbox it doesnt work - when right-clicking on the pinned icon I, a menu unfolds with only below options:
* unpin
* resize
* more
* uninstall
",michal.mulawa
19238,Boot time for linux guest is about 50% slower on 6.1.2  compared to 5.2.34,Linux,VirtualBox 6.1.2,2020-01-16T19:53:21Z,2020-01-20T18:33:01Z,2020-01-20T18:33:01Z,"Host : Windows 10 1903 (10.0.18362.535)

I have been using linux mint 19.2 installed on Virtualbox 5.2.34 for a while.
I just recently upgraded virtualbox to the latest version 6.1.2.

The boot time on 5.2.34 is in average : 1.26  (1 minute and 26 seconds )
The boot time on 6.1.2  is in average : 2.13  (2 minutes and 13 seconds )",DanMc01
19234,VBoxClient --clipboard terminates silently,Linux,VirtualBox 6.1.2,2020-01-16T09:44:09Z,2020-01-16T10:06:59Z,2020-01-16T10:06:59Z,"VBoxClient --clipboard no longer runs on my Debian VM. If I run it by hand:


{{{
$ VBoxClient -v --clipboard -f 
Shared Clipboard: Starting X11 event thread
Shared Clipboard: Stopping X11 event thread ...
Shared Clipboard: X11 event thread terminated successfully
Error connecting to host service, rc=VERR_NOT_IMPLEMENTED
Service terminated abnormally with VERR_NOT_IMPLEMENTED
Running service failed: VERR_NOT_IMPLEMENTED
}}}



Previously reported at <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946843> and <https://forums.virtualbox.org/viewtopic.php?f=3&t=96309>",Sam Morris
20525,High VMM Load on Intel CPUs introduced in 6.1.20,Windows,VirtualBox 6.1.20,2021-08-26T18:15:06Z,2022-07-27T19:24:30Z,2022-07-27T19:24:30Z,"Beginning in version 6.1.20, and also happening in .22, and .24, there is a significant increased VMM Load reported in the Session Information dialog with hosts running Intel processors when using 2 or more vCPUs, getting progressively worse as the vCPU count is increased up to the recommended threshold shown in the VM Settings dialog.

I reverted to 6.1.18 and confirmed the issue is not present in this version, with low to minimal VMM Load.

I tested and am not seeing the issue on a Ryzen 5 3400G host at this time. I have performed the same test with multiple vCPUs with 6.1.20, and 6.1.24 and the VMM Load is low in all these cases on a Ryzen host.

All hosts tested are running Windows 10 x64. Tested and confirmed issue with Windows 10 x64 and Debian x86-64 guests on Intel 3rd gen Core i5, Core i7 5820K, Xeon E5-1620 v2, and Xeon E5-2620 v4 CPUs.",lbgaus
20379,6.1.18 to 6.1.20 Intel pro/1000 changes,other,VirtualBox 6.1.20,2021-05-25T12:45:54Z,2021-05-30T09:54:08Z,2021-05-30T09:54:08Z,"Hello,

Current Menuet64 network driver (bridged) for i8254x works fine with 
VirtualBox 6.1.18, but not anymore with 6.1.20.

I've read from previous tickets that for example the 
RDT register and interrupts are handled differently in 6.1.20.

So could you provide some (bit-level) details about the RDT 
register (and possibly other) changes, so I can debug the driver here ?

Thank you.
",AndrewMC
20364,VirtualBox guest freezes when chaning host audio interfaces,Linux,VirtualBox 6.1.20,2021-05-13T17:27:47Z,2021-05-25T13:30:35Z,2021-05-25T13:30:35Z,"The VirtualBox Ubuntu guest may freeze / (GUI hangup) when the audio in a guest is in use and an audio interface changes on the Windows 10 host.

Tested with multiple Ubuntu guest versions 18.04 up to 21.04.

Users reported the same issue when connecting USB audio devices (like bluetooth).

See full detailed logs and 100% reproducible testcase in issue:
https://forums.virtualbox.org/viewtopic.php?f=6&t=94233&p=499715#p499715",Erwin
20315,6.1.20 Fails to start guest : memory can't be written,BSD,VirtualBox 6.1.20,2021-04-22T14:32:55Z,2021-04-23T21:36:15Z,2021-04-23T21:36:15Z,As of 6.1.18 it succeeded.,MikhailRokhin
20318,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT),Linux,VirtualBox 6.1.20,2021-04-23T07:25:42Z,2021-04-23T07:25:42Z,2021-04-23T07:25:42Z,"Hi,
any help please",olfat
20311,Failed to create a host network interface.,Linux,VirtualBox 6.1.20,2021-04-21T16:58:04Z,2021-04-21T16:59:18Z,2021-04-21T16:59:18Z,"Failed to create a host network interface.

SetupDiCallClassInstaller (DIF_INSTALLDEVICE) failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

",TH
20357,VM launch fail on Windows 10 when WSL2 and Docker is enabled,Linux,VirtualBox 6.1.22,2021-05-11T10:16:02Z,2022-08-01T18:37:28Z,2022-08-01T18:37:28Z,"We are using Docker containers and Vagrant + VirtualBox virtual machines in Windows 10 (now 20H2). Would be very convenient to make both parties (Docker+WSL2 and VirtualBox) working together on same machine. However when Docker Desktop with WSL2 support is installed, existing VirtualBox virtual machines (Linux 64-bit quests with installed VirtualBox Guest additions) fail to launch. Instead error message appear:

''WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).
VT-x is not available (VERR_VMX_NO_VMX).
''

""Windows Hypervisor Platform"" feature enabling in Windows features does not change anything. It is not possible to change paravirtualization interface type under VM ""Settings - System - Acceleration"" too - OK button remain disabled.

To get VirtualBox VMs running again either ""hypervisorlaunchtype"" must be disabled through Windows Command Prompt with command
{{{
bcdedit /set hypervisorlaunchtype off
}}}
or Docker Desktop must be uninstalled together with ""Windows Hypervisor Platform"", ""Virtual Machine Platform"" and ""Windows Subsystem for Linux"" feature disabling in Windows Features with subsequential Windows restart. Both actions obviously permit Docker container using together with VirtualBox. Are there is another way how to use VirtualBox 64-bit VMs in Windows host together with WSL2 + Docker installed in same Windows host?

I seen Hyper-V virtualization support appearing in VirtualBox changelog starting from version 6.1.18 with Hyper-V related fixes in 6.1.22. However it does not help for us. Didn't found any useful information about how to run Docker+WSL2 and VirtualBox together in Internet either.

Environment info:
{{{
Host: Windows 10 20H2, 64-bit
Guests: Ubuntu Linux 18.04 LTS, 64-bit
Hardware: Dell OptiPlex 980, Intel Core i5-750 CPU (has VT-x support), 16 GB RAM
Dell BIOS, version A18, VT-x is enabled
}}}",Janis Baumanis
20371,Video recording settings not saved,Linux,VirtualBox 6.1.22,2021-05-19T09:15:39Z,2022-07-28T19:33:56Z,2022-07-28T19:33:56Z,"It seems that video recording settings of VMs are not saved. At least this is true for file path and frame size. Leaving VirtualBox Manager and restarting it, video recording settings are back to default.

In the .vbox file of the VM, I found the entry VideoCapture never reflecting these settings.

Maybe this is related to [ticket:20297], because depending on the modification history of video recording settings I experience the same crash. ",Reiner Brodbeck
20431,Sound lost after a couple of changes of host audio output device,Windows,VirtualBox 6.1.22,2021-06-26T11:23:53Z,2022-04-12T16:23:36Z,2022-04-12T16:23:36Z,"I have found another bug, which looks similar to an old one from #17225: if I change the host output from speaker to the Bluetooth headphones, the sound of VBox goes to the headphones. Then I change back and the VBox sounds also goes to the speakers. But the next time I repeat the change to Bluetooth, the VBox ignores it. The sound form the host and programs, running on the host played in the Bluetooth headphones, but the sound from VBox is lost. If I turn the BT headphones off, the VBox sound returns to the speakers, but I can't get the VBox sound to the Bluetooth anymore. The only way is to save and restore the VM state or to turn the VM off and then on (restart).

All information about how I test the sound in VBox is in other ticket.  I'm on 6.1.23 version 145326 now.",boxer01
20446,VM intermittently freezing,Windows,VirtualBox 6.1.22,2021-07-02T19:08:59Z,2022-03-03T03:31:57Z,2022-03-03T03:31:57Z,"Virtual Box Version 6.1.22 r144080 (Qt5.6.2)

Operating System = Windows 10 (OS Build 19042.1052)
                   VM simulating operating system = XP

Works fine for a while then freezes when repeating the same action that had worked fine just before.  

Only way to get it to unfreeze is to Close down application completely.  

Had been working on Lotus spreadsheet when it freezes.  Have had 6 freezes in 2 days.


All worked perfectly 2 versions ago, but see no way to go back to an earlier version.  Started having the problem previous version and updated to this version since it was causing the same problem.
",Sooz C
20382,Unable to create a HostOnly network on Windows 10 NetCfgInstanceId failed,Linux,VirtualBox 6.1.22,2021-05-28T18:29:05Z,2021-11-05T13:24:30Z,2021-11-05T13:24:30Z,"Using the GUI and ctrl+H to show the host network manager, running as administrator in Windows 10 home, I am no longer able to define a HostOnly network. This is the error I receive:

Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

How can I fix this?
",fjb_saper
20405,Virtual Machine crashes when dragging link,Linux,VirtualBox 6.1.22,2021-06-15T15:40:57Z,2021-09-20T18:21:06Z,2021-09-20T18:21:06Z,"Hello, I was using a virtual machine when i accidentally dragged a link inside the virtual machine. The virtual machine got aborted by virtualbox. it also gave a memory read error. I think the reason why it gave that error is because virtualbox is not checking if what the user drags inside of the virtual machine is a file or directory so it tries to read it then because it is not a file it gives a read error. So i would suggest you guys let virtualbox check if what the user drags inside the virtual machine is a file or directory.
So i would like to report this issue to help improve virtualbox.
If i could contribute through code it would a dream.
[[Image(https://media.discordapp.net/attachments/470253814235136044/854380201428516894/unknown.png?width=722&height=406)]]
[[Image(https://media.discordapp.net/attachments/470253814235136044/854380211632865297/unknown.png?width=722&height=406)]]
If you look above you can see the virtual machine has been terminated or aborted.",MemoryJack
20483,"Virtubox crashes when the vbox window was resized. Host Windows 10 Pro (64-bit), guest Debian GNU/Linux",Linux,VirtualBox 6.1.22,2021-08-01T04:30:39Z,2021-09-17T09:49:46Z,2021-09-17T09:49:46Z,"Host: 
Edition	Windows 10 Pro (64-bit)
version	21H1
Installed	‎2020/‎12/‎16
OS build	19043.1110
Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
Debian GNU/Linux 

When I try to resize the VBox window under Windows 10 Pro (64-bit)  by grabbing the right edge and tried to shrink the width, VBox crashed.

It seems it encountered exception.
Funny, I see screen count changed or something to that effect in the attached log.
I only have a single physical display.

TIA
",ci-zephyurus
20390,Guest hung after host resumes from sleep,Linux,VirtualBox 6.1.22,2021-06-07T23:17:24Z,2021-09-08T00:32:39Z,2021-09-08T00:32:39Z,"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

When I suspend and resume the host, the guest is no longer responsive, requires a forced power off and complete restart of the guest.  Similar to 20270, but the trick of pausing and resuming doesn't work.

Used to work fine, I suspect it started with a host OS update.  Happened under 6.1.17 too.

Logs attached.",gkcgareth
20457,Guest crashes when unpausing,Linux,VirtualBox 6.1.22,2021-07-13T21:16:15Z,2021-09-08T00:30:33Z,2021-09-08T00:30:33Z,"Guest was paused for a long time (overnight).  When unpaused, it ran for a few seconds then locked up.  Required a hard reset.

Guest logs attached.

VirtualBox Graphical User Interface
Version 6.1.22 r144080 (Qt5.6.2)
Copyright © 2021 Oracle Corporation and/or its affiliates. All rights reserved.",gkcgareth
20522,hang on windows after update notifier window pops up,Linux,VirtualBox 6.1.22,2021-08-23T15:54:51Z,2021-08-23T15:54:51Z,2021-08-23T15:54:51Z,"i was using a relatively recent VirtualBox version on Windows 10
and was sending my host machine to sleep (as it works quite nice all the time).
after a wake up VBox brought up the notifyer dialog for a new version
beeing available on the internet for download. (not sure if that dialog is normally modal or not - but it would be better if its not!)
at this point i was no longer able to control the main application and neither the currently running VM window. neither keyboard nor mouse input were able to interact with any of the two main windows and (BAD THING HERE) not even with the update notifier pop up windows.

(closing either of this first with a task manager did not cure the situation for the other window.)",jetpilot
20462,VBoxNetLwf and EventID 12 on Windows,all,VirtualBox 6.1.22,2021-07-18T05:33:59Z,2021-07-29T11:04:38Z,2021-07-29T11:04:38Z,"I am aware that this has been posted already but I cannot find an open ticket! In reference to:
https://forums.virtualbox.org/viewtopic.php?f=6&t=87971
I would like to mention that all solutions are not working and the issue is permanent:

Randomly, the VBoxNetLwf driver crashes and causes an event log entry with ID 12. Unfortunately this also causes the WiFi connection to disconnect and it takes some time until Windows recovers internet connection.

I've attached two of these log entries in a file.

Is there anything that can be done about it? Is there already any knowledge when this happens and where (in the source code) this issue occurs? I also read it maybe related to energy management. But I doubt that since it happens for me also when I am actively working on the computer e.g. connected to a remote machine via VPN (which gets disconnected in that case, obviously).",Slimfast
20464,Virtualbox 6.1.22 crashes on windows 10 host,Linux,VirtualBox 6.1.22,2021-07-20T02:50:25Z,2021-07-20T02:50:25Z,2021-07-20T02:50:25Z,"My virtual box crashes after booting as well as after hibernation. It works fine after the first crash, but it surely crashes for the first time. I am using Virtualbox version 6.1.22, my host machine is Windows 10 and the guest machine is Kali.
",jishu
20381,6.1.22 hangs perhaps due to vmsvga/video,Linux,VirtualBox 6.1.22,2021-05-27T07:24:51Z,2021-07-12T16:38:43Z,2021-07-12T16:38:43Z,"I had to downgrade to 6.1.20, which was stable for me.

I suspect it has something to do with video/vmsvga

Machine: HP Envy Pavilion 17t-j186nr 
Host is windows-10 updated to 19043.985 21H1
Guest is Fedora-Workstation-34 kernel 5.12.6-300, guest additions 6.1.22 is installed

With 6.1.22, If machine is started as hidden, machine can be ssh-ed to and is stable for very long time.

With 6.1.22, If machine is made to be shown, then after GDM login, after starting a terminal app, wezterm, firefox, virtualbox freezes, becomes non-responsive and remains stuck. 

It is possible to get mouse cursor, which in stcuk state is invisible, to the bottom, to hover over and bring up the VM-menu, minimize it and then get to the windows host. Other menu commands like reset do not work.

Outside, in the host windows, taskmgr can be used to kill and Virtualbox processes, helps close all virtualbox windows, and start over. 

reinstall of 6.1.22 did not help
",gkamathh
20454,Linux cannot Log  user in with visual interface,other,VirtualBox 6.1.22,2021-07-12T12:11:04Z,2021-07-12T12:11:04Z,2021-07-12T12:11:04Z,"Since the 6.1.22 update I cannot log in to any visual interface anymore (Tested in Ubuntu 20.04.2 LTS ). 

CLI login is allowed and Linux console is fully functional but login attempts through the visual interface results in ""Oh no! Something has gone wrong"" screens. 

I have tested the same image exported to VMware Workstation 16 and works flawlessly.

Attached log file",fizcris
20451,Bridged adapter list is empty (with NDIS5 drivers),all,VirtualBox 6.1.22,2021-07-09T10:35:18Z,2021-07-09T10:35:18Z,2021-07-09T10:35:18Z,"As a workaround for #15060 I tried installing VirtualBox using the old NDIS 5 network drivers, by running the installer with the option `-msiparams NETWORKTYPE=NDIS5`

After installation, attempting to configure a bridged network interface is impossible because the list of adapters to bridge to is empty (see attached screenshot).

There are no other error messages from VirtualBox about a the failure to enumerate network adapters. It looks like the NDIS5 drivers are active, given...

{{{
PS > get-windowsdriver -online | Where-Object -property ProviderName -Like *oracle* | format-list

Driver           : oem16.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_a4e9db3f071a0883\vboxnetadp.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem22.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetflt.inf_amd64_1ca009f9c76e42da\vboxnetflt.inf
Inbox            : False
ClassName        : NetService
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem56.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetfltm.inf_amd64_4f271f5e54b849f3\vboxnetfltm.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem9.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxusb.inf_amd64_721cfc8f354e0c0c\vboxusb.inf
Inbox            : False
ClassName        : USB
BootCritical     : True
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080
}}}
",Sam Morris
20447,NVMe fails in Windows 10/11 guest,Windows,VirtualBox 6.1.22,2021-07-04T23:47:12Z,2021-07-05T21:20:34Z,2021-07-05T21:20:34Z,It's impossible to start from bootable DVD-iso connected to NVMe and Windows 10/11 setup can't detect hdd attached to NVMe to install it to.,MikhailRokhin
20442,XHCI has wrong PCI config space and runtime register settings,other,VirtualBox 6.1.22,2021-06-30T21:17:30Z,2021-07-05T07:24:04Z,2021-07-05T07:24:04Z,"host: Win-10, guest: OS/2

These PCI config space registers contain incorrect values (without being touched by any driver):
SBRN: is=0x20 should be=0x30 (only allowed value)
FLADJ: is=0x00 should be=0x20 (default value)

Additionally, runtime register MFINDEX is upcounting and wrapping even though the operational USBCMD register does not have the ""R/S"" bit set (""run"").

This is according to XHCI spec. I am not enough of a virtual machine expert to know if it is the USB HW that is not working according to spec or if it is the virtualization.

I have tried to get XHCI working with the corresponding XHCI driver (for OS/2) but it would not work. Not sure if that's the HW/virtualization or the HC driver doing the wrong thing.",lerdmann
20432,Cannot write to raw disk under Windows 10 21H1 guest in VBox 6.1.22,Linux,VirtualBox 6.1.22,2021-06-27T13:05:56Z,2021-06-27T14:06:44Z,2021-06-27T14:06:44Z,"Severe bug, results in complete loss of all data written.

Quick description: I have some mechanical Western Digital Purple SATA drives hooked up via a Perc H310 SAS HBA. (SAS can use SATA drives). Windows 10 host, Ubuntu guest. Some of them can be written, but one which is larger and has NTFS on it can't. The ones that can be written to use ext4 and btrfs partitions. This probably isn't relevant, but who knows.

I had been using VBox 6.1.15 on a Windows 10 host (updated to latest non-insider version which is 21H1, build 19043.1081) with a Ubuntu 20.04 guest, with guest additions installed. Recently, I tried using it with a 14 TB WDC WD140PURZ-850A82 (Western Digital Purple 14TB mechanical SATA drive) connected via a Perc H310 SAS HBA. It is completely new and I created a single partition on it spanning the whole disk. I formatted it to NTFS using Windows 10 and put it offline, then created a VMDK using 

{{{
PS C:\WINDOWS\system32> & 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' internalcommands createrawvmdk -filename C:\VirtualBox\SAS-PhysicalDrive5-14tb.vmdk -rawdisk \\.\PhysicalDrive5
}}}

and then set it to write-through under the VBox gui. Finally I hooked it up to a SATA AHCI controller with 16 ports. The ""Use Host I/O Cache"" box was originally empty (unchecked), and I would get this error:

{{{
The I/O cache encountered an error while updating data in medium ""ahci-0-4"" (rc=VERR_WRITE_PROTECT). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}

If I DO check the ""Use Host I/O Cache"" box, then the data seems to get written and no error is produced - but when I unmount and remount the partition, it's gone.

What's weird is that there are other drives, also from the same drive family (WD Purple) and on the same SAS controller, which don't have the same issue. But they're linux formatted (either ext4 or btrfs) and also smaller (less than 10 TB).

If I turn on ""Use Host I/O Cache"", I am able to write to the disk. However, 3 issues remain still:

1. performance is very, very poor. On the order of 20 MB/sec. These drives are capable of 150 MB/sec when used under the Windows 10 host on the same controller.

2. if I type sync in the guest, it takes > 5 minutes, and meanwhile hangs up all disk IO

3. The data isn't ACTUALLY written to the disk.


Things I tried include:
- formatting the disk again. Didn't help
- I tried whether writing to the disk works when it's hooked up to the host (and not offlined). It works - files written to disk remain after offlining and again onlining the disk (which essentially unmounts and again mounts the disk on Windows 10).
- I updated to VBox 6.1.22 with latest guest additions, no improvement
- In the VM, I created a new LsiLogic SAS controller, and put the drives under that, no improvement

Finally, I am always running VBox GUI as admin, which is required in order for raw disk access to work in the first place, for all drives, even the ones where writing to disk does work.

Also, I've noticed that when I format the disk to a single NTFS partition under Windows 10, it actually creates two partitions: one tiny ~15MB one that's a ""Microsoft reserved partition"" (/dev/sde1 under Linux for me), and one that spans the rest of the disk (/dev/sde2) (which is where the data lives). Under the Windows 10 Disk Management panel, only one partition is shown. When I mount /dev/sde2, I can see the System Volume Information directory and some other files I put on that drive when it was mounted directly on the host, so I know it's the right partition.

P.S. I have previously re-opened #14461 thinking that was the same bug, but it's not - in #14461 you could work around to write data to the disk, in my situation the same workaround results in data being written to a black hole. Could someone please close that ticket?",cheater
20427,can't start the virtual machine,OSX Server,VirtualBox 6.1.22,2021-06-21T16:18:33Z,2021-06-21T16:40:00Z,2021-06-21T16:40:00Z,"when i start virtual machine i have got this error

{{{
Failed to open a session for the virtual machine Mac.

Could not launch the VM process for the machine 'Mac' (VERR_INVALID_UTF16_ENCODING).

Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

}}}

how can i fix it?

",gihan
20400,Virtual Machine crashes when dragging link,Linux,VirtualBox 6.1.22,2021-06-15T15:35:49Z,2021-06-19T12:39:25Z,2021-06-19T12:39:25Z,"Hello, I was using a virtual machine when i accidentally dragged a link inside the virtual machine. The virtual machine got aborted by virtualbox. it also gave a memory read error. I think the reason why it gave that error is because virtualbox is not checking if what the user drags inside of the virtual machine is a file or directory so it tries to read it then because it is not a file it gives a read error. So i would suggest you guys let virtualbox check if what the user drags inside the virtual machine is a file or directory.
So i would like to report this issue to help improve virtualbox.
If i could contribute through code it would a dream.",MemoryJack
20419,NAT Port Forwarding CONN RESET ISSUES,Windows,VirtualBox 6.1.22,2021-06-16T17:42:24Z,2021-06-19T04:56:49Z,2021-06-19T04:56:49Z,"Trying to port forward port 10000-10002 between the 
windows 10 pro host OS
windows 10 enterprise guest OS

on those ports the guest contains the microsoft azure storage emulator endpoints.

I am trying to make REST API call to those endpoints from the host OS will no sucess.

So far, I have turned off the windows defender firewall in the Guest OS  and allowed for the TCP,UDP inbound outbound connections on the HOST OS. I also upgraded my VM FROM 6.1.18-142142 TO 6.1.22-144080.This happend for browser, web app API, python and C#. We know this is the case becuase the API call to MySQL on guest 3306 works sucesfully and on turning off the guest OS, the failed call indicated the MySQL server was only on the guest

The results were from a HTTP Requests that hangs to a requests that respond ""CONNECTION RESET"", this happend on both versions of virtual box
",windmillcode
20406,Mouse integration missing,Windows,VirtualBox 6.1.22,2021-06-15T19:57:49Z,2021-06-15T19:57:49Z,2021-06-15T19:57:49Z,"After update to 6.1.22, the mouse click sometimes not workin proprealy, so i need to disable mouse integration to continuie using VM, current i'm running w10 vm in w10 host",Lmendes.cwb
20398,Error Guru Meditation,Windows,VirtualBox 6.1.22,2021-06-14T09:48:51Z,2021-06-14T09:48:51Z,2021-06-14T09:48:51Z,Al intentar cargar el sistema operativo de una nueva máquina virtual me ha dado el mensaje Guru Meditation y no puedo instalarla,Alfonsodearagon
20395,Centos 7 i386 causes serious malfunctions when booted with ncpus>1,Linux,VirtualBox 6.1.22,2021-06-11T10:34:08Z,2021-06-11T10:34:08Z,2021-06-11T10:34:08Z,"I had occasion to try testing something on CentOS 7 i386. So I fetched CentOS-7-i386-NetInstall-2009.iso, and tried booting it on my Win10 host running VB 6.1.22, and strange behavior ensued. So I tried a premade 7 2009 image, which did the same, and a premade 7 2003 image, which did either the same thing or aborted.

First, it flooded with BUG: Bad page state in process swapper. Then, after a bit, the strangest behavior ensued - it started pegging multiple cores on the host, attempting to do anything with the VM window or other VB windows became infeasible (I needed to use Task Manager to kill the VM ultimately, the times it didn't abort and crash on its own) and my Caps Lock light started oscillating furiously, which continues even if it ultimately gets into the graphical login screen.

Running with n=1 cores, it seems to work fine.

Since Debian buster i386 works fine on this host, it's not impossible for it to be a flaw in what CentOS 7 is doing, but if it works on real hardware, then not working in a VM still seems like a flaw in the VM?",rincebrain
20394,Settings issue,Linux,VirtualBox 6.1.22,2021-06-11T04:38:12Z,2021-06-11T04:38:12Z,2021-06-11T04:38:12Z,"I cant change the VM´s settings, and i cant run it because a AMD-V setting ",Xion18502
20391,"With Windows host,Bridged Adapter Oracle VirtualBox (6.1) doesn't work if the VM Opterating system is Ubuntu 16.04",Linux,VirtualBox 6.1.22,2021-06-09T22:57:39Z,2021-06-09T22:57:39Z,2021-06-09T22:57:39Z,"Here is an outline of the problem:

Parameters:
•	I’m using Windows 7
•	I’m using Oracle VirtualBox 6.1
•	I’m running Ubuntu 16.04 on Oracle VirtualBox VM’s

Outline of the Problem:

•	Can’t connect to the internet if I select “Bridged Adapter” in 
        the Networking Options of an Oracle VirtualBox VM.
•	Can connect to the Internet via the NAT Adapter.
•	When I try to communicate between Oracle VirtualBox VM’s via 
        the Bridged Adapter, I get the error message “Host not Found.
",intelidrift
20389,VBoxSharedClipboardClass-17032: VirtualBoxVM.exe - Application Error,Linux,VirtualBox 6.1.22,2021-06-07T23:10:51Z,2021-06-07T23:10:51Z,2021-06-07T23:10:51Z,"VirtualBox 6.1.22 r144080
Host:  Windows 10 (2004 - 19041.1023)
Guest: Ubuntu 21.10

Copying into clipboard from host caused:

{{{
---------------------------
VBoxSharedClipboardClass-17032: VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFC9EBC2B32 referenced memory at 0x0000000000000000. The memory could not be written.

}}}


Only one guest running at the time, remained responsive but without shared clipboard functionality.  Clicking OK caused immediate close of the guest.  Logs attached.

Has been working solidly until recently.",gkcgareth
20388,VM aborted while saving state,Linux,VirtualBox 6.1.22,2021-06-05T10:43:51Z,2021-06-05T10:43:51Z,2021-06-05T10:43:51Z,"I tried to save the state of the VM by selecting File → Close from the popup menu (invoked via a custom Host key shortcut) and, with the “Save state” radio button selected, pressing OK. At first, the VM seemed to save normally, but then the save process appeared to stop prematurely and the VirtualBox interface showed the VM state as “Aborted”.

This occurred after upgrading VirtualBox from 6.0.24 to 6.1.22. Before the incident, the VM had been running for several days and, if I recall correctly, was successfully saved and restored once, and also paused and resumed once.",mgrzegor
20385,VirtualBox crashes by accessing 0xFFFFFFFFFFFFFFFF when USB dongle is unplugged/plugged.,Linux,VirtualBox 6.1.22,2021-06-03T04:19:48Z,2021-06-03T04:29:34Z,2021-06-03T04:29:34Z,"I am using virtualbox 6.1.22: 6.1.22 r144080 (Qt5.6.2) to be exact.
Host is Windows 10 Pro 64-bit., 20H2, OS build is 19042.985
Guest is Debian GNU/Linux, 5.10.0-4-amd64 

I have a USB Wi-Fi dongle NEC Aterm WL300NU-AG adaptor.
This works fine under Windows 10.

I tried to use this dongle from within linux to test my Wi-Fi devices at home against fragattacks (recently found Wi-Fi vulnerability).
So I removed the driver under Windows 10 for this USB. 
(It is plugged and no messing from Windoes 10 itself without the driver, I suppose.)
I intend to use the dongle via the native linux driver.

Under guest linux, I could somehow make the dongle recognized initially,
and eventually was able to assign IP address to it (manually, not by DHCP) and ping the interface address from other PCs via Wi-Fi. 
So experimentally it works, but the device went off-line unexpectedly.
The driver seems to have a known issue.
In order to reset the device, I tried unplugging and plugging it a few times. 
Then VBox crashed saying it accessed 0xFFFFFFFFFFFFFFFF address. 
(Actually I did this a lot initially, but at that time VBox did not crash.)

Alright, I saved a log. (The experiment took a couple of hours).

Now, I rebooted the guest linux by restarting VBox and see if I can continue testing the dongle. Nope.
The device was not visible from within guest linux using lsusb anymore(?!).
So I tried unplugging and unplugging only a couple of times when I get the same address violation and VBox crashed. This time I got the capture on the screen to show the address. 

I think there is a problem with USB handling.
I am attaching the first log (crash that occurred after a couple of hours testing. Actually, it was at the tail end of a very long session.)
and the second log along with the screen dump.

",ci-zephyurus
20378,Virtualbox Extension makes Windows Startmenue unusable,Windows,VirtualBox 6.1.22,2021-05-25T09:46:30Z,2021-05-25T09:46:30Z,2021-05-25T09:46:30Z,When I install the Guest Additions the Windows Start Menue stopps working correct,Temaktor
20376,USB Moxa UPort1150l device cannot start Code 10,Windows,VirtualBox 6.1.22,2021-05-24T11:44:18Z,2021-05-24T11:44:18Z,2021-05-24T11:44:18Z,"Hello!

'''Hardware and hosts:[[BR]]'''

Dell Precision 7520 Windows 10 company based 20H2 (year ago some older version)[[BR]]

Virtual Windows 7 - all updates[[BR]]


I have found that about a year ago my Uport was working fine with Win7. After a update VM and extensions it stopped working. Now I have tested also this with new fresh Win7 installation and same problem exist.

In device manager the device status is ""This device cannot start. (Code 10)"". If I try to use some other driver from Moxa like Uport 1150 then result is same.",Vahelduvool
20356,Mouse integration click focus gets lost when using (Ultra)vncviewer client inside Windows 10 guest,Windows,VirtualBox 6.1.22,2021-05-10T14:41:10Z,2021-05-10T14:41:10Z,2021-05-10T14:41:10Z,"I often experience issues with the mouse integration focus getting partially lost inside my Windows 10 guest (running on my windows 10 host) , meaning: i can hove above windows and buttons and you see them respond to the hovering, but clicking the button or area does not get through.

I notice this usually when i have been or am using the Ultravnc viewer inside the the guest client. It seems to disorient mouse capturing features.

To resolve this, i have to click the mouseintegration button on the lower right and then disable the automatic integration, then manually click the Windows 10 guest and confirm catching the mouse. After confirmation, the system is then responding to mouse clicks (right and left).

The behavior turned up since updating to 6.1.22, i did not had any issues like this with my former version (6.1.18!)",lbsl
20352,[Guest - windows 7] Cannot detect Qualcomm MMC Storage USB device,other,VirtualBox 6.1.22,2021-05-09T22:30:33Z,2021-05-09T22:30:33Z,2021-05-09T22:30:33Z,"*This is a CRITICAL issue related to Android embeded development on Windows guest machine;[[BR]]
Universal Qualcomm USB Driver: [https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/] [[BR]]
Steps to reproduce:
1. Access Edl mode on a Qualcomm-insided Android device (by ADB, test point on board, etc ...) [[BR]]
2. Open Device management on Windows guest OS and check detected usb passthrought devices; [[BR]]
Results:
1. Only host machine detects successfully Qualcomm MMC USB Storage device, we can check in Disk Management programme, it shows all related partitions on on-board MMC storage; [[BR]]
2. Guest machine can NOT detect Qualcomm MMC USB Storage device and all related MMC partitions; [[BR]]

Expectations:
The guest machine should detects Qualcomm MMC USB Storage device and all related MMC partitions [[BR]]

Screenshots: [https://drive.google.com/drive/folders/1MKIm7xnrIDJ0BfPKRLfOJzZmK3z61DGk?usp=sharing]
References:
1. https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ [Adb commandline approach]
2. http://andrux-and-me.blogspot.com/2015/09/bringing-lg-g2-back-from-dead.html [Onboard test point approach]
Thanks team,",Kelvin
20347,The error message appear when the virual machine shut down,Windows,VirtualBox 6.1.22,2021-05-08T06:14:02Z,2021-05-08T06:14:02Z,2021-05-08T06:14:02Z,"It always show error message ""The instruction at 0x00007FFE199F9B2C referenced memory. The memory could not be written."" I try to reinstall the application, but didn't work. I use portable usb to store most of vm and ISO files. I think it wouldn't a problem for the vm, but I am not sure what happened. I hope your teams can look at this problem, I would very appreciate if you could solve this problem I currently facing with. Thank you and have a great day",jetAngel
20343,instruction 0x00007FFD15769B2C,other,VirtualBox 6.1.22,2021-05-07T22:14:50Z,2021-05-07T22:14:50Z,2021-05-07T22:14:50Z,"Hello everybody

I am new with Virtualbox. I have downloaded the latest version of virtualBox and install and configure the latest lubuntu but finally when I exit of lubuntu an error message appears ""The instruction 0x00007FFD15769B2C do reference to the memory in 0windows and updatx00007FFD15769B2C. The memory can not written""
I have the latest windows version and also I updated all actualizations, but the error apperas again.
I have an hp laptop i7 11 generation with windows 10 home, i have the virtualization enabled but the problem continues

Van somebody help me with this error?

Best reagrds
Jose

  ",yuse
20341,"HARDENING fails to verify DLLs on Windows for non-interactive, restricted user",all,VirtualBox 6.1.22,2021-05-05T17:22:26Z,2021-05-06T07:26:09Z,2021-05-06T07:26:09Z,"== Background ==

I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

{{{
VBoxManage startvm ""[...]"" --type headless
}}}

== HARDENING prevents necessary functionality ==

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason is HARDENING, which simply refuses to load necessary and otherwise legitimate Windows-DLLs, resulting in errors like the following. Things heavily depend on the configured VM and the purpose of loading some DLLs, the following error is from a VM using bridged networking.

{{{
supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
NetworkAttachmentType_Bridged: Failed to get NetCfg, hrc=ERROR_TRUST_FAILURE 0x800706FE (0x800706fe)
AssertLogRel F:\tinderbox\win-6.1\src\VBox\Main\src-client\ConsoleImpl2.cpp(5376) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): !FAILED(hrc)
hrc=ERROR_TRUST_FAILURE 0x800706FE
Constructor failed with rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR pfnCFGMConstructor=00007ffc15bd1e60
VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(318) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *),void *,int (__cdecl *)(struct UVM *,struct VM *,void *),void *,struct VM **,struct UVM **); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR
VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details.
ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400
Console: Machine state changed to 'PoweredOff'
Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=E_FAIL (0X80004005))
}}}

== HARDENING fails signature verification ==

While changing bridged networking to NAT makes the VM start, I simply have use cases which require a bridged network and one can't be sure anyway. The problem in all of those cases still is HARDENING not being able to verify some DLLs, which can be seen more detailed in the following logs:

{{{
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffc74d20000 'C:\windows\system32\rsaenh.dll'
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000808 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019ef030
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019eef70
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: New context 00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=00000000019efab0
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=32 wszDigest=668C2310EFB19B6732352E1B4C6B047E3037FC14D9878DA0CC690CFA6D37CE20
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
supR3HardNtViCallWinVerifyTrustCatFile -> -22900 (org 22900)
supHardenedWinVerifyImageByHandle: -> -22900 (\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll) WinVerifyTrust
Error (rc=0):
supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll: Not signed.
supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
Error (rc=0):
supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\NetSetupShim.dll' (C:\Windows\System32\NetSetupShim.dll): rcNt=0xc0000190
supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\System32\NetSetupShim.dll'
supR3HardenedDllNotificationCallback: Unload 00007ffc2aa90000 LB 0x000ef000 C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc77240000 LB 0x00052000 C:\windows\System32\SHLWAPI.dll [flags=0x0]
supR3HardenedDllNotificationCallback: Unload 00007ffc15f60000 LB 0x003c0000 C:\Program Files\Oracle\VirtualBox\VBoxC.dll [flags=0x0]
Terminating the normal way: rcExit=0
supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1448 ms, the end);
supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1921 ms, the end);
}}}

The following is the relevant code:

{{{
/* Get the next match. */
HCATINFO hCatInfo = g_pfnCryptCATAdminEnumCatalogFromHash(hCatAdmin, abHash, cbHash, 0, &hCatInfoPrev);
if (!hCatInfo)
{
    if (!fFreshContext)
    {
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> %u; iCat=%#x)\n"", RtlGetLastWin32Error(), iCat));
        if (hCatInfoPrev != NULL)
            g_pfnCryptCATAdminReleaseCatalogContext(hCatAdmin, hCatInfoPrev, 0 /*dwFlags*/);
        g_pfnCryptCATAdminReleaseContext(hCatAdmin, 0 /*dwFlags*/);
        goto l_fresh_context;
    }
    ULONG ulErr = RtlGetLastWin32Error();
    fNoSignedCatalogFound = ulErr == ERROR_NOT_FOUND && fNoSignedCatalogFound != 0;
    if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (%u)\n"", ulErr));
    else if (iCat == 0)
        SUP_DPRINTF((""supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed %u\n"", ulErr));
    break;
}
}}}

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/Support/win/SUPHardenedVerifyImage-win.cpp#L2703

== Comparing verification results ==

The following is how a successful verification of that same file looks like. Specially look at ""cbHash"" and ""wszDigest"", which seems to be the exact same values like for the first attempt in the former logs. So if this verification succeeds, the catalogs contain the necessary data and the state of the DLL is obviously OK.

{{{
supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000930 pwszName=\Device\HarddiskVolume4\Windows\System32\NetSetupShim.dll
supR3HardNtViCallWinVerifyTrustCatFile: Cached context 0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: hCatAdmin=0000000001433810
supR3HardNtViCallWinVerifyTrustCatFile: cbHash=20 wszDigest=592E7D18568150098B2F131AD72F2156D1CA3A58
}}}

The following lines are of additional interest because they seem to contain some error code of Windows:

{{{
supR3HardNtViCallWinVerifyTrustCatFile: Retrying with fresh context (CryptCATAdminEnumCatalogFromHash -> 1062; iCat=0x0)
supR3HardNtViCallWinVerifyTrustCatFile: CryptCATAdminEnumCatalogFromHash failed ERROR_NOT_FOUND (1062)
}}}

Which might the following:

{{{
ERROR_SERVICE_NOT_ACTIVE
1062 (0x426)
The service has not been started.
}}}

https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1000-1299-

== dberr.txt ==

A corresponding error code is logged to the file ""C:\Windows\System32\catroot2\dberr.txt"" after adjusting its permissions to allow my executing restricted default user to write to it. For some reason this is not the default, but doesn't make any difference for signature checking itself. These lines repeat multiple times, most like for each attempt to check the signature for each DLL of interest.

{{{
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: waitsvc.cpp at line #352 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #345 encountered error 0x00000005
CatalogDB: 12:29:34 03.05.2021: catdbcli.cpp at line #590 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #2479 encountered error 0x00000426
CatalogDB: 12:29:34 03.05.2021: catadnew.cpp at line #939 encountered error 0x00000426
}}}

== Educated guess: COM permissions problem again? ==

So here's what I think is going on: This signature verification relies on some COM-component again and default security settings of those only allow SYSTEM, ADMINISTRATORS and INTERACTIVE to activate those. I have documented that in the related ticket #20340 already. When using task scheduler with my restricted user it's no member of any of these groups, therefore necessary components are not activated and signature can't be checked. This changes instantly when using the same command line etc. with the same user with an interactive shell.

While that could be argued as a limitation of Windows default settings, the problem in my opinion in this case is that HARDENING is requiring that signature verification, not Windows, while without it things would simply work. So to make HARDENING succeed in this case, I would need to make my restricted user being a member of ADMINISTRATORS, which obviously doesn't make too much sense from a security perspective: Providing far more permissions than absolutely necessary to make an additional security(!) check succeed first. :-)

Like discussed in #20340, this might be worked around by creating an additional group and providing necessary permissions on the COM component of interest to that group. The problem is that I couldn't find the exact component yet... :-/

https://stackoverflow.com/questions/67331016/why-does-cryptcatadminenumcatalogfromhash-return-error-not-found-1062-for-n

https://docs.microsoft.com/en-us/answers/questions/378892/why-does-34cryptcatadminenumcatalogfromhash34-retu.html

Another workaround would be to make HARDENING optionally being disabled, it harms in this case, or at least make it more tolerant and ignore some of those errors under some circumstances. As said, the mentioned DLLs are all Windows default DLLs, unchanged, which otherwise easily pass signature verification.",Thorsten Schöning
20340,Headless mode on Windows requires too high permissions because of COM security,all,VirtualBox 6.1.22,2021-05-05T16:36:07Z,2021-05-05T16:36:07Z,2021-05-05T16:36:07Z,"I need to automatically run VMs headless WITHOUT any interactive user login after Windows booted. The started VMs should additionally run somewhat secure using a default, restricted non-admin user of Windows. This seems like exactly the setup recommended on non-Windows and am I using with Ubuntu 16.04 and phpVirtualBox currently. In theory this should easily be possible by creating a standard user in Windows and a task in the task scheduler to execute a VM headless using that user and e.g. the following command line:

> VBoxManage startvm ""[...]"" --type headless

While that works using an interactive login on the shell, it didn't work by default using task scheduler. The reason can be found in the event viewer of Windows:

> Durch die Berechtigungseinstellungen für ""Anwendungsspezifisch"" wird
> dem Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F}
> und der APPID
> {819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

> Durch die Berechtigungseinstellungen für ""Computerstandard"" wird dem
> Benutzer ""TEPU\virtual_box"" (SID:
> S-1-5-21-3056241376-1506544733-1187908793-1167) unter der Adresse
> ""LocalHost (unter Verwendung von LRPC)"" keine Berechtigung vom Typ
> ""Lokal Aktivierung"" für die COM-Serveranwendung mit der CLSID
> {74AB5FFE-8726-4435-AA7E-876D705BCBA5}
> und der APPID
> {EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
> im Anwendungscontainer ""Nicht verfügbar"" (SID: Nicht verfügbar)
> gewährt. Die Sicherheitsberechtigung kann mit dem Verwaltungstool
> für Komponentendienste geändert werden.

Virtual Box installs COM servers which by default can only be started by the groups SYSTEM, ADMINISTRATOR or INTERACTIVE. My created user isn't any member of those groups when used by the task scheduler, but when logging in interactively and using the shell.

{{{
VirtualBox Application
{819B4D85-9CEE-493C-B6FC-64FFE759B3C9}
}}}

{{{
VirtualBox System Service
{EC0E78E8-FA43-43E8-AC0A-02C784C4A4FA}
VBoxSDS
}}}

The security settings to start the necessary COM servers can be changed to include my created user with the necessary permissions and afterwards VBoxManage starts successfully and the COM-related error entries in the event viewer are gone. 

* https://ibb.co/6ysd4FZ
* https://ibb.co/DDsNzKW
* https://ibb.co/MZhwx7n
* https://ibb.co/ctrR7cp

As you already have an installer bringing services, device drivers etc. into the system, you could as well adjust security for those COM servers. Some other software simply creates a group for their own purposes, assigning the necessary permissions and document somewhere that users like the one created by me simply need to be a member of that group. That approach is pretty common, e.g. VMware and OpenVPN create custom groups for special maintenance as well.

I'm considering this a defect instead of an enhancement, because using users with least possible privileges is a recommended security practice and because COM isn't used on non-Windows, that approach works on other platforms. After fixing or working around this problem, VBox will be easier to use with the same concepts and good practices across more OS.

Thanks!",Thorsten Schöning
20336,Windows 10 guest - VirtualBox Graphics Adapter - Windows has stopped this device.,Windows,VirtualBox 6.1.22,2021-05-03T17:04:43Z,2021-05-03T17:04:43Z,2021-05-03T17:04:43Z,"Hi,
I've been using VirtualBox since a long time.
I'm using VirtualBox 6.1.22.
Now when I've 3D Acceleration enabled in my Windows 10 VM, Device Manager in Windows 10 reports VirtualBox Graphics Adapter - Windows has stopped this device as it has reported problems.
But when 3D Acceleration is disabled it works fine but the display is glitchy.

My specs:
Host:Windows 10 Home Single Language
CPU:Intel Core i5 10210U 2.11 Ghz
Intel UHD Graphics 620
NVIDIA GeForce MX230 2GB GDDR5(Dedicated Graphics)",asrar.sunge198
21007,Linux Guest / No Audio in VBox >= 6.1.24,Linux,VirtualBox 6.1.24,2022-06-24T15:12:55Z,2022-06-24T15:12:55Z,2022-06-24T15:12:55Z,"When using VirtualBox >= 6.1.24 (Windows 10 host, Linux Mint Mate 20.2 guest), audio output does not work. It works with VirtualBox <= 6.1.22.

Audio players, video players, browsers, all seemingly work as intended (e.g., video is shown), just no sound.

I tried the following fix: added the line ""options snd-intel8x0 ac97_clock=48000"" to the file ""/etc/modprobe.d/alsa-base.conf"" .

This brought partial improvements: Video is now played with sound -- no matter whether from the internet or my own local .mp4 files. The test ""aplay /usr/share/sounds/alsa/Front_Center.wav"" works. However, my own .mp3 and .wav files, ripped from CD, still don't produce any output.

I also noticed that when I do ""aplay /usr/share/sounds/alsa/Front_Center.wav"" and immediately interrupt it with ctrl-z, audio output ''does'' work. So it seems this aplay provides some initializations that normally are missing.


Attached two log files: One before applying the above-mentioned fix, one after. There are Audio errors in there; however, I have no idea what can be done about them.",aabb
20474,[vmwgfx]] *ERROR* Failed to open channel,Linux,VirtualBox 6.1.24,2021-07-24T10:35:44Z,2022-03-06T08:22:30Z,2022-03-06T08:22:30Z,"I am running VirtualBox 6.1.24 on Win10 x64, Hyper-V is paravirtualization interface. Ubuntu 20.04 is guest OS.VM is configured to use VMSVGA with 3D enabled.

During boot up, dmesg log has many following records:

[  107.916494] 10:21:10.493550 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
               10:21:10.493575 main     Log opened 2021-07-24T10:21:10.493522000Z
[  107.916494] 10:21:10.493713 main     OS Product: Linux
[  107.916494] 10:21:10.493841 main     OS Release: 5.8.0-63-generic
[  107.916494] 10:21:10.493933 main     OS Version: #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021
[  107.916494] 10:21:10.494012 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
               10:21:10.494034 main     Process ID: 1337
               10:21:10.494057 main     Package type: LINUX_64BITS_GENERIC
[  107.920318] 10:21:10.501490 main     6.1.24 r145751 started. Verbose level = 0
[  107.927561] 10:21:10.508214 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.152249] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  121.193173] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  133.960208] rfkill: input handler disabled
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  134.204342] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  137.828211] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  174.892246] rfkill: input handler enabled
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  177.579907] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.140558] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  178.292236] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  183.200987] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  184.596248] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.
[  186.692221] [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.


Detailed logs are attached.",tysonite
20467,Guest freeze after restoring from saved state,Linux,VirtualBox 6.1.24,2021-07-21T21:20:46Z,2021-09-08T00:29:58Z,2021-09-08T00:29:58Z,"Saved guest state, left it alone over night.  Resumed from saved state the next morning, guest ran for a few minutes then froze.  Required power off to recover.

Version 6.1.22

00:00:41.067179 TM: cTSCTicksPerSecond=0x7de2930c (2 112 000 780) enmTSCMode=1 (VirtTscEmulated) (state load)
00:00:41.067225 GIM: KVM: VCPU  0: Enabled system-time struct. at 0x0000000070e01000 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x3e6641e77 uVirtNanoTS=0x1d8b90e9e TscKHz=2112000
00:00:41.067391 TM: Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
00:00:41.067504 GIM: KVM: VCPU  1: Enabled system-time struct. at 0x0000000070e01040 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44d7575f1 uVirtNanoTS=0x209861cac TscKHz=2112000
00:00:41.067524 GIM: KVM: VCPU  2: Enabled system-time struct. at 0x0000000070e01080 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44ddad072 uVirtNanoTS=0x209b619f2 TscKHz=2112000
00:00:41.067536 GIM: KVM: VCPU  3: Enabled system-time struct. at 0x0000000070e010c0 - u32TscScale=0xf26c9548 i8TscShift=-1 uVersion=2 fFlags=0x1 uTsc=0x44e3dffac uVirtNanoTS=0x209e5104d TscKHz=2112000
00:00:41.067695 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0) (restore)
00:00:41.067710 RTC: Stopped the periodic timer (restore)
00:00:41.067746 HGCM: Restoring [VBoxGuestPropSvc]
00:00:41.068417 HGCM: Restoring [VBoxGuestControlSvc]
00:00:41.068625 HGCM: Restoring [VBoxSharedFolders]
00:00:41.069102 HGCM: Restoring [VBoxDragAndDropSvc]
00:00:41.069378 HGCM: Restoring [VBoxSharedClipboard]
00:00:41.069740 Shared Clipboard: New Clipboard API enabled
00:00:41.073974 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (Linux >= 2.6, 64-bit)
00:00:41.074187 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:00:41.074218 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.074239 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074248 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074260 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
00:00:41.074269 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.074279 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074287 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074319 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074328 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.074339 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
00:00:41.074347 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=13
00:00:41.075353 E1000#0: Interrupt attempts: 0
00:00:41.075369 E1000#0: Interrupts raised : 0
00:00:41.075377 E1000#0: Interrupts lowered: 0
00:00:41.075384 E1000#0: ICR outside ISR   : 0
00:00:41.075391 E1000#0: IMS raised ints   : 0
00:00:41.075398 E1000#0: Interrupts skipped: 0
00:00:41.075405 E1000#0: Masked interrupts : 0
00:00:41.075412 E1000#0: Early interrupts  : 0
00:00:41.075419 E1000#0: Late interrupts   : 0
00:00:41.075426 E1000#0: Lost interrupts   : 0
00:00:41.075432 E1000#0: Interrupts by RX  : 0
00:00:41.075439 E1000#0: Interrupts by TX  : 0
00:00:41.075446 E1000#0: Interrupts by ICS : 0
00:00:41.075453 E1000#0: Interrupts by RDTR: 0
00:00:41.075460 E1000#0: Interrupts by RDMT: 0
00:00:41.075467 E1000#0: Interrupts by TXQE: 0
00:00:41.075474 E1000#0: TX int delay asked: 0
00:00:41.075481 E1000#0: TX delayed:         0
00:00:41.075488 E1000#0: TX delay expired:   0
00:00:41.075495 E1000#0: TX no report asked: 0
00:00:41.075502 E1000#0: TX abs timer expd : 0
00:00:41.075509 E1000#0: TX int timer expd : 0
00:00:41.075516 E1000#0: RX abs timer expd : 0
00:00:41.075523 E1000#0: RX int timer expd : 0
00:00:41.075530 E1000#0: TX CTX descriptors: 0
00:00:41.075536 E1000#0: TX DAT descriptors: 0
00:00:41.075543 E1000#0: TX LEG descriptors: 0
00:00:41.075550 E1000#0: Received frames   : 0
00:00:41.075557 E1000#0: Transmitted frames: 0
00:00:41.075564 E1000#0: TX frames up to 1514: 0
00:00:41.075577 E1000#0: TX frames up to 2962: 0
00:00:41.075586 E1000#0: TX frames up to 4410: 0
00:00:41.075593 E1000#0: TX frames up to 5858: 0
00:00:41.075600 E1000#0: TX frames up to 7306: 0
00:00:41.075607 E1000#0: TX frames up to 8754: 0
00:00:41.075614 E1000#0: TX frames up to 16384: 0
00:00:41.075621 E1000#0: TX frames up to 32768: 0
00:00:41.075628 E1000#0: Larger TX frames    : 0
00:00:41.075635 E1000#0: Max TX Delay        : 0
00:00:41.075646 E1000#1: Interrupt attempts: 0
00:00:41.075653 E1000#1: Interrupts raised : 0
00:00:41.075660 E1000#1: Interrupts lowered: 0
00:00:41.075667 E1000#1: ICR outside ISR   : 0
00:00:41.075674 E1000#1: IMS raised ints   : 0
00:00:41.075681 E1000#1: Interrupts skipped: 0
00:00:41.075688 E1000#1: Masked interrupts : 0
00:00:41.075694 E1000#1: Early interrupts  : 0
00:00:41.075701 E1000#1: Late interrupts   : 0
00:00:41.075708 E1000#1: Lost interrupts   : 0
00:00:41.075715 E1000#1: Interrupts by RX  : 0
00:00:41.075722 E1000#1: Interrupts by TX  : 0
00:00:41.075729 E1000#1: Interrupts by ICS : 0
00:00:41.075736 E1000#1: Interrupts by RDTR: 0
00:00:41.075743 E1000#1: Interrupts by RDMT: 0
00:00:41.075749 E1000#1: Interrupts by TXQE: 0
00:00:41.075756 E1000#1: TX int delay asked: 0
00:00:41.075763 E1000#1: TX delayed:         0
00:00:41.075770 E1000#1: TX delay expired:   0
00:00:41.075777 E1000#1: TX no report asked: 0
00:00:41.075784 E1000#1: TX abs timer expd : 0
00:00:41.075790 E1000#1: TX int timer expd : 0
00:00:41.075797 E1000#1: RX abs timer expd : 0
00:00:41.075804 E1000#1: RX int timer expd : 0
00:00:41.075811 E1000#1: TX CTX descriptors: 0
00:00:41.075818 E1000#1: TX DAT descriptors: 0
00:00:41.075825 E1000#1: TX LEG descriptors: 0
00:00:41.075831 E1000#1: Received frames   : 0
00:00:41.075838 E1000#1: Transmitted frames: 0
00:00:41.075845 E1000#1: TX frames up to 1514: 0
00:00:41.075852 E1000#1: TX frames up to 2962: 0
00:00:41.075859 E1000#1: TX frames up to 4410: 0
00:00:41.075866 E1000#1: TX frames up to 5858: 0
00:00:41.075873 E1000#1: TX frames up to 7306: 0
00:00:41.075879 E1000#1: TX frames up to 8754: 0
00:00:41.075886 E1000#1: TX frames up to 16384: 0
00:00:41.075893 E1000#1: TX frames up to 32768: 0
00:00:41.075900 E1000#1: Larger TX frames    : 0
00:00:41.075907 E1000#1: Max TX Delay        : 0
00:00:41.075917 E1000#2: Interrupt attempts: 0
00:00:41.075924 E1000#2: Interrupts raised : 0
00:00:41.075931 E1000#2: Interrupts lowered: 0
00:00:41.075938 E1000#2: ICR outside ISR   : 0
00:00:41.075945 E1000#2: IMS raised ints   : 0
00:00:41.075952 E1000#2: Interrupts skipped: 0
00:00:41.075959 E1000#2: Masked interrupts : 0
00:00:41.075966 E1000#2: Early interrupts  : 0
00:00:41.075972 E1000#2: Late interrupts   : 0
00:00:41.075979 E1000#2: Lost interrupts   : 0
00:00:41.075986 E1000#2: Interrupts by RX  : 0
00:00:41.075993 E1000#2: Interrupts by TX  : 0
00:00:41.076000 E1000#2: Interrupts by ICS : 0
00:00:41.076007 E1000#2: Interrupts by RDTR: 0
00:00:41.076013 E1000#2: Interrupts by RDMT: 0
00:00:41.076020 E1000#2: Interrupts by TXQE: 0
00:00:41.076027 E1000#2: TX int delay asked: 0
00:00:41.076034 E1000#2: TX delayed:         0
00:00:41.076041 E1000#2: TX delay expired:   0
00:00:41.076047 E1000#2: TX no report asked: 0
00:00:41.076054 E1000#2: TX abs timer expd : 0
00:00:41.076061 E1000#2: TX int timer expd : 0
00:00:41.076068 E1000#2: RX abs timer expd : 0
00:00:41.076075 E1000#2: RX int timer expd : 0
00:00:41.076081 E1000#2: TX CTX descriptors: 0
00:00:41.076088 E1000#2: TX DAT descriptors: 0
00:00:41.076095 E1000#2: TX LEG descriptors: 0
00:00:41.076102 E1000#2: Received frames   : 0
00:00:41.076109 E1000#2: Transmitted frames: 0
00:00:41.076116 E1000#2: TX frames up to 1514: 0
00:00:41.076122 E1000#2: TX frames up to 2962: 0
00:00:41.076129 E1000#2: TX frames up to 4410: 0
00:00:41.076136 E1000#2: TX frames up to 5858: 0
00:00:41.076143 E1000#2: TX frames up to 7306: 0
00:00:41.076150 E1000#2: TX frames up to 8754: 0
00:00:41.076157 E1000#2: TX frames up to 16384: 0
00:00:41.076165 E1000#2: TX frames up to 32768: 0
00:00:41.076172 E1000#2: Larger TX frames    : 0
00:00:41.076179 E1000#2: Max TX Delay        : 0
00:00:41.076189 E1000#3: Interrupt attempts: 0
00:00:41.076197 E1000#3: Interrupts raised : 0
00:00:41.076204 E1000#3: Interrupts lowered: 0
00:00:41.076211 E1000#3: ICR outside ISR   : 0
00:00:41.076218 E1000#3: IMS raised ints   : 0
00:00:41.076225 E1000#3: Interrupts skipped: 0
00:00:41.076231 E1000#3: Masked interrupts : 0
00:00:41.076238 E1000#3: Early interrupts  : 0
00:00:41.076245 E1000#3: Late interrupts   : 0
00:00:41.076252 E1000#3: Lost interrupts   : 0
00:00:41.076259 E1000#3: Interrupts by RX  : 0
00:00:41.076283 E1000#3: Interrupts by TX  : 0
00:00:41.076290 E1000#3: Interrupts by ICS : 0
00:00:41.076297 E1000#3: Interrupts by RDTR: 0
00:00:41.076304 E1000#3: Interrupts by RDMT: 0
00:00:41.076311 E1000#3: Interrupts by TXQE: 0
00:00:41.076318 E1000#3: TX int delay asked: 0
00:00:41.076325 E1000#3: TX delayed:         0
00:00:41.076332 E1000#3: TX delay expired:   0
00:00:41.076339 E1000#3: TX no report asked: 0
00:00:41.076346 E1000#3: TX abs timer expd : 0
00:00:41.076352 E1000#3: TX int timer expd : 0
00:00:41.076359 E1000#3: RX abs timer expd : 0
00:00:41.076366 E1000#3: RX int timer expd : 0
00:00:41.076373 E1000#3: TX CTX descriptors: 0
00:00:41.076380 E1000#3: TX DAT descriptors: 0
00:00:41.076387 E1000#3: TX LEG descriptors: 0
00:00:41.076394 E1000#3: Received frames   : 0
00:00:41.076401 E1000#3: Transmitted frames: 0
00:00:41.076408 E1000#3: TX frames up to 1514: 0
00:00:41.076414 E1000#3: TX frames up to 2962: 0
00:00:41.076421 E1000#3: TX frames up to 4410: 0
00:00:41.076428 E1000#3: TX frames up to 5858: 0
00:00:41.076435 E1000#3: TX frames up to 7306: 0
00:00:41.076442 E1000#3: TX frames up to 8754: 0
00:00:41.076449 E1000#3: TX frames up to 16384: 0
00:00:41.076456 E1000#3: TX frames up to 32768: 0
00:00:41.076462 E1000#3: Larger TX frames    : 0
00:00:41.076469 E1000#3: Max TX Delay        : 0
00:00:41.077169 Changing the VM state from 'LOADING' to 'SUSPENDED'
00:00:41.077264 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:41.077634 NAT: Link down
00:00:41.077688 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:41.077711 Console: Machine state changed to 'Running'
00:00:41.413451 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.468266 VMMDev: Guest Log: 05:23:50.740142 control  Session 0 is about to close ...
00:00:41.496511 VMMDev: Guest Log: 05:23:50.765559 control  Stopping all guest processes ...
00:00:41.520448 VMMDev: Guest Log: 05:23:50.785749 control  Closing all guest files ...
00:00:41.538332 VMMDev: Guest Log: 05:23:50.809370 control  vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:41.553963 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:00:41.562333 VMMDev: Guest Log: 19:58:06.188434 timesync vgsvcTimeSyncWorker: Radical host time change: 52 465 401 000 000ns (HostNow=1 626 897 486 173 000 000 ns HostLast=1 626 845 020 772 000 000 ns)
00:00:41.603543 VD#0: DEK is missing
00:00:41.605905 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)
00:00:41.606263 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:00:41.682916 PDMR3Suspend: 76 471 817 ns run time
00:00:41.682942 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:00:41.682963 Console: Machine state changed to 'Paused'
00:00:41.683147 Console: VM runtime error: fatal=false, errorID=DrvVD_DEKMISSING message=""VD: The DEK for this disk is missing""
00:00:41.901987 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
00:00:41.906646 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.914961 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:41.924632 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:41.932803 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:55.433857 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:00:55.437234 Changing the VM state from 'RESUMING' to 'RUNNING'
00:00:55.437266 Console: Machine state changed to 'Running'
00:00:55.437702 VUSB: Attached 'HidMouse' to port 1 on RootHub#1 (FullSpeed)
00:00:55.442756 GUI: 2D video acceleration is disabled
00:00:55.442897 GUI: HID LEDs sync is enabled
00:00:55.448377 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:55.454667 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:55.461637 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
00:00:56.250340 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000f820000 w=1920 h=1027 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0
00:00:58.156594 NAT: Link up
00:00:58.165917 NAT: DNS#0: 192.168.1.1
00:01:00.002777 NAT: IPv6 not supported
00:01:00.012749 NAT: DHCP offered IP address 10.0.4.15
00:01:05.442153 VMMDev: Guest Log: 19:58:16.316090 timesync vgsvcTimeSyncWorker: Radical guest time change: 52 465 497 062 000ns (GuestNow=1 626 897 496 316 076 000 ns GuestLast=1 626 845 030 819 014 000 ns fSetTimeLastLoop=true )
",gkcgareth
20524,VirtualBox crashes with FreeBSD guest,BSD,VirtualBox 6.1.24,2021-08-25T12:50:16Z,2021-09-06T20:17:55Z,2021-09-06T20:17:55Z,See attached log.,DeGarden
20505,Wrong System Time in OS/2 Guest,other,VirtualBox 6.1.24,2021-08-18T16:23:17Z,2021-08-18T16:23:17Z,2021-08-18T16:23:17Z,"There is a problem with the ""Guest Additions TimeSync Service"" for OS/2 when using the long format for the TZ environment variable on the guest like

TZ=MET-1DST,3,-1,0,7200,10,-1,0,10800,3600

I've posted a detailed description to the forum, please see [https://forums.virtualbox.org/viewtopic.php?f=4&t=103491 this thread].

The problem seems to be an issue in the underlying libc, see the replies from user LewisR in the same thread and especially [https://github.com/bitwiseworks/libc/issues/109 here] and [https://github.com/bitwiseworks/libc/issues/109#issuecomment-882764025 there].

A workaround is to start vboxservice.exe with the ""Guest Additions TimeSync Service"" disabled.

Probably the Guest Additons for OS/2 should be liked against a fixed version of libc once it gets available.


Thank you,

Michael
",mipri
20481,Working VM suddenly stop loading in GUI mode (F7) but working  in tty1 to tty6 mode,Linux,VirtualBox 6.1.24,2021-07-31T13:40:58Z,2021-08-02T12:33:23Z,2021-08-02T12:33:23Z,"Hi,
I ahve few(3) VMS based out of ubuntu 18.04(bionic) which were all functional from at least a year now. But yesterday, one of the 3 VM stops booting up in GUI mode(F7). It ends up ina blinking curson on the screen.
I can login into machine from tty1,ty2 to tty6 '''but not  getting anything on tty7 but a blinking cursor only'''.

Attaching vbox logs for someone to take a look urgently.

Note: I have checked some existing issues:
1. My host(windows 10) hypervisor is disabled.
2. I can  successfully run other 2 VMs
3. My VM has sufficient RAM/Space(from df and free output)
4. Virtualisation is enabled in BIOS settings.
5. Uptodate Vbox version and extension pack.
6. Done apt-get update  from tty1 and rebooted multiple times.
7. 3D acceleration is in disabled mode.

Please check my logs attached. ",vas
20478,Virtualbox locks up badly with fstrim on CentOS 8,Linux,VirtualBox 6.1.24,2021-07-28T16:57:33Z,2021-07-28T16:57:33Z,2021-07-28T16:57:33Z,"I tried using fstrim, with a VM presenting a virtio-scsi ""disk"", and it worked for a while (defined as ""the VDI file backing the FS shrinking on disk""), then eventually most IO hung indefinitely.

Most excitingly, SysRq-B resulted in the VM being stuck with its ""display"" showing a mix of black and occasional green boxes and not rebooting, then if I attempted to do anything to the VM (e.g. ""Reset"", ""Poweroff""), the window became unresponsive, and I had to force-close it, and VB reported ""Aborted"" for the VM status.

When I tried reproducing it just now for this ticket, it instead just blocked indefinitely in the OS - no errors reported, but fstrim wouldn't respond to ^C or kill -9, and trying to close the VM window hung and then reported Aborted.",rincebrain
20476,Interpret Host Key combination on keys up instead of down,Windows,VirtualBox 6.1.24,2021-07-24T22:30:16Z,2021-07-24T22:30:16Z,2021-07-24T22:30:16Z,"I'd like the guest OS to be able to see that Ctrl+Alt are down even though those keys are mapped as the Host Key combination.

Other virtualization software allows the key combination to be seen by the guest by not acting upon said combination until all keys in the combination return up, with no additional keys or mouse clicks preformed between the down/up events of those keys.

The reason for this request is spending an hour tracking down why Ctrl+Alt+Left-Click didn't perform the action I had mapped in Visual Studio. If the above request is not feasible, please consider providing some type of feedback to the user that something special is going on when pressing the Host Key, such as flashing the window or, if the status bar is visible, make the background for the Host Key combination flash a different color a couple times.",OkieDan
20473,Can't insall VirtualBox VM,Windows,VirtualBox 6.1.24,2021-07-24T01:50:05Z,2021-07-24T01:50:05Z,2021-07-24T01:50:05Z,"Hi,

I cant' seem to run the attached VM to VirtualBox, please help",Shawnloveshorses161
20472,Can't insall VirtualBox,Windows,VirtualBox 6.1.24,2021-07-23T20:13:48Z,2021-07-23T20:13:48Z,2021-07-23T20:13:48Z,"Hi :) 

I am on a Surface Pro 5 i5 4gbram, can't install VirtualBox on Windows 11. 

Did it on Windows 10 but not on 11.

It gives an error, Windows it can't run due to performance and it is basically this app can't run on this version of Windows.
",Shawnloveshorses161
20470,Enabled VB Host Only Network adapter causes Internet Connection Icon to show No Internet on Windows 10,other,VirtualBox 6.1.24,2021-07-23T08:26:45Z,2021-07-23T08:31:45Z,2021-07-23T08:31:45Z,"When having VirtualBox Host Only Network adapter enabled across reboots on Windows 10, the Internet Connection Icon soon (time varies somewhat) starts to show no internet connection even though the internet connection works correctly.

Took me some time to find out that the adapter was the cause for this problem. Now I always disable the adapter before rebooting.",loxia_01
20469,6.1.24 Memory can't be written,Windows,VirtualBox 6.1.24,2021-07-22T12:00:47Z,2021-07-22T12:00:47Z,2021-07-22T12:00:47Z,"Windows 11 guest restarted after update normally.[[BR]]

Bootmgr messaged about HDD corruption and couldn't proceed. I closed guest window and it showed message from VirtualBox that memory can't be written.

The error appeared once only and I couldn't reproduce it again.",MikhailRokhin
20468,VM crashes during reboot if EFI is used on Ryzen CPU,Windows,VirtualBox 6.1.24,2021-07-21T22:23:17Z,2021-07-21T23:58:34Z,2021-07-21T23:58:34Z,"Guru crash dialog during reboot of EFI Windows 10 VM upon the way back up at the EFI screen when more than 1 vCPU is used.  I have a Ryzen 7 3700X CPU on a B550M chipset motherboard.
Reference forum post https://forums.virtualbox.org/viewtopic.php?f=1&t=103398&sid=5b8fb3bf048f3b4fda4d91bcbd9ec0d3.  User fth0 looked at the logs and found that ""vCPU1 (the second vCPU) is in real mode and triple-faults"".

Logs attached.
",Justinh
20520,White screen when 3D Acceleration enabled,Linux,VirtualBox 6.1.26,2021-08-22T17:17:49Z,2022-12-13T07:38:20Z,2022-12-13T07:38:20Z,"I get a white desktop screen after logging into Linux with 3D Acceleration enabled.

VM was working as expected until the August update to VirtualBox.

VirtualBox Version 6.1.26 r145957 (Qt5.6.2)
Oracle VM VirtualBox Extension Pack (Version: 6.1.26 r145957; VRDE Module: VBoxVRDP)

{{{
00:00:19.820085 VMSVGA3d: cap[9]=failed rc=VERR_INVALID_PARAMETER! {S23E8_TEXTURES}
00:00:19.820088 VMSVGA3d: cap[10]=failed rc=VERR_INVALID_PARAMETER! {S10E5_TEXTURES}
00:00:19.820301 VMSVGA3d: cap[62]=failed rc=VERR_INVALID_PARAMETER! {MISSING62}
00:00:19.820348 VMSVGA3d: cap[82]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC4_UNORM}
00:00:19.820350 VMSVGA3d: cap[83]=failed rc=VERR_INVALID_PARAMETER! {SURFACEFMT_BC5_UNORM}

00:00:20.333005 GUI: 2D video acceleration is disabled

00:04:46.441670 VMSVGA: PIXEL shader: Failed to create:
00:04:46.441718 0xFFFF0300, 0x0200001F, 0x80010005, 0x900F0000, 0x05000051, 0xA00F0001, 0x00000000, 0x3F000000,
00:04:46.441828 0xBF800000, 0x3F800000, 0x0200001F, 0x80000000, 0xA00F0800, 0x03000042, 0x800F0003, 0x90E40000,
00:04:46.441939 0xA0E40800, 0x02000001, 0x80080000, 0x80E40003, 0x02000001, 0x80070000, 0xA0000001, 0x03000005,
00:04:46.442043 0x800F0001, 0xA0E40000, 0x80FF0000, 0x02000001, 0x800F0002, 0x80E40001, 0x02000001, 0x800F0800,
00:04:46.442146 0x80E40002, 0x0000FFFF,

}}}",Lynda
20724,VB crashed after a while on company computer,Linux,VirtualBox 6.1.26,2021-12-14T13:21:57Z,2021-12-14T13:21:57Z,2021-12-14T13:21:57Z,"Every time I try to launch my VM with Ubuntu, it's crashes after couple of seconds (sometimes after couples of minutes).
This problem is caused by my company's computer setup. When my administrator has temporarily disabled some Credential Guard, my virtual machine works great.",stefek
20527,Copy text from host cause VirtualBox 6.1.26 random crash.,Windows,VirtualBox 6.1.26,2021-08-28T09:57:35Z,2021-11-05T22:29:25Z,2021-11-05T22:29:25Z,"Sorry for my English.

I'm using Virtualbox 6.1.26 on Windows 10 host with Windows 11 guests.

Sometimes, When I copy text from the host web browser, The running guest VM may randomly(rarely) crash, even the ""clipboard sharing"" is disabled.

Here are the logs and my computer configure, If need any info, please feel free to ask.

Host:
CPU: AMD Ryzen 5 5600X
RAM: KLEVV DDR4-2677 16GB x2
Motherboard: MSI MAG B550M BAZOOKA (MS-7C95)
Graphics card: Sapphire Radeon RX560

Guest:
CPU: 2 cores
RAM: 3072 MB
Chipset: ICH9
I/O APIC: Enabled
PAE/NX: Enabled
Hardware acceleration: Default
Graphics memory: 128 MB
",chenshaoju
20548,AMD vs Intel CPU big performance difference,Windows,VirtualBox 6.1.26,2021-09-14T07:03:50Z,2021-10-20T11:43:14Z,2021-10-20T11:43:14Z,"I use single VM on both Intel and AMD hardware. When I moved it from Intel to AMD I noticed the performance is much better. Next I tried to switch to Hyper-V on both machines, converted the VDI file and use it. 

On Intel Core i5 2540M and Intel Core i5-8265U the performance difference was about 50 percent while on AMD Ryzen 5 3600 both VirtualBox and Hyper-V performs almost identical (5 percent difference is as expected). The AMD PC machine has super fast Samsung 980 Pro SSD while the Intel laptop just an ordinary WD SSD. Still the difference is huge.

The guest OS I use for software development. It is Windows 10, Visual Studio, MS SQL Server and so on. I run unit tests of a complex project and recorded how long it takes, see the tests.png attachment. 

There is a long thread [https://forums.virtualbox.org/viewtopic.php?f=2&t=103488] about it with more detailed information.

",Petr Vones
20619,Failed to Restore VM,Linux,VirtualBox 6.1.26,2021-10-19T20:03:53Z,2021-10-19T20:06:26Z,2021-10-19T20:06:26Z,I am restoring the Virtual Machine and it stops completely.,desteves
20618,VirtualBox installer on Windows 11: This app can't run on this device,all,VirtualBox 6.1.26,2021-10-19T16:21:30Z,2021-10-19T16:21:30Z,2021-10-19T16:21:30Z,"Disabling core isolation memory integrity is not an option for me.

VMware Workstation Player is confirmed to be working on my device but I am in a position where I need to run a multitude of virtual machines at once.",fredd
20617,Audio. Sound doesn't work in fedora live-cd with intel hd audio controller selected,Linux,VirtualBox 6.1.26,2021-10-17T18:12:10Z,2021-10-17T18:12:10Z,2021-10-17T18:12:10Z,"When using intel hd audio controller to install fedora 34 or 35 to a virtual machine, the sound doesn't work in the live cd image.
As the result, we cannot install the system with accessibility enabled.
Steps to reproduce:
1. Download fedora 34 workstation from:
https://download.fedoraproject.org/pub/fedora/linux/releases/34/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-34-1.2.iso
2. Create new virtual machine. After creating virtual machine, choose intel hd audio controller in settings/audio.
3. Run the virtual machine.
4. When it finishes loading into live-cd, press alt+f2. Then type ""orca"" without quoates and press enter.
Expected result:
The audio driver should work and you should hear: ""Screen reader on"". Then you can continue with the installation or exploring live-cd with orca enabled.
Actual result:
After typing ""orca"" in run dialog and pressing enter, there is no sound in live-cd.
Note:
When ICH AC97 controller is selected, the sound works, but it crackles and plays only partially, so the user isn't available to interact normally with the live-cd when orca is on and perform the installation or exploring the system.",Vsevolod Popov
20614,No Audio output/passthrough from Linux Guest to Windows Host,Linux,VirtualBox 6.1.26,2021-10-16T17:30:37Z,2021-10-16T17:30:37Z,2021-10-16T17:30:37Z,"I'm running an Ubuntu 18.04 Guest on a Windows 10 Host in VirutalBox 6.1.26.  When I attempt to play sound from the Ubuntu host using ALSA I get no sound passthrough to the host.  This last worked in VirtualBox 6.1.18 with no problem.  Since my upgrade it no longer works.  When I try to start the audio I get the following specific errors in my host log :

00:00:54.313145 VMMDev: Guest Log: 17:15:44.427713 main     VBoxService 6.1.24 r145751 (verbosity: 0) linux.amd64 (Jul 15 2021 18:33:29) release log
00:00:54.313157 VMMDev: Guest Log: 17:15:44.427715 main     Log opened 2021-10-16T17:15:44.427710000Z
00:00:54.313182 VMMDev: Guest Log: 17:15:44.427760 main     OS Product: Linux
00:00:54.313198 VMMDev: Guest Log: 17:15:44.427778 main     OS Release: 4.15.0-159-generic
00:00:54.313212 VMMDev: Guest Log: 17:15:44.427793 main     OS Version: #167-Ubuntu SMP Tue Sep 21 08:55:05 UTC 2021
00:00:54.313227 VMMDev: Guest Log: 17:15:44.427807 main     Executable: /opt/VBoxGuestAdditions-6.1.24/sbin/VBoxService
00:00:54.313230 VMMDev: Guest Log: 17:15:44.427807 main     Process ID: 1890
00:00:54.313232 VMMDev: Guest Log: 17:15:44.427808 main     Package type: LINUX_64BITS_GENERIC
00:00:54.314916 VMMDev: Guest Log: 17:15:44.429498 main     6.1.24 r145751 started. Verbose level = 0
00:00:54.315580 VMMDev: Guest Log: 17:15:44.430155 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:54.315743 Guest Control: GUEST_MSG_REPORT_FEATURES: 0x7, 0x8000000000000000
00:01:09.441017 HDA: DP base (lower) set: 0x000000003ae32000
00:01:09.441031 HDA: DMA position buffer is enabled
00:01:09.498001 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140707423584279ms) than used period size (0ms)
00:01:09.541955 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:09.541973 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE",kellbrir
20609,Poor performance on 4k display with scale factor less than 200%,Windows,VirtualBox 6.1.26,2021-10-16T10:48:12Z,2021-10-16T10:48:12Z,2021-10-16T10:48:12Z,"I'm experiencing problems with VirtualBox 6.1.26 (tried other versions as well, very end of 5 series, and end of 6.0) and 4k external display. My laptop is Lenovo P53 with i7-9850H and Nvidia T2000 graphics card. 4k display needs scaling and when it's set 200% (effective resolution Full HD) then everything is smooth. If I go lower than 200% the screen gets choppy - even when dragging the explorer window very slow refresh rate is noticeable. When I change to 100% for the scale factor everything is very smooth again. My goal is to use 150% scaling and that will give me QHD resolution - but it's impossible to use due to lag. 

I tried all possible options. Adding more CPUs or enabling 3D acceleration doesn't make any difference.  Changing the scale factor from 200% to 199% like with flick of switch affects performance. 

I can't believe that this powerful laptop can't handle a 4k display with scaling. Something is not right here. 

Host: Windows 10 
Guest: Windows 7 

",VB_User
20574,VBoxManage 'start --type headless' cannot be correctly closed by 'controlvm acpipowerbutton',Linux,VirtualBox 6.1.26,2021-09-25T09:05:30Z,2021-10-12T17:41:27Z,2021-10-12T17:41:27Z,"After using: 
{{{
VBoxManage startvm CentOS7-1 CentOS7-2 CentOS7-3 --type headless
}}}
CentOS7-1, 2, 3 are individual vms created by meself and started correctly.

After using:
{{{
VBoxManage controlvm CentOS7-3 acpipowerbutton
}}}
The vm named CentOS7-3 should have been closed correctly.

But after using:
{{{
VBoxManage startvm CentOS7-3 --type headless
}}}
It fails and outputs as below:
{{{
Waiting for VM ""CentOS7-1"" to power on...
VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession
}}}

you can find more detail infos in the topic I posted https://forums.virtualbox.org/viewtopic.php?f=3&t=103980

What's more, through log file named VBoxHardening.log.I find log file which is closed incorrectly lack two lines outputs comparing to log file which is closed correctly:
{{{
3fd0.3fd4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 604653 ms, the end);
3f98.3f9c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 605077 ms, the end);
}}}

Hope this additional msg can help pro devs to solve this problems.
Thx for devs attention and contributions!",Q2K3
20602,UI not working when Win10 User resize scale.,other,VirtualBox 6.1.26,2021-10-11T17:13:53Z,2021-10-11T17:13:53Z,2021-10-11T17:13:53Z,"Hi there,

When I need to import / export  or create New VM, need UI window to complete.

BUT it is not working when User set win10 windows scale in 150% (not 100%)

Workaround is set windows = 100%, then adjust to 150% after completed.

PLEASE HELP let it can support WIN10 WINDOWS SCALE. thx",MorrisTW
20589,"NAT TFTP: leading slash in path cause ""Access violation""",Linux,VirtualBox 6.1.26,2021-10-01T18:22:50Z,2021-10-05T20:34:25Z,2021-10-05T20:34:25Z,"I was trying to boot Grub2 using the built-in NAT TFTP. However, after being successfully loaded by iPXE Grub fails to load the additional files (/boot/grub/i386-pc/normal.mod, etc.) printing: error: Access violation

Same error is returned by NAT TFTP when using a tftp client on a booted Gust OS when the requested path has a leading forward slash.

Workaround: switch to an alternative TFTP server on localhost:
{{{
VBoxManage modifyvm SLESInst --nattftpserver1 10.0.2.2
}}}
Steps to reproduce:

- Generate Grub dir without grub.cfg or vmlinuz/initrd (they're not needed for testing)
{{{
[root@reallin il]# grub-mknetdir --net-directory=/srv/tftp --subdir=/boot/grub -d /usr/lib/grub/i386-pc
Netboot directory for i386-pc created. Configure your DHCP server to point to /srv/tftp/boot/grub/i386-pc/core.0
}}}
- Copy the files to the default TFTPPrefix
{{{
cp -rT /srv/tftp/boot ~/.VirtualBox/TFTP/boot
}}}
- point the VBox DHCP server to the right file
{{{
# If I use leading slash here boot fails sooner
VBoxManage modifyvm MyVM --nattftpfile1=boot/grub/i386-pc/core.0
}}}
- Boot a guest from Network

Expected: Grub loads in ""Normal"" mode

Actual: Grub loads in ""Rescue"" mode.

Additional info:
{{{
[il@reallin ~]$ atftp 10.0.2.4
tftp> get boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp> get /boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp: error received from server <Access violation>
tftp: aborting
tftp> 
}}} 
",lfmeloman
20588,Guest OS startup crashes the VM,Linux,VirtualBox 6.1.26,2021-10-01T17:44:38Z,2021-10-01T17:44:38Z,2021-10-01T17:44:38Z,"When I trying to start VM with RHEL7 it no longer can startup.
It crashing into ""Guru mediation"".
",xor2003
20538,Virtualbox 6.1.26 and current 6.1.27 not installable and working on my Windows 11 22249,all,VirtualBox 6.1.26,2021-09-08T05:31:33Z,2021-10-01T13:34:12Z,2021-10-01T13:34:12Z,"Possibly related: #20536
Since after well awaited and beloved update to 22249 pre_release, is the error with the Host-Only Adaptor (Filter Error Message). And after deinstall no reinstall possible, sadly no message on rollback, but probably same issue.

After update with existing VM: VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Could remove and readd adaptor without error message, but no change.

This is, as you all know, very critical, as VMs running in my fixed Windows 11 for production might have a problem now, as Virtual Box not working on the same computer..",Delphi
20587,Critical error while running virtual machine,Windows,VirtualBox 6.1.26,2021-10-01T12:19:57Z,2021-10-01T12:19:57Z,2021-10-01T12:19:57Z,"Error message is appearing on trying to start virtual machine: Critical error has occurred while running the virtual machine and the machine execution has been stopped.
",SUNNY25
20581,Accessibility. Inaccessible shut down virtual machine screen with screen readers enabeled.,other,VirtualBox 6.1.26,2021-09-28T08:51:51Z,2021-09-30T16:15:26Z,2021-09-30T16:15:26Z,"When navigating the virtual machine shut down screen with screen reader enabeled, none of the elements can be announced by screen reader. All of the elements are announced as ""Unknown"".
Steps to reproduce:
1. Launch NVDA. You can get it from:
 https://nvaccess.org/
2. Launch virtual box and launch virtual machine in it.
3. When the virtual machine is launched, press right CTRL+q key combination.
You will here: close virtual machine.
4. Tab between elements.
You will here ""Unknown"".
Expected result:
Screen reader should announce the element's name, role and value. In this case: Okay and cancel buttons and the set of radiobuttons: ""Save the machine state, Send the shutdown signal, Power off the machine"".
Actual result: Screen reader doesn't announce any elements, it keeps saying ""Unknown"" while tabbing and moving with up and down arrows between radio buttons, so it is impossible to shut down the virtual machine using the screen reader.
See standards and guidelines:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html",Vsevolod Popov
20584,Mutliple CPU's Stalls When Loading,other,VirtualBox 6.1.26,2021-09-29T14:21:44Z,2021-09-29T14:21:44Z,2021-09-29T14:21:44Z,"I am running VB on Windows 10, and when I use more than one processor for a VM is stalls when loading. This is true from Ubuntu 20 and RHEL 8, with encrypted drives and without encrypted drives. I am not sure it consistently stops in the same place, but here is what I have from my test:
* For Ubuntu
 * It is stopping when during the ""Loading essential drivers"". The last line is ""xor: measuring software checksum speed"".
 * When I click the X button to close the console, click ""Send shutdown signal"", and then ""OK"", and I repeat this 2 or more times, it will continue to boot again and I can use the server.
  *

* For RHEL 8
 * It does not display a prompt
 * I use the same process to boot Ubuntu on RHEL 8, but it does not boot and I close it down.
 * It is not consistent where it stalls. Once it was in the middle of the boot, then it goes to a black screen; another time it made it to the login prompt, but when I tried to enter my credentials, the console did not respond.



",guidamedia
20583,Sudden failure,Windows,VirtualBox 6.1.26,2021-09-28T22:37:38Z,2021-09-28T22:37:38Z,2021-09-28T22:37:38Z,"Échec de l'ouverture de session pour la machine virtuelle XP Virtuel.

The VM session was closed before any attempt to power it on.

Code d'erreur : E_FAIL (0x80004005)
Composant : SessionMachine
Interface : ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

",osmond
20529,VM crashes on copy text to clipboard,Windows,VirtualBox 6.1.26,2021-08-31T05:24:45Z,2021-09-28T11:19:56Z,2021-09-28T11:19:56Z,"VM crashes frequently on x64 Windows (Win7 & Win10) guest running on x64 Windows 10 host on copy text to clipboard
x86 guest never crashes.",Alex_Locarus
20578,Error Guest Addiction Windows 7 does not load drivers,Windows,VirtualBox 6.1.26,2021-09-27T10:57:00Z,2021-09-27T10:57:00Z,2021-09-27T10:57:00Z,"Good morning, recently I have tried to put usb in my virtual machine with windows 7, trs install all the compponentes (guest aditions and others) I get error of drivers in windows 7 I can not find solution on the internet or way to install drivers",Juanraro
20576,Installer must be able to update VBoxSDS windows service entry,other,VirtualBox 6.1.26,2021-09-25T18:05:32Z,2021-09-25T18:05:32Z,2021-09-25T18:05:32Z,"When VBoxSDS erxists in windows service list, installer fails. 

It's not so hard to invoke ""sc delete VBoxSDS"" command, report to user(write log entry) if necessary and successfully proceed. As it happens after manual ""sc delete"".

In case there was a failure with loss of previously installed files, simple over-[writing-existent-system-entries-]installation - the most obvious and easy solution - becomes troublesome and painful.",KDV
20575,"Installer must never rely on trash, left by previous version",other,VirtualBox 6.1.26,2021-09-25T17:54:34Z,2021-09-25T17:54:34Z,2021-09-25T17:54:34Z,"Installing VBox of newer version into windows after ${user profile}/Local/Temp cleanup fails.
Installer starts to beg for previous version MSI package, providing no workarounds.

Installation process must flow successfully instead. Installer must be able to upgrade or eradicate previous version traces at least. No trash, especially (installing sub-)system critical one must be left. A warning(never blocking failure) message about eradicating previous version could be provided to user, if necessary.",KDV
20566,VirtualBoxVM.exe: unknown software exception (0x80000003) on AMD FX-8300,all,VirtualBox 6.1.26,2021-09-17T02:25:41Z,2021-09-22T05:57:33Z,2021-09-22T05:57:33Z,"My computer CPU is AMD FX-8300.

When I open a VM and press ""Start"" button, the VirtualBoxVM.exe will stop after 2 seconds, and Windows pops up an ""Application Error"" dialog, which wrote:

""The exception unknown software exception (0x80000003) occurred in the application at location 0xac502432.""

VirtualBox is totally unusable on AMD FX-8300.
But same computer, different CPU: AMD Phenom II X4 945, VirtualBox works fine.",VB6
20553,VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension,Linux,VirtualBox 6.1.26,2021-09-17T01:25:08Z,2021-09-22T04:23:30Z,2021-09-22T04:23:30Z,"hi Team,

While importing the OVA file into Virtual box, an error in being popped up with ""VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension""
I already verified, of having the disk with its proper extensions in .ovf file.
But still having the issues whereas when I import the same ova file in VMware, it did worked at its pace and can start the VM.
Please help on this asap ?",Sanchit Gupta
20569,Cannot interact with VM while settings are open,all,VirtualBox 6.1.26,2021-09-19T22:26:25Z,2021-09-21T19:56:21Z,2021-09-21T19:56:21Z,"Often it is useful to interact with the VM window while configuring settings.

For example, while setting up NAT forwarding, may want to execute ""ifconfig"" in the guest to retrieve guest IP.

Right now, the settings window forces itself on top and prevents interacting with the guest. This means there is a common pattern of navigating to a settings page, realizing one has forgotten the info one needs, then having to close all windows, get the info from the guest, and retrace steps back to the appropriate settings window.",grapereader
20571,"Pressing ""Maximize"" button causing error, while the state starts saving",Windows,VirtualBox 6.1.26,2021-09-20T18:01:20Z,2021-09-20T18:01:20Z,2021-09-20T18:01:20Z,"Pressing the ""Maximize"" button (in dropdown panel), when the state starts saving, in full screen mode, causes an error and an abnormal termination of the virtual machine.

Often trying to minimize the virtual machine, when the state starts saving, I mistakenly click the adjacent ""Maximize"" button, and VM crashed.",astverskoy
20568,6.1.26 Memory can't be written,Windows,VirtualBox 6.1.26,2021-09-19T14:57:36Z,2021-09-19T15:00:52Z,2021-09-19T15:00:52Z,Can't repeat it. It was sudden during pausing VM.,MikhailRokhin
20540,E_FAIL (0x80004005) after Launch,Linux,VirtualBox 6.1.26,2021-09-08T07:35:16Z,2021-09-16T09:34:36Z,2021-09-16T09:34:36Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
20550,Failed to save machine state,other,VirtualBox 6.1.26,2021-09-15T16:14:23Z,2021-09-15T17:09:11Z,2021-09-15T17:09:11Z,"I got an error saving state of running VM. This was working previously, I recently updated VirtualBox, now using Version 6.1.26 r145957 (Qt5.6.2).

{{{
""H:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" controlvm ""{XXXXXX}"" savestate
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: E_ACCESSDENIED
VBoxManage.exe: error: Failed to save machine state
VBoxManage.exe: error: Assertion failed: [SUCCEEDED(rc)] at 'F:\tinderbox\win-6.1\src\VBox\Main\src-server\MachineImpl.cpp' (10359) in long __cdecl Machine::i_saveStorageControllers(struct settings::Storage &).
VBoxManage.exe: error: COM RC=E_ACCESSDENIED (0x80070005).
VBoxManage.exe: error: Please contact the product vendor!
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleControlVM(struct HandlerArg *)"" at line 664 of file VBoxManageControlVM.cpp
}}}


",Loenix
20535,"W64 host, Ubuntu guest: mouse cursor corrupt in Terminal on secondary 4K screen",Linux,VirtualBox 6.1.26,2021-09-06T11:45:41Z,2021-09-08T09:41:15Z,2021-09-08T09:41:15Z,"System details at the end.

Whether the VB container window is sized very small or large, there is a glitch with the mouse cursor inside Terminal windows in the guest OS.

Note that there are two 4K monitors attached. **This bug only appears if the VB container window is on one of the secondary monitors.** If it is on the laptop's main screen, the cursor simply disappears when typing, which I believe is the desired behaviour.

The specific issue is as follows: once the mouse cursor is moved inside the Terminal window, it is at first correct. However, type as much as one character, and it turns into a block of glitched data, 8-10 characters wide and one character tall. If the cursor is moved even a tiny amount, it returns to normal, until the user types once again.

I've attached images of the before and after effects within a small VB container window.

It appears that when the cursor is being removed, the underlying pixels are being bitblt'ed from the wrong part of video memory.

**System details**

VB 6.1.26 build 145957 (Qt5.6.2)

Host:
* Edition	Windows 10 Pro
* Version	20H2
* Installed on	‎06/‎07/‎2021
* OS build	19042.1165
* Experience	Windows Feature Experience Pack 120.2212.3530.0

Guest:
* Ubuntu 64 bit Hirsute, all patches current
* VM Additions installed.

PC:
* Processor	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz   2.71 GHz
* Installed RAM	8.00 GB (7.88 GB usable)
System type	64-bit operating system, x64-based processor

Config:
* HP EliteBook 840 G4
* 3 GiB RAM assigned to guest
* Main screen: 1080p inbuilt
* Secondary screens:
 * 2x 28"" 4K
 * full resolution
 * 125% scaling
 * both connected using DisplayPort.",JonAtFS
20539,E_FAIL (0x80004005) after Launch,Linux,VirtualBox 6.1.26,2021-09-08T07:35:16Z,2021-09-08T07:35:16Z,2021-09-08T07:35:16Z,"current status:

Version 6.1.26 r145957 (Qt5.6.2)

Host OS: Windows 10 64bit

Guest OS: Red Hat(64-bit)

The error occur just when i launch the guestOS before the logo appear.

The VM session was aborted.
Result Code: E_FAIL (0x80004005)

Component: SessionMachine

Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}

i have found out a similar case on Ticket #20516 which have proved to be solved out.but it didn't work in my case. 

log file is attached below 

",kirSin
20537,Guest process stops responding when host suspends and guest is running a docker container,Linux,VirtualBox 6.1.26,2021-09-08T00:25:25Z,2021-09-08T00:32:05Z,2021-09-08T00:32:05Z,"VirtualBox version 6.1.26
Host OS is Windows 10 Prod 19043.1202
Guest OS is Ubuntu 21.04 (with latest updates applied)

To reproduce:
 - On a windows 10 host, create a Linux guest.
 - Install docker on the guest, and start one or more containers
 - Suspend the host
 - Resume the host - Guest will freeze within seconds

When I suspend the host the guest normally comes back fine, however whenever a docker container is running, it does not.
I've seen it with different docker stacks, but haven't exhaustively if it's any one in particular - seems to be just whenever one is running.",gkcgareth
20533,Network card error after deleting Virtual Machine,Linux,VirtualBox 6.1.26,2021-09-03T10:51:19Z,2021-09-03T14:34:08Z,2021-09-03T14:34:08Z,"Hi,

As I wrote in the summary, after removing a VM from VirtualBox I can not change my network properties in the host for all networks cards I have.

I'm hosting from a Windows PC with Windows 10 Pro.

The error appears after removing a Debian VM. Just to notice it did the same issue with a CentOS VM, and to go back to normal it was necessary to execute a factory reset on my PC.

Also it is not possible to desactivate or reactivate the connection.

My computer is my principal tool to work and I frequently use this parameters.

Thanks for any help and solution. ",ddag
20532,BSOD when un-plugging USB device with Windows 10 Host and Windows 7 Guest (VM On),Windows,VirtualBox 6.1.26,2021-09-02T15:52:06Z,2021-09-02T15:52:06Z,2021-09-02T15:52:06Z,"Host : Microsoft Windows [version 10.0.19042.1165]
Guest : Windows 7

step 1 : (OK)
- run the guest VM
- plug USB devices

step 2a : (OK)
- switch off the VM
- un-plug USB devices

step 2b : (HOST BSOD and reset)
- un-plug USB devices while VM is still running

",ManWithNoName
20528,3d acceleration with VMSVGA sometimes leads to a crash or a hang of VirtualBox,Linux,VirtualBox 6.1.26,2021-08-30T20:40:34Z,2021-08-30T20:40:34Z,2021-08-30T20:40:34Z,"When using a Linux VM (debian 9/10) and Windows host with VMSVGA video adapter and 3d acceleration, the VM sometimes might crash or hang. The crash/hang happens in a few minutes after we start a video conferencing app in the browser (with a webcam enabled). With 3d acceleration disabled there is no crash.

When the crash occurs, the error message is ""The instruction at .... referenced memory at 0x0000000000000010...""

The steps to reproduce:

1. Start a VM
2. Forward the webcam to the VM (via VBox UI, Devices->Webcams)
3. Open Google Chrome or Chromium browser. We tried various versions, e.g. Chrome 78.0.3904.108, 64-bit and Chromium 90.0.4430.212, 64-bit. The checkbox ""Use hardware acceleration when available"" needs to be enabled in the browser settings (it is enabled by default).
4. Navigate to zoom.us and login (a free account is enough).
5. Host a meeting with a webcam enabled. The meeting needs to be started in the browser, not in the native linux app. There is no need for others to join the meeting.
6. If it doesn't hang or crash immediately - give it a few minutes to run. And if it doesn't crash now - close the browser (sometimes the crash only happens when closing the browser).

Attached are 2 logs: one with a crash with Chromium 90 and another one with a hang with Chromium 83. The hang has happened when the ""accept cookies"" window from zoom.us was loading: it turned out to be completely corrupted and the VM hang occurred. The error in the log is VMSVGA related but is different to what I see in case of a crash. In the attached logs Hyper-V is enabled. But this doesn't make a difference and we can reproduce this issues with Hyper-V disabled as well.

This problem was first reported in https://www.virtualbox.org/ticket/19154. 
I did more tests today trying to reproduce the problem using Nvidia GPU, but couldn't. Today I also couldn't reproduce the problem using Intel GPU and exactly the same setup as I was using previously. So the problem is not 100% reproducible, unfortunately (until today I could reproduce it all the time - ~20-30 times or so). If I see the problem again, I will do tests with NVidia and will update the ticket.",Mikhail Kovalev
20526,High VMM load on VMs with more than 1 core,all,VirtualBox 6.1.26,2021-08-28T02:27:31Z,2021-08-28T02:27:31Z,2021-08-28T02:27:31Z,"The VMM load is stuck about 60% when running VMs assigned with more than 1 core although the guest is totally idle.
I'm using 6.1.x revision 146512 but the problem persist on all the recent versions.
I have enabled ioapic,apic,x2apic but no use.
Note that the VM process does not use much cpu actually, but it is a bit more lag than usual.

image
[[Image(https://i.ibb.co/L0jFyJM/image.png)]]",ebk
20516,E_FAIL (0x80004005) after host PC hibernation,all,VirtualBox 6.1.26,2021-08-20T18:10:26Z,2021-08-23T18:40:35Z,2021-08-23T18:40:35Z,"After I woke up the host PC from hibernation, when I try to start a virtual machine I get the following error:

{{{
Failed to open a session for the virtual machine Windows_10_Pro_LV_2018_SP1.
The VM session was aborted.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}

The error occurs before the VirtualBox logo appears in the launch screen of the virtual machine.[[BR]]
The error does not happen if the host PC is shutdown and restarted.[[BR]]
The error has occurred after updating virtualbox to 6.1.26.

VirtualBox Graphical User Interface[[BR]]
Version 6.1.26 r145957 (Qt5.6.2)[[BR]]
Host OS: Windows 7 Pro 64bit[[BR]]
Guest OS: Windows 10 Pro 64bit or Windows 7 Pro 64bit

As highlighted in the forum post [https://forums.virtualbox.org/viewtopic.php?f=6&t=103708], the problem is solved by completely disabling the audio of the virtual machine.

The issue is repeatable, by re-enabling the audio the error appears the same.

The VBox.log file is attached for checking.
",Asper
20519,ubuntu isn't booting right,Linux,VirtualBox 6.1.26,2021-08-22T14:10:38Z,2021-08-22T14:10:38Z,2021-08-22T14:10:38Z,"after tweaking and messing around with the guest os, which is ubuntu. instead of 'save the machine state', i used 'send the shutdown signal', and now the virtual machine isn't booting right. is there a way i can restore to previous versions?",Shoham
20517,Unable to connect 2TB seagate external USB drives to RHEL7 Guest,Linux,VirtualBox 6.1.26,2021-08-21T23:06:43Z,2021-08-21T23:06:43Z,2021-08-21T23:06:43Z,"Hi Team, 
I'm having issues connecting multiple different 1.7 TB seagate external USB drives to my RHEL7 guest vms. 

The error and a drive properties view from windows is attached for your review. 

Also, I can attach a 1TB external drive just fine, so I'm thinking that it's a driver compatibility issue with the larger drives that's the problem? 

Thanks!",hanch0
20501,Installation start crash of Win10 guest on Win7 host.,Windows,VirtualBox 6.1.26,2021-08-14T14:45:34Z,2021-08-14T14:45:34Z,2021-08-14T14:45:34Z,"Machine: LENOVO W701 with Win7 ultimate host OS. 
Win10 Iso image is open in BD-ROM virtual DVD drive. After configuration of the VM for Win10 guest OS clicking start. The VM starts running in VB 6.1.26 and the Win10 screen appears with blue window in mids the black screen. Roughly 10 seconds later an error message appears reporting the fatal error crash.
The log file does not make my sly. Anyone an idea what has happened?
A Win7 guest installation on this system works fine.",drghl
20492,Debian installer hangs: BUG: unable to handle kernel NULL pointer dereference at 00000004,Linux,VirtualBox 6.1.26,2021-08-06T22:14:39Z,2021-08-06T22:14:39Z,2021-08-06T22:14:39Z,"I'm trying to install Debian 10 i386 on a Windows 10 (64-bit) host but the installer hangs during ""Select and install software"", specifically ""Configuring man-db (i386)"". Do not modify the default software selection (Debian desktop, print server and standard system utilities). It happens every time, both in the graphical and the non-graphical installer. I'm running an AMD Ryzen 7 3800X and AMD-V appears to be enabled.

This is logged by the kernel once the system hangs:
{{{
[  401.003262] BUG: unable to handle kernel NULL pointer dereference at 00000004
[  401.003775] *pde = 00000000 
[  401.003978] Oops: 0002 [#1] SMP
[  401.004197] CPU: 0 PID: 21003 Comm: mandb Not tainted 4.19.0-17-686 #1 Debian 4.19.194-1
[  401.004767] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[  401.005336] EIP: _raw_spin_lock+0x14/0x30
[  401.005618] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.007152] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.007694] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: ee4efef4
[  401.008228] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.008863] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
[  401.009382] Call Trace:
[  401.009597]  speculation_ctrl_update+0x1aa/0x220
[  401.009976]  speculation_ctrl_update_current+0x18/0x20
[  401.010399]  task_update_spec_tif+0x25/0x30
[  401.010745]  ssb_prctl_set.part.1+0x1d/0x30
[  401.011091]  arch_seccomp_spec_mitigate+0x45/0x50
[  401.011488]  do_seccomp+0x5b0/0x5f0
[  401.011776]  sys_seccomp+0x16/0x20
[  401.012059]  do_fast_syscall_32+0x81/0x1a0
[  401.012400]  entry_SYSENTER_32+0x68/0xbb
[  401.012848] EIP: 0xb7efdd31
[  401.013188] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
[  401.015419] EAX: ffffffda EBX: 00000001 ECX: 00000000 EDX: 0162db20
[  401.016174] ESI: 015b5352 EDI: b7eded4d EBP: b7c7dde9 ESP: bfdab85c
[  401.016929] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246
[  401.017753] Modules linked in: fuse battery dm_mod md_mod xfs jfs btrfs xor zstd_decompress zstd_compress xxhash raid6_pq libcrc32c vfat fat ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb e1000 nls_utf8 isofs usb_storage hid_generic usbhid hid sr_mod cdrom sd_mod ata_generic ohci_pci ehci_pci ohci_hcd ehci_hcd ata_piix snd_intel8x0 snd_ac97_codec ahci libahci ac97_bus evdev libata psmouse snd_pcm snd_timer usbcore usb_common snd soundcore scsi_mod
[  401.022503] CR2: 0000000000000004
[  401.022903] ---[ end trace 8693d9353e91b6c4 ]---
[  401.023448] EIP: _raw_spin_lock+0x14/0x30
[  401.023933] Code: 89 d8 5b 5d c3 90 89 c8 e8 c9 7e a2 ff eb f1 8d b4 26 00 00 00 00 0f 1f 44 00 00 55 89 c1 89 e5 53 31 d2 bb 01 00 00 00 89 d0 <3e> 0f b1 19 85 c0 75 04 5b 5d c3 90 89 c2 89 c8 e8 27 6a a2 ff 90
[  401.026189] EAX: 00000000 EBX: 00000001 ECX: 00000004 EDX: 00000000
[  401.026947] ESI: 00000000 EDI: 00000020 EBP: ee4efef8 ESP: dca193bc
[  401.027704] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010046
[  401.028492] CR0: 80050033 CR2: 00000004 CR3: 362bf000 CR4: 000406d0
}}}

I've attached the full kernel log, as well as the VirtualBox log on the host.",joelpuig
20592,Version 6.1.26 r145957 (Qt5.6.2) GUI crashes quite a times after start,all,VirtualBox 6.1.26,2021-10-02T06:22:01Z,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"I am using Windows 10 Pro (Version	10.0.19042 Build 19042)and many a times, immediately after starting the application the GUI crashes. Virtualbox Version 6.1.26 r145957 (Qt5.6.2)

It was happening in an older version also. Mostly second time it starts just fine. 

None of my other apps crash, my system is an i7 with 32GB RAM. Attaching crash dumps.

Crash dump size is larger, unable to attach, copied in this folder on Google Drive : https://drive.google.com/drive/folders/13Wbp5wuq1thK2RzXxJZP6rxEtb9JYO1D?usp=sharing

",Ravi R
21387,Windows 11 BSOD,other,VirtualBox 6.1.28,2022-12-31T17:03:15Z,2023-01-04T12:24:24Z,2023-01-04T12:24:24Z,"After upgrading to Windows 11 and performing the installation steps below, I repeatedly got BSOD after issuing 'vagrant up' command. Since I need a working VB and could not find a working solution using Windows 11, I downgraded to Windows 10.

Upgraded from Windows 10 21h2 to Windows 11 22h2, upgraded Vagrant to 2.3.4 (required for Windows 11), upgraded Virtualbox to 6.1.28 (required for Windows 11), using Homestead box version 11.3.0 (unchanged), using existing homestead.yaml.",white-tiger
20667,The keyboard not working after the complete installation of Linux Mint 20.2.,Linux,VirtualBox 6.1.28,2021-11-14T12:42:18Z,2022-09-07T08:31:06Z,2022-09-07T08:31:06Z,The keyboard not working after the complete installation of Linux Mint 20.2. When the installation is completed & said press enter keys I pressed but not working please solve this problem this is a bug!,Cannon1000
20683,PNP DETECTED FATAL ERROR,other,VirtualBox 6.1.28,2021-11-22T10:12:49Z,2022-01-27T12:36:08Z,2022-01-27T12:36:08Z,"In version 6.1.28 of virtualbox, when connecting any usb device, even a headset while virtualbox is active, a screenshot of Windows 10 jumps with the PNP DETECTED FATAL ERROR error.
The compilation of windows that I have installed is 19044.1348",Vicente Irala López
20782,VirtualBox revert to invalid options automatically,Linux,VirtualBox 6.1.28,2022-01-20T14:46:50Z,2022-01-20T14:46:50Z,2022-01-20T14:46:50Z,"Hello,
  I have installed a custom Linux guest OS and I wish to keep my video card to VBoxVGA. Unfortunately VirtualBox every time I change the selection or visit the settings page, by default revert this setting to VMsvga without prompt and this driver causes kernel panic to my VM. This is not happening in older versions of VirtualBox.",ssavva
20673,Machine hang,Windows,VirtualBox 6.1.28,2021-11-17T16:23:43Z,2022-01-20T01:04:01Z,2022-01-20T01:04:01Z,"I have Windows 11 host and VirtualBox 6.1.28. After install Guest Additions in Windows NT 4.0 Server, the machine go to Guru Meditation.

Please resolve my problem. I was attached log files and the screenshoot.",19Barto89
20650,host-only network is not working on windows 10 pro with 6.1.28,Linux,VirtualBox 6.1.28,2021-11-05T15:24:45Z,2022-01-19T11:11:01Z,2022-01-19T11:11:01Z,"I have upgraded the virtualbox to 6.1.28, and host-only network is not working.

on the gui of host-only network manager, there is only an empty list, and can't add an adapter. I also try to add an adapter by command line, but get exception as the following:

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 95 of file VBoxManageHostonly.cpp

could you help to solve this problem??",kklin
20729,High definition audio: cannot control volume with standard pin widgets,other,VirtualBox 6.1.28,2021-12-15T02:09:15Z,2021-12-15T02:09:15Z,2021-12-15T02:09:15Z,"I was writing a driver for High definition audio controller, I found that standard HD audio pin widgets cannot control the volume/mute of Sigmatel codec for output. Even direct output widgets cannot control the volume/mute of output converter. To control the volume/mute we need to communicate with the stac codec directly through controller interface. This need fixes as the standard method described by intel, should work. ",Manas Kamal
20630,Sound disappears after second change from Speaker to Bluetooth Headphones on the host,Windows,VirtualBox 6.1.28,2021-10-24T12:04:54Z,2021-12-13T01:22:32Z,2021-12-13T01:22:32Z,"This is a duplicate of the ticket #20431. The description and the analysis of the issue is already there. The error is here since 4 versions (was caused by the another refactor of sound backend back in the March 2021). It still here in the version 6.1.28 147628 and 6.1.29 147791, so I opened this duplicate.

Quick description here: after the host output device changes from Speaker to Bluetooth, then back to Speaker and then once again to BT, the sound output from VBox is lost. Other application from the host still can use the BT as output, but VBox can only use the Speaker after that. The only remedy is to restart or to save and restore the VM, but this only gives one single more short for the BT. After that the whole situation repeats itself.
",boxer01
20689,Audio output switching no longer works reliably.,Windows,VirtualBox 6.1.28,2021-11-24T18:23:28Z,2021-11-24T18:23:28Z,2021-11-24T18:23:28Z,"Audio output switching no longer works reliably.

Windows 10 host, Windows 10 guest.  Swapping audio output (like plugging in to a monitor with speakers), the audio dies.  Not sure if it can be resurrected with some combination of guest and/or host reboots.

It used to transfer seamlessly in 6.1.18.  This is a regression, probably introduced in 6.1.20: ""Audio: Multiple fixes and enhancements"".",Zapados
20687,kernel module isn't loaded because the VBox drive is not installed,Windows,VirtualBox 6.1.28,2021-11-24T15:17:39Z,2021-11-24T16:26:51Z,2021-11-24T16:26:51Z,"I used without problems for about three years VM VBox 5.6.2 on an host Win 7-64 , but around a months ago the pc has had some malfunctions with fan and power supply that they caused problems in the management of windows on the desktop and the Explorer block. Moreover VM Vb has stop to run, showing the message enclosed.
Now I have fixed any HD or SW issues and updated the VM Vbox version to 6.1.28 but it still doesn't work due of same problem: VBOX Drive don't installed.",marcopro
20685,Ubuntu VM crash,Linux,VirtualBox 6.1.28,2021-11-23T09:05:01Z,2021-11-23T13:57:48Z,2021-11-23T13:57:48Z,My Ubuntu VM crashed for an unknown reason,mediawiz
20670,virtual machine does not start,Windows,VirtualBox 6.1.28,2021-11-17T01:02:14Z,2021-11-20T08:32:38Z,2021-11-20T08:32:38Z,Version 6.1.28 r147628 (Qt5.6.2),altair_kusanagi
20672,During the execution of the docker pull command the VM dies,Linux,VirtualBox 6.1.28,2021-11-17T15:23:26Z,2021-11-18T19:23:27Z,2021-11-18T19:23:27Z,"I have a VM installed with the operating system Ubuntu 20.04 LTS .
Running the command docker pull from the docker registry of AWS the virtual machine dies ",GriGiu
20665,Shutting down VM crashes all other Hyper-V instances on Windows 11,all,VirtualBox 6.1.28,2021-11-12T14:37:06Z,2021-11-12T17:49:24Z,2021-11-12T17:49:24Z,"Attempting to shut down any running VM in any fashion (either from within VM or via power off) on Windows 11 with Hyper-V running will result in all other Hyper-V machines crashing.

Attaching logs from VirtualBox 6.1.28, one machine powering off and second crashing. This is not exclusive to Hyper-V machines however - any running Hyper-V VM, either native Hyper-V, WSL2 or VMWare (also using VMP) will crash(!).

I can attach vmware-vmx.exe dumps if necessary too.",eider
20651,Internal Microphone is not detected/doesn't work on Linux - Ubuntu,Linux,VirtualBox 6.1.28,2021-11-05T15:56:34Z,2021-11-05T15:56:34Z,2021-11-05T15:56:34Z,"Internal Microphone is not detected/doesn't work (e.g. microphone inside notebook) on Ubuntu 20. When I connect USB headphones with a microphone, only this USB microphone is detected. Host Windows 10, guest Ubuntu 20.",Matej
20649,Version 6.1.97 r147979 for Win 11,Windows,VirtualBox 6.1.28,2021-11-04T20:44:44Z,2021-11-04T20:44:44Z,2021-11-04T20:44:44Z,"Unfortunately, VBoxGuestAdditions.iso cannot be installed. After the installation and restart, Win11 can no longer be started in the VM. Win11 tries to repair itself, but brings up the message that no repair is possible. There is no other option than to delete the VM and set it up again, including reinstalling Win11.
Unfortunately, the screen resolution and other things cannot be set without the GuestAddition. The Win11 installation cannot really be used on the VM.
Can you help me?",icewater
20647,Windows 3.11 not working with hardware virtualization,Windows,VirtualBox 6.1.28,2021-10-30T17:22:22Z,2021-10-30T17:29:23Z,2021-10-30T17:29:23Z,"If you install MSDOS 6.22 and Windows 3.11 in a Virtualbox machine, Windows 3.11 cannot start when hardware virtualization is enabled (mandatory in VB 6.1). The same virtual machine works OK in VB 6.0 with the hardware virtualization disabled. Windows 3.1 is not affected, only Windows 3.11 (Windows for Workgroups). Is there any workaround for this problem?",Iker Rodriguez
20646,In the machine settings page system->acceleration hardware virtualization check box not responding.,Windows,VirtualBox 6.1.28,2021-10-29T15:29:36Z,2021-10-29T19:20:57Z,2021-10-29T19:20:57Z,"For a virtual machine settings, a invalid setting is indicating on the system -> acceleration page , suggested that the hardware acceleration should be off. After uncheck it the OK button is not enabled , not able to save the configurations.",subhajit
20643,Virtualbox crashes on install of Win11,Windows,VirtualBox 6.1.28,2021-10-27T12:00:20Z,2021-10-27T12:00:20Z,2021-10-27T12:00:20Z,"win11-DVDs starts normaly, copy his files to the disk and after an reboot, the vm crashes. see attached vm-log.",tomec5189
20638,Windows does not start,other,VirtualBox 6.1.28,2021-10-26T13:56:37Z,2021-10-26T13:56:37Z,2021-10-26T13:56:37Z,"I have a bug that i cant solve because mi pc does not start virtualbox this is the log File:

00:00:00.002638 main     VirtualBox COM Service 6.1.28 r147628 win.amd64 (Oct 18 2021 18:49:03) release log
00:00:00.002641 main     Log opened 2021-10-26T11:33:41.760766100Z
00:00:00.002641 main     Build Type: release
00:00:00.002643 main     OS Product: Windows 11
00:00:00.002644 main     OS Release: 10.0.22000
00:00:00.002645 main     OS Service Pack: 
00:00:00.014185 main     DMI Product Name: MS-7C37
00:00:00.020329 main     DMI Product Version: 1.0
00:00:00.020333 main     Firmware type: UEFI
00:00:00.020525 main     Secure Boot: Disabled
00:00:00.020530 main     Host RAM: 16305MB (15.9GB) total, 11461MB (11.1GB) available
00:00:00.020534 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSDS.exe
00:00:00.020534 main     Process ID: 16736
00:00:00.020535 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.021118 main     WinMain: VBoxSDS: InitializeSecurity: 0
00:00:00.024852          registerVBoxSVC: aVBoxSVC=0000000000c75818 aPid=16848 (0x41d0)
00:00:00.025051          i_lookupOrCreatePerUserData: Created new entry for S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)
00:00:00.025058          registerVBoxSVC: Making aPid=16848 (0x41d0) the chosen one for user S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)!
00:03:09.773444          registerVBoxSVC: aVBoxSVC=0000000000c753b8 aPid=5360 (0x14f0)
00:03:09.773960          registerVBoxSVC: Seems VBoxSVC instance died.  Dropping it and letting caller take over. (hrc=RPC_S_SERVER_UNAVAILABLE 0x800706BA)
00:03:09.774327          i_unchooseTheOne: Irregular release ... (pid=16848 (0x41d0) user=RubenAguado/Ruben Aguado sid=S-1-5-21-4179917506-290648088-1681930059-1001)
00:03:09.774368          i_unchooseTheOne: ... done.
00:03:09.774372          registerVBoxSVC: Making aPid=5360 (0x14f0) the chosen one for user S-1-5-21-4179917506-290648088-1681930059-1001 (RubenAguado/Ruben Aguado)!
",RubenAguado
20634,No sound with pipewire after updating fedora 34 guest system,Linux,VirtualBox 6.1.28,2021-10-25T09:21:35Z,2021-10-25T09:21:35Z,2021-10-25T09:21:35Z,"After updating the newly installed fedora 34 and restarting the guest system, there is no sound output because of the pipewire activation.
Steps to reproduce:
1. Create a new virtual machine.
2. Install fedora 34 workstation or fedora 34 mate spin on it.
3. After starting the system, try to play any audio. You will notice that it works because pulseaudio is used.
4. Install the new version of virtualbox guest additions.
5. Update the machine with sudo dnf update command in terminal.
6. Restart the guest machine.
Expected result:
After restarting the virtual machine, audio should continue working.
Actual result:
When launching orca screen reader or playing any other audio file, nothing plays and audio output doesn't work.
While testing,  ICH AC97 driver was used.
Also, this issue appears with intel hd audio controller selected.",Vsevolod Popov
20755,No audio heard in v6.1.24 through v6.1.30,Windows,VirtualBox 6.1.30,2021-12-31T01:00:30Z,2023-01-18T05:23:44Z,2023-01-18T05:23:44Z,"I'm currently running VirtualBox hosted on Windows 10 Pro 21H1. I have 3 guests with the following audio configurations:

Windows XP Pro 32-bit - Windows Direct Sound / ICH AC97
Windows 7 Pro 64-bit- Windows Direct Sound / Intel HD Audio
Windows 10 Pro 64-bit - Windows Direct Sound / Intel HD Audio

Under v6.1.22 the audio works for all three guests, albeit with the repeating / echoing audio which others have reported.

If I update to any version from v6.1.24 through v6.1.30, the audio in the Windows XP guest works OK, but there is no audio on my Windows 7 and Windows 10 guests.

logs from 6.1.22 and 6.1.30 attached.",doctorx
20830,Black Screen on VirtualBox,Linux,VirtualBox 6.1.30,2022-02-16T14:58:05Z,2022-12-31T12:03:49Z,2022-12-31T12:03:49Z,I am using Virtual box and Kali linux version in it. Once i rebooted it prompted for username and password so after entering it the screen was fully black. Even i close the virtual box and opened it but same issue i am facing,sharan312
21074,launchVMProcess via MSCOM -- environment changes parameter type mismatch ambiguity,all,VirtualBox 6.1.30,2022-08-24T04:28:06Z,2022-08-24T04:28:06Z,2022-08-24T04:28:06Z,"
When calling launchVMProcess() through MSCOM by VBScript, JScript, Python, etc.. they all end up with a ""type mismatch"" error. After some process of limitation, it might be the third and final parameter the cause of it: the list of environment changes.

According to the source in c++, it supposed to accept a string array, but the source wants a specific type of array: a string (utf-8) array. It doesn't like variant arrays (I believe they're called safearrays?). Unfortunately, because the samples or examples provided in the SDK doc is too outdated -- i.e. using openRemoteSession rather than launchVMprocess -- I'm lost as to how to pass something to that third parameter that'll satisfy VirtualBox MSCOM.

I was referring to the definition of launchVMProcess() here:
//trunk/src/VBox/Main/src-server/MachineImpl.cpp#L7814

If there are new steps that weren't documented, they should be updated accordingly; especially the SDK doc.

It's worth mentioning that the issue from Ticket #20750 might be related to what was mentioned here.",jprogman
20922,No Ethernet Ubuntu/Windows guest after computer wake host from sleep,all,VirtualBox 6.1.30,2022-04-30T13:37:42Z,2022-04-30T13:37:42Z,2022-04-30T13:37:42Z,"'''Problem'''
- Broken Ethernet TX/RX in Ubuntu/Windows guest after computer wake from sleep.
- Wireshark in the guest shows TX packets, but no incoming packets.
- Wireshark in the host does not show any network traffic from/to the guest.

'''Setup'''
- VirtualBox v6.1.30 or v6.1.32
- Windows 10 20H2 host (updates installed of today)
- Ubuntu 21.04 guest or Windows 10 guest (updates + guest additions installed)
- VM Intel (R) i211 Gigabit Network connection (default)
- VM Bridge network

'''Reproducible testcase'''
1. Make sure Ethernet works on the host and guest.
2. Set computer in sleep mode.
3. Wake computer.
4. Network on host works.
5. Network in guest broken: TX and RX failed according to WireShark logs.

'''Additional info'''
- Reproducible on AMD Ryzen 7/9 and Intel Core I7 laptops/desktops.
- Hyper-V on host not enabled.
- Disabling/enabling network in guest does not work.
- Ethernet cable disconnect/reconnect host does not work.
- Virtual Ethernet link down/up guest does not work.
- Set guest in paused mode before sleep/wake host does not work.
- Disconnect Ethernet before sleep/wake host does not work.

See forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105781",Erwin
20753,VirtualBox exe failed to install on Windows 11,Windows,VirtualBox 6.1.30,2021-12-30T21:18:44Z,2022-03-07T12:39:31Z,2022-03-07T12:39:31Z,"Hello,

I am facing a serious problem when installing virtualbox.exe
I tried multiple versions and all didn't install knowing that before I had vbox installed normally. But when I uninstalled it to update to the new version I got this problem.

I am using Windows 11.

Proof Of Concept:
1. Open `VirtualBox-6.1.30-148432-Win.exe` and proceed with the steps.
2. I get this error while installing
Error:
The Windows Installer Service could not be accessible. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
3. And after I hit `OK`. I get the following message.
Installation failed! Error: Fatal error during installation.

Please notice that any exe files are being installed normally without any errors. I am facing this problem when just installing virtual box.

I hope you can find a solution for this problem.

Kind Regards.",ahmad_halabi
20835,I cannot do normal start it only start as uncoupled start,Linux,VirtualBox 6.1.30,2022-02-21T06:45:18Z,2022-02-21T21:56:18Z,2022-02-21T21:56:18Z,"The virtual machine 'android32bvb_7_1_int11' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'G:\Virtual Machines\android32bvb_7_1_int11\Logs\VBoxHardening.log'.


Código resultado: 
E_FAIL (0x80004005)
Componente: 
MachineWrap
Interfaz: 
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
",Jose Nunez
20695,Audio Crackling and Distorted - New,Windows,VirtualBox 6.1.30,2021-11-27T22:35:22Z,2022-02-08T17:29:40Z,2022-02-08T17:29:40Z,"I've been getting audio crackling and distorted since the latest update (Nov 26)

Running Windows 10 with a Windows 11 VM. It was fine until the latest update of VB. I would forget I was in the VM when I watched a movie in it --- until now.

Version 6.1.30 r148432 (Qt5.6.2)",Photoman15
20747,Memory can't be read after resuming VM from pause,BSD,VirtualBox 6.1.30,2021-12-23T23:25:05Z,2022-02-07T18:27:06Z,2022-02-07T18:27:06Z,Memory can't be read after resuming VM from pause,MikhailRokhin
20774,CP2102 USB to UART Bridge Ctrl - USB Device Connection Echec (0x80004005),Windows,VirtualBox 6.1.30,2022-01-16T18:45:44Z,2022-01-16T21:38:14Z,2022-01-16T21:38:14Z,"The Silicon Labs CP2102 USB to UART Bridge Controller doesn't work as expected.

Host : Windows 10
Guest : Windows XP SP3",ManWithNoName
20770,Guest Additions: Drag and Drop Fails to Work / Register,all,VirtualBox 6.1.30,2022-01-12T17:13:20Z,2022-01-12T17:13:20Z,2022-01-12T17:13:20Z,"While the copy and paste works just as expected, I can not get drag and drop to work. I have re-installed (right before posting this) virtualbox 6.1.30 along with the appropriate 6.1.30 guest additions to double check.

To ensure I am not messing up installation, I have tried all different ways of installing the guest additions (GUI, terminal, etc).

To give you some visual, it shows a red circle with a slash through it when hovering the file over a virtualbox machine.

",metalfirefox
20761,"VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one",all,VirtualBox 6.1.30,2022-01-06T14:01:18Z,2022-01-06T14:01:18Z,2022-01-06T14:01:18Z,"As described here: https://forums.virtualbox.org/viewtopic.php?f=6&t=104892&start=15

Currently, i saw that issue on v6.1.97 (testing with TPM support), but i also saw it months ago on older release versions",jmar83
20760,Slow performance since last update,Linux,VirtualBox 6.1.30,2022-01-06T03:47:51Z,2022-01-06T03:47:51Z,2022-01-06T03:47:51Z,"update to windows 11 slowed things down and since the las vbox update, my VM are unusable

extreme slow speed (response,Latency,Loading)
CPU usage is high for no apparent reason (Firefox use 60% CPU (8cores)

crashes

ive installed vmware to test if it was due to windows 11 but vmware work like vbox when no probleme were existing",dparadis
20756,"Picture falling apart until lock up with Wayland, 3D, VMSVGA and Linux guest",Linux,VirtualBox 6.1.30,2022-01-01T19:13:40Z,2022-01-04T21:50:08Z,2022-01-04T21:50:08Z,"While X.org locks up almost immediately with fractional scaling with 3D enabled Wayland gives some time to work. But scrolling is ultra slow picture start falling apart  more and more until eventual lock up. It does not depend on fractional scaling. Happens with 100% as well.

Both are working without those problems without 3D enabled, except X.org does not change system-wide DPI when changing scaling and Wayland does not remember scaling setting, so resets to 100% on every boot and change of resolution.

It is Windows 10 host, Ubuntu 21.10 guest (been same with 21.04, 20.X etc).

",regs
20757,CANT START ENGINE,Linux,VirtualBox 6.1.30,2022-01-02T18:43:10Z,2022-01-02T18:44:28Z,2022-01-02T18:44:28Z,"I cannot start it or attach linux installation to apps. i researched everything, but i've found nothing...plz help me",BABBA BOI
20754,No audio heard in v6.1.24 through v6.1.30,Windows,VirtualBox 6.1.30,2021-12-31T01:00:23Z,2021-12-31T01:00:23Z,2021-12-31T01:00:23Z,"I'm currently running VirtualBox hosted on Windows 10 Pro 21H1. I have 3 guests with the following audio configurations:

Windows XP Pro 32-bit - Windows Direct Sound / ICH AC97
Windows 7 Pro 64-bit- Windows Direct Sound / Intel HD Audio
Windows 10 Pro 64-bit - Windows Direct Sound / Intel HD Audio

Under v6.1.22 the audio works for all three guests, albeit with the repeating / echoing audio which others have reported.

If I update to any version from v6.1.24 through v6.1.30, the audio in the Windows XP guest works OK, but there is no audio on my Windows 7 and Windows 10 guests.

logs from 6.1.22 and 6.1.30 attached.",doctorx
20750,Examples to control VM via COM do not work,Windows,VirtualBox 6.1.30,2021-12-26T15:17:09Z,2021-12-26T15:17:09Z,2021-12-26T15:17:09Z,"Hi!

I have a VM named Win8.1, running on a Win10 host, which can be controlled manually via the VM manager.

Now, I'd like to control it via COM, but even the examples shipped with the SDK do not work.


== Python  ==

The file SDKRef.pdf lists the following Python code in section 2.3.1.
I just changed the name of the VM  to Win8.1 and added two print commands:


{{{
import win32com.client
vbox = win32com.client.Dispatch(""VirtualBox.VirtualBox"")
session = win32com.client.Dispatch(""VirtualBox.Session"")
mach = vbox.findMachine(""Win8.1"")
print(""Machine.State: "", mach.State) 
print(""Machine SnapshotFolder: "", mach.SnapshotFolder)
progress = mach.launchVMProcess(session, ""gui"", """")
progress.waitForCompletion(-1)
}}}

The output is:
{{{
Machine.State:  1
Machine SnapshotFolder:  C:\VMs\Win8.1\Snapshots
Traceback (most recent call last):
  File ""C:\Users\webers\Desktop\vbox.py\vbox.py"", line 8, in <module>
    progress = mach.launchVMProcess(session, ""gui"", """")
  File ""<COMObject <unknown>>"", line 2, in launchVMProcess
pywintypes.com_error: (-2147352571, 'Typenkonflikt.', None, 3)
}}}

The output of the two print commands is correct, so COM in general works, but launching the VM fails with error ""Typenkonflikt"" (this is german, so it's not a Python error, but comes from my german VM installation or the german Win10 host)

 
== VBS ==

In sdk\bindings\mscom\vbs\sample, there is this listing, where I only inserted my VM name:

{{{
' $Id: vboxinfo.vbs 135976 2020-02-04 10:35:17Z bird $
'' @file
' ???
'

'
' Copyright (C) 2009-2020 Oracle Corporation
'
' This file is part of VirtualBox Open Source Edition (OSE), as
' available from http://www.virtualbox.org. This file is free software;
' you can redistribute it and/or modify it under the terms of the GNU
' General Public License (GPL) as published by the Free Software
' Foundation, in version 2 as it comes in the ""COPYING"" file of the
' VirtualBox OSE distribution. VirtualBox OSE is distributed in the
' hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
'

Sub Print(str)
   Wscript.Echo str
End Sub

Sub StartVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """")
  progress.waitForCompletion(-1)
  session.close()
End Sub


Sub StopVm(vb, mach)
  Dim session, progress

  Set session = CreateObject(""VirtualBox.Session"")
  vb.openExistingSession session, mach.id
  session.console.powerDown().waitForCompletion(-1)
  session.close()
End Sub


Sub Main
   Dim vb, mach

   set vb = CreateObject(""VirtualBox.VirtualBox"")
   Print ""VirtualBox version "" & vb.version

   ' Safe arrays not fully functional from Visual Basic Script, as we
   ' return real safe arrays, not ones wrapped to VARIANT and VBS engine
   ' gets confused. Until then, explicitly find VM by name.
   ' May wish to use hack like one described in
   ' http://www.tech-archive.net/Archive/Excel/microsoft.public.excel.programming/2006-05/msg02796.html to handle safearrays
   ' if desperate

   Set mach = vb.findMachine(""Win8.1"")
   Print ""Machine: "" & mach.name  & "" ID: "" & mach.id

   StartVm vb, mach
End Sub

Main

}}}

Again, the print commands work correctly. But then, line 26 (Set progress = vb.openRemoteSession(session, mach.id, ""gui"", """") throws an error:

{{{
Line: 26
Column: 3
Error: The object does not support the proberty or method: 'vb.openRemoteSession'
Code: 800A01B6
Source: Run time error in Microsoft VBScript 
}}}
I've also replaced ""openRemoteSesstion"" by ""launchVMProcess"", with the only result that this is replaced in the error message, too.


----

So, is there any functional example on how to control a VM via COM?",sweber
20749,High cpu usage in guest on several cores causes severe host lagging.,Linux,VirtualBox 6.1.30,2021-12-24T18:55:56Z,2021-12-24T21:58:52Z,2021-12-24T21:58:52Z,"I have AMD Ryzen 3 3100 4-Core Processor hyperthreaded.
When I run atlas simulation job from lhc@home on virtualbox with 4 cores 
system starts to lag.",kotenok2000
20748,6.1.30.148432 Install Results in Extract Path Error,Linux,VirtualBox 6.1.30,2021-12-24T15:23:19Z,2021-12-24T15:31:48Z,2021-12-24T15:31:48Z,"Upon downloading the latest build and executing it I get the following error on Windows 10.

Failed to create extraction path 'C:\Users\ADMINI~1\AppData\Local\Temp\2\VirtualBox': VERR_PATH_NOT_FOUND

What I found is that the Temp\2 folder does not exist.  I manually created the 2 folder under temp and installation successfully completed after that.",Bruceman1
20746,Memory can't be read,BSD,VirtualBox 6.1.30,2021-12-23T23:22:14Z,2021-12-23T23:22:14Z,2021-12-23T23:22:14Z,Memory can't be read,MikhailRokhin
20743,VBox 6.1.x does not boot FreeBSD EFI,BSD,VirtualBox 6.1.30,2021-12-23T00:22:56Z,2021-12-23T00:22:56Z,2021-12-23T00:22:56Z,"Vbox 6.0.24 (or older) boots (FreeBSD) EFI images just fine.
Vbox 6.1.x (I've tried all versions) does not boot EFI but instead goes to network boot even if that's disabled for the VM.",adwsklerjuihgweiop
20737,after using save the machine state vm virtual box is not asking for login for next time,Linux,VirtualBox 6.1.30,2021-12-19T07:09:26Z,2021-12-19T07:09:26Z,2021-12-19T07:09:26Z,"hello,
i am using Virtual Box 6.1.30 and i am running kali linux in vm my main os or host machine is windows 11 
bug is that when i am selecting 'save the machine state'  before terminating the instance and after closing that machine when i start that machine again it's not asking for login credentials user and password
it's allowing to directly use that machine without login credentials the logged in user is the same before saving the machine state.
 
",AFTAB SAMA
20732,Win7 2 screen  boot failure,Windows,VirtualBox 6.1.30,2021-12-17T08:51:54Z,2021-12-17T08:51:54Z,2021-12-17T08:51:54Z,"virtual  Win7 , 2 screen,The startup failed after KB5008212 was installed.",km Senior electrician
20730,issue with Virtual box 6.1.3,Windows,VirtualBox 6.1.30,2021-12-16T04:02:33Z,2021-12-16T04:02:33Z,2021-12-16T04:02:33Z,"Hi,

After upgrading VBox from 6.1.26 to 6.1.3 and installing VBox guest client on VM server, Audio driver stop working (input & output). Please see below details, I found from VM log. Also, I was trying to revert it back from 6.1.3 to 6.1.26 along with installing the previous VBox guest client. however, still it does not work. Please share your feedback to solve the issue.     

00:01:45.238665 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:45.238766 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:46.147902 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:46.154942 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:01:46.155013 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:51.688116 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:51.703855 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:51.703903 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:52.830026 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:52.836064 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:52.836369 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:54.355233 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:54.368893 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:54.368967 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:01:55.936261 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:01:55.950584 WasAPI: IAudioClient::IsFormatSupported(,4ch S16 44100Hz,) failed: AUDCLNT_E_UNSUPPORTED_FORMAT
00:01:55.950695 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
00:02:14.811520 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
00:02:14.946336 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
00:02:14.946384 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE

01:26:10.523556 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:26:22.139051 Audio: Warning: Scheduling hint of stream '[WasAPI] Front:0' is bigger (140728898420746ms) than used period size (0ms)
01:26:22.153892 WasAPI: IAudioClient::IsFormatSupported(,2ch S16 44100Hz,) failed: E_INVALIDARG
01:26:22.153966 Audio: Failed to initialize stream '[WasAPI] Front:0': VERR_AUDIO_STREAM_COULD_NOT_CREATE
09:40:53.702393 Audio: Device configuration of driver 'WasAPI' has changed
09:40:53.798489 Audio: Device configuration of driver 'WasAPI' has changed
09:40:54.136774 Audio: Found 6 devices for driver 'WasAPI'
09:40:54.136808 Audio: Device 'Speakers / Headphones (Realtek Audio)':
09:40:54.136808 Audio:   ID              = {0.0.0.00000000}.{8c7e1b82-8bf9-4c4c-92f7-c198b06fdfe7}
09:40:54.136809 Audio:   Usage           = output
09:40:54.136809 Audio:   Flags           = DEFAULT_OUT
09:40:54.136810 Audio:   Input channels  = 0
09:40:54.136810 Audio:   Output channels = 2
09:40:54.136827 Audio: Device 'Speakers / Headphones (Realtek Audio)':
09:40:54.136827 Audio:   ID              = {0.0.0.00000000}.{8c7e1b82-8bf9-4c4c-92f7-c198b06fdfe7}
09:40:54.136827 Audio:   Usage           = output
09:40:54.136828 Audio:   Flags           = NONE
09:40:54.136828 Audio:   Input channels  = 0
09:40:54.136828 Audio:   Output channels = 2


",Reza-DATA-Engineer
20697,Guest Additions 6.1.28 and 6.1.30 cannot install Windows Server 2012 R2,Windows,VirtualBox 6.1.30,2021-11-28T07:19:38Z,2021-12-13T21:26:41Z,2021-12-13T21:26:41Z,"I've been running Windows Server 2012 R2, along with Windows 7, Windows Server 2016 and Windows Server 2019 guest virtual machines, on my  VirtualBox host, for several months now. 

Up until Guest Additions 6.1.26 (on VirtualBox 6.1.26) there was no serious problems installing those older Guest Additions from the applicable mounted *.ISO files, onto any of those aforementioned operating systems.

However as of Guest Additions 6.1.28 (on VirtualBox 6.1.28) and also now Guest Additions 6.1.30 (on VirtualBox 6.1.30), I am constantly getting an error which prevents Guest Additions to properly install on Windows Server 2012. The error is as follows (FYI I am only showing error for latest Guest Additions version):

-----------------------------------------------
Stopped logging into separate file
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Version: 6.1.30 (Rev 148432)
Previous version: 6.1.26 (Rev 145957)
Detected OS: Windows 8_1 (64-bit)
System Directory: C:\Windows\system32
Checking for installation requirements for Vista / Windows 7 / Windows 8 ...
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: DIFxAPI.dll... 100%
Extract: VBoxDrvInst.exe... 100%
Extract: VBoxVideo.inf... 100%
Extract: VBoxVideo.cat... 100%
Extract: iexplore.ico... 100%
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Stopping VBoxService ...
Stopping VBoxService via SCM ...
Stopping VBoxService done
Stopping VBoxTray ...
Stopping VBoxTray done
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: VBoxVideo.sys... 100%
Extract: vboxdisp.dll... 100%
Extract: VBoxMouse.sys... 100%
Extract: VBoxMouse.inf... 100%
Extract: vboxmouse.cat... 100%
Extract: VBoxGuest.sys... 100%
Extract: VBoxGuest.inf... 100%
Extract: vboxguest.cat... 100%
Extract: VBoxTray.exe... 100%
Extract: VBoxControl.exe... 100%
Extract: VBoxWHQLFake.exe... 100%
Output folder: C:\Windows\system32
Extract: VBoxService.exe... 100%
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Extract: vboxwddm.cat... 100%
Extract: VBoxWddm.sys... 100%
Extract: VBoxWddm.inf... 100%
Extract: vboxdispd3d.dll... 100%
Extract: vboxnine.dll... 100%
Extract: vboxsvga.dll... 100%
Extract: vboxicd.dll... 100%
Extract: vboxgl.dll... 100%
Extract: vboxdispd3d-x86.dll... 100%
Extract: vboxnine-x86.dll... 100%
Extract: vboxsvga-x86.dll... 100%
Extract: vboxicd-x86.dll... 100%
Extract: vboxgl-x86.dll... 100%
Extract: C:\Windows\system32\drivers\VBoxSF.sys... 100%
Skipped: C:\Windows\system32\VBoxMRXNP.dll
Extract: C:\Program Files\Oracle\VirtualBox Guest Additions\nseCA4C.tmp... 100%
Rename on reboot: C:\Program Files\Oracle\VirtualBox Guest Additions\nseCA4C.tmp->C:\Windows\system32\VBoxMRXNP.dll
Extract: C:\Windows\SysWOW64\VBoxMRXNP.dll... 100%
Extract: C:\Windows\system32\VBoxHook.dll... 100%
Installing drivers ...
Output folder: C:\Program Files\Oracle\VirtualBox Guest Additions
Installing guest driver ...
Executing: ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log""
Installing driver ...
INF-File: C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf
(1) ENTER:  DriverPackageInstallW
(1) RETURN: DriverPackageInstallW  (0xE0000244)
ERROR (e0000244): Unknown error!

Execution returned exit code: 2
Error excuting """"C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log"""" (exit code: 2) -- aborting installation
Error excuting """"C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxDrvInst.exe"" driver install ""C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf"" ""C:\Program Files\Oracle\VirtualBox Guest Additions\install_drivers.log"""" (exit code: 2) -- aborting installation
-----------------------------------------------

When I then click on the [Cancel] button, an error popup appears as per the attached file ""VBox Guest Additions (6.1.30) - Pop Up Screen (20211128).jpg"". According to that popup there should be a log file named ""install_ui.log"" in the directory shown. However no such log file is written to the drive. I searched the entire guest operating system drive to be sure it was not written to some other location but no such file exists.

I am including ""VBox Guest (6.1.30) - Operating System Version (20211128).jpg"" to show the version of the VirtualBox Guest that I have the bug on.

Although I am showing only the latest 6.1.30 addition error, I was receiving a similar error for Guest Additions 6.1.28. 

I was hoping 6.1.30 Guest Additions would resolve the problem, but it did not.

I have gone to the trouble of installing a brand new VirtualBox Guest OS running Windows Server 2012 R2, and applying all Microsoft security & critical patches applicable to the operating system, before I then tested Guest Additions 6.1.30. Alas I got the same error.

Just to clarify: Guest Additions 6.1.28 and 6.1.30 installed perfectly on Windows 7, Windows 2016 and Windows 2019 without a problem. I am only experiencing the problem with Windows Server 2012 R2.

END",CuriousPaul
20723,"Guest can't pick-up/use Host audio device (like BT or USB headset) after the device was physically reconnected/re-plugged (LOGS, STEPS)",Windows,VirtualBox 6.1.30,2021-12-13T01:16:59Z,2021-12-13T01:16:59Z,2021-12-13T01:16:59Z,"Pls advise on temporary workaround (if any), as it blocks from using some of audio devices with VirtualBox (greate solution, btw, thank you so much!)

Steps:
1 Choose some pluggable audio device on Host. It can be any - USB or Bluetooth/BT headset/headphones, behavior is the same
2 Play audio in Guest
3 Disconnect/unplug audio device physically from Host
4 Audio playback falls back properly to the newly selected Host audio device (like speakers of a laptop)
5 Plug-in/reconnect disconnected USB or BT audio device, ensure it's selected as default in Host and audio plays just fine from Host
6 Try to play audio from Guest
RESULT: silence, nothing audible
I've expected audio to play normally, but it can be done only if I restart Guest

What's interesting is that if after step 6 I switch Host's audio device to 
the fallback device (like laptop's speakers), I start to hear Guest's audio. So the audio itself is not broken in Guest.

What I've tried to do to get it back:
* Disable/enable Audio Out/In in VB's toolbar
* Mute/unmute, ensure that all is unmuted after reconnections
* Stop/Start audiosrv and AudioEndpointBuilder on both Host and Guest
    The only uncertain thing here is that after some sequence of Stop/Starts I think audio started to go out to proper device, but then I couldn't reproduce/restore exact sequence of starts/stops so I'm no longer shure it wasn't a misinterpretation.

Pls note that if to change audio device back and forth without disconnecting/unplugging it, all works fine as expected.
Just in case, speaking of BT device - it's connected to the Host's bluetooth not to the Guest bypassing Host (if to pass-through BT device ""Intel Corp. [0002]"" to Guest)

Please help to solve it and if possible, suggest temporary workaround for the issue (through CLI), so I can restore audio without a need to restart Guest.

I've attached two set of verbose logs, ""Audio issue - NOT OK unplugging"" represents the issue. ""Audio issue - OK changing without unplugging"" is for the simple change without unplugging (just in case).

Logs contains AUDCLNT_E_DEVICE_INVALIDATED and VERR_AUDIO_STREAM_NOT_READY
{{{
00:02:55.763182 WasAPI: GetCurrentPadding failed on '[WasAPI] Front:0': AUDCLNT_E_DEVICE_INVALIDATED
00:02:55.763232 WasAPI: GetCurrentPadding([WasAPI] Front:0) failed during playback: AUDCLNT_E_DEVICE_INVALIDATED (@0x0)
00:02:55.763265 Audio: @0x6fa0: Stream '[WasAPI] Front:0' pre-buffering commit problem: wrote 0x0 out of 0x6fa0 + 0x0 - rc=VERR_AUDIO_STREAM_NOT_READY *pcbWritten=0x20 PREBUF_COMMITTING -> PREBUF_COMMITTING
}}}

VB version is 6.1.30 r148432 (Qt5.6.2) but I've seen it on previous versions as well.

It looks like others experience similar issues, but they were primarily referring to Bluetooth devices, but the issue seems to be more generic and affects all detachable audio devices.
Just in case, other tickets are #20630, #20431

I've seen references to function `drvHostAudioWasHA_StreamPlay()`:
{{{
else
{
    LogRelMax(64, (""WasAPI: GetCurrentPadding(%s) failed during playback: %Rhrc (@%#RX64)\n"",
    pStreamWas->Cfg.szName, hrc, pStreamWas->offInternal));
    /** @todo reinit on AUDCLNT_E_DEVICEINVALIDATED? */
    rc = VERR_AUDIO_STREAM_NOT_READY;
    break;
}
}}}",PavloUnn
20716,Impossible to use VirtualBox Guest Addition on Linux Preempt RT Kernel,Linux,VirtualBox 6.1.30,2021-12-07T11:30:59Z,2021-12-07T11:30:59Z,2021-12-07T11:30:59Z,"I'm using Xubuntu 18.04 LTS as VM Guest (VirtualBox 6.1.28, I've tried with 6.1.30 also, Windows 10 Host).

If I'm using standard Linux kernels (4.x or 5.x), I'm able to install VirtualBox Guest Addition using the sudo ./autorun.sh command from the ISO mounted folder. No issue, working perfectly.

But If I'm using Linux Preempt RT Kernel, impossible to install VirtualBox Guest Addition. I've tried with Kernel 4.16.12-RT5, 5.14-RT19, 5.15.2-RT9. As a result, no shared folder, no mouse...
I've correctly compiled and installed linux-headers and linux-image corresponding to each Preempt RT kernel which are working correctly in standard PC.
The linux distribution is up to date using the sudo apt-get update, sudo apt-get upgrade, sudo apt-get dist-upgrade commands.
I've tried also to install virtualbox-dkms, dkms and virtualbox-guest-utils without any better result

It seems that the Virtualbox Guest Addition is not able to use to dedicated Preempt RT headers, even if they are set in linux kernel installation.

Please see the attached log for explanation.",oartigues
20713,Serial Port Hangs after xxxx Time,Windows,VirtualBox 6.1.30,2021-12-02T19:18:50Z,2021-12-02T19:18:50Z,2021-12-02T19:18:50Z,"An old VB6 application runs under Win XP which communicates with a controller via COM port 2.
The application always stops working after a certain period of time.
There was simply no more data sent.
The application was also unable to close the Com Port.
We tried 6.1.30 and 6.1.28 without success.
Now it has been running for several days thanks to version 5.2.44

It is certainly not a problem for the VB6 application, the error could also be reproduced with the HTERM program",mbi
20703,OVA import from Windows Explorer (file manager) does not enable Import button,all,VirtualBox 6.1.30,2021-12-01T18:16:27Z,2021-12-01T18:16:27Z,2021-12-01T18:16:27Z,"Cheers, got an UI bug in Windows edition with 6.1.30, I think it behaved differently with earlier releases: if I take an OVA file from Explorer and double-click it, VB UI opens and shows info from that OVA, but the Import button stays gray.

Now I have to go to file selector on the left and pick the same OVA and then I can Import it. This kinda defeats the purpose of double-clicking ;)

IIRC with earlier 6.1.x versions the import window layout looked different, but import via integration with Explorer ""just worked"".

",Jim Klimov
20702,"Execution of "".exe"" fails in shared folders, with Windows 10 or 11",Windows,VirtualBox 6.1.30,2021-12-01T14:42:25Z,2021-12-01T14:42:25Z,2021-12-01T14:42:25Z,"Host Windows 10. Guest Windows 10 or 11.
(Windows XP x32 and Windows 7 x64, work fine)

When an "".exe"" is run inside a shared folder, it gives the error ""The specified path does not exist"" depending on the number of characters in the path + the file name, and the text entered in ""Folder name"" (sharename).

Examples with mountpoint = ""X:"":

sharename = ""1"":
  OK    X:\1234567.exe

  NOK  X:\12345678.exe
sharename = ""12"":
  OK    X:\12345678.exe

  NOK  X:\123456789.exe
sharename = ""123"":
  OK    X:\123456789.exe

  NOK  X:\1234567890.exe
...
sharename = ""12345678"":
  OK    X:\12345678901234.exe

  NOK  X:\123456789012345.exe

Interestingly, the more characters sharename has, the more characters the "".exe"" file name allows.",FelixG
20692,No signature was present in the subject,other,VirtualBox 6.1.30,2021-11-26T02:00:10Z,2021-11-26T04:14:03Z,2021-11-26T04:14:03Z,"Cannot install VirtualBox due to failure installing VBoxUSB driver:
{{{
Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
}}}

When viewing the properties of VBoxUSB.inf it reports the following for the sha256 cert:
{{{
No signature was present in the subject
}}}

I have attached signtool output comparing VBoxUSB.sys and VBoxUSB.cat. The same cert is successfully validated on the .sys but fails on the .cat with ""No signature found"".

I am running a dev build of Windows 11, not currently sure whether this issue affects all Windows 11.

Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=104557",sgadsby
20856,Windows Vista Ultimate 64 Bit Guest Additions not working,Windows,VirtualBox 6.1.32,2022-03-05T13:24:59Z,2022-08-19T03:55:41Z,2022-08-19T03:55:41Z,"I am using Windows Vista Ultimate 64 Bit and I wanted to install Guest Additions so I can use Windows Aero Theme but I get an error when installing Guest Additions. The error says Error excuting (Yes spelled exactly like dat) C:\Program Files\Oracle\VirtualBox Guest Additions\VboxDrvInst.exe 
And I allowed whatever prompt I got.",Aremon
20879,Error creating a new Host Network Manager,other,VirtualBox 6.1.32,2022-03-24T11:15:50Z,2022-08-06T09:35:15Z,2022-08-06T09:35:15Z,"When I try to create a new Host Network Manager I receive this error:

Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-6.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Utf8Str,class com::Utf8Str,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0046).
Please contact the product vendor!.

I am running a 6.1.3 version on a Windows 11 Microsoft Surface Laptop.",mestebanpt
20999,Ubuntu 22.04 freezes - Windows 11,Linux,VirtualBox 6.1.32,2022-06-21T16:26:35Z,2022-07-09T23:40:51Z,2022-07-09T23:40:51Z,"I have windows 11, and I downloaded virtualbox 6.1 and installed Ubuntu 22 04. I followd this tutorial (https://www.youtube.com/watch?v=EQy9AUVuyF0&t=1s) step by step.

Ubuntu finished installation without any issues, but when I try to run it, it seems to get stuck. A snapshot is visible at (https://askubuntu.com/questions/1415045/ubuntu-22-04-seems-to-freeze-in-virtualbox-6-1-on-windows-11)

I have tried restarting my computer, but nothing seems to work. Can anyone help with the solution? Thanks in advance.

",user17302
20903,[feature request][Windows] embedding a manifest into the exe/dll,all,VirtualBox 6.1.32,2022-04-16T01:47:00Z,2022-07-05T20:13:43Z,2022-07-05T20:13:43Z,"Windows Host:  
none of the binaries (exe/dll) include any manifest.

I've done some testing, with a generic manifest I've suited for all of the files,  
with 'compatibility' for running the app outside of Windows 10 vista virtualization, 'DPI awareness' and the text rendering was amazingly crispy, and 'segmented heap' which seems to improve the program stack handling. I even through in 'long-path awareness' just because I've could.

normally I would patched the embedded (resource-24),  
but it seems that Windows Defender don't like me to do that on signed programs, 

so I've just placed a copy of a '.manifest' for each of the files in c:\Program Files\Oracle\VirtualBox (for example 'VirtualBox.exe.manifest') using 
https://github.com/eladkarako/manifest/blob/master/example_manifests/generic.manifest  

and it seems to do the job. 

I did had to apply this registry patch to make it work,  

{{{
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
""PreferExternalManifest""=dword:00000001
}}}

still, runs fine.


I'm still testing the overall performances,  
but I can say the GUI is super clear and sharp,  
I'm using a 150% DPI on my screen, which always seems to show things a bit blurry. and that fixed it completely, the controls seems to keep their place correctly (sometimes DPI awareness makes controls leak their position).

using the new Windows 10 segmented heap seems to help with memory allocation somewhat, but I'm still stress testing.

as for long-path awareness,  
I do have a registry patch to opt-in the feature as explained in:  

https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd#enable-long-paths-in-windows-10-version-1607-and-later

but I don't have any machines on an especially long paths.

however, I know it might help with machines placed on quirky remote locations as well. 


I strongly suggest applying this nice and easy (no actual code modification is required) fix, the results are amazing (at least as for memory consumption with the segmented heap and GUI crispiness).
",Elad Karako
20794,Mouse (in both guest and host) behaves strangely when captured.,Windows,VirtualBox 6.1.32,2022-01-28T07:57:13Z,2022-07-02T07:27:42Z,2022-07-02T07:27:42Z,"This bug is new to version 6.x (not sure the exact version it started in, as I just upgraded to 6.1.32 from a 5.x version a few days ago). Also, this bug only happens when using mouse capture (not when using mouse integration). I don't think it's dependent on the guest OS, as it has an impact on the host mouse cursor as well as the guest, but it may be dependent on the host OS (not sure if Linux version of VBox has this bug, as my PC only has Windows on it). It also doesn't matter if it's using capture instead of integration due to Guest Additions not being installed, or due to the mouse integration part of Guest Additions being manually disabled.

The bug causes the the host mouse cursor to be locked into a rectangular region of the screen, which is located in the upper-left hand corner of the host computer screen. It doesn't matter where the guest window is. The locked in rectangle is always in the upper-left corner of the host screen. If you use the mouse to try scroll the cursor out it wraps around.

On the guest side, the moment you move the mouse after capturing the mouse, the guest mouse cursor completely disappears. This aspect of the bug may be dependent on the guest OS, but I haven't tried it in any guest OS other than Windows, so I can't verify this.

As I don't have technical knowledge of the internals of VirtualBox, I don't know what component is responsible for this bug, so I have left that set to ""other"" on this bug report form.

I've attached a video I recorded of my screen using my cellphone camera showing this issue. It shows how it only has an impact when mouse capture is being used, by running an OS with Guest Additions with mouse integration, and then I disable the integration and let the mouse get captured, where the bug then becomes immediately obvious.",Ben321
21011,guestcontrol in terminated state right after using it on a just restored online snapshot,Windows,VirtualBox 6.1.32,2022-06-28T12:33:40Z,2022-06-28T12:33:40Z,2022-06-28T12:33:40Z,"It seems that the guestcontrol interface goes into terminating state, right after an online snapshot has been restored of a VM (windows 10 image).

This is a problem I detected on a VM with 6.1.32 vbox guest additions installed. This problem is not present on a VM with 6.0.4 vbox guest additions installed.

Steps to reproduce:
{{{
1) load OVA (win10 OVA in my case)
2) start VM and create online snapshot
3) poweroff VM
4) restore online snapshot taken in step 2
5) start VM, now the VM will jumpstart into the (online) machine state as saved in step 2
6) execute a guestcontrol command from the host immediately after step 5
}}}

After step 6, the guestcontrol command returns with this kind of error:
""VBoxManage.exe: error: Error starting guest session (current status is: terminated)""

The best way to reproduce the error is to automate the steps as it seems some race condition being the rootcause here. These were the simple steps I had in my batch script to reproduce the issue:

{{{
@echo off

set VM_NAME=win10_10.0.17_clean

echo restore snapshot on %VM_NAME%
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" snapshot %VM_NAME% restore ""online_snapshot""

echo start VM %VM_NAME%
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" startvm %VM_NAME%

rem echo zzzzz
rem sleep 1

echo execute command via guest control interface
""C:\Program Files\Oracle\VirtualBox\VBoxManage.exe"" guestcontrol %VM_NAME% run --putenv ""USERNAME=user"" --username user --password user  --wait-stdout --wait-stderr --timeout 600000 cmd.exe -- /C ipconfig
}}}

Executing this sequence on a VM with 6.1.32 vbox guest additions results in the mentioned 'terminated' state of the guestcontrol interface. There is not other way to get out of that, by just rebooting the VM. Otherwise, the guestcontrol interface remains in 'terminated' state.

If there is tiny sleep between step 5 & 6 (as can also be seen in the script) the issue is not there, and the command is executed succesfully.

So it seems some sort of race condition.

I have attached some logging. You will see that whenever the issue is there the logs show 'VERR_NOT_FOUND' errors:

NOK -->
{{{
00:00:09.268742 VMMDev: Guest Log: 14:01:20.520064 main     VBoxService 6.1.32 r149290 (verbosity: 0) win.amd64 (Jan 13 2022 19:13:21) release log
00:00:09.268766 VMMDev: Guest Log: 14:01:20.520064 main     Log opened 2022-06-27T14:01:20.520064800Z
00:00:09.268834 VMMDev: Guest Log: 14:01:20.522599 main     OS Product: Windows 10
00:00:09.268864 VMMDev: Guest Log: 14:01:20.522599 main     OS Release: 10.0.17763
00:00:09.268919 VMMDev: Guest Log: 14:01:20.522696 main     OS Service Pack: 
00:00:09.268946 VMMDev: Guest Log: 14:01:20.522696 main     Executable: C:\Windows\System32\VBoxService.exe
00:00:09.268953 VMMDev: Guest Log: 14:01:20.522696 main     Process ID: 5272
00:00:09.268957 VMMDev: Guest Log: 14:01:20.522696 main     Package type: WINDOWS_64BITS_GENERIC
00:00:09.268983 VMMDev: Guest Log: 14:01:20.522696 main     Hi, this is guest session ID=1
00:00:09.269316 VMMDev: Guest Log: 14:01:20.523084 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:09.269585 VMMDev: Guest Log: 14:01:20.523084 main     Error: Failed to accept session 57 (client ID 1): VERR_NOT_FOUND
00:00:09.269628 VMMDev: Guest Log: 14:01:20.523084 main     Error: Setting message filterAdd=0x1 failed with rc=VERR_NOT_FOUND
}}}

In the VM with guest additions 6.0.4 these errors do not pop up and the logs look like this:
{{{
00:00:10.154777 VMMDev: Guest Log: 11:24:33.124468 main     VBoxService 6.0.4 r128413 (verbosity: 0) win.amd64 (Jan 25 2019 18:38:16) release log
00:00:10.154798 VMMDev: Guest Log: 11:24:33.124468 main     Log opened 2022-06-28T11:24:33.124468000Z
00:00:10.154834 VMMDev: Guest Log: 11:24:33.124468 main     OS Product: Windows 10
00:00:10.154862 VMMDev: Guest Log: 11:24:33.124468 main     OS Release: 10.0.17763
00:00:10.154888 VMMDev: Guest Log: 11:24:33.124468 main     OS Service Pack: 
00:00:10.154915 VMMDev: Guest Log: 11:24:33.124468 main     Executable: C:\Windows\System32\VBoxService.exe
00:00:10.154923 VMMDev: Guest Log: 11:24:33.124468 main     Process ID: 5212
00:00:10.154928 VMMDev: Guest Log: 11:24:33.124468 main     Package type: WINDOWS_64BITS_GENERIC
00:00:10.154957 VMMDev: Guest Log: 11:24:33.124468 main     Hi, this is guest session ID=1
00:00:10.155536 RTC: period=0x10 (16) 2048 Hz
00:00:10.155670 VMMDev: Guest Log: 11:24:33.140222 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
00:00:10.171222 RTC: period=0x10 (16) 2048 Hz
00:00:10.186838 RTC: period=0x10 (16) 2048 Hz
00:00:10.188166 VMMDev: Guest Log: 11:24:33.171524 main     Session 1 is about to close ...
00:00:10.188261 VMMDev: Guest Log: 11:24:33.171524 main     Stopping all guest processes ...
00:00:10.188293 VMMDev: Guest Log: 11:24:33.171524 main     Closing all guest files ...
00:00:10.188324 VMMDev: Guest Log: 11:24:33.171524 main     Session 1 ended

}}}

For reproduction of the issue I am using Vbox version 6.1.32 with a VM using guest additions 6.1.32.",Mayhem
21010,mouse sluggish,Windows,VirtualBox 6.1.32,2022-06-26T23:03:10Z,2022-06-26T23:03:10Z,2022-06-26T23:03:10Z,I have windows 10 on my main pc and windows 7 on vb. When I click on something my mouse gets sluggish and you can actually see where the arrow is through out the movement. I haven't been able to find a work around. ,novalore40
21001,la instalacion viene rota,other,VirtualBox 6.1.32,2022-06-21T18:56:31Z,2022-06-21T19:10:27Z,2022-06-21T19:10:27Z,lo intalo despues de mucho tiempo sin instalarlo (pq antes el año pasado lo tenia instalado) viene con error critico y no abria asi q  abri el setup para repararlo y me encuentro q no se puede reparar,xd64
20983,Will crash everytime after WIFI router rebooted.,Windows,VirtualBox 6.1.32,2022-06-13T20:29:27Z,2022-06-13T20:29:27Z,2022-06-13T20:29:27Z,"VBOX will always crash and exit with ""Application Error"" after WIFI router rebooted, don't know why still, hope you can fix it soon, thanks.",gvvice
20973,guru meditation,Windows,VirtualBox 6.1.32,2022-06-08T15:15:08Z,2022-06-08T15:15:08Z,2022-06-08T15:15:08Z,"Hello.

With the last update of the VirtualBox, I have a problem with the Virtual Machines.

The host is in Windows 7 - 64 bits.

When the Virtual Machine starts, sometimes show the guru meditation.

I attach the files if somebody can help me.

Thanks for all.",Ino
20940,Unable to boot any VM (Ubuntu): kernel panic - not syncing attempted to kill the idle task,Linux,VirtualBox 6.1.32,2022-05-13T09:25:19Z,2022-06-08T08:42:34Z,2022-06-08T08:42:34Z,"Hello everyone.

I can't boot any of my VMs in Virtualbox. I have several VMs with different versions of Ubuntu, specifically Ubuntu 12 and Ubuntu 20. The same problem occurs in all of them when starting, getting on the screen: ""kernel panic - not syncing attempted to kill the idle task "". Attached log. I have tried to generate a new VM with Ubuntu 12, but I get the same problem. Thanks for your help.",pmartinezOracle
20951,"Después de desconectar segundo monitor, la máquina virtual sigue intentando mostrarse allí",Windows,VirtualBox 6.1.32,2022-05-20T16:44:03Z,2022-05-20T16:44:03Z,2022-05-20T16:44:03Z,"Ayer trabajé con un monitor adicional a mi computadora.  Abrí una máquina virtual y la desplegué en el monitor externo.
Hoy ya no tengo ese monitor.  Abrí VirtualBox, abro la misma máquina virtual de ayer, pero no se despliega en la pantalla del computador, el problema es que se está desplegando en el monitor externo que ya no tengo conectado.
Bajé todas las ventanas (Win+D) para intentar ver la máquina virtual, pero no hay forma.",renezito
20945,Corner dragging second dual monitor screen causes monitor close without warning,Linux,VirtualBox 6.1.32,2022-05-17T00:46:57Z,2022-05-17T00:46:57Z,2022-05-17T00:46:57Z,"Using the cursor and left clicking the double arrow to expand/contract monitor 2 will cause the monitor to suddenly close with no warning.

You have to go back to the View menu and click on ""Enable"" Virtual Screen 2 to reopen it.

Using Minimize/Maximize buttons on Virtual Screen work as normal.  The sudden close only happens when dragging the corner to resize it.

System: Unbuntu 20.4
Virtual Box: Oracle VM Virtual Box 6.1
    In VBox Settings assigned Video settings 40MB


It's a minor issue, just thought engineering might want to know it exists, should be duplicable.",Tony C
20921,After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work,Linux,VirtualBox 6.1.32,2022-04-29T17:53:51Z,2022-04-30T19:42:55Z,2022-04-30T19:42:55Z,"After upgrade guest to Ubuntu 22.04 LTS screen and mouse doesn't work

See please video: https://drive.google.com/file/d/1C0IOJlqY-n71PDoVgYfVfrsuHKaUMnvD/view?usp=sharing",Ilia Poliakov
20880,No Sound,Linux,VirtualBox 6.1.32,2022-03-24T21:40:57Z,2022-04-26T17:50:26Z,2022-04-26T17:50:26Z,"6.0.18 Kali 2022.1 vm.  No sound.  6.0.24 Kali 2022.2. No sound.  6.1.32 r149290 (Qt5.6.2) Kali 2022.1.  No sound.  Tried removing vbox and reinstall. Tried Ubuntu desktop latest distro.  No sound.  

Any advice would be great and thank you.  I love vbox.

Log:
{{{

00:00:04.300986 VirtualBox VM 6.1.32 r149290 win.amd64 (Jan 17 2022 11:29:30) release log
00:00:04.300991 Log opened 2022-03-24T05:10:51.555341700Z
00:00:04.300992 Build Type: release
00:00:04.300996 OS Product: Windows 7
00:00:04.300997 OS Release: 6.1.7601
00:00:04.300998 OS Service Pack: 1
00:00:04.555010 DMI Product Name: 0914                            
00:00:04.562185 DMI Product Version: Ideapad Z560                    
00:00:04.563273 Firmware type: BIOS
00:00:04.563288 Host RAM: 7990MB (7.8GB) total, 5148MB (5.0GB) available
00:00:04.563294 Executable: E:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:04.563296 Process ID: 4100
00:00:04.563297 Package type: WINDOWS_64BITS_GENERIC
00:00:04.565222 Installed Extension Packs:
00:00:04.565361   Oracle VM VirtualBox Extension Pack (Version: 6.1.32 r149290; VRDE Module: VBoxVRDP)
00:00:04.567121 Console: Machine state changed to 'Starting'
00:00:04.567375 Qt version: 5.6.2
00:00:04.571103 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:04.773997 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:04.774024 SUP: seg #1: R X 0x00001000 LB 0x00109000
00:00:04.774027 SUP: seg #2: R   0x0010a000 LB 0x0004a000
00:00:04.774031 SUP: seg #3: RW  0x00154000 LB 0x00013000
00:00:04.774048 SUP: seg #4: R   0x00167000 LB 0x0000e000
00:00:04.774051 SUP: seg #5: RW  0x00175000 LB 0x00003000
00:00:04.774054 SUP: seg #6: R   0x00178000 LB 0x0000b000
00:00:04.774057 SUP: seg #7: RWX 0x00183000 LB 0x00002000
00:00:04.774060 SUP: seg #8: R   0x00185000 LB 0x00007000
00:00:04.775744 SUP: Loaded VMMR0.r0 (E:\Program Files\Oracle\VirtualBox\VMMR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:04.775804 SUP: VMMR0EntryEx located at XXXXXXXXXXXXXXXX and VMMR0EntryFast at XXXXXXXXXXXXXXXX
00:00:04.775807 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\VMMR0.r0=0xXXXXXXXXXXXXXXXX
00:00:04.777776 Guest OS type: 'Debian_64'
00:00:04.778741 fHMForced=true - No raw-mode support in this build!
00:00:04.782637 File system of 'C:\Users\Home\Downloads\kali-linux-2022.1-installer-amd64.iso' (DVD) is ntfs
00:00:04.786993 File system of 'E:\Users\Home\VirtualBox VMs\Kali\Snapshots' (snapshots) is unknown
00:00:04.787013 File system of 'E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi' is ntfs
00:00:04.824560 Shared Clipboard: Service loaded
00:00:04.824585 Shared Clipboard: Mode: Bidirectional
00:00:04.824698 Shared Clipboard: Service running in normal mode
00:00:04.845565 Drag and drop service loaded
00:00:04.845590 Drag and drop mode: Bidirectional
00:00:04.869561 ************************* CFGM dump *************************
00:00:04.869566 [/] (level 0)
00:00:04.869572   CpuExecutionCap   <integer> = 0x0000000000000064 (100)
00:00:04.869576   EnablePAE         <integer> = 0x0000000000000000 (0)
00:00:04.869580   HMEnabled         <integer> = 0x0000000000000001 (1)
00:00:04.869582   MemBalloonSize    <integer> = 0x0000000000000000 (0)
00:00:04.869584   Name              <string>  = ""Kali"" (cb=5)
00:00:04.869586   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:04.869589   PageFusionAllowed <integer> = 0x0000000000000000 (0)
00:00:04.869591   RamHoleSize       <integer> = 0x0000000020000000 (536 870 912, 512 MB)
00:00:04.869595   RamSize           <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
00:00:04.869601   TimerMillies      <integer> = 0x000000000000000a (10)
00:00:04.869603   UUID              <bytes>   = ""c6 81 a3 0c 11 15 18 46 a8 9b 22 69 d5 9b 31 1f"" (cb=16)
00:00:04.869680 
00:00:04.869682 [/CPUM/] (level 1)
00:00:04.869685   GuestCpuName       <string>  = ""host"" (cb=5)
00:00:04.869687   NestedHWVirt       <integer> = 0x0000000000000000 (0)
00:00:04.869689   PortableCpuIdLevel <integer> = 0x0000000000000000 (0)
00:00:04.869691   SpecCtrl           <integer> = 0x0000000000000000 (0)
00:00:04.869694 
00:00:04.869694 [/CPUM/IsaExts/] (level 2)
00:00:04.869700 
00:00:04.869700 [/DBGC/] (level 1)
00:00:04.869701   GlobalInitScript <string>  = ""C:\Users\Home\.VirtualBox/dbgc-init"" (cb=36)
00:00:04.869702   HistoryFile      <string>  = ""C:\Users\Home\.VirtualBox/dbgc-history"" (cb=39)
00:00:04.869703   LocalInitScript  <string>  = ""E:\Users\Home\VirtualBox VMs\Kali/dbgc-init"" (cb=44)
00:00:04.869704 
00:00:04.869704 [/DBGF/] (level 1)
00:00:04.869705   Path <string>  = ""E:\Users\Home\VirtualBox VMs\Kali/debug/;E:\Users\Home\VirtualBox VMs\Kali/;cache*E:\Users\Home\VirtualBox VMs\Kali/dbgcache/;C:\Users\Home\"" (cb=141)
00:00:04.869706 
00:00:04.869706 [/Devices/] (level 1)
00:00:04.869707 
00:00:04.869707 [/Devices/8237A/] (level 2)
00:00:04.869708 
00:00:04.869708 [/Devices/8237A/0/] (level 3)
00:00:04.869709   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869710 
00:00:04.869710 [/Devices/GIMDev/] (level 2)
00:00:04.869711 
00:00:04.869711 [/Devices/GIMDev/0/] (level 3)
00:00:04.869713   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869713 
00:00:04.869713 [/Devices/VMMDev/] (level 2)
00:00:04.869714 
00:00:04.869715 [/Devices/VMMDev/0/] (level 3)
00:00:04.869716   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869717   PCIDeviceNo   <integer> = 0x0000000000000004 (4)
00:00:04.869718   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869718   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869719 
00:00:04.869719 [/Devices/VMMDev/0/Config/] (level 4)
00:00:04.869720   GuestCoreDumpDir <string>  = ""E:\Users\Home\VirtualBox VMs\Kali\Snapshots"" (cb=44)
00:00:04.869722 
00:00:04.869722 [/Devices/VMMDev/0/LUN#0/] (level 4)
00:00:04.869723   Driver <string>  = ""HGCM"" (cb=5)
00:00:04.869724 
00:00:04.869724 [/Devices/VMMDev/0/LUN#0/Config/] (level 5)
00:00:04.869725   Object <integer> = 0x0000000008ae67f0 (145 647 600)
00:00:04.869726 
00:00:04.869726 [/Devices/VMMDev/0/LUN#999/] (level 4)
00:00:04.869728   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869728 
00:00:04.869728 [/Devices/VMMDev/0/LUN#999/Config/] (level 5)
00:00:04.869730   First   <integer> = 0x0000000000000000 (0)
00:00:04.869730   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869731   papLeds <integer> = 0x0000000003eef1c8 (65 991 112)
00:00:04.869732 
00:00:04.869732 [/Devices/acpi/] (level 2)
00:00:04.869733 
00:00:04.869734 [/Devices/acpi/0/] (level 3)
00:00:04.869735   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869736   PCIDeviceNo   <integer> = 0x0000000000000007 (7)
00:00:04.869736   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869737   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869738 
00:00:04.869738 [/Devices/acpi/0/Config/] (level 4)
00:00:04.869740   CpuHotPlug          <integer> = 0x0000000000000000 (0)
00:00:04.869741   FdcEnabled          <integer> = 0x0000000000000000 (0)
00:00:04.869742   HostBusPciAddress   <integer> = 0x0000000000000000 (0)
00:00:04.869743   HpetEnabled         <integer> = 0x0000000000000000 (0)
00:00:04.869743   IOAPIC              <integer> = 0x0000000000000001 (1)
00:00:04.869744   IocPciAddress       <integer> = 0x0000000000010000 (65 536)
00:00:04.869745   NumCPUs             <integer> = 0x0000000000000002 (2)
00:00:04.869746   Parallel0IoPortBase <integer> = 0x0000000000000000 (0)
00:00:04.869747   Parallel0Irq        <integer> = 0x0000000000000000 (0)
00:00:04.869747   Parallel1IoPortBase <integer> = 0x0000000000000000 (0)
00:00:04.869748   Parallel1Irq        <integer> = 0x0000000000000000 (0)
00:00:04.869749   Serial0IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:04.869749   Serial0Irq          <integer> = 0x0000000000000000 (0)
00:00:04.869750   Serial1IoPortBase   <integer> = 0x0000000000000000 (0)
00:00:04.869751   Serial1Irq          <integer> = 0x0000000000000000 (0)
00:00:04.869752   ShowCpu             <integer> = 0x0000000000000001 (1)
00:00:04.869752   ShowRtc             <integer> = 0x0000000000000000 (0)
00:00:04.869753   SmcEnabled          <integer> = 0x0000000000000000 (0)
00:00:04.869754 
00:00:04.869754 [/Devices/acpi/0/LUN#0/] (level 4)
00:00:04.869755   Driver <string>  = ""ACPIHost"" (cb=9)
00:00:04.869756 
00:00:04.869756 [/Devices/acpi/0/LUN#0/Config/] (level 5)
00:00:04.869758 
00:00:04.869758 [/Devices/acpi/0/LUN#1/] (level 4)
00:00:04.869759   Driver <string>  = ""ACPICpu"" (cb=8)
00:00:04.869759 
00:00:04.869760 [/Devices/acpi/0/LUN#1/Config/] (level 5)
00:00:04.869761 
00:00:04.869761 [/Devices/ahci/] (level 2)
00:00:04.869762 
00:00:04.869762 [/Devices/ahci/0/] (level 3)
00:00:04.869764   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869765   PCIDeviceNo   <integer> = 0x000000000000000d (13)
00:00:04.869766   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869766   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869767 
00:00:04.869767 [/Devices/ahci/0/Config/] (level 4)
00:00:04.869768   Bootable  <integer> = 0x0000000000000001 (1)
00:00:04.869769   PortCount <integer> = 0x0000000000000001 (1)
00:00:04.869770 
00:00:04.869770 [/Devices/ahci/0/Config/Port0/] (level 5)
00:00:04.869771   Hotpluggable <integer> = 0x0000000000000000 (0)
00:00:04.869772 
00:00:04.869772 [/Devices/ahci/0/LUN#0/] (level 4)
00:00:04.869773   Driver <string>  = ""VD"" (cb=3)
00:00:04.869774 
00:00:04.869774 [/Devices/ahci/0/LUN#0/Config/] (level 5)
00:00:04.869776   BlockCache <integer> = 0x0000000000000001 (1)
00:00:04.869777   Format     <string>  = ""VDI"" (cb=4)
00:00:04.869778   Mountable  <integer> = 0x0000000000000000 (0)
00:00:04.869778   Path       <string>  = ""E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi"" (cb=43)
00:00:04.869779   Type       <string>  = ""HardDisk"" (cb=9)
00:00:04.869780   UseNewIo   <integer> = 0x0000000000000001 (1)
00:00:04.869781 
00:00:04.869781 [/Devices/ahci/0/LUN#0/Config/Plugins/] (level 6)
00:00:04.869782 
00:00:04.869783 [/Devices/ahci/0/LUN#0/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:04.869784   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:04.869785 
00:00:04.869785 [/Devices/ahci/0/LUN#0/Config/VDConfig/] (level 6)
00:00:04.869787   AllocationBlockSize <string>  = ""1048576"" (cb=8)
00:00:04.869787 
00:00:04.869788 [/Devices/ahci/0/LUN#999/] (level 4)
00:00:04.869789   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869790 
00:00:04.869790 [/Devices/ahci/0/LUN#999/Config/] (level 5)
00:00:04.869791   DeviceInstance        <string>  = ""ahci/0"" (cb=7)
00:00:04.869792   First                 <integer> = 0x0000000000000000 (0)
00:00:04.869793   Last                  <integer> = 0x0000000000000000 (0)
00:00:04.869794   pConsole              <integer> = 0x0000000003eeddd0 (65 986 000)
00:00:04.869795   papLeds               <integer> = 0x0000000003eee5d0 (65 988 048)
00:00:04.869796   pmapMediumAttachments <integer> = 0x0000000003eef1e8 (65 991 144)
00:00:04.869797 
00:00:04.869797 [/Devices/apic/] (level 2)
00:00:04.869798 
00:00:04.869799 [/Devices/apic/0/] (level 3)
00:00:04.869800   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869800 
00:00:04.869801 [/Devices/apic/0/Config/] (level 4)
00:00:04.869802   IOAPIC  <integer> = 0x0000000000000001 (1)
00:00:04.869803   Mode    <integer> = 0x0000000000000003 (3)
00:00:04.869803   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:04.869804 
00:00:04.869804 [/Devices/e1000/] (level 2)
00:00:04.869805 
00:00:04.869805 [/Devices/e1000/0/] (level 3)
00:00:04.869806   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869807   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:04.869808   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869808   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869809 
00:00:04.869809 [/Devices/e1000/0/Config/] (level 4)
00:00:04.869810   AdapterType    <integer> = 0x0000000000000000 (0)
00:00:04.869811   CableConnected <integer> = 0x0000000000000001 (1)
00:00:04.869812   LineSpeed      <integer> = 0x0000000000000000 (0)
00:00:04.869813   MAC            <bytes>   = ""08 00 27 79 fa 01"" (cb=6)
00:00:04.869814 
00:00:04.869814 [/Devices/e1000/0/LUN#0/] (level 4)
00:00:04.869815   Driver <string>  = ""NAT"" (cb=4)
00:00:04.869816 
00:00:04.869816 [/Devices/e1000/0/LUN#0/Config/] (level 5)
00:00:04.869818   AliasMode       <integer> = 0x0000000000000000 (0)
00:00:04.869819   BootFile        <string>  = ""Kali.pxe"" (cb=9)
00:00:04.869819   DNSProxy        <integer> = 0x0000000000000000 (0)
00:00:04.869820   Network         <string>  = ""10.0.2.0/24"" (cb=12)
00:00:04.869821   PassDomain      <integer> = 0x0000000000000001 (1)
00:00:04.869822   TFTPPrefix      <string>  = ""C:\Users\Home\.VirtualBox\TFTP"" (cb=31)
00:00:04.869823   UseHostResolver <integer> = 0x0000000000000000 (0)
00:00:04.869823 
00:00:04.869823 [/Devices/e1000/0/LUN#999/] (level 4)
00:00:04.869825   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869825 
00:00:04.869826 [/Devices/e1000/0/LUN#999/Config/] (level 5)
00:00:04.869827   First   <integer> = 0x0000000000000000 (0)
00:00:04.869828   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869828   papLeds <integer> = 0x0000000003eef0a8 (65 990 824)
00:00:04.869829 
00:00:04.869829 [/Devices/i8254/] (level 2)
00:00:04.869830 
00:00:04.869831 [/Devices/i8254/0/] (level 3)
00:00:04.869832 
00:00:04.869832 [/Devices/i8254/0/Config/] (level 4)
00:00:04.869833 
00:00:04.869833 [/Devices/i8259/] (level 2)
00:00:04.869834 
00:00:04.869834 [/Devices/i8259/0/] (level 3)
00:00:04.869835   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869836 
00:00:04.869836 [/Devices/i8259/0/Config/] (level 4)
00:00:04.869837 
00:00:04.869837 [/Devices/ichac97/] (level 2)
00:00:04.869838 
00:00:04.869838 [/Devices/ichac97/0/] (level 3)
00:00:04.869839   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869840   PCIDeviceNo   <integer> = 0x0000000000000005 (5)
00:00:04.869841   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869841   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869842 
00:00:04.869842 [/Devices/ichac97/0/AudioConfig/] (level 4)
00:00:04.869843 
00:00:04.869844 [/Devices/ichac97/0/Config/] (level 4)
00:00:04.869845   Codec        <string>  = ""AD1980"" (cb=7)
00:00:04.869846   DebugEnabled <integer> = 0x0000000000000000 (0)
00:00:04.869846 
00:00:04.869847 [/Devices/ichac97/0/LUN#0/] (level 4)
00:00:04.869848   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869848 
00:00:04.869849 [/Devices/ichac97/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.869850   Driver <string>  = ""HostAudioWas"" (cb=13)
00:00:04.869851 
00:00:04.869851 [/Devices/ichac97/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.869852   VmName <string>  = ""Kali"" (cb=5)
00:00:04.869853   VmUuid <string>  = ""0ca381c6-1511-4618-a89b-2269d59b311f"" (cb=37)
00:00:04.869853 
00:00:04.869854 [/Devices/ichac97/0/LUN#0/Config/] (level 5)
00:00:04.869855   DriverName    <string>  = ""HostAudioWas"" (cb=13)
00:00:04.869856   InputEnabled  <integer> = 0x0000000000000000 (0)
00:00:04.869857   OutputEnabled <integer> = 0x0000000000000001 (1)
00:00:04.869857 
00:00:04.869857 [/Devices/ichac97/0/LUN#1/] (level 4)
00:00:04.869859   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869859 
00:00:04.869860 [/Devices/ichac97/0/LUN#2/] (level 4)
00:00:04.869861   Driver <string>  = ""AUDIO"" (cb=6)
00:00:04.869861 
00:00:04.869861 [/Devices/ioapic/] (level 2)
00:00:04.869862 
00:00:04.869863 [/Devices/ioapic/0/] (level 3)
00:00:04.869864   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869864 
00:00:04.869864 [/Devices/ioapic/0/Config/] (level 4)
00:00:04.869865   NumCPUs <integer> = 0x0000000000000002 (2)
00:00:04.869866 
00:00:04.869866 [/Devices/mc146818/] (level 2)
00:00:04.869867 
00:00:04.869868 [/Devices/mc146818/0/] (level 3)
00:00:04.869869 
00:00:04.869869 [/Devices/mc146818/0/Config/] (level 4)
00:00:04.869870   UseUTC <integer> = 0x0000000000000001 (1)
00:00:04.869871 
00:00:04.869871 [/Devices/parallel/] (level 2)
00:00:04.869871 
00:00:04.869872 [/Devices/pcarch/] (level 2)
00:00:04.869873 
00:00:04.869873 [/Devices/pcarch/0/] (level 3)
00:00:04.869874   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869874 
00:00:04.869875 [/Devices/pcarch/0/Config/] (level 4)
00:00:04.869876 
00:00:04.869876 [/Devices/pcbios/] (level 2)
00:00:04.869877 
00:00:04.869877 [/Devices/pcbios/0/] (level 3)
00:00:04.869878   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869879 
00:00:04.869879 [/Devices/pcbios/0/Config/] (level 4)
00:00:04.869881   APIC               <integer> = 0x0000000000000001 (1)
00:00:04.869882   BootDevice0        <string>  = ""FLOPPY"" (cb=7)
00:00:04.869883   BootDevice1        <string>  = ""DVD"" (cb=4)
00:00:04.869884   BootDevice2        <string>  = ""IDE"" (cb=4)
00:00:04.869885   BootDevice3        <string>  = ""NONE"" (cb=5)
00:00:04.869885   FloppyDevice       <string>  = ""i82078"" (cb=7)
00:00:04.869886   HardDiskDevice     <string>  = ""piix3ide"" (cb=9)
00:00:04.869887   IOAPIC             <integer> = 0x0000000000000001 (1)
00:00:04.869888   LanBootRom         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom"" (cb=100)
00:00:04.869889   McfgBase           <integer> = 0x0000000000000000 (0)
00:00:04.869890   McfgLength         <integer> = 0x0000000000000000 (0)
00:00:04.869890   NumCPUs            <integer> = 0x0000000000000002 (2)
00:00:04.869891   PXEDebug           <integer> = 0x0000000000000000 (0)
00:00:04.869892   SataHardDiskDevice <string>  = ""ahci"" (cb=5)
00:00:04.869893   SataLUN1           <integer> = 0x0000000000000000 (0)
00:00:04.869894   UUID               <bytes>   = ""c6 81 a3 0c 11 15 18 46 a8 9b 22 69 d5 9b 31 1f"" (cb=16)
00:00:04.869896   UuidLe             <integer> = 0x0000000000000001 (1)
00:00:04.869897 
00:00:04.869897 [/Devices/pcbios/0/Config/NetBoot/] (level 5)
00:00:04.869898 
00:00:04.869898 [/Devices/pcbios/0/Config/NetBoot/0/] (level 6)
00:00:04.869899   NIC           <integer> = 0x0000000000000000 (0)
00:00:04.869900   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869901   PCIDeviceNo   <integer> = 0x0000000000000003 (3)
00:00:04.869902   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869902 
00:00:04.869902 [/Devices/pci/] (level 2)
00:00:04.869903 
00:00:04.869904 [/Devices/pci/0/] (level 3)
00:00:04.869904   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869905 
00:00:04.869905 [/Devices/pci/0/Config/] (level 4)
00:00:04.869906   IOAPIC <integer> = 0x0000000000000001 (1)
00:00:04.869907 
00:00:04.869907 [/Devices/pcibridge/] (level 2)
00:00:04.869908 
00:00:04.869909 [/Devices/pckbd/] (level 2)
00:00:04.869909 
00:00:04.869910 [/Devices/pckbd/0/] (level 3)
00:00:04.869911   Trusted <integer> = 0x0000000000000001 (1)
00:00:04.869911 
00:00:04.869912 [/Devices/pckbd/0/Config/] (level 4)
00:00:04.869913 
00:00:04.869913 [/Devices/pckbd/0/LUN#0/] (level 4)
00:00:04.869914   Driver <string>  = ""KeyboardQueue"" (cb=14)
00:00:04.869915 
00:00:04.869915 [/Devices/pckbd/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.869916   Driver <string>  = ""MainKeyboard"" (cb=13)
00:00:04.869917 
00:00:04.869917 [/Devices/pckbd/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.869918   Object <integer> = 0x0000000003e3efe0 (65 269 728)
00:00:04.869919 
00:00:04.869919 [/Devices/pckbd/0/LUN#0/Config/] (level 5)
00:00:04.869920   QueueSize <integer> = 0x0000000000000040 (64)
00:00:04.869921 
00:00:04.869921 [/Devices/pckbd/0/LUN#1/] (level 4)
00:00:04.869922   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:04.869923 
00:00:04.869923 [/Devices/pckbd/0/LUN#1/AttachedDriver/] (level 5)
00:00:04.869924   Driver <string>  = ""MainMouse"" (cb=10)
00:00:04.869925 
00:00:04.869925 [/Devices/pckbd/0/LUN#1/AttachedDriver/Config/] (level 6)
00:00:04.869927   Object <integer> = 0x0000000003ec5b30 (65 821 488)
00:00:04.869927 
00:00:04.869928 [/Devices/pckbd/0/LUN#1/Config/] (level 5)
00:00:04.869929   QueueSize <integer> = 0x0000000000000080 (128)
00:00:04.869929 
00:00:04.869930 [/Devices/pcnet/] (level 2)
00:00:04.869930 
00:00:04.869931 [/Devices/piix3ide/] (level 2)
00:00:04.869932 
00:00:04.869932 [/Devices/piix3ide/0/] (level 3)
00:00:04.869933   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869934   PCIDeviceNo   <integer> = 0x0000000000000001 (1)
00:00:04.869935   PCIFunctionNo <integer> = 0x0000000000000001 (1)
00:00:04.869936   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869936 
00:00:04.869937 [/Devices/piix3ide/0/Config/] (level 4)
00:00:04.869938   Type <string>  = ""PIIX4"" (cb=6)
00:00:04.869938 
00:00:04.869939 [/Devices/piix3ide/0/LUN#2/] (level 4)
00:00:04.869940   Driver <string>  = ""VD"" (cb=3)
00:00:04.869941 
00:00:04.869941 [/Devices/piix3ide/0/LUN#2/Config/] (level 5)
00:00:04.869943   Format    <string>  = ""RAW"" (cb=4)
00:00:04.869943   Mountable <integer> = 0x0000000000000001 (1)
00:00:04.869944   Path      <string>  = ""C:\Users\Home\Downloads\kali-linux-2022.1-installer-amd64.iso"" (cb=62)
00:00:04.869945   ReadOnly  <integer> = 0x0000000000000001 (1)
00:00:04.869945   Type      <string>  = ""DVD"" (cb=4)
00:00:04.869946 
00:00:04.869946 [/Devices/piix3ide/0/LUN#2/Config/Plugins/] (level 6)
00:00:04.869947 
00:00:04.869948 [/Devices/piix3ide/0/LUN#2/Config/Plugins/VDPluginCrypt/] (level 7)
00:00:04.869949   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VDPluginCrypt.DLL"" (cb=114)
00:00:04.869950 
00:00:04.869950 [/Devices/piix3ide/0/LUN#999/] (level 4)
00:00:04.869952   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869952 
00:00:04.869952 [/Devices/piix3ide/0/LUN#999/Config/] (level 5)
00:00:04.869954   DeviceInstance        <string>  = ""piix3ide/0"" (cb=11)
00:00:04.869955   First                 <integer> = 0x0000000000000000 (0)
00:00:04.869956   Last                  <integer> = 0x0000000000000003 (3)
00:00:04.869957   pConsole              <integer> = 0x0000000003eeddd0 (65 986 000)
00:00:04.869958   papLeds               <integer> = 0x0000000003eee5b0 (65 988 016)
00:00:04.869959   pmapMediumAttachments <integer> = 0x0000000003eef1e8 (65 991 144)
00:00:04.869960 
00:00:04.869960 [/Devices/serial/] (level 2)
00:00:04.869961 
00:00:04.869961 [/Devices/usb-ehci/] (level 2)
00:00:04.869962 
00:00:04.869962 [/Devices/usb-ehci/0/] (level 3)
00:00:04.869964   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869964   PCIDeviceNo   <integer> = 0x000000000000000b (11)
00:00:04.869965   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869966   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869967 
00:00:04.869967 [/Devices/usb-ehci/0/Config/] (level 4)
00:00:04.869968 
00:00:04.869968 [/Devices/usb-ehci/0/LUN#0/] (level 4)
00:00:04.869969   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:04.869970 
00:00:04.869970 [/Devices/usb-ehci/0/LUN#0/Config/] (level 5)
00:00:04.869971 
00:00:04.869971 [/Devices/usb-ehci/0/LUN#999/] (level 4)
00:00:04.869972   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869973 
00:00:04.869973 [/Devices/usb-ehci/0/LUN#999/Config/] (level 5)
00:00:04.869974   First   <integer> = 0x0000000000000000 (0)
00:00:04.869975   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869976   papLeds <integer> = 0x0000000003eef1d8 (65 991 128)
00:00:04.869977 
00:00:04.869977 [/Devices/usb-ohci/] (level 2)
00:00:04.869978 
00:00:04.869978 [/Devices/usb-ohci/0/] (level 3)
00:00:04.869979   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869980   PCIDeviceNo   <integer> = 0x0000000000000006 (6)
00:00:04.869980   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869981   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869982 
00:00:04.869982 [/Devices/usb-ohci/0/Config/] (level 4)
00:00:04.869983 
00:00:04.869983 [/Devices/usb-ohci/0/LUN#0/] (level 4)
00:00:04.869984   Driver <string>  = ""VUSBRootHub"" (cb=12)
00:00:04.869985 
00:00:04.869985 [/Devices/usb-ohci/0/LUN#0/Config/] (level 5)
00:00:04.869986 
00:00:04.869986 [/Devices/usb-ohci/0/LUN#999/] (level 4)
00:00:04.869987   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.869988 
00:00:04.869988 [/Devices/usb-ohci/0/LUN#999/Config/] (level 5)
00:00:04.869989   First   <integer> = 0x0000000000000000 (0)
00:00:04.869990   Last    <integer> = 0x0000000000000000 (0)
00:00:04.869990   papLeds <integer> = 0x0000000003eef1d0 (65 991 120)
00:00:04.869991 
00:00:04.869991 [/Devices/vga/] (level 2)
00:00:04.869992 
00:00:04.869993 [/Devices/vga/0/] (level 3)
00:00:04.869994   PCIBusNo      <integer> = 0x0000000000000000 (0)
00:00:04.869995   PCIDeviceNo   <integer> = 0x0000000000000002 (2)
00:00:04.869995   PCIFunctionNo <integer> = 0x0000000000000000 (0)
00:00:04.869996   Trusted       <integer> = 0x0000000000000001 (1)
00:00:04.869997 
00:00:04.869997 [/Devices/vga/0/Config/] (level 4)
00:00:04.869999   3DEnabled          <integer> = 0x0000000000000001 (1)
00:00:04.870000   CustomVideoModes   <integer> = 0x0000000000000000 (0)
00:00:04.870001   FadeIn             <integer> = 0x0000000000000001 (1)
00:00:04.870001   FadeOut            <integer> = 0x0000000000000001 (1)
00:00:04.870002   HeightReduction    <integer> = 0x0000000000000000 (0)
00:00:04.870003   LogoFile           <string>  = """" (cb=1)
00:00:04.870004   LogoTime           <integer> = 0x0000000000000000 (0)
00:00:04.870005   MonitorCount       <integer> = 0x0000000000000002 (2)
00:00:04.870005   ShowBootMenu       <integer> = 0x0000000000000002 (2)
00:00:04.870006   VMSVGA3dEnabled    <integer> = 0x0000000000000001 (1)
00:00:04.870007   VMSVGAEnabled      <integer> = 0x0000000000000001 (1)
00:00:04.870007   VMSVGAPciBarLayout <integer> = 0x0000000000000001 (1)
00:00:04.870008   VMSVGAPciId        <integer> = 0x0000000000000001 (1)
00:00:04.870009   VRamSize           <integer> = 0x0000000008000000 (134 217 728, 128 MB)
00:00:04.870010 
00:00:04.870011 [/Devices/vga/0/LUN#0/] (level 4)
00:00:04.870012   Driver <string>  = ""MainDisplay"" (cb=12)
00:00:04.870012 
00:00:04.870013 [/Devices/vga/0/LUN#0/Config/] (level 5)
00:00:04.870014   Object <integer> = 0x0000000003ea2a80 (65 677 952)
00:00:04.870015 
00:00:04.870015 [/Devices/vga/0/LUN#999/] (level 4)
00:00:04.870016   Driver <string>  = ""MainStatus"" (cb=11)
00:00:04.870016 
00:00:04.870017 [/Devices/vga/0/LUN#999/Config/] (level 5)
00:00:04.870018   First   <integer> = 0x0000000000000000 (0)
00:00:04.870019   Last    <integer> = 0x0000000000000000 (0)
00:00:04.870019   papLeds <integer> = 0x0000000003eef1e0 (65 991 136)
00:00:04.870020 
00:00:04.870021 [/Devices/virtio-net/] (level 2)
00:00:04.870022 
00:00:04.870022 [/EM/] (level 1)
00:00:04.870023   TripleFaultReset <integer> = 0x0000000000000000 (0)
00:00:04.870023 
00:00:04.870024 [/GIM/] (level 1)
00:00:04.870024   Provider <string>  = ""KVM"" (cb=4)
00:00:04.870025 
00:00:04.870025 [/HM/] (level 1)
00:00:04.870027   64bitEnabled            <integer> = 0x0000000000000001 (1)
00:00:04.870028   EnableLargePages        <integer> = 0x0000000000000001 (1)
00:00:04.870063   EnableNestedPaging      <integer> = 0x0000000000000001 (1)
00:00:04.870064   EnableUX                <integer> = 0x0000000000000001 (1)
00:00:04.870065   EnableVPID              <integer> = 0x0000000000000001 (1)
00:00:04.870065   Exclusive               <integer> = 0x0000000000000000 (0)
00:00:04.870066   HMForced                <integer> = 0x0000000000000001 (1)
00:00:04.870067   IBPBOnVMEntry           <integer> = 0x0000000000000000 (0)
00:00:04.870068   IBPBOnVMExit            <integer> = 0x0000000000000000 (0)
00:00:04.870069   L1DFlushOnSched         <integer> = 0x0000000000000001 (1)
00:00:04.870070   L1DFlushOnVMEntry       <integer> = 0x0000000000000000 (0)
00:00:04.870070   LovelyMesaDrvWorkaround <integer> = 0x0000000000000001 (1)
00:00:04.870071   MDSClearOnSched         <integer> = 0x0000000000000001 (1)
00:00:04.870072   MDSClearOnVMEntry       <integer> = 0x0000000000000000 (0)
00:00:04.870073   SpecCtrlByHost          <integer> = 0x0000000000000000 (0)
00:00:04.870074   UseNEMInstead           <integer> = 0x0000000000000000 (0)
00:00:04.870074 
00:00:04.870075 [/MM/] (level 1)
00:00:04.870075   CanUseLargerHeap <integer> = 0x0000000000000000 (0)
00:00:04.870076 
00:00:04.870076 [/NEM/] (level 1)
00:00:04.870077   Allow64BitGuests        <integer> = 0x0000000000000001 (1)
00:00:04.870078   LovelyMesaDrvWorkaround <integer> = 0x0000000000000001 (1)
00:00:04.870079 
00:00:04.870079 [/PDM/] (level 1)
00:00:04.870080 
00:00:04.870080 [/PDM/AsyncCompletion/] (level 2)
00:00:04.870081 
00:00:04.870081 [/PDM/AsyncCompletion/File/] (level 3)
00:00:04.870082 
00:00:04.870082 [/PDM/AsyncCompletion/File/BwGroups/] (level 4)
00:00:04.870084 
00:00:04.870084 [/PDM/BlkCache/] (level 2)
00:00:04.870085   CacheSize <integer> = 0x0000000000500000 (5 242 880, 5 MB)
00:00:04.870086 
00:00:04.870086 [/PDM/Devices/] (level 2)
00:00:04.870087 
00:00:04.870087 [/PDM/Devices/VBoxEhci/] (level 3)
00:00:04.870089   Path         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR3.DLL"" (cb=111)
00:00:04.870090   R0SearchPath <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:04.870091 
00:00:04.870091 [/PDM/Devices/VBoxNvme/] (level 3)
00:00:04.870095   Path         <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxNvmeR3.DLL"" (cb=111)
00:00:04.870097   R0SearchPath <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64"" (cb=96)
00:00:04.870098 
00:00:04.870098 [/PDM/Drivers/] (level 2)
00:00:04.870099 
00:00:04.870099 [/PDM/Drivers/DrvHostWebcam/] (level 3)
00:00:04.870100   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxHostWebcam.DLL"" (cb=115)
00:00:04.870101 
00:00:04.870101 [/PDM/Drivers/VBoxC/] (level 3)
00:00:04.870102   Path <string>  = ""VBoxC"" (cb=6)
00:00:04.870102 
00:00:04.870102 [/PDM/NetworkShaper/] (level 2)
00:00:04.870103 
00:00:04.870103 [/PDM/NetworkShaper/BwGroups/] (level 3)
00:00:04.870104 
00:00:04.870105 [/PDM/USB/] (level 2)
00:00:04.870105 
00:00:04.870106 [/PDM/USB/VBoxUsbCardReader/] (level 3)
00:00:04.870106   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbCardReaderR3.DLL"" (cb=120)
00:00:04.870107 
00:00:04.870107 [/PDM/USB/VBoxUsbWebcam/] (level 3)
00:00:04.870108   Path <string>  = ""E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxUsbWebcamR3.DLL"" (cb=116)
00:00:04.870109 
00:00:04.870109 [/TM/] (level 1)
00:00:04.870110   UTCOffset <integer> = 0x0000000000000000 (0)
00:00:04.870111 
00:00:04.870111 [/USB/] (level 1)
00:00:04.870112 
00:00:04.870112 [/USB/HidMouse/] (level 2)
00:00:04.870113 
00:00:04.870113 [/USB/HidMouse/0/] (level 3)
00:00:04.870114 
00:00:04.870114 [/USB/HidMouse/0/Config/] (level 4)
00:00:04.870115   Mode <string>  = ""absolute"" (cb=9)
00:00:04.870115 
00:00:04.870116 [/USB/HidMouse/0/LUN#0/] (level 4)
00:00:04.870117   Driver <string>  = ""MouseQueue"" (cb=11)
00:00:04.870117 
00:00:04.870118 [/USB/HidMouse/0/LUN#0/AttachedDriver/] (level 5)
00:00:04.870119   Driver <string>  = ""MainMouse"" (cb=10)
00:00:04.870120 
00:00:04.870120 [/USB/HidMouse/0/LUN#0/AttachedDriver/Config/] (level 6)
00:00:04.870121   Object <integer> = 0x0000000003ec5b30 (65 821 488)
00:00:04.870122 
00:00:04.870122 [/USB/HidMouse/0/LUN#0/Config/] (level 5)
00:00:04.870123   QueueSize <integer> = 0x0000000000000080 (128)
00:00:04.870124 
00:00:04.870124 [/USB/USBProxy/] (level 2)
00:00:04.870125 
00:00:04.870125 [/USB/USBProxy/GlobalConfig/] (level 3)
00:00:04.870126 
00:00:04.870127 ********************* End of CFGM dump **********************
00:00:04.870379 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:04.870466 MM: cbHyperHeap=0x240000 (2359296)
00:00:04.872611 CPUM: fXStateHostMask=0x0; initial: 0x0; host XCR0=0x0
00:00:04.873840 CPUM: Matched host CPU INTEL 0x6/0x25/0x5 Intel_Core7_Westmere with CPU DB entry 'Intel Core i7-3960X' (INTEL 0x6/0x2d/0x6 Intel_Core7_SandyBridge)
00:00:04.874032 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:04.874058 CPUM: Disabled PCID without FSGSBASE to workaround buggy guests
00:00:04.874066 CPUM: Microcode revision 0x00000004
00:00:04.874402 PGM: Host paging mode: AMD64+PGE+NX
00:00:04.874442 PGM: PGMPool: cMaxPages=2304 (u64MaxPages=2084)
00:00:04.874462 PGM: pgmR3PoolInit: cMaxPages=0x900 cMaxUsers=0x1200 cMaxPhysExts=0x1200 fCacheEnable=true 
00:00:04.885544 TM: GIP - u32Mode=3 (Invariant) u32UpdateHz=100 u32UpdateIntervalNS=10000000 enmUseTscDelta=2 (Practically Zero) fGetGipCpu=0x11 cCpus=4
00:00:04.885592 TM: GIP - u64CpuHz=2 793 001 012 (0xa679d034)  SUPGetCpuHzFromGip => 2 793 001 012
00:00:04.885598 TM: GIP - CPU: iCpuSet=0x0 idCpu=0x0 idApic=0x0 iGipCpu=0x3 i64TSCDelta=0 enmState=3 u64CpuHz=2793108784(*) cErrors=0
00:00:04.885603 TM: GIP - CPU: iCpuSet=0x1 idCpu=0x1 idApic=0x1 iGipCpu=0x0 i64TSCDelta=0 enmState=3 u64CpuHz=2793001012(*) cErrors=0
00:00:04.885607 TM: GIP - CPU: iCpuSet=0x2 idCpu=0x2 idApic=0x4 iGipCpu=0x1 i64TSCDelta=0 enmState=3 u64CpuHz=2793843206(*) cErrors=0
00:00:04.885611 TM: GIP - CPU: iCpuSet=0x3 idCpu=0x3 idApic=0x5 iGipCpu=0x2 i64TSCDelta=0 enmState=3 u64CpuHz=2793826954(*) cErrors=0
00:00:04.885714 TM: cTSCTicksPerSecond=2 793 001 012 (0xa679d034) enmTSCMode=1 (VirtTscEmulated)
00:00:04.885732 TM: TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:04.886591 EMR3Init: fIemExecutesAll=false fGuruOnTripleFault=true 
00:00:04.886887 IEM: TargetCpu=CURRENT, Microarch=Intel_Core7_Westmere
00:00:04.887105 GIM: Using provider 'KVM' (Implementation version: 0)
00:00:04.887136 CPUM: SetGuestCpuIdFeature: Enabled Hypervisor Present bit
00:00:04.887272 AIOMgr: Default manager type is 'Async'
00:00:04.887280 AIOMgr: Default file backend is 'NonBuffered'
00:00:04.887515 BlkCache: Cache successfully initialized. Cache size is 5242880 bytes
00:00:04.887526 BlkCache: Cache commit interval is 10000 ms
00:00:04.887532 BlkCache: Cache commit threshold is 2621440 bytes
00:00:05.836511 PcBios: [SMP] BIOS with 2 CPUs
00:00:05.836574 PcBios: Using the 386+ BIOS image.
00:00:05.836909 PcBios: MPS table at 000e1300
00:00:05.838457 PcBios: Using LAN ROM 'E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\PXE-Intel.rom' with a size of 0xc000 bytes
00:00:05.838565 PcBios: fCheckShutdownStatusForSoftReset=true   fClearShutdownStatusOnHardReset=true 
00:00:05.888309 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:05.888329 SUP: seg #1: R X 0x00001000 LB 0x0001e000
00:00:05.888333 SUP: seg #2: R   0x0001f000 LB 0x0000c000
00:00:05.888336 SUP: seg #3: RW  0x0002b000 LB 0x00001000
00:00:05.888339 SUP: seg #4: R   0x0002c000 LB 0x00002000
00:00:05.888342 SUP: seg #5: RW  0x0002e000 LB 0x00001000
00:00:05.888345 SUP: seg #6: R   0x0002f000 LB 0x00001000
00:00:05.888348 SUP: seg #7: RWX 0x00030000 LB 0x00001000
00:00:05.888351 SUP: seg #8: R   0x00031000 LB 0x00002000
00:00:05.888453 SUP: Loaded VBoxDDR0.r0 (E:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:05.888463 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xXXXXXXXXXXXXXXXX
00:00:05.888997 CPUM: SetGuestCpuIdFeature: Enabled xAPIC
00:00:05.889007 CPUM: SetGuestCpuIdFeature: Enabled x2APIC
00:00:05.889381 IOAPIC: Using implementation 2.0! Chipset type ICH9
00:00:05.889500 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:05.889796 VMMDev: cbDefaultBudget: 130 922 048 (7cdb640)
00:00:05.912902 Shared Folders service loaded
00:00:05.931191 Guest Control service loaded
00:00:05.985616 VGA: Using the 386+ BIOS image.
00:00:05.989092 VD: VDInit finished with VINF_SUCCESS
00:00:06.017422 DrvVD: Flushes will be ignored
00:00:06.017450 DrvVD: Async flushes will be passed to the disk
00:00:06.019989 AIOMgr: Endpoint for file 'E:\Users\Home\VirtualBox VMs\Kali\Kali.vdi' (flags 000c0723) created successfully
00:00:06.064638 VD: Opening the disk took 45257236 ns
00:00:06.064829 AHCI: LUN#0: disk, PCHS=16383/16/63, total number of sectors 218103808
00:00:06.065215 AHCI#0: Reset the HBA
00:00:06.065226 VD#0: Cancelling all active requests
00:00:06.066942 PIIX3 ATA: LUN#0: no unit
00:00:06.066967 PIIX3 ATA: LUN#1: no unit
00:00:06.067102 DrvVD: Flushes will be ignored
00:00:06.067112 DrvVD: Async flushes will be passed to the disk
00:00:06.067349 VD: Opening the disk took 223712 ns
00:00:06.067388 PIIX3 ATA: LUN#2: CD/DVD, total number of sectors 1462072, passthrough disabled
00:00:06.067444 PIIX3 ATA: LUN#3: no unit
00:00:06.067465 PIIX3 ATA: Ctl#0: finished processing RESET
00:00:06.067484 PIIX3 ATA: Ctl#1: finished processing RESET
00:00:06.067610 E1000#0: Chip=82540EM LinkUpDelay=3000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=enabled RC=disabled
00:00:06.073801 NAT: Guest address guess set to 10.0.2.15 by initialization
00:00:06.123047 NAT: DNS#0: 10.154.1.1
00:00:06.124538 AC97: Using codec 'AD1980'
00:00:06.218937 Audio: Found 5 devices for driver 'WasAPI'
00:00:06.218954 Audio: Device 'Speakers (Conexant CX20671 SmartAudio HD)':
00:00:06.218955 Audio:   ID              = {0.0.0.00000000}.{5aee2f46-7a75-40b4-966e-d7a1df957f8a}
00:00:06.218956 Audio:   Usage           = output
00:00:06.218956 Audio:   Flags           = DEFAULT_OUT
00:00:06.218957 Audio:   Input channels  = 0
00:00:06.218957 Audio:   Output channels = 2
00:00:06.218960 Audio: Device 'Speakers (Conexant CX20671 SmartAudio HD)':
00:00:06.218961 Audio:   ID              = {0.0.0.00000000}.{5aee2f46-7a75-40b4-966e-d7a1df957f8a}
00:00:06.218961 Audio:   Usage           = output
00:00:06.218962 Audio:   Flags           = NONE
00:00:06.218962 Audio:   Input channels  = 0
00:00:06.218962 Audio:   Output channels = 2
00:00:06.218965 Audio: Device 'Microphone (Conexant CX20671 SmartAudio HD)':
00:00:06.218965 Audio:   ID              = {0.0.1.00000000}.{032a30e1-a128-4e17-8f6b-da2a069a099e}
00:00:06.218966 Audio:   Usage           = input
00:00:06.218966 Audio:   Flags           = DEFAULT_IN
00:00:06.218967 Audio:   Input channels  = 2
00:00:06.218967 Audio:   Output channels = 0
00:00:06.218969 Audio: Device 'Microphone (Conexant CX20671 SmartAudio HD)':
00:00:06.218970 Audio:   ID              = {0.0.1.00000000}.{032a30e1-a128-4e17-8f6b-da2a069a099e}
00:00:06.218970 Audio:   Usage           = input
00:00:06.218970 Audio:   Flags           = NONE
00:00:06.218971 Audio:   Input channels  = 2
00:00:06.218971 Audio:   Output channels = 0
00:00:06.218974 Audio: Device 'Stereo Mix (Conexant CX20671 SmartAudio HD)':
00:00:06.218974 Audio:   ID              = {0.0.1.00000000}.{51d473a9-ba14-4ba3-a007-f776ebc945b9}
00:00:06.218974 Audio:   Usage           = input
00:00:06.218975 Audio:   Flags           = NONE
00:00:06.218975 Audio:   Input channels  = 2
00:00:06.218975 Audio:   Output channels = 0
00:00:06.219358 AC97: Reset
00:00:06.219385 AC97: Mixer reset (EAID=0x809, EACS=0x9)
00:00:06.219390 AC97: Record select to left=mic, right=mic
00:00:06.260679 SUP: seg #0: R   0x00000000 LB 0x00001000
00:00:06.260697 SUP: seg #1: R X 0x00001000 LB 0x00002000
00:00:06.260701 SUP: seg #2: R   0x00003000 LB 0x00001000
00:00:06.260704 SUP: seg #3: RW  0x00004000 LB 0x00001000
00:00:06.260707 SUP: seg #4: R   0x00005000 LB 0x00002000
00:00:06.260710 SUP: seg #5: RWX 0x00007000 LB 0x00001000
00:00:06.260713 SUP: seg #6: R   0x00008000 LB 0x00002000
00:00:06.260743 SUP: Loaded VBoxEhciR0.r0 (E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR0.r0) at 0xXXXXXXXXXXXXXXXX - ModuleInit at XXXXXXXXXXXXXXXX and ModuleTerm at XXXXXXXXXXXXXXXX using the native ring-0 loader
00:00:06.260752 SUP: windbg> .reload /f E:\Program Files\Oracle\VirtualBox\ExtensionPacks\Oracle_VM_VirtualBox_Extension_Pack\win.amd64\VBoxEhciR0.r0=0xXXXXXXXXXXXXXXXX
00:00:06.262034 VUSB: Attached 'HidMouse' to port 1 on RootHub#1 (FullSpeed)
00:00:06.262069 PGM: The CPU physical address width is 36 bits
00:00:06.262136 PGM: PGMR3InitFinalize: 4 MB PSE mask 0000000fffffffff -> VINF_SUCCESS
00:00:06.262300 TM: TMR3InitFinalize: fTSCModeSwitchAllowed=true 
00:00:06.262494 VMM: Thread-context hooks unavailable
00:00:06.262503 VMM: Warning! RTThreadPreemptIsPending() cannot be trusted!  Need to update kernel info?
00:00:06.262505 VMM: Kernel preemption is possible
00:00:06.264747 HM: fWorldSwitcher=0x0 (fIbpbOnVmExit=false fIbpbOnVmEntry=false fL1dFlushOnVmEntry=false); fL1dFlushOnSched=false fMdsClearOnVmEntry=false
00:00:06.264759 HM: Using VT-x implementation 3.0
00:00:06.264786 HM: Max resume loops                  = 1024
00:00:06.264787 HM: Host CR4                          = 0x6f8
00:00:06.264788 HM: Host EFER                         = 0xd01
00:00:06.264789 HM: MSR_IA32_SMM_MONITOR_CTL          = 0x0
00:00:06.264789 HM: MSR_IA32_FEATURE_CONTROL          = 0x5
00:00:06.264790 HM:   LOCK
00:00:06.264790 HM:   VMXON
00:00:06.264791 HM: MSR_IA32_VMX_BASIC                = 0xda04000000000f
00:00:06.264792 HM:   VMCS id                           = 0xf
00:00:06.264792 HM:   VMCS size                         = 1024 bytes
00:00:06.264793 HM:   VMCS physical address limit       = None
00:00:06.264793 HM:   VMCS memory type                  = Write Back (WB)
00:00:06.264794 HM:   Dual-monitor treatment support    = true 
00:00:06.264794 HM:   OUTS & INS instruction-info       = true 
00:00:06.264795 HM:   Supports true-capability MSRs     = true 
00:00:06.264795 HM:   VM-entry Xcpt error-code optional = false
00:00:06.264795 HM: MSR_IA32_VMX_PINBASED_CTLS        = 0x7f00000016
00:00:06.264796 HM:   EXT_INT_EXIT
00:00:06.264796 HM:   NMI_EXIT
00:00:06.264797 HM:   VIRTUAL_NMI
00:00:06.264797 HM:   PREEMPT_TIMER
00:00:06.264797 HM:   POSTED_INT (must be cleared)
00:00:06.264813 HM: MSR_IA32_VMX_PROCBASED_CTLS       = 0xfff9fffe0401e172
00:00:06.264814 HM:   INT_WINDOW_EXIT
00:00:06.264814 HM:   USE_TSC_OFFSETTING
00:00:06.264814 HM:   HLT_EXIT
00:00:06.264814 HM:   INVLPG_EXIT
00:00:06.264815 HM:   MWAIT_EXIT
00:00:06.264815 HM:   RDPMC_EXIT
00:00:06.264815 HM:   RDTSC_EXIT
00:00:06.264816 HM:   CR3_LOAD_EXIT (must be set)
00:00:06.264816 HM:   CR3_STORE_EXIT (must be set)
00:00:06.264816 HM:   CR8_LOAD_EXIT
00:00:06.264816 HM:   CR8_STORE_EXIT
00:00:06.264817 HM:   USE_TPR_SHADOW
00:00:06.264817 HM:   NMI_WINDOW_EXIT
00:00:06.264817 HM:   MOV_DR_EXIT
00:00:06.264818 HM:   UNCOND_IO_EXIT
00:00:06.264818 HM:   USE_IO_BITMAPS
00:00:06.264818 HM:   MONITOR_TRAP_FLAG
00:00:06.264819 HM:   USE_MSR_BITMAPS
00:00:06.264819 HM:   MONITOR_EXIT
00:00:06.264819 HM:   PAUSE_EXIT
00:00:06.264819 HM:   USE_SECONDARY_CTLS
00:00:06.264849 HM: MSR_IA32_VMX_PROCBASED_CTLS2      = 0xff00000000
00:00:06.264850 HM:   VIRT_APIC_ACCESS
00:00:06.264850 HM:   EPT
00:00:06.264850 HM:   DESC_TABLE_EXIT
00:00:06.264851 HM:   RDTSCP
00:00:06.264851 HM:   VIRT_X2APIC_MODE
00:00:06.264851 HM:   VPID
00:00:06.264851 HM:   WBINVD_EXIT
00:00:06.264852 HM:   UNRESTRICTED_GUEST
00:00:06.264852 HM:   APIC_REG_VIRT (must be cleared)
00:00:06.264852 HM:   VIRT_INT_DELIVERY (must be cleared)
00:00:06.264853 HM:   PAUSE_LOOP_EXIT (must be cleared)
00:00:06.264853 HM:   RDRAND_EXIT (must be cleared)
00:00:06.264853 HM:   INVPCID (must be cleared)
00:00:06.264854 HM:   VMFUNC (must be cleared)
00:00:06.264854 HM:   VMCS_SHADOWING (must be cleared)
00:00:06.264854 HM:   ENCLS_EXIT (must be cleared)
00:00:06.264855 HM:   RDSEED_EXIT (must be cleared)
00:00:06.264855 HM:   PML (must be cleared)
00:00:06.264855 HM:   EPT_VE (must be cleared)
00:00:06.264856 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264856 HM:   XSAVES_XRSTORS (must be cleared)
00:00:06.264856 HM:   MODE_BASED_EPT_PERM (must be cleared)
00:00:06.264857 HM:   SPPTP_EPT (must be cleared)
00:00:06.264857 HM:   PT_EPT (must be cleared)
00:00:06.264857 HM:   TSC_SCALING (must be cleared)
00:00:06.264858 HM:   USER_WAIT_PAUSE (must be cleared)
00:00:06.264858 HM:   ENCLV_EXIT (must be cleared)
00:00:06.264858 HM: MSR_IA32_VMX_ENTRY_CTLS           = 0xffff000011ff
00:00:06.264859 HM:   LOAD_DEBUG (must be set)
00:00:06.264859 HM:   IA32E_MODE_GUEST
00:00:06.264860 HM:   ENTRY_TO_SMM
00:00:06.264860 HM:   DEACTIVATE_DUAL_MON
00:00:06.264860 HM:   LOAD_PERF_MSR
00:00:06.264860 HM:   LOAD_PAT_MSR
00:00:06.264861 HM:   LOAD_EFER_MSR
00:00:06.264861 HM:   LOAD_BNDCFGS_MSR (must be cleared)
00:00:06.264861 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264862 HM:   LOAD_RTIT_CTL_MSR (must be cleared)
00:00:06.264862 HM: MSR_IA32_VMX_EXIT_CTLS            = 0x7fffff00036dff
00:00:06.264863 HM:   SAVE_DEBUG (must be set)
00:00:06.264863 HM:   HOST_ADDR_SPACE_SIZE
00:00:06.264863 HM:   LOAD_PERF_MSR
00:00:06.264864 HM:   ACK_EXT_INT
00:00:06.264864 HM:   SAVE_PAT_MSR
00:00:06.264864 HM:   LOAD_PAT_MSR
00:00:06.264865 HM:   SAVE_EFER_MSR
00:00:06.264865 HM:   LOAD_EFER_MSR
00:00:06.264865 HM:   SAVE_PREEMPT_TIMER
00:00:06.264880 HM:   CLEAR_BNDCFGS_MSR (must be cleared)
00:00:06.264880 HM:   CONCEAL_VMX_FROM_PT (must be cleared)
00:00:06.264881 HM:   CLEAR_RTIT_CTL_MSR (must be cleared)
00:00:06.264881 HM: MSR_IA32_VMX_TRUE_PINBASED_CTLS   = 0x7f00000016
00:00:06.264882 HM: MSR_IA32_VMX_TRUE_PROCBASED_CTLS  = 0xfff9fffe04006172
00:00:06.264883 HM: MSR_IA32_VMX_TRUE_ENTRY_CTLS      = 0xffff000011fb
00:00:06.264884 HM: MSR_IA32_VMX_TRUE_EXIT_CTLS       = 0x7fffff00036dfb
00:00:06.264884 HM: MSR_IA32_VMX_MISC                 = 0x401e7
00:00:06.264885 HM:   PREEMPT_TIMER_TSC                 = 0x7 - erratum detected, using 0x0 instead
00:00:06.264886 HM:   EXIT_SAVE_EFER_LMA                = true 
00:00:06.264886 HM:   ACTIVITY_STATES                   = 0x7 ( HLT SHUTDOWN SIPI_WAIT )
00:00:06.264887 HM:   INTEL_PT                          = false
00:00:06.264887 HM:   SMM_READ_SMBASE_MSR               = false
00:00:06.264887 HM:   CR3_TARGET                        = 0x4
00:00:06.264888 HM:   MAX_MSR                           = 0x0 ( 512 )
00:00:06.264888 HM:   VMXOFF_BLOCK_SMI                  = false
00:00:06.264889 HM:   VMWRITE_ALL                       = false
00:00:06.264889 HM:   ENTRY_INJECT_SOFT_INT             = 0x0
00:00:06.264890 HM:   MSEG_ID                           = 0x0
00:00:06.264890 HM: MSR_IA32_VMX_VMCS_ENUM            = 0x2a
00:00:06.264891 HM:   HIGHEST_IDX                       = 0x15
00:00:06.264891 HM: MSR_IA32_VMX_EPT_VPID_CAP         = 0xf0106114141
00:00:06.264892 HM:   RWX_X_ONLY
00:00:06.264892 HM:   PAGE_WALK_LENGTH_4
00:00:06.264892 HM:   EMT_UC
00:00:06.264893 HM:   EMT_WB
00:00:06.264893 HM:   PDE_2M
00:00:06.264893 HM:   INVEPT
00:00:06.264893 HM:   INVEPT_SINGLE_CONTEXT
00:00:06.264894 HM:   INVEPT_ALL_CONTEXTS
00:00:06.264894 HM:   INVVPID
00:00:06.264894 HM:   INVVPID_INDIV_ADDR
00:00:06.264895 HM:   INVVPID_SINGLE_CONTEXT
00:00:06.264895 HM:   INVVPID_ALL_CONTEXTS
00:00:06.264895 HM:   INVVPID_SINGLE_CONTEXT_RETAIN_GLOBALS
00:00:06.264896 HM: MSR_IA32_VMX_CR0_FIXED0           = 0x80000021
00:00:06.264896 HM: MSR_IA32_VMX_CR0_FIXED1           = 0xffffffff
00:00:06.264897 HM: MSR_IA32_VMX_CR4_FIXED0           = 0x2000
00:00:06.264897 HM: MSR_IA32_VMX_CR4_FIXED1           = 0x267ff
00:00:06.264898 HM: APIC-access page physaddr         = 0x000000023417e000
00:00:06.264899 HM: VCPU  0: MSR bitmap physaddr      = 0x0000000233eb9000
00:00:06.264900 HM: VCPU  0: VMCS physaddr            = 0x0000000233eb6000
00:00:06.264901 HM: VCPU  1: MSR bitmap physaddr      = 0x0000000233ebd000
00:00:06.264901 HM: VCPU  1: VMCS physaddr            = 0x0000000233eba000
00:00:06.264902 HM: Guest support: 32-bit and 64-bit
00:00:06.264910 HM: Supports VMCS EFER fields         = true 
00:00:06.264911 HM: Enabled VMX
00:00:06.264915 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:06.264916 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:06.264917 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:06.264917 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:06.264918 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:06.264918 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:06.264919 HM: Enabled nested paging
00:00:06.264919 HM:   EPT flush type                  = Single context
00:00:06.264919 HM: Enabled unrestricted guest execution
00:00:06.264920 HM: Enabled large page support
00:00:06.264920 HM: Enabled VPID
00:00:06.264921 HM:   VPID flush type                 = Single context
00:00:06.264921 HM: Enabled VMX-preemption timer (cPreemptTimerShift=0)
00:00:06.264922 HM: VT-x/AMD-V init method: Local
00:00:06.264923 EM: Exit history optimizations: enabled=true  enabled-r0=true  enabled-r0-no-preemption=false
00:00:06.267403 AIOMgr: Async flushes not supported
00:00:06.267422 PcBios: SATA LUN#0 LCHS=1024/255/63
00:00:06.267440 APIC: fPostedIntrsEnabled=false fVirtApicRegsEnabled=false fSupportsTscDeadline=false
00:00:06.267445 TMR3UtcNow: nsNow=1 648 098 653 521 591 300 nsPrev=0 -> cNsDelta=1 648 098 653 521 591 300 (offLag=0 offVirtualSync=0 offVirtualSyncGivenUp=0, NowAgain=1 648 098 653 521 591 300)
00:00:06.267455 VMM: fUsePeriodicPreemptionTimers=false
00:00:06.267462 CPUM: Logical host processors: 4 present, 4 max, 4 online, online mask: 000000000000000f
00:00:06.267466 CPUM: Physical host cores: 2
00:00:06.267467 ************************* CPUID dump ************************
00:00:06.267504          Raw Standard CPUID Leaves
00:00:06.267504      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267506 Gst: 00000000/0000  0000000b 756e6547 6c65746e 49656e69
00:00:06.267508 Hst:                0000000b 756e6547 6c65746e 49656e69
00:00:06.267509 Gst: 00000001/0000  00020655 00020800 82b82203 178bfbff
00:00:06.267510 Hst:                00020655 00100800 029ae3ff bfebfbff
00:00:06.267511 Gst: 00000002/0000  55035a01 00f0b2e3 00000000 09ca212c
00:00:06.267512 Hst:                55035a01 00f0b2e3 00000000 09ca212c
00:00:06.267513 Gst: 00000003/0000  00000000 00000000 00000000 00000000
00:00:06.267513 Hst:                00000000 00000000 00000000 00000000
00:00:06.267514 Gst: 00000004/0000  04000121 01c0003f 0000003f 00000000
00:00:06.267515 Hst:                1c004121 01c0003f 0000003f 00000000
00:00:06.267516 Gst: 00000004/0001  04000122 00c0003f 0000007f 00000000
00:00:06.267517 Hst:                1c004122 00c0003f 0000007f 00000000
00:00:06.267517 Gst: 00000004/0002  04000143 01c0003f 000001ff 00000000
00:00:06.267518 Hst:                1c004143 01c0003f 000001ff 00000000
00:00:06.267519 Gst: 00000004/0003  04000163 03c0003f 00000fff 00000002
00:00:06.267520 Hst:                1c03c163 03c0003f 00000fff 00000002
00:00:06.267521 Gst: 00000004/0004  04000000 00000000 00000000 00000000
00:00:06.267521 Hst:                00000000 00000000 00000000 00000000
00:00:06.267522 Gst: 00000005/0000  00000000 00000000 00000000 00000000
00:00:06.267523 Hst:                00000040 00000040 00000003 00001120
00:00:06.267524 Gst: 00000006/0000  00000000 00000000 00000000 00000000
00:00:06.267524 Hst:                00000007 00000002 00000001 00000000
00:00:06.267525 Gst: 00000007/0000  00000000 00000000 00000000 00000000
00:00:06.267526 Hst:                00000000 00000000 00000000 00000000
00:00:06.267526 Gst: 00000008/0000  00000000 00000000 00000000 00000000
00:00:06.267527 Hst:                00000000 00000000 00000000 00000000
00:00:06.267528 Gst: 00000009/0000  00000000 00000000 00000000 00000000
00:00:06.267528 Hst:                00000000 00000000 00000000 00000000
00:00:06.267529 Gst: 0000000a/0000  00000000 00000000 00000000 00000000
00:00:06.267530 Hst:                07300403 00000004 00000000 00000603
00:00:06.267531 Gst: 0000000b/0000  00000000 00000001 00000100 00000000
00:00:06.267531 Hst:                00000001 00000002 00000100 00000000
00:00:06.267532 Gst: 0000000b/0001  00000001 00000002 00000201 00000000
00:00:06.267533 Hst:                00000004 00000004 00000201 00000000
00:00:06.267534 Gst: 0000000b/0002  00000000 00000000 00000002 00000000
00:00:06.267534 Hst:                00000000 00000000 00000002 00000000
00:00:06.267535                                Name: GenuineIntel
00:00:06.267536                            Supports: 0x00000000-0x0000000b
00:00:06.267552                              Family:  6 	Extended: 0 	Effective: 6
00:00:06.267553                               Model:  5 	Extended: 2 	Effective: 37
00:00:06.267554                            Stepping: 5
00:00:06.267555                                Type: 0 (primary)
00:00:06.267556                             APIC ID: 0x00
00:00:06.267557                        Logical CPUs: 2
00:00:06.267557                        CLFLUSH Size: 8
00:00:06.267558                            Brand ID: 0x00
00:00:06.267559 Features
00:00:06.267559   Mnemonic - Description                                  = guest (host)
00:00:06.267576   FPU - x87 FPU on Chip                                   = 1 (1)
00:00:06.267578   VME - Virtual 8086 Mode Enhancements                    = 1 (1)
00:00:06.267579   DE - Debugging extensions                               = 1 (1)
00:00:06.267580   PSE - Page Size Extension                               = 1 (1)
00:00:06.267581   TSC - Time Stamp Counter                                = 1 (1)
00:00:06.267582   MSR - Model Specific Registers                          = 1 (1)
00:00:06.267583   PAE - Physical Address Extension                        = 1 (1)
00:00:06.267584   MCE - Machine Check Exception                           = 1 (1)
00:00:06.267585   CX8 - CMPXCHG8B instruction                             = 1 (1)
00:00:06.267586   APIC - APIC On-Chip                                     = 1 (1)
00:00:06.267587   SEP - SYSENTER and SYSEXIT Present                      = 1 (1)
00:00:06.267588   MTRR - Memory Type Range Registers                      = 1 (1)
00:00:06.267589   PGE - PTE Global Bit                                    = 1 (1)
00:00:06.267590   MCA - Machine Check Architecture                        = 1 (1)
00:00:06.267591   CMOV - Conditional Move instructions                    = 1 (1)
00:00:06.267592   PAT - Page Attribute Table                              = 1 (1)
00:00:06.267593   PSE-36 - 36-bit Page Size Extension                     = 1 (1)
00:00:06.267594   PSN - Processor Serial Number                           = 0 (0)
00:00:06.267595   CLFSH - CLFLUSH instruction                             = 1 (1)
00:00:06.267596   DS - Debug Store                                        = 0 (1)
00:00:06.267597   ACPI - Thermal Mon. & Soft. Clock Ctrl.                 = 0 (1)
00:00:06.267598   MMX - Intel MMX Technology                              = 1 (1)
00:00:06.267599   FXSR - FXSAVE and FXRSTOR instructions                  = 1 (1)
00:00:06.267600   SSE - SSE support                                       = 1 (1)
00:00:06.267601   SSE2 - SSE2 support                                     = 1 (1)
00:00:06.267602   SS - Self Snoop                                         = 0 (1)
00:00:06.267603   HTT - Hyper-Threading Technology                        = 1 (1)
00:00:06.267604   TM - Therm. Monitor                                     = 0 (1)
00:00:06.267605   PBE - Pending Break Enabled                             = 0 (1)
00:00:06.267606   SSE3 - SSE3 support                                     = 1 (1)
00:00:06.267607   PCLMUL - PCLMULQDQ support (for AES-GCM)                = 1 (1)
00:00:06.267608   DTES64 - DS Area 64-bit Layout                          = 0 (1)
00:00:06.267609   MONITOR - MONITOR/MWAIT instructions                    = 0 (1)
00:00:06.267609   CPL-DS - CPL Qualified Debug Store                      = 0 (1)
00:00:06.267610   VMX - Virtual Machine Extensions                        = 0 (1)
00:00:06.267611   SMX - Safer Mode Extensions                             = 0 (1)
00:00:06.267612   EST - Enhanced SpeedStep Technology                     = 0 (1)
00:00:06.267613   TM2 - Terminal Monitor 2                                = 0 (1)
00:00:06.267614   SSSE3 - Supplemental Streaming SIMD Extensions 3        = 1 (1)
00:00:06.267615   CNTX-ID - L1 Context ID                                 = 0 (0)
00:00:06.267616   SDBG - Silicon Debug interface                          = 0 (0)
00:00:06.267617   FMA - Fused Multiply Add extensions                     = 0 (0)
00:00:06.267618   CX16 - CMPXCHG16B instruction                           = 1 (1)
00:00:06.267619   TPRUPDATE - xTPR Update Control                         = 0 (1)
00:00:06.267620   PDCM - Perf/Debug Capability MSR                        = 0 (1)
00:00:06.267620   PCID - Process Context Identifiers                      = 0 (1)
00:00:06.267621   DCA - Direct Cache Access                               = 0 (0)
00:00:06.267622   SSE4_1 - SSE4_1 support                                 = 1 (1)
00:00:06.267623   SSE4_2 - SSE4_2 support                                 = 1 (1)
00:00:06.267624   X2APIC - x2APIC support                                 = 1 (0)
00:00:06.267625   MOVBE - MOVBE instruction                               = 0 (0)
00:00:06.267626   POPCNT - POPCNT instruction                             = 1 (1)
00:00:06.267627   TSCDEADL - Time Stamp Counter Deadline                  = 0 (0)
00:00:06.267628   AES - AES instructions                                  = 1 (1)
00:00:06.267629   XSAVE - XSAVE instruction                               = 0 (0)
00:00:06.267630   OSXSAVE - OSXSAVE instruction                           = 0 (0)
00:00:06.267631   AVX - AVX support                                       = 0 (0)
00:00:06.267632   F16C - 16-bit floating point conversion instructions    = 0 (0)
00:00:06.267633   RDRAND - RDRAND instruction                             = 0 (0)
00:00:06.267634   HVP - Hypervisor Present (we're a guest)                = 1 (0)
00:00:06.267635 Structured Extended Feature Flags Enumeration (leaf 7):
00:00:06.267635   Mnemonic - Description                                  = guest (host)
00:00:06.267636   FSGSBASE - RDFSBASE/RDGSBASE/WRFSBASE/WRGSBASE instr.   = 0 (0)
00:00:06.267636   TSCADJUST - Supports MSR_IA32_TSC_ADJUST                = 0 (0)
00:00:06.267637   SGX - Supports Software Guard Extensions                = 0 (0)
00:00:06.267638   BMI1 - Advanced Bit Manipulation extension 1            = 0 (0)
00:00:06.267639   HLE - Hardware Lock Elision                             = 0 (0)
00:00:06.267640   AVX2 - Advanced Vector Extensions 2                     = 0 (0)
00:00:06.267641   FDP_EXCPTN_ONLY - FPU DP only updated on exceptions     = 0 (0)
00:00:06.267641   SMEP - Supervisor Mode Execution Prevention             = 0 (0)
00:00:06.267642   BMI2 - Advanced Bit Manipulation extension 2            = 0 (0)
00:00:06.267643   ERMS - Enhanced REP MOVSB/STOSB instructions            = 0 (0)
00:00:06.267644   INVPCID - INVPCID instruction                           = 0 (0)
00:00:06.267645   RTM - Restricted Transactional Memory                   = 0 (0)
00:00:06.267645   PQM - Platform Quality of Service Monitoring            = 0 (0)
00:00:06.267646   DEPFPU_CS_DS - Deprecates FPU CS, FPU DS values if set  = 0 (0)
00:00:06.267647   MPE - Intel Memory Protection Extensions                = 0 (0)
00:00:06.267648   PQE - Platform Quality of Service Enforcement           = 0 (0)
00:00:06.267648   AVX512F - AVX512 Foundation instructions                = 0 (0)
00:00:06.267649   RDSEED - RDSEED instruction                             = 0 (0)
00:00:06.267650   ADX - ADCX/ADOX instructions                            = 0 (0)
00:00:06.267651   SMAP - Supervisor Mode Access Prevention                = 0 (0)
00:00:06.267652   CLFLUSHOPT - CLFLUSHOPT (Cache Line Flush) instruction  = 0 (0)
00:00:06.267653   INTEL_PT - Intel Processor Trace                        = 0 (0)
00:00:06.267654   AVX512PF - AVX512 Prefetch instructions                 = 0 (0)
00:00:06.267655   AVX512ER - AVX512 Exponential & Reciprocal instructions = 0 (0)
00:00:06.267655   AVX512CD - AVX512 Conflict Detection instructions       = 0 (0)
00:00:06.267656   SHA - Secure Hash Algorithm extensions                  = 0 (0)
00:00:06.267657   PREFETCHWT1 - PREFETCHWT1 instruction                   = 0 (0)
00:00:06.267658   UMIP - User mode insturction prevention                 = 0 (0)
00:00:06.267659   PKU - Protection Key for Usermode pages                 = 0 (0)
00:00:06.267659   OSPKE - CR4.PKU mirror                                  = 0 (0)
00:00:06.267660   MAWAU - Value used by BNDLDX & BNDSTX                   = 0x0 (0x0)
00:00:06.267661   RDPID - Read processor ID support                       = 0 (0)
00:00:06.267662   SGX_LC - Supports SGX Launch Configuration              = 0 (0)
00:00:06.267664          Raw Hypervisor CPUID Leaves
00:00:06.267664      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267665 Gst: 40000000/0000  40000001 4b4d564b 564b4d56 0000004d
00:00:06.267666 Hst:                00000001 00000002 00000100 00000000
00:00:06.267667 Gst: 40000001/0000  01000089 00000000 00000000 00000000
00:00:06.267668 Hst:                00000001 00000002 00000100 00000000
00:00:06.267669          Raw Extended CPUID Leaves
00:00:06.267669      Leaf/sub-leaf  eax      ebx      ecx      edx
00:00:06.267669 Gst: 80000000/0000  80000008 00000000 00000000 00000000
00:00:06.267670 Hst:                80000008 00000000 00000000 00000000
00:00:06.267671 Gst: 80000001/0000  00000000 00000000 00000001 28100800
00:00:06.267672 Hst:                00000000 00000000 00000001 28100800
00:00:06.267672 Gst: 80000002/0000  65746e49 2952286c 726f4320 4d542865
00:00:06.267674 Hst:                65746e49 2952286c 726f4320 4d542865
00:00:06.267674 Gst: 80000003/0000  37692029 55504320 20202020 4d202020
00:00:06.267675 Hst:                37692029 55504320 20202020 4d202020
00:00:06.267677 Gst: 80000004/0000  30343620 20402020 30382e32 007a4847
00:00:06.267678 Hst:                30343620 20402020 30382e32 007a4847
00:00:06.267678 Gst: 80000005/0000  00000000 00000000 00000000 00000000
00:00:06.267679 Hst:                00000000 00000000 00000000 00000000
00:00:06.267680 Gst: 80000006/0000  00000000 00000000 01006040 00000000
00:00:06.267681 Hst:                00000000 00000000 01006040 00000000
00:00:06.267682 Gst: 80000007/0000  00000000 00000000 00000000 00000100
00:00:06.267682 Hst:                00000000 00000000 00000000 00000100
00:00:06.267683 Gst: 80000008/0000  00003024 00000000 00000000 00000000
00:00:06.267684 Hst:                00003024 00000000 00000000 00000000
00:00:06.267685 Ext Name:                        
00:00:06.267685 Ext Supports:                    0x80000000-0x80000008
00:00:06.267686 Family:                          0  	Extended: 0 	Effective: 0
00:00:06.267686 Model:                           0  	Extended: 0 	Effective: 0
00:00:06.267687 Stepping:                        0
00:00:06.267687 Brand ID:                        0x000
00:00:06.267688 Ext Features
00:00:06.267688   Mnemonic - Description                                  = guest (host)
00:00:06.267708   FPU - x87 FPU on Chip                                   = 0 (0)
00:00:06.267709   VME - Virtual 8086 Mode Enhancements                    = 0 (0)
00:00:06.267710   DE - Debugging extensions                               = 0 (0)
00:00:06.267711   PSE - Page Size Extension                               = 0 (0)
00:00:06.267712   TSC - Time Stamp Counter                                = 0 (0)
00:00:06.267713   MSR - K86 Model Specific Registers                      = 0 (0)
00:00:06.267714   PAE - Physical Address Extension                        = 0 (0)
00:00:06.267715   MCE - Machine Check Exception                           = 0 (0)
00:00:06.267716   CX8 - CMPXCHG8B instruction                             = 0 (0)
00:00:06.267717   APIC - APIC On-Chip                                     = 0 (0)
00:00:06.267718   SEP - SYSCALL/SYSRET                                    = 1 (1)
00:00:06.267737   MTRR - Memory Type Range Registers                      = 0 (0)
00:00:06.267740   PGE - PTE Global Bi",Capt Obvious
20911,Virtual box unable to start VM failing with error (rc=-5640),Linux,VirtualBox 6.1.32,2022-04-23T09:11:32Z,2022-04-23T09:11:32Z,2022-04-23T09:11:32Z,"(rc=-5640)
Please try reinstalling VirtualBox.
where: supR3HardenedWinReSpawn what: 1
VERR_SUP_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure: The process has more than one thread.",Prateek DA
20900,VirtualBox crashes on startup: Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.,all,VirtualBox 6.1.32,2022-04-14T06:08:29Z,2022-04-14T06:08:29Z,2022-04-14T06:08:29Z,"When I start VirtualBox it crashes immediate.
Message is:
Het is niet gelukt het VirtualBox COM-object te verkrijgen.
Het programma wordt nu afgesloten.

Completely failed to instantiate CLSID_VirtualBox: REGDB_E_CLASSNOTREG.
Resultaatcode: REGDB_E_CLASSNOTREG (0x80040154)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Un- and reinstalled VB, but still same problem.
I added a bugreport file

",A3aan
20820,Hardening Issue since 6.1.32,Windows,VirtualBox 6.1.32,2022-02-10T02:04:36Z,2022-04-11T18:42:29Z,2022-04-11T18:42:29Z,"Since 6.1.32-149290 I have a hardening error. The last version without this issue was 6.1.31-148916. 

I get an error ""NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)"" when I try to start a VM. The nonworking versions are also 6.1.33-149396, 6.1.33-149686, 6.1.33-149825. The logs from the version 
6.1.33-149686 are attached. 

This is Windows 10 21H2 VM on Windows 10 21H2 machine.
",boxer01
20898,VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) during Windows 11 update,Windows,VirtualBox 6.1.32,2022-04-11T15:58:00Z,2022-04-11T15:58:00Z,2022-04-11T15:58:00Z,Just got a guru meditation during the update of the Windows 11 in VM. Here are the logs and the picture.,boxer01
20895,Better error messages when starting Linux image on Windows 11,Linux,VirtualBox 6.1.32,2022-04-10T20:03:41Z,2022-04-10T20:03:41Z,2022-04-10T20:03:41Z,"I need better error messages when starting a new Ubuntu image on Windows 11 Home edition. Please so some basic checks in VirtualBox that everything is in order before starting the Ubuntu image. 

Host: Windows 11 Home edition
Guest os: Ubuntu 

For example, is there some Windows Hyper-V settings that needs to be changed? Do I need to uninstall Hyper-V?

Running Vagrant with VirtualBox from this Vagrantfile:
https://github.com/freeciv/freeciv-web/blob/develop/Vagrantfile

The last messages in the VirtualBox log is this:
00:00:07.916785 TM: Host/VM is not suitable for using TSC mode 'RealTscOffset', request to change TSC mode ignored
00:00:08.794811 GIM: KVM: Enabled wall-clock struct. at 0x00000000bfc00000 - u32Sec=1649620734 u32Nano=685699103 uVersion=2
00:00:09.850407 PIT: mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
00:00:10.164896 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)",AndreasRosdal
20894,VirtualBox 6.1.30 & 6.1.32 VM terminated returning from hibernate,Linux,VirtualBox 6.1.32,2022-04-08T18:27:43Z,2022-04-08T18:27:43Z,2022-04-08T18:27:43Z,"Hello,

I have a Ubuntu VM on a Windows 10 Host on a laptop.
When returning from hibernate status while powered on battery, the VM cannot be resumed and a VirtualBox error window states a critical error has occurred and the VM must be terminated.

I get the same result with both VirtualBox 6.1.30 and 6.1.32.
VirtualBox log is only showing ""emR3Debug: rc=VERR_VMX_INVALID_VMXON_PTR"" as last info before the PC goes to hibernate state.
All rest of the log file does not exhibit any meaningful message.

Any help is very appreciated as I suspect more a VM setting issue than a bug but I am not certain and I do not know what kind of VM setting has to be tuned.

Thanks

Laurent",Laurentzed
20893,Guest Windows XP 32 bit does not start anymore after network crash,Windows,VirtualBox 6.1.32,2022-04-06T13:22:07Z,2022-04-06T13:29:35Z,2022-04-06T13:29:35Z,"Host: Windows 10 64 bit (12 Gb installed RAM, 8 CPU's)
Guest: Windows XP 32 bit (1 Gb allowed RAM, 1 CPU allowed)
Network: Windows Server 2008 R2

Yesterday there was a problem in the server (hung), while that happened I had an old program running locally within the VM. In spite of that, I still closed everything apparently in a normal way.
Today I cannot launch the host, when I try I get the message in the image [[Image()]]
My system is in Spanish but it informs that there was a critical error during the execution of the VM and has been stopped; it supplies the option to continue (Ignore button), I tried it to no avail.
All I get when I try to launch the host is a black screen and, sometimes, the message in the attached image, other times it just stays there and I have to shut it down using the X button.
By the way, I've been using VM for years and this is the very first time that I have a problem I cannot solve easily, in fact I don't remember ever having problems before. Thanks in advance.",Mamá Cora
20891,Critical Error starting VM Machine,Windows,VirtualBox 6.1.32,2022-04-01T15:36:41Z,2022-04-04T11:54:50Z,2022-04-04T11:54:50Z,"After some minutes of run, the VM go in a critical error.
Sometimes during the boot of VM I have a critical error and the VM stops.

The VM Machine has Windows 10 OS.
The host machine is Windows 7

Some days ago there was no trouble running this VM. Now I have this trouble.
I have tried to update VirtualBox (now is 6.1.32 r 149290 (Qt5.6.2)) but I have the same error.

In attach: VBox.log,  VBox.png, ""screen-shot of error""",Bebuccio
20889,VM fails during starting,Windows,VirtualBox 6.1.32,2022-03-29T22:47:13Z,2022-04-03T17:01:20Z,2022-04-03T17:01:20Z,"During starting or after a few minutes of running an error appers.
Yesterday it run without any problem, nothing new was installed to the PC.",Jirka
20890,cannot run any linux VM on ThinkPad X1 Extreme gen 4 with Windows 11 host OS,Linux,VirtualBox 6.1.32,2022-03-31T15:06:13Z,2022-03-31T15:06:13Z,2022-03-31T15:06:13Z,"hello, I'm using VirtualBox 6.1.32 r149290 (Qt5.6.2) and i have a lot of problems running any virtual machines with linux OS. below problems:

- the system from the ISO image takes a long time to install
- after installation and selecting the ""restart"" button, the machine freezes and cannot restart
- after a reset, and trying to start the virtual machine, I get a system loading screen (the host CPU load increases), but the system does not start.
- sometimes (less than 1 of 10) system boots but runs very slowly, keeps very high activity of CPU on the host


I'm using Lenovo ThinkPad X1 Extreme gen 4 (20Y5CTO1WW): 11850H, 64GB RAM, 4TB 4th gen SSD.",krak
20881,Guest additions on Linux(Artix) with dinit init system,Linux,VirtualBox 6.1.32,2022-03-25T13:35:55Z,2022-03-25T13:35:55Z,2022-03-25T13:35:55Z,"
Tried to install Guest Additions by runnung ""VBoxLinuxAdditions.run"".

Install fails due to an error in ""routines.sh"".

{{{
./routines.sh: Zeile 236: systemctl: Kommando nicht gefunden
}}}

Artix Linux guest (artix-plasma-dinit-20220123-x86_64.iso) on Win10 host.
",JAMxWA
20876,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,VirtualBox 6.1.32,2022-03-18T13:53:57Z,2022-03-18T13:53:57Z,2022-03-18T13:53:57Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output. The procedure is shown below.
1.Start up Windows XP
2. Windows XP is set to PAUSE
3. 1 hour and 10 minutes elapse
4. Release PAUSE
5. AUDIO is not output
Thank you very much for your cooperation.",aokadak@…
20857,Windows 10 21H2 - Menu Start Issue,Windows,VirtualBox 6.1.32,2022-03-05T13:56:45Z,2022-03-18T07:41:03Z,2022-03-18T07:41:03Z,"After installing the latest VM VBox Extension Pack version 6.1.32 and checking 3d acceleration (Screen -> Acceleration -> Mark enable 3d acceleration) on a guest system (windows 10 21H2) the windows 10 start menu is unusable. 
It becomes transparent, does not scale and crashes the whole system. 
After disabling 3D acceleration - everything works fine. 

The error remains regardless of the screen parameters i.e. Video memory, number of monitors etc.



",ReconX2
20868,Automated login not working on Arch Linux guest of a Windows host,Linux,VirtualBox 6.1.32,2022-03-14T16:14:42Z,2022-03-14T16:14:42Z,2022-03-14T16:14:42Z,"I followed instructions in https://www.virtualbox.org/manual/ch09.html#autologon
to be able to login automatically on my Arch Linux host under a Windows 10 host, providing credentials as explained for Windows guests (not described for Linux guests), which shows in syslog on the Linux guest as ...
{{{
pam_vbox_setcred called, iFlags=0x4
pam_vbox_setcred: argv[0] = debug
}}}
but pam_vbox is unable to subsequently retrieve the credentials leaving the following error in syslog:
{{{
pam_vbox: 6.1.32r149290, running on amd64
pam_vbox_init: runtime initialized
pam_vbox_init: guest lib initialized
pam_vbox_init: rhost=<none>, tty=:0, prompt=<none>
her	dbus-daemon[2156]: Successfully activated service 'org.a11y.atspi.Registry'
her	SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait""=""1""
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWait"" with rc=VINF_SUCCESS
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsWaitTimeout"" with rc=VERR_NOT_FOUND
pam_vbox_read_prop: read key ""/VirtualBox/GuestAdd/PAM/CredsMsgWaiting"" with rc=VERR_NOT_FOUND
Showing message ""Waiting for credentials ..."" (type 4)
pam_vbox_check_creds: could not query for credentials! rc=VERR_PERMISSION_DENIED. Aborting
pam_vbox_authenticate: overall result rc=VERR_PERMISSION_DENIED
}}}
",MAnantharaman
20867,Kernel modules not re-built on updating guest additions on Linux,Linux,VirtualBox 6.1.32,2022-03-14T15:49:43Z,2022-03-14T15:49:43Z,2022-03-14T15:49:43Z,"Calling ./VBoxLinuxAdditions.run to install a new version of guest additions (here: 6.1.32) installs everything but does not re-build kernel-modules like vboxguest, vboxsf - and neither does rcvboxadd setup. The reason is that in the latter, specifically in the function setup_modules, a check is made whether vboxguest.*o* exists for the current kernel and gives up if it does - without checking the module-version. I worked around this by deleting vboxguest.ko ... ",MAnantharaman
20865,"ause is set and Pause is canceled, Audio will not be output. (continuation)",Windows,VirtualBox 6.1.32,2022-03-11T08:54:25Z,2022-03-11T08:54:25Z,2022-03-11T08:54:25Z,"When the guest OS does PAUSE on windows xp and cancels PAUSE, Audio is not output in VirtualBox v6.1.30, Audio is output in 6.1.32, but Audio is output after the 3rd, 4th or 2 hours. It disappears.
Thank you.",aokadak@…
20863,Critical error,Windows,VirtualBox 6.1.32,2022-03-09T23:44:02Z,2022-03-09T23:44:02Z,2022-03-09T23:44:02Z,"A critical error has occurred while running the virtual machine and the machine has been stopped.

",fabio sordi
20862,PAUSEから再開した場合、オーディオが出力されない,Windows,VirtualBox 6.1.32,2022-03-09T07:31:57Z,2022-03-09T07:32:57Z,2022-03-09T07:32:57Z,"WindowsXPでVirtualBoxをPauseにしてPauseを解除した場合、Audioが出力されません。
",aokadak@…
20855,Windows Vista Ultimate 64 Bit Guest Additions not working,Windows,VirtualBox 6.1.32,2022-03-05T13:20:20Z,2022-03-05T13:20:20Z,2022-03-05T13:20:20Z,I am using Windows Vista Ultimate 64 Bit and I wanted to install Guest Additions so I can use Windows Aero Theme but I get an error when installing Guest Additions.,Aremon
20854,Oracle VM not booting,other,VirtualBox 6.1.32,2022-02-27T05:10:53Z,2022-03-03T21:38:35Z,2022-03-03T21:38:35Z,"failed to open a session for the virtual machine result code E_Fail
VM created and attached not booting ",Venkat Rangan
20831,Windows 2008 R2 issues.,Windows,VirtualBox 6.1.32,2022-02-17T10:33:10Z,2022-03-02T07:28:34Z,2022-03-02T07:28:34Z,"Good day.
We have windows 2008 R2 enterprise as a host running on dual Xeon Silver 4210 processor mounted on ASUS motherboard Z11PR-D16 with 392 Gb of memory.
All guest machines are Windows 7 x64 with 6 Gb memory.
We faced this issue: we can run 23 VMs concurrently, but when we start 24-th VM an error appears: 
""The virtual machine 'xxx' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\VMs\XXX\Logs\VBoxHardening.log'.
E_FAIL (0x80004005)
MachineWrap
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}""
There are two logs attached, with successful start and failed one.
VirtualBox version: 6.1.32.
Successful start log
https://www.mediafire.com/file/t38s7g1r0bt4j1j/Logs-success.zip/file
Failed start log
https://www.mediafire.com/file/2v2yrjyna8toyrl/Logs-error.zip/file
",ZMKS
20853,Memory can't be read after resuming VM from pause after few resumes,Windows,VirtualBox 6.1.32,2022-02-25T17:09:56Z,2022-02-25T17:09:56Z,2022-02-25T17:09:56Z,Memory can't be read after resuming VM from pause: this time after few successful resumes.,MikhailRokhin
20839,Vmbox is running too slow,all,VirtualBox 6.1.32,2022-02-24T06:58:15Z,2022-02-24T06:58:15Z,2022-02-24T06:58:15Z,After recent update vm box running too slow . I am not able to install any iso file. ,sudip234
20837,Unable to get Virtualbox to run,other,VirtualBox 6.1.32,2022-02-22T04:50:44Z,2022-02-22T04:50:44Z,2022-02-22T04:50:44Z,"I am receiving an error when I try to activate virtualbox. I am running windows 10. I am not an advanced user so I was not able to understand possible answers to the issue. I will need step by step instructions on how to correct the problem. The error is 

Failed to open a session for the virtual machine Gamez.

Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Onlygamez
20833,Linux Guest VM Crashes If Bridged Network Is Selected,Linux,VirtualBox 6.1.32,2022-02-18T04:15:58Z,2022-02-18T04:15:58Z,2022-02-18T04:15:58Z,"I just installed VB onto my Windows 10 PC and tried to install Oracle Linux 8 onto it.  If Bridged Network is selected, the VM crashes.",jawale
20825,copy/paste failure from Win 10 host to Linux guest with VirtualBox 6.1.32,Linux,VirtualBox 6.1.32,2022-02-13T04:08:02Z,2022-02-13T04:08:02Z,2022-02-13T04:08:02Z,"I am running the latest (fully patched) version of Windows 10 For Workstations as my host OS.

On that host OS, I have recently installed the latest VirtualBox 6.1.32 and its Guest Additions.

Running that VirtualBox, I have created a virtual machine and installed the latest Xubuntu 21.10 as a guest OS.

I have observed a bizarre shared clipboard problem: if I copy something from TextPad (a Windows text editor program, running on the host OS) and paste it into the guest (Xubuntu) OS, the first time I do this the paste works.  But if I try it a second time (copy some different text in TextPad, try to paste it into Xubuntu), what gets pasted is the contents of the first copy from TextPad.  It is as if the 2nd copy is not seen by Xubuntu.  But that 2nd copy is seen by other Windows applications: I can do a paste into many other applications and they see the 2nd copied text just fine.

Another weird fact: if I then copy something from Xubuntu and paste it back into TextPad, and then do a copy of something new in TextPad (besides what I copied before), then it now successfully pastes into Xubuntu.

I have only seen this issue between TextPad and Xubuntu.  If, instead, I copy from, say, Notepad++ and paste into Xubuntu, every copy and paste works just fine.

I have been running both TextPad and VirtualBox for many years, and this copy paste bug did NOT exist before ~14 months ago.

I first noticed this issue ~14 months ago, when my Win 10 box was running VirtualBox 6.1.16, and made this forum posting: https://forums.virtualbox.org/viewtopic.php?f=6&t=101174.

Several people replied because others are seeing similar problems.

When I recently updated to the latest VirtualBox 6.1.32 and installed the latest Xubuntu, I decided to revisit this bug once more.  I made this recent posting to that forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=101174&start=30#p513218

Forum user fth0, a very helpful responder, looked at my log files and did not seem to see any issue.  (His suggestions about OneDrive and ScanSnap I have a very hard time imagining how they could be the culprit.)

He suggested that I add a bug report, so here I am.  I am attaching all the files associated with my last forum posting.
",HaroldFinch
20819,Upgrading to 6.1.32 Failed due to USB permissions...,all,VirtualBox 6.1.32,2022-02-09T20:30:28Z,2022-02-09T20:30:28Z,2022-02-09T20:30:28Z,"Going trough the regular standard VirtualBox upgrade noticed upgrade to 6.1.32 failed and succeed in two different computers.

My work computer which is secured and by AD blocked the usage of USB due to Data Security requirements, failed to start after install the upgrade to 6.1.32.

However at home computer doing the exactly same upgrade, succeed because there was not constrain about the USB Security at home and not ruled by Windows AD Group Policy filtering USB.

Just like to report, being more agnostic and less intrusive will allow the usage and embracement of VirtualBox more widely.

Thank you for this fantastic product. please keep doing the great work.

Best Regards Dinooz ",Dinooz
20816,Installing VirtualBox Guest Additions Causes All Mouse/Pointer Drivers to Experience a Code 52 Error,all,VirtualBox 6.1.32,2022-02-08T16:13:12Z,2022-02-08T16:13:12Z,2022-02-08T16:13:12Z,"After installing VirtualBox Guest Additions on both Windows 10 and Windows 11, the mouse/pointer immediately disappears from the screen (even before the reboot) and displays error code 52 in the device manager for all mouse/pointer drivers currently installed on the host. Currently, the only workaround to this is to disable device driver signature checks in Windows.",1Poseidon3
20814,Upgrade from 6.1.3 to 6.1.32 causes VT-x detection to fail,Linux,VirtualBox 6.1.32,2022-02-07T15:03:39Z,2022-02-07T15:03:39Z,2022-02-07T15:03:39Z,"I have virtualbox running on windows 10

I have a VM that requires nested virtualization.

It ran fine under 6.1.30 but since upgrading to 6.1.32 it fails saying:

not in hypervisor partition
VT-x is disabled in the BIOS for all CPU modes

Downgrade to 6.1.30 cured the problem
I have replicated the symptoms on two different devices:

Intel Core i3-2350M 2.3GHz running Windows 10 Pro 21H2
Intel core i3-2370M 2.4 GHz Running Windows 10 Pro 21H2

",Pcrossley
20810,Can't use gpu to increase vram,Linux,VirtualBox 6.1.32,2022-02-04T09:38:45Z,2022-02-04T09:38:45Z,2022-02-04T09:38:45Z,"Hello i have wanted to up vram, so i have set exec of virtualbox in gpu0 (nvidia graphic card) but when i launch vbox and/or virtual machine he doesn't use my gpu0 have you an idea of why ?

[[Image(https://i.imgur.com/1r4ecp6.png)]]

i have set virtualbox.exe and virtualboxvm.exe to use gpu0",Ludovic BERTHET
20803,Using Greenshot for screenshot management on Host crash VirtualBox,Linux,VirtualBox 6.1.32,2022-02-01T19:09:35Z,2022-02-01T19:13:32Z,2022-02-01T19:13:32Z,"Hello,

I use greenshot on my computer and also open Virtualbox with an Ubuntu Guest

I launch virtual box and my guest is running.

I use Greenshot to do a screenshot and open in image editor

I go on the greenshot software and copy the image to the clickboard button

Then my virtualbox software is killed When I copy this 
Environment

I use 

Windows 10 

Greenshot 1.2.10 Build 6

Virtualbox 6.1.32 r149290

Greenshot support is saying :
https://greenshot.atlassian.net/browse/BUG-2892
Greenshot places an image to the clipboard, which to our knowledge is according to the specifications from Microsoft itself.
",Greggreg
20799,Duplicate packages in the guest OS when bridging to the LACP adapter in Windows,other,VirtualBox 6.1.32,2022-01-31T16:13:58Z,2022-01-31T17:17:23Z,2022-01-31T17:17:23Z,"In VirtualBox version 6.1.32, when using a bridge to the LACP adapter in Windows Server 2012 R2, duplicate packages appear in the guest OS.

Tested on Debian 11 using ping.



The host PC running Windows Server 2012 R2 is connected to the router via a Zyxel GS1900-8 switch using the LACP protocol via 2 Intel I350 NICs.
If you send a ping from any guest OS, for example, to a router, then several packets will be returned in response - 1 + 3 duplicates.
At the same time, there is an increase in the load on the CPU and RAM of both the guest OS and the host OS, respectively.





Previous versions of VirtualBox did not have this problem, including 6.1.30.

The versions of the expansion packs used were the corresponding versions of VirtualBox.



VMware Workstation had the same problem for a long time, and now it has reached VirtualBox. :(

I tested this effect earlier in VMware Workstation Pro 16 with Linux and Windows guest OS - the result is the same, there are duplicates.",Konstantin.P
20800,Virtual Box Machine fails on startup,Windows,VirtualBox 6.1.32,2022-01-31T16:52:10Z,2022-01-31T16:52:10Z,2022-01-31T16:52:10Z,"Exactly as Ticket #19282

message:
------------------------------------------------
Échec de l'ouverture de session pour la machine virtuelle W10-V.

The virtual machine 'W10-V' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Administrateur\VirtualBox VMs\W10-V\Logs\VBoxHardening.log'.

Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
-----------------------------------------------------------

To solve the problem, I had to uninstall '''Trusteer Endpoint Protection by IBM''' as suggested in the aforementioned ticket",Malbec
20778,Game crashing when VirtualBox Host-Only Adapter is present and enabled,other,VirtualBox 6.1.32,2022-01-19T19:05:56Z,2022-01-21T23:19:25Z,2022-01-21T23:19:25Z,"The game XIII from GoG crashes on startup when the VirtualBox Host-Only adapter is installed and enabled.  This is 100% reproducible on my system, and has been confirmed on another system.  The game is installed and running on the host, not VirtualBox.  VirtualBox doesn't have to be running for the crash to occur.

When the game starts, it apparently enumerates all of the active network adapters and attempts to check something on each one.  The response from the VirtualBox Host-Only Adapter results in the game crashing.

This was determined by launching the game in a debugger and stepping backward from the crash with time-travel debugging.  The code just before the crash was making network related calls.

I don't know if this is a defect in the game, or a defect in the adapter, just that disabling the adapter fixes the problem, and enabling it causes the issue to return.",g051051
20779,drm:vmw_host_printf [vmwgfx]] *ERROR* in version 6.1.30 & 6.1.32,Linux,VirtualBox 6.1.32,2022-01-20T05:44:09Z,2022-01-20T08:26:05Z,2022-01-20T08:26:05Z,"CentOS 9 Stream VM provisioned with *.vdi|*.vhd|*.vmdk disk and dynamically allocated capacity of 100GB configurations gives the 'drm:vmw_host_printf [vmwgfx]] *ERROR* Failed to send host log message' after OS post installation boot. 

Included are screenshots of the error, device configurations and the host Windows OS configurations occurring on two workstations. A provisioned VM with a *.vdi|*.vhd|*.vmdk disk capacity of 45.6GB dynamically allocated encountered no issues with the post-install boot with the same CentOS 9 Stream OS.

Supporting images are attached. Please let me know if additional technical information about the issue is needed.",BrownFoxx
20935,Mouse cursor rendered in low resolution,Windows,VirtualBox 6.1.34,2022-05-10T08:03:37Z,2023-01-06T09:36:53Z,2023-01-06T09:36:53Z,"As described in forum: https://forums.virtualbox.org/viewtopic.php?f=6&t=105871

Host: Windows 10 Pro 21H2, Vbox 6.1.34 (the free version, no Extension Pack)[[BR]]
Guest: Windows 7 + Guest Additions v6.1.34

The Pointer scheme selected in the guest Control Panel is ""(None)"".

The pointer inside the VM is very pixelated. See photos below. One is the pointer inside the VM window, very pixelated, the other shows it outside the VM window, not pixelated, smooth.

The DPI scaling in the guest is set to 100%, the host has also 100%.

The photos on imgur:
https://imgur.com/XOqHicD
https://imgur.com/DLEiCpp
",xerces8
20924,IPv6 not working out of the box with bridged WiFi and Linux guests,Linux,VirtualBox 6.1.34,2022-05-02T08:32:36Z,2022-10-16T00:31:25Z,2022-10-16T00:31:25Z,"When using a bridge WiFi interface, IPv6 doesn't work out of the box on Linux guests. IPv6 becomes operational only after issuing ""ip -6 neigh del <gateway-linklocal-ipv6> dev <dev>"" as proposed in this gist: https://gist.github.com/0xquad/6090af4fe2c5b5fc6299 (although I found issuing it one single time suffices. No need to issue it repeatedly as the gist suggests).

This problem occurs only with Linux guests. Windows (10?) guests can use IPv6 just fine without any additional steps. Several WiFi NICs (Intel, Realtek) were tested, as well as several routers (FritzBox, Compal, generic OpenWrt). Confirmed also by different people, with different distros, including at least Ubuntu 20.04, 21.10, 22.04, Linux Mint 19.x, Mint 20.x, ArchLinux, Kali 2021. I don't have a Linux host to test with, but it's at least a bug with Windows hosts.

The bug appears similar to https://www.virtualbox.org/ticket/5503 (supposedly fixed) and https://www.virtualbox.org/ticket/14212. However, the latter mentions broken promiscuous mode as problematic. Since Windows guests aren't affected, I think that this is a different bug. The bug exists at least since VirtualBox 5.x, probably earlier versions affected as well.",treysis
20937,"Multi monitor operation not working as expected, regression to 5.2",Linux,VirtualBox 6.1.34,2022-05-11T09:46:12Z,2022-09-29T07:28:20Z,2022-09-29T07:28:20Z,"Host: Windows 10, 64 bit
Guest: Ubuntu 22.02 64 bit, Linux Mint 64 bit,... - Linux guest additions installed from VirtualBox's image as provided by the host

Situation: in version 5.2.x one could setup a VBox with two monitors, start the VBox and switch it to fullscreen mode - immediately on both monitors. That setting was persisent, so starting the VBox later would bring it up on two monitors in fullscreen mode without any manual action.

After upgrading to VirtualBox 6.1.34, the VBox settings were changed to ""VMSVGA"" graphics controller.

In version 6.1.34 it is not possible to activate the second monitor if the VBox is already in fullscreen mode - the menu option is not shown at all.
And in window mode one has to activate the second virtual monitor by hand each time the guest was started.

If one chooses ""VBoxVGA"" graphics controller, then the VBox apppears on two monitors in fullscreen mode immediately as it did in version 5.2. But there's then a really ugly bug with wrong mouse coordinates, that makes the VBOx unusable.

I have attached a log file of the following process:
1. starting the VBox (Xubuntu 22.04)
2. logging in
3. trying to activate the second virtual monitor - that FAILED (the window pops up and disappears immediatly)
4. once again trying to activate the second virtual monitor - worked now
5. shutting down the guest

I have tried both, a VBox that was already present and used with version 5.2.44 in the past and a brand new VBox created with version 6.1.34. There's no difference.

So IMHO that's a regression in version 6.1 compared to version 5.2 - it used to work pretty fine in version 5.2.
",Feuerfloh
20972,Black screen,Windows,VirtualBox 6.1.34,2022-06-08T13:35:04Z,2022-09-19T06:18:08Z,2022-09-19T06:18:08Z,Black screen in opened virtual OS,jjjj jjjj
20995,Failed to open a session for the virtual machine #VMName#.,Windows,VirtualBox 6.1.34,2022-06-20T08:30:16Z,2022-08-30T07:12:41Z,2022-08-30T07:12:41Z,"VirtualBox-6.1.32-149290 works 100% and all VM's start.

From version 6.1.33 get the following error on ALL VM's:

Failed to open a session for the virtual machine #VMName#.

The virtual machine '#VMName#' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\#UserName#\VirtualBox VMs\#VM_And_LogFolder#\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

Tried Installing 6.1.33 with and without Extension Packs - Error as Above
Tried installing 6.1.34 with and without Extension Packs - Error as Above
Tried installing 6.1.34a with and without Extension Packs - Error as Above

Please note: I don't think it is the Extension packs because running v6.1.34a with Extension Pack 6.1.32 gives same error.

Included is the LOG files for:
Successful start and shutdown of a VM (v6.1.32)
1.VBox_20220620_6.1.32.log
2.VBoxHardening_20220620_6.1.32.log
Unsuccessful start of same VM (v6.1.34a)
1.VBoxHardening_20220620_6.1.34a.log",Hercules Oberholzer
21076,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,Linux,VirtualBox 6.1.34,2022-08-25T14:16:03Z,2022-08-25T14:16:03Z,2022-08-25T14:16:03Z,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,ignasi
20957,Latest 6.1.35 Guest additions can not be installed in Windows 7 vms. Cause Bluescreen,Windows,VirtualBox 6.1.34,2022-05-26T09:54:18Z,2022-07-27T22:23:32Z,2022-07-27T22:23:32Z,Title says it all. If you mount the 6.1.35 revision 151572 iso or the one provided with the 6.1.35 revision 151573 the Windows 7 vm will get a bluescreen. Tested with x86 x64 and Server 2008 R2. Same if you you copy the files to a shared folder any try to install them from there. The exe files seem to trigger it. Installing the 6.1.34 version works.,frg
20958,No Solaris desktop keyboard or mouse with mounted ISO,Solaris,VirtualBox 6.1.34,2022-05-26T14:20:05Z,2022-07-11T11:27:43Z,2022-07-11T11:27:43Z,"'''Successfully replicated in Windows 10 and Oracle Linux 7.9 hosts.'''
If an ISO is mounted before starting a Solaris 11 VM in desktop mode the keyboard and mouse are not usable. This occurs regardless of whether the ISO is VirtualBoxGuest, boot, repo, or other. If the ISO is disconnected and then the VM started it can be attached an used. This appears to only occur with Solaris 11, currently using the CBE. Have tried multiple rebuilds using both the release repository and the repo created from the downloadable zip files. May somehow be related to the guest extensions not remaining active. Had to re-install extension on both Windows and Linux hosts after OS updates.",spbarrett
21021,VBoxTray *crash* on virtual screen resize.,Windows,VirtualBox 6.1.34,2022-07-10T18:00:15Z,2022-07-10T18:00:15Z,2022-07-10T18:00:15Z,"'''Error:''' VBoxTray.exe access violation (0xc0000005), Address: 0x004123aa

'''Guest:''' Windows NT 4.0 SP6a

'''Configuration:'''
* virtual screen: 1152×864, true color
* VM: View | Auto-resize guest display = disabled

'''Steps to reproduce:'''
* VM: View | Virtual screen 1 | Resize to 800×600",drwtsn32
21019,VirtualBox 6.1.34a causing BSOD when plugging in ST-LINK/V2,Linux,VirtualBox 6.1.34,2022-07-10T02:56:55Z,2022-07-10T03:06:11Z,2022-07-10T03:06:11Z,"Hello, I am attempting to connect an LPC1114 to an Ubuntu 18.04.6 VM running on VirtualBox 6.1.34a via an ST-LINK/V2. Shortly after connecting the device and adding it to the Ubuntu VM, my personal machine experienced a BSOD which threw PNP_DETECTED_FATAL_ERROR (ca). 

This BSOD recurred 2 more times, only when VirtualBox was running and the device was plugged in simultaneously, the BSOD did not occur when either event happened individually.

Taking a look at the minidump, it seems IoGetDevicePropertyData and VBoxUSBMon have something to do with it. Attached are the relevant minidump and VM log.",camcom
21008,"""Enable nested virtualization"" button is bugged",all,VirtualBox 6.1.34,2022-06-26T07:04:55Z,2022-06-26T16:48:34Z,2022-06-26T16:48:34Z,"I downloaded and installed last VirtualBox version for Windows: 6.1.34 r150636 (Qt5.6.2). 
I ran a VM. Then I wanted to turn on nested virtualization in CPU's options, but the button was disabled (see screenshot attached).
I have AMD Ryzen 5600x CPU and SMV is enabled in UEFI options.

I managed to figure out the problem spending some time on this: I used the console tool.
This command works correctly:
''VBoxManage.exe modifyvm ""test"" --nested-hw-virt on''
The checkbox becomes being checked after that and nested virt is turned on.
If I uncheck the checkbox again, it becomes inactive again.

Please, fix the checkbox.
I didn't notice the issue with the other checkboxes.
",IL
21005,Only reserve needed RAM,Windows,VirtualBox 6.1.34,2022-06-23T09:57:38Z,2022-06-23T09:57:38Z,2022-06-23T09:57:38Z,"When VirtualBox 6.1.34 is configured On Windows 10 host, the amount of memory reserved is specified in the settings. And this amount of memory is reserved on the host by the VM when launched.

Would it be possible change the way this setting works, to define a MAX amount of memory available to the VM, and only reserve on-the-fly onto the host the real needed memory when the VM is running ?

In the way, you can launch without trouble on a 64 Gb system 10 (for example) VM that could use each one MAX 16 Gb of memory, if all of these VM only use less than 64 Gb (or better 32 Gb) of RAM in total.",Shine
20987,Drag and Drop not working windows host and windows guest,Windows,VirtualBox 6.1.34,2022-06-14T17:02:47Z,2022-06-14T17:02:47Z,2022-06-14T17:02:47Z,"Drag and drop isn't working. Checked for Guest Addition installed, DnD is enabled. Looks like it wants to work from guest to host but file isn't transferred. DnD isn't even attempted or allowed from Host to Guest.",Lost_Developer
20984,Windows 10 remote desktop connection problem,Windows,VirtualBox 6.1.34,2022-06-13T22:51:28Z,2022-06-13T23:08:39Z,2022-06-13T23:08:39Z,"After installing Windows 10 in a virtual machine
with VBoxWindowsAdditions installed, the remote desktop client in Windows does not want to establish a connection

when VBoxWindowsAdditions is removed from the system in the virtual machine, it connects to the remote desktop


Tested on 2 Windows PCs and both Windows 10 PCs


The problem is with VBoxWindowsAdditions on windows 10 in a virtual machine",Mateusz Woźniakowski
20980,"VM launch failed when ""Virtual Machine Platform"" (WSL2/WSA) is enabled",Windows,VirtualBox 6.1.34,2022-06-12T15:33:50Z,2022-06-12T15:33:50Z,2022-06-12T15:33:50Z,"In VirtualBox version before 6.1.28, there is a problem that once a feature of Windows named ""Virtual Machine Platform"" is enabled, VMs will get stuck when launching without showing anyting. And then in version 6.1.30, this problem has been soved. There is an entry in the changelog: ""Fixed 6.1.28 regression preventing VMs starting when using Hyper-V mode on Windows 10"". But now in Version 6.1.32 and 6.1.34, this problem appears again. In other words, any Windows features relies on ""Virtual Machine Platform"", such as WSL2 or WSA, can't work together with VirtualBox version 6.1.32 or later.",SolAbc
20978,pop critical error,Windows,VirtualBox 6.1.34,2022-06-10T15:42:38Z,2022-06-10T15:42:38Z,2022-06-10T15:42:38Z,"when I open the virtual machine it tells me ""critical error"". I tried to uninstall and install virtualbox but the same thing always happens.
I attach log",luzzillo
20975,VERR_VMX_VMXON_FAILED during install of CentOS 7,Linux,VirtualBox 6.1.34,2022-06-08T23:22:16Z,2022-06-08T23:22:16Z,2022-06-08T23:22:16Z,While installing CentOS 7 VM failed with VERR_VMX_VMXON_FAILED and  NtOpenDirectoryObject failed on \Driver: 0xc0000022. Unable to restart VM. ,Tony_Z
20974,Critical Error while installing windows 10 in virtualbox,Windows,VirtualBox 6.1.34,2022-06-08T17:00:27Z,2022-06-08T17:00:27Z,2022-06-08T17:00:27Z,Critical Error while installing windows 10 in virtualbox. At the beginning of the install of windows 10 a popup window alerted me that an error occurred. It did not specify the error but gave an option to ignore or power down.,Tony_Z
20971,Linux guest VM hangs after upgrading VirtualBox to 6.1.34,Linux,VirtualBox 6.1.34,2022-06-07T18:32:33Z,2022-06-07T18:32:33Z,2022-06-07T18:32:33Z,"I'm running VirtualBox on Windows 10.
I've recently updated VirtualBox from 6.1.30 to 6.1.34.
My Ubuntu 20.04 VM has hung during an upgrade to Ubuntu 22.04.
I had to force close the VM. This has caused the system to become unbootable, so I've installed Ubuntu 22.04 from scratch.
After installation the system started hanging during boot or just after fresh login. The hanging was so hard that the guest system became unusable - I had to force close it.
I've downgraded VirtualBox to 6.1.32, but the problem persisted.
The problem went away after a second downgrade to version 6.1.30.

I'm using a default hypervisor in the VM so it's probably Hyper-V.",Przemysław Kulczycki
20969,Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.  The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.  Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df},Linux,VirtualBox 6.1.34,2022-06-07T18:16:09Z,2022-06-07T18:21:22Z,2022-06-07T18:21:22Z,"Failed to open a session for the virtual machine Kali-Linux-2022.2-virtualbox-amd64.

The virtual machine 'Kali-Linux-2022.2-virtualbox-amd64' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\Computer\VirtualBox VMs\Kali-Linux-2022.2-virtualbox-amd64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

'''VBoxHardening.log:'''
{{{
1c58.1e4c: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000084 g_uNtVerCombined=0xa04a6300
1c58.1e4c: \SystemRoot\System32\ntdll.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:24.962297600Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.242392000Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1eeb38
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x7b5414ec
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x1f5000 (2052096)
1c58.1e4c:     Resource Dir:    0x184000 LB 0x6fff8
1c58.1e4c:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1682
1c58.1e4c:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: NT Layer DLL
1c58.1e4c: \SystemRoot\System32\kernel32.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:16.157371700Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.008042100Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0xbb058
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x4e5c27cf
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0xbd000 (774144)
1c58.1e4c:     Resource Dir:    0xbb000 LB 0x520
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\KernelBase.dll:
1c58.1e4c:     CreationTime:    2022-05-13T09:37:25.904947200Z
1c58.1e4c:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
1c58.1e4c:     ChangeTime:      2022-05-13T21:27:08.226771300Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x2cf640
1c58.1e4c:     NT Headers:      0xf0
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x458acb5b
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x2cd000 (2936832)
1c58.1e4c:     Resource Dir:    0x2a4000 LB 0x548
1c58.1e4c:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1706
1c58.1e4c:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: Windows NT BASE API Client DLL
1c58.1e4c: \SystemRoot\System32\apisetschema.dll:
1c58.1e4c:     CreationTime:    2019-12-07T09:08:13.518339400Z
1c58.1e4c:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
1c58.1e4c:     ChangeTime:      2022-05-13T09:38:12.902031600Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x1f538
1c58.1e4c:     NT Headers:      0xd0
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x31288ce0
1c58.1e4c:     Image Version:   10.0
1c58.1e4c:     SizeOfImage:     0x20000 (131072)
1c58.1e4c:     Resource Dir:    0x1f000 LB 0x408
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Microsoft® Windows® Operating System
1c58.1e4c:     ProductVersion:  10.0.19041.1
1c58.1e4c:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
1c58.1e4c:     FileDescription: ApiSet Schema DLL
1c58.1e4c: NtOpenDirectoryObject failed on \Driver: 0xc0000022
1c58.1e4c: supR3HardenedWinFindAdversaries: 0x800
1c58.1e4c: \SystemRoot\System32\drivers\cfrmd.sys:
1c58.1e4c:     CreationTime:    2014-06-26T05:33:42.000000000Z
1c58.1e4c:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
1c58.1e4c:     ChangeTime:      2020-10-11T11:10:28.369648400Z
1c58.1e4c:     FileAttributes:  0x20
1c58.1e4c:     Size:            0x9d20
1c58.1e4c:     NT Headers:      0xe8
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Machine:         0x8664 - amd64
1c58.1e4c:     Timestamp:       0x5004f2a1
1c58.1e4c:     Image Version:   6.1
1c58.1e4c:     SizeOfImage:     0xe000 (57344)
1c58.1e4c:     Resource Dir:    0xc000 LB 0x3e0
1c58.1e4c:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
1c58.1e4c:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
1c58.1e4c:     ProductName:     Windows (R) Win 7 DDK driver
1c58.1e4c:     ProductVersion:  6.1.7600.16385
1c58.1e4c:     FileVersion:     6.1.7600.16385 built by: WinDDK
1c58.1e4c:     FileDescription: Safe Deletion Driver
1c58.1e4c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: Calling main()
1c58.1e4c: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
1c58.1e4c: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1c58.1e4c: SUPR3HardenedMain: Respawn #1
1c58.1e4c: System32:  \Device\HarddiskVolume4\Windows\System32
1c58.1e4c: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1c58.1e4c: KnownDllPath: C:\WINDOWS\System32
1c58.1e4c: supR3HardenedWinInit: Performing a limited self purification...
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=SELF_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000042ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000430000-000000000043ffff 0x0004/0x0004 0x0040000
1c58.1e4c:   0000000000440000-000000000044ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000450000-000000000046cfff 0x0002/0x0002 0x0040000
1c58.1e4c:   000000000046d000-000000000046ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000470000-0000000000520fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000521000-0000000000523fff 0x0104/0x0004 0x0020000
1c58.1e4c:   0000000000524000-000000000056ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *0000000000570000-0000000000573fff 0x0002/0x0002 0x0040000
1c58.1e4c:   0000000000574000-000000000057ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000580000-0000000000581fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000582000-000000000058ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000590000-0000000000591fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000592000-00000000005a9fff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000005aa000-00000000005fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000600000-00000000006affff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000006b0000-00000000006b2fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000006b3000-00000000007fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000800000-00000000008c8fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008c9000-00000000008dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008e0000-00000000008e5fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000008e6000-00000000009dffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00000000009e0000-0000000000a06fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a07000-0000000000adffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000ae0000-0000000000b0ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000b10000-0000000000b1efff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000b1f000-0000000000b1ffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *0000000000b20000-0000000000b2afff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000b2b000-0000000000d20fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000d21000-0000000000d21fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000d22000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff4407dffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff4407e0000-00007ff4407e4fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff4407e5000-00007ff4408dffff 0x0000/0x0002 0x0040000
1c58.1e4c:  *00007ff4408e0000-00007ff5408fffff 0x0000/0x0004 0x0020000
1c58.1e4c:  *00007ff540900000-00007ff5428fffff 0x0000/0x0004 0x0020000
1c58.1e4c:   00007ff542900000-00007ff542900fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00007ff542901000-00007ff54290ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542910000-00007ff542910fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542911000-00007ff54291ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff542920000-00007ff542942fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff542943000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc14fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc15000-00007ff7afc17fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc18000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1bfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1c000-00007ff7afc1dfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1e000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe210ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe2110000-00007ffbe2110fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2111000-00007ffbe2225fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe2226000-00007ffbe239efff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe239f000-00007ffbe23a2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a3000-00007ffbe23a3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23a4000-00007ffbe23dcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
1c58.1e4c:   00007ffbe23dd000-00007ffbe3f1ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe3f20000-00007ffbe3f20fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f21000-00007ffbe3f9efff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3f9f000-00007ffbe3fd1fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd2000-00007ffbe3fd2fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd3000-00007ffbe3fd3fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fd4000-00007ffbe3fdcfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\kernel32.dll
1c58.1e4c:   00007ffbe3fdd000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe4694fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4695000-00007ffbe4696fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4697000-00007ffbe469ffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
1c58.1e4c: kernelbase.dll: timestamp 0x458acb5b (rc=VINF_SUCCESS)
1c58.1e4c: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
1c58.1e4c: supR3HardenedWinInit: SUPHARDNTVPKIND_SELF_PURIFICATION_LIMITED -> VINF_SUCCESS, cFixes=0
1c58.1e4c: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
1c58.1e4c: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
1c58.1e4c: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
1c58.1e4c: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardenedWinDoReSpawn(1): New child 284c.3ce4 [kernel32].
1c58.1e4c: supR3HardNtChildGatherData: PebBaseAddress=0000000000a24000 cbPeb=0x388
1c58.1e4c: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
1c58.1e4c: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
1c58.1e4c: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000a24000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=00000000009bfe78 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
1c58.1e4c: supR3HardenedWinSetupChildInit: Start child.
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
1c58.1e4c: supR3HardNtChildPurify: Startup delay kludge #1/0: 523 ms, 34 sleeps
1c58.1e4c: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
1c58.1e4c:  *0000000000000000-000000000087ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000880000-000000000089ffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000008a0000-00000000008bcfff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000008bd000-00000000008bffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000008c0000-00000000009bafff 0x0000/0x0004 0x0020000
1c58.1e4c:   00000000009bb000-00000000009bdfff 0x0104/0x0004 0x0020000
1c58.1e4c:   00000000009be000-00000000009bffff 0x0004/0x0004 0x0020000
1c58.1e4c:  *00000000009c0000-00000000009c3fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00000000009c4000-00000000009cffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00000000009d0000-00000000009d1fff 0x0004/0x0004 0x0020000
1c58.1e4c:   00000000009d2000-00000000009fffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *0000000000a00000-0000000000a23fff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000a24000-0000000000a26fff 0x0004/0x0004 0x0020000
1c58.1e4c:   0000000000a27000-0000000000bfffff 0x0000/0x0004 0x0020000
1c58.1e4c:   0000000000c00000-000000007ffdffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
1c58.1e4c:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
1c58.1e4c:   000000007ffe4000-00007ff5ee77ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee780000-00007ff5ee780fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee781000-00007ff5ee78ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff5ee790000-00007ff5ee7b2fff 0x0002/0x0002 0x0040000
1c58.1e4c:   00007ff5ee7b3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
1c58.1e4c:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
1c58.1e4c:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
1c58.1e4c:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
1c58.1e4c: supR3HardNtChildPurify: Done after 526 ms and 0 fixes (loop #0).
284c.3ce4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
284c.3ce4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~00000000009bf908)
284c.3ce4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
284c.3ce4: New simple heap: #1 0000000000d00000 LB 0x400000 (for 2052096 allocation)
1c58.1e4c: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: System32:  \Device\HarddiskVolume4\Windows\System32
284c.3ce4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
284c.3ce4: KnownDllPath: C:\WINDOWS\System32
284c.3ce4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
284c.3ce4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
284c.3ce4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
284c.3ce4: Registered Dll notification callback with NTDLL.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
284c.3ce4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
1c58.1e4c: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 107 ms.
284c.3ce4: \SystemRoot\System32\ntdll.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:24.962297600Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1eeb38
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x7b5414ec
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x1f5000 (2052096)
284c.3ce4:     Resource Dir:    0x184000 LB 0x6fff8
284c.3ce4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1682
284c.3ce4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: NT Layer DLL
284c.3ce4: \SystemRoot\System32\kernel32.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:16.157371700Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0xbb058
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x4e5c27cf
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0xbd000 (774144)
284c.3ce4:     Resource Dir:    0xbb000 LB 0x520
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\KernelBase.dll:
284c.3ce4:     CreationTime:    2022-05-13T09:37:25.904947200Z
284c.3ce4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
284c.3ce4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x2cf640
284c.3ce4:     NT Headers:      0xf0
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x458acb5b
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x2cd000 (2936832)
284c.3ce4:     Resource Dir:    0x2a4000 LB 0x548
284c.3ce4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1706
284c.3ce4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: Windows NT BASE API Client DLL
284c.3ce4: \SystemRoot\System32\apisetschema.dll:
284c.3ce4:     CreationTime:    2019-12-07T09:08:13.518339400Z
284c.3ce4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
284c.3ce4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x1f538
284c.3ce4:     NT Headers:      0xd0
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x31288ce0
284c.3ce4:     Image Version:   10.0
284c.3ce4:     SizeOfImage:     0x20000 (131072)
284c.3ce4:     Resource Dir:    0x1f000 LB 0x408
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Microsoft® Windows® Operating System
284c.3ce4:     ProductVersion:  10.0.19041.1
284c.3ce4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
284c.3ce4:     FileDescription: ApiSet Schema DLL
284c.3ce4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
284c.3ce4: supR3HardenedWinFindAdversaries: 0x800
284c.3ce4: \SystemRoot\System32\drivers\cfrmd.sys:
284c.3ce4:     CreationTime:    2014-06-26T05:33:42.000000000Z
284c.3ce4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
284c.3ce4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
284c.3ce4:     FileAttributes:  0x20
284c.3ce4:     Size:            0x9d20
284c.3ce4:     NT Headers:      0xe8
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Machine:         0x8664 - amd64
284c.3ce4:     Timestamp:       0x5004f2a1
284c.3ce4:     Image Version:   6.1
284c.3ce4:     SizeOfImage:     0xe000 (57344)
284c.3ce4:     Resource Dir:    0xc000 LB 0x3e0
284c.3ce4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
284c.3ce4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
284c.3ce4:     ProductName:     Windows (R) Win 7 DDK driver
284c.3ce4:     ProductVersion:  6.1.7600.16385
284c.3ce4:     FileVersion:     6.1.7600.16385 built by: WinDDK
284c.3ce4:     FileDescription: Safe Deletion Driver
284c.3ce4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: Calling main()
284c.3ce4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
284c.3ce4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
284c.3ce4: SUPR3HardenedMain: Respawn #2
284c.3ce4: supR3HardNtEnableThreadCreationEx:
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
284c.3ce4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
284c.3ce4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ntdll.dll)
284c.3ce4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
284c.3ce4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
284c.3ce4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\ntdll.dll (Input=ntdll.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
284c.3ce4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe4530000 'C:\WINDOWS\System32\ntdll.dll'
284c.3ce4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardenedWinDoReSpawn(2): New child 255c.41c4 [kernel32].
284c.3ce4: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
284c.3ce4: supR3HardNtChildGatherData: PebBaseAddress=0000000000ccf000 cbPeb=0x388
284c.3ce4: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffbe4530000 uNtDllChildAddr=00007ffbe4530000
284c.3ce4: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffbe45a4b00
284c.3ce4: supR3HardenedWinSetupChildInit: Initial context:
  rax=0000000000000000 rbx=0000000000000000 rcx=00007ff7afb57900 rdx=0000000000ccf000
  rsi=0000000000000000 rdi=0000000000000000 r8 =0000000000000000 r9 =0000000000000000
  r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  r14=0000000000000000 r15=0000000000000000  P1=0000000000000000  P2=0000000000000000
  rip=00007ffbe4582630 rsp=0000000000b9fad8 rbp=0000000000000000    ctxflags=0010001b
  cs=0033 ss=002b ds=0000 es=0000 fs=0000 gs=0000    eflags=00000200   mxcrx=00001f80
   P3=0000000000000000  P4=0000000000000000  P5=0000000000000000  P6=0000000000000000
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
284c.3ce4: kernel32.dll: timestamp 0x4e5c27cf (rc=VINF_SUCCESS)
284c.3ce4: supR3HardenedWinSetupChildInit: Start child.
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
284c.3ce4: supR3HardNtChildPurify: Startup delay kludge #1/0: 524 ms, 34 sleeps
284c.3ce4: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
284c.3ce4:  *0000000000000000-0000000000a5ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000a60000-0000000000a7ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000a80000-0000000000a9cfff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000a9d000-0000000000a9ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000aa0000-0000000000b9afff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000b9b000-0000000000b9dfff 0x0104/0x0004 0x0020000
284c.3ce4:   0000000000b9e000-0000000000b9ffff 0x0004/0x0004 0x0020000
284c.3ce4:  *0000000000ba0000-0000000000ba3fff 0x0002/0x0002 0x0040000
284c.3ce4:   0000000000ba4000-0000000000baffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000bb0000-0000000000bb1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000bb2000-0000000000bfffff 0x0001/0x0000 0x0000000
284c.3ce4:  *0000000000c00000-0000000000ccefff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000ccf000-0000000000cd1fff 0x0004/0x0004 0x0020000
284c.3ce4:   0000000000cd2000-0000000000dfffff 0x0000/0x0004 0x0020000
284c.3ce4:   0000000000e00000-000000007ffdffff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe1000-000000007ffe2fff 0x0001/0x0000 0x0000000
284c.3ce4:  *000000007ffe3000-000000007ffe3fff 0x0002/0x0002 0x0020000
284c.3ce4:   000000007ffe4000-00007ff55706ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557070000-00007ff557070fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff557071000-00007ff55707ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff557080000-00007ff5570a2fff 0x0002/0x0002 0x0040000
284c.3ce4:   00007ff5570a3000-00007ff7afb4ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ff7afb50000-00007ff7afb50fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afb51000-00007ff7afbc7fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc8000-00007ff7afbc8fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afbc9000-00007ff7afc11fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc12000-00007ff7afc12fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc13000-00007ff7afc13fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc14000-00007ff7afc18fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc19000-00007ff7afc19fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1a000-00007ff7afc1afff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1b000-00007ff7afc1efff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc1f000-00007ff7afc67fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
284c.3ce4:   00007ff7afc68000-00007ffbe452ffff 0x0001/0x0000 0x0000000
284c.3ce4:  *00007ffbe4530000-00007ffbe4530fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4531000-00007ffbe464bfff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe464c000-00007ffbe4693fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4694000-00007ffbe469ffff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46a0000-00007ffbe46aefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46af000-00007ffbe46affff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b0000-00007ffbe46b2fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe46b3000-00007ffbe4724fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume4\Windows\System32\ntdll.dll
284c.3ce4:   00007ffbe4725000-00007ffffffeffff 0x0001/0x0000 0x0000000
284c.3ce4: VirtualBoxVM.exe: timestamp 0x623a5dfe (rc=VINF_SUCCESS)
284c.3ce4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
284c.3ce4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
284c.3ce4: '\Device\HarddiskVolume4\Windows\System32\ntdll.dll' has no imports
284c.3ce4: supR3HardNtChildPurify: Done after 566 ms and 0 fixes (loop #0).
284c.3ce4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000d00000 LB 0x400000)
255c.41c4: Log file opened: 6.1.34r150636 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa04a6300
255c.41c4: supR3HardenedVmProcessInit: uNtDllAddr=00007ffbe4530000 g_uNtVerCombined=0xa04a6300 (stack ~0000000000b9f568)
284c.3ce4: supR3HardNtEnableThreadCreationEx:
255c.41c4: ntdll.dll: timestamp 0x7b5414ec (rc=VINF_SUCCESS)
255c.41c4: New simple heap: #1 0000000000f00000 LB 0x400000 (for 2052096 allocation)
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: System32:  \Device\HarddiskVolume4\Windows\System32
255c.41c4: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
255c.41c4: KnownDllPath: C:\WINDOWS\System32
255c.41c4: supR3HardenedVmProcessInit: Opening vboxdrv...
255c.41c4: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
255c.41c4: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
255c.41c4: Registered Dll notification callback with NTDLL.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\kernel32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\kernel32.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2110000 LB 0x002cd000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\KernelBase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\KernelBase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3f20000 LB 0x000bd000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\KERNEL32.DLL'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ff7afb50000 LB 0x00118000 C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
255c.41c4: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffbe45a4b00 pvNtTerminateThread=00007ffbe45cd790
284c.3ce4: supR3HardNtChildWaitFor: Found expected request 1 (CloseEvents) after 125 ms.
255c.41c4: \SystemRoot\System32\ntdll.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:24.962297600Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.011955800Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.242392000Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1eeb38
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x7b5414ec
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x1f5000 (2052096)
255c.41c4:     Resource Dir:    0x184000 LB 0x6fff8
255c.41c4:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1840f0 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1682
255c.41c4:     FileVersion:     10.0.19041.1682 (WinBuild.160101.0800)
255c.41c4:     FileDescription: NT Layer DLL
255c.41c4: \SystemRoot\System32\kernel32.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:16.157371700Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:16.176080300Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.008042100Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0xbb058
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x4e5c27cf
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0xbd000 (774144)
255c.41c4:     Resource Dir:    0xbb000 LB 0x520
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xbb0b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\KernelBase.dll:
255c.41c4:     CreationTime:    2022-05-13T09:37:25.904947200Z
255c.41c4:     LastWriteTime:   2022-05-13T09:37:25.981546200Z
255c.41c4:     ChangeTime:      2022-05-13T21:27:08.226771300Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x2cf640
255c.41c4:     NT Headers:      0xf0
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x458acb5b
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x2cd000 (2936832)
255c.41c4:     Resource Dir:    0x2a4000 LB 0x548
255c.41c4:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x2a40b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1706
255c.41c4:     FileVersion:     10.0.19041.1706 (WinBuild.160101.0800)
255c.41c4:     FileDescription: Windows NT BASE API Client DLL
255c.41c4: \SystemRoot\System32\apisetschema.dll:
255c.41c4:     CreationTime:    2019-12-07T09:08:13.518339400Z
255c.41c4:     LastWriteTime:   2019-12-07T09:08:13.518339400Z
255c.41c4:     ChangeTime:      2022-05-13T09:38:12.902031600Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x1f538
255c.41c4:     NT Headers:      0xd0
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x31288ce0
255c.41c4:     Image Version:   10.0
255c.41c4:     SizeOfImage:     0x20000 (131072)
255c.41c4:     Resource Dir:    0x1f000 LB 0x408
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0x1f060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Microsoft® Windows® Operating System
255c.41c4:     ProductVersion:  10.0.19041.1
255c.41c4:     FileVersion:     10.0.19041.1 (WinBuild.160101.0800)
255c.41c4:     FileDescription: ApiSet Schema DLL
255c.41c4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
255c.41c4: supR3HardenedWinFindAdversaries: 0x800
255c.41c4: \SystemRoot\System32\drivers\cfrmd.sys:
255c.41c4:     CreationTime:    2014-06-26T05:33:42.000000000Z
255c.41c4:     LastWriteTime:   2014-06-26T05:33:42.000000000Z
255c.41c4:     ChangeTime:      2020-10-11T11:10:28.369648400Z
255c.41c4:     FileAttributes:  0x20
255c.41c4:     Size:            0x9d20
255c.41c4:     NT Headers:      0xe8
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Machine:         0x8664 - amd64
255c.41c4:     Timestamp:       0x5004f2a1
255c.41c4:     Image Version:   6.1
255c.41c4:     SizeOfImage:     0xe000 (57344)
255c.41c4:     Resource Dir:    0xc000 LB 0x3e0
255c.41c4:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
255c.41c4:     [Raw version resource data: 0xc060 LB 0x380, codepage 0x0 (reserved 0x0)]
255c.41c4:     ProductName:     Windows (R) Win 7 DDK driver
255c.41c4:     ProductVersion:  6.1.7600.16385
255c.41c4:     FileVersion:     6.1.7600.16385 built by: WinDDK
255c.41c4:     FileDescription: Safe Deletion Driver
255c.41c4: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: Calling main()
255c.41c4: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
255c.41c4: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe: Signature #1/2: info status: 24202
255c.41c4: '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe' has no imports
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe)
255c.41c4: SUPR3HardenedMain: Final process, opening VBoxDrv...
255c.41c4: supR3HardenedEarlyCompact: Removed heap 1 (0x00000000f00000 LB 0x400000)
255c.41c4: supR3HardNtEnableThreadCreationEx:
255c.41c4: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll: Signature #1/2: info status: 24202
255c.41c4: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbdcfb0000 LB 0x00005000 C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 24202 (0x5e8a)) on \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VBoxSupLib.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbdcfb0000 'C:\Program Files\Oracle\VirtualBox\VBoxSupLib.DLL'
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #29 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\wintrust.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\wintrust.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'rpcrt4.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'rpcrt4.dll' -> '\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rpcrt4.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'msvcrt.dll' -> '\Device\HarddiskVolume4\Windows\System32\msvcrt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msvcrt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msvcrt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\Wintrust.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe26a0000 LB 0x0009e000 C:\WINDOWS\System32\msvcrt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msvcrt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe3970000 LB 0x00125000 C:\WINDOWS\System32\RPCRT4.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rpcrt4.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2510000 LB 0x00068000 C:\WINDOWS\System32\Wintrust.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c70000 LB 0x00100000 C:\WINDOWS\System32\ucrtbase.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\ucrtbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\ucrtbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1d70000 LB 0x00156000 C:\WINDOWS\System32\CRYPT32.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\crypt32.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\crypt32.dll
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-fibers-l1-1-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-fibers-l1-1-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-fibers-l1-1-1'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-synch-l1-2-0) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-synch-l1-2-0 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-synch-l1-2-0'
255c.41c4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(api-ms-win-core-localization-l1-2-1) -> 0x0, fPresent=1
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=api-ms-win-core-localization-l1-2-1 (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2110000 'api-ms-win-core-localization-l1-2-1'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\msasn1.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\msasn1.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1830000 LB 0x00012000 C:\WINDOWS\SYSTEM32\MSASN1.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\msasn1.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\system32\Wintrust.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcrypt.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcrypt.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcrypt.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000801:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1c40000 LB 0x00027000 C:\WINDOWS\System32\bcrypt.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1c40000 'C:\WINDOWS\system32\bcrypt.dll'
255c.41c4: bcrypt.dll loaded at 00007ffbe1c40000, BCryptOpenAlgorithmProvider at 00007ffbe1c451e0, preloading providers:
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\bcryptprimitives.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe23e0000 LB 0x00082000 C:\WINDOWS\System32\bcryptprimitives.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcryptprimitives.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe23e0000 'C:\WINDOWS\system32\bcryptprimitives.dll'
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD2',0,0) -> 0x0 (hAlgo=00000000014417e0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD4',0,0) -> 0x0 (hAlgo=0000000001441e60)
255c.41c4:     BCryptOpenAlgorithmProvider(,'MD5',0,0) -> 0x0 (hAlgo=0000000001442180)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA1',0,0) -> 0x0 (hAlgo=00000000014434b0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA256',0,0) -> 0x0 (hAlgo=00000000014437d0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'SHA512',0,0) -> 0x0 (hAlgo=0000000001443af0)
255c.41c4:     BCryptOpenAlgorithmProvider(,'RSA',0,0) -> 0x0 (hAlgo=0000000001443e10)
255c.41c4:     BCryptOpenAlgorithmProvider(,'DSA',0,0) -> 0x0 (hAlgo=0000000001444130)
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptsp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptsp.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe15f0000 LB 0x00018000 C:\WINDOWS\SYSTEM32\CRYPTSP.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptsp.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #18 'bcrypt.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\rsaenh.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\rsaenh.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'bcrypt.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'bcrypt.dll' -> '\Device\HarddiskVolume4\Windows\System32\bcrypt.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\bcrypt.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedScreenImage/NtCreateSection: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0cb0000 LB 0x00034000 C:\WINDOWS\system32\rsaenh.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptbase.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptbase.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1610000 LB 0x0000c000 C:\WINDOWS\SYSTEM32\CRYPTBASE.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\cryptbase.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\kernel32.dll (Input=kernel32.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe3f20000 'C:\WINDOWS\System32\kernel32.dll'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\wintrust.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\WINTRUST.DLL (Input=WINTRUST.DLL, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe2510000 'C:\WINDOWS\System32\WINTRUST.DLL'
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\CRYPT32.dll (rcNtResolve=0xc0150008) *pfFlags=0x2 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe1d70000 'C:\WINDOWS\System32\CRYPT32.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe4280000 LB 0x0001d000 C:\WINDOWS\System32\imagehlp.dll [fFlags=0x0]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\imagehlp.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\imagehlp.dll
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\rsaenh.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\system32\rsaenh.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
255c.41c4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffbe0cb0000 'C:\WINDOWS\system32\rsaenh.dll'
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe2c30000 LB 0x0009c000 C:\WINDOWS\System32\sechost.dll [fFlags=0x0]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #11 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\sechost.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\sechost.dll
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #10 'rpcrt4.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\gpapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\gpapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe0510000 LB 0x00023000 C:\WINDOWS\SYSTEM32\gpapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\gpapi.dll [lacks WinVerifyTrust]
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\profapi.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\profapi.dll
255c.41c4: supR3HardenedDllNotificationCallback: load   00007ffbe1b80000 LB 0x0001f000 C:\WINDOWS\SYSTEM32\profapi.dll [fFlags=0x0]
255c.41c4: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\profapi.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #0 'msvcrt.dll'.
255c.41c4: supR3HardenedWinVerifyCacheScheduleImports: Import todo: #8 'crypt32.dll'.
255c.41c4: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume4\Windows\System32\cryptnet.dll)
255c.41c4: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume4\Windows\System32\cryptnet.dll
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'crypt32.dll'...
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: 'crypt32.dll' -> '\Device\HarddiskVolume4\Windows\System32\crypt32.dll' [rcNtRedir=0xc0150008]
255c.41c4: supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume4\Windows\System32\crypt32.dll [lacks WinVerifyTrust]
255c.41c4: supR3HardenedWinVerifyCacheProcessImportTodos: Processing 'msvcrt.dll'...
255c.41c4: supR3HardenedWin",Murdoch
20967,"Sometimes mouse works only in part of the screen, 6.1.34 with Ubuntu 22.04 guest",Linux,VirtualBox 6.1.34,2022-06-03T14:52:12Z,2022-06-03T14:52:12Z,2022-06-03T14:52:12Z,"Host: Windows 10, Guest: Ubuntu 22.04

When booting the Guest OS, occasionally mouse support works only partially:
* Mouse clicks work in the left-side of the dock, but not with rest of the desktop
* Mouse cursor is correctly set and shows everywhere
* After right-clicking a dock item the context menu can be properly clicked
* In full-screen mode additionally the small top-right triple icon menu works as well (but not in windowed mode)
* Keyboard support seems to work properly, and if I e.g. open Terminal from the dock, keyboard input for the terminal works although mouse input doesn't work.
* Switching between PS/2 or Tablet as VM Pointing Device setting doesn't seem to affect the issue.

Additional details:
CPU type core i7-8700K, VT-x, Nested VT-x and Nested Paging enabled. (Probably not relevant)

WORKAROUND:
The issue seems to go away if Wayland is disabled by editing /etc/gdm3/custom.conf

Forum thread:
https://forums.virtualbox.org/viewtopic.php?f=3&t=106184",jlauha
20966,Ova/Ovf Signature Verification Issue,other,VirtualBox 6.1.34,2022-06-03T14:10:11Z,2022-06-03T14:10:11Z,2022-06-03T14:10:11Z,"I sign my ovf file with my own code signing certificate. I am getting a certificate validation error while importing the resulting signed ovf file. I am getting this error even though I upload the SubCA and CA certificates of the signing certificate to the Windows Certificate Store.

I downloaded the source code of the 6.1.34 version of VirtualBox and debug it on my windows machine. And I found that the problem was because of the Name Constraints extension in the SubCA certificate of the certificate I signed.

While reading SubCA certificate from Windows Certificate Store on rtCrStoreAddCertsFromNative method, RTCrX509Certificate_DecodeAsn1 method gives an error in the relevant SubCA certificate. The error message reads: 0x00000000033ae4e8 ""CurCtx.Cert.TbsCertificate.T3.Extensions.papItems[#].ExtnValue.NameConstraings. It gives error 0x80 (expected 0x10/0x20)'

What kind of a problem is there in the SubCA certificate, can you help with this?",MustafaBayrak
20959,Unable To Insert Guest Additional CD Image,Windows,VirtualBox 6.1.34,2022-05-28T11:41:34Z,2022-06-03T13:38:45Z,2022-06-03T13:38:45Z,"I Can't Insert Guest Additional CD Image I Need To Do It '''Manually'''
From The Folder, I'm Windows 10 64 Bit Virtualbox 6.1.34 Please Fix It",Miniblox Gaming
20963,Window decorations do not scale correctly when moved across monitors,Linux,VirtualBox 6.1.34,2022-05-31T21:25:43Z,2022-05-31T21:25:43Z,2022-05-31T21:25:43Z,"I have a multi monitor setup on my windows 10 host.  One of the screens has a much higher DPI than the others so I ran it at native resolution and use scaling to keep the same visual appearance as the other.  This is the microsoft recommended approach, and is the default configuration for this device.

Under this setup, any virtual box window always has the scaling for that first monitor applied - when I move any VB window to the other display, the title bar is twice as big as it should be, and windows that open there are sized twice as big as you'd expect.  Window contents appear to scale fine.

This doesn't happen with any other application that I've found so far.  All other apps scale correctly depending which monitor they on.

An easy test is to have a common edge between the monitors and move a window so it's half on each  monitor, then move and back and forth so the majority falls on different monitors - you will see the scaling take affect as you do, and notice that VB windows behave differently to other applications.

To reproduce:
1. Set up two monitors, and configure the main monitor with a scale factor of 200%
2. Open up the main VirtualBox window, and move it between the monitors - observe the size of the title bar as you do so.  Slowly move until 50% of the window is on the other monitor, and observe changes.  Repeat these steps with a non VB window (e.g. notepad, explorer) to see the difference",gkcgareth
20946,No audio Pop!OS 22.04 guest / Virtualbox 6.1.34,Linux,VirtualBox 6.1.34,2022-05-18T07:22:07Z,2022-05-18T07:22:07Z,2022-05-18T07:22:07Z,"Hello Community,

I've got no in&out audio anymore since upgrading my vm to release Pop!OS 22.04. Maybe because the audio subsystem is now using Pipewire ? 

More precisely, for Windows DirectSound + Intel HD Audio. Only ICH AC97 does produce sound. But it's heavily garbled. 

Since this is an Ubuntu based distribution I presume this happens to all Ubuntu 22.04 releases. 

Rebuilding the kernel with the guest additions didn't help.

Is there anything I can try or help with to resolve this issue ?",JLC
20943,Latest Win 11 updates causing total fault of Virtualbox ver.6.1.34,Linux,VirtualBox 6.1.34,2022-05-15T06:06:30Z,2022-05-15T06:06:30Z,2022-05-15T06:06:30Z,"Environment: PC HP EliteDesk 800 G8 Tower PC
Processor	11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz   2.50 GHz
Installed RAM	16,0 GB (15,7 GB usable)
System type	64-bit operating system, x64-based processor

OS Windows 11 (upgrade from Win 10 on day of first installation 11-04-2022)
Edition	Windows 11 Pro
Version	21H2
Installed on	‎11/‎04/‎2022
OS build	22000.593
Experience	Windows Feature Experience Pack 1000.22000.593.0

Network private IP 192.168.0.x
Network Adapter Intel Ethernet Connection (14) I219-LM

VirtualBox Oracle ver.6.1.34
with Bridged Adapter attached to Intel Ethernet Connection (14) I219-LM
Adapter Type Intel PRO/1000 MT Desktop (82540EM)

Total fault description:

After start of VM (Debian10 iso image) in early starting phase entire process stoped with VM total failure. 
Until 26-04-2022 (before Win11 update) was this VM running without any problem as well as several other Debian 8, 9, 10 VMs.
After updates on 26-04-2022 with:
Cumulative Update for Windows 11 for x64-based Systems (KB5012643)
Cumulative Update for Windows 11 for x64-based Systems (KB5012592)
total fault appears as
collision in net drivers - VirtualBox Host-Only Ethernet Adapter) Cumulative Update for Windows 11 for x64-based Systems (KB5012643) 

After uninstall of updates the VM is working without any problem.

Supposed fault source:
VirtualBox driver 'Host-Only Ethernet Adapter' is unable to run with newest Win 11 updates.

Remarks: 
When fault occurs I done plenty of tests with different VirtualBox Network settings (NAT,..) and Intel drivers but no solution found. Only uninstall of latest Win updates allowed fault-free run. 
New updates of Win11 published in May 2022 are causing the same problem with VirtualBox.",jotcomponents
20926,"2 screens in a guest (extended), the mouse pointer is not displayed correctly on the 2nd screen",Windows,VirtualBox 6.1.34,2022-05-03T08:31:35Z,2022-05-03T08:31:35Z,2022-05-03T08:31:35Z,"Hello, I need 2 screens in a Windows guest system. The host system (Windows, VirtualBox 6.1.34) is equipped with 2x 4k monitors (laptop + monitor connected via HDMI). In the guest (Windows) I need 2x Full HD resolution. For this I use the function VirtualBox→Display→Virtual Monitor 1 or Virtual Monitor 2→To 200%. The display is expanded to monitor 2 (monitor 1 is the main monitor). When moving the window in Monitor 2 (e.g. Notepad), the mouse pointer is not displayed correctly in the guest
see picture_01.png
The behavior also occurs when the mouse is moved over the control elements of a window (e.g. vertical scroll bar of Notepad). The behavior is independent of the operating system (guest). The behavior is independent of the program (guest). The behavior also occurs when the guest is operated with 2x 4k resolution (scale to 100%). The behavior does not occur on monitor 1 (main Monitor).
see picture_02.png
For help, i thank you in advance",reine667
20925,"When scaling a Windows Guest, the mouse pointer is not displayed correctly in the guest",Windows,VirtualBox 6.1.34,2022-05-03T08:06:36Z,2022-05-03T08:06:36Z,2022-05-03T08:06:36Z,"Hello, I need a scaled display in the guest system (Host→4k, Guest→FullHD). The host system (Windows, VirtualBox 6.1.34) is equipped with 2x 4k monitors (laptop + monitor connected via HDMI). In the guest (Windows) I need a Full HD resolution (1 monitor). For this I use the function VirtualBox→Display→Virtual Monitor 1→Scale to 200%. When changing the width of columns (e.g. in Windows Explorer), the mouse pointer is not displayed correctly in the guest.
see picture_01.png
In contrast, if the guest is running at a 4k resolution (scale to 100%)
see picture_02.png
the mouse pointer is displayed correctly. The behavior is independent of the operating system (Guest). The behavior is independent of the program (Guest). Changing the graphics controller on the guest (VBoxVGA, VBoxSVGA) does not change the behavior. For help, i thank you in advance ",reine667
20908,Cannot install or delete VirtualBox,Windows,VirtualBox 6.1.34,2022-04-22T16:30:47Z,2022-04-26T12:47:42Z,2022-04-26T12:47:42Z,I migrated VitualBox from my Windows 10 computer to my Windows 11 computer. VirtualBox won't start; trying to Repair it is unsuccessful; trying to Reinstall it is unsuccessful; trying to Delete it is unsuccessful. Please help!,HorseyBob
20906,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,VirtualBox 6.1.34,2022-04-22T00:50:34Z,2022-04-22T00:50:34Z,2022-04-22T00:50:34Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
21061,Shared folder Automount not working properly Linux Mint 21 Cinnamon,Linux,VirtualBox 6.1.36,2022-08-13T09:15:34Z,2023-02-04T08:53:42Z,2023-02-04T08:53:42Z,"Automount works perfectly in my older Linux Mint 20.3 Cinnamon VM.
I installed Linux Mint 21 Cinnamon. But automount does not work properly.
It mounts the folder and I gave permissions to my user to vboxsf
But the sub folders or files are randomly locked without permissions to read/write. It seems some files/folder are owned by root, those works and some are unknown owner those don't work.
Rebooting will randomly change which file/folder have root or unknown owner.

Latest VBox and guest additions is installed.

I tried disabling automount and doing a manual mount or adding to /etc/fstab and both work perfectly.
",Munch
21339,"USB Filter PortNumber field formatting for ports higher than 9 => fixed in SVN/next 7.0.x,6.1.x maintenance",Windows,VirtualBox 6.1.36,2022-12-14T20:31:59Z,2022-12-19T08:54:13Z,2022-12-19T08:54:13Z,"Inability to insert a PortNumber higher than 9, the ""Port"" field of the USB Filter only accepts numeric characters, this makes the insertion of port numbers higher than 9 not possible, considering that this field reads hexadecimal inputs, the insertion of a port number like 13(000d) not possible.
As a workaround, manual input of the hex value in the .vbox file of the guest works.

For further information: https://forums.virtualbox.org/viewtopic.php?f=6&t=108063",fantinel
21194,Export creates a defective .ova file (missing disk image) : cannot import itself back.,Linux,VirtualBox 6.1.36,2022-10-22T19:25:08Z,2022-10-22T19:25:08Z,2022-10-22T19:25:08Z,"I am using VBox 6.1.36 under Windows 10 Pro.

When I exported my VM from VirtualBox so that it will be imported to VMWare player, etc., VMware Player, and VMWare workstation pro  does not read the disks correctly (I think). 
The number of disks recognized by VMWare player was about half the numbers of attached disks used in VirtualBox. So the import basically failed.

So I tried to read the exported description back to VirtualBox to see what happens.

To my surprise, VirtualBox reported the following error, which collaborates my observation of missing disks in VMWare Player, etc.

--- Begin Quote: The following the error I saw. It is under Japanese Windows 10 Pro.

{{{


仮想アプライアンス""J:\NEW-VMWARE-DIR\debian64bit-Rev02-transition.ova""のインポートに失敗しました。

The above says, VBox failed to import the *.ova description.


&lt;vbox:Machine&gt; element in OVF contains a medium attachment for the disk image 10bf7d63-35a5-4f22-87fd-b11a1634da12 but the OVF describes no such image.

終了コード : E_FAIL (0x80004005)
コンポーネント: ApplianceWrap
インターフェース: IAppliance {86a98347-7619-41aa-aece-b21ac5c1a7e6}
}}}


---- end quote

The original VM seems to work just fine as far as I use it to develop patches for Thunderbird mail client and other tasks.
",ci-zephyurus
21104,VirtualBox.chm index missing?,Windows,VirtualBox 6.1.36,2022-09-09T17:17:52Z,2022-09-09T17:17:52Z,2022-09-09T17:17:52Z,"I am unable to search the help file.
It appears there is no index to search.
Can I add/build one (I do not know if the User can add/create an index) or can you update the help file to be searchable?

Please advise.
Thanks, Tracey
Searching for USB results in ""No Topics Found"" ",Tracey
21085,mp bios bug 8254,Linux,VirtualBox 6.1.36,2022-08-31T11:47:09Z,2022-08-31T11:47:09Z,2022-08-31T11:47:09Z,bende bios bug 8254  noapic hatası veriyor bana yardımcı olun tıkandım kaldım,seafflyy
21083,EFI shell fails to detect non-ESP partitions,all,VirtualBox 6.1.36,2022-08-29T19:26:43Z,2022-08-29T19:29:32Z,2022-08-29T19:29:32Z,"Starting with 6.1.34, EFI (both shell and ""GUI"") fails to detect non-ESP partitions in optical media.  Booting from the media using the included boot loader works.  However, it's no longer possible to bypass the boot loader and boot directly from the non-ESP partitions.

I've tested a Windows 10 host with VirtualBox 6.1.34 and 6.1.36.  I've observed the problem with debian-11.2.0-amd64-netinst.iso, ubuntu-22.04-live-server-amd64.iso, and FreeBSD-13.0-RELEASE-amd64-disc1.iso.

This worked in 6.1.32.",ov2k
21060,Getting memory reference error after upgraded to Virtualbox 6.1,Windows,VirtualBox 6.1.36,2022-08-12T14:01:52Z,2022-08-22T21:48:09Z,2022-08-22T21:48:09Z,I am getting the memory reference error after upgrading to Virtualbox 6.1. Can you please help solving the issue?,Natarajan Arumugam
21032,Crash on start up,other,VirtualBox 6.1.36,2022-07-24T19:24:34Z,2022-08-20T13:35:32Z,2022-08-20T13:35:32Z,"I recently updated to 6.1.36 and previously working machines now crash. I have redownloaded the usb3 extensions before positing this bug.

To reproduce :-
Take a working machine of any guest type.
Change usb to usb 3
Create a usb disk controler
(still boots)
Attach a disk image to the usb controller
(does not boot : ... references memory at 0x00000000)",sceedy
21069,VM crash diuring install lazarus or anower big packageset,Linux,VirtualBox 6.1.36,2022-08-18T12:13:01Z,2022-08-18T14:01:39Z,2022-08-18T14:01:39Z,"Hello.

BEFORE, latest activity:
I maked before crushes disk shrunked: VBoxManage modifyhd /path/to/VDI/VM.vdi --compact  (path are different, instructions https://askubuntu.com/questions/1092812/zerofree-on-ubuntu-18-04)

then i see excelent resul: VDI file set to 21GB from 500GB 

After somes reboot i try to launth TLauncher und try to install java 8 -- VM crush.
Then i try to install new lazarus - VM crush.  

",Дмитро
21064,My virtual machine half screen blank,other,VirtualBox 6.1.36,2022-08-15T16:03:08Z,2022-08-15T16:03:08Z,2022-08-15T16:03:08Z,"[[Image(https://i.postimg.cc/vTfcBVHY/IMG-20220815-211452.jpg)]]

",Saikat
21059,Virtualbox VM crashed while installing Virtualbox Guest Additions in win8.1 guests,Windows,VirtualBox 6.1.36,2022-08-12T03:48:32Z,2022-08-12T03:48:32Z,2022-08-12T03:48:32Z,"I was installing VB Guest Additions in a Windows 8.1 guest. After a few seconds, when I was prompted to install a video driver in the guest and I clicked ""Yes"", the virtual machine stopped responding and the host prompted a memory error.  Then,I could never again boot the VM using the hard disk because the same error pops up every time.

'''Reproduce'''
1. Create a win8.1 VM
2. Install win8.1.
3. Try to install VBAdditions.

'''Environment'''
Version: VB 6.1.36
Host OS: Windows 11 22H2
Guest OS: Windows 8.1

",fyc
21058,Erro ao inicializar maquina virtual,Windows,VirtualBox 6.1.36,2022-08-10T13:55:48Z,2022-08-10T13:55:48Z,2022-08-10T13:55:48Z,"Bom dia,

O seguinte erro aparece ao inicializar a maquina virtual.
Falha ao abrir uma sessão para a máquina virtual:
The virtual machine 'VIRT' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)

Já fiz vários testes para sanar o erro, mas sem sucesso, incluindo:
Desinstalar e instalar novamente, atualizar para a ultima versão, desativar Hyper-V do Windows e entre outros básicos. O mais estranho que o erro começou ""do nada"". Podem me ajudar?
",Gugu Aquino
21057,Snapshots restore files on Writetrough Disk,Windows,VirtualBox 6.1.36,2022-08-09T18:50:57Z,2022-08-09T18:50:57Z,2022-08-09T18:50:57Z,"Hello dear support team. My snapshots restore files on Writetrough Disk.
Here my thread on forum https://forums.virtualbox.org/viewtopic.php?f=6&t=106742

I use two VDI on my VM. First VDI: Normal type. Created for system using (OS, applications, system configuration). I want to take snapshots only from Normal disk type.
Second VDI: Write-through type. Created for file storage. I don't want to take snapshot from Write-through disk.
But files are restored on Write-through disk... I do not understand anything.
Please check me step by step. I will try to be as detailed as possible.
1. I created new VM with new VDI (Normal type for system using). Capacity 30GB. Screenshot https://www.dropbox.com/s/gy764nib8kljrdc/Screenshot_8.png?dl=0
2. I created new VDI (Write-through type for file storage). Capacity 50GB. https://www.dropbox.com/s/2g2cfr621yuqo93/Screenshot_12.png?dl=0
3. Check attached to VM disks. https://www.dropbox.com/s/8ospntq1fx4w9l5/Screenshot_16.png?dl=0 second https://www.dropbox.com/s/8zr79tm9zp6a2ny/Screenshot_17.png?dl=0
4. Now I'm install Windows 10 on 30GB disk (Normal type) https://www.dropbox.com/s/g0uk8bkozy51scy/Screenshot_18.png?dl=0
5. Initialization wright-trough disk after Windows installation https://www.dropbox.com/s/0dnlszujxk5akcw/Screenshot_19.png?dl=0
6. Now I have 2 local disk in Windows Explorer https://www.dropbox.com/s/tw8vf0c14dcf18j/Screenshot_22.png?dl=0
Now it will be interesting
7. Create test folders https://www.dropbox.com/s/fhv3vg2x9z4gnhv/Screenshot_23.png?dl=0
8. Take snapshot https://www.dropbox.com/s/ce1x0r39d34ebfy/Screenshot_25.png?dl=0
9. Test folders deleted using SHIFT+DEL https://www.dropbox.com/s/icjf5t3wyjmz4qh/Screenshot_28.png?dl=0
10. Shutting down VM and restore Test 1 snapshot https://www.dropbox.com/s/orv5cr5ijt29v65/Screenshot_31.png?dl=0
I expect to restore test folder on only drive C:\ (Normal type)
11. Why test folder restored on Write-trough disk (E:\)? https://www.dropbox.com/s/edqmh7ojn7ngmbx/Screenshot_33.png?dl=0",CyanCetus
21056,[CRITICAL] Network driver causing system crashes on windows 11,all,VirtualBox 6.1.36,2022-08-08T20:53:39Z,2022-08-08T20:53:39Z,2022-08-08T20:53:39Z,"I'd seen this bug reported in other places, but no currently open tickets mention hard, system-wide crashes. One of them mentions being disconnected from the wifi for a brief time, but this is way worse than just that.

I hadn't even used VirtualBox at all since my computer started up, but any time I try to load more intensive websites on my host operating system (completely independent from VB I might add), it has about a 1 in 10 chance of crashing my entire OS. Straight to black screen, computer shuts off and reboots.

I only use virtualbox once in a while, so imagine my surprise when I started investigating why my computer keeps crashing only to find that this event was found before every crash. Initially I thought that was a bug in this version of the software and updated to 6.1.36, but nothing changed on that front. 

I love open source projects, but honestly if this isn't fixed soon I may have to switch to a proprietary VM software, simply because I can't leave this installed on my computer if it's going to cause crashes every other day. It didn't used to happen before I updated to the most recent version of windows, but the fact remains that this driver is still the cause of those crashes.

The problem always correlates with an event ""The driver detected an internal driver error on \Device\VBoxNetLwf."" The event has ID 12 and is listed under the keyword ""classic"".",pizzamonkey
21054,Ability for the guest to write on a online-for-the-host partition,Linux,VirtualBox 6.1.36,2022-08-07T18:00:10Z,2022-08-08T07:55:31Z,2022-08-08T07:55:31Z,"because as I saw it's read-only .

On my PC's hard disk with Windows 10 Home :

Host : Windows 10 Home

Guests :

firmware-testing-amd64-netinst.iso ( a Debian installer ) : installing  Debian physically on my PC's hard disk dual-boot with Windows 10 Home , everything works except GRUB isn't installed on the original ESP ( EFI system partition ) with EFI\Microsoft\Boot etc .

debian-live-11.4.0-amd64-xfce+nonfree.iso ( a Debian live ) : cannot write e.g. a file on a PC's hard disk partition ( original ESP , C: , D: , Debian partition ( me on ext2 ) ) .

See https://forums.virtualbox.org/viewtopic.php?f=6&t=106689 .

Is it a regression related to https://www.virtualbox.org/ticket/14425 ?",ecccc3
21048,"Honor Windows' ""Automatically hide scroll bars"" setting",all,VirtualBox 6.1.36,2022-08-04T11:51:50Z,2022-08-04T11:51:50Z,2022-08-04T11:51:50Z,"VirtualBox Manager automatically hides the scroll bar of the VM list and it seems you can't turn this behavior off in preferences. It would be nice if VirtualBox would always show the scroll bar if the user disabled ''Ease of Access'' -> ''Display'' -> ''Automatically hide scroll bars in Windows'' in Windows settings. The corresponding registry value is 
{{{
HKCU\Control Panel\Accessibility\DynamicScrollbars
}}}",hqngl
21040,VM blocked on humongus amounts of disk read,Linux,VirtualBox 6.1.36,2022-07-28T16:20:26Z,2022-08-02T12:01:44Z,2022-08-02T12:01:44Z,"Problem occurring since updating to 6.1.36 from 6.1.34

running condition tested for reproduction:
  - on a old windows 10 host install, run old or new Linux guests (both EFI, and non EFI) that were working on 6.1.34
  - on a fresh windows 10 host install (21H2), with the same scenarios.

steps to reproduce:
  - from a system without VirtualBox installed, or with VirtualBox 6.1.34 installed:
    - install or update to 6.1.36,
    - try to run any linux guest

observed behavior:
  - at startup a 19GB vdi guest generates a 100 second read @ 600+ MB/s (so about 60GB read) blocking the guest execution for the whole time,
  - after logging in, a second wave of read is triggered (about 30s, so 20GB), 
  - and on shutdown the read is also triggered for about 90 seconds rendering the whole process very cumbersome and sluggish.
  - note: using the menu to insert guest additions CD also triggers a read freeze.",os19000
21042,I can't open the app,Windows,VirtualBox 6.1.36,2022-08-01T18:32:01Z,2022-08-01T19:06:00Z,2022-08-01T19:06:00Z,"So I just tried to install the app but when I try to launch it after installing it it just keeps on the background and it doesnt start up, I tried everything I found on google but noyhing works",ZenZen
21036,VB Startup after Host Shutdown without VB Guest Shutdown,Windows,VirtualBox 6.1.36,2022-07-26T12:35:31Z,2022-07-26T15:22:24Z,2022-07-26T15:22:24Z,"VirtualBox doesn't show up after a host shutdown (Start/Shutdown) without VB guest shutdown (VB was running and killed by windows shutdown)

The Windows 11 VM was perfectly running prior to this accidently caused shutdown. 

Host:
  Windows 10 Enterprise / 21H2 / 19044.1826[[BR]]
  AMD Ryzen 9 3950X 16-Core Processor[[BR]]
  RAM 64,0 GB[[BR]]
 
Guest:
  Winwows 11 Professional / latest updates (yesterday)

VB Processes running:
 VBoxSDS.exe: ~ 1.8 MB

 VBoxSVC.exe: continously increasing -> >100GB

 VirtualBox.exe: 6.6 MB 

In task manager one can see continuously increasing memory consumption of VBoxSVC.exe which results in a host crash (in my case at over 100GB (64GB RAM installed)  

",Pigo
21035,Upgrading from VirtualBox 6.1.34 to 6.1.36 on Windows results in incorrect drivers,other,VirtualBox 6.1.36,2022-07-26T06:49:05Z,2022-07-26T06:49:05Z,2022-07-26T06:49:05Z,"Windows 11 Home. No previous installations of VirtualBox. Steps to reproduce:

Install 6.1.34. Install Extensions for 6.1.34. Create a VM (does not matter what it contains). Upgrade to 6.1.36. Install Extensions for 6.1.36.

Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Uninstall VirtualBox. Reboot. Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys.

Manually remove VBoxNetAdp6.sys, VBoxNetLwf.sys and VBoxUSB.sys. Reboot.

Install 6.1.36. Install Extensions for 6.1.36 (confirm re-installation of extensions). Inspect \Windows\System32\drivers\vbox*.sys. You should see: VBoxNetAdp6.sys, VBoxNetLwf.sys, VBoxSup.sys and VBoxUSBMon.sys.

It would appear that (1) the upgrade code in the 6.1.36 installer does not correctly remove the older drivers, (2) the 6.1.36 uninstaller does not correctly remove the (older) drivers, and (3) the upgrade code in the 6.1.36 installer does not correctly install the new drivers.",weird_stuff_happens
21029,no bidirectional clipboard in windows 11 host / ubuntu 18.04 guest,Linux,VirtualBox 6.1.36,2022-07-22T18:28:54Z,2022-07-25T15:03:11Z,2022-07-25T15:03:11Z,"Hi, 

I can't remember when this stopped working, just recently upgraded virtualbox and the vbox guest additions, and now I realize this is not working:

 * bidirectional clipboard

Guest Additions:

{{{
systemctl status vboxadd.service
● vboxadd.service
   Loaded: loaded (/opt/VBoxGuestAdditions-6.1.36/init/vboxadd; enabled; vendor preset: enabled)
   Active: active (exited) since Fri 2022-07-22 14:47:29 -03; 37min ago
  Process: 643 ExecStart=/opt/VBoxGuestAdditions-6.1.36/init/vboxadd start (code=exited, status=0/SUCCESS)
 Main PID: 643 (code=exited, status=0/SUCCESS)

jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: Starting.
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: VirtualBox Guest Additions kernel modules 6.1.36
jul 22 14:47:28 x1buntu vboxadd[643]: r152435 are
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: already available for kernel 5.4.0-122-generic and
jul 22 14:47:28 x1buntu vboxadd[643]: do not require to be rebuilt.
jul 22 14:47:28 x1buntu useradd[924]: failed adding user 'vboxadd', data deleted
jul 22 14:47:28 x1buntu useradd[925]: failed adding user 'vboxadd', data deleted
jul 22 14:47:28 x1buntu vboxadd[643]: VirtualBox Guest Additions: Running kernel modules will not be replaced until
jul 22 14:47:28 x1buntu vboxadd[643]: the system is restarted
jul 22 14:47:29 x1buntu systemd[1]: Started vboxadd.service.
}}}

Guest OS:

{{{
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic
}}}

Host OS: Windows 11 Pro 21H2 (22000.795), x64",arfe
21026,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,VirtualBox 6.1.36,2022-07-20T12:29:17Z,2022-07-20T12:29:17Z,2022-07-20T12:29:17Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
21025,Screen lock in Windows 10 Host makes the Linux Guest unresponsive (regression),Linux,VirtualBox 6.1.36,2022-07-20T10:59:23Z,2022-07-20T10:59:23Z,2022-07-20T10:59:23Z,"After upgrading from 6.1.30 to 6.1.34, I've started to notice that my Centos 7.8 Guest goes unresponsive on regular basis.

I've been able to pinpoint it to the screen lock in the Windows 10 21H2 Host. Whenever I unlock the screen the VBoxHeadless.exe process uses 100% of all of the cores available to the Guest machine. Guest is unreachable neither by ssh nor by GUI.

This happens regardless of the graphic display used, and also in the headless start. Also changing hypervisor between the Hyper-V and KVM does not make a difference.

VirtualBox 6.1.36 behaves the same as 6.1.34, however downgrading to the 6.1.30 solves the issue.

Logs do not contain anything except repeating pattern of:
00:02:22.924401 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:02:24.627881 VMMDev: GuestHeartBeat: Guest is alive (gone 5 713 045 344 ns)
00:03:09.694062 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:15.648850 VMMDev: GuestHeartBeat: Guest is alive (gone 9 990 252 305 ns)
00:03:30.642448 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:30.792413 VMMDev: GuestHeartBeat: Guest is alive (gone 4 159 194 451 ns)
00:03:47.088470 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:52.836984 VMMDev: GuestHeartBeat: Guest is alive (gone 9 762 953 270 ns)
00:03:56.874575 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:03:57.771949 VMMDev: GuestHeartBeat: Guest is alive (gone 4 934 966 056 ns)
00:04:01.784622 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
",MichalBrz
21107,VM's keep freezing,Windows,VirtualBox 6.1.38,2022-09-17T15:40:23Z,2023-02-03T08:53:27Z,2023-02-03T08:53:27Z,"Have several different VM's.  They all keep freezing unless I click the mouse pointer in the VM window.  Even tried pausing VM from menu, then unpausing.  Each time the VM runs for about a second or two before it freezes up.  The VM's boot up okay, and windows desktop runs and initializes, but after a few minutes the VM's keep pausing.

Very repeatable.  LMK if more information is needed.  Attached log here from one VM.
Thank you",ArtZ
21393,chrash of VM during shutdown,Windows,VirtualBox 6.1.38,2023-01-03T19:26:43Z,2023-01-03T19:26:43Z,2023-01-03T19:26:43Z,I have frequent crashes during the shutdown of the virtual machine.,tiria
21097,Automatic update of VBox and Failed to open a session for the virtual machine Ubuntu => fixed in SVNsvn,Linux,VirtualBox 6.1.38,2022-09-05T12:04:39Z,2022-11-29T03:04:01Z,2022-11-29T03:04:01Z,"Few weeks ago, when I had updated VirtualBox, I had faced an error with opening a session for the virtual machine (guest OS is Ubuntu).
Found a suggestion that VBox version 6.1.32 is good and I had downgraded the VBox and everything works fine, I can start a session for the VM.
I had turned off the automatic update of VirtualBox, but few times since then, VirtualBox was updated automatically to the newest version.

For some, unknown to me reason, I can't use the newest VBox version, but my VBox keep upgrading even when automatic update is turned off.
What is the solution? Should I downgrade my VBox every day?",AZidai
21290,nvme error,Windows,VirtualBox 6.1.38,2022-11-20T15:44:41Z,2022-11-20T15:44:41Z,2022-11-20T15:44:41Z,I am not able to work with a drive nvme. I have a nvme disk Samsung 970Evo Plus but if I try to use a disk connected to the nvme drive it does not work al all.,tiria
21289,crash during shutdown,Windows,VirtualBox 6.1.38,2022-11-20T00:08:27Z,2022-11-20T00:08:27Z,2022-11-20T00:08:27Z,the system crashes when I shutdown it,tiria
21119,Restoring a saved Guest does not restore the saved display size,Windows,VirtualBox 6.1.38,2022-10-08T15:07:17Z,2022-10-08T15:07:17Z,2022-10-08T15:07:17Z,"To produce the error. Start a Windows 10 Guest and when idle save the guest, noting the screen display size. Restart the guest VM and note the screen size after allowing time for guest to become idle. Note the screen size is NOT the same as the saved guest VM was.
This happens whether the guest VM is Windows 10 or Windows 11.
In some cases, the correct screen display size is created at the beginning of the restore but is changed to 640x480 when the restore is completed.",MacNala2
21118,USB isochronous transfers cause problems under OS/2 guest,other,VirtualBox 6.1.38,2022-10-03T07:04:10Z,2022-10-03T07:15:20Z,2022-10-03T07:15:20Z,"Host: Windows 11, guest: OS/2

If I try to play sounds via a USB connected audio 1.0 or audio 2.0 sound device, the sound always is extremely choppy.
This directly relates to ticket #18947, but this time I selected ""USB"" as the component instead of ""Audio"" because this clearly is a USB issue with isochronous transfers.
If needed, I could provide tracing information from the guest USB audio driver or I could provide additional analysis if requested (thinking about the ""samples per microframe"" value that the USB audio 2.0 device reports back on its ""sync isochronous in"" endpoint).",lerdmann
21117,Windows 11 host machine's touchscreen stops working while running a Linux guest VM.,other,VirtualBox 6.1.38,2022-10-02T19:05:07Z,2022-10-02T19:05:07Z,2022-10-02T19:05:07Z,"I have a HP Windows 11 ""All-in-One"" PC with a touchscreen. When I attempt to run Home Assistant in VirtualBox, the host's touchscreen stops responding, requiring the use of a mouse instead. Is there a fix for this?",WillD
21103,guest resolution defaults to 640x480 waking from sleep state,Windows,VirtualBox 6.1.38,2022-09-09T00:14:10Z,2022-09-29T13:28:38Z,2022-09-29T13:28:38Z,"every time i start a guest with win10 from saved state 
it defaults to 640x480 even though its saved with a resolution
1600x900",sphinxios
21114,Critical error. The memory could not be read.,Windows,VirtualBox 6.1.38,2022-09-29T13:24:38Z,2022-09-29T13:24:38Z,2022-09-29T13:24:38Z,"Unfortunately, I don't have a log file or a reproduction step for the error.",Eugene
21101,installation folder is not remembered when upgraded,other,VirtualBox 6.1.38,2022-09-08T23:42:16Z,2022-09-08T23:42:16Z,2022-09-08T23:42:16Z,"the folder is not remembered when updated it falls bach to
the default on every time  tried several versions even the latest 6.1.38",sphinxios
21100,Microphone is too silent in the VM with Windows 10 or 11,Windows,VirtualBox 6.1.38,2022-09-08T23:10:29Z,2022-09-08T23:10:29Z,2022-09-08T23:10:29Z,"I have an old problem with microphone: even with the maximum level on the host, it is nearly silent in the guest. If I test it on the host, I can see the level goes to 100%, but the same test in the guest gives only 10% volume.

I searched the tickets and forum. All I could find is the suggestion to use Line-in in pre-Windows 10 versions, but there is no Line-in in my Windows 10 or Windows 11 VM. My host is Windows 10 by the way.

So, my question is: are there any other possibilities to bring the microphone volume to the right level in the guest?",boxer01
21094,Guru Meditation Error,Linux,VirtualBox 6.1.38,2022-09-02T18:44:21Z,2022-09-02T18:44:21Z,2022-09-02T18:44:21Z,"I have downloaded the Quickstart Cloudera Vm 5.13.0-0- virtual box with Red Hat for VirtualBox 6.1.38 and when I ""start"" the iteration I get a Guru Meditation critical error. I do not have any chance of interaction. ",fhqwhgads
19358,VMs lose bridged network connection after host suspend/resume,all,VirtualBox 6.1.4,2020-02-28T15:20:54Z,2023-01-29T17:33:29Z,2023-01-29T17:33:29Z,"This doesn't happen every time, but often enough to become frustrating: when I suspend/resume the host, '''all''' of the guests (Windows ''and'' Linux) are unable to communicate over the bridged network.

What does '''not''' work:
 - suspending/resuming the guest
 - restarting the guest OS network services
 - restarting the guest OS
 - disabling/enabling the guest's network adapter
 - disabling/enabling the host's network adapter that is bridged
 - disabling/enabling the vbox bridging driver on the host's network adapter

One thing that did work:
 - connect alternate network adapter on host (eg.: wireless) and set as bridge for VM

Aside from that, the only thing that fully works is to reboot the host, but I have several passwords to enter and dozens of applications to run in order to get my environment setup, which makes frequent rebooting untenable.

This may also provide a clue: when I enabled the host's wireless adapter, the host was not able to receive an IP lease from the router's DHCP server, I had to key in a static IP for the host.

Is there a service or executable I can restart or run to kickstart the bridged networking?",VeHav2GoVeeper
19326,VirtualBox Manager 6.1.x causes BSOD when docking into HP Universal dock G2,other,VirtualBox 6.1.4,2020-02-20T16:25:26Z,2022-11-09T21:56:24Z,2022-11-09T21:56:24Z,"Host Operating system is newly imaged Windows 10.

To reproduce:

* download and install VirtualBox 6.1.4 with all defaults
* start the VirtualBox Manager
* plug the HP Univeral G2 into the laptop

This will crash the Windows 10 host with a Blue Screen Of Death: ""PNP DETECTED FATAL ERROR"".

The problem happens only when docking.
Operations while undocked are fine.
Operations while docked are fine.
Undocking works fine.

There isn't any VM involved (therefore no VM log). This is only from having the VirtualBox Manager started.

This is specific to versions 6.1.x. I have checked with 6.1.0, 6.1.2 and 6.1.4. I have tried installing VirtualBox both docked and undocked. I have also installed as an Administrator. The BSOD happened in all cases.

The problem does not happen with 6.0.x. I am currently using 6.0.16 without any problems.

This has been verified on two different HP Zbook 15u G5 (i7-8650u - 32GB RAM) and one HP EliteBook 840 G5. I tried both with the factory BIOS and the latest available BIOS (Jan 17 2020). It has also been verified on two different universal docks G2 - again, both with the factory firmware and with the latest available firmware.

I am attaching one of the VBoxSVC log file right agter undocking and docking. The last 3 lines of the log files were produced while undocking. No additional logging was produced when docking.
",come_raczy
19457,Guest Addition not working with Windows NT 4.0 Guest,Windows,VirtualBox 6.1.4,2020-04-02T12:54:37Z,2022-04-03T15:49:06Z,2022-04-03T15:49:06Z,"Steps to reproduce the issue:

Install VirtualBox 6.1.4

Install Extension_Pack-6.1.4.vbox-extpack

Create a VM and install Win NT 4.0 on the guest. I used a german OEM iso from here: https://archive.org/download/WinNTWKS40DEU/NTWKS40D.iso

Install Service Pack 6a on the guest.

Install Guest Additions on guest. The installation completes without any errors. After installing it requests a reboot.

Now, whenever I boot the VM and login a user, the system freezes for around a minute and then displays an error message.
Translated to english:
""The start of at least one service failed, which should be started at system boot. Check the Event Viewer.""

There are no information in the Event Viewer. But when I look at the services, the only service with automatic start, which is not running is ""VirtualBox Guest Additions Service"". When I manually try to start this service, the following error appears (free translation to english):
""The VirtualBox Guest Additions Service on HOSTNAME could not be started.
Error 2186: The service does not respond to the control function.""

Some functions of the guest additions are working fine, like higher resolutions and True Color mode. But Shared folders or mouse integration are not working at all. When I try the exact same procedure with VirtualBox 5.2.38, I do not get any errors.",Sbf93
19365,Graphic anomalies in Windows 10 2004,Windows,VirtualBox 6.1.4,2020-02-29T08:59:56Z,2021-12-01T14:43:32Z,2021-12-01T14:43:32Z,"I have installed Windows 10 2004 64-Bit as guest under Windows 10 64-Bit 1909 as host system. Graphic adapter is VBOXSVGA with 3D acceleration. Actual guest additions are running.
The Windows start menu and the task bar are completely tranparent and not grey transparent, so the text cannot be read. Furthermore the settings dialog seems to freeze, after minimizing and maximizing the windows changes are visible.
When I disable transparency effects in the settings under personalizing, colors, everything works fine.
I observed this problem first time in Windows 10 2004 as guest, in Windows 10 1909 the graphic output was OK.",awhb
19356,Copy and paste and drag and drop doesn't work,Linux,VirtualBox 6.1.4,2020-02-28T04:22:49Z,2020-08-11T11:36:22Z,2020-08-11T11:36:22Z,"this was the error for Windows to Linux(Kali Linux):
Drag and drop operation from host to guest failed.
Drag and drop error from host (VERR_NET_PATH_NOT_FOUND).
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: GuestWrap
Interface: IGuest {13a11514-402e-022e-6180-c3944de3f9c8}

This error is Linux to Windows:
Specified format 'text/plain;charset=utf-8' is not supported.
Result Code: 
E_INVALIDARG (0x80070057)
Component: 
GuestDnDSourceWrap
Interface: 
IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee: 
IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
",Coder2005
19451,Guest crash after some hours working,Windows,VirtualBox 6.1.4,2020-03-31T08:28:07Z,2020-05-26T08:19:05Z,2020-05-26T08:19:05Z,On 6.x versions of VBox crashes are stable :-(,Дмитро
19360,[Win7 64 Host] Clipboard not working after update,Windows,VirtualBox 6.1.4,2020-02-28T20:18:48Z,2020-05-13T16:22:06Z,2020-05-13T16:22:06Z,"After i updated VB 6.1.2 and same guest additions, the clipboard on Windows 2000 didnt worked anymore. After VB 6.1.4 came out, i tested it again and still didnt worked. With the GA 5.2.38 and VB 6.1.4, the clipboard worked but not the drag & drop, that did work with GA 6.1.4. On other Windows (tested XP,Win7 so far) it works with GA 6.1.4, so it seems only a Bug for Windows 2000. I hope you still support Windows 2000 Guest.",helgo1506
19576,AssertLogRel F:\tinderbox\win-rel\src\VBox\Runtime\win\RTErrConvertFromWin32.cpp(448) int __cdecl RTErrConvertFromWin32(unsigned int): <NULL>  Unhandled error 1453,Linux,VirtualBox 6.1.4,2020-05-11T00:36:11Z,2020-05-11T00:36:11Z,2020-05-11T00:36:11Z,"VirtualBox 6.1.4 under host windows10, running linux guest crashed due to an assertion failure.
Unhandled error 1453.

VirtualBox was running while I was tinkering with the programs on the Windows 10 site when suddenly the PC froze [I think Windows 10 was executing binary dump of the virtualbox image for debugging.] then about a minute or so later, I got an error dialog about memory reference error or something, but I failed to capture the screen, but rely on the log file(s) instead.",ci-zephyurus
19438,Resize Screen crashes Everything,Linux,VirtualBox 6.1.4,2020-03-27T13:53:02Z,2020-04-25T14:41:27Z,2020-04-25T14:41:27Z,"I am using Windows 10, VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.6.2)
 with an Ubuntu 18.04 LTS guest. Once the guest is installed and rebooted, resizing the screen in windows can lock the VM, and eventually the whole PC. 

Steps to reproduce resize the screen and before the guest is refreshed add a little more screen. Different kinds of hangs but the VM guest is always hung. Sometimes VBox host hangs also.",jerry ely
19385,Start Menu on Windows 10 LTSC becomes broken after some time,Windows,VirtualBox 6.1.4,2020-03-07T19:27:57Z,2020-04-20T07:49:47Z,2020-04-20T07:49:47Z,"I am using Microsoft Windows 10 1809 LTSC MSDN version, and after some time, the start menu becomes broken, as in the screenshot, it blinks and does not show the headers",astverskoy
19491,have errors showing up trying to get into macOS Catalina,OSX Server,VirtualBox 6.1.4,2020-04-14T22:44:21Z,2020-04-16T09:49:23Z,2020-04-16T09:49:23Z,This is the first time I am trying to get into Catalina from my windows 10-64 bit environment.  I have tried several times but I am getting error codes.as shown.  ,esams2
19461,App Error - Instruction at ... referenced memory at...,Linux,VirtualBox 6.1.4,2020-04-05T14:55:14Z,2020-04-15T20:03:18Z,2020-04-15T20:03:18Z,"I am using Linux guest on Windows 10 host. Inside of my guest when I use some Chrome based apps: Chrome, Vivaldi, Electron apps like VSCode, after few minutes of using them I get such an error:  Instruction at ... referenced memory at.... The memory could not be written. VBox then crashes. I'm attaching screenshot and VBox log file.
",Macio
19484,Reacting to host shutdown,Windows,VirtualBox 6.1.4,2020-04-13T16:36:26Z,2020-04-13T16:39:11Z,2020-04-13T16:39:11Z,"1. run Windows 10x64 virtual machine in Windows 10x64 host
2. in host Windows session, start Notepad and type something
3. in host Windows session, initiate shutdown
4. observe the message ""these applications prevent shutdown"" - showing Notepad
5. press ""cancel"" thus terminating the shutdown of the host
6. observe what happens to the virtual machine:

- error message ""failed to pause the execution of the virtual machine""
Callee RC: 
RPC_S_SERVER_UNAVAILABLE 0x800706BA (0x800706BA)
- the console of the virtual machine remains connected and showing the desktop, but it's not working anymore

open VirtualBox Manager, and check the status of the virtual machine - it's ""aborted""

What was expected: if virtual machine was reacting to the host shutdown, it probably should have either shut down itself, or gracefully terminated; there should be no attempt to pause (which failed); the GUI probably should disappear -  rather than stayed on the screen while being non-operational.


",vad
19483,[CRITICAL] Windows XP VM Won’t Start,Windows,VirtualBox 6.1.4,2020-04-13T04:49:42Z,2020-04-13T04:49:42Z,2020-04-13T04:49:42Z,"I was not able to attach a log file for this; the log is empty. Let me describe the issue.
When I make a new VM with Windows XP on it, with sufficient RAM, CPU, Disk, and the correct ISO, it says invalid settings detected. I hover over it and it leads me to System/Acceleration and it tells me to uncheck Hardware Virtualisation. Fair enough, I toggle it off. The invalid settings error persists at the same place. Here are my specs:

Windows 7 Home Premium SP 1 Build 7601
Lenovo Ideapad 2010 (x64 based)
Intel Core i5 CPU, M480 @ 2.67 GHz, 2667 MHz, 2 Cores
BIOS Version LENOVO 29CN35WW(V2.12), 8/12/2010
SMBIOS Version 2.6
8 GB RAM

I am also on the latest stable version, 6.1.4r136177 (Qt5.6.2)


",Asquenn
19479,Unable to create Host-Only Network on Virtual Box,other,VirtualBox 6.1.4,2020-04-12T01:03:51Z,2020-04-12T01:03:51Z,2020-04-12T01:03:51Z,"Hi,

I know there are emany posts on this topic and i have gone through almost all of them but my issue still persists.

I am unable to create a host-only network on my Virtual Box. Many of the posts suggested to reinstall the Virtual Box and I did perform the following steps:
.
1) Uninstalled Virtual Box 6.1.4
2) Uninstalled norton AV on my machine (Windows 10 - 16GB RAM)
3) Disabled Windows Defender (Both AV & Forewall)
4) Rebooted the machine many a times.
5) Reinsalled Virtual Box (Run as administrator)

The problem still persists

'''Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
'''


I also tried to download to a lower version (5.2.34) but to no avail.


",Sheezan
19478,NAT limitations,Windows,VirtualBox 6.1.4,2020-04-11T19:07:24Z,2020-04-11T19:11:12Z,2020-04-11T19:11:12Z,"Current version NAT limitations are well documented in https://www.virtualbox.org/manual/UserManual.html#nat-limitations

Some of them, such as ICMP, have been there over ten years, as this bugtrack documents: https://www.virtualbox.org/ticket/181

So, back in march 2007, ""Frank"" decided that is was ""wontfix"".

I am trying to use VoIP solutions (SIP), asterisk, etc but I would prefer to use a VM box and use NAT for this. I am experiencing dificulties that I believe are due to those sw using inside ICMP, so, no ICMP no working...

TIA",caspertone2003
19464,Windows 10 64bit Not Available In The Guest Templates,Windows,VirtualBox 6.1.4,2020-04-07T01:20:06Z,2020-04-08T11:06:27Z,2020-04-08T11:06:27Z,"I am facing an issue with version 6.1.4 r136177 (Qt5.6.2). I installed it, enabled the virtualization in BIOS then Windows 64bit guest became available in the OS list. I installed it, but after restart my host Machine the option to create a new Windows 64bit guest is not available anymore. I tried to uninstall, removed registers, path, etc but nothing is working. I tried all the suggestions of the VirutalBox forum but nothing is working. 

Please find below my current configuration:

Host Information:

-> Lenovo T440
-> Windows 10 Enterprise Version 1703 OS Build 15063.2108
-> Virtual Box Version 6.1.4 r136177 (Qt5.6.2)
-> Windows Hyper-V is disabled
-> Virtualization BIOS is enabled (VT-X)
-> CPU virtualization is enabled
-> Containers is disabled
-> Windows Subsystem for Linux is disabled",Naua
19363,Bidirectional support not working after 6.1.4 update in Linux Mint 19.1 or Ubuntu 14.04,Linux,VirtualBox 6.1.4,2020-02-29T03:21:44Z,2020-04-06T18:17:13Z,2020-04-06T18:17:13Z,"I did an update yesterday to VB 6.1.4, installed the latest extension pack 6.1.4r136177, and updated the vbox guest additions to 6.1.4. I lost the ability to automatically mount my shared folder, I solved this by editing the following

sudo systemctl edit --full vboxadd-service

removed ""systemd-timesync.service"" from ""Conflicts="" line in [Unit] section. 
change from -->
Conflicts=shutdown.target systemd-timesync.service

To -->
Conflicts=shutdown.target

Then rebooted
Solved the automount issue, but did not solve the bidirectional copy and paste not working. What can I try next?

Having same problem with bidirectional copy and paste in my Ubuntu guest as well.  Id say, since I have the same issue in both this may be a bug.  ",DStair
19420,mount -t vboxsf Operation not supported by device,BSD,VirtualBox 6.1.4,2020-03-21T21:27:52Z,2020-04-06T17:10:27Z,2020-04-06T17:10:27Z,"When use `mount -t vboxsf ...`as suggested by VB-host SharedFolders hint, it fails, but writes nothing in dmesg. And there is mistake in the hint - it should be vboxVFS not vboxSF. Because vboxSF triggers nothing and vboxVFS triggers kldload of /boot/modules/vboxvfs.ko . [[BR]][[BR]]

When use `mount -t vboxvfs ...` and `mount_vboxvfs ...` it shows:[[BR]]

link_elf_obj: symbol bcmp undefined[[BR]]
linker_load_file: /boot/modules/vboxvfs.ko - unsupported file type  [[BR]][[BR]]

FreeBSD 13-Current[[BR]]
Additions: 5.2.34_2 (installed via pkg, not compiled) [[BR]][[BR]]
",MikhailRokhin
19456,VINF_EM_TRIPLE_FAULT when starting Ubuntu 16.04 on Win10 2004,Linux,VirtualBox 6.1.4,2020-04-02T12:00:21Z,2020-04-02T12:50:53Z,2020-04-02T12:50:53Z,"Win 10 2004 host, with Hyper-V enabled
VBox 6.1.4
Fresh Ubuntu Server 160406 64-bit install
Ubuntu boots and then ""hangs"" during the boot process
Intermittently, not always, it will throw a VINF_EM_TRIPLE_FAULT when this happens
Played around with various system / processor settings, no change. Reverted to defaults.",yorickdowne
19443,Bridge Adapter Name List displays not existed NIC on Windows,all,VirtualBox 6.1.4,2020-03-29T10:03:56Z,2020-03-29T10:11:04Z,2020-03-29T10:11:04Z,Some removed NICs are still displayed in the Name List if VMs set to Bridged Adapter mode.,ohnoithappens
19422,VirtualBox Host-Only Ethernet Adapter DHCP settings proper apply need restart of VB,BSD,VirtualBox 6.1.4,2020-03-22T20:28:05Z,2020-03-28T13:29:46Z,2020-03-28T13:29:46Z,"Changing DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H) need restart of the whole VB to be applied properly. If not, settings VB was started with are applied (whatsoever user changes them), after just guest is restarted.


It should work in other way: user stops guest, changes DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H), starts guest and changes are properly applied.


Now it needs to stop all guests, main window of VB should be closed, VB should be started again.",MikhailRokhin
19439,Resize Screen crashes Everything,Linux,VirtualBox 6.1.4,2020-03-27T13:53:09Z,2020-03-27T13:53:09Z,2020-03-27T13:53:09Z,"I am using Windows 10, VirtualBox Graphical User Interface
Version 6.1.4 r136177 (Qt5.6.2)
 with an Ubuntu 18.04 LTS guest. Once the guest is installed and rebooted, resizing the screen in windows can lock the VM, and eventually the whole PC. 

Steps to reproduce resize the screen and before the guest is refreshed add a little more screen. Different kinds of hangs but the VM guest is always hung. Sometimes VBox host hangs also.",jerry ely
19437,A critical error has occurred while running the virtual machine and the machine execution has been stopped.,Linux,VirtualBox 6.1.4,2020-03-27T13:11:03Z,2020-03-27T13:11:03Z,2020-03-27T13:11:03Z,"I am using windows10 64bit on UEFI pc desktop this error occured to me trying to use kali linux on virtual box i will attach my vbox.log and vbox.png 
i enabled virtualization , and installed the ext pack same version as the program and still can't make up what's is even the problem! , 
i can't figure any thing from the vbox.log so , any suggestions? ",DEV
19436,"Unstable Guest- win 10, 7 , Fedora 29, Ubuntu 19.04",all,VirtualBox 6.1.4,2020-03-27T12:18:04Z,2020-03-27T12:18:04Z,2020-03-27T12:18:04Z,"I have found win 10, 7 , Fedora 29, Ubuntu 19.04 having issues with 6.1.4 (unresponsive, apps crashing, guest reboot),(tested on different hardware)
it is looks like a bug, log attched",war357
19426,USB-to-Ethernet crash with Ubuntu guest and Windows 10 host,Linux,VirtualBox 6.1.4,2020-03-23T22:58:21Z,2020-03-24T01:41:52Z,2020-03-24T01:41:52Z,"Hi,

I'm passing a USB 3.0 USB-to-Ethernet adapter to a Ubuntu 18.04 VM running on a Windows 10 host. After a few seconds of high bandwidth data transfer, the xhci driver in the guest crashes with the following output in dmesg:

{{{
[ 2556.648728] xhci_hcd 0000:00:0c.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 2556.648734] xhci_hcd 0000:00:0c.0: Looking for event-dma 00000000381ff450 trb-start 00000000381ff300 trb-end 00000000381ff300 seg-start 00000000381ff000 seg-end 00000000381ffff0
}}}

The bug happens whether or not I have the guest additions installed. I've tested that this bug does NOT occur when using the same adapter on either a native Windows 10 or Ubuntu machine. I also tried updating the kernel and drivers in the guest VM to the latest version but the bug still occurs. The bug also seems to happen with a variety of USB 3.0 USB-to-Ethernet adapters.

Notably the bug seems to happen on several Dell laptops (Dell Precision 5520). I tested the same setup on an HP laptop with an Ubuntu host but the issue did not appear.",xynith
19419,"Guru Mediation - Cent Os 7, when i start a local ant build",Linux,VirtualBox 6.1.4,2020-03-21T10:23:48Z,2020-03-21T10:33:31Z,2020-03-21T10:33:31Z,Guru Meditation is coming very frequently. Please help me to resolve the issue,mariswamy
19417,incorrect power off handling with background vms,other,VirtualBox 6.1.4,2020-03-20T16:26:32Z,2020-03-20T16:26:32Z,2020-03-20T16:26:32Z,"if I have a background machine running and try to log out or poweroff without closing it, I have standard windows dialog about that the virtualbox don't let to shutdown.
vm powers off automaticly, but the VBoxSvc process stays running and don't let to shutdown.
when I kill it system shuts down normally.",ilyapashuk
19416,random file system corrruption on Windows 10,Linux,VirtualBox 6.1.4,2020-03-20T15:59:35Z,2020-03-20T16:15:32Z,2020-03-20T16:15:32Z,"My system info:



{{{
Host Name:                 PENTIUM
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          vagiz
Registered Organization:
Product ID:                00330-80000-00000-AA650
Original Install Date:     2/29/2020, 8:24:00 AM
System Boot Time:          3/19/2020, 1:14:52 AM
System Manufacturer:       Micro-Star International Co., Ltd.
System Model:              MS-7B98
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~3696 Mhz
BIOS Version:              American Megatrends Inc. 1.80, 12/25/2019
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume5
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     16,248 MB
Available Physical Memory: 5,630 MB
Virtual Memory: Max Size:  16,248 MB
Virtual Memory: Available: 1,731 MB
Virtual Memory: In Use:    14,517 MB
Page File Location(s):     N/A
Domain:                    WORKGROUP
Logon Server:              \\PENTIUM
Hotfix(s):                 8 Hotfix(s) Installed.
                           [01]: KB4534132
                           [02]: KB4497727
                           [03]: KB4500109
                           [04]: KB4503308
                           [05]: KB4537759
                           [06]: KB4538674
                           [07]: KB4541338
                           [08]: KB4551762
Network Card(s):           3 NIC(s) Installed.
                           [01]: Intel(R) Ethernet Connection (7) I219-V
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.30
                                 [02]: fe80::2525:f387:2d51:482c
                                 [03]: fdaa:bbcc:ddee:0:d549:d972:f087:7aea
                                 [04]: fdaa:bbcc:ddee:0:98a1:602:e24a:c661
                                 [05]: fdaa:bbcc:ddee:0:2525:f387:2d51:482c
                           [02]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::c0ff:26ea:bebe:8ea6
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.18.26.193
                                 [02]: fe80::1819:a7d9:5836:496b

}}}
Vagrant file:

{{{
Vagrant.configure(""2"") do |config|
  # The most common configuration options
  # https://docs.vagrantup.com.

  # boxes at https://vagrantcloud.com/search.
  # https://app.vagrantup.com/bento
  config.vm.box = ""bento/centos-7""

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  config.vm.network :forwarded_port, guest: 22, host: 12022
  config.vm.network :forwarded_port, guest: 12080, host: 12080
  config.vm.network :forwarded_port, guest: 12443, host: 12443
  #config.vm.synced_folder ""."", ""/vagrant"", :mount_options => [""dmode=777"",""fmode=666""]
  config.ssh.username = 'vagrant'
  config.ssh.password = 'vagrant'
  config.ssh.insert_key = false
  config.vm.provider ""virtualbox"" do |vb|
        vb.memory = ""1600""
        vb.cpus = ""2""
        end
end
}}}

Random file corruption, e.g. wget https://files.phpmyadmin.net/phpMyAdmin/4.9.4/phpMyAdmin-4.9.4-english.tar.gz

I have tried Hyper-V on/off multiple times with different disks: SSD, NVMe, SATA and disable/enable windows/Vagrant caching.
sometimes cannot even boot from the beginning (system displays emergency mode). tried to reinstall VirtualBox multiple times, use different install image version. nothing changed, random corruption especially with heavy write.

as an example, internal MariaDB output when importing:

{{{
Mar 20 14:22:37 localhost systemd: Starting MariaDB 10.4.12 database server...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] /usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 8606 ...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using Linux native AIO
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Uses event mutexes
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Number of pools: 1
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Completed initialization of buffer pool
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Waiting for purge to start
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 10.4.12 started; log sequence number 60496037333; transaction id 79440
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] Plugin 'FEEDBACK' is disabled.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] 'proxies_priv' entry '@% root@localhost.localdomain' ignored in --skip-name-resolve mode.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] InnoDB: Buffer pool(s) load completed at 200320 14:22:41
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Reading of all Master_info entries succeeded
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Added new Master_info '' to hash table
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=localhost-relay-bin' to avoid this problem.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] /usr/sbin/mysqld: ready for connections.
Mar 20 14:22:41 localhost mysqld: Version: '10.4.12-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 0  MariaDB Server
Mar 20 14:22:41 localhost systemd: Started MariaDB 10.4.12 database server.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=256128, page number=2147483648], should be [page id: space=1511, page number=3530]
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace hpci/articles page [page id: space=1511, page number=3530]. You may have to recover from a backup.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
Mar 20 14:46:44 localhost mysqld: len 16384; hex 00000000800000000000000000003c000000a2998f692000998f692efb00000137000003e8800102000258003780000000003420a6000000000000800000000000000000003c000000a3998f693000998f693efb00000137000003e8800102000260003780000000003420a7000000000000800000000000000000003c000000a4998f694000998f694efb00000137000003e8800102040268003780000000003420a8000000000000800000000000000000003c000000a5998f695000998f695efb00000137000003e8800102000270003780000000003420a9000000000000800000000000000000003c000000a6998f696000998f696efb00000137000003e8800102000278003780000000003420aa000000000000800000000000000000003c000000a7998f697000998f697efb00000137000003e8800102000280003780000000003420ab000000000000800000000000000000003c00000000998f6a0000998f6a0efb00000137000003e8800102040288003780000000003420ac000000000000800000000000000000003c00000001998f6a1000998f6a1efb00000137000003e8800102000290003780000000003420ad000000000000800000000000000000003c00000002998f6a2000998f6a2efb00000137000003e8800102000298003780000000003420ae000000000000800000000000000000003c00000003998f6a3000998f6a3efb00000137000003e88001020002a0003780000000003420af000000000000800000000000000000003c00000004998f6a4000998f6a4efb00000137000003e88001020402a8003780000000003420b0000000000000800000000000000000003c00000005998f6a5000998f6a5efb00000137000003e88001020002b0003780000000003420b1000000000000800000000000000000003c00000006998f6a6000998f6a6efb00000137000003e88001020002b8003780000000003420b2000000000000800000000000000000003c00000007998f6a7000998f6a7efb00000137000003e88001020002c0003780000000003420b3000000000000800000000000000000003c00000008998f6a8000998f6a8efb00000137000003e88001020402c8003780000000003420b4000000000000800000000000000000003c00000009998f6a9000998f6a9efb00000137000003e88001020002d0003780000000003420b5000000000000800000000000000000003c0000000a998f6aa000998f6aaefb00000137000003e88001020002d8003780000000003420b6000000000000800000000000000000003c0000000b998f6ab000998f6abefb00000137000003e88001020002e0003780000000003420b7000000000000800000000000000000003c0000000c998f6ac000998f6acefb00000137000003e88001020402e8003780000000003420b8000000000000800000000000000000003c0000000d998f6ad000998f6adefb00000137000003e88001020002f0003780000000003420b9000000000000800000000000000000003c0000000e998f6ae000998f6aeefb00000137000003e88001020002f8003780000000003420ba000000000000800000000000000000003c0000000f998f6af000998f6afefb00000137000003e8800102000300003780000000003420bb000000000000800000000000000000003c00000010998f6b0000998f6b0efb00000137000003e8800102040308003780000000003420bc000000000000800000000000000000003c00000011998f6b1000998f6b1efb00000137000003e8800102000310003780000000003420bd000000000000800000000000000000003c00000012998f6b2000998f6b2efb00000137000003e8800102000318003780000000003420be000000000000800000000000000000003c00000013998f6b3000998f6b3efb00000137000003e8800102000320003780000000003420bf000000000000800000000000000000003c00000014998f6b4000998f6b4efb00000137000003e8800102040328003780000000003420c0000000000000800000000000000000003c00000015998f6b5000998f6b5efb00000137000003e8800102000330003780000000003420c1000000000000800000000000000000003c00000016998f6b6000998f6b6efb00000137000003e8800102000338003780000000003420c2000000000000800000000000000000003c00000017998f6b7000998f6b7efb00000137000003e8800102000340003780000000003420c3000000000000800000000000000000003c00000018998f6c0000998f6c0efb00000137000003e8800102040348003780000000003420c4000000000000800000000000000000003c00000019998f6c1000998f6c1efb00000137000003e8800102000350003780000000003420c5000000000000800000000000000000003c0000001a998f6c2000998f6c2efb00000137000003e8800102000358003780000000003420c6000000000000800000000000000000003c0000001b998f6c3000998f6c3efb00000137000003e8800102000360003780000000003420c7000000000000800000000000000000003c0000001c998f6c4000998f6c4efb00000137000003e8800102040368003780000000003420c8000000000000800000000000000000003c0000001d998f6c5000998f6c5efb00000137000003e8800102000370003780000000003420c9000000000000800000000000000000003c0000001e998f6c6000998f6c6efb00000137000003e8800102000378003780000000003420ca000000000000800000000000000000003c0000001f998f6c7000998f6c7efb00000137000003e8800102000380003780000000003420cb000000000000800000000000000000003c00000020998f6c8000998f6c8efb00000137000003e8800102040388003780000000003420cc000000000000800000000000000000003c00000021998f6c9000998f6c9efb00000137000003e8800102000390003780000000003420cd000000000000800000000000000000003c00000022998f6ca000998f6caefb00000137000003e8800102000398003780000000003420ce000000000000800000000000000000003c00000081998f669000998f669efb00000138000003e88001020003a0003780000000003420cf000000000000800000000000000000003c00000082998f66a000998f66aefb00000138000003e88001020403a8003780000000003420d0000000000000800000000000000000003c00000083998f66b000998f66befb00000138000003e88001020003b0003780000000003420d1000000000000800000000000000000003c00000084998f66c000998f66cefb00000138000003e88001020003b8003780000000003420d2000000000000800000000000000000003c00000085998f66d000998f66defb00000138000003e88001020003c0003780000000003420d3000000000000800000000000000000003c00000086998f66e000998f66eefb00000138000003e88001020403c8003780000000003420d4000000000000800000000000000000003c00000087998f66f000998f66fefb00000138000003e88001020003d0003780000000003420d5000000000000800000000000000000003c00000088998f670000998f670efb00000138000003e88001020003d8003780000000003420d6000000000000800000000000000000003c00000089998f671000998f671efb00000138000003e88001020003e0003780000000003420d7000000000000800000000000000000003c0000008a998f672000998f672efb00000138000003e88001020403e8003780000000003420d8000000000000800000000000000000003c0000008b998f673000998f673efb00000138000003e88001020003f0003780000000003420d9000000000000800000000000000000003c0000008c998f674000998f674efb00000138000003e88001020003f8003780000000003420da000000000000800000000000000000003c0000008d998f675000998f675efb00000138000003e8800102000400003780000000003420db000000000000800000000000000000003c0000008e998f676000998f676efb00000138000003e8800102040408003780000000003420dc000000000000800000000000000000003c0000008f998f677000998f677efb00000138000003e8800102000410003780000000003420dd000000000000800000000000000000003c00000090998f680000998f680efb00000138000003e8800102000418003780000000003420de000000000000800000000000000000003c00000091998f681000998f681efb00000138000003e8800102000420003780000000003420df000000000000800000000000000000003c00000092998f682000998f682efb00000138000003e8800102040428003780000000003420e0000000000000800000000000000000003c00000093998f683000998f683efb00000138000003e8800102000430003780000000003420e1000000000000800000000000000000003c00000094998f684000998f684efb00000138000003e8800102000438003780000000003420e2000000000000800000000000000000003c00000095998f685000998f685efb00000138000003e8800102000440003780000000003420e3000000000000800000000000000000003c00000096998f686000998f686efb00000138000003e8800102040448003780000000003420e4000000000000800000000000000000003c00000097998f687000998f687efb00000138000003e8800102000450003780000000003420e5000000000000800000000000000000003c00000098998f688000998f688efb00000138000003e8800102000458003780000000003420e6000000000000800000000000000000003c00000099998f689000998f689efb00000138000003e8800102000460003780000000003420e7000000000000800000000000000000003c0000009a998f68a000998f68aefb00000138000003e8800102040468003780000000003420e8000000000000800000000000000000003c0000009b998f68b000998f68befb00000138000003e8800102000470003780000000003420e9000000000000800000000000000000003c0000009c998f68c000998f68cefb00000138000003e8800102000478003780000000003420ea000000000000800000000000000000003c0000009d998f68d000998f68defb00000138000003e8800102000480003780000000003420eb000000000000800000000000000000003c0000009e998f68e000998f68eefb00000138000003e8800102040488003780000000003420ec000000000000800000000000000000003c0000009f998f68f000998f68fefb00000138000003e8800102000490003780000000003420ed000000000000800000000000000000003c000000a0998f690000998f690efb00000138000003e8800102000498003780000000003420ee000000000000800000000000000000003c000000a1998f691000998f691efb00000138000003e88001020004a0003780000000003420ef000000000000800000000000000000003c000000a2998f692000998f6974732061637469766573206120677265656e206c6561662067726164652061732077656c6c20617320696e6469636174696e67207768696368206172652045636f6365727420617070726f7665642c20776869636820617265207072657365727661746976652d6672656520616e64207768696368207061726162656e2d667265652e203c2f703e3c703e43726f64612068617320616c736f20676f6e6520646f776e2074686520677265656e20726f7574652c206c61756e6368696e6720557020436c6f736520616e6420477265656e2c2061206e657720677265656e20677569646520746f20697473207370656369616c69747920726177206d6174657269616c732e2054686520677569646520656e61626c657320666f726d756c61746f727320746f2064657465726d696e6520686f7720677265656e20612070726f647563742069732c2077697468207265666572656e636520746f206f726967696e2028706c616e742c20616e696d616c206f72206d696e6572616c292c20706574726f6368656d6963616c732c2073696c69636f6e65732c207072657365727661746976657320616e642062696f6465677261646162696c69747920616d6f6e677374206f74686572732e2054686520677569646520616c736f206665617475726573206120477265656e2043726974657269612074686174206d61726b7320612064656c69626572617465206d6f766520617761792066726f6d207468652063757272656e742063657274696669636174696f6e207374616e646172647320617661696c61626c652e20556e6465722074686520637269746572696120616c6c2070726f647563747320696e20746865206775696465206172652066726565206f6620657468796c656e65206f7869646520616e642070726f70796c656e65206f786964652d626173656420636f6d706f6e656e74732c20636f6e7461696e206e6f20706574726f6c65756d2064697374696c6c617465732c206e6f2070687468616c617465732c206e6f207061726162656e732c206e6f20666f726d616c6465687964652d72656c656173696e67207072657365727661746976657320616e642068617665206e6f74206265656e20746573746564206f6e20616e696d616c732e3c2f703e3c703ee2809c54686572652061726520736f206d616e792064697363726570616e63696573206265747765656e20656163682063657274696669657220746861742077652068617665206c65667420746865206f7074696f6e206f66207768696368207374616e6461726420746f20666f6c6c6f7720746f206f757220637573746f6d6572732ce2809d206578706c61696e6564205361726168204d696c6c6e732c206d61726b6574696e6720636f6d6d756e69636174696f6e7320636f6f7264696e61746f722c20706572736f6e616c2026206865616c746820636172652c2043726f64612e20e2809c57652061726520616c736f2077616974696e6720666f7220746865204575726f7065616e2063657274696669636174696f6e207374616e6461726420746f206c61756e63682c207768696368206d6179206368616e676520736f6d652063726974657269612ee2809d3c2f703e3c703e466f6c6c6f77696e6720746869732073656e74696d656e742c2074686520636f6d70616e792068617320646576656c6f7065642074776f206e65772073756e20636172652070726f64756374732c20536f6c617665696c2043542d33303020616e6420536f6c617669656c20435a2d3330302c20616e642074776f20687964726174696e672070657074696465732066726f6d206f7267616e696320736f75726365732e20487964726f6176656e612048704f20616e6420487964726f657863656c73612048704f20617265206d6f69737475726973696e67206167656e747320646572697665642062792067656e746c6520656e7a796d6174696320687964726f6c79736973206f6620636572746966696564206f7267616e69632063726f70732e3c2f703e3c703e53796d72697365206861732062726f6164656e656420697473206f7267616e696320706f7274666f6c696f2c20616464696e67206e65772070726f647563747320746f20697473204578747261706f6e65204f7267616e69632072616e67652c207768696368206973206261736564206f6e20636f6e74726f6c6c65642068617276657374696e672e204e65772070726f647563747320696e636c756465204e656f2041637469706f6e6520536f6170204e75747368656c6c2c20612031303025206e61747572616c2073757266616374616e74207375697461626c6520666f722075736520696e20706572736f6e616c2063617265206170706c69636174696f6e732073756368206173207368616d706f6f7320616e6420626f6479207761736865732e3c2f703e3c703ee2809c426f74616e6963616c73206172652070726f76656e20696e2073637265656e696e67206d6574686f647320746f20686176652072656c6576616e742065666665637473207375636820617320616e74692d6972726974616e7420616e6420616e74696f786964616e7420666f7220636f736d65746963206170706c69636174696f6e732ce2809d204d69636861656c205363687572696368742c20726567696f6e616c20627573696e657373206d616e616765722c2053796d726973652c20746f6c64205350432e3c2f703e3c703e54686520636f6d70616e792068617320616c736f2072656e616d65642069747320636f736d657469637320627573696e65737320756e69742c2077686963682077696c6c206e6f77206265206b6e6f776e206173204c69666520457373656e7469616c732c20627574206973207374696c6c20612070617274206f662053796d72697365e2809973205363656e7420262043617265206469766973696f6e2e3c2f703e3c703e53696c61622068617320616c736f20656e746572656420746865206f7267616e6963206172656e612c206c61756e6368696e672061206e65772045636f6365727420636572746966696564206f7267616e69632072616e67652c2077686963682077696c6c20696e697469616c6c7920636f6d7072697365207468726565206163746976652070726f6475637473202d204f73696c6966742042696f2c205374727563747572696e652042696f20616e6420566974616e6f6c2042696f2e20203c2f703e3c703e416e64204c69706f20686173206c61756e636865642061206e6577206c696e65206f66206e61747572616c20656d6f6c6c69656e74732c20646572697665642066726f6d2031303025206e61747572616c20706c616e7420736f75726365732e20546865204c69706f6275747465722072616e676520636f6d707269736573203131207661726965746965732c206569676874206f66207768696368206172652076616c6964617465642062792045636f636572742c207768696c652074686520726566696e6564206f7267616e696320736865612076617269616e7420697320636572746966696564206f7267616e69632062792045636f636572742e2056617269657469657320696e636c7564652061707269636f742c20726566696e656420636f636f612c206f6c6976652c206a6f6a6f62612c20726566696e6564206d616e676f20616e6420706561636820616e64206170706c69636174696f6e2073756767657374696f6e7320696e636c75646520736b696e2c2073756e20616e64206861697220636172652070726f64756374732c2066696e6520736f61707320616e6420626f647920627574746572732e3c2f703e3c2f703e3c703e5a656e6974656368e2809973206e6577204d6561646f77666f616d20616e64204f72616e6765206275747465727320616c736f20676976652061206e6f6420746f206e61747572616c2c20776974682045636f636572742076616c69646174696f6e2e205468652070726f647563747320617265207361696420746f206265207375697461626c6520666f7220612076617269657479206f66206170706c69636174696f6e7320696e636c7564696e6720736b696e20636172652c206861697220636172652c20636f6c6f757220636f736d657469637320616e64206e61696c20636172652e203c2f703e3c703ee2809c54686572652069732061206c6f74206f66206e6f6e73656e736520676f696e67206f6e2077697468206e61747572616c20616e64206f7267616e69637320617420746865206d6f6d656e742ce2809d207361696420436172746572204c61205661792c20707265736964656e742c205a656e69746563682e20e2809c54686520696e647573747279206e6565647320746f206368616e6765202d206974e28099732074696d6520776520776f6b6520757020616e64207265616c697365642074686520776f726c64206973206368616e67696e672e204920616d2070757474696e672045636f63657274206f6e2065766572797468696e6720492063616e206265636175736520492062656c6965766520696e20697420736f207374726f6e676c79202d206974e2809973207468652077617920666f72776172642ee2809d3c2f703e3c703e546865206f6e63652066616d696c696172206e616d65206f662046696e6574657820686173206e6f77206265656e2066756c6c79206162736f7262656420696e746f20496e6e6f737065632e205468652066616d696c6961722046696e736f6c7620656d6f6c6c69656e747320617265207374696c6c20617661696c61626c652c20616c74686f7567682070726f64756374696f6e2077617320726563656e746c7920657870616e6465642066726f6d2074686520555320746f204575726f70652028456c6c65736d65726520506f72742c20554b292c2062757420617420746869732079656172e280997320696e2d636f736d65746963732074686520636f6d70616e79207761732070726f6d6f74696e67204e6174726c71756573742045333020696e20706172746963756c61722c20612072656164696c792062696f64656772616461626c65206368656c6174696e67206167656e74207468617420726573706f6e647320746f2063757272656e7420726571756972656d656e74732e20e2809c50656f706c6520617265207265616c6c79207374617274696e6720746f2070617920617474656e74696f6e20746f20677265656e20616e6420677265656e20696e6772656469656e74732ce2809d2073616964205068696c204d6174656e612c20496e6e6f7370656320767020616e642067656e6572616c206d616e616765722e20e2809c5765e280997265207265696e76656e74696e67206f757273656c7665732061732061207370656369616c697479206368656d6963616c7320636f6d70616e7920616e64207765e28099766520676f742061206772656174206e65772070726f64756374206c696e652e204f75722073747261746567792069732067726f777468202d206f7267616e696320616e64207468726f756768206163717569736974696f6e2c2077686572652069742066697473206f75722073747261746567792ee2809d3c2f703e3c703e50726573657276617469766573207765726520616e6f7468657220617265612077686572652074686520677265656e207468656d652070726f647563656420736f6d6520696e746572657374696e67206e65772070726f64756374732e204472205374726165746d616e7320696e74726f64756365642061206e65772045636f636572742d6c697374656420616e74696d6963726f6269616c20696e6772656469656e74207468617420697320636c61696d656420746f2070726f766964652061206e61747572616c20616c7465726e617469766520746f2074686520636f6e76656e74696f6e616c207072657365727661746976657320746861742068617665206265656e20676976656e206120686172642074696d6520627920736f6d65207061727473206f6620746865206d6564696120726563656e746c792e3c2f703e3c703e4465726d61736f6674203638382045636f206973206120706c616e742d62617365642066756e6769636964616c20696e6772656469656e742c20646572697665642066726f6d20626173696c20616e64206973207361696420746f20706f7373657373207375706572696f7220616e74696d6963726f6269616c20636861726163746572697374696373207468616e206f7468657220706c616e74206465726976656420616c7465726e6174697665732063757272656e746c7920617661696c61626c652ee2809c54686572652068617320646566696e6974656c79206265656e206d6f72652064656d616e6420666f7220677265656e2070726f64756374732074686973207965617220616e64206f7572206e65772070726f6475637420686173206265656e206d65742077697468207665727920676f6f6420726573706f6e73652ce2809d20736169642044722e205374726165746d616e73e2809920537573616e6e65204ac3a46e696368656e2e20e2809c576520686176652045636f63657274206c697374696e6720616e6420617265206177616974696e6720536f696c204173736f63696174696f6e2063657274696669636174696f6e2ee2809d203c2f703e3c703e5769746820657665722067726561746572207365676d656e746174696f6e20696e2074686520736b696e206361726520736563746f722c2074686520636f6d7065746974696f6e20746f20646576656c6f7020696e6772656469656e74732074686174206f6666657220616476616e63656420736b696e20636172652062656e656669747320697320617420616e20616c6c2074696d6520686967682e204265696e67206120e28098677265656ee28099206272616e64206973206f6e65207468696e67206275742074686520696e6772656469656e7473206861766520746f2064656c6976657220736f706869737469636174656420726573756c74732e3c2f703e3c703e4761747465666f7373c3a920756e7665696c656420697473206c6174657374206c61756e63682c204379746f62696f6c204c756d696e2d4579652c20616e2061637469766520696e6772656469656e742077697468207374726f6e672076617363756c6f2d70726f746563746976652070726f70657274696573207468617420697320636c61696d656420746f20726564756365206461726b20636972636c657320616e6420707566667920736b696e2061726f756e64207468652065796520617265612e205468652061637469766520636f6e7461696e7320617368206261726b20657874726163742c206f7267616e69632073696c69636f6e20616e6420766974616d696e2042332c20776869636820616374206f6e2074686520736b696ee280997320637574616e656f7573206d6963726f63697263756c6174696f6e2e2056697369626c6520726573756c74732061726520636c61696d6564206166746572203238206461797320616e6420737567676573746564206170706c69636174696f6e7320696e636c7564652065796520636f6e746f75722074726561746d656e74732c207072652d20616e6420706f73742d737572676572792074726561746d656e74732c20616e74692d616765696e67206361726520616e6420666c6173682072616469616e63652074726561746d656e74732e3c2f703e3c703e4d6962656c6c65206d65616e7768696c65206c61756e636865642074776f206e657720616e74692d616765696e6720736b696e206361726520696e6772656469656e7473206261736564206f6e20706c616e7420736369656e63652e20506879746f43656c6c546563204d616c757320446f6d65737469636120697320616e20616374697665206261736564206f6e206170706c65207374656d2063656c6c732074686174207573657320706174656e742070656e64696e6720706c616e742063656c6c2063756c7475726520746563686e6f6c6f677920616e64206973207361696420746f2070726f7465637420736b696e207374656d2063656c6c7320616761696e737420616765696e672061732077656c6c2061732064656c6179696e67207468652073656e657363656e6365206f66206861697220666f6c6c69636c65732c2068656c70696e6720746f2070726573657276652074686520766974616c69747920616e6420796f75746866756c6e657373206f662074686520736b696e2e3c2f703e3c703e416c736f206d616b696e67206974732064656275742066726f6d204d6962656c6c6520776173204173747261466f7263652c20616e20616e74692d616765696e672070726f6475637420646576656c6f70656420666f7220626c656d697368656420736b696e2e2044656d616e6420666f7220616e74692d626c656d6973682070726f647563747320666f72206d6f7265206d61747572652c206e6f6e2d7465656e61676520736b696e2069732067726f77696e672072617069646c7920627574206163636f7264696e6720746f204d6962656c6c652c207468657265206172652076657279206665772070726f647563747320617661696c61626c6520746f207472656174207468697320636f6e646974696f6e2e2054686520696e6772656469656e7420636f6e7461696e7320417374726167616c7573206d656d6272616e61636575732c206120706c616e74207573656420696e20547261646974696f6e616c204368696e657365204d65646963696e652c20616e6420697320636c61696d656420746f206669726d20616e6420736d6f6f746820736b696e2c2072656475636520696d70657266656374696f6e732c2062616c616e636520736562756d2070726f64756374696f6e2c2070726576656e7420627265616b6f75747320616e64206c656176652074686520736b696ee280997320636f6d706c6578696f6e20636c65617220616e6420726566696e65642e3c2f703e3c703e446f7720416d657263686f6c2070726573656e7465642061206e65772c20706174656e742d70656e64696e6720656e63617073756c6174696f6e20616e642064656c69766572792073797374656d2c20536174696e46582c20776869636820656e61626c657320626f746820687964726f70686f62696320616e6420687964726f7068696c6963206163746976657320746f20626520656e63617073756c6174656420696e20612076617269657479206f6620736b696e20636172652070726f64756374732e204974206973207361696420746f2062652076657279206561737920746f206d69782062792073696d706c6520736865617220746f2063726561746520656e63617073756c6174696f6e20616e6420746f207369676e69666963616e746c7920696d70726f7665207468652073746162696c69736174696f6e206f662073656e73697469766520616374697665732061732077656c6c2061732067726561746572206566666963616379206f7665722074696d652e20566974616d696e73204120616e64204320616e64204448412077657265207374756469656420616e6420696d70726f7665642073746162696c697479207761732061636869657665642e20e2809c4974206365727461696e6c7920656e61626c6573207468652064656c6976657279206f66206e61747572616c206163746976657320736f2063616e206265207573656420696e20737570706f7274206f66206e61747572616c20636c61696d732ce2809d20636f6d6d656e746564204a656e6e696665722053696773776f7274682c20627573696e65737320636f6d6d756e69636174696f6e73207370656369616c697374207769746820446f7720416d657263686f6c2e20e2809c416e64207769746820746865206f6e676f696e672064656d616e6420666f72206d756c746966756e6374696f6e616c6974792c20706f74656e7469616c6c7920696e636f6d70617469626c6520696e6772656469656e7473206c696b652044484120616e6420616d696e6f20616369647320666f722073756e6c6573732074616e6e696e6720616e6420616e74692d616765696e672063616e20626520656e63617073756c6174656420746f6765746865722ee2809d20427920656e63617073756c6174696e6720706f74656e7469616c6c792069727269746174696e6720616374697665732c2074686520706f74656e7469616c20666f722069727269746174696f6e20697320726564756365642e20536174696e465820697320616c736f207361696420746f20696d70726f766520746865206165737468657469632070726f70657274696573206f66206661636520637265616d732c206579652067656c2c20736572756d20616e6420626f6479206c6f74696f6e20666f726d756c6174696f6e732e203c2f703e3c703e4c69676874657220616e642062726967687465723c2f703e3c703e5261686e20666f6375736564206f6e20736b696e206c69676874656e696e67206c61756e6368696e672043656c6c4163746976652057686974652c2061206e657720696e6772656469656e7420646576656c6f70656420666f722067656e746c6520736b696e206c69676874656e696e672c20616e6420636f6e7461696e696e67206120636f6d62696e6174696f6e206f6620766974616d696e2042332c2073756c706875726f75732065787472616374206f6620776174657263726573732c2062696f2d617661696c61626c65207a696e6320616e6420616e20457373656e7469616c2043656c6c20426f6f737420466163746f722e20496e20766974726f207465737473206f6e20334420736b696e206d6f64656c732073686f77656420757020746f2035302520726564756374696f6e20696e206d656c616e696e2070726f64756374696f6e20616e6420616e2031312520736b696e206c69676874656e696e67206f6620417369616e20736b696e2e20e2809c546865207461726765742077617320746f20646576656c6f7020616e2061637469766520666f722077686974656e696e67207468617420776173207361666520746f20736b696e2ce2809d206578706c61696e65642044616e69656c61204775696c646d616e6e2c2068656164206f66206d61726b6574696e672c205261686e2e3c2f703e3c703e4c69706f746563206c61756e63686564204368726f6d616272696768742c2061206e657720627269676874656e696e6720616374697665207468617420697320636c61696d656420746f20696e647563652061207369676e69666963616e74206c69676874656e696e67206566666963616379206f6e2074686520736b696e20616e642068656c707320746f20756e69667920736b696e20746f6e652e204368726f6d6f62726967687420646f6573206e6f742073686f7720616e79206379746f746f78696320656666656374732c206f7220616e792069727269746174696f6e206f722073656e73697469736174696f6e207265616374696f6e206163636f7264696e6720746f2074686520636f6d70616e792e3c2f703e3c703e456c656d656e74616c2070726f74656374696f6e3c2f703e3c703ee28098456c656d656e7473206f6620626561757479e280992077617320746865206e657720736c6f67616e20666f722043696261206174207468652073686f772e20e2809c49742064657363726962657320646966666572656e7420656c656d656e7473206f6620746563686e6f6c6f677920756e646572206f6e6520756d6272656c6c61202d207765e2809972652074616b696e672061206d6f726520686f6c697374696320617070726f61636820616e6420636f6d62696e696e6720636f6e6365707473206f66206265617574792c2077656c6c2d6265696e6720616e64206865616c74682ce2809d2073616964204d69636861656c2057696c6b6f702c20627573696e65737320686561642055562070726f74656374696f6e20262061637469766520627573696e657373206c696e6520686f6d65202620706572736f6e616c20636172652c20436962612e2054686520636f6d70616e79207761732070726f6d6f74696e6720e2809c62657474657220616765696e67e2809d2061732061206d6f726520706f73697469766520776179206f66206c6f6f6b696e6720617420616765696e672c206965206865616c746869657220616765696e67207468726f75676820616e20616e74692d616765696e6720617070726f61636820617320756e666f7274756e6174656c792061676520726576657273616c206973206e6f7420706f737369626c652e205468652069646561206973207468617420746869732063616e206265206163686965766564207468726f75676820757365206f662043696261e28099732054696e6f736f72622055562066696c746572732c2054696e6f6465726d206d6f6973747572697365727320616e642054696e6f6465726d20656e63617073756c6174656420616374697665733b2043696261207361696420697420657870656374732054696e6f736f7262205320616e642054696e6f736f7262204d20746f206761696e20616363657074616e636520696e207468652055532074686973207965617220736f20706c616e7320746f20626520726561647920666f7220746865206d6174657269616c7320746f20626520696e636c7564656420696e2066696e69736865642070726f6475637473206e65787420796561722e20e2809c57652077616e7420746f20657874656e64207468652073636f7065206f66206f75722061637469766974696573202d206974e2809973206e6f74206f6e6c7920612062656175747920746f7069632c206974e28099732061206865616c74682069737375652ee2809d20556c69204f7374657277616c6465722c20676c6f62616c206d61726b6574696e67206d616e616765722055562070726f74656374696f6e20616e642061637469766520656666656374732061646465643a20e2809c436962612077617320616e206561726c7920706c6179657220696e2055564120736f207765e2809972652061206d61726b6574206c65616465722e205765206e6f772077616e7420746f20776f726b207769746820637573746f6d65727320746f20636f6e76657920746865206d65737361676520746f2074686520756c74696d61746520636f6e73756d65722ee2809d2054686520636f6d70616e7920616c736f2077616e747320746f20776f726b2077697468206465726d61746f6c6f676973747320746f20696d70726f76652074686520756e6465727374616e64696e67206f662073756e2070726f74656374696f6e2074686572652e20e2809c5468657920646f6ee280997420616c6c20756e6465727374616e642053504620616e64206974e2809973207665727920696d706f7274616e742074686174207468657920646f2ce2809d2073616964204f7374657277616c6465722e20e2809c4974e280997320696d706f7274616e7420746f20776f726b206f6e2074686520696d616765206f662073756e73637265656e7320627574207765e28099726520636f756e74696e67206f6e20746865206661637420746861742070656f706c652077696c6c20616c776179732077616e7420746f206578706f7365207468656d73656c76657320746f2073756e2e20416e6420766974616d696e204420646566696369656e6379206973206e6f77206265696e67207365656e206173206265696e6720726573706f6e7369626c6520666f722061206c6f74206f662063616e636572732c207768696c6520766974616d696e2044207265717569726573205556422e204275742070726f74656374696f6e20636f6d65732066697273742ee2809d203c2f703e3c703e4e657874206d6f6e7468205350432077696c6c207265706f7274206f6e206d616e79206d6f7265206c61756e6368657320616e64206576656e74732066726f6d207468652073686f772c20696e636c7564696e6720746869732079656172e280997320696e737069726174696f6e616c20696e2d666f63757320666561747572652c2055746f7069612c20616e6420746865206576657220706f70756c6172207472656e64732070726573656e746174696f6e732e203c2f703e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000772915fce46b8b1f; asc               <      i    i.    7         X 7     4                  <      i0   i>    7         ` 7     4                  <      i@   iN    7         h 7     4                  <      iP   i^    7         p 7     4                  <      i`   in    7         x 7     4                  <      ip   i~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j.    7           7     4                  <      j0   j>    7           7     4                  <      j@   jN    7           7     4                  <      jP   j^    7           7     4                  <      j`   jn    7           7     4                  <      jp   j~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      k    k     7           7     4                  <      k    k     7           7     4                  <      k    k.    7           7     4                  <      k0   k>    7           7     4                  <      k@   kN    7         ( 7     4                  <      kP   k^    7         0 7     4                  <      k`   kn    7         8 7     4                  <      kp   k~    7         @ 7     4                  <      l    l     7         H 7     4                  <      l    l     7         P 7     4                  <      l    l.    7         X 7     4                  <      l0   l>    7         ` 7     4                  <      l@   lN    7         h 7     4                  <      lP   l^    7         p 7     4                  <      l`   ln    7         x 7     4                  <      lp   l~    7           7     4                  <      l    l     7           7     4                  <   !  l    l     7           7     4                  <   ""  l    l     7           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      g    g     8           7     4                  <      g    g     8           7     4                  <      g    g.    8           7     4                  <      g0   g>    8           7     4                  <      g@   gN    8           7     4                  <      gP   g^    8           7     4                  <      g`   gn    8           7     4                  <      gp   g~    8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h.    8         ( 7     4                  <      h0   h>    8         0 7     4                  <      h@   hN    8         8 7     4                  <      hP   h^    8         @ 7     4                  <      h`   hn    8         H 7     4                  <      hp   h~    8         P 7     4                  <      h    h     8         X 7     4                  <      h    h     8         ` 7     4                  <      h    h     8         h 7     4                  <      h    h     8         p 7     4                  <      h    h     8         x 7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      i    i     8           7     4                  <      i    i     8           7     4                  <      i    its actives a green leaf grade as well as indicating which are Ecocert approved, which are preservative-free and which paraben-free. </p><p>Croda has also gone down the green route, launching Up Close and Green, a new green guide to its speciality raw materials. The guide enables formulators to determine how green a product is, with reference to origin (plant, animal or mineral), petrochemicals, silicones, preservatives and biodegradability amongst others. The guide also features a Green Criteria that marks a deliberate move away from the current certification standards available. Under the criteria all products in the guide are free of ethylene oxide and propylene oxide-based components, contain no petroleum distillates, no phthalates, no parabens, no formaldehyde-releasing preservatives and have not been tested on animals.</p><p>   There are so many discrepancies between each certifier that we have left the option of which standard to follow to our customers,    explained Sarah Millns, marketing communications coordinator, personal & health care, Croda.    We are also waiting for the European certification standard to launch, which may change some criteria.   </p><p>Following this sentiment, the company has developed two new sun care products, Solaveil CT-300 and Solaviel CZ-300, and two hydrating peptides from organic sources. Hydroavena HpO and Hydroexcelsa HpO are moisturising agents derived by gentle enzymatic hydrolysis of certified organic crops.</p><p>Symrise has broadened its organic portfolio, adding new products to its Extrapone Organic range, which is based on controlled harvesting. New products include Neo Actipone Soap Nutshell, a 100% natural surfactant suitable for use in personal care applications such as shampoos and body washes.</p><p>   Botanicals are proven in screening methods to have relevant effects such as anti-irritant and antioxidant for cosmetic applications,    Michael Schuricht, regional business manager, Symrise, told SPC.</p><p>The company has also renamed its cosmetics business unit, which will now be known as Life Essentials, but is still a part of Symrise   s Scent & Care division.</p><p>Silab has also entered the organic arena, launching a new Ecocert certified organic range, which will initially comprise three active products - Osilift Bio, Structurine Bio and Vitanol Bio.  </p><p>And Lipo has launched a new line of natural emollients, derived from 100% natural plant sources. The Lipobutter range comprises 11 varieties, eight of which are validated by Ecocert, while the refined organic shea variant is certified organic by Ecocert. Varieties include apricot, refined cocoa, olive, jojoba, refined mango and peach and application suggestions include skin, sun and hair care products, fine soaps and body butters.</p></p><p>Zenitech   s new Meadowfoam and Orange butters also give a nod to natural, with Ecocert validation. The products are said to be suitable for a variety of applications including skin care, hair care, colour cosmetics and nail care. </p><p>   There is a lot of nonsense going on with natural and organics at the moment,    said Carter La Vay, president, Zenitech.    The industry needs to change - it   s time we woke up and realised the world is changing. I am putting Ecocert on everything I can because I believe in it so strongly - it   s the way forward.   </p><p>The once familiar name of Finetex has now been fully absorbed into Innospec. The familiar Finsolv emollients are still available, although production was recently expanded from the US to Europe (Ellesmere Port, UK), but at this year   s in-cosmetics the company was promoting Natrlquest E30 in particular, a readily biodegradable chelating agent that responds to current requirements.    People are really starting to pay attention to green and green ingredients,    said Phil Matena, Innospec vp and general manager.    We   re reinventing ourselves as a speciality chemicals company and we   ve got a great new product line. Our strategy is growth - organic and through acquisition, where it fits our strategy.   </p><p>Preservatives were another area where the green theme produced some interesting new products. Dr Straetmans introduced a new Ecocert-listed antimicrobial ingredient that is claimed to provide a natural alternative to the conventional preservatives that have been given a hard time by some parts of the media recently.</p><p>Dermasoft 688 Eco is a plant-based fungicidal ingredient, derived from basil and is said to possess superior antimicrobial characteristics than other plant derived alternatives currently available.   There has definitely been more demand for green products this year and our new product has been met with very good response,    said Dr. Straetmans    Susanne J  nichen.    We have Ecocert listing and are awaiting Soil Association certification.    </p><p>With ever greater segmentation in the skin care sector, the competition to develop ingredients that offer advanced skin care benefits is at an all time high. Being a    green    brand is one thing but the ingredients have to deliver sophisticated results.</p><p>Gattefoss   unveiled its latest launch, Cytobiol Lumin-Eye, an active ingredient with strong vasculo-protective properties that is claimed to reduce dark circles and puffy skin around the eye area. The active contains ash bark extract, organic silicon and vitamin B3, which act on the skin   s cutaneous microcirculation. Visible results are claimed after 28 days and suggested applications include eye contour treatments, pre- and post-surgery treatments, anti-ageing care and flash radiance treatments.</p><p>Mibelle meanwhile launched two new anti-ageing skin care ingredients based on plant science. PhytoCellTec Malus Domestica is an active based on apple stem cells that uses patent pending plant cell culture technology and is said to protect skin stem cells against ageing as well as delaying the senescence of hair follicles, helping to preserve the vitality and youthfulness of the skin.</p><p>Also making its debut from Mibelle was AstraForce, an anti-ageing product developed for blemished skin. Demand for anti-blemish products for more mature, non-teenage skin is growing rapidly but according to Mibelle, there are very few products available to treat this condition. The ingredient contains Astragalus membranaceus, a plant used in Traditional Chinese Medicine, and is claimed to firm and smooth skin, reduce imperfections, balance sebum production, prevent breakouts and leave the skin   s complexion clear and refined.</p><p>Dow Amerchol presented a new, patent-pending encapsulation and delivery system, SatinFX, which enables both hydrophobic and hydrophilic actives to be encapsulated in a variety of skin care products. It is said to be very easy to mix by simple shear to create encapsulation and to significantly improve the stabilisation of sensitive actives as well as greater efficacy over time. Vitamins A and C and DHA were studied and improved stability was achieved.    It certainly enables the delivery of natural actives so can be used in support of natural claims,    commented Jennifer Sigsworth, business communications specialist with Dow Amerchol.    And with the ongoing demand for multifunctionality, potentially incompatible ingredients like DHA and amino acids for sunless tanning and anti-ageing can be encapsulated together.    By encapsulating potentially irritating actives, the potential for irritation is reduced. SatinFX is also said to improve the aesthetic properties of face creams, eye gel, serum and body lotion formulations. </p><p>Lighter and brighter</p><p>Rahn focused on skin lightening launching CellActive White, a new ingredient developed for gentle skin lightening, and containing a combination of vitamin B3, sulphurous extract of watercress, bio-available zinc and an Essential Cell Boost Factor. In vitro tests on 3D skin models showed up to 50% reduction in melanin production and an 11% skin lightening of Asian skin.    The target was to develop an active for whitening that was safe to skin,    explained Daniela Guildmann, head of marketing, Rahn.</p><p>Lipotec launched Chromabright, a new brightening active that is claimed to induce a significant lightening efficacy on the skin and helps to unify skin tone. Chromobright does not show any cytotoxic effects, or any irritation or sensitisation reaction according to the company.</p><p>Elemental protection</p><p>   Elements of beauty    was the new slogan for Ciba at the show.    It describes different elements of technology under one umbrella - we   re taking a more holistic approach and combining concepts of beauty, well-being and health,    said Michael Wilkop, business head UV protection & active business line home & personal care, Ciba. The company was promoting    better ageing    as a more positive way of looking at ageing, ie healthier ageing through an anti-ageing approach as unfortunately age reversal is not possible. The idea is that this can be achieved through use of Ciba   s Tinosorb UV filters, Tinoderm moisturisers and Tinoderm encapsulated actives; Ciba said it expects Tinosorb S and Tinosorb M to gain acceptance in the US this year so plans to be ready for the materials to be included in finished products next year.    We want to extend the scope of our activities - it   s not only a beauty topic, it   s a health issue.    Uli Osterwalder, global marketing manager UV protection and active effects added:    Ciba was an early player in UVA so we   re a market leader. We now want to work with customers to convey the message to the ultimate consumer.    The company also wants to work with dermatologists to improve the understanding of sun protection there.    They don   t all understand SPF and it   s very important that they do,    said Osterwalder.    It   s important to work on the image of sunscreens but we   re counting on the fact that people will always want to expose themselves to sun. And vitamin D deficiency is now being seen as being responsible for a lot of cancers, while vitamin D requires UVB. But protection comes first.    </p><p>Next month SPC will report on many more launches and events from the show, including this year   s inspirational in-focus feature, Utopia, and the ever popular trends presentations. </p>
Mar 20 14:46:44 localhost mysqld: w)   k  ;
Mar 20 14:46:44 localhost mysqld: InnoDB: End of page dump
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 1274019770, innodb 28570114,  page type 39311 == PAGE TYPE CORRUPTED.none 3735928559, stored checksum in field2 1999181308, calculated checksums for field2: crc32 1274019770, innodb 3035797051, none 3735928559,  page LSN 41625 2406031360, low 4 bytes of LSN at page end 3832253215, page number (if stored to page already) 2147483648, space id (if created with >= MySQL-4.1.1 and stored already) 256128
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

}}}


I tried to use Windows 7 with the same version of VirtualBox - no problems at all.



",vagiz
19412,Verr_io_gen_failure in Windows XP Pro and Win 7 Pro,Windows,VirtualBox 6.1.4,2020-03-17T13:50:20Z,2020-03-17T13:50:20Z,2020-03-17T13:50:20Z,"Hello,

i get this Verr_io_gen_failure when i connect a Telenot comXline 3516-1 to the usb port. This happened in Windows XP Pro and Windows 7 Pro.
I see no possiibility to connect the Telenot to the guest systems.

I tried all i can, the usb filter is set right. I tried different settings in the filter.

The usb filter generally works perfect, exept the Telenot conection :(",alsk1
19410,"Remove, and delete files of the VMs will close the Virtualbox",Windows,VirtualBox 6.1.4,2020-03-17T07:28:35Z,2020-03-17T10:57:18Z,2020-03-17T10:57:18Z,"I just upgraded the application to 6.1.4.r136177(Qt5.6.2), the first thing I did to remove old VMs which was migrated from the old version.

I have around 7 VMs and deleted them one by one and to be specific , the problem occurred only when I removed and deleted files of Linux OS.

attached is the Event viewer event.",Mahmood.Shehab
19352,Guru Meditation when using more than 1 CPU + EFI (VINF_EM_TRIPLE_FAULT),Windows,VirtualBox 6.1.4,2020-02-27T00:07:14Z,2020-03-13T17:35:01Z,2020-03-13T17:35:01Z,"When I use EFI + CPU greater than 1 the client crashes with Guru Meditation (VINF_EM_TRIPLE_FAULT). From version 6.1.0 the issue starts to occur and is still present in version 6.1.4. In version 6.0.18- the error didnt't occur once. 

'''I made a lot of tests so I claim the trigger for this error is EFI enabled + vCPU > 1.'''

This is also discussed in forum where I attached log files directly after crash in version 6.1.0. Do you need log files for 6.0.18 (latest working version) and 6.1.4 (latest failing version)?

https://forums.virtualbox.org/viewtopic.php?f=6&t=96937",Tommy Parker
19393,Virtualbox Linux Guest crashes when opening Eclipse IDE,Linux,VirtualBox 6.1.4,2020-03-11T07:57:30Z,2020-03-11T08:18:17Z,2020-03-11T08:18:17Z,"Hi,

if I open the Eclipse IDE under my Linux guest, then the guest crashes.

The guest is ArchLinux 64bit and the host Windows 10. I use the official Virtualbox guest extensions and kernel modules. The Linux Kernel of the guest is 5.5.8

I will attach the Logfiles",JMeier12
19390,Unable to restart VM after loading it from a saved state,all,VirtualBox 6.1.4,2020-03-09T19:51:22Z,2020-03-09T19:53:06Z,2020-03-09T19:53:06Z,"This is occurring on multiple systems. Windows 7 & 10 hosts, Windows 7,8,10 & Linux guests

'''Recreation:'''
1) Boot up a Windows 7, Windows 8, Windows 10, or Linux VM.
2) Once loaded to the desktop, close the VM with the ""Save machine state"" option.
3) Start up the VM from the saved state.
4) Restart the VM. (ex: Start -> Power -> Restart)

 '''Problem:''' Soon after the VM begins to reload, a Guru Meditation error results. 
Log files are attached. The last recorded error is VERR_PGM_HANDLER_NOT_FOUND.

Point of interest: For Windows guests, a Windows Vista style boot screen (black w/ just a bar) is shown, instead of the usual Windows logo. So ''something'' is set a couple of seconds prior to the failure that is causing it.",JMH1
19389,win 7 problemes,other,VirtualBox 6.1.4,2020-03-09T16:33:17Z,2020-03-09T17:11:43Z,2020-03-09T17:11:43Z,"Bonjour depuis quelques jours, windows 7 ne fonctionne plus complètement et s'arrête. Il me demande de terminer le processus alors que je n'ai pas utilisé du tout, les programmes internes. Je suis dans l'impossibilité de redémarrer windows et je dois arrêter la machine virtuelle.
Je suis sous la dernière version (Version 6.1.4 r136177 (Qt5.6.2).
Dois-je essayer de supprimer la machine virtuelle et la recharger ou bien tout désinstaller et recommencer le processus d'installation.
j'ai une version normale de windows 7 ?
Cordialement.
",pascal28
19377,Add additional diagnostic information for the VERR_SUP_VP_THREAD_NOT_ALONE error,all,VirtualBox 6.1.4,2020-03-04T14:49:22Z,2020-03-04T14:49:22Z,2020-03-04T14:49:22Z,"Would it be possible to add additional information to the hardening log when this happens, to make it easier for users to identify the application that is causing the conflict?

For example, when VirtualBox detects an extra thread running that shouldn't be there, can you print a stacktrace to the hardening log that includes the DLL names for the code that is currently executing in that other thread?",rwreed
19376,[Win 7 64 Host] Sound not working in any VM,all,VirtualBox 6.1.4,2020-03-04T12:26:52Z,2020-03-04T12:26:52Z,2020-03-04T12:26:52Z,"Hallo there, 

My sound works since some versions (i think 5.x it started) when my sound didnt worked anymore in any VM. Its only in the VMs! Host sound works in any situation.
In this post, i already covered most of my Problem. [https://forums.virtualbox.org/viewtopic.php?f=6&t=96994&p=471320#p471320]",helgo1506
19362,VirtualBox crash on start ReactOS with BTRFS,other,VirtualBox 6.1.4,2020-02-29T01:13:37Z,2020-02-29T01:13:37Z,2020-02-29T01:13:37Z,"Install ReactOS 0.4.12 russian language with btrfs guest filesystem. After reboot run is crash.

ReactOS you can get from reactos.org",kotenok2000
19354,Problems accessing lots of items with nvda screenreader in virtualbox,other,VirtualBox 6.1.4,2020-02-27T09:06:14Z,2020-02-27T09:06:14Z,2020-02-27T09:06:14Z,"It is impossible to access lots of items in virutalbox using nvda screenreader. For example, you cannot choose one virtual machine if there are several virtual machines, you cannot choose an iso image file when first running a virtual machine. To reproduce the steps you should: 1. Launch nvda screenreader, 2. Open virtualbox, create a virtual machine and launch it. When the window with choosing the image disk opens press tab and you will hear the phrase ""uknown"". Expected behaviour: you should hear buttons such as continue, browse, you should be able to access the list with drives. I am also not able to quit the virtual machine using nvda screenreader.",Vsevolod Popov
19350,Radio box behavior on close window,Windows,VirtualBox 6.1.4,2020-02-25T21:44:38Z,2020-02-25T21:44:38Z,2020-02-25T21:44:38Z,"Hi I have noticed a behavior in the UI which may not be intended. When the Close Virtual Machine window appears, double clicking on any of the radio buttons will cause that option to be accepted. Would it be safer to instead only accept with the OK button?",mike_coreit
19341,VirtualBox 6.1.4 on Win 10 critical error on start,all,VirtualBox 6.1.4,2020-02-23T18:48:44Z,2020-02-24T11:29:34Z,2020-02-24T11:29:34Z,"----------------------------------------------------------
Failed to acquire the VirtualBox COM object.

The application will now terminate.

Error in C:\Users\<username>\.VirtualBox\VirtualBox.xml (line 33) -- UUID &quot;{00000000-0000-0000-0000-000000000000}&quot; has zero format.

F:\tinderbox\win-rel\src\VBox\Main\src-server\VirtualBoxImpl.cpp[740] (long __cdecl VirtualBox::init(void)).

Result Code: E_FAIL (0x80004005)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}
--------------------------------------------------------------------
Not sure where the reference to the F:\drive is coming from since I have no F: drive. 

Also, Line 33 or the referenced XML file has no resemblance to the error message about UUID 0000... zero format, but instead reads 

""  <ExtraDataItem name=""HostOnly/{69874491-c60a-44dc-a52d-f9e8b3f35315}/Name"" value=""VirtualBox Host-Only Ethernet Adapter""/>
    </ExtraData>""

Cannot provide log in usual manner since UI won't run. ",tjod
19330,Can't push Next button when VirtualBox Manager Import Virtual Appliance in  large zoom display setting,all,VirtualBox 6.1.4,2020-02-21T06:42:01Z,2020-02-21T06:42:01Z,2020-02-21T06:42:01Z,"I am using surface pro 7 with display 300% scale setting.
When Virtualbox Manager -> ""Import Virtual Appliance"", I can't push ""Next"" button because ""Import Virtual Appliance"" window is very large and some buttons appear out of display(attached virualbox6.1.4-scale300%.PNG).

This problem occurs with version 6.1.X, not occurs with version 6.0.X(attached virtual6.0.16-scale300%.PNG).

Of course, I don't always want to use 300%. I wanted to show that this problem occurs even on a famous PC(surface pro 7).
I usually use Fujitsu LIFEBOOK UH75/C3. In this Laptop PC, this problem occurs in its default scale(150%) and not occurs in 125% or less.

Fujits LIFEBOOK UH75/C3: 13.3in(1920 x 1080)
Surface Pro 7 12.3in(2736 x 1824)
Windows 10(1903)
",TT
21353,apic timer does not trigger in time,Linux,VirtualBox 6.1.40,2022-12-25T01:27:42Z,2022-12-25T01:27:42Z,2022-12-25T01:27:42Z,"Rencently,I found a bug of APIC timer.Since the vbox set the last VCPU thread as the thread to wakeup all the timer and other VCPU threads will sleep 500ms until the Last VCPU thread wakeup them.
If the last VCPU thread sleep a long time firstly,other VCPU thread's apic timer will not able to trigger in timer.This make other VCPU thread sleep at least 500ms.

here is may patch to the funtion apicSetTimerIcr in VMM/VMMALL/APICAll.cpp to fix the bug

{{{
#include ""TMInternal.h""
static VBOXSTRICTRC apicSetTimerIcr(PPDMDEVINS pDevIns, PVMCPUCC pVCpu, int rcBusy, uint32_t uInitialCount)
{
    VMCPU_ASSERT_EMT(pVCpu);

    PAPIC      pApic      = VM_TO_APIC(pVCpu->CTX_SUFF(pVM));
    PAPICCPU   pApicCpu   = VMCPU_TO_APICCPU(pVCpu);
    PXAPICPAGE pXApicPage = VMCPU_TO_XAPICPAGE(pVCpu);

    Log2((""APIC%u: apicSetTimerIcr: uInitialCount=%#RX32\n"", pVCpu->idCpu, uInitialCount));
    STAM_COUNTER_INC(&pApicCpu->StatTimerIcrWrite);

    /* In TSC-deadline mode, timer ICR writes are ignored, see Intel spec. 10.5.4.1 ""TSC-Deadline Mode"". */
    if (   pApic->fSupportsTscDeadline
        && pXApicPage->lvt_timer.u.u2TimerMode == XAPIC_TIMER_MODE_TSC_DEADLINE)
        return VINF_SUCCESS;

    /*
     * The timer CCR may be modified by apicR3TimerCallback() in parallel,
     * so obtain the lock -before- updating it here to be consistent with the
     * timer ICR. We rely on CCR being consistent in apicGetTimerCcr().
     */
    TMTIMERHANDLE hTimer = pApicCpu->hTimer;
    VBOXSTRICTRC rc = PDMDevHlpTimerLockClock(pDevIns, hTimer, rcBusy);
    if (rc == VINF_SUCCESS)
    {
        pXApicPage->timer_icr.u32InitialCount = uInitialCount;
        pXApicPage->timer_ccr.u32CurrentCount = uInitialCount;
        if (uInitialCount)
            apicStartTimer(pVCpu, uInitialCount);
        else
            apicStopTimer(pVCpu);


        PVMCC pVM   = pVCpu->CTX_SUFF(pVM);
        PVMCPUCC pVCpuDst = VMCC_GET_CPU(pVM, pVM->tm.s.idTimerCpu);

        #ifdef IN_RING3
            VMR3NotifyCpuFFU(pVCpuDst->pUVCpu, VMNOTIFYFF_FLAGS_DONE_REM | VMNOTIFYFF_FLAGS_POKE);
        #elif defined(IN_RING0)

           if (VMMGetCpu(pVM) != pVCpuDst)
            {
                switch (VMCPU_GET_STATE(pVCpuDst))
                {
                    case VMCPUSTATE_STARTED_EXEC:
                        GVMMR0SchedPokeNoGVMNoLock(pVM, pVM->tm.s.idTimerCpu);
                        break;

                    case VMCPUSTATE_STARTED_HALTED:
                        GVMMR0SchedWakeUpNoGVMNoLock(pVM, pVM->tm.s.idTimerCpu);
                        break;

                    default:
                        break; /* nothing to do in other states. */
                }
            }
        #endif

        PDMDevHlpTimerUnlockClock(pDevIns, hTimer);
    }
    return rc;
}
}}}
",liowmark
21348,VM with Linux crashes worse than DOS or Windows 95. Your dog can crash it,other,VirtualBox 6.1.40,2022-12-19T16:05:33Z,2022-12-21T12:56:29Z,2022-12-21T12:56:29Z,"Just write elementary program which creates large files, say, 1GB in size or one large file larger than 32 GB. And when your program running created 32GB of data in files VM part with Linux 100% crashes. 

Or if you have already large files aaa1, aaa2... and you combine them into one large file bbb which will be larger than 32GB this will also crash VB with its Linux like it is a dumb DOS 2.1. Here is syntax how to do that.   

$ ssh aaa* > bbb

I can try to attach this few lines Fortran program which is creating multiple files 1GB but if this will fail (because i  do not see any links or buttons how attach the file) you also can take it from the Forum (Windows Host part) where i was just published it.

P.S.
I failed to attach the file. OK here is the text. Just compile it with gFortran or any other Fortran compiler and run telling it to create more than 32 files (each will be 1 GB size file). It will crash at file #31",DanV
21307,Virtual Box 6.1.40 r154048(Qt5.6.2) freezing,Linux,VirtualBox 6.1.40,2022-11-24T00:20:32Z,2022-11-24T10:05:03Z,2022-11-24T10:05:03Z,"I recently upgraded VM to the summary version. Subsequently I have had guest system freezes at random times, usually when idle. I am running Linux LinuxMint 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux. I had on problems with previous versions.  Log should be attached.",Aiki451
21276,The drag and drop does not work,Windows,VirtualBox 6.1.40,2022-11-15T23:48:32Z,2022-11-15T23:48:32Z,2022-11-15T23:48:32Z,I have windows 10 host and windows 10 guest but drag and drop only works from guest to host,Heber
21186,VM No memory  Result Code:  E_FAIL (0x80004005),Linux,VirtualBox 6.1.40,2022-10-21T13:45:35Z,2022-11-03T21:42:40Z,2022-11-03T21:42:40Z,"What to do? 

Failed to open a session for the virtual machine Rocky Linux_8x64.

Failed to load R0 module C:\Program Files\Oracle\VirtualBox/VMMR0.r0: RTCrStoreConvertToOpenSslCertStore failed: \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VMMR0.r0 (VERR_NO_MEMORY).

Failed to load VMMR0.r0 (VERR_NO_MEMORY).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

",Butterfly011
21217,Cannot boot from VISO,Windows,VirtualBox 6.1.40,2022-10-29T19:09:38Z,2022-10-29T19:09:38Z,2022-10-29T19:09:38Z,"I have been struggling to boot an extracted Windows 11 medium using a VISO file without success until I found a comment regarding this topic:
https://www.virtualbox.org/ticket/19910#comment:24

They mention that on 6.1.32 booting from VISO worked fine which I can confirm.
However, I could not get it to work with VB 6.1.38, 6.1.40, 7.0.0 or 7.0.2.",Flubberlutsch
19588,Crash - referenced memory at 0x0000000000000000,Linux,VirtualBox 6.1.6,2020-05-15T16:29:56Z,2022-02-14T21:08:06Z,2022-02-14T21:08:06Z,"Host: Windows 10, 1803

Guest: Linux Mint, 18.3 Cinnamon 64-bit, 3.6.7

Guest Browser: Pale Moon, 28.9.3 (64-bit)

Web Site: 'https://coronavirus.jhu.edu/map.html'

Crash: ""VirtualBoxVM.exe - Application Error""

""The instruction at 0x00007FFA7B9075AD referenced memory at 0x0000000000000000. The memory could not be read.""

Status: Hard, reproducible.

Attached: C:\VMs\Mint18\Mint18-2020-05-15-12-12-36.log
",Mark Filipak
19505,Windows ME guest ICH AC97/Sound Blaster 16 Audio issues,Windows,VirtualBox 6.1.6,2020-04-17T16:48:30Z,2021-08-24T20:40:43Z,2021-08-24T20:40:43Z,"Whenever Windows ME Host plays audio such as a WAV, MID, or MP3, when the user clicks stop or when the audio file reaches the end, the audio file may or may not it keeps looping the last 1 or 2 seconds infinitely. It will most of the time. It even happens when a user logs in and the startup sound keeps playing until you play another audio file and stop it multiple times until all noise stops. ",RexBuyeo
19499,Wrong guest screen resolution with host using 1366x768,Linux,VirtualBox 6.1.6,2020-04-16T11:01:53Z,2020-09-16T13:30:33Z,2020-09-16T13:30:33Z,"Hello. I'm using VirtualBox 6.1.6 on a Windows 10 host, running an ArchLinux guest with the guest additions installed from the ISO, also in version 6.1.6.

When I maximize the screen, or use full screen, the guest resolution is wrong. It seems that VirtualBox is trying to round to the closest multiple of 8, so a few extra pixels are inserted. In maximized mode, scroll bars (horizontal and vertical) are shown. In full screen, a few pixels get off-screen.

It's a minor issue, and I could solve it by using the 1360x768 resolution on my laptop. It's not the recommended resolution, but solves the VirtualBox issue.",luisgbm
19551,Virtual Machine can not start,all,VirtualBox 6.1.6,2020-05-03T18:01:39Z,2020-09-04T14:39:12Z,2020-09-04T14:39:12Z,"Hi,

After Virtual Box upgrade to 6.1.6 r137129 (Qt5.6.2) many machines stop to work. Virtual BOX and Guest Aditional upgrade were performed fine. But after few days, in some VMachine the screen stay black after the power on. The issue happened in some WINDOWS10 and FEDORA Virtual Machine, but not on all.

I tried to uninstall and install VIRTUAL BOX but the black screen issue is still present. The only solution is delete and create the Machine from scratch.

Could some one help me to debug the issue to understand why it is happen?",Ivan_70
19589,Black screen after GUI login on Ubuntu with tools installed.,Linux,VirtualBox 6.1.6,2020-05-16T13:39:58Z,2020-08-28T12:50:31Z,2020-08-28T12:50:31Z,"Hi 

I'm running on virutalbox (6.1.6r137129) on Windows 10 and I have installed an Ubuntu 20.04 guest on the host. I have then installed the virtualbox guest additions on the guest. 

The problem I have is that after bootup, the login window is displayed and I log in but then the screen goes totally black. If I then resize the window, the desktop appears

I'm not sure if this is a bug in virtualbox / guest additions or some sort of conflict with Ubuntu. I have tried this multiple times installing new version of Ubuntu and each time the problem re-occurs so for me it is repeatable. 

Steps to reproduce:

1. Install Ubuntu 20.04 Guest OS (I gave it 128MB video memory, VMSVGA video, 3D acceleration enabled 

2. Boot guest OS 

3. Install guest additions (you'll need ""build-essential"" package installed too) 

4. Reboot 

5. Set guest to start up in full screen mode. 

6. Login 

<black screen> 

7. Re-size guest window. 

<image appears>

",MattF
19827,Display problem using Python-IDE,Windows,VirtualBox 6.1.6,2020-08-21T17:31:16Z,2020-08-21T17:31:16Z,2020-08-21T17:31:16Z,"I tried the Eric IDE for Python on a Win10 VM.
The text on various window tabs was distorted.
The effect occured with VBoxSVGA and activated 3D acceleration.
It vanished with 3D acceleration deactivated.",dornech2
19524,6.1.6 performance dreadful on VMSVGA and LinuxMint 18.2 VM on Windows 10 host,Linux,VirtualBox 6.1.6,2020-04-23T02:38:46Z,2020-05-28T20:13:00Z,2020-05-28T20:13:00Z,"I require VBoxSVGA with LinuxMint 18.2 running on a Windows 10 host.  Selection of VMSVGA causes a slow down of the entire VM, including disk access.  That's so weird.

",Trent
19624,Scroll bars missing in VirtualBox 6,all,VirtualBox 6.1.6,2020-05-26T18:24:52Z,2020-05-26T18:24:52Z,2020-05-26T18:24:52Z,"Hi,

I use scroll bars.  So it sucks when they constantly disappear.

There should be an option to permanently enable them.

Thanks.

Windows 8.1 64-bit
VirtualBox 6.1
",veganaiZe
19585,Mouse buttons freezes when using remote desktop,Linux,VirtualBox 6.1.6,2020-05-14T23:13:16Z,2020-05-14T23:13:16Z,2020-05-14T23:13:16Z,"The mouse buttons stop working (no response) when running Ubuntu (any version). The pointer still moves, but no clicking has no effect.

THis is very repeatable - it occurs every 2 or 3 minutes. The only workaround, is to close RDT, then start again.

Note: this issue does not happen when running windows application on the remote machine. Only when running Ubuntu on VirtualBox (6.1.X , i.e. any version of VBox).",2020Newbie
19578,VirtualBox startup failure under win10,Windows,VirtualBox 6.1.6,2020-05-13T01:38:27Z,2020-05-14T05:44:48Z,2020-05-14T05:44:48Z,"VirtualBox startup failure under win10

I have checked BIOS virtual settings
I have set Hyper-V off
I have stopped all Hyper-V services
",oracle-lover
19573,Can not install Ubuntu 18.04 or 20.04 only 16.04,Linux,VirtualBox 6.1.6,2020-05-08T11:40:55Z,2020-05-08T11:40:55Z,2020-05-08T11:40:55Z,"I tried to install Ubuntu 20.04 but it freezes during installation, then I tried 18.04 and same result, then I tried 16.04 and that installed normally.

I have windows 10, MSI Prestige laptop with 256GB SSD and 8GB memory
Version	10.0.18363 Build 18363


",Fugit185
19552,NAT Network is not working when I try to create or edit  a different IP other than (10.0.2.0)),Windows,VirtualBox 6.1.6,2020-05-04T09:19:43Z,2020-05-04T09:19:43Z,2020-05-04T09:19:43Z,"Virtualbox  version 6.1.6

This version has issues when trying to ping internet using NAT network.
there is no pin and cannot access the internet.

the problem is not in the default NAT network created by virtualbox 10.0.2.0/24.

the problem appears when i configure a new NAT network or edit the default one, like for example 192.168.0.0/24 in this case it will not work and can not access the internet.

I tested the following versions 6.0.20, 6.0.18, 6.0.12 and all of them work fine with no problems. 

 ",hassanmonji
19549,Problems in restoring VM window size from saved states,Windows,VirtualBox 6.1.6,2020-05-02T15:56:59Z,2020-05-02T15:56:59Z,2020-05-02T15:56:59Z,"Since upgrading to VBox 6.1.x (Win10 64)I noticed that the program frequently fails in correctly restoring the VM window size (especially if non maximized) when starting a VM from a saved state.

The VM starts normally (although with much less precision in the progress indicator, also since VBox 6.1x) but the VM window, after flashing for a moment at the saved size, shrinks to 640x480 and has to be manually resized, while obviously all the guest's desktop icons get rearranged and any open program windows gets shrunk as well.
This doesn't happen always but often (on an apparently random basis) and never happened, as far as I remember, with previous releases. I couldn't yet spot any clear and reproducible cause.

This is not a major problem, obviously.
However it actually IS some kind of malfunction.
At first I thought it could be just a momentary little regression in the new major update, but since it's still there in the latest 6.1.6 I thought I'd report it here too.",Armando
19548,VirtualBox freeze guest Ubuntu 18.04 if i add bridge or vlan,Linux,VirtualBox 6.1.6,2020-05-02T14:44:47Z,2020-05-02T14:49:17Z,2020-05-02T14:49:17Z,"host VirtualBox 6.1.6 r137129 (on windows 8 x64), guest Ubuntu 18.04 LTS HWE kernel 5.3.0-51-104generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 GNU/Linux, host have 1 ethernet interface directly connected to standalone d-link router with cable, guest have 3 nic's, 1 nat, 2 internal network, 3 brdiged-adapter. 

problem with manage bridge or vlan on guest, if i add manualy interface to bridge or configure vlan, after execute command - guest(ubuntu) freeze, do manual reboot.. example:

#bridge  
modprobe bridge
brctl addbr br0 #(all is ok)
brctl addif br0 bond0 #(all is ok)
brctl addif enp0s3 #(freeze) (tests enp0s3 as NAT, enp0s8 as Lan and enp0s9 as Bridged-adapter)

doesn't matter enp0s3/8/9 up or down before add to bridge, with IP address or without it..

#vlan
apt install vlan
modprobe 8021q
vconfig add enp0s3 100 
added VLAN with VID == 100 to IF -:enp0s3:-
(freeze)

maybe this a problem with my ubuntu in wrong network configuration or with kernel, I ask your help to make it all work :)",Deloris
19544,Inability to run 6.0-6.1.7 upgrading to 6.1.6,all,VirtualBox 6.1.6,2020-05-01T01:31:45Z,2020-05-01T01:31:45Z,2020-05-01T01:31:45Z,"After upgrading recently I am unable to launch vbox. The following error occurs on 6.1.6 and 6.1.7 (test). I tried rolling back versions and can successfully run 5.2.40 and lower. As soon as I cross  into 6.0+ the error occurs. The VBoxSDS doesn't seem to want to run and no files are written to the .VirtualBox directory on 6.0+. I did have 6.1.x installed and running before upgrading to 6.1.6 but I do not remember which version specifically. 


'''Failed to acquire the VirtualBox COM object.'''

The application will now terminate.

Completely failed to instantiate CLSID_VirtualBox: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D.

Result Code: ERROR_SERVICE_REQUEST_TIMEOUT 0x8007041D (0x8007041D)
Component: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}


I have tried:
1. Admin rights
2. Removing .VirtualBox directory
3. Cleaning registry
4. Comparability modes: Admin and older windows versions
5. Recover .VirtualBox files from backup
6. Update and verify all drivers
7. Remove all antivirus including defender
8. Hyper-V and VMware can run and have been removed
9. Extend service timeout length despite this being an immediate failure
10. Run bug report: WARNING: Failed to create the VirtualBox object (hr=0x8007041d)


Can provide bug report info if needed.",IamUSER
19522,VirtualBox does not recognize Windows 10 taskbar on the side,Linux,VirtualBox 6.1.6,2020-04-22T10:07:44Z,2020-04-22T10:11:56Z,2020-04-22T10:11:56Z,"I am using VirtualBox 6.1.6 on a Windows 10 host with Ubuntu 18.04.4 LTS as guest OS. I have installed the latest guest additions and am using the VMSVGA gfx driver. I am using a side-by-side dual monitor setup which is extended in Windows.

My windows taskbar is placed on the left, respectively right side for each monitor, effectively reducing the available width for maximized windows.

Since switching from 6.0.x I have the following issue:
My guest OS windows will show scrollbars to view the full screen rather than scaling the viewport down to fit into the window. I am using maximized guest os windows with the ""auto-resize gust display"" function enabled. I have switched off the display of menu or statusbars.

When moving the windows taskbar to the bottom of my host system, all scrollbars disappear.



",chross
19507,Shared folders in Guest OS (Windows 10) also occupy unused drive letters,Windows,VirtualBox 6.1.6,2020-04-17T17:11:36Z,2020-04-17T17:11:36Z,2020-04-17T17:11:36Z,"Drive letters are occupied even if they are not assigned in Windows 20 Guest OS! The Shared Folder are correctly connected to the designated drive letters in the Guest OS. Unfortunately, the other drive letters are also occupied. This leads for example to problems with other NAS SHARES that should be connected to drive letters. (Letters are occupied!!). 
The problem does not exist in the same environment with Virtualbox 5.2.40.

Shared Folder - Host OS Windows 10 (Build 1909) - Guest OS Windows 10 (Build 1909).  ",RonaldMcDonald
19502,VM cannot start if network adapter has a trailing space(s) in FriendlyName,all,VirtualBox 6.1.6,2020-04-16T22:51:34Z,2020-04-16T22:51:34Z,2020-04-16T22:51:34Z,"For some reasons my VM's with all kind of guest OS (Ubuntu, Windows, FreeBSD) suddenly refused to start with error ""Cannot start a VM because Network adapter <...> not found. You can shutdown or ..."". Name of adapter in dropdown list matched those in Windows network adapter properties.[[BR]]

After digging in debug logs I mentioned this -[[BR]]
 
@log Vbox.log.2:[[BR]]
============================[[BR]]
00:00:16.458034 AssertLogRel F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5274) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): <NULL>[[BR]]
00:00:16.458076 NetworkAttachmentType_Bridged: FindByName failed, rc=E_INVALIDARG (0x80070057)VMSetError: F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5275) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool); rc=VERR_INTERNAL_ERROR[[BR]]
00:00:16.458174 VMSetError: Nonexistent host networking interface, name ''''NVIDIA nForce 10/100 Mbps Ethernet''''[[BR]]
00:00:16.459027 Constructor failed with rc=VERR_INTERNAL_ERROR pfnCFGMConstructor=000007fef02e0b00[[BR]]
00:00:16.459846 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Nonexistent host networking interface, name 'NVIDIA nForce 10/100 Mbps Ethernet' (VERR_INTERNAL_ERROR)}, preserve=false aResultDetail=-225[[BR]]
00:00:16.460104 Console: Machine state changed to 'PoweredOff'[[BR]]
=============================[[BR]]
@Vbox.log[[BR]]
00:00:03.619271 [/Devices/e1000/1/LUN#0/Config/] (level 5)[[BR]]
00:00:03.619273   IfPolicyPromisc      <string>  = ""deny"" (cb=5)[[BR]]
00:00:03.619274   IgnoreConnectFailure <integer> = 0x0000000000000000 (0)[[BR]]
00:00:03.619275   Network              <string>  = '''""HostInterfaceNetworking-NVIDIA nForce 10/100 Mbps Ethernet ""''' (cb=60)[[BR]]
00:00:03.619276   Trunk                <string>  = ""\DEVICE\{77FEAE02-6B93-4633-B53D-9B670059780A}"" (cb=47)[[BR]]
00:00:03.619277   TrunkType            <integer> = 0x0000000000000003 (3)[[BR]]
=============================[[BR]]
Registry key at[[BR]]
""\\\Registry\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_03EF&SUBSYS_03EF1849&REV_A2\3&267a616a&0&38\FriendlyName"" was '''""NVIDIA nForce 10/100 Mbps Ethernet ""'''[[BR]]
=============================[[BR]]
So I suggest that somewhere in VBox's code trailing (and maybe leading) spaces in  the adapter's name are trimmed, causing further mismatch.[[BR]]
After I changed registry key (deleted trailing space character) all my VM's started perfectly, as before.

",Dyno_bel
19501,"Hello, good mornning from Mexico",Windows,VirtualBox 6.1.6,2020-04-16T15:19:08Z,2020-04-16T16:10:30Z,2020-04-16T16:10:30Z,"I tryed to start a virtual machine and a message error, into that mesage apears a note:try reinstalling the software, I tryed with versions, 5,2, 5,5, 6.1 and it is the same case
message:
The virtual machine 'RTCW' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\mgocc\VirtualBox VMs\RTCW\Logs\VBoxHardening.log'.",Pipen13
19498,vbox 6.1.2 vboxnetdhcp process blocks the update to vbox 6.1.6,all,VirtualBox 6.1.6,2020-04-16T11:01:53Z,2020-04-16T11:01:53Z,2020-04-16T11:01:53Z,you need to close vbox 6.1.2 and REBOOT your (windows 10) pc before installing / updating to vbox 6.1.6,clive darra
19622,VINF_EM_TRIPLE_FAULT on Server 2019 initial boot and install,Windows,VirtualBox 6.1.8,2020-05-25T19:14:15Z,2021-06-19T20:03:18Z,2021-06-19T20:03:18Z,"VT-v enabled in host bios, attempted with guest efi enabled as well as disabled. Host Hyper-V platform disabled. After parsing the logs with an untrained eye, it looks as if it might be an issue with the cpu. Attempted with 1, 4 and 8 threads allocated, and 4gb and 8gb memory allocated. ",moumoku
19781,DMI Handle is not unique,Linux,VirtualBox 6.1.8,2020-07-30T13:42:09Z,2020-07-30T13:42:09Z,2020-07-30T13:42:09Z,"I have been having issues with the DMI on VirtualBox.

When I run dmidecode on Ubuntu 18.04, there are 2 entries for Handle 0x0008.
When python's py-dmidecode runs, it loops through the DMI and the contents of the second entry for Handle 0x0008 replace the previous entry, causing it's output to be invalid.

I think the Handle entries should be unique.

I have attached a copy of my dmi output with the above issue (0x0008 listed twice).",MattRobinson
19715,VRDP/VBoxAuth not accepting MSTSC connection,Windows,VirtualBox 6.1.8,2020-07-10T22:29:45Z,2020-07-10T22:29:45Z,2020-07-10T22:29:45Z,"I've been trying to do this off and on for several years and on many versions of VB without success.  I've been through the documentation many times and asked for help on the forums.  Nobody has been able to find a solution and others have reported that this happens for them as well, including on Mac OS and Windows 7 and 10 hosts.

Host OS = Win 8.1[[br]]
Guest OS = Win XP[[br]]
VB version = 6.1.8, with matching extension pack[[br]]
VRDP Authentication = External/default (VBoxAuth)[[br]]
VRDP Port = 5003[[br]]

This process works fine if Authentication = Null, but when set to External I cannot make a connection from my local host (or any other Windows host) to the guest machine via VRDP. MSTSC tells me ""This computer can't connect to the remote computer"" before it even asks for a login.

I have been trying this on many different versions of VB, going back to the early days of v4.x.  Considering how widespread it seems to be in VB releases and across various hosts, I would think this is a problem that is part of the basic functionality.

A log is attached, but the important message from it seems to be
 ""AUTH: external authentication module returned 'access denied'""
",Davin
19704,VirtualBox 6.1.8 machine restart crash,Windows,VirtualBox 6.1.8,2020-07-07T09:25:48Z,2020-07-09T08:15:09Z,2020-07-09T08:15:09Z,"Hello.
VirtualBox 6.1.8-137981 works fine, but randomly when restarting crash the machine being only possible close the machine window and start an new machine window.
LOG are here added.
Excuse not is possible for me in moment test current version, but perhaps has the same issue because that crash when restart is since more of 2 previous versions.
Have an nice day.",Augusto
19639,host freezes when network load is high,Windows,VirtualBox 6.1.8,2020-06-03T20:49:20Z,2020-06-03T20:49:20Z,2020-06-03T20:49:20Z,"Hello, my friends.

I use a virtual machine to work while I stay in quarantine.
Periodically I faced with heisenbug when my host machine freezes.
I had no idea why this was happening.
But today I was able to reproduce the steps that lead to freezing.

So, what I have.
VBox: 6.1.8
Host: win 7 x64
Motherboard: ASUS AC97 rev.2 
Host disk: SSD Plextor PX-128M6S
Host network card: Realtek PCIe GBE (pci\ven_10ec&dev_8168&subsys_85051043&rev_09)

Guest: win 7 x64
Guest virtual network: Bridge / Intel pro 1000MT Desktop
Virtual disk: VHD / AHCI / i/o caching enabled
Virtual chipset: ICH9 / i/o apic enabled


What I do.
When I try to download a large file (e.g. 1 GB) 
then after a while the guest and the host system freezes.. absolutely )))

What could be the real cause of freezing
- bridged network adapter,
- i/o caching, scaling virtual disk,
- or chipset ...
I don't know,
but I tried a dozen variants of parameters,
and all the same, periodically it happens..
",Aleksey_Popov_1988
19629,VBox Fedora Linux Guest Additions 6.1.8 Client failed to get display change,Linux,VirtualBox 6.1.8,2020-05-28T17:25:27Z,2020-05-28T17:53:40Z,2020-05-28T17:53:40Z,"An error is displayed after updating VirtualBox to version 6.1.8 with the guest Additions into the Fedora Linux 31 operating system running KDE desktop.
Even when you have rebooted everything (having windows as the host OS) and logged on to Linux using a normal user account the desktop displays an error box bottom right-hand corner which is as follows: ""VBoxClient failed to get display change. rc=Verr_Access_Denied""",Clivewi
19626,"VirtualBox host-only adapter keeps getting set to an invalid configuration, which breaks multicast.",other,VirtualBox 6.1.8,2020-05-27T18:29:01Z,2020-05-28T14:51:14Z,2020-05-28T14:51:14Z,"Greetings!

OS: Windows 10 Pro x64
VirtualBox: 6.1.8r137981(Qt5.6.2)

The ""VirtualBox Host-Only Network"" adapter in Windows keeps getting set to an invalid state. When virtualbox is first installed, it populates the IPv4 IP address and DNS server. I also have to manually set the ""Automatic Metric"" to something like 800 as leaving it set to automatic breaks Multicast packets.

Every so often, I'll find I can't join a Multicast stream. Checking the settings in the ""VirtualBox host-only network"" adapter reveals:
- IP address/Subnet/Gateway are still set to manual, but are blank.
- DNS server is set to manual, and is completely blank
- Automatic Metric is set to automatic.

If I set the metric back to 800 and click ok, I get a message saying the IP address needs to be specified.

I have absolutely no idea what keeps changing the network properties for this adapter and setting it to an invalid state.",Fishscene
19627,Gnome Terminal does not open on Linux guest after installing 6.1.8 GA,Linux,VirtualBox 6.1.8,2020-05-28T09:21:16Z,2020-05-28T09:32:48Z,2020-05-28T09:32:48Z,"This seems to be related to the other x.11 issues reported with 6.1.8.

If I uninstall GA, I can open a gnome-terminal just fine.

However once I install GA, the terminal fails to launch (the mouse pointer turns to animated wait icon but ultimately no terminal window is opened).

I'm running Windows Host on Windows 10, Centos 8 (up-to-date) guest.

My Centos installation has both Wayland and xorg X.11 display servers installed for some reason (not sure if that's standard on Centos) but it's possible to select which one to use at logon.

When selecting Wayland I get the ""Parent seems to be non-X.11"" error message popup, but that error doesn't come up when I select the xorg server, so that's just the x.11 detection that's new in this release.

The problem is that gnome-terminal doesn't launch at all regardless of which x.11 server I select.

If I connect to the Linux guest from a Windows ssh client, that's fine, but running gnome-terminal from that bash shell doesn't work. Other x.11 programs (eg firefox) work fine from both the guest desktop and a remote ssh shell.

This should be easy to replicate.

Let me know if I can help diagnose further.
",qdev
19596,0x80bb0001 and 0x80bb000c freeze Virtualbox and forces PC reboot,Linux,VirtualBox 6.1.8,2020-05-17T20:12:29Z,2020-05-23T23:21:57Z,2020-05-23T23:21:57Z,"Have a virtual machine called ""manjaro-kde"". When I start Virtualbox 6.1.8 a different vm is selected, but as soon as I choose ""manjaro-kde"", Virtualbox just freezes and can't be closed. The GUI X button is greyed out. I have to use Process Explorer to kill it, and after that can't be relaunched until I reboot. At least UI should provide several ways to fix it, not freeze and forcing a reboot.

{{{
Oracle VM Virtualbox Manager
manjaro-kde: Inaccessible
Could not find an open hard disk with UUID {68875579-5923-4090-b612-f672cb93c5ff}
Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80bb0001)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
}}}
Forum thread: https://forums.virtualbox.org/viewtopic.php?f=6&t=98232",DeGarden
19613,Windows Guest on Windows 7+ loses focus during mouse capture.,Windows,VirtualBox 6.1.8,2020-05-22T15:09:04Z,2020-05-22T15:09:04Z,2020-05-22T15:09:04Z,"Mouse capture on Windows Guest (actually Android x86 also has issues):

If the start menu is hidden and is brought up during mouse movement, causes mouse capture to break free of the window, using the mouse after that causes odd behavior (wrong mouse click, etc).

High mouse acceleration also causes mouse capture to break free.

P/S2 Mouse, USB Tablet, USB Multi-Touch Tablet produce the same results.

To test:  Use the Windows 98 SE from Archives.org, mouse will refuse to stay in window after the start menu appears after hidden and will continue to become unusable after the initial break free.",BBISOFT
19612,Windows 10 with and without Hyper-V installed.,Windows,VirtualBox 6.1.8,2020-05-22T14:54:43Z,2020-05-22T14:54:43Z,2020-05-22T14:54:43Z,"Option:  VT-x/AMD-V Unchecked (not disabled)
Hyper-V: not installed, VT-x/AMD-V shows as Acceleration (shouldn't)
Hyper-V: installed, VT-x/AMD-V shows as Acceleration (shouldn't)

With Hyper-V installed (only once, even after removed), emulation fails to start due to missing VT-x/AMD-V support.

VT-x/AMD-V should follow the requirements of the checkbox, if not wanted, it shouldn't ""auto on"", instead the Acceleration should list ""None"".",BBISOFT
19611,"Cannot install Debian on 3 ISOs, after installing from 2 other discs constantly prompts to insert disc 1, even if it is already inserted",Linux,VirtualBox 6.1.8,2020-05-22T06:57:11Z,2020-05-22T06:57:11Z,2020-05-22T06:57:11Z,"I was installing Debian from 3 ISO images. 
Debian installer scanned all the discs, and at some point, it told me to insert 2 other discs. 
Then it prompted to insert disc 1 again, and that's where the problems began. 
I inserted disc 1, and it prompted me to insert it over and over again, even though the disc was in the virtual drive.  
It didn't recognize the disc. 
When I pressed return button, it said ""Cannot read from disc"" when I continued to installing GRUB. 
When the installation ended, I tried to boot Debian, and it didn't boot.
I have checked the ISO images, and there was nothing wrong with them.",anonymous7002
19604,Win XP Crash during AVG Install,Windows,VirtualBox 6.1.8,2020-05-20T00:07:06Z,2020-05-20T00:07:06Z,2020-05-20T00:07:06Z,"Hi,
I was installing AVG AV in Win XP Box, which is running on a Win 8.1 machine. It resulted in a critical error which stopped the VM. The program prompted me to log a ticket and post the log and image.  How do I correct this?  I have been retrieving data from old FDDs in the VM.  Now my data is trapped in the VM.

Thanks,
JC-bnm ",JC-bnm
19599,[VM Crash] Cannot access memory at 0x00000...,Linux,VirtualBox 6.1.8,2020-05-18T16:02:11Z,2020-05-18T17:05:29Z,2020-05-18T17:05:29Z,"My Ubuntu VM will randomly decide to access an inaccessible memory address causing a panic and crash.

I haven't been able to nail this down to a specific event, it seems to happen randomly. If I can identify a reproducible event I'll update the report.",Chris Doherty
21153,Programs show garbage output,Linux,VirtualBox 7.0.0,2022-10-14T23:22:36Z,2023-02-07T11:03:50Z,2023-02-07T11:03:50Z,Both alacritty - which uses the GPU - and emacs do not show characters and display garbage on typing under Wayland in Ubuntu 22 in VirtualBox 7.0. Currently unusable.,palladio
21138,7.0.0 doesn't work for a Windows 10 guest with multiple monitors,Windows,VirtualBox 7.0.0,2022-10-12T22:56:49Z,2022-11-08T19:56:17Z,2022-11-08T19:56:17Z,"After upgrading from 6.1.38 to 7.0.0 on a Windows 10 host, it seems to be working fine with a single-monitor Windows 10 guest VM, but not with a Windows 10 guest VM that has 3 monitors. It gets confused as to which monitor the mouse is clicking in, making it pretty much unusable. For example, I have the Windows task bar on the center monitor only, and when I try to click with the mouse pointer located over the Windows start button there, nothing happens. If I move the mouse pointer to the bottom left corner of the left monitor and click there, then the start menu opens on the middle monitor.

Also, when the mouse is in the main window the pointer looks good and stable (although it doesn't work for clicking in that window), but when I move it to one of the other windows then it gets jumpy and fuzzy.

I tried to disable 2 of the monitors from within Windows, but that was almost impossible with the mouse clicking on the wrong one.

Rolled back to 6.1.38 and all is hunky dory again.

I then disabled 2 of the 3 monitors while running in 6.1.38 before re-installing 7.0.0, and then the VM worked fine with just the one monitor. But when I then tried to re-enable a 2nd one, the issue came back.",Ian Puleston
21146,"Buttons,transparent list background and startmenu are garbaged with 3d acceleration in win10 guest.",Windows,VirtualBox 7.0.0,2022-10-13T16:32:45Z,2022-10-27T21:16:02Z,2022-10-27T21:16:02Z,"When 3d acceleration is enabled{
Buttons,transparent list background and other UI elements in Win10 Settings are garbaged.
Start Menu sometimes turns white.
}",ebk
21152,Save state and snapshot functionality is broken in version 7.0.0,Windows,VirtualBox 7.0.0,2022-10-14T22:00:23Z,2022-10-24T17:15:51Z,2022-10-24T17:15:51Z,"As I already wrote in the beta forum, I can't use neither save state nor snapshot functions in the new version.
After saving the state or making a snapshot, the next start of the guest causes an exception in the Vbox.

The saved state also can't be dropped. The drop function gives you ok, but after starting the VM, it tries to start from the saved state. Which is still on the disk.

Here is my original forum [https://forums.virtualbox.org/viewtopic.php?f=15&t=107200 post], and another [https://forums.virtualbox.org/viewtopic.php?f=2&t=107367 post] after release. I also append my logs.",boxer01
21136,Unwanted transparency in the Windows 11 guest,Windows,VirtualBox 7.0.0,2022-10-12T22:09:39Z,2022-10-23T23:16:04Z,2022-10-23T23:16:04Z,"I already described this in the beta [[https://forums.virtualbox.org/viewtopic.php?f=15&t=106990|forum]], with logs and pictures. Some of the elements of Windows itself (like Start menu or volume control) are transparent in the way it shouldn't be. It isn't a transparency effect from the Windows itself, which could be turned off. And this is an annoying bug in the cases when the current background color isn't matching the element content.",boxer01
21175,Result of sorting VMs isn't saved properly,all,VirtualBox 7.0.0,2022-10-21T07:16:25Z,2022-10-21T07:16:25Z,2022-10-21T07:16:25Z,"Since 7.0.0 it seems result of sorting VMs isn't saved properly.[[BR]]
If I click right button of mouse on any VM and select ""Sort"", then VMs are listed in alphabetical order.[[BR]]
But if I restarted VirtualBox Manager, then VMs are listed in the order before sorting.[[BR]]
It also happens with 7.0.2.
",Yasu
21173,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.",Windows,VirtualBox 7.0.0,2022-10-21T02:38:16Z,2022-10-21T02:38:16Z,2022-10-21T02:38:16Z,"When Windows XP (Guest OS) is PAUSE and restarted, AUDIO is not output.

  1. Start up Windows XP
  2. Windows XP is set to PAUSE
  3. (1 minutes elapse)
  4. (Release PAUSE)
  5. (AUDIO is output)
  6. (Set to PAUSE)
  7. 1 hour to 3 hours elapse
  8. Release PAUSE
  9. AUDIO is not output

Thank you very much for your cooperation. 
",aokadak@…
21165,Turtle != Snail,other,VirtualBox 7.0.0,2022-10-18T21:23:38Z,2022-10-18T21:23:38Z,2022-10-18T21:23:38Z,"One of the long awaited features of VirtualBox 7.0 only made it halfway into VirtualBox 7.0.0:

In the VBox.log file, it says: ""NEM: NEMR3Init: Snail execution mode is active!"". But the icon in the VM's window status bar still shows a green turtle. ;)",fth0
21157,Virtual box 7.0 oversize interface with DPI setup in Host,other,VirtualBox 7.0.0,2022-10-17T12:05:44Z,2022-10-17T12:05:44Z,2022-10-17T12:05:44Z,"The buttons and text is too large under 150% DPI setting in Windows 10 Host.

Interface image attached
[https://freeimage.host/i/tz2nMF]",tester_2022
21150,"Some programs see no files in shared folders (Host: W10, Guest: XP)",Windows,VirtualBox 7.0.0,2022-10-14T15:19:57Z,2022-10-14T15:19:57Z,2022-10-14T15:19:57Z,"In order to reproduce, you will need Norton Commander (I have version 3) or Alpha4 (a database manager; I have version 8).

In the guest VM (XP), Windows Explorer and CMD are able to see and list all the files in a shared folder mounted in the guest.

In some cases, alpha4 shows no files at all, and in others, it shows only files with .set extension (it's supposed to show .set and .dbf files always).

Norton Commander shows no files at all in shared folders mounted in the guest.

When issuing a DIR command when Norton Commander is running, I get ""Extended Error 234"" and no files listed at all (the DIR command should list files normally).

Norton Commander 3.0 can be downloaded from here: [https://winworldpc.com/product/norton-commander/3x]",ArneS
21143,with 2 monitor with different display resolution the mouse does't works,Windows,VirtualBox 7.0.0,2022-10-13T10:12:39Z,2022-10-13T10:23:09Z,2022-10-13T10:23:09Z,"Using the version 7 of Virtualbox, configured with two screens as per the attached images, configured to the maximum occupancy of the video, the mouse moves everywhere but the click is not located in the correct place on the X axis so it becomes impossible to select or open and close windows or interact with the system. The further you move away from the left side of the first screen, the more the error increases. Fortunately, you can select the windows menu and shut down the operating system. Conversely, if I use only one monitor, even on the ultrawide screen I have no problems.",JamesTKirk
21134,Screen capture didn't work on Windows guest,Windows,VirtualBox 7.0.0,2022-10-12T09:28:58Z,2022-10-12T09:28:58Z,2022-10-12T09:28:58Z,"Screen capture return black or transparent when the Vbox video driver installed into Win 10 21H2 guest. On driver removal screen capture works fine.

STR:
1) Update VirtualBox from 6.1 to 7
2) Update Guest tools in the Wondows guest OS
3) Try using screen capture 

Vbox logs attached
Screen recording on cloud, due to attachments limit

https://disk.yandex.ru/i/JcATChyQcuZl3Q
https://disk.yandex.ru/d/H3jMvKKWw-CxgQ

",vpupkin3
21129,Graphic bug when I enable aero effects on Windows 7,Windows,VirtualBox 7.0.0,2022-10-11T18:31:58Z,2022-10-11T18:35:27Z,2022-10-11T18:35:27Z,When I enable Aero effects on the latest version of VirtualBox the Aero graphics are poor after installing the VirtualBox Guest Additions,Sorecchione07
21219,RPC_S_SERVER_UNAVAILABLE when closing down VirtualBox GUI before virtual machine starts (regression),Linux,VirtualBox-7.0.2,2022-10-30T13:00:37Z,2023-02-12T15:38:45Z,2023-02-12T15:38:45Z,"Problem description:
1. In Oracle VM VirtualBox Manager (GUI tool) click on virtual machine and then Start button.
2. Because I don't need VirtualBox Manager GUI anymore I close it down.
3. Like 2 to 3 seconds later I get error:
Failed to open a session for the virtual machine <vm name>
and Details:
Callee RC: RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)

It looks to me this problem only appears if VirtualBox Manager is closed down before virtual machine is getting started.

If I wait for few seconds and the virtual machine's window appears before I close down VirtualBox Manager, it looks like error never appears.

This problem started to happen now that after using VirtualBox 6.1 for years I upgraded directly to VirtualBox 7.0.2.

I am very used to closing down VirtualBox Manager after I click on Start virtual machine button. It gets supper annoying that I get this error, because I just forget that now for some reason I have to wait before virtualbox machine GUI appears.

It looks like a regression in v7.0 comparing to v6.1.

My host is: Windows 10
My guest is: Ubuntu 22.04",bobJ
21230,VboxManage guestcontrol issue,Windows,VirtualBox-7.0.2,2022-11-01T10:33:28Z,2023-01-19T10:47:38Z,2023-01-19T10:47:38Z,"Prior to upgrading to VB 7.0, I could use vboxmanage guestcontrol to run a batch script on a windows 10 virtual machine and that script had access to the virtual machines shared folders/drives. I have been using this script for many years and many versions of VirtualBox. Now when the script runs it is reporting the H drive is not found. Everything in the VM_Setup.bat script works except for access to the H drive. The virtual machine has access to the H drive just not the guestcontrol feature.

Share folder section for the virtual machine is below. All of these drives work inside the virtual machine.
<SharedFolders>
<SharedFolder name=""Projects"" hostPath=""F:\"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""Downloads"" hostPath=""H:\Library\Downloads"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""Shared"" hostPath=""H:\"" writable=""true"" autoMount=""false""/>
<SharedFolder name=""ElecWorkFile"" hostPath=""Z:\"" writable=""true"" autoMount=""false""/>
</SharedFolders>

vboxmanage guestcontrol %VMN% run --quiet --unquoted-args --username ""%VMU%"" --password """" --exe ""H:\Scripts\VM_Setup.bat"" -- H:\Scripts\VM_Setup.bat %VM%

VBoxManage.exe: error: Waiting for guest process (flags 0x1) failed: No such file or directory ""H:\Scripts\VM_Setup.bat"" on guest
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component GuestProcessWrap, interface IGuestProcess, callee IUnknown
VBoxManage.exe: error: Context: ""WaitForArray(ComSafeArrayAsInParam(aWaitStartFlags), gctlRunGetRemainingTime(msStart, cMsTimeout), &waitResult)"" at line 1373 of file VBoxManageGuestCtrl.cpp
Waiting for VM Setup to Complete...
Press any key to continue . . .

<------ Test Script (TestQ.bat) Start ---------->
@echo off
cls
setlocal enabledelayedexpansion

SET VM=vm1
SET VMN=""WinX Rockwell""
SET VDI=WinX_Rockwell
SET VMU=alliance
SET VBMP=C:\Program Files\Oracle\VirtualBox
SET VBM=vboxmanage.exe
SET PATH=%PATH%;%VBMP%
SET LINES=0

:WAITFORSETUP
SET VMDONE=0

For /f ""usebackq tokens=*"" %%i IN (`%VBM% guestcontrol %VMN% run --quiet --unquoted-args --username ""%VMU%"" --password """" --exe ""H:\Scripts\VM_Status.bat"" -- H:\Scripts\VM_Status.bat %VM% `) DO (
SET /a LINES+=1
SET RESULTS=%%i
echo %%i
)
echo %VMDONE% %LINES%
IF ""%LINES%"" EQU ""0"" GOTO SKIP
IF ""%LINES%"" NEQ ""4"" GOTO SKIP
IF NOT ""!RESULTS!."" EQU ""!RESULTS:Complete=!."" (
SET VMDONE=1
)

:SKIP
If %VMDONE% EQU 0 (
Echo Waiting for VM Setup to Complete...
) ELSE (
Echo VM Setup to Complete
)
endlocal

pause
<------ Test Script (TestQ.bat) End ---------->
",cmccarron
21336,VirtualBox 7.0.2 interferes with LG Curved UltraWide 40WP95C audio,Linux,VirtualBox-7.0.2,2022-12-13T18:39:05Z,2022-12-13T18:39:05Z,2022-12-13T18:39:05Z,"I recently bought a LG Curved UltraWide 40WP95C monitor which is hooked up via DisplayPort to an NVidia 1080 graphics card. I use the built-in speakers in the monitor, which appear as 'LG ULTRAWIDE (NVIDIA High Definition Audio)'

System worked fine until I upgraded to VirtualBox 7.0.2 from 6.1.30. After this the audio device above would disappear if the screen blanked. On unblanking, Windows would have selected a different output device. To get the audio device back I had to start the Windows Device Manager and do a 'Scan for hardware changes'. This then found the device which I could then re-select as the output device.

A few seconds after doing the 'Scan for hardware changes' aI would get an error saying 'USB device not recognized', and an 'Unknown USB Device (Port Reset Failed)' would appear in the Device Manager under 'USB controllers'. Looking in the Windows Event Viewer I found an Error, Information and Error at the approx time this occurred. The messages below have a vendor id in them that maps to Virtual Box.


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\Vid_80EE&Pid_CAFE\5&9a1cce4&0&6
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: 
Migration Rank: 0xF000FFFFFFFFF122
Present: false
Status: 0xC0000719

# information

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 was configured.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1949
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\5&24955ba6&0&0


# Error

Device USB\VID_0000&PID_0001\6&1144d9c0&0&3 had a problem starting.

Driver Name: usb.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: 
Lower Filters: 
Upper Filters: 
Problem: 0x2B
Problem Status: 0x0


After uninstalling VirtualBox completely the problem disappeared and the 'LG ULTRAWIDE (NVIDIA High Definition Audio)' device has remained available, and selected as the default device, whenever the screen blanks.
",DaveCleland
21274,Incorrect font size use sticks after virtualbox window is moved to the second display,Linux,VirtualBox-7.0.2,2022-11-15T12:44:41Z,2022-11-15T12:44:41Z,2022-11-15T12:44:41Z,"Host Windows 10 PRO
[[BR]]
VirtualBox 7.0.2[[BR]]
Guest: Debian GNU/Linux [[BR]]
uname -a[[BR]]
Linux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux[[BR]]

I have two monitors attached to the PC.
[[BR]]

I have experienced a very annoying font size problem.

When the VirtualBox window is moved to the second display,
virtualbox suddenly causes the guest linux to use very large font.[[BR]]

The problem is that even after I move the virtual box window back to the original 1st display, the large font size is still used and it is really unusable after this happens.
I think the change of font size on the 2nd display may be related to the
different display resolution and used font size (there is an multiplication factor I set using individual config of the display, etc. I am using the Japanese Window and so I don't know the menu names for these settings in English.)


The only reference related such a font size issue I can find is the comment in 
comment 3 of ticket Ticket #20282.
{{{
but it uses a wrong font size if it is on the 2nd screen. 
}}}

Please note that strange font size usage when the program window is moved from the 1st window to the 2nd window is observed for many applications.
MS EXCEL, MS WORD, Thunderbird mail client to name a few, especially only half the window is shifted to the 2nd window.
However, many programs resume to use the right font size once the program window is reverted to the 1st window, or completely moved to the 2nd window.

VirtualBox is the only program that keeps on using strangely large font size even if I move the window back to the original. And for that matter, it keeps on using the strangely large font and it becomes unusable for my purpose.
Once VBox is retarted, the problem goes away, but it is very undesirable.

I will attach screen captures to explain the problem, but I am not sure if I can get the screen dump when the VBox window is split between the two windows.
I will take a photo in that case.
 

",ci-zephyurus
21260,shared folder does not work.  modprobe vboxfs fails due to  missing symbol (Debian kernel 6.0.0.2),Linux,VirtualBox-7.0.2,2022-11-10T07:32:09Z,2022-11-15T06:42:14Z,2022-11-15T06:42:14Z,"Host Windows 10 Pro
22H2 
19045.2251

Guest: Debian GNU Linux
$ uname -a
inux ip030 6.0.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux

VirtualBox:
7.0.2 r154219 (Qt5.15.2)

---
Problem: Shared folder between host and guest no longer works.

I have noticed that file sharing between the host no longer works.
I *think* this is  related to the local upgrade of the kernel to 6.0.0.2.

I installed the guesttools.
However, after some investigation, I realized vboxsf module is not loaded.
The reason is the missing symbols when vboxsf is loaded.

modprobe vboxsf fails:
{{{
root@ip030:/var/log# modprobe vboxsf
modprobe: ERROR: could not insert 'vboxsf': Unknown symbol in module, or unknown parameter (see dmesg)
}}}
dmesg shows:
{{{
[ 1992.940391] Spectre V2 : System may be vulnerable to spectre v2
[ 1992.940396] vboxsf: loading module not compiled with retpoline compiler.
[ 1992.940527] vboxsf: Unknown symbol VBoxGuest_RTLogRelGetDefaultInstanceEx (err -2)
[ 1992.940535] vboxsf: Unknown symbol VBoxGuest_RTLogLoggerEx (err -2)
[ 1992.940541] vboxsf: Unknown symbol VBoxGuest_RTErrConvertToErrno (err -2)
[ 1992.940554] vboxsf: Unknown symbol VBoxGuest_RTStrNLen (err -2)
[ 1992.940589] vboxsf: Unknown symbol VBoxGuest_RTLogBackdoorPrintf (err -2)
[ 1992.940600] vboxsf: Unknown symbol VBoxGuest_rtR0MemObjLinuxVirtToPage (err -2)
[ 1992.940631] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexCreate (err -2)
[ 1992.940637] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexDestroy (err -2)
[ 1992.940643] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRequest (err -2)
[ 1992.940649] vboxsf: Unknown symbol VBoxGuest_RTSemFastMutexRelease (err -2)
[ 1992.940655] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg1Weak (err -2)
[ 1992.940661] vboxsf: Unknown symbol VBoxGuest_RTAssertMsg2Weak (err -2)
[ 1992.940667] vboxsf: Unknown symbol VBoxGuest_RTAssertShouldPanic (err -2)
[ 1992.940673] vboxsf: Unknown symbol VBoxGuest_RTStrCopy (err -2)
[ 1992.940679] vboxsf: Unknown symbol VBoxGuestIDC (err -2)
[ 1992.940685] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRequest (err -2)
[ 1992.940691] vboxsf: Unknown symbol VBoxGuest_RTSemMutexRelease (err -2)
[ 1992.940697] vboxsf: Unknown symbol VBoxGuest_RTSemMutexCreate (err -2)
[ 1992.940702] vboxsf: Unknown symbol VBoxGuest_RTSemMutexDestroy (err -2)
[ 1992.940708] vboxsf: Unknown symbol VBoxGuest_RTMemContAlloc (err -2)
[ 1992.940714] vboxsf: Unknown symbol VBoxGuest_RTMemContFree (err -2)


}}}

It seems that vboxsf is not compiled locally using retpoline compiler?
But I am not sure if it matters or not.

",ci-zephyurus
21269,Unable to use more than 1 host-only adapter using Virtualbox 7.x,Windows,VirtualBox-7.0.2,2022-11-13T18:51:17Z,2022-11-13T18:51:17Z,2022-11-13T18:51:17Z,"Updated to VB 7.02.  I had 2 host-only adapters set up.  After upgrading BOTH host-only adapters were invalid. I would get an error stating that the host-only adapter was unable to open/load.  Create a NEW host-only adapter - same issue.

After deleting BOTH host-only adapters, the app created it's OWN host-only adapter.  I can use this one.  However, I am unable to use ANY OTHER host-only adapter.  I can change the config host-only adapter that the app created, and it works.  However, if I try to create my own (doesn't matter the config), I get an error when trying to load the VM. This DOES NOT happen with vitrualbox 6.x

My laptop is running Windows 11 Pro (latest updates).  The VM is Windows 10 ENT EVAL, but it doesn't matter what OS I use for the VM.
",Fenderluvr
21262,Cannot run multiple guest VMs of the same type if their *.vbox files are all in the same directory,all,VirtualBox-7.0.2,2022-11-10T23:24:47Z,2022-11-10T23:24:47Z,2022-11-10T23:24:47Z,"It seems that Virtualbox is using some kind of folder-level locking construct that makes it impossible to run multiple guest VMs if those guest VMs' corresponding *.vbox files are all in the same folder.  Attempting to launch a second VM stored in the same folder when another is running will lock up the window before the BIOS image appears and the VM will crash with this error:


{{{
The VM session was aborted.
Result Code:
E_FAIL (0X80004005)
Component:
SessionMachine
Interface:
ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
}}}


I like organizing all of my guest OSes by their main OS-type.  So, for example, Windows NT, 2000, 2003, and 2019 will all live in the same ""WINDOWS"" folder under a given directory hierarchy.  Ditto for Solaris 10, Solaris 11.4, OmniOS, and OpenIndiana under a ""SOLARIS"" directory.  I do not like using individual subfolders under this hierarchy and I want all of the *.vbox files to be together.

I don't really know why I like it this way, but I do, and I have found it difficult to organize things in a different manner that makes both myself and Virtualbox happy.  It feels like the folder-level locking is a kludge (I mean, why not file-level locking?), or at least, the crash is not being handled terribly well (a helpful error message being returned would be a marked improvement vs just outright crashing).

FWIW, how I got to this condition is every time I create a new guest VM, I set the bare minimum config, then shut VBox down and  any services to make sure all of the XML files are flushed out.  Then I manually move *.vbox and *.vdi files around to where I want them, then edit the XML's to point things to the new locations.  Other than the occasional hiccup from a still-running VBox process holding a lock, this setup has worked well for the past several years.  The inability to run multiple OSes of the same type is not a major blocker, but I had been perplexed for a while why it wasn't possible until I finally did some debugging.

Can someone maybe take a look at whether folder-level locking is still appropriate, or at least put some code in to detect this scenario and return an error message to the user?",Kumba
21207,Mouse snap behaves sticky on VB via a remote desktop,Windows,VirtualBox-7.0.2,2022-10-27T11:24:24Z,2022-11-10T11:48:40Z,2022-11-10T11:48:40Z,"Mouse snap behaves sticky on VB via a remote desktop

When I remote login via mstsc on a machine and use the VB on that machine the mouse snap behaves weird. It jumps instead of smooth moves. Sometimes it jumps to totally different places.

Guest Adition for 7.02 are also installed. VM OS is Win 11. Host OS is Win 10.",SecondBox
21241,Almalinux 8.6 aborts (virt-what),other,VirtualBox-7.0.2,2022-11-06T07:57:59Z,2022-11-08T14:43:45Z,2022-11-08T14:43:45Z,"After installing AlmaLinux 8.6 (RHEL 64-bit), normal start fails.
When using systemd.unit=rescue.target, I can get to a shell and when executing virt-what, the VM is aborted. Works on VirtualBox 6.1.40.",mtheiss
21251,Deleting snapshot's still available to Clone,other,VirtualBox-7.0.2,2022-11-07T18:58:21Z,2022-11-07T18:58:21Z,2022-11-07T18:58:21Z,"VirtualBox 7.0.2 on Windows 10 host.

1. Create snapshot that has plenty of changes from previous snapshot.
2. In VirtualBox Manager click on snapshot and Delete button. Problem appears Clone icon is still enable for currently deleting snapshot and if clicked Clone wizard appears.

It doesn't make sense to enable Clone for currently deleting snapshot. Probably clone would not even finish.",bobJ
21235,Can't run VBox,Linux,VirtualBox-7.0.2,2022-11-02T17:51:33Z,2022-11-02T17:51:33Z,2022-11-02T17:51:33Z,"I'm first use of vbox . I'm just download vbox and vdi image and run it. And it cause this error
I don't know what type of error it is.",takriz
21228,Plenty of sav files in Snapshots without any snapshot,Linux,VirtualBox-7.0.2,2022-11-01T08:18:24Z,2022-11-02T14:05:48Z,2022-11-02T14:05:48Z,"On Windows 10 host (Ubuntu guest) I have had a plenty of snapshots over period of time I have used VirtualBox 6.1 and now VirtualBox 7.0.2. I created snapshots and deleted them, then creating new ones etc. But today I have deleted all of the snapshots.

Now looking into Snapshots folder and I expect no files are in this folder anymore, but to my surprise there are plenty of files all with SAV file extension (the problem I am reporting).

Command ""dir"" output on Windows host:
19/05/2022  22:08       712.041.461 2022-05-19T21-07-57-214718900Z.sav
31/05/2022  17:56       782.450.690 2022-05-31T16-56-50-903121400Z.sav
07/06/2022  21:46       665.091.925 2022-06-07T20-46-36-299478900Z.sav
22/06/2022  21:55       702.938.444 2022-06-22T20-55-17-961063100Z.sav
14/07/2022  21:12       843.395.181 2022-07-14T20-12-47-010062000Z.sav
06/08/2022  16:09       707.927.057 2022-08-06T15-09-23-494845800Z.sav
30/08/2022  18:16       836.501.505 2022-08-30T17-16-26-777190700Z.sav
02/10/2022  17:44       717.281.998 2022-10-02T16-44-24-007573200Z.sav
07/10/2022  18:45       757.231.318 2022-10-07T17-45-24-466885500Z.sav

From file's date (May, Jun, July and August) I assume this files are from VirtualBox 6.1.x times. From file extension it looks those files are some saved snapshot's states. Why does they still exists? I assume there is/was some bug that does/did not delete saved state when snapshots gets deleted.

I shut down the virtual machine and move those files away from virtual machine Snapshot directory to some directory outside of VirtualBox and I started virtual machine and it starts up successfully and virtual machine works just normally.

I assume those files are not needed anymore, are they? Can I permanently delete them without any harm?",bobJ
21227,VM stop on error,Linux,VirtualBox-7.0.2,2022-10-31T20:56:18Z,2022-10-31T20:56:18Z,2022-10-31T20:56:18Z,Crash during guest OS upgrade.,Дмитро
21191,VirtualBox 7.0.x aborts VM using Windows XP,Windows,VirtualBox-7.0.2,2022-10-22T14:08:39Z,2022-10-31T02:04:50Z,2022-10-31T02:04:50Z,VM hosting WinXPSP3 created using VBox 6.1 fails to start (aborts systematically) on VBox 7.0 and 7.0.2,Kyle_Katarn
21213,Loading a saved state stops some graphical apps from rendering until reboot,Linux,VirtualBox-7.0.2,2022-10-28T21:51:10Z,2022-10-30T22:11:20Z,2022-10-30T22:11:20Z,"It is a simple problem and not critical but I need to make it work because I work with saved states a lot. I should mention that I am somewhat newbie with this guest system archlinux.

I have windows 10 and vbox7.0.2

Basically some GUI applications stop rendering properly if the VM is loaded from a saved state: midori, badwolf, spotify-launcher

I always save the state to resume it and my applications are still there without having to reopen everything, this is something quite common in virtualbox and it never gave me a problem (edited)

Apps like midori, badwolf or spotify-launcher work fine, but they stop rendering if I load a saved state and the only solution is to restart the vm, but other apps like nemo (file explorer) or the terminal (alacritty) don't have that problem.

I think the common detail is that they are gtk applications (however nemo works fine) and my guest distribution is probably not fully prepared for it because I use a very raw install of arch linux:
-i3, picom (i think it could be related), midori, badwold, opera, minbrowser, spotify-launcher. I had also installed arc-gtk-themes

I have tried to log the problem without results or relevant info inside of the VM, reset i3, picom and polybar but none of that corrects the problem.

I already tried reinstalling virtualbox-guest-utils and gtk, I installed gnome but also didn't change anything.

Booted up and midori works:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644709525266503/unknown.png]

Saved state just fine:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644710116659250/unknown.png]

Loading state just right after:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711106510858/unknown.png]

Some apps looks like this, they WORK but dont render properly:
[https://cdn.discordapp.com/attachments/826822179051929630/1035644711580475402/unknown.png]

I believe it this most likely a problem on my end, either host or guest, so considering you may not be able to reproduce, I attached some logs.


",mr.satoshi
21220,progress bar for exporting appliance is ambiguous,all,VirtualBox-7.0.2,2022-10-30T15:22:08Z,2022-10-30T15:22:08Z,2022-10-30T15:22:08Z,"The progress bar when exporting an appliance (and possibly other uses of the bar) are uncertain when the task is complete and there is no positive affirmation that the task is finished properly.

Some applications get to 100% and have some clean up tasks to do for 10-60 seconds and then give a positive affirmation.  There was a common dropbox problem where it got to 100% and never actually completed.  Most progress bars display themselves only while progressing and go away once finishing the task.

But here, it's hard to tell 99% from 100% as the default text is small and both have the same color progress bar.  But there is can be a lingering doubt whether it's actually completed without a positive confirmation of ""I'm done""

I don't know the ideal confirmation be it an ""task completed"" box with and ""OK"" button but one can be hesitant to close as it's uncertain it's actually done.",pguin
21208,7.0.2 r154219 does not play well with Windows 7 3D acceleration,Windows,VirtualBox-7.0.2,2022-10-27T21:05:45Z,2022-10-27T21:24:22Z,2022-10-27T21:24:22Z,"Using 3d Acceleration on my Windows 7 Professional guest (which worked fine with Vbox6) has all sorts of problems when on Vbox 7.

Most notably, I get a ""mirage"" effect any time I mouse over an item. Additionally, the minimize, maximize, and exit buttons do not appear at any time on any window. ",T4nkcommander
21209,Insert Guest Additions does not insert CD ISO,Windows,VirtualBox-7.0.2,2022-10-27T21:12:30Z,2022-10-27T21:12:30Z,2022-10-27T21:12:30Z,"Unlike in previous revisions, ""Insert Guest Additions"" does not do anything. The new notification window will tell me it is working, and the log says it writes files to my guest's ProgramFiles\Oracle\Vbox Guest Additions\update folder, but I cannot run the installer like in previous builds as the guest will not recognize a CD has been inserted. 

Loading other ISOs work fine, and I can install guest additions using the file path provided above (albeit with graphical glitches noted in other tickets). ",T4nkcommander
21196,Display issue with Windows System,Windows,VirtualBox-7.0.2,2022-10-23T10:52:03Z,2022-10-27T21:09:04Z,2022-10-27T21:09:04Z,Display broken after VBOX additions installed.,iRabbit_Jimmy
21206,Can't start vm after update,all,VirtualBox-7.0.2,2022-10-26T10:11:12Z,2022-10-26T20:22:32Z,2022-10-26T20:22:32Z,I have an ubuntu virtual machine with an encrypted disk on windows host. After update from 6.1.40 to 7.0.2 it does not start (there is no window where I can print my password for decryption). After downgrading to 6.1.40 I successfully started my vm.,sorsdt
21195,Display issue with Windows 8,Windows,VirtualBox-7.0.2,2022-10-23T09:32:08Z,2022-10-23T09:32:08Z,2022-10-23T09:32:08Z,"Windows 8 may not render UI properly in VirtualBox 7.0.2 r154219.
Guest OS: Windows 8
Host OS: Windows 10 Pro 21H2
Virtual Graphics Card: VBOXSVGA(192MB VRAM)
Host Graphics Card: Intel HD Graphics 4000 and AMD Radeon HD8570M with dinamic-switching.
[[Image()]]",Shimakaze
21283,"Windows 11 VM freezes with Windows 11 Host, VirtualBox 7.0.4",Windows,VirtualBox-7.0.4,2022-11-18T22:23:49Z,2023-02-13T18:04:08Z,2023-02-13T18:04:08Z,"I am running Windows 11 Pro 22621.819 with VirtualBox 7.0.4 and Hyper-V disabled. I was seeing the Windows 11 Guest VM freeze very quickly after boot, often within a few minutes. After the upgrade to 7.0.4 it still freezes, but after running for several hours. So it's better, but not fixed. This VM is a prebuilt developer image from Microsoft (WinDev2210Eval) with all Windows Updates applied to it.

",cmptrgk
21334,arcaos hard disks not recognized,other,VirtualBox-7.0.4,2022-12-12T04:35:48Z,2023-01-31T17:31:12Z,2023-01-31T17:31:12Z,"In Arcaos (OS/2) guests, hard disks are no longer recognized with Win ver 7.x.  The hard disks worked normally with ver 6.x.  The hard disks fail to be seen and partitioned. This defect is in BIOS or EFI installations.  This defect is seen with SATA, IDE, NVME type virtual storage.  The CD ROM is recognized and works normal in SATA. I had to revert back to 6.1.40.  Everything works in ver 6.x.",Rich87
21411,VBOX 7.0.x  graphic corruption - Intel GPU,Linux,VirtualBox-7.0.4,2023-01-16T13:19:25Z,2023-01-31T07:48:34Z,2023-01-31T07:48:34Z,"With VBOX 7.0 my Xubuntu 22.04 VM is unusable I have too much graphic corruption (Windows 11 Host / Seamless mode).
When I switch the guest app window to full screen I have no more corruption.

I had no issue with VBOX 6.x

Tested with
* Intel Gen 12 CPU (i7-1265U) / Iris Xe Graphics
* Intel Gen 8 CPU (i7-8550U) / Intel® UHD 620

[[Image(https://forums.virtualbox.org/download/file.php?id=47912)]]

I will try on my Nvidia 2800 GTX

Best regards",M.Poil
21410,RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf],Linux,VirtualBox-7.0.4,2023-01-16T09:54:46Z,2023-01-19T08:30:56Z,2023-01-19T08:30:56Z,"Hi,

I am seeing below error with kernel 6.1.5-200.fc37.x86_64.
{{{
------------[ cut here ]------------
memcpy: detected field-spanning write (size 14) of single field ""&pReq->StrPath"" at /tmp/vbox.0/utils.c:591 (size 6)
WARNING: CPU: 0 PID: 2470 at /tmp/vbox.0/utils.c:591 vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Modules linked in: vboxsf(OE) snd_seq_dummy snd_hrtimer vboxvideo(OE) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set rfkill nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter ip_tables qrtr sunrpc snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm intel_rapl_msr snd_timer intel_rapl_common pktcdvd pcspkr snd soundcore i2c_piix4 joydev zram crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic virtio_net ghash_clmulni_intel vmwgfx net_failover sha512_ssse3 drm_ttm_helper video serio_raw failover vboxguest(OE) ttm wmi ata_generic pata_acpi scsi_dh_rdac scsi_dh_emc scsi_dh_alua fuse dm_multipath
CPU: 0 PID: 2470 Comm: ls Tainted: G        W  OE      6.1.5-200.fc37.x86_64 #1
Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
RIP: 0010:vbsf_inode_revalidate_worker+0x542/0x580 [vboxsf]
Code: cf fd ff ff b9 06 00 00 00 4c 89 fe 4c 89 14 24 48 c7 c2 e0 a8 a5 c0 48 c7 c7 90 a8 a5 c0 c6 05 04 a6 00 00 01 e8 42 4c 31 d7 <0f> 0b 4c 8b 14 24 e9 9e fd ff ff 83 f8 98 41 bb b9 ff ff ff b8 fe
RSP: 0018:ffffb046852bbb58 EFLAGS: 00010282
RAX: 0000000000000074 RBX: ffff986681154e00 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff9874a863 RDI: 00000000ffffffff
RBP: ffff9866874a0144 R08: 0000000000000000 R09: ffffb046852bb9f8
R10: 0000000000000003 R11: ffffffff99146488 R12: ffff98667f8b6f00
R13: ffff98668100d6c0 R14: ffff986682574c00 R15: 000000000000000e
FS:  00007f85aafd3c40(0000) GS:ffff98675bc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056279ce6f718 CR3: 00000000011ce000 CR4: 00000000000506f0
Call Trace:
 <TASK>
 vbsf_dentry_revalidate+0x4f/0xb0 [vboxsf]
 lookup_fast+0x74/0xe0
 walk_component+0x1f/0x150
 path_lookupat+0x67/0x190
 filename_lookup+0xd3/0x1c0
 vfs_statx+0x8e/0x150
 do_statx+0x50/0x80
 __x64_sys_statx+0x62/0x80
 do_syscall_64+0x5b/0x80
 ? do_syscall_64+0x67/0x80
 ? fpregs_restore_userregs+0x12/0xe0
 ? exit_to_user_mode_prepare+0x18f/0x1f0
 ? syscall_exit_to_user_mode+0x17/0x40
 ? do_syscall_64+0x67/0x80
 ? do_syscall_64+0x67/0x80
 ? exc_page_fault+0x70/0x170
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f85ab16ca5e
Code: 83 0d 00 ba ff ff ff ff 64 c7 00 16 00 00 00 e9 a5 fd ff ff e8 d3 0f 02 00 0f 1f 00 f3 0f 1e fa 41 89 ca b8 4c 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2a 89 c1 85 c0 74 0f 48 8b 05 9d 83 0d 00 64
RSP: 002b:00007ffda585f578 EFLAGS: 00000246 ORIG_RAX: 000000000000014c
RAX: ffffffffffffffda RBX: 000056279ce5fee8 RCX: 00007f85ab16ca5e
RDX: 0000000000000900 RSI: 00007ffda585f6b0 RDI: 00000000ffffff9c
RBP: 000000000000025e R08: 00007ffda585f580 R09: 0000000000000020
R10: 000000000000025e R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 000056279ce5fed0 R15: 0000000000000000
 </TASK>
---[ end trace 0000000000000000 ]---
}}}",Srini8987
21412,Virtualbox + Hyper-V + 1GB Paging doesn't seem to be supported?,other,VirtualBox-7.0.4,2023-01-16T19:54:28Z,2023-01-17T19:00:38Z,2023-01-17T19:00:38Z,"I have a toy OS in which I use 1GB pages. 

The hardware supports 1GB. 
It works correctly on my Linux machine within VirtualBox. 
It works correctly on windows when Hyper-V is disabled.
It works correctly on windows using their Hyper-V VM manager.
It works correctly in qemu.

My conclusion so far is that the specific combination of VirtualBox + Hyper-V + 1GB paging is simply not yet supported correctly.

The result is a triple fault the moment the page is accessed for any reason. I'm not on my development machine at the moment, but I will post a log and a bootable ISO demonstrating the issue as soon as I can.

I'd definitely prefer to use VirtualBox for this as the Hyper-V VMs are quite limited.

Thanks!",Evan Teran
21408,Windows: High host cpu usage with 7.0.4,Windows,VirtualBox-7.0.4,2023-01-13T11:25:35Z,2023-01-13T11:25:35Z,2023-01-13T11:25:35Z,"Even though the guest OS is idle the VBoxHeadless process uses up a whole core for running (see attached screenshot).

The VM was running for a whole day and it's also the same if the start the VM normal or headless - it is constantly consuming the whole CPU core.

Both guest and host use the latest Windows 10 version (22H2 19045.2486).

I have also attached the configuration files of my VM, VBox logs and the sys-info of my host system.",IndyJones
21405,Linux guest on Windows 10 host does not start in seamless mode,Linux,VirtualBox-7.0.4,2023-01-12T14:25:59Z,2023-01-12T14:25:59Z,2023-01-12T14:25:59Z,"When the Linux host is started, it ''always'' starts in windowed mode, not in seamless mode. I must manually switch to seamless. When I shut down the machine in seamless mode and restart it, I expect it to restart in that mode, as it did in former versions of VirtualBox (6.x).

",reibi
21404,SECOND LINUX GUEST CRASHES ON WINDOWS STARTUP - VBOX 7.04 BUG,Linux,VirtualBox-7.0.4,2023-01-12T10:53:01Z,2023-01-12T10:53:01Z,2023-01-12T10:53:01Z,"When i am trying to automatically start a second Linux guest on windows 10 startup (through shell:startup), i get an error and the second Linux guest crashes.

The error message is ""The exception Breakpoint A Breakpoint has been reached (0x0000sFFCF66B225A. Click OK to terminate the program""

This bug  (or similarwith same results) occurs in all updates after 6.1.34 version, so i can't start e second guest automatically.

Please fix it !!!

Thank you ",Tasos Skarpathakis
21403,Broken Display Arrangement Configuration w/ VirtualBox Additions 7.0.4.,Linux,VirtualBox-7.0.4,2023-01-10T19:48:41Z,2023-01-10T19:48:41Z,2023-01-10T19:48:41Z,"Hello, the issue in which I will try to describe occurs when you have more than 1 display associated with the Linux Guest, in my case Ubuntu Mate 22.04 LTS running under a Windows Host.

The issue occurs when you try to switch the default display arrangement so that it matches the physical arrangement of the displays. For example, if your 2 displays need to be switched so that when you move a window from 1 display to the other, it understands that the display is on the left opposed to on the right.

The behavior that occurs when you attempt to switch the arrangement is this:

- The Guest displays a confirmation dialog.
- When you try to click on ""Keep this Configuration"" there is no way to interact with the dialog.
- However if you move the mouse to the display the dialog is not on, and try clicking where the window would be if it was on that display, you can interact with the dialog in a very difficult way.

The Guest moves the window to the correct display but the the window is rendered on the wrong display.

When I downgraded to VirtualBox v6.1.40, the issue still occurred. I then downgraded to the VirtualBox Additions that come with v6.1.40, and once that was complete, the issue no longer occurred worked correctly.

Therefore it is my conclusion that the VirtualBox Additions that are packaged with VirtualBox v7.0.4 are causing this annoying and unfortunate behavior in regards to display arrangement.

I can provide more information if needed however I cannot easily provide a video capture of the behavior I am experiencing.

Thanks,

-
Rick",agilis
21396,Mouse cursor not working properly with 2 monitor setup,all,VirtualBox-7.0.4,2023-01-05T22:03:20Z,2023-01-05T22:23:15Z,2023-01-05T22:23:15Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped at the top left corner of the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  When the VM window is moved to the same one as the main VirtualBox window the mouse still does not function properly in the VM.  Tried to attach a video but couldn't due to file size restrictions on here.",KernelPanic
21395,Mouse cursor buggy with 2 monitor setup,all,VirtualBox-7.0.4,2023-01-05T21:59:21Z,2023-01-05T21:59:21Z,2023-01-05T21:59:21Z,"When the main window is open on one monitor but the VM window is open on the other, the mouse will not work in the VM window, just gets trapped by the X button on the main window, focus changes when you try to click in it.  Did not happen prior to v7.  Running Windows 10 64 bit.  In the video attached, I was only able to record my rightmost screen (with the VM window in it) but the main VirtualBox window was maximized on the display to the left of the one that was recorded.",KernelPanic
21392,Microsoft Hyper-V Virtual Machine Bus Provider failed with code 37,Windows,VirtualBox-7.0.4,2023-01-03T13:45:05Z,2023-01-04T12:36:24Z,2023-01-04T12:36:24Z,"- Device driver displays following error:
Windows cannot initialise the device driver for this hardware. (Code 37)
The request is not supported.

- VB VM configuration has :
  [x] Enable PAE/NX
  [x] Enable Nested VT-x/AMD-V
both enabled

also Acceleration is configured:
Paravirtualization Interface: Hyper-V
Hardware Virtualization: [x] Enabled Nested Paging

- VB is installed on the following system:

OS Name	Microsoft Windows 11 Pro
Version	10.0.22621 Build 22621
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	LP11-D5938-5930
System Manufacturer	Dell Inc.
System Model	Latitude 5511
System Type	x64-based PC
System SKU	09C1
Processor	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz, 2712 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date	Dell Inc. 1.18.0, 10/3/2022
SMBIOS Version	3.2
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Dell Inc.
BaseBoard Product	0C33CM
BaseBoard Version	A00
Platform Role	Mobile
Secure Boot State	On
Installed Physical Memory (RAM)	32.0 GB
Virtualization-based security	Running
Virtualization-based security Required Security Properties	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, Secure Memory Overwrite, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured	Hypervisor enforced Code Integrity
Virtualization-based security Services Running	Credential Guard, Hypervisor enforced Code Integrity
A hypervisor has been detected. Features required for Hyper-V will not be displayed.	

",kjdro
21389,v7.0.0 + v7.0.2 + v7.0.4 hang-up and damages vms of v6.1.38,Windows,VirtualBox-7.0.4,2023-01-02T19:13:51Z,2023-01-02T19:13:51Z,2023-01-02T19:13:51Z,"My host machine is Windows11Pro with the last updates installed. I use various virtual machines with virtualbox 6.1.38 and they work fine. I tried to update to v7.0.0 + v7.0.2 + v7.0.4 and the old machines not only do not work with the new release but were damaged! I have been complelled to reinstall again v6.1.38 and recover the virtual machines by backups. The guest operating systems are: WindowsXP + Windows7_32 + Windows7_64 + Windows10Pro + Windows11Pro. What happens is that the virtual machine locks during boot, the cpu goes to 100% and the memory load remains the same. It seems that during the startup something goes wrong, the hypervisor hang-up and damage the boot disk. The biggest problem is that of the damage of the virtual machine.",tiria
21357,Guest addtions update issue in WIN 7,Windows,VirtualBox-7.0.4,2022-12-29T10:06:31Z,2022-12-29T10:06:31Z,2022-12-29T10:06:31Z,"Name: C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso

Could not open guest session: VERR_NOT_FOUND.
Result Code:
VBOX_E_IPRT_ERROR (0X80BB0005)
Component:
GuestWrap
Interface:
IGuest {00892186-a4af-4627-b21f-fc561ce4473c}
",iRabbit_Jimmy
21356,Guest addtions update issue in WIN 7,other,VirtualBox-7.0.4,2022-12-29T10:06:27Z,2022-12-29T10:06:27Z,2022-12-29T10:06:27Z,"Name: C:\Program Files\Oracle\VirtualBox/VBoxGuestAdditions.iso

Could not open guest session: VERR_NOT_FOUND.
Result Code:
VBOX_E_IPRT_ERROR (0X80BB0005)
Component:
GuestWrap
Interface:
IGuest {00892186-a4af-4627-b21f-fc561ce4473c}
",iRabbit_Jimmy
21303,exception in module VBoxMRXNP.dll => Fixed in SVN,Windows,VirtualBox-7.0.4,2022-11-23T13:10:14Z,2022-12-23T17:12:29Z,2022-12-23T17:12:29Z,"application running in MS Visual Studio 2019 crashes if it tries to access the file system (retrieve folder structure). In VirtualBox 6.1 it works fine.

windows Event log:
Faulting application name: EstiCon.Client.exe, version: 22.3.4.100, time stamp: 0x637e116c
Faulting module name: VBoxMRXNP.dll, version: 7.0.4.4605, time stamp: 0x6375102d
Exception code: 0x4000001f
Fault offset: 0x000132b0
Faulting process id: 0x448c
Faulting application start time: 0x01d8ff37dd906849
Faulting application path: c:\projekty\EstDevTest\Client\EstiCon.Client\bin\Debug\EstiCon.Client.exe
Faulting module path: C:\WINDOWS\system32\VBoxMRXNP.dll
Report Id: 7eb1303a-fddb-4eb3-a7ef-848370c48846
Faulting package full name: 
Faulting package-relative application ID: ",medved
21352,"VM crash with ""Memory could not be read"" error when usb-c monitors are disconnected",other,VirtualBox-7.0.4,2022-12-21T21:27:54Z,2022-12-21T21:27:54Z,2022-12-21T21:27:54Z,"Hi,

I am working on a laptop with USB-C port extender. There are two monitors connected via this hub. 
Host system is Windows 11. 
Guest system is Debian Bullseye with guest additions installed.

I usually wok with VM open in either maximized window or full screen mode on one of external monitors, sometimes on two of them. 

When I unplug the usb-c port extender without moving VM windows to internal laptop dislay, the VM throws error that says something in the spirit of:
 
> Instruction at 0x00007FF9F8D215FE referred to memory at address 0x0000029E2900F000. Memory could not be read. 

The exact error message is attached to this ticket, but it is in polish unfortunatelly. 

The problem was present in Virtualbox 6.something. I have upgraded to 7.0.4, but the problem perssts. 

I happens almost every time I unplug the hub without moving the vm windows to main screen or minimizing them. It never happens if I have vm window only on internal screen. 

I have VM set up with:
RAM: 32GB
CPU: 6
EFI: on
Accelleration: Hyper-V
Video memory: 128MB
Screens: 2
GFX: VMSVGA
Accelleration: 3D

",SWilk
21322,VM loses connection to Host,Windows,VirtualBox-7.0.4,2022-11-30T15:08:06Z,2022-12-20T09:13:49Z,2022-12-20T09:13:49Z,"After some time the guest OS (Windows 11 Pro 22H2 22621.819 Windows Feature Experience Pack 1000.22636.1000.0) loses connection to the host OS (Windows 11 Enterprise 21H2 22000.1219).
Keyboard and mouse are unresponsive, ACPI shutdown doesn't work either, although the guest os seems to work normally.
The log (attached) reports several 'vmmDevHeartbeatFlatlinedTimer'",Matt G
21338,Kernel Panic Boot2Docker Distro,Linux,VirtualBox-7.0.4,2022-12-14T16:44:28Z,2022-12-19T01:57:35Z,2022-12-19T01:57:35Z,Please see this [https://github.com/hashicorp/vagrant/issues/13011 Vagrant bug report]. The comment by phinze suggests this is a VirtualBox issue.,goldfita
21345,Deleting running VM snapshot leaves the .sav file on disk,Windows,VirtualBox-7.0.4,2022-12-18T16:39:15Z,2022-12-18T16:39:15Z,2022-12-18T16:39:15Z,"The snapshot file for running VM (.sav) remains on the disk after deleting the snapshot. Issue appeared with 7.0.4 and was not there in 6.1.xx.

I have multiple running VM snapshots so it takes time and effort to identify the unused .sav files and delete them manually.

Issue is replicated easily as mentioned on the [https://forums.virtualbox.org/viewtopic.php?f=6&t=108066 forum's thread].",AmirPK
21343,Keeps losing linked disk,other,VirtualBox-7.0.4,2022-12-16T11:16:33Z,2022-12-16T11:16:33Z,2022-12-16T11:16:33Z,"I had cause to delete a linked clone (not the files ..) to investigate something. Now, having re-added the clone (successfully ..), I'm having to keep adding the clone's disk snapshot to the list of hard disks (it appears under the parent as expected).

A restart of the application retains the added disk and the VM boots, but it seems that whenever I restart the host (I normally just sleep/resume), the snapshotted disk disappears from the list of registered disks and has to be added by hand again. The 'add' doesn't seem to be retained through a host restart - or at least I've only so far seen the phenomenon after restarts. Will add to the report if I see it on other occasions.",Granta
21340,VM crashes while upgrading GuestAdditions to 7.0.4,Windows,VirtualBox-7.0.4,2022-12-15T09:05:34Z,2022-12-15T09:05:34Z,2022-12-15T09:05:34Z,What the title says. Attaching logs...,Wand
21335,can't see guest OS mapped network drives in File Manager - regression,Windows,VirtualBox-7.0.4,2022-12-12T15:40:17Z,2022-12-12T15:40:17Z,2022-12-12T15:40:17Z,"VB 7.0.4, W10 guest OS.
In the bridged network guest, map a drive to a server on your network - e.g., y:\\myserver\myshare.  (server credentials are different than guest OS credentials)
Start File Mgr, login - observe the Y drive is not shown.  This worked in 6.0.",Justinh
21330,Switching between Guided and Expert mode clears populated fields,other,VirtualBox-7.0.4,2022-12-09T22:06:53Z,2022-12-10T18:13:56Z,2022-12-10T18:13:56Z,"If you start a new VM, put in some basics, like name, ISO, etc., then switch modes, those inputs are cleared and you have to start over.",Justinh
21331,"Delete of a VM does not delete unattended files, so can't recreate VM",other,VirtualBox-7.0.4,2022-12-09T23:40:43Z,2022-12-09T23:40:43Z,2022-12-09T23:40:43Z,"If you create a VM using unattended installation, then you RMB on the VM in the hypervisor -> Remove -> Delete All, the unattended files remain.  then if you try to create a new VM using the same VM name, you get an error because of the left over files.",Justinh
21329,Help doc comes up behind new VM dialog and can't be accessed,other,VirtualBox-7.0.4,2022-12-09T21:46:55Z,2022-12-09T21:46:55Z,2022-12-09T21:46:55Z,"1) start a new VM
2) in the ""Create Virtual Machine"" dlg, click the Help button - the help doc opens but you can't get to it!

Also, the ""?"" in the title bar does nothing useful, so I couldn't even use that as an alternate.",Justinh
21324,Carbon Black EDR: VirtualBox VMs Fail to Start After Windows Sensor Upgrades to 7.3.0,all,VirtualBox-7.0.4,2022-12-05T14:00:00Z,2022-12-05T14:00:00Z,2022-12-05T14:00:00Z,"https://community.carbonblack.com/t5/Knowledge-Base/EDR-VirtualBox-VMs-Fail-to-Start-After-Windows-Sensor-Upgrades/ta-p/113625

Environment
EDR Windows Sensor:  7.3.0
Virtual Box: 6.1.34

Symptoms
VirtualBox VMs do not start if the Windows host is running EDR win-7.3.0.

Cause
VirtualBox hardening script may have issues with the updated, secure signed certificate on the CB win-7.3.0 cbedramsi.dll file.

Resolution
Until VirtualBox hardening script permits the new signed certificate, the Windows host should stay on EDR win-7.2.2.
VMs within VMware Workstation or Microsoft HyperV start properly when the Windows host is running EDR win-7.3.0.

Additional Notes
CB win-7.3.0 uses a new more secure certificate; SHA2 384bit Sectigo CA with integrity checks.
If a case is opened with Virtual Box, VMware Carbon Black Support and Engineers could provide additional information.  
 
",neglas
21323,Non-mouse Integration,all,VirtualBox-7.0.4,2022-12-01T02:00:54Z,2022-12-01T02:00:54Z,2022-12-01T02:00:54Z,"I have noticed that whenever I disable mouse integration on my virtual machines, my mouse would jump to the top left corner of my screen when I captured it. If I re-enable mouse integration it works as expected. Looking through the logs, I don't notice anything unusual, but I've attached them anyway. I've used a Windows 10 virtual machine as my test.",Harvey Walker
21316,"VM GUI does not open, machine visibly starting in preview",all,VirtualBox-7.0.4,2022-11-26T11:59:04Z,2022-11-26T11:59:04Z,2022-11-26T11:59:04Z,"When clicking on the ""Start"" button for any VM in the VM Manager, it starts, but no VM control window appears. However, the machine is visibly starting in the small preview box.
I know of 2 workarounds:
1. Use RDP.
2. Close VM Manager. Restart the VBoxSDS service. Open VM Manager and wait until it appears. This fixes my problem until the host reboots.
These are the commands I run to restart the VBoxSDS service:

{{{
sc stop VBoxSDS
sc start VBoxSDS
}}}
",AptemCat
21293,UI confused by multiple DPI settings,all,VirtualBox-7.0.4,2022-11-21T19:21:31Z,2022-11-26T03:30:12Z,2022-11-26T03:30:12Z,"Upgrading from 6.1.x to 7.x the UI seems ""doubled in size"".
I have 3 monitors, main set to 150% scale, laterals set to 125% scale.
Seems that the UI gets confused by this (?) and ends up with very large fonts.
",EPinci
21298,Menu Screen -virtual screen - Use creen # does not work no more,Windows,VirtualBox-7.0.4,2022-11-23T10:45:55Z,2022-11-23T10:45:55Z,2022-11-23T10:45:55Z,"From version 7, it's impossible to move a ""full screen mode"" VM from a screen of my computer to another. It always worked well with version 6.

The VM stays stuck on screen 3 when I ask it to go to screen 2, while taking the size of the screen 2 (!).

See capture.",JLB
21287,Unable to Show Windows Side by Side,other,VirtualBox-7.0.4,2022-11-19T08:33:54Z,2022-11-19T08:33:54Z,2022-11-19T08:33:54Z,"I have multiple VMs opened and I want to show them side by side, so in the task bar I clicked on Show Windows Side by Side option but it is not working, it used to work for the previous version but after I updated it in the new version it doesn't work anymore!",stevenrolando
21505,Black Screen and Blinking Cursor using 3D Accelerator,Windows,VirtualBox-7.0.6,2023-02-15T11:37:54Z,2023-02-15T11:37:54Z,2023-02-15T11:37:54Z,"I have installed VB-7.0.6 with 7.0.6 Guest Additions on my Windows 7 Pro client.   However, if I turn on 3D Accelerator in Settings, my system then has a black screen and a blinking cursor and is unusable.  

When I reported this issue here:  https://forums.virtualbox.org/viewforum.php?f=2   I was instructed to open a ticket.

Here is the log files and my hardware setup.  ",QB
21450,Cannot build Guest Additions 7.0.6 for CentOS Stream 9 kernel 5.14.0-239.el9.x86_64 => fixed in svn,Linux,VirtualBox-7.0.6,2023-01-31T23:04:39Z,2023-02-14T11:37:32Z,2023-02-14T11:37:32Z,"{{{
In file included from /tmp/vbox.1/vboxvideo_guest.h:34,
                 from /tmp/vbox.1/modesetting.c:27:
/tmp/vbox.1/vbox_drv.h:378:32: error: field ‘base’ has incomplete type
  378 |         struct drm_framebuffer base;
      |                                ^~~~
In file included from /tmp/vbox.1/hgsmi_base.c:27:
/tmp/vbox.1/vbox_drv.h:378:32: error: field ‘base’ has incomplete type
  378 |         struct drm_framebuffer base;
      |                                ^~~~
make[2]: *** [scripts/Makefile.build:321: /tmp/vbox.1/hgsmi_base.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [scripts/Makefile.build:321: /tmp/vbox.1/modesetting.o] Error 1
make[1]: *** [Makefile:1915: /tmp/vbox.1] Error 2
make: *** [/tmp/vbox.1/Makefile-footer.gmk:133: vboxvideo] Error 2
}}}
",Steven Barre
21446,Linux guest additions 7.0.6: vbox_drv.c compile error with (RH)EL 8.7 kernel: implicit declaration of function ‘vgacon_text_force’ => fixed in svn,Linux,VirtualBox-7.0.6,2023-01-30T12:57:55Z,2023-02-14T11:36:42Z,2023-02-14T11:36:42Z,"Host:
- Microsoft Windows [Version 10.0.19044.2486]
- VirtualBox 7.0.6 r155176 (Qt5.15.2)

Guest (as updated to latest 8.7):
- RockyLinux 8.7
- kernel: 4.18.0-425.10.1.el8_7.x86_64

Guest additions kernel module will fail to build on:

{{{
/tmp/vbox.0/vbox_drv.c: In function ‘vbox_init’:
/tmp/vbox.0/vbox_drv.c:54:34: error: implicit declaration of function ‘vgacon_text_force’ [-Werror=implicit-function-declaration]
 #  define VBOX_VIDEO_NOMODESET() vgacon_text_force() && vbox_modeset == -1
                                  ^~~~~~~~~~~~~~~~~
}}}
(see attached log)

Same build error w/ VBoxGuestAdditions_7.0.7-155247 (latest testing available)

I've seen in RHEL kernel changelog that nomodeset changes might have been backported into -425, not sure if this is the cause though?

{{{
* Fri Dec  9 13:00:00 2022 Jarod Wilson <jarod@redhat.com> [4.18.0-425.9.1.el8_7]
- Documentation/admin-guide: Document nomodeset kernel parameter (Jocelyn Falempe) [2145218 2143952]
- drm: Move nomodeset kernel parameter to the DRM subsystem (Jocelyn Falempe) [2145218 2143952]
}}}


Changing
{{{
#  define VBOX_VIDEO_NOMODESET() vgacon_text_force() && vbox_modeset == -1
}}}
to
{{{
#  define VBOX_VIDEO_NOMODESET() drm_firmware_drivers_only() && vbox_modeset == -1
}}}
seems to fix the build, although I have no idea whether this produces working driver module.",mareks
21502,PhpStorm is not displayed correctly,Linux,VirtualBox-7.0.6,2023-02-13T19:00:54Z,2023-02-13T19:22:45Z,2023-02-13T19:22:45Z,"After update to version 7.0.6 windows of PhpStorm displays with black screen. only some icons are visible on the black screen.
VM Log - [https://pastebin.com/HuEXwQXt]
[[Image(https://prnt.sc/JvSroECLwPJT)]]",Dmytro
21497,Wrong Bus Frequency and DRAM Frequency,other,VirtualBox-7.0.6,2023-02-12T19:48:51Z,2023-02-12T19:48:51Z,2023-02-12T19:48:51Z,"Using CPU-Z 2.02 in a Win2K3 (or ReactOS 0.4.15) guest using VBox 7.0.6 on a Win11 host, incorrect Bus Frequency and DRAM Frequency is being reported",Kyle_Katarn
21495,A critical error has occurred while running the virtual machine,other,VirtualBox-7.0.6,2023-02-12T18:46:52Z,2023-02-12T18:46:52Z,2023-02-12T18:46:52Z,"Hi All,

Please help, I am using the Virtual box(7.0.6) with Windows 10 64 bit(host) and Ubuntu(22.04) 64 bit (client), when i try to run Docker Desktop in virtual box with Nested VT-x/AMD-V enable having an error with

(""A critical error has occurred while running the virtual machine and the machine execution has been stopped."")

When I dont launch docker desktop I dont see this error

Here I am attaching the log record and its files.
",gopik45
21494,Only crashes and error messages since the update to 7.0.6,Windows,VirtualBox-7.0.6,2023-02-12T11:33:02Z,2023-02-12T11:33:02Z,2023-02-12T11:33:02Z,"The update has been around for a while, though I've always put it off until now. And as it turns out, for a good reason: since the latest update, I only get error messages. I don't know what the new ""update"" is supposed to bring, except some improvements in the GUI. 

PC was already restarted after the update, just as info. 

So, the problem is that sometimes I can start a new VM and sometimes not. The VM is W10, if relevant. Everything has remained as it is so far, nothing was changed at all after the update. It's even worse when I want to boot/activate a saved state, that doesn't work at all by now since the update. There come then error messages like:

Callee RC:


RPC_S_SERVER_UNAVAILABLE/0x800706ba (0X800706BA)


or


The instruction at 0x... referenced memory at 0x0000000000. The memory could not be written. Click on OK to terminate the program. Click on CANCEL to debug the program.",FrankKlein
21493,"DnD: Error: Drag and drop to guest not possible -- either the guest OS does not support this, or the Guest Additions are not installed.",Linux,VirtualBox-7.0.6,2023-02-12T05:48:02Z,2023-02-12T05:48:02Z,2023-02-12T05:48:02Z,"Drag and drop operation from host to guest failed.

DnD: Error: Drag and drop to guest not possible -- either the guest OS does not support this, or the Guest Additions are not installed.

Código de Resultado: VBOX_E_DND_ERROR (0X80BB0011)
Componente: GuestDnDTargetWrap
Interface: IGuestDnDTarget {50ce4b51-0ff7-46b7-a138-3c6e5ac946b4}
Chamador: IDnDTarget {ff5befc3-4ba3-7903-2aa4-43988ba11554}

",Willian Tetsuo Kaneta
21492,Host Win11-VM with Win11 works under VB 6.1.x under VB 7.0.x VM freezes after a few minutes,Windows,VirtualBox-7.0.6,2023-02-11T22:33:27Z,2023-02-11T22:33:27Z,2023-02-11T22:33:27Z,"Problem: 

One of my most important VMs that runs every day and often for several days at a time is a Windows 11 VM (current kernel and driver, updated from Windows 7->Windows 10->Windows 11) and runs without problems and Virtualbox 6.1.x

As soon as the same VM runs under 7.0.x it freezes with the same settings, etc. I hoped that the error would disappear with the later versions and bug fixes in 7.0.x but unfortunately the behaviour is still the same (since 7.0.0 to 7.0.6).

Of course the latest VirtualboxGuestAdditions are always installed (at the moment the 7.0.6 VirtualboxGuestAddoitions runs in the Win 11 VM under Virtuelbox 6.1.42 without problems) in every Virtualbox version in the Win 11 VM.

I have already tried the settings such as ParaVirtualisation Hyper-V or Default and 3D acceleration on or off (normally off). Nothing helped-

Host System: Windows 11
CPU: Intel i7-6820
RAM: 64GB
Graficcards: Intel HD Graphics 530 (Driver Version 31.0.101.2115 (Date: 16.11.2022)) , Nvidia Qua M2000M (Driver Version 31.0.15.2824 (Date: 15.01.2023))


",RonaldMcDonald
21433,[VirtualBox 7.0.x] Graphical artifacts with 3D acceleration enabled | Windows 7/10 guest,Windows,VirtualBox-7.0.6,2023-01-26T11:36:10Z,2023-02-11T20:22:32Z,2023-02-11T20:22:32Z,"After installing the Guest Additions on guests like Windows 10 or Windows 7 (on Windows 7 you need to additionally enable Aero) and having the 3D acceleration enabled, graphical glitches/artifacts/issues start appearing.

Example steps to reproduce:
1. Create a new Windows 10 VM (enable 3D acceleration in the VM settings)
2. Install Windows 10
3. Install Guest Additions
4. Restart guest system (to complete Guest Additions installation)
5. After restarting, you should start seeing graphical issues, like:
* transparent News and Interests button
* white squares when browsing through the Start Menu (or completely white Start Menu)
* or flickering menu that opens after clicking on “Type here to search” and moving your mouse

Video: https://www.youtube.com/watch?v=QZ0pQqBiykE

Host GPU: Gigabyte GeForce GTX 960 Windforce OC 4GB DDR5/128bit DVI/HDMI/DP[[br]]
Host Driver Version: 528.24

I also would like to add that those issues are exclusive to VirtualBox 7. I didn't encounter them on VirtualBox 6.",przemo20
21443,VERR_HGCM_SERVICE_NOT_FOUND vbox 7.0.6,Linux,VirtualBox-7.0.6,2023-01-28T19:57:36Z,2023-02-10T09:58:56Z,2023-02-10T09:58:56Z,"After downloading the update for 7.0.6, installed over the top of my version 6. On completion, booted my Fedora guest.  Got to the login.  Entered credentials.  At this point I can only assume that it was connecting to resources and preparing audio and graphics for the desktop. One or two seconds after entering credentials, got an error message that the guest had crashed. The only options were to click OK to terminate the guest or to debug the guest.

Reverted back to 6.1.42, tweaked audio driver from WAS (not sure how that setting made it into the vbox file) to DirectSound (had to do this since it failed to add the guest due to driver error), booted the guest and was just fine.",Kronos1776
21475,TwinCAT conflict,other,VirtualBox-7.0.6,2023-02-08T09:28:46Z,2023-02-08T09:28:46Z,2023-02-08T09:28:46Z,"VirtualBox  doesnt start guest OS if TwinCAT software is running.
TwinCAT is known to exclusively occupy the virtualization capability of the HOST processor, however Virtual Machine is set not to use Para-virtualization interface or nested pages. 
",Arsham Atonyan
21462,vm crash,Windows,VirtualBox-7.0.6,2023-02-07T19:19:31Z,2023-02-07T19:19:31Z,2023-02-07T19:19:31Z,"Restoreing Snapshot crashing vm on vbox 7.0.6
image: Atlas 20H2 -> https://atlasos.net/downloads
",okoca
21455,Host with v7.0.6 seeing significantly higher cpu usage vs v6.1.40,Windows,VirtualBox-7.0.6,2023-02-03T01:26:40Z,2023-02-04T20:15:27Z,2023-02-04T20:15:27Z,"I just tested the latest version 7.06 running the same exact vm's. 20 vms in and it's already at 38% cpu.

I tried the same vm's again using v6.1.40 and I can run 40 vm's no problem while only using 18% cpu.

Host system

CPU: Dual EPYC 7742
Ram: 500G
Drive: U.3 SSD's


Windows 7 guest.
I'm running the 32-bit 4 wallets on each vm.
https://www.crypto-city.com/element-hyp/wallet/
https://www.crypto-city.com/truckcoin-trk/info
https://www.crypto-city.com/xra-rate-coin/info
https://www.crypto-city.com/bitflowers/wallet/",VirtualBoxFan
21447,VirtualBox 7.x + | DNS / Name resolution problem,Linux,VirtualBox-7.0.6,2023-01-30T14:20:10Z,2023-01-31T13:57:24Z,2023-01-31T13:57:24Z,"When trying to install a VM with Linux as guest OS under VirtualBox 7.x, the installation fails at the name resolution of the online repo.
This was tested with Debian and Arch Linux. 
The installation gives an error at the moment when the name resolution to the repo is needed.
To exclude an error in the images, Debian was installed from a full image, for this no online repo is necessary during the installation.
In the freshly started OS, however, the error of the non-existent name resolution occurs again, SSH via port forwarding does not work either.
A ping to ""google.de"" is unsuccessful. 
A ping to ""8.8.8.8"", is successful.
During the installation all default values of the installer were taken over.

'''When performing the same installations on VirtualBox 6.1.42, this error does not occur and the name resolution works, likewise SSH works without problems.'''

'''Host: Windows 10 Pro 22H2'''

'''Guest: Debian Stable Bullseye 11.6.0 (Kernel 5.10)
Arch Linux Rolling (Kernel 6.1)'''",carcap
21449,vboxautostartsvc config file issue with windows domain account,Linux,VirtualBox-7.0.6,2023-01-31T08:00:56Z,2023-01-31T08:00:56Z,2023-01-31T08:00:56Z,"Following the directions in documentation 2.21.4 Windows: Starting the Autostart Service, I have run into the issue where it is NOT accepting a domain account in the autostart configuration file.  I keep getting ""Unexpected token, expected '='"" error in the windows event log.  My domain user is ""raptor"" in the ""truck"" domain.  Permutations of domain\user, user@domain do not work.  It only works if default_policy=allow, which may be a huge risk.


Config file contains only the following:

{{{
default_policy=deny
raptor@truck={
allow=true
startup_delay=10
}
}}}


Looking at the code, I believe the issue is in src/vbox/frontends/vboxautostart/vboxautostartcfg.cpp in the static function autostartConfigTokenizerCreateToken where getting complete token is checking for RT_C_IS_ALNUM which does not allow for either the \ or the @ part of user name and domain since those are not in the alphanumeric range defined in vbox/include/iprt/ctype.h.",RobertV
21441,Drag and drop not working,Linux,VirtualBox-7.0.6,2023-01-28T14:49:43Z,2023-01-30T12:40:13Z,2023-01-30T12:40:13Z,"DnD not working between host (Win 11) and guest Ubuntu 22.04. 

Operazione di trascinamento e rilascio dal guest all'host non riuscita.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Codice uscita:VBOX_E_DND_ERROR (0X80BB0011)
Componente:GuestDnDSourceWrap
Interfaccia:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Chiamante:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}

",Dave78
21445,"Drag and Drop Host to Guest works, but not Guest to Host",Linux,VirtualBox-7.0.6,2023-01-29T22:47:42Z,2023-01-29T22:47:42Z,2023-01-29T22:47:42Z,"VirtualBox 7.0.6
Guest: Linux Mint 21.1 XFCE 64 bit
Host: Windows 11

I just did a fresh install of Linux Mint, but I am having some issues with the drag and drop.
I set the option to bidirectional. Dragging from host to guest works, but dragging from guest to host does not. Whenever I attempt to do the latter, one of two possible logs pops up.


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_IPE_UNINITIALIZED_STATUS).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


",Niobium62
21444,"Drag and Drop Host to Guest works, but not Guest to Host",Linux,VirtualBox-7.0.6,2023-01-29T22:47:36Z,2023-01-29T22:47:36Z,2023-01-29T22:47:36Z,"VirtualBox 7.0.6
Guest: Linux Mint 21.1 XFCE 64 bit
Host: Windows 11

I just did a fresh install of Linux Mint, but I am having some issues with the drag and drop.
I set the option to bidirectional. Dragging from host to guest works, but dragging from guest to host does not. Whenever I attempt to do the latter, one of two possible logs pops up.


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_IPE_UNINITIALIZED_STATUS).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


{{{
Drag and drop operation from guest to host failed.

DnD: Error: Requesting pending data from guest failed (VERR_TIMEOUT).

Result Code:VBOX_E_DND_ERROR (0X80BB0011)
Component:GuestDnDSourceWrap
Interface:IGuestDnDSource {dedfb5d9-4c1b-edf7-fdf3-c1be6827dc28}
Callee:IDnDSource {d23a9ca3-42da-c94b-8aec-21968e08355d}
}}}


",Niobium62
21437,Drag and Drop no longer works,Solaris,VirtualBox-7.0.6,2023-01-27T19:40:16Z,2023-01-27T19:40:16Z,2023-01-27T19:40:16Z,"Version 7.0.6 r155176 (Qt5.15.2)

The drag and drop between my widows laptop and Virtual Box no longer works
Pretty sure it work in previous version of 6.0+",pt519
21420,The create button is not showing when creating a new Virtual Machine.,Windows,VirtualBox-7.0.6,2023-01-21T07:03:24Z,2023-01-26T09:05:30Z,2023-01-26T09:05:30Z,"[[Image(X:/downloads/Screenshots/ss1.png)]]I have tried re-installing and tried other versions of Virtual box too, But I am not able to create a Virtual Machine :(.

can someone please help me with this

I am running Virtual box on Windows 11",tuglukbaba
21430,Ubuntu kernel panic on Windows 11,Linux,VirtualBox-7.0.6,2023-01-24T13:03:26Z,2023-01-24T13:03:26Z,2023-01-24T13:03:26Z,Trying to get the DVWA (Damn Vulnerable Web App) VM working in the current version of OVB running on a Windows 11 laptop.  Every time I tried to start the DVWA VM (an Ubuntu Linux VM) it crashed with a kernel panic.  When I downgraded from Windows 11 back to Windows 10 it started successfully.  ,Dr John Mc
21416,"If you have multiple LVM partitions for example on sda2 on Oracle 9.1 Linux Guest on Windows 10 Host, the cloned or exported VM will not boot properly",Linux,VirtualBox-7.0.6,2023-01-18T10:09:55Z,2023-01-18T10:09:55Z,2023-01-18T10:09:55Z,"Hello,

You replicate the problem like this:

1. Install a new VM from the Oracle 9.1 iso. 
2. Define just one disk and ensure it is very large e.g. 2TB. 
3. Ensure the default installation creates at least two LVM partitions:
    e.g. ol-root and ol-home on sda2
4. When cloned or exported/imported even to the same host machine, the resulting cloned VM will not boot properly, because only the first of the partitions is retained. In the example above, only ol-root is visible to the machine. ol-home disappears off the face of the earth.

As you can see the steps to replicate the problem is trivial. 

Thanks for your attention.

Cheers!

Yuet
",Yuet
