Recent content by didz

SGX was depreciated due to security flaws and was not included in the lga 1700 core processor line up. From what I read, "OS usually expects BIOS to set certain bits in MSR_IA32_FEATURE_CONTROL for some features (e.g. VMX and LMCE)." You said "MSR_FEATURE_CONTROL doesn't seem to be capable of...

Ok, but System Guard is not loading, which depends on TXT/SMX. Theoretically if the bit was disabled in the bios, windows should still load SMX? Are those features on top of SMX necessary for it to function properly? Can you name those features?

As noteted above, HWINFO (and coreinfo64) state SMX (aka TXT) is enabled, the latter at least says is 'capable'. However, windows event viewer states "Event 220, System Guard enabled but not supported. Reason: TXT is disabled by the BIOS in MSR_FEATURE_CONTROL." How can it be disabled in the...

Appears you are right, perhaps after enabling HVCI windows does a hellufa job to ensure it can't be bypassed. I ran hwinfo inside hirens boot cd, which is based on a windows 10 x64 pe environment, bypassing windows hvci, which allows to detect these hidden features. Does green signify they are...

No, because I reiterate, when I disable virtualization based security, (and secure boot) under "services running" it shows none running.

Msinfo states, security available: base virtualization support, secure boot, dma protection, secure memory overite, uefi code readonly, smm security mitigations 1.0, mode based execution control, apic virtualization services running 'credential guard, hypervisor enforced code integrity...

Appears that this turns out to not be true. Turns out Hyper-V was already disabled in optional features. So, I disabled "Windows Hypervisor Platform" instead, all device guard features via group policy, and secure boot, and the result is the same. Bcdedit hypervisorlaunchtype is also set to the...

Look in the screenshot, says HVCI disabled. I disabled secureboot. That shuts down HVCI. Its installed as an optional feature, but not active... windows system information and hwinfo both say disabled. I'll disable everything regardless when I have the time just to confirm what actually happens.

Why is this happening?

Ok Martin, I tried with HVCI disabled, and yet the result is the same, hwinfo isn't detecting VMX, which is enabled in the bios. How do we go about rectifying this issue?

Thank you Martin. Is this the same for SMX? And I notice TME is also shown to be supported and enabled... is this certain? Unfortunately there is no option for this in the bios...

Using the latest stable version. Why do you think its not showing enabled here? You can see it is enabled in bios... So its either a HWINFO bug, or a bios bug... how do we get to the bottom of this? Update: i do have hyper-v / core isolation enabled, could this cause it?