Windows 10 - how to prevent forced driver updates for single devices permanently

Discussion in 'Windows, Linux & Others on the Mac' started by macenied, Aug 10, 2015.

  1. macenied, Aug 10, 2015
    Last edited: Aug 11, 2015

    macenied macrumors 6502a

    macenied

    Joined:
    Aug 20, 2014
    #1
    Hi,

    All credits to the guy who posted it - I just configured it and it works. Very handy if you want to stick with working bootcamp drivers for selected devices.

    The solution:

    http://www.tenforums.com/drivers-ha...er-graphics-driver-stop-future-updates-2.html

    posting #12

    This way Windows 10 Pro can update everything it wants except drivers for devices you specify.

    It was the last pending task I wanted to solve / achieve for the W10 Pro installation on my MBP 7.1. Windows 10 Home editions don't have the gpedit.msc editor and cannot apply this solution.

    I need to do this on the MBP for the integrated NVidia Geforce 320M GPU which works perfectly using the version 332.28 drivers. Newer drivers currently cause problems.

    Enjoy !
     
  2. Shirasaki macrumors 603

    Shirasaki

    Joined:
    May 16, 2015
    #2
    Basically all policies are stored in registry, therefore changing settings in gpedit.msc is equal to changing dedicated registry keys in registry editor. The most significant drawback is: this approach is riskier since there is no readable explanation of each key.

    Unfortunately I don't know which of those keys are changed. I have enterprise version of Windows 10 installed and I can use gpedit.msc to do it.

    BTW: I have disabled Windows Update from gpedit.msc in Windows 10.
     
  3. macenied, Aug 11, 2015
    Last edited: Aug 11, 2015

    macenied thread starter macrumors 6502a

    macenied

    Joined:
    Aug 20, 2014
    #3
    Yes, you are right about editing the registry. Should be doable but I prefere the editor, especially because a device can have many ID's which may be painful to configure using RegEdit. I have no problem with installing updates when they work. The Nvidia driver update for the 320M does not, so I blocked it. When Windows Update runs, it downloads and tries to install the driver but it fails. After that you can hide the update using wushowhide to get rid of the error and subsequent download and installation attempts. Nice, I like it.
     
  4. Shirasaki macrumors 603

    Shirasaki

    Joined:
    May 16, 2015
    #4
    Like Mac OS X plist files, many Windows hidden settings could be changed in registry.

    The risk is virtually identical: no one can tell which key controls which setting, maybe unless Microsoft or Apple engineers.
     
  5. doynton macrumors 6502

    Joined:
    Oct 19, 2014
    #5
    Group policy is only available in windows 10 Pro or Enterprise versions.

    If you have the home version you need to update the registry direct. The end result is the same - you just use a different GUI.
     
  6. Shirasaki macrumors 603

    Shirasaki

    Joined:
    May 16, 2015
    #6
    So I prefer professional system because they may give more convenient tools than home version. And as I know, home version Windows 10 will try to keep up to date, as long as new updates are available.
     
  7. macenied thread starter macrumors 6502a

    macenied

    Joined:
    Aug 20, 2014
    #7
    Update. This method works like a charm. After several W10 updates from Microsoft and even W10 image restores ( using Macrium 6 free ) the drivers for the configured devices are intact ( not touched ). I configured following devices not to be updated on my MBP 7.1 :

    NVIDIA GeForce 320M

    * PCI\VEN_10DE&DEV_08A0&SUBSYS_00C2106B&REV_A2
    * PCI\VEN_10DE&DEV_08A0&SUBSYS_00C2106B
    * PCI\VEN_10DE&DEV_08A0&CC_030000
    * PCI\VEN_10DE&DEV_08A0&CC_0300
    * PCI\VEN_10DE&DEV_08A0&REV_A2
    * PCI\VEN_10DE&DEV_08A0
    * PCI\VEN_10DE&CC_030000
    * PCI\VEN_10DE&CC_0300
    * PCI\VEN_10DE
    * PCI\CC_030000
    * PCI\CC_0300

    NVIDIA High Definition Audio

    * HDAUDIO\FUNC_01&VEN_10DE&DEV_000C&SUBSYS_10DE0101&REV_1002
    * HDAUDIO\FUNC_01&VEN_10DE&DEV_000C&SUBSYS_10DE0101
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&CTLR_DEV_0D94&VEN_10DE&DEV_000C&REV_1002
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&VEN_10DE&DEV_000C&REV_1002
    * HDAUDIO\FUNC_01&VEN_10DE&DEV_000C&REV_1002
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&CTLR_DEV_0D94&VEN_10DE&DEV_000C
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&VEN_10DE&DEV_000C
    * HDAUDIO\FUNC_01&VEN_10DE&DEV_000C
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&CTLR_DEV_0D94&VEN_10DE
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&VEN_10DE
    * HDAUDIO\FUNC_01&VEN_10DE
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE&CTLR_DEV_0D94
    * HDAUDIO\FUNC_01&CTLR_VEN_10DE
    * HDAUDIO\FUNC_01&GF&VEN_10DE&DEV_000C&SUBSYS_10DE0101&REV_1002
    * HDAUDIO\FUNC_01

    NVIDIA nForce PCI System Management

    * PCI\VEN_10DE&DEV_0D79&SUBSYS_CB8910DE&REV_A1
    * PCI\VEN_10DE&DEV_0D79&SUBSYS_CB8910DE
    * PCI\VEN_10DE&DEV_0D79&CC_0C0500
    * PCI\VEN_10DE&DEV_0D79&CC_0C05
    * PCI\VEN_10DE&DEV_0D79&REV_A1
    * PCI\VEN_10DE&DEV_0D79
    * PCI\VEN_10DE&CC_0C0500
    * PCI\VEN_10DE&CC_0C05
    * PCI\VEN_10DE
    * PCI\CC_0C0500
    * PCI\CC_0C05

    NVIDIA nForce System Management Controller

    * PCI\VEN_10DE&DEV_0D7A&SUBSYS_CB8910DE&REV_A1
    * PCI\VEN_10DE&DEV_0D7A&SUBSYS_CB8910DE
    * PCI\VEN_10DE&DEV_0D7A&CC_0B4000
    * PCI\VEN_10DE&DEV_0D7A&CC_0B40
    * PCI\VEN_10DE&DEV_0D7A&REV_A1
    * PCI\VEN_10DE&DEV_0D7A
    * PCI\VEN_10DE&CC_0B4000
    * PCI\VEN_10DE&CC_0B40
    * PCI\VEN_10DE
    * PCI\CC_0B4000
    * PCI\CC_0B40
     
  8. Shirasaki macrumors 603

    Shirasaki

    Joined:
    May 16, 2015
    #8
    Congratulations you can figure this out. :)
     

Share This Page