itman 1,790 Posted December 16, 2018 Share Posted December 16, 2018 (edited) Just upgraded to Win 10 x(64) 1809 Home yesterday. Seeing this in my Win Event Kernel-Boot log: Measured Boot library encountered a failure and entered insecure state. InitState: 1, StatusCode: 0xC0000001, Failure Address: 0x945657, Reference Address: 0xA4E840, Reason: 1. As far as I am aware of, measured boot relates to loading of Windows Defender or third party AV ELAM driver. Edited December 16, 2018 by itman Link to comment Share on other sites More sharing options...
Administrators Marcos 5,407 Posted December 16, 2018 Administrators Share Posted December 16, 2018 ESET's EELAM driver doesn't load during system startup. I assume that uninstalling ESET would not make any difference with regard to the error. I was able to find only one report of this issue, however, it's not clear what actually fixed it for the user: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/measured-boot-library-encountered-a-failure-and/b3b41312-abb3-4ea0-9a7b-17c1a2ed5506. Link to comment Share on other sites More sharing options...
itman 1,790 Posted December 17, 2018 Author Share Posted December 17, 2018 59 minutes ago, Marcos said: was able to find only one report of this issue, however, it's not clear what actually fixed it for the user: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/measured-boot-library-encountered-a-failure-and/b3b41312-abb3-4ea0-9a7b-17c1a2ed5506. Yeah, saw that previously. Ran the bcdboot command and it didn't make any difference. Further research yields: Quote Secure Boot and Measured Boot are only possible on PCs with UEFI 2.3.1 and a TPM chip. Fortunately, all Windows 10 PCs that meet Windows Hardware Compatibility Program requirements have these components, and many PCs designed for earlier versions of Windows have them as well. https://docs.microsoft.com/en-us/windows/security/information-protection/secure-the-windows-10-boot-process My PC motherboard has a BIOS and it doesn't have a TPM chip. So chalk this one up to the "never ending" 1809 snafus. At least it doesn't appear to bork the boot processing. Link to comment Share on other sites More sharing options...
Recommended Posts