The simple rule is tp look for the word "Error" and use some common sense when finding it, as there may be false positives (errors that should be there). If it's not immediately obvious what's going wrong, then it's hard to tell for anyone who isn't somewhat familiar with the code. Best thing to do is upload the log to the forum or somewhere where one of us can look at it.
-bird On 2016-09-23 10:09 AM, Kalogrianitis Socratis wrote: > Is there a "procedure" for reading the VBoxHardening.log? I can't seem to > grasp the inner finer details. What strings should I be looking for? I've > learned that if uxtheme.dll shows up, that's a red flag. And a couple of > antivirus(es). But I'm afraid I don't fully understand how to decipher the > whole thing. Any thoughts? > > We're trying in the forums to help users to figure out why their VirtualBox > won't start, but unless we're educated, it's pretty much a guess game... > _______________________________________________ > vbox-dev mailing list > vbox-dev@virtualbox.org > https://www.virtualbox.org/mailman/listinfo/vbox-dev _______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev
