VM doesn't start / Black screen

[moasti2D]

Hi,

I've got problem when I want to start VM.

29e4.3668: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume2\Windows\System32\tzres.dll
29e4.3668: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 0000000000000408 (hFile=00000000000011b8) with 0xc0000022 -> STATUS_TRUST_FAILURE
29e4.3668: supR3HardenedScreenImage/NtCreateSection: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume2\Windows\System32\tzres.dll [avoiding WinVerifyTrust]
29e4.3668: supR3HardenedMonitor_NtCreateSection: NtMapViewOfSection failed on 00000000000011b8 (hFile=0000000000000408) with 0xc0000022 -> STATUS_TRUST_FAILURE

See log for further information.

Thanks for you reply.

[socratis]

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Remember, these are guidelines, not the exact solution, you have to use your judgement as to which program might be responsible...

2cfc.1cbc: supR3HardenedWinFindAdversaries: 0x2
2cfc.1cbc: \SystemRoot\System32\drivers\symevent64x86.sys:
...
2cfc.1cbc:     FileDescription: Symantec Event Library

I'd start with completely uninstalling all Symantec related programs.

[BossEmcee]

Resurrecting this thread because I found no valid answers to this issue online. This error is likely a red herring and should not stop a boot. The problem could be as simple as the VM is configured too aggressively for your machine. Try lowering the number of cores / base memory to no more than 75% of your PCs physical limits. This seems obvious but with more teams using automation tools to set up environments, such settings can be buried in config files. In my case, the default vagrant file that I had used to instantiate the VM assumed I had a supercomputer.

[mpack]

Don't disturb the dead. Start your own topic.

I'm locking this one.