VM hanging on boot, appears to be tzres.dll STATUS_TRUST_FAILURE related

[AK6]

Running VirtualBox 6. 0. 18-136238 (but have also tried with version 6. 0. 14-133895 and had the same issue) on Windows 10 Enterprise Version 10. 0. 17763 build 17763. I am starting up a new Ubuntu 18. 04 image and it's getting stuck at "Freeing SMP alternatives memory: 36K"

Nothing out of the ordinary is appearing in the vbox. log, but the vboxhardening. log has this:

Code: Select all

1694. 3704: '\ Device \ HarddiskVolume3 \ Windows \ System32 \ tzres. dll' has no imports
1694. 3704: supHardenedWinVerifyImageByHandle: -> 22900 (\ Device \ HarddiskVolume3 \ Windows \ System32 \ tzres. dll)
1694. 3704: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume3\Windows\System32\tzres. dll
1694. 3704: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 00000000000012fc (hFile=00000000000012f4) with 0xc0000022 -> STATUS_TRUST_FAILURE
1694. 3704: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \ Device\HarddiskVolume3 \ Windows \ System32 \ tzres. dll [avoiding WinVerifyTrust]
1694. 3704: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 00000000000012f4 (hFile=00000000000012fc) with 0xc0000022 -> STATUS_TRUST_FAILURE

I tried the solution that was listed under the topic: "Hardening Fix (workaround) For Error After Install and Restart" (can't post the full link as this is my first post). I cannot get past this and am stuck. Appreciate any help.

[Ksad43]

18b0.4af0: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000001398 (hFile=000000000000139c) with 0xc0000022 -> STATUS_TRUST_FAILURE
18b0.4af0: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume6\Windows\System32\tzres.dll [avoiding WinVerifyTrust]
18b0.4af0: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 000000000000139c (hFile=0000000000001398) with 0xc0000022 -> STATUS_TRUST_FAILURE

I have the same issue on Windows 10 host and Windows 7 guest.

...and the same problem if I try Ubuntu guest on Win 10 host.

[scottgus1]

Please zip and post both the guest vbox.log and the hardening log.

[Ksad43]

Here are the logs of both Windows 7 and Ubuntu guest.

Ubuntu somehow manages to survive the STATUS_TRUST_FAILURE error, but it is very unstable, GUI becomes constantly unresponsive, black screens etc.

[scottgus1]

The Windows guest hardening log ends with exit code 0, so no hardening issues there. The Ubuntu hardening log is incomplete because it was taken while the guest Virtualbox window was open.

Both vbox.logs contain 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. Or it might guru-meditate. 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. See I have a 64bit host, but can't install 64bit guests. This tutorial has a couple more things to look for in step 2. Be sure these are all turned off.

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

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. 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, zip and post another vbox.log. For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

[Ksad43]

I tried:

1) Set Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard key "EnableVirtualizationBasedSecurity" to 0

2) I checked every other setting from the post "64 bit host, can't install 64bit guests". Every setting except the registry key in point (1) was already turned off.

3) I disabled antivirus and made a cold boot.

Noteworthy is perhaps, that when I connect to company's domain, registry key (1) gets turned on again. Plus antivirus turns itself back on. But no other virtualization related setting is re-enabled.

Nevertheless I performed the tests with virtual machines without connecting to company's domain and re-checked the virtualization registry and widows settings plus anti virus settings after each restart and everything was off. But nothing helped.

New logs are attached.

[scottgus1]

The log still has the tell-tale lines, your Hyper-V is still active.

I checked every other setting from the post "64 bit host, can't install 64bit guests".

There's a big one in there that fixes things for most folks, if corporate doesn't turn things back on again. I mentioned it above. Take a good look again.

I disabled antivirus

Sometimes a complete uninstall is necessary.

when I connect to company's domain, registry key (1) gets turned on again. Plus antivirus turns itself back on.

Sounds like corporate is undoing your efforts; you need to talk to your boss first. If you can make a case that your work suffers because you can't run Virtualbox, the boss could go to bat with IT for you to ease things up on your workstation.

[TerLaw]

I signed up here just to thank scott for his suggestion....man..been suffering for the past 2 weeks without a working VM with all my data on it. Followed your suggestions carefully, and the bcedit command worked

[scottgus1]

Thanks! But credit should go where it is due: Mpack and Socratis figured all that stuff out. They are the real gurus.