This post is more than 5 years old

3 Posts

5241

May 9th, 2017 07:00

Version 1.13.3, 1.13.3 Bios for Latitude 5570 causing BITLOCKER issues

Imagining multiple laptops, yesterday bios Version 1.13.3, 1.13.3 came out. Started it into our rotation.

Afterwards bitlocker was no longer able to start "internal issue". Tried to revert back to old and still same issue even after re-image it. All TPM and secure boot options correct. Also have done: Imaged laptop, let bitlocker encrypt, suspended it, updated bios, after restart bitlocker didnt resume, tried to force it and prompted with internal error again.

May 16th, 2017 03:00

Yes, I've just tested it and the problem appears to be solved in BIOS version 1.14.4.

May 10th, 2017 09:00

I have the same problem on latitude e5470U

8 new laptop have the same issue.

Tried to reset the bios, downgrade, clear, reinstall windows.

May 10th, 2017 09:00

same problem on 4 laptop here.

trying to downgrade the bios, clear the tpm, reset the bios, reinstall the computer.

" internal error has been detecting "

3 Posts

May 10th, 2017 15:00

Ended up having to clear the TPM, downgrade it (found in the security portion for drivers and downloads) remove MBAM, then was finally able to encrypt correctly.

Was able to make it work on bios version 1.12 and 1.13*

May 10th, 2017 15:00

I'm having precisely the same problem, except I've tried downgrading the BIOS (to 1.12.6) and doing a full CMOS reset, and the problem's still there.

Has anyone heard anything officially from Dell about this?

3 Posts

May 10th, 2017 15:00

It does seem they pulled the latest bios version from the driver and downloads section.

May 10th, 2017 16:00

I am having the same issue

Latitude E5570

BIOS 1.13.3

UEFI Enabled

Secureboot Enabled

Legacy Boot Disabled

TPM Firmware 2.0

MDT fails with "ProtectKeyWithTPM" and Windows reports "internal error" when attempting to Bitlock

May 16th, 2017 03:00

no news from dell ?

May 16th, 2017 03:00

New bios online i test it !

May 16th, 2017 04:00

good for me too !

6 Posts

May 17th, 2017 10:00

they pulled 1.13.3 because it bricked two E5570, had to replace the boards

No Events found!

Top