Windows 10 upgrade issues.

[pepemonje]

Hi Everyone,

Yesterday I upgrade my window 7 machine to Windows 10. I had installed virtualbox with several VMs configured and working fine. After the upgrade, I was unable to run any of them anymore. I keep getting the same error message:

Failed to open a session for the virtual machine Xpenology.

The virtual machine 'Xpenology' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Usuario\VirtualBox VMs\Vorlagen\Xpenology\Logs\VBoxStartup.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

I've tried to uninstall and reinstall Virtualbox. Also with different versions. Deactivate firewall and antivirus. Non of this worked.
I would appreciate any help, I don't know what else I can do.

I attach the log file if it helps.

VBoxStartup.log

Log file.

(43.47 KiB) Downloaded 16 times

Thanks in advance.

Regards,

[Mitchboo]

I am also experiencing a big problem.

Do not know if it is related or not. Do not know if anybody here feels like helping. After being chastised for posting without searching first, and noting that none of the posts similar to mine seemed to have found even embryos of solutions, I doubt the description of the forums on the site holds true :

Forums. The VirtualBox forums are where the community can come together to help each other and to discuss VirtualBox. The forums should be your first port of call if you have problems using VirtualBox (or if you wish to help others solve problems!), since this frees up the developers' time for making VirtualBox even better.

In the hope anybody cares, here it is :

I have not been able to run Virtual Box 5 under Windows 10 64 bits build 10240. When I try to create a new VM for Windows 8.1 I, I get a box saying :

----------------------------------------------------------------------------------------------
NtCreateFile(\Device\VboxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries)

Driver is probably sttuck stopping/starting. Try 'sc.exe query vboxdrv' to get
more information about its state. rebooting may actually help. (rc=-101)

Make sure kernel module has been loaded successfully.

[Abort]
----------------------------------------------------------------------------------------------

So I did sc and here is the result :

Code: Select all

SERVIC_NAME : vboxdrv
TYPE                : 1 KERNEL_DRIVER
STATE              : 4 RUNNING
                             (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
 

All this sounds Martian, unless it is Endorian, or even Klingon ?

I have used VirtualBox for quite a while, and it usually works out of the box (virtual of course .

Would all that mean that simply VB5 is not compatible with the brand new Windows 10 ? When will a fix be available ?

TIA

[Thoranx]

I have the exact same error ending with the same line in my log file. Hopefully someone can help us out.

[pepemonje]

Hi,

I finally decide to do a fresh install of windows 10. Backed up my VMs and reinstall Virtualbox.
Everything is working now. Anyway, I couldn't figure out what was the issue with the update.

Thanks.

[p060477]

Hi,

I finally decide to do a fresh install of windows 10. Backed up my VMs and reinstall Virtualbox.
Everything is working now. Anyway, I couldn't figure out what was the issue with the update.

Thanks.

really hope that VB dev's really do not make us do this ..solving the issue between VB and win 10
on the VB side

[mpack]

really hope that VB dev's really do not make us do this

Make you do what? Backing up your VMs is something you should be doing as a matter of course, if they have value.

[p060477]

really hope that VB dev's really do not make us do this

Make you do what? Backing up your VMs is something you should be doing as a matter of course, if they have value.

i was talking about this:
"I finally decide to do a fresh install of windows 10"...
just win has been able not to force us to format our pc and to do e new complete win 10 install and
so we really hope that VB dev's do not force us to do that..i repeat we really do not want to be forced to
format our pc's..
but we hope VB dev's solve the issues FROM VB side...

[BillG]

If something went wrong during the upgrade and something is not working properly, the logical thing to do is to do a system reset or a system reinstall. You can spend days or weeks fiddling about trying to fix it (or hoping that somebody else will) and end up finally admitting defeat.