VBox Not working in Windows 10 Build 10525

[Kalpesh]

Hello,

VirtualBox is not working in Windows 10 Build 10525

Error Log:
Faulting application name: VBoxSDL.exe, version: 5.0.3.2217, time stamp: 0x55d43118
Faulting module name: VBoxSDL.exe, version: 5.0.3.2217, time stamp: 0x55d43118
Exception code: 0xc0000005
Fault offset: 0x0000000000018d29
Faulting process id: 0x1900
Faulting application start time: 0x01d0da8ddc58fdbb
Faulting application path: C:\Program Files\Oracle\VirtualBox\VBoxSDL.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VBoxSDL.exe
Report Id: 8606c92c-173f-44cb-8653-c66155b29a07
Faulting package full name:
Faulting package-relative application ID:

[klaus]

Only the crash is new. VBoxSDL has been broken for so long on 64 bit Windows without anyone complaining that we considered completely removing it...

[Kalpesh]

now i am getting below crash

Faulting application name: VirtualBox.exe, version: 5.0.3.2217, time stamp: 0x55d43119
Faulting module name: VirtualBox.exe, version: 5.0.3.2217, time stamp: 0x55d43119
Exception code: 0xc0000005
Fault offset: 0x0000000000018f29
Faulting process id: 0xbb0
Faulting application start time: 0x01d0da945205bcf8
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: c1b9e7da-6af2-45cb-b7b1-442420c845d8
Faulting package full name:
Faulting package-relative application ID:

[rseiler]

From the previous thread:

For as far as it works for anyone else...
I simply changed the compatibility mode to Windows 7 for the virtualbox manager, this at least gets it to run with the least flaws, but i have to start the clients from within the VB manager.

I've tried setting compatibility on that one and other key files, since that can be an easy cheat out of problems like this for any number of programs, but no luck. Anyone else?

[Kalpesh]

I tried compatibility "Windows 7/8" setting but its not working.

[Jacob Klein]

Windows 10 x64 Build 10525 - Can't open VirtualBox

I wanted to inform the community, and the Oracle developers, that VirtualBox can't currently be opened on this build of Windows 10. I realize that this build of Windows 10 is an Insider Preview. And I'm not complaining about VirtualBox not working, even though it is frustrating. This post is meant to be informative, and to request that it be fixed when time allows, before Windows 10 Threshold 2 is released to the public.

If you need anything else, please don't hesitate to ask. I look forward to this being resolved.

Thanks,
Jacob Klein

Oracle VirtualBox fails on:
- Windows 10 x64 Build 10525
- Oracle VirtualBox v4.3.31 Test Build 101940 (I can't yet use/test v5, for different reasons).

Relevant Error info (from Event Viewer):
Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Level: Error
Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x55c1e4a1
Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x55c1e4a1
Exception code: 0xc0000005
Fault offset: 0x0000000000018a29

Fault bucket 120301926489, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: VirtualBox.exe
P2: 0.0.0.0
P3: 55c1e4a1
P4: VirtualBox.exe
P5: 0.0.0.0
P6: 55c1e4a1
P7: c0000005
P8: 0000000000018a29
P9:
P10:

My intent is to reply to my post, as new VirtualBox builds are released, to indicate if they helped at all.

Thanks,
Jacob Klein

[Omnomnom]

Same here on VBox 5.0.3:

Faulting application name: VirtualBox.exe, version: 5.0.3.2224, time stamp: 0x55d4a0cd
Faulting module name: VirtualBox.exe, version: 5.0.3.2224, time stamp: 0x55d4a0cd
Exception code: 0xc0000005
Fault offset: 0x0000000000018f29
Faulting process id: 0xa74
Faulting application start time: 0x01d0daab238c9108
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: ff5233b5-208b-4da9-94b7-3ed0a3d47697
Faulting package full name:
Faulting package-relative application ID:

[coderus]

Omg, i just upgraded to 10525 build and it stopped working for me also. Downgrading is not an option. How the hell this may happen with such product as VirtualBox?

[Omnomnom]

I just backed out 10525, and VBox is working fine again. I'll think long and hard about loading another preview release of windows on my main machine.

[necros2014]

vbox 5.0.3 102290 - no gui after start (win 10 10525 x64)

[marcthin]

I have the same experiant Virt.box dies after klicking on the icon; I also revert to the RTM build 10250 and Virt.Box works with some hickups bit it works.
For mee no previous build from windows for the time being!

Regards
Marcthin

[regs]

Chrome's fix for their crash on 10525. Could be related.
https://codereview.chromium.org/1308563 ... lver_64.cc

[Glover]

I'm also having the issue (10525). Looks like it could be something to do with the new Memory Manager? I'm just spit balling ideas at the moment

[Jacob Klein]

It is an Access Violation (0xc0000005), and Oracle could pretty-easily determine where it's happening. Fault offset values have been provided by users, and they could also step through a debug build. We just have to wait for their dev team to deem it a priority.

In the meantime, I've created dual-booting partitions for all of my hosts --- A "Windows 10 Pro x64 Release" partition, and a "Windows 10 Pro x64 Insider" partition. And, if I need to use anything with VirtualBox, I make sure I'm in the "Release" partition.

VirtualBox's code is the only application, out of all my applications, that doesn't work right on the Windows 10 Insider build.
I hope they can get it fixed.

[Jacob Klein]

Just wanted to chime in, with a couple more VirtualBox builds that are still broken, not able to open, on Windows 10 Pro x64 Build 10525.

Oracle VirtualBox v4.3.31 Test Build 102328
Exception code: 0xc0000005
Fault offset: 0x0000000000018a29

Oracle VirtualBox v5.0.3 Test Build 102322
Exception code: 0xc0000005
Fault offset: 0x0000000000018fa9