Hi
@esafeddie and everyone interested. Clearing up, or rather resetting critical NVRAM variables can also be accomplished during every opsys restart/reboot with the config.plist entries as per the attached screenshot This obviates the need for NVRAM resets and ensures system wide consistency of the contents of these variables, at least as far as macOS is concerned.
This measure is particularly useful if you multi-boot, as I do, with Linux as part of the selection options in your boot picker. Linux does it's own thing, outside the influence of the OpenCore boot loader, and populates some of these variables with its own values, a disaster when you then return from Linux to macOS, which all of a sudden finds an environment it cannot comfortably live in, thus introducing instabilities and all sorts of other unwanted macOS behavior.
The method works as follows:
NVRAM-->Delete
When booting the contents of the selected NVRAM variables ( placeholders)
first get deleted, without bothering what values are actually present within them, valid or not.
NVRAM-->Add
Thereafter the values that are assigned to each respective NVRAM variable actually gets stuffed into it's corresponding host (placeholder) thereby ensuring what is in there does not originate from some obscure process or opsys.
We are dealing with UEFI booting here, with the NVRAM variables mostly adhering to a globally universal naming convention throughout, hence the possibility that they can get overwritten quite easily without you ever being aware of it, other than the consequences that manifest itself in inexplicable weird behavior.
Enjoy or destroy.
Greetings Henties
-