virtualbox.org

Hell,

For month now I've been using vBox on Windows 10 (host) for Wind 10 images. Everything was perfect. I even copied the VDI's on an ssd so it got much faster.

Until … yesterday morning.

I started up my Win 10 pc and ran vBox. All my win 10 machines crashed all at once. Slow like hell, untimely crashes and untimely reboots. I lost some of my snapshots … and even had to kill one of my vbox as it was totalled.

I tried re-installing a new Win10 vdi, took me a whole day to finish and the machine never got started. Killed it too.

The thing is that I did not do anything that could end up in creating this mess. Even today, I still cannot start a machine I finally got to work yesterday (after long efforts an patience of rebooting). I tried changing Core settings, memory, video … Helps only in my mind.

I must say I have an Lubuntu vBox which, so far, is still working fine.

Could Microsoft Updates on the host machine be responsible for this ?

If possible please help me.

Thanks.

Rmk : I checked, Hyper V is turned off !

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Thanks for your answer. I will try to get the log but the behavior is very erratic.

Sometimes it stucks on the boot so I see the Win blue squares and the circling dots frozen.
Sometimes It goes trough and when running suddenly somekind of top bar is graphically scrambled and the machine freezes or reboots.
Sometimes It jus reboots
and sometimes it seems to run but you never know for how long.

Here as I am typing I started one of the vbox and the login screen is like it was on two screens. Means that half of the screen is black the rest is half the login screen.

One thing is common to all this. When try to enter my password, the bitmap is flashing (in peaces) and I have to enter my password blindly most of the times. (I have no virus )

Since this morning I am trying to reinstall a new machine (Win 10 pro) and after 2ours I am at 3%)

There, it crashed. So you will get the log file.

Still no problem with Lubuntu and Win 98 (yes, I know !)

Thanks anyway for your concern.
F.

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Find the Command Prompt icon, right click it and choose Run As Administrator.

3. Enter this command:

bcdedit /set hypervisorlaunchtype off

4. Enter this command:

shutdown -s -t 2

5. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

If your Virtualbox does not start successfully, see I have a 64bit host, but can't install 64bit guests. The 64-bits tutorial has a couple more things to look for in step 2. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

Hello,

I did follow your advice and … it works !
well at least it seems it does !

Indeed there was that frog being now replaced by the 'V'.

When I started my computer on friday morning it launched the update (part of it was for defender). Could it be something in that update that set the parameter back on ?!
Must be as I did not, neither did I install anything …

Well, if you don't read anymore from me it'd be because it works.

Thanks for you fast and competent help.

Kind regards
F.

Glad you're up and running!