nVidia folder being created at c:\ after every reboot

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 10
    Windows 10 x64 2004
       #21

    Wobitancrawfodi said:
    Yes, I am the same woman from Gurgu3D.

    Sorry, you are saying that if I block driver downloads from Microsoft via Windows Update group policy, I can't download and install drivers from nVidia? Hmm. That's strange. I've had that setting enabled for years across hundreds of PCs I have built and managed, and the creation of this folder started only almost two weeks ago and ONLY on one PC

    The OS hasn't changed since I installed 1703 back July of 2017, other than the version (1703, 1709, 1809 always via clean install), it's always been the same Windows 10 X64. So what do you mean "Wrong OS selected"?

    I only use the standard drivers. I get my drivers from Advanced Driver Search | NVIDIA

    If I had installed the DCH drivers I would have lost the nVidia control panel and be getting an error every single time I start the computer.

    I posted on Guru3D because of the inability to install any driver after using DDU. I posted here because of the folder creation. The original post here makes no mention of DDU, as that was a suggestion proposed by someone here. It was only then I headed over to Guru3D.

    In what appears to be a poorly worded and failed attempt at clarity I gave background on the whole scenario. I should stop doing that as is seems to muddy the waters and often results in no solutions.

    On these forums, the topic is the creation of the folder, and tbh, that really is the only thing I am concerned about. DDU is a fantastic tool from the looks of it, but I've used it once only since I first used Windows back in the early 90's.

    If I changed something then I don't know what I changed. It certainly wasn't deliberate. My PC has been stable since I reinstalled it in Feb 2020. The ONLY thing I've changed is the monthly Microsoft Windows 10 CU's and NOTHING else.

    It's starting to look like a complete reinstall of Windows is going to be the only solution. At least then I can check at various points if and when the folder creation starts happening and get a feel for what's causing it.

    - - - Updated - - -

    I think I have a workaround. Why logging started I don't know, but I found a reg file on https://custhelp.nvdia.com that disables logging and it has stopped the folder creation.

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Installer]
    "Logging"=dword:00000000
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Installer]
    "Logging"=dword:00000000
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Logging\Definitions\LogFilters\PassFilter]
    "DefaultLogLevel"=dword:00000000
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Logging\Definitions\LogFilters\PassFilter]
    "DefaultLogLevel"=dword:00000000
    
    [-HKEY_CURRENT_USER\SOFTWARE\NVIDIA Corporation\Logging]
    
    [-HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\NVIDIA Corporation\Logging]
    Hi,
    For the group policy settings, depending of the setting you changed, you could have blocked driver installing. If you have chosen the right one, then no problem then.
    As for DCH driver, you should have the NVCP installed unless you are using the LTSC version of windows.

    For the wrong OS selected it is when you are downloading the driver. I saw quite a few user reporting issue to me just to find you they downloaded the wrong driver.

    As you told DDU is not your priority here, but if you want, could you share with me the DDU logs if you still have them? I'll give a look just in case something evident popup to me.
    you can send them at [email protected]

    Anyway either if it is my app or not, sorry for the issues you are having.
      My Computer


  2. Posts : 303
    Windows 10 x64 1809 LTSC
    Thread Starter
       #22

    Hey, thanks for getting back.

    Attached are my Windows update settings; Note that I use WSUS here, so updates come from there.

    "Do not include drivers With Windows updates" has been set for as long as we've been using Windows 10.

    No, not using LTSC.

    Using standard drivers. The image I created has store removed, so I cannot get the NVCP from the Windows store. I will resist the DCH drivers for as long as I can (and any other drivers that require me to get apps from the store, such as the Realtek audio drivers).

    The link I included in my previous post shows the standard drivers by default and I always make sure. If I accidentally use the DCH version (which happened the first time nVidia switch over to them), you find out real fast - as soon as you reboot and you get an error saying the NVCP cannot be found and you have a real wtf moment :)

    I doubt I still have the logs. When I restored the PC from a backup image they would have been wiped out. But - It's a trivial exercise to go through the process again. The image restore takes around 3 minutes. So when I get time over the next day or two I'll see if I can reproduce the problem for you.

    nVidia folder being created at c:\ after every reboot-wu_settings.png
      My Computers


  3. Posts : 10
    Windows 10 x64 2004
       #23

    Your Group policy seems ok.
    1 thing I just remember, is that when you install a DCH driver you cannot install a standard driver after.
    It is possible that this is your issue.

    As for information, when using DDU to uninstall the Nvidia driver (DCH) it should fix this and allow you to install the standard one.

    If you want to use windows without the store, I highly recommend that you use the LTSC version instead of a "unsupported" modification of a normal Windows 10.

    Another interesting information is that,on my case, the NVCP is faster from the DCH version. The driver is not really coming from the store, only the NVCP. The store has strict usage of the windows system. Ex: Registry access is extremely limited (unless microsoft gave special permission to the company developing the app) and by so an application like DDU could not be converted to the MS store.
    Main advantage of this is compared to the standard NVCP, the DCH one (from the store) will not create (as much) registry key as it is denied to do so. And we all know less registry key laying around is better performance wise.
    Anyway that was my 2cents :)
      My Computer


  4. Posts : 303
    Windows 10 x64 1809 LTSC
    Thread Starter
       #24

    Thank you for sharing your insights.

    No, there has been no mix up of driver versions. All drivers since I discovered DCH have been tested on a test PC before being released to my server where people get them from. Everyone here knows not to download drivers or updates for anything from online sources. Windows is always installed from scratch.In place upgrades are never done.

    I certainly agree with your thoughts on the registry. I've given up cleaning up left over registry entries when uninstalling things. I've never met an uninstaller that did a 100% clean up (with the exception of DDU which seems very thorough and well thought out). So these days I just restore from an image and don't bother with uninstalls.

    One day I will get around to LTSC. I spent many months tweaking 1809 and it's leaner than even LTSC, but I haven't had the time to start with a new version. I will have to get to that because 1809 will be out of support soon.

    Yes, I understand that NVCP comes from store and driver comes from nVidia. I have done some reading on DCH and I understand most of it but bottom line - I don't trust Microsoft. If Linux supported all the things we wanted to do with a PC I'd jump ship in an instant. So if we are forced to use Windows, we'll use the least amount of it we have to.

    Anyway, I'm going to re-install Windows; Whilst I did find a work around I have an itch that needs to be scratched - I want to know why this folder creation started.

    I'll get back to you once I've tested DDU again too.

    - - - Updated - - -
    @Wagnard, please find attached log file from DDU and a screen cap of the error I get after a reboot having uninstalled drivers using DDU.
    nVidia folder being created at c:\ after every reboot-driver_fail.png
    nVidia folder being created at c:\ after every reboot Attached Files
      My Computers


  5. Posts : 10
    Windows 10 x64 2004
       #25

    Hi, I checked the log and at first look everything seems ok.
    I would be interested to see your device manager to see the current state of the GPU.
      My Computer


  6. Posts : 303
    Windows 10 x64 1809 LTSC
    Thread Starter
       #26

    Wagnard said:
    Hi, I checked the log and at first look everything seems ok.
    I would be interested to see your device manager to see the current state of the GPU.
    I'm guessing you want that after running DDU and before restoring from an image to get the system operational? At that point the system shows no display adapters at all. Here's how it looks now, having restored from my latest image...

    nVidia folder being created at c:\ after every reboot-device_mangler.png
      My Computers


  7. Posts : 10
    Windows 10 x64 2004
       #27

    Wobitancrawfodi said:
    I'm guessing you want that after running DDU and before restoring from an image to get the system operational? At that point the system shows no display adapters at all. Here's how it looks now, having restored from my latest image...

    nVidia folder being created at c:\ after every reboot-device_mangler.png
    Ok, this kinda answer my question. I guess the display adapter will be shown in other devices.
    When this is the case, usually it point out to something being broken with SetupApi. After a DDU run, normally you should see a display adapter with a name like "Microsoft basic display adapter" or something along theses lines.

    If you had no adapter listed in the "Display Adaptor" section , it is normal that the driver installer throw you this message.
    From this screenshot, you have quite a lot of uninstalled devices. Do you have issues installing them too ?
    Are you able to install the current nvidia driver now? I see you are on a earlier version at the moment.
      My Computer


  8. Posts : 303
    Windows 10 x64 1809 LTSC
    Thread Starter
       #28

    These are all for devices I don't use or want on my systems. Intel Management Engine, Bluetooth, WiFi, Turbo Boost, etc. They are deliberately not installed. I don't waste time installing drivers for devices I don't want to use, or that are unsafe (IME), or have adverse impacts on the system (turbo boost).

    No, the display adapter did not show in other devices. What you see there now is exactly what was there after running DDU. Any way, it sounds like the mystery is solved. No display adapter = cannot install display drivers. And the good news... There is nothing wrong with DDU, but you knew that already, hey

    441.87 is the driver version installed Feb 09 2020. I don't automatically update drivers for three reasons (1). If they are from Microsoft they have a high chance of bricking my device (2). "If it ain't broke don't fix it". There needs to be a reason to install new drivers. Just because it's there doesn't mean it should be installed. (3). New drivers may offer nothing I need. If they do I will install them. In fact, often, problems arise from installing new drivers. No one tests any more, especially Microsoft - that's left to the masses.

    I only upgraded as part of the testing trying to figure out what was causing the umdlogs folder creation. When the later version still produced the problem there was no reason to stay on that version given that the existing version works fine and forms the foundation of what was supposed to be a stable, predictable system.

    Every time I update display drivers I lose 2-3GB of disk space. So, urgent security fixes aside, the only time drivers get updated is when (a). They've been tested thoroughly on my test system and (b). I do my twice-yearly refresh of Windows.

    This way when someone says "It must be your fault, you must have changed something" I can respond with all sincerity and say "NO! My system has been the same for xx months. I have not changed anything"...

    The way I do things is a hangover from working way too long in corporate I.T. environments
      My Computers


  9. Posts : 10
    Windows 10 x64 2004
       #29

    Wobitancrawfodi said:
    These are all for devices I don't use or want on my systems. Intel Management Engine, Bluetooth, WiFi, Turbo Boost, etc. They are deliberately not installed. I don't waste time installing drivers for devices I don't want to use, or that are unsafe (IME), or have adverse impacts on the system (turbo boost).

    No, the display adapter did not show in other devices. What you see there now is exactly what was there after running DDU. Any way, it sounds like the mystery is solved. No display adapter = cannot install display drivers. And the good news... There is nothing wrong with DDU, but you knew that already, hey

    441.87 is the driver version installed Feb 09 2020. I don't automatically update drivers for three reasons (1). If they are from Microsoft they have a high chance of bricking my device (2). "If it ain't broke don't fix it". There needs to be a reason to install new drivers. Just because it's there doesn't mean it should be installed. (3). New drivers may offer nothing I need. If they do I will install them. In fact, often, problems arise from installing new drivers. No one tests any more, especially Microsoft - that's left to the masses.

    I only upgraded as part of the testing trying to figure out what was causing the umdlogs folder creation. When the later version still produced the problem there was no reason to stay on that version given that the existing version works fine and forms the foundation of what was supposed to be a stable, predictable system.

    Every time I update display drivers I lose 2-3GB of disk space. So, urgent security fixes aside, the only time drivers get updated is when (a). They've been tested thoroughly on my test system and (b). I do my twice-yearly refresh of Windows.

    This way when someone says "It must be your fault, you must have changed something" I can respond with all sincerity and say "NO! My system has been the same for xx months. I have not changed anything"...

    The way I do things is a hangover from working way too long in corporate I.T. environments :)
    Well there is bugs in DDU or things to improved, looking at the SetupAPI code after your report let me to find some odd stuff that probably doesn't impact anything but still wasn't right. I always try to keep an open mind that DDU could be the issue.

    For the UMD log, I second what the others are saying. For some reason there were registry entries added that enabled logs. I trust you that it was not you who added theses but something else did and as far as I know they are not added by themselves.

    Btw I really like your thinking on computer in general and I guess that is what to expect from a good IT :)
    P.S You should really look on the LTSC, I really think it would be good for you. And sorry for my English, it is not my first language so trying to be as precise as possible and trying not to be confusing.
    Last edited by Wagnard; 05 Jul 2020 at 16:47.
      My Computer


  10. Posts : 303
    Windows 10 x64 1809 LTSC
    Thread Starter
       #30

    Lol, strange days. Who knows what happened. I'm about to embark on the re-install of Windows to see if I can find when it happens. I did actually check the registry. There are only 3 places the keys are going to be found, and there were actually no logging keys there at all. So, once I added them that stopped it.

    Your English is fine.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:04.
Find Us




Windows 10 Forums