VM failed to start, hardening related

[Chrony]

Same thing happened to me today after Windows 11 update:

Captura de tela 2024-04-10 095222.png (9.14 KiB) Viewed 846 times

VBoxHardening.log

(186.22 KiB) Downloaded 4 times

[klaus]

Looks like some AV software is interfering with VirtualBox... could you try creating an exception or disable the AV software temporarily?

[Chrony]

I disabled WIndows Defender, but the same error occurred.

VBoxHardening.log

(185.17 KiB) Downloaded 4 times

[klaus]

Windows Defender is never patching executable code in-memory (otherwise 98% of the Windows users would report trouble). There must be something else...

[Chrony]

There is simply nothing left... I have been using this VM for over 5 years and today, exactly today, after the Windows 11 update it stopped working... Which is causing me serious problems.

[multiOS]

@Chrony

The Logs you have provided are truncated, so may be missing some important clues which often come near the very end of a complete Log. You should always 'zip' Logs to ensure they remain within the Forum's upload limits.

If this error happened immediately after a Host Windows Update it might also be useful to provide the latest VBox.Log for a failed startup.

[Chrony]

Attached are the compressed logs.

Logs.zip

(174.69 KiB) Downloaded 2 times

[granada29]

@Chrony
There is a problem with your VirtualBox installation. You are running a rather old version of the package (VirtualBox 7.0.6) but more importantly the Extension Pack is a totally different version.

Code: Select all

00:00:06.889871   Oracle VM VirtualBox Extension Pack (Version: 6.1.40 r154048; VRDE Module: VBoxVRDP; Crypto Module:  unusable because of 'VBoxExtPackVMRegister returned VERR_VERSION_MISMATCH, pReg=0000000000000000 ErrInfo='Helper version mismatch - expected 0x30000 got 0x50000'')

I suggest you update both VirtualBox and the Extension Pack to the current release, 7.0.14, and try again. Download both from https://www.virtualbox.org/wiki/Downloads

[Chrony]

Nothing...

Captura de tela 2024-04-11 110619.jpg (48.48 KiB) Viewed 636 times

Captura de tela 2024-04-11 110642.png (22.44 KiB) Viewed 636 times

Captura de tela 2024-04-11 110707.png (14.37 KiB) Viewed 636 times

[Chrony]

Logs.zip

(175.77 KiB) Downloaded 3 times

[granada29]

These logs are not generated by your current VirtualBox installation - they seem identical to ones you posted previously.

Code: Select all

00:00:06.793367 VirtualBox VM 7.0.6 r155176 win.amd64 (Jan 11 2023 16:38:38) release log
00:00:06.793369 Log opened 2024-04-05T10:45:48.184871100Z

[Chrony]

Only VBoxHardening.log is changed, VBox.log has no changes since yesterday.

Captura de tela 2024-04-11 170845.jpg (32.72 KiB) Viewed 569 times

[fth0]

Please see my section about "Damaged installation of the Microsoft Visual C++ Runtime" in Re: Diagnosing VirtualBox Hardening Issues.

---

These logs are not generated by your current VirtualBox installation - they seem identical to ones you posted previously.

That's because the abort takes place before the VBox.log file is written.

[Chrony]

Thank you very much! My problem was solved by downloading vcruntime140_1.dll and copying it to windows/system32