This sounds like something is botched seriously in your setup, and it's not restricted to VirtualBox. I think you need to concentrate on the problem outside of the scope of VirtualBox...computer_guy wrote:I also found another issue related to this, when I went tos save log in my documents it gave error "The path does not exist or is not readable" so i had to save in one of 3 'accessible' folders like my Downloads
Yeap, in order to get "the" log, you need to run the VM and observe the error, so that it gets recorded in the log. We don't want to see a random log, from a random run, with random settings. We want to see a log where/when the problem shows in the logs.computer_guy wrote:My mistake, didn't realize I would need to start up VM after installing correct version.
For example, this log (after you re-run the VM) shows that you are actually running the official VirtualBox:
VirtualBox VM 5.2.10 r122088 linux.amd64 (Apr 13 2018 20:42:29) release log