virtualbox.org

Hi,

I'm on windows 10 host machine, I've a problem with an ubuntu guest machine.

What do you think ?

Neither of the logs you provided is very useful. Both seem to have been copied out while the program was still running, and the files not flushed and closed.

I do see that the wrong extension pack is installed, and is the Ubuntu guest really 32bit as the chosen template suggests?

Hi,

You can find the log after I closed the VM:
- The first log ( hardening.log vbox.log ) is a total freezing machine.
- the second log ( hardening2.log vbox2.log ) is a cpu lock.

Thank you again !

In the hardening file, I found:

2224.3620: NtOpenDirectoryObject failed on \Driver: 0xc0000022
35d0.24ac: supR3HardenedWinReSpawn: NtSetInformationThread/ThreadHideFromDebugger failed: 0xc0000022 (harmless)
34e0.1d04: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000b24 (hFile=0000000000000c7c) with 0xc0000022 -> STATUS_TRUST_FAILURE
34e0.1d04: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\tzres.dll [avoiding WinVerifyTrust]
34e0.1d04: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000c7c (hFile=0000000000000b24) with 0xc0000022 -> STATUS_TRUST_FAILURE
34e0.1d04: supR3HardNtViCallWinVerifyTrustCatFile: hFile=0000000000000d98 pwszName=\Device\HarddiskVolume2\Windows\System32\tzres.dll

What do you think ?

You still have the wrong extension pack installed. You also have not answered the question I asked: is the guest OS is really 32bit?

The hardening log ends with an error code of 0, meaning you do not have a hardening problem. You do have superfluous third party AV installed, so I would not call your PC healthy.

p.s. I don't need two copies of every log. One relevant log is enough.

p.p.s. I don't understand what you mean by "total freezing machine" and "cpu lock". Neither are terms that are familiar to me. Both sound like they may mean the same thing: a hang. If you are saying that the host hangs then that IMO would indicate a problem with host hardware. The only problem with that theory is that I see no indication of either a host or guest lockup in the log. The first log shows the VM running for 140 hours before being closed normally, at user request.

Yes it's a 32 bit guest machine.
It's the guest that is hanging.
Is it a problem the error : STATUS_TRUST_FAILURE

mickae1 wrote: Is it a problem the error : STATUS_TRUST_FAILURE

As I said, the hardening log ends with a code of 0, which indicates that the trust failure is not a problem. Plus the part of the log that you quoted tells you that the error is harmless.

Plus, I looked for "tzres.dll" on my own PC, and found that it isn't signed at all, though it seems to be a genuine Microsoft DLL. I'm assuming that means it's a 32bit DLL (only 64bit DLLs are conventionally signed).