Hi there,
Could anyone please shed some light on why I'm seeing the following error message and offer a solution?
Hardening log not included as too large to upload.
Hardening error
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hardening error
It will upload if zipped, and we will need it, please. Use the forum's Upload Attachment tab to post the zip file.cgs1 wrote:Hardening log not included as too large to upload.
Re: Hardening error
Thank you,
Attached below
Attached below
- Attachments
-
- hardening.zip
- (12.22 KiB) Downloaded 19 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hardening error
Your hardening log has an exit code of 0x1 and about a couple hundredn of these:
IBM's workaround
IBM's solution
a script to implement IBM's solution
Or run Trusteer Rapport in a guest, not on the host.
Virtualbox problem with Trusteer Rapport9dc.b2c: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status -23021 (0xffffa613)) on \Device\HarddiskVolume2\Program Files (x86)\Trusteer\Rapport\bin\x64\rooksbas_x64.dll [lacks WinVerifyTrust]
IBM's workaround
IBM's solution
a script to implement IBM's solution
Or run Trusteer Rapport in a guest, not on the host.
Re: Hardening error
Thank you kindly, good sir!
altering the registry files does indeed seem to have cured the hardening error.
Unfortunately, though the VM now launches, opening in a window, it almost immediately closes, leaving me with the following error message:
Failed to open a session for the virtual machine Stakis Technik 2017.3.
The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Are you able to assist with this error also?
BR,
Craig
altering the registry files does indeed seem to have cured the hardening error.
Unfortunately, though the VM now launches, opening in a window, it almost immediately closes, leaving me with the following error message:
Failed to open a session for the virtual machine Stakis Technik 2017.3.
The native API dll was not found (C:\Windows\system32\WinHvPlatform.dll) (VERR_NEM_NOT_AVAILABLE).
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Are you able to assist with this error also?
BR,
Craig
Re: Hardening error
Attached are current log files.
Also worth mentioning, I became aware of this after updating from Ver5.2.22 to ver6.0 (subsequently updated to 6.1) - Running on Win7 64 host.
With that said, I hadn't used the VM for a while before updating, so it may be due to another update.
Also worth mentioning, I became aware of this after updating from Ver5.2.22 to ver6.0 (subsequently updated to 6.1) - Running on Win7 64 host.
With that said, I hadn't used the VM for a while before updating, so it may be due to another update.
- Attachments
-
- Logs.zip
- (80.76 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hardening error
This latest log shows you are running Virtualbox 6.1.0
The error:
"AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)."
means that the AMD virtualization technology switch in your computer's BIOS is turned off.
Up until 6.1.0, guests like yours, with one core and 32-bits, could run with the virtualization switch turned off in the BIOS.
Starting with 6.1.0, this no-virtualization capability has been removed. If you want to run 6.1.x & later you'll have to find that BIOS switch (Google can help you, probably) and turn it on, even for this 1-core 32-bit guest.
If you can't find the switch or the BIOS doesn't have it (some manufacturers didn't put it in) then you'll have to downgrade to 6.0.x or earlier again.
The error:
"AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)."
means that the AMD virtualization technology switch in your computer's BIOS is turned off.
Up until 6.1.0, guests like yours, with one core and 32-bits, could run with the virtualization switch turned off in the BIOS.
Starting with 6.1.0, this no-virtualization capability has been removed. If you want to run 6.1.x & later you'll have to find that BIOS switch (Google can help you, probably) and turn it on, even for this 1-core 32-bit guest.
If you can't find the switch or the BIOS doesn't have it (some manufacturers didn't put it in) then you'll have to downgrade to 6.0.x or earlier again.
Re: Hardening error
Scottgus,
Just rolled back to 5.2.22 (still had the install file available). All working fine now.
As my needs from this software are basic at best, I think i'll just stick with what works for now.
If not, i'll have a nose around in the BIOS and enable virtualisation.
Thank you for your help, you are a gentleman and a scholar! Think I owe you a beer!
All the best,
Craig
Just rolled back to 5.2.22 (still had the install file available). All working fine now.
As my needs from this software are basic at best, I think i'll just stick with what works for now.
If not, i'll have a nose around in the BIOS and enable virtualisation.
Thank you for your help, you are a gentleman and a scholar! Think I owe you a beer!
All the best,
Craig
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Hardening error
Glad to help, Craig!
Coca-Cola would do just fine.
Coca-Cola would do just fine.