Page 1 of 1
issue starting vm
Posted: 23. Sep 2021, 00:52
by Iwanoff
Exactly the same error, up to:
"{85632c68-b5bb-4316-a900-5eb28d3413df}"
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Renaming did not give anything, and there are no specified characters in these files.
What else could be the problem?
Re: issue starting vm
Posted: 23. Sep 2021, 03:47
by scottgus1
Please post the exact text of the error. Use the Copy button in the error box if it is there.
Re: issue starting vm
Posted: 23. Sep 2021, 11:59
by Iwanoff
"Не удалось открыть сессию для виртуальной машины WinXP_Yu.
The virtual machine 'WinXP_Yu' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\IRA\VirtualBox VMs\WinXP_Yu\Logs\VBoxHardening.log'.
Код ошибки: E_FAIL (0x80004005)
Компонент: MachineWrap
Интерфейс: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}"
Thank you for your feedback!
Re: issue starting vm
Posted: 24. Sep 2021, 01:07
by scottgus1
Thanks for the log. Zipping is definitely ok and recommended.
Hardening has an exit code of 1. wintrust.dll has trouble along the way, but I can't tell if it was resolved. crypt32.dll has an unresolved error. The software causing the error doesn't show in the log, which does happen sometimes.
See
Diagnosing VirtualBox Hardening Issues, posts 3 & 4. Look for 3rd-party web-safe-browsing software, Trusteer Rapport, other such ilk.
Also, Windows 7 is no longer a supported host OS for Virtualbox 6.1.x. Try 6.0.x or 5.2.x.