A_Alo wrote:I only can reconice this fail in log file
1) This is not a failure, this is the correct shutdown procedure and 2) you missed a couple of messages before that:
01:01:00.492445 VMMDev: Guest requests the VM to be turned off
01:01:00.493070 Changing the VM state from 'RUNNING' to 'POWERING_OFF'
What you're seeing is typical Win10 behavior, where after the OS does some updates, it reboots. Search around the webs for similar behavior...
Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS of the guest.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
OK, thanks
It´s very stranger, because when windows10 apply updates, it should advise previusly. And it usually shutdown itself several times throughout the morning, I´ll try to reinstall win10.
thanks for your support.
Have a nice day.
Regards Adrian.
A_Alo wrote:It´s very stranger, because when windows10 apply updates, it should advise previusly
Yeah, it should. But it doesn't. As I said, search the internet for documented similar behavior.
A_Alo wrote:I´ll try to reinstall win10.
You'll have to go through the same thing again. Reinstalling doesn't fix a fundamental flaw...
What you could do is to actively apply the updates when you know that you can afford to reboot your VM/computer.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.