VirtualBox/4.3.20 no longer starts on Windows 10

[kAlvaro]

I was using Windows 8 and I hadn't launched VirtualBox for a while, then I upgraded to Windows 10 and I've just discovered that it won't even start. I've read the "Windows 10 is not officially supported yet" notices and posts but most people seem to have only minor issues. Is my problem related to that?

Code: Select all

VirtualBox COM Server 4.3.20 r96997 win.amd64 (Nov 24 2014 11:05:59) release log
00:00:00.003001 main     Log opened 2015-09-03T19:31:18.945298700Z
00:00:00.003001 main     Build Type: release
00:00:00.003001 main     OS Product: Unknown NT v10.0
00:00:00.003001 main     OS Release: 10.0.10240
00:00:00.003001 main     OS Service Pack: 
00:00:00.016001 main     DMI Product Name: System Product Name
00:00:00.024001 main     DMI Product Version: System Version
00:00:00.024001 main     Host RAM: 8134MB total, 4175MB available
00:00:00.024001 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.024001 main     Process ID: 5308
00:00:00.024001 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.026001          Loading settings file "C:\Users\alvaro/.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.075886          failed to get the sun_VBoxNetFlt component, error (0x1)
00:00:00.104889          HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.104889          DNS server 1: 62.81.16.213
00:00:00.104889          DNS server 2: 62.81.16.148
00:00:00.170891          VDInit finished
00:00:00.171892          Loading settings file "D:\Servidores\VirtualBox\Machines\Windows\Windows 7 Ultimate 64bits\Windows 7 Ultimate 64bits.vbox" with version "1.13-windows"
00:00:00.172891          Loading settings file "D:\Servidores\VirtualBox\Machines\Windows\Window XP - Cacharreos\Window XP - Cacharreos.vbox" with version "1.13-windows"
00:00:00.173891          Loading settings file "D:\Servidores\VirtualBox\Machines\Windows\Window XP - Plantilla\Window XP - Plantilla.vbox" with version "1.13-windows"
00:00:00.174891          Loading settings file "D:\Servidores\VirtualBox\Machines\Windows\Zanzibar3\Zanzibar3.vbox" with version "1.14-windows"
00:00:00.175891          Loading settings file "D:\Servidores\VirtualBox\Machines\Window XP - Legacy\Window XP - Legacy.vbox" with version "1.13-windows"
00:00:11.993545 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'D:\Servidores\VirtualBox\Machines\Windows\Windows 7 Ultimate 64bits\Windows 7 Ultimate 64bits.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:11.993545 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'D:\Servidores\VirtualBox\Machines\Windows\Window XP - Cacharreos\Window XP - Cacharreos.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:11.994546 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'D:\Servidores\VirtualBox\Machines\Windows\Window XP - Plantilla\Window XP - Plantilla.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:11.994546 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'D:\Servidores\VirtualBox\Machines\Windows\Zanzibar3\Zanzibar3.VHD' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:11.994546 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'D:\Servidores\VirtualBox\Machines\Window XP - Legacy\Window XP - Legacy.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:11.998547 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={fafa4e17-1ee2-4905-a10e-fe7c18bf5554} aComponent={VirtualBox} aText={The object is not ready}, preserve=false

[frank]

VBox 4.3.20 will most likely not run on Windows 10. You have to upgrade at least to VBox 5.0.2, better use a test build as linked on the download page. If you are using Windows 10 >= 10240 then you need to wait even longer for a solution.

[Giusi]

If you are using Windows 10 >= 10240 then you need to wait even longer for a solution.

you mean that the solution will come,whenever it will be,
first for the win 10 release stable build 10240
and then after for the win 10 insider previews latest builds am i wrong?

[kAlvaro]

VBox 4.3.20 will most likely not run on Windows 10. You have to upgrade at least to VBox 5.0.2, better use a test build as linked on the download page. If you are using Windows 10 >= 10240 then you need to wait even longer for a solution.

Thank you very much. I can confirm that with latest snapshot (5.0.3 r102467) VirtualBox Administrator finally starts in my 10240 Windows build.

I've also tried a couple of virtual machines and not only do they start but they don't suffer from issues that are immediately obvious.