Hardening error

[Ken S]

Running Win 11 Host, Win 19 guest, Beta 2

Yesterday I tried to load VBox, and received a hardening error, and that I should reinstall VBox.

I closed that dialog box and retried VBox and all was ok.

Which log should I send? When I right click and Show Log there are Development VM2, VBox.log, VBoxHardening.log, VBox.log.1, 2 and 3.

Ken

[mpack]

If you received a hardening error then the error dialog told you to to include "VBoxHardening.log", though it's rather obvious really.

To save time you should include VBox.log in the same zip - i.e. the one you put the hardening log into. Attach the zip here.

[Ken S]

Attached

[mpack]

Superfluous third party AV detected (Malwarebytes).

IMO, Windows 8 and beyond do not need third party help. And before that the best option was no AV at all (the risk was always overblown by those with a vested interest in selling you snake oil fixes).

[klaus]

Looks like your AV software (Malwarebytes) is manipulating the content of the VM process, making it differ from the expected content in e.g. the resources section. It's really annoying that some AV software still thinks that behaving like malware is a way to protect.

[Ken S]

Thanks, I have removed Malwarebytes.

[fth0]

If removing the Malwarebytes software(s) solved your issue, please provide a new (zipped) VBoxHardening.log file nonetheless.

Background reason: In the previous days, I've seen similar manipulations reported in VBoxHardening.log files of VirtualBox 7.0.0 in other threads, where they probably didn't play a role in the reported issues.

[Ken S]

File attached.

I cannot say removing MalwareBytes solved my issue. I have been running VBox for some time with no issue. That one time I received that error, I reran Vbox and all was well. A day or two later, I removed Malwarebytes. VBox continues to run without error. It certainly is not an "always" error.

Thanks
Ken

[fth0]

Thanks for the explanations and the log file, but the latter isn't the file I've been asking for.

[Ken S]

I have done this several times this morning ... what am I doing wrong? Right click VM name, select Show Log, tab control appears, with 6 tabs, click on tab for VBoxHardening.log, click Save .... and it saves another tab, VBox log.1.

Attached is I hope the file shown as VBoxHardening.log (obtained by clicking VBox.log.1 and clicking Save)



Ken

[fth0]

I don't know what's going wrong either.

This time, the file x.log is a VBoxHardening.log file, but it's identical to the Development VM 2-2022-10-09-19-34-10.log file you provided 3 days ago. Don't bother, it's not that important.