Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by cryohellinc, Jun 5, 2018.
Good to know thx for the reply
signed up just to ask, in the "clean" version of the driver provided here, a file "NVtelemetry64.dll" still exists in the "driver" directory, is this file verified to be harmless on its own?
In that case, Welcome to the forum!
Some other components rely on it, but file by itself is harmless. DisplayDriverRAS.dll on the other hand actually sends stuff.
As of late Nvidia has integrated some of the telemetry components into the core driver itself, so just fully "removing" them as it used to be by deleting them is now impossible (unless there was some new development that I missed out on).
Nevertheless, there is a workaround that works and breaks the telemetry chain resulting in no data being sent out.
The above method is not included in the clean driver (for now). But takes like 10 seconds to implement manually.
thanks for the welcome, and the info was most useful!
I was actually plotting on how to bypass this too, my first idea was to edit the inf file but windows complained it had been tampered with when i tried to install, feels like that is a protection system working backwards allowing undesirable software in.
my second idea was a little different though, I think it is technically a 'clean bypass? I was simply going to use windows firewall to block outgoing requests from NVtelemetry64.dll I guess I should block DisplayDriverRAS.dll instead, or just block outgoing network access to all dll files that came as part of the driver (it's the only way to be sure?)
it should work right ? could maybe even be integrated to the clean driver somehow as part of the install? thought I may just end up doing the dirty install, I like the idea of that dll not even existing on my drive so long as the drives work fine and don't flag me a hack/cheater or anything with what few games i do play
I have been using the workaround method with a dummy file for quite some time now across all my devices including work pc, without any issues at all. Try it out and let me know how it works for you.
The reason as to why I haven't implemented this method into the clean drivers yet is lack of testing - a dozen of people are hardy a sample group big enough to assure that everything works just fine. So please by all means - give some feedback in the end.
I had issues using a dummy "Windows couldn't find the file specified" but I didn't try blocking with windows firewall, what I did do was install the clean driver as per normal (without a dummy file)
navigate over to the driverstore folder where the driver is installed which would be ...
then simply deleted both NV_telemetry and DisplayDriverRAS, limited testing (restarting, clicking around the desktop, playing media etc) shown no errors so far.
one thing though is the entries for the removed dll files still exist in the registry and can't be removed, maybe they also do when using dummy files method too?
would be interested to know if searching the registery for DisplayDriverRAS.dll with the dummy file method turns up anything?
Technically, all the strings that point to RAS dll and registry entries will still be there.
However, they will not do anything, as all of the instructions that were within the .dll are not present.
Odd that you had this Windows warning. At what stage did it pop up?
durin driver installation,clicked on my existing generic display in device manager, clicked update driver and pointed it to the clean driver location, with a dummy file it gave that error but with the original files it installed fine
either way it is ruing without telemetry now which probably wouldnt have bee able to figure out on my own so I am happy, thanks
Why not use DDU prior to installation and afterwards simply installing a clean driver? In that case dummy method works perfectly.
While creating a custom windows 10 Install I found that Windows has an NVIDIA Statistics file in the 1903 installation. I removed this file and I have no problems with the drivers
If you could post what kind of problems you had, that would be helpful (for some people)...
Read what I said again. I did not say I had any problems
For future reference - what file are we talking about?
Ill have a look shortly. and I'll update this post
Sorry its not a file I deleted , Its a privacy setting I disabled.
In NTLite go to Settings> Privacy Theres a setting there called
Allow Experience Improvement Program (Nvidia Driver).
Cleaned the drivers myself per OP's instructions and used the 0KB "DisplayDriverRAS.dll" and everything works as usual. You cannot set the maximum pre-rendered frames in this version, instead we have this option(for people that don't know):
Just a heads up: R435 drivers (including 436.02) have integrated the Nvidia Profile Updater into the Nvidia Display Container service as a plugin.
If you don't want the plugin to "phone home" every now and then to check for updated profiles, you can remove the plugin as follows:
Delete the NvProfileUpdater shortcut from the "C:\Program Files\NVIDIA Corporation\Display.NvContainer\plugins\Session\" folder.
Delete the NvProfileUpdater folder from the "C:\Program Files\NVIDIA Corporation\" folder.
Restart the Nvidia Display Container service (or restart PC if you prefer).
This plugin also creates a folder in "C:\ProgramData\NVIDIA Corporation\" for its log files, so you can safely remove that NvProfileUpdater folder as well if you decide to remove the plugin.
This plugin is still only utilised if GFE is on the system, update commands are not invoked automatically by the plugin.
According to the plugin's logs, it kept trying to connect to Nvidia every few minutes even when I wasn't connected to the Internet. I also don't use/install GFE.