Hardening error on Dell model 5490 - Windows 10 - Enterprise x64 - 1809
12 views
Skip to first unread message
Jeff Dey
Jul 31, 2019, 10:04:37 AM7/31/19
to Vagrant
We are installing Windows 10 Build 1809 Enterprise from a DVD, completly offline. Once done, VirtualBox 6.0.10 is installed from a USB key, and Vagrant to run the box Hashicorp/Precise64 as a proof of concept. We constantly get an hardening error on Dell 5490. Tested with 4 different laptop, all the same Dell 5490 model.
There is no other software installed. No antivirus, no Hyper-V enabled.
Pretty sure that all the settings of the BIOS have been flipped on and off again. We had this setup working only 1 time on a Dell 5490, and it didn't last the afternoon before getting the same hardening error.
If I use a factory fresh Dell 5490, keeping the Windows 10 "home" version and all the softwares that comes with it, it works.
On another model of computer, a not-a-Dell but a custom build PC, this setup work flawlessly.
At this point, we spent about 3 weeks of works to find the issue. I should have asked on forums before, but here we are. At the moment, I've wipped out one the laptop, and doing again a fresh install of this setup to get logs and screens captures of the issue. I'll be able to provide them later.
Any ideas?
There is no other software installed. No antivirus, no Hyper-V enabled.
Pretty sure that all the settings of the BIOS have been flipped on and off again. We had this setup working only 1 time on a Dell 5490, and it didn't last the afternoon before getting the same hardening error.
If I use a factory fresh Dell 5490, keeping the Windows 10 "home" version and all the softwares that comes with it, it works.
On another model of computer, a not-a-Dell but a custom build PC, this setup work flawlessly.
At this point, we spent about 3 weeks of works to find the issue. I should have asked on forums before, but here we are. At the moment, I've wipped out one the laptop, and doing again a fresh install of this setup to get logs and screens captures of the issue. I'll be able to provide them later.
Any ideas?
Jim McGinness
Jul 31, 2019, 3:31:57 PM7/31/19
to Vagrant
I'm not sure what you mean by a "hardening error".
One thing I've run into is that the virtualization support is normally turned off in laptops' BIOS as the factory default. But you say you've installed vbox and run a VM under it without Vagrant being present, so that doesn't sound like the issue here.
Jeff Dey
Aug 1, 2019, 11:21:34 AM8/1/19
to Vagrant
We've found the solution yesterday, thanks to this post: https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios
Running the Readiness tool, and disabling the Application Guard, the Credential Guard and Device Guard did the trick.
https://www.microsoft.com/en-us/download/details.aspx?id=53337
We also disabled the Core Isolation trought a registry edit, since the GUI seems buggy in Windows 10 - 1809:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
Enabled DWORD = 0
HVCIMATRequired DWORD = 0
Locked DWORD = 0
Running the Readiness tool, and disabling the Application Guard, the Credential Guard and Device Guard did the trick.
https://www.microsoft.com/en-us/download/details.aspx?id=53337
We also disabled the Core Isolation trought a registry edit, since the GUI seems buggy in Windows 10 - 1809:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
Enabled DWORD = 0
HVCIMATRequired DWORD = 0
Locked DWORD = 0
Jim McGinness
Aug 1, 2019, 1:27:14 PM8/1/19
to Vagrant
My usual response when something this many layers deep is "what a world we've made", but I think most of us have no part of this complexity. Good that you found a solution and even better that it's posted here for others to find.
Reply all
Reply to author
Forward
0 new messages