Why VirtualBox is broken so often in Windows 10

[horvan]

Dear VirtualBox Dev-Team/Commuinty

As a Windows Insider using Microsoft’s fast rig It's a pain to see how often VirtuialBox is broken after Microsoft makes an update to his System. While Virtualbox runs by Chance every 4. or 5. Update VMware for example does its Job consistently regardless of any updates. Because this is about virtualization Software and both are using almost the same techniques in General this must be an allowed question.

Why Virtual-Box is marked as Incompatible Software after every update by Microsoft and VM-Ware works like a Charm altough Microsoft pushes an update?

Is there anything we can do agiainst it? I have the last Test Build here and Windows 14328_16048_1609

The Virtual-Box gui does not come up since I updated to the last build. This Problem occures from time to time Last time it was solved by installing the last test build by now the current test buld doesn’t Show anything when starting virtual box

Please be free to move this Topic elsewhere. I am loookimng Forward to see what makes it so difficult.

Here are some event-protocol data

viewtopic.php?f=38&t=69672&p=360190#p360190

[klaus]

VirtualBox is checks its runtime environment extremely carefully for the possible presence of malware which could abuse its privileges. Looks like Microsoft is making a lot of changes with Windows 10 (after making very few changes during the last 10 years) in security sensitive areas. Unfortunately every such change can upset the sanity checks in VirtualBox. Before you ask: no, the checks can't be optionally disabled, as otherwise malware would do that, too.

I can't speculate what VMware does (or does not do) to make them more compatible. It's closed source software, and we don't know how it works internally.

[mpack]

It would probably also help if you avoid bleeding edge Win10 insider releases: you can either have stability or bleeding edge, having both is not possible.

[michaln]

It's not even clear if Microsoft is making more changes. The difference is that with the previous development model, users would see version N and then version N+1, with nothing in between. Software had to be adapted for the new version and then everything was stable for a few years. With Insider builds that is no longer the case and users see every intermediate development stage. So instead of adapting software for a new Windows version once, it has to be done incrementally all the time. It's really much more like the Linux development model.

Whether it's better or worse is something that users have to decide for themselves.

[horvan]

These are great replies at all Thank you!

[klaus]

The breakage which triggered the original post should be resolved by the current Test build for 5.0.