Can anyone explain the issue and how/why it is occurring?
I keep seeing more and more about the new 2016 models coming with this feature disabled. Is there any risks in checking into it on terminal and enabling it if necessary? If so is it better to enable it in terminal, or just performing a NVRAM reset? Any downsides to a NVRAM reset?
Or is it fine to disregard it entirely as Apple will likely fix it in an update anyway? Any info would be appreciated
I keep seeing more and more about the new 2016 models coming with this feature disabled. Is there any risks in checking into it on terminal and enabling it if necessary? If so is it better to enable it in terminal, or just performing a NVRAM reset? Any downsides to a NVRAM reset?
Or is it fine to disregard it entirely as Apple will likely fix it in an update anyway? Any info would be appreciated