PS: NVIDIA Web Driver installer repacking is not needed ever since NVIDIA introduced “experimental Mac Book Pro and i Mac support”.I assume, that your EFI application works in a similar way as my driver, doesn’t it?

Apple requires a special Developer ID:“Kext signing requires a special Developer ID Application signing identity with the custom extension with OID 1.2.840.113635.

You can see this in Keychain Access if it’s present.

Right now this procedure is an extremely simple way to avoid system update dependent (automatic) rerunning of the script.

BTW: The exact same technique to force loading the NVIDIA driver, though it is not natively qualified for PCI tunneling, should work to inject the needed modifications into the Apple Graphics Device as well as any ATI/AMD driver.

coz my local h/w s/w dealers does not know anything about it.

WMI is Windows Management Instrumentation, which is an interface through which Windows components can provide information and notifications to each other, often between remote computers (more info about WMI).We use WMI in most of our wizards, such as ‘Create Cluster Wizard’, ‘Validate a Configuration Wizard’, and ‘Add Node Wizard’, so any of the following messages and warnings we list could be due to WMI issues: If you continue to see errors after checking that WMI is running, the firewall is properly configured and rebooting, it is possible that your WMI repository has become corrupt so the cluster can no longer read from it. This was confirmed with the 10.12.3 and 10.12.4 to 10.12.5 update as well as various NVIDIA driver updates. If it does not work after upgrading try running the following command in terminal (it might help, maybe): Helping me out: Some weeks ago my Mac Book Pro has been stolen.The kext generation itself could even be automated using a script, as the kext actually does not include any code itself. (Apart of one try which was not accelerated, but which I lost after adding additional modifications and which I did not backup.) However it IS possible somehow.The pro side of this injection technique obviously is, that it is persistent across reboot, with the only letdown right now, that disabling SIP (partially) is still required.Hello again, Do either of your methods allow for use without an external monitor?