[ModEdit; Partial VBoxHardening.log removed. It didn't even contain the ExitCode!]Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Error message
-
- Posts: 12
- Joined: 9. Jan 2010, 02:14
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: XP SP3
Error message
What to do about this ?
Last edited by socratis on 3. Apr 2019, 03:00, edited 1 time in total.
Reason: Removed partial log.
Reason: Removed partial log.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error message
First of all, that's not the complete error message, that's part of it. Please post the complete error, not what you think might be appropriate/important.
Same thing goes for the VBoxHardening.log. You can't post chunks of it and expect a diagnosis. Do you do the same with a doctor, only tell them half of the symptoms?
If the error is a hardening one, 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.
We could potentially give you a suggestion or two if you posted a complete, ZIPPED VBoxHardening.log and we see signs of known applications.
Same thing goes for the VBoxHardening.log. You can't post chunks of it and expect a diagnosis. Do you do the same with a doctor, only tell them half of the symptoms?
If the error is a hardening one, 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.
We could potentially give you a suggestion or two if you posted a complete, ZIPPED VBoxHardening.log and we see signs of known applications.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 12
- Joined: 9. Jan 2010, 02:14
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: XP SP3
Re: Error message
Here is the hardening log
- Attachments
-
- VBoxHardening.zip
- (18.01 KiB) Downloaded 43 times
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Error message
Despite your log showing this...
-Andy.
...your VBoxHardening.log appears to be terminating successfully...2c7c.2ba8: supR3HardenedWinFindAdversaries: 0x80 2c7c.2ba8: \SystemRoot\System32\drivers\MBAMSwissArmy.sys: 2c7c.2ba8: ProductName: Malwarebytes SwissArmy
I think we also need the VBox.log for the guest (assuming it got far enough to create it).bb8.1ce4: Terminating the normal way: rcExit=0 2a28.26b8: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 4423 ms, the end); 2c7c.2ba8: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 5148 ms, the end);
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Error message
You are attempting to run a macOS guest (aka a Hackintosh) under a Windows 10 host on non-Apple hardware. This is not supported and is also a violation of Apple's End User License Agreement (EULA). More details can be found at: Important notice regarding Mac OS X as Guest.VBox.log wrote:VirtualBox VM 5.2.26 r128414 win.amd64 (Jan 25 2019 18:59:02) release log 00:00:02.075741 OS Product: Windows 10 00:00:02.075742 OS Release: 10.0.17763v 00:00:02.117866 DMI Product Name: To be filled by O.E.M. 00:00:02.121413 DMI Product Version: To be filled by O.E.M. ... 00:00:02.227207 Guest OS type: 'MacOS' 00:00:02.236876 File system of 'E:\- Virtualbox Images\macOS Sierra 10.12 by wikigain.vmdk' is ntfs
Had you searched around the forums you would have seen that there are many similar threads all of which end up in the same state - locked and consigned to oblivion. Yours will be sent the same way the next time a site admin / mod passes by.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error message
Moving to "OSX Guests" from "Windows Hosts".
Unfortunately, that OSX Guests area is starting to look like a locksmith's warehouse...
Unfortunately, that OSX Guests area is starting to look like a locksmith's warehouse...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.