Main VirtualBox UI crashes on startup on Windows 10 preview build 10525

[davefiddes]

My PC remains parts of the Windows 10 Insider Program after upgrading. It recently update to Build 10525 which is the first public post RTM build of Windows 10.

I am finding that VirtualBox 5.0.2 and 5.0.3 build 102322 all crash on start up. I've removed and reinstalled the software to no avail (it appears to install cleanly). My user .VirtualBox\VBoxSVC.log is not updated at all.

I can't find a way of getting test build PDB symbols but WinDbg reports the following back trace:

FAULTING_IP: 
VirtualBox+18fa9
00007ff6`e0b18fa9 8a042511000000  mov     al,byte ptr [11h]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ff6e0b18fa9 (VirtualBox+0x0000000000018fa9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000011
Attempt to read from address 0000000000000011

FAULTING_THREAD:  0000000000003798

PROCESS_NAME:  VirtualBox.exe

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 00007ff8bbe00000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP:  55dbadef

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000011

READ_ADDRESS:  0000000000000011 

FOLLOWUP_IP: 
VirtualBox+18fa9
00007ff6`e0b18fa9 8a042511000000  mov     al,byte ptr [11h]

MOD_LIST: <ANALYSIS/>

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_READ_WRONG_SYMBOLS

PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_DEREFERENCE

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 00007ff6e0b199c7 to 00007ff6e0b18fa9

STACK_TEXT:  
00000000`0028f000 00007ff6`e0b199c7 : 00007ff6`e0bd26c0 00007ff6`e0bd26e0 00007ff8`bbe91fd0 00000000`00000000 : VirtualBox+0x18fa9
00000000`0028f060 00007ff6`e0b07a84 : 00007ff6`e0bdd190 00000000`00000003 00000000`01ca6040 00000000`003c0028 : VirtualBox+0x199c7
00000000`0028f100 00007ff8`bbd63b52 : 00000000`00000000 00000000`00000000 00007ff6`e0b07a60 00000000`00000000 : VirtualBox+0x7a84
00000000`0028f960 00007ff8`bbe6a6f4 : 00007ff8`bbd63b30 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x22
00000000`0028f990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34

[nimda]

VirtualBox 5.0.51(test build for Windows 10)

fails to start after the fresh install

on Windows10Home Insider Preview Build 10525

Windows10 Event Viewer output:

Faulting application name: VirtualBox.exe, version: 5.0.51.2346, time stamp: 0x55dc4bec Faulting module name: VirtualBox.exe, version: 5.0.51.2346, time stamp: 0x55dc4bec Exception code: 0xc0000005 Fault offset: 0x0000000000018fa9 Faulting process id: 0x1b38 Faulting application start time: 0x01d0e0da27b3bab7 Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Report Id: 8c30ac3d-41b8-4292-a692-2abca120e855 Faulting package full name: Faulting package-relative application ID:

[Frank Mehnert]

Hopefully fixed with VBox 5.0.4.