ERROR TO OPEN VB

[alaz]

I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB:

"Error in supR3HardNtChildWaitFor Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles). Plea try reinstallin VirtualBox. where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)"

So I tried to reinstal but it's the same error.

What's happening???

[alaz]

I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB: "Error in supR3HardNtChildWaitFor Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles). Plea try reinstallin VirtualBox. where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)" So I tried to reinstal but it's the same error. What's happening???

When I close this window, another one open:

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Andre_2\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'. Código de Resultado: E_FAIL (0x80004005) Componente: MachineWrap Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

[alaz]

I AM RECEIVING THIS MESSAGE, EVERY TIME i TRY TO RUN VB: "Error in supR3HardNtChildWaitFor Timed out after 2001 md waiting for child request #0 (PurifyChildAndCloseHandles). Plea try reinstallin VirtualBox. where: supR3HardNtChildWaitFor what: 5 Unknown Status 258 (0x102) (258) - Unknown Status 258 (0x102)" So I tried to reinstal but it's the same error.

What's happening???

When I close this window, another one open: The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Andre_2\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'. Código de Resultado: E_FAIL (0x80004005) Componente: MachineWrap Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

[Socratis]

You can always edit your posts, you don't have to post the same information 3 times...

It's usually better and faster, if issues get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Please read really carefully the following FAQ: ​Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement...

If you still have a problem after reading through the whole thing, please head to the ​forums, and open a new thread. Please be sure to mention that you came from the bug tracker and include the ticket number.