VBox Not working in Windows 10 Build 10525

[loukingjr]

As a software developer myself, I'm going to say that it is not impossible.

Sorry but any real "developer" would never make such a ridiculous claim. All one has to do is think about the hundreds if not thousands or tens of thousands of XP programs that can't run on current versions of Windows. Or versions of programs that no longer run on the platforms they were written for.

I've managed not to get frustrated over software problems. There is no point.

[Jacob Klein]

I'm not sure why you decided to personally attack me.

I'll continue to work around the problem, by setting up dual-boot, and waiting patiently for the developers to fix it.

[loukingjr]

I wasn't attacking you personally. You responded to my post, I responded back. Disagreeing with someone does not constitute a "personal attack".

[scottgus1]

Why Oh Why can't Virtualbox run on Windows 10 YET?!!

Two thoughts on this:

Ever notice how professional Major League Baseball batters have averages in the high .200's to the middle .300s? That means, basically, for every ten possible strike balls thrown over the plate, they can only hit two or three. Why? Because it's hard to hit a moving target. And they get paid millions to try.

Ever heard the demo version of a song that's already been played on the radio? Yuck! There's a lot of processing done to get the song (and singers - think Autotune) ready for market.

So Windows is throwing moving targets that are demos. Everyone who wants to run a Win10 host is going to just have to chill until the MS ball comes over the plate in exactly the same place every throw and with the same highly-polished pitch. Then Virtualbox will be able to hit it very time.

[loukingjr]

Just to add, users seem to be ignoring the fact that Windows 10 has had at least 4 cumulative updates to try and fix problems existing on metal and continues to try and address others. When Windows 10 is "perfect" then I will worry about VirtualBox running on it.

[Jacob Klein]

"Continuous improvements" is the new mantra for Microsoft and Windows.
Windows 10 was never going to be perfect, and will never be perfect, and will be continously "improved".

It's a new, rough, world for the VirtualBox dev team. An even rougher world for VirtualBox users on Insider Preview builds of Windows

[loukingjr]

Which is why I'm not running insider previews on my only Windows box. I am running build 10532 as a guest in VirtualBox on a few hosts.

[Arindrew]

VirtualBox-5.0.3-102467-Win also does not work on 10525. Tried with various "compatibility modes".

[Van88]

I test Version 5.0.2 and 5.0.3 on Windows 10 (Build 10532) it does not working!

[Jacob Klein]

VirtualBox 5.0.4 r102546 (released today), is actually opening on Windows 10 Build 10532.
I was expecting the devs to indicate that they'd checked in a fix for this issue, but that didn't happen I guess.

Anyway, I hope that 4.3.30/31 also get the fix, as I need to be using that version.
I'll continue to monitor.

[klaus]

The changelog of 5.0.4 mentions the fix. It's sometimes too much work to update all forum threads... tickets and changelog are what we try to do every time.

Regarding 4.3 updates: don't know when the next release will be, but once we get more confirmations it's likely that there will be a test build in the near future.

[Jacob Klein]

Thanks, for fixing it for 5.0.x, and also for communicating here!
Looking forward to testing a 4.31.x version, when it's ready.

[rseiler]

Thanks for fixing. I'm not sure how we went from no test builds working and no indication that anything was on the immediate horizon, to 5.0.4 working suddenly, but there you go.

[klaus]

We can only do test builds with a fix once we have it... when the "eureka" is only a few hours before the planned release build it can happen that there is no test build at all.

[Kalpesh]

Hello,

VirtualBox 5.0.5 Build 102614 working fine in Windows 10 Build 10532.