Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
The only way to disable nvidia telemetry now is to delete the nvtelemetry.dll #19
The only way to disable nvidia telemetry now is to delete the nvtelemetry.dll, for example in the folder: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_547eeefb57db4499
if you do not delete this... then C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe will connect to *.gfe.nvidia.com
i used nvslimmer and clean installed only the display driver, nvidia telemetry was still attempting to connect; here is the strange pattern I found:
Without fail I am seeing the following reoccuring connections. NvidiaDisplayContainer.exe connects in intervals to to activation.gfe.nvidia.com, simultaneously ESET internet security connects to eset key activation servers. edf.eset.com points to a Microsoft Azure cloud server with a bad TLS cert, just visit: edf.eset.com or edfpcs.trafficmanager.net. The strange thing, is why does eset and nvidia always function in concert? hundreds of these every day:
Noted below: after deleting nvtelemetry.dll the following patterns changed dramatically.
After deleting nvtelemetry.dll eset queries were cut nearly in half. pico*.eset.com was no longer connected to, nor was activation.gfe.nvidia.com.