I get the same problem with build 14936. I agree that it started with build 14926 trying to update 14915.EricMCSE76 wrote:Starting with build 14926 - the appear to be 2 issues.
1) The issue referenced by Microsoft in their known issues that VirtualBox crashes - this is specific to running Virtualbox as a host on that build, not running that build as a guest
2) When running the 14926 (and the newly released 14931) build as a guest - you get a bunch of garbled white blocks on the startup screen. The guest reboots itself twice and then you get the options to go into safe mode, restore previous build, etc. This appears to be a graphics driver related issue. I have found that if you get into that state - don't revert back to the prior build. Power off the guest, go into the display settings for the guest and check the box to enable 3D Acceleration. After that, the guest runs just fine with builds 14926 and 14931. I suspect VirtualBox needs to update the display driver so it works correctly without the additional acceleration option.
There's some evidence suggesting that Windows / Windows Update doesn't like the Video Driver for VBox.
I've been able to install these builds only by making an .ISO of the appropriate .ESD file and doing a clean install on top of the old installation.
So long as the Windows Update program isn't involved, it seems we get a good "build" of the OS. However, this is a rather tedious process.
I'm pretty convinced that with build 14926, something changed in the Windows Video Driver area that made the Update program go crash. The only temporary workaround I've found is to go to advanced troubleshooting and choose reduced resolution (#3) and this allows a reasonable boot. Really clumsy though.
The 2D/3D Acceleration options don't help. In fact, I've found that the 3D Acceleration causes the boot process to stall; I had to kill the VM and get rid of the 3D option before I could manage any kind of boot.
I need to add that after doing the install and configuring things, I've installed Guest Additions for VBox 5.0.26 and the thing still runs. However, I seriously doubt that an update to the next Insider Build will work -- unless uninstalling the VBox Video Driver will cure the problem.