VirtualBox 4.3.38 not runs on Win10 (host) after Win-Update KB3176929

[arilou]

Before Windows 10 update KB3176929, VirtualBox 4.3.38 was running with no problems. Now it doesn't open GUI anymore, just finishes. Also "repair" or "uninstall/install" of VB don't fix the problem, also uninstalling the Win10 update has no effect. Starting VB with admin-rights doesn't either.

VB 4.3.38 is the latest version that supports Win98 guest, AND can be installed on Win10 (host). So I can't use VB 5.x instead. (There are no VMWare or MS VirtualPC versions that provide Win10-Install AND stable Win98-guest, so there is no alternative way ~ afaik.)

Windows Error Report/Event log:

Source: Application Error
Event-ID: 1000
categorie: (100)
Name of error application: VirtualBox.exe, Version: 0.0.0.0, timestamp: 0x57167a8a
Name of error module: VirtualBox.exe, Version: 0.0.0.0, timestamp: 0x57167a8a
error code: 0xc0000005
error offset: 0x0000000000016b02
ID of error process: 0x13c0
path to error application: C:\Program Files\VirtualBox\VirtualBox.exe
path to error module: C:\Program Files\VirtualBox\VirtualBox.exe

(VB does not return an errorlevel to command prompt (errorlevel=0).)

[Socratis]

Replying to arilou:

VB 4.3.38 is the latest version that supports Win98 guest, AND can be installed on Win10 (host). So I can't use VB 5.x instead.

I've been running all the 5.x.x series since the betas. I'm now at development version 5.1.3 build 109780. I can run Windows 98 just fine... (well except that it crashes and burns with the SoundBlaster16 enabled, but that's another issue).

And I'm not so sure that 4.3.x supports Windows 10 as a host. In fact the User Manual for 4.3.38 goes up to Windows 8 (not even 8.1, but it may support it) and Server 2012. In any event, it can't keep up with the ever changing Windows 10, so, I think you should consider upgrading.

[degree]

I've the same issue. VB 4.3.38 and lower doesn't start in Windows 10 Anniversary Update 14393.10 build.

I have to use 4.3.x, because of Sailfish SDK. It doesn't work with 5.x versions on Windows.

Windows Error Report/Event log:

Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x559faaf3

Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x559faaf3

Exception code: 0xc0000005

Fault offset: 0x0000000000019512

Faulting process id: 0x4744

Faulting application start time: 0x01d1f63e5d8677c8

Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe

Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe

Report Id: 3bab1b33-6417-4cd3-879c-b4f829dc66e4

Faulting package full name:

Faulting package-relative application ID:

[Socratis]

@degree: If you have a working system, you should be always aware that it might break if something gets updated. So, your Windows update broke your system (I know it's difficult to avoid the updates, but it is doable). If that Sailfish SDK is so important to your work, you should have kept the computer from modifying its state, even stay away from the network altogether.

The "not supported" status for 4.3.x means that:

• If it works, it works. Great.
• If it doesn't, no extra work is going to be invested by the developers to make it work. Not that they might not. But the chances are they won't.