Virtual Box 6.0.20 Error when running VM

[matboro1]

Hi,
I have problem in VirtualBox 6.0.20 - I was updating and removed and reinstalled. My OS is Win 10

I create new VM and I starting with installing OS I have this communique
CODE: SELECT ALL EXPAND VIEW
The virtual machine 'aaaaa' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Boro\Documents\VM\aaaaa\Logs\VBoxHardening.log'.

Code: Select all

Kod wyniku (RC):
E_FAIL (0x80004005)
Komponent:
MachineWrap
Interfejs:
IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

I have a log in attachment
VM_log.txt

[scottgus1]

The hardening log is not complete, it appears to be the end of the log. Zip the whole log, and post the zip file, using the forum's Upload Attachment tab.

[matboro1]

Hi,
I sending logs in zip file

[scottgus1]

OK, thanks for the complete log!

As I read it, there is a problem with opengl32.dll.
The ExitCode=0x1, according to Diagnosing VirtualBox Hardening Issues means corruption of a file (possible) or other "nanny" software (the log doesn't report any that I see).

Looks like an sfc /scannow in an admin command prompt is needed, or a video driver update?

[matboro1]

Ok,
I repaired according to WIN Support ---> use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system ---> sfc /scannow show a

Code: Select all

Windows Resource Protection found corrupt files but was unable to fix some of them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag.

so I started looking

Code: Select all

Cannot 
repair member file [l:34{17}]"Accessibility.dll" of Accessibility, Version = 

and not found in logs, in logs I see

Code: Select all

2020-04-28 21:29:43, Info CSI 00000238 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

IMO I have to OS format

I manualy updating video driver ---> error still exists ;(