pdorsch
1 Nickel

Cannot enable credential guard on Latitude E5270

Hi,


using Windows 10 Enterprise with DELL Latitude E5270

I have the issue that i can´t enable DG/CG because of

HSTI validation failed

and

InCompatible HVCI Kernel Driver Modules found

Module: stdcfltn.sys
        Reason: execute pool type count:                2
Module: savonaccess.sys
        Reason: execute pool type count:          4574455
Module: swi_callout.sys
        Reason: execute pool type count:              143
Module: e1d65x64.sys
        Reason: execute page mapping count:             4

I already checked for the latest patch KB3213522 updated bios and drivers, so i could remove the  Airplane mode switch driver issue which was also listed. i had to reinstall the Networkdrivers to remove e1d65x64.sys

and now i´m left with these 2

InCompatible HVCI Kernel Driver Modules found

Module: stdcfltn.sys
        Reason: execute pool type count:                2
Module: savonaccess.sys
        Reason: execute pool type count:            60688

stdcfltn.sys is from the disk "SK hynix SC308 SATA 256GB" but i can´t find anything i could install

and i don´t know what savonaccess.sys is

en.community.dell.com/.../20963932

0 Kudos
4 Replies
pdorsch
1 Nickel

RE: Cannot enable credential guard on Latitude E5270

savonacces.sys is from Sophos On-Access Scanning

0 Kudos
pdorsch
1 Nickel

RE: Cannot enable credential guard on Latitude E5270

any tips for HSTI "validation failed"?

0 Kudos
pdorsch
1 Nickel

RE: Cannot enable credential guard on Latitude E5270

More Information from MS:

msdn.microsoft.com/.../mt712332.aspx

But still no solution

0 Kudos
pdorsch
1 Nickel

RE: Cannot enable credential guard on Latitude E5270

Dell Support:

[..]

thank you for your request.

please contact Mirosoft for solved the problem.

Thants no Hardware problem from Dell System.

[..]

After quite some days, I just recieved an answer from dell to my HSTI validation error on an DELL Latitude E5270. it was escalated inhouse and there will be a Bios-Update in mid-april adressing that issue...

0 Kudos