Jump to content

[HOW TO] OpenCore 0.7.0 > 0.7.1 differences

2 posts in this topic

Recommended Posts

Posted (edited)

Please read the message from @vit9696 with the best summary you can read about what's new in OpenCore 0.7.1.


This time we may think that we are facing a minor OpenCore update because we have to learn and modify an affordable number of features. Nothing comparable to June's update. However this is not entirely true. What happens is that the 0.7.0 update was huge, much more complex than usual.


This 0.7.1 update may seem simple compared to the previous one but it does not stop having important changes:

  • more than 60 builds have been released
  • some bugs have been fixed
  • documentation has been improved (adding debug docs updates)
  • OpenCanopy continues to receive improvements
  • builtin firmware versions have been updated
  • PCI device info dumping has been added to SysReport
  • new kext patcher for Lilu, supporting macOS from 10.6 to 12
  • For Monterey:
    OpenCore and kexts have been adapted to macOS 12 Monterey
    added BlueToolFixup to fix Bluetooth issues on macOS 12
  • For Windows 11:
    added a document containing requirements and potential paths to work around them
    added TpmInfo.efi tool to check TPM status.




ACPI > Quirks > added SyncTableIds (boolean): to sync table OEM identifiers with the SLIC table to prevent licensing issues in older Windows operating systems. It can be False.


Kernel > Scheme > added CustomKernel(boolean): to support custom kernels from the Kernels directory located at the root of the ESP partition. For unsupported platforms including Atom and AMD that require modified versions of XNU kernel in order to boot. It can be False.




  • Fixed transparency click detection on OpenCanopy boot entries for the icon to be selected when clicking on the transparent areas. Note for artists: transparent areas of icons can have opacity=1% to ensure correct operation, although in theory it is not necessary with this OpenCanopy enhancement.
  • Added recommended Apple12 and Windows11 flavours.
  • Fixed various bugs.
  • Improved documentation.




TpmInfo.efi: to check Intel TPM capability on the platform, which allows using TPM 2.0 if enabled. The tool does not check whether TPM 2.0 is actually enabled or disabled. TpmInfo must be run from the UEFI Shell, if it is run from the picker it shows a text message so short that it is impossible to read what it says.




Fix path length calculation and remove the wrong check for Misc > Entries > Path and Misc > Boot > PickerVariant. Sometimes ocvalidate showed an error message (path too long) even if it did not exceed 128 bytes. As per ocvalidate's Readme: "All the paths relative to OpenCore root must be 128 bytes total".




It's recommendable to update kexts to the new versions:

  • AirportBrcmFixup
  • AppleALC
  • BrcmPatchRAM
  • CPUFriend
  • IntelMausi
  • Lilu
  • NVMeFix
  • RestrictEvents
  • SidecarFixup
  • VirtualSMC
  • VoodooPS2
  • WhateverGreen.


Edited by miliuco
  • Like 8
  • Thanks 6
Posted (edited)

Note about TPM


The integration of TpmInfo.efi in OpenCore 0.7.1 has an obvious reason in the Windows 11 release that requires TPM to be installed. In some BIOSes TPM option is not found and PTT option does appear, both are equivalent but it is worth explaining how they differ.



Last word in securing personal computers and servers has been the Trusted Platform Module (TPM) specification,  a technology designed to provide security features.
TPM is a chip designed to perform cryptographic operations that includes several physical security mechanisms that make it resistant to alterations. It has specific security features to prevent malicious software from altering your system.
TPM is built into the CPU. If your computer has a processor from the last 6 years it is almost certain that it has a TPM.
In BIOS this option is usually in Advanced > Trusted computing or something similar. It can be TPM enable (auto) or disable.


Intel introduced a change, Intel Platform Trust Technology (PTT) architecture, which implements TPM in system firmware so computers with Intel PTT don't require a dedicated CPU. To your operating system, PTT looks and acts like TPM.
PTT is being deployed on low-power PCs, tablets and other devices that in the past could not bear the additional cost, complexity or other requirements demanded by hardware-based TPM.

So in BIOS you can have TPM or PTT, depending on the hardware manufacturer.

Edited by miliuco
  • Like 2
  • Thanks 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...