VBox Not working in Windows 10 Build 10525

[Jacob Klein]

We get that 5.0.4 and 5.0.5 test builds, are currently starting up normally in Windows 10 Build 10525 and Build 10532.
I'm still checking every 4 hours, for an updated 4.3.31 test build that includes the fix. Remaining patient.

[Jacob Klein]

A new Windows build was released to the Windows Insiders group, Build 10547.

Oracle VirtualBox v4.3.31 Test Build 102328
... is still unable to open, even on Windows 10 Pro x64 Build 10547.
Exception code: 0xc0000005
Fault offset: 0x0000000000018a29

Oracle VirtualBox v5.0.5 Test Build 102676
... opens correctly.

Just reporting results, while waiting on that 4.3.x fix, as patiently as I can. (It has now been a month, since the problem was reported.)

Thanks,
Jacob

[Jacob Klein]

Just wanted to chime in again, with an update.

It appears that the 5.0.3/5.0.4 fix for Windows 10 Build 10525+, has NOT been backported to the 4.3.31 branch yet, even though we got a new 4.3.31 version today. I hope it does get backported at some point, but it sure would be nice to have developer clarification/confirmation that this is on some to-do list for 4.3.x.

Oracle VirtualBox v4.3.31 Test Build 102733
... is still unable to open on Windows 10 Pro x64 Build 10547.
Exception code: 0xc0000005
Fault offset: 0x0000000000018a29

Still waiting.

[klaus]

Since the "make VirtualBox work perfectly with Windows 10" task turns out to be far bigger than originally anticipated it currently looks that unconditionally backporting everything to 4.3.x will be too much effort, given the decreasing user count of 4.3.x. This means that if you plan to run VirtualBox on Windows 10 host with full functionality you shouldn't plan using 4.3.x. Some fixes will make it into 4.3.x, but it's not possible to guarantee anything (or promise that the backports will happen soon after some specific issue in 5.0.x has been fixed).

[Jacob Klein]

Thanks for replying.

I'm actually not needing "full functionality" on the 4.3.x branch -- I'm just wanting it to be able to run at all
It sounds like I might be waiting indefinitely on that, which is a bummer if that's the case.

For reference, I have BOINC VirtualBox tasks that use VBoxWrapper versions that are incompatible with VirtualBox 5.x, and I use Windows 10 (dual booting between Release partition and Insider partition). I'll continue to implement workarounds for your current incompatibility with the Insider build, and I think it'll be interesting whenever this Insider "Threshold 2" build is released to the public, in October/November.

I will continue to wait (on being able to use 4.3.x on 10525+), but unless I'm mistaken, you're saying "it's possible that you may be waiting indefinitely", even beyond the public release of this Windows 10 build. Dang. Oh well.

Thanks again for replying, and feel free to clarify anything I may have misconstrued.

[klaus]

The crash issue is something which likely gets backported, but there's no 4.3.x release planned for the next week or two (in a month the story might be different) and thus some backports are postponed.

[Jacob Klein]

I sincerely thank you, klaus, for the clarification.
Best of luck making things continue to work better on Windows 10.
-- Jacob

[Jacob Klein]

A new Windows build was released to the Windows Insiders group, Build 10565.

Oracle VirtualBox v4.3.31 Test Build 103278
... is still unable to open, on Windows 10 Pro x64 Build 10565.
Exception code: 0xc0000005
Fault offset: 0x0000000000018a29

Oracle VirtualBox v5.0.7 Test Build 103278
... opens correctly.

I continue to look forward to a possible v4.3.x startup fix.

Thanks,
Jacob

[Jacob Klein]

Oracle VirtualBox v4.3.32 Build 103443
... fixes the issue for me. VirtualBox 4.3.x can now open, without error, on Windows 10 Pro Insider Preview x64 Build 10565.

Thanks!!!
- Jacob

[horvan]

Name der fehlerhaften Anwendung: VirtualBox.exe, Version: 5.0.18.6667, Zeitstempel: 0x5714e21a
Name des fehlerhaften Moduls: VirtualBox.exe, Version: 5.0.18.6667, Zeitstempel: 0x5714e21a
Exeptioncode: 0xc0000005
Fauldoffset: 0x00000000000137e2
ID of fault Process: 0x2ea0
Starttime: 0x01d19e04c521526b
Path: D:\VirtualBox\VirtualBox.exe
Path of fault Module: D:\VirtualBox\VirtualBox.exe
Berichtskennung: fb661602-12ce-4545-8550-1f9802e28fd7
full Name of the fault package:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

[Jacob Klein]

Hello horvan,

We are tracking the Windows 10 Build 14328 startup issue, here:
viewtopic.php?uid=82061&f=38&t=77351

Please try not to resurrect old threads.

Thanks,
Jacob