1. Forum
  2. Usenet
  3. ALT.COMP.OS.WINDOWS-10

  • Re: Group policy disables driver updates

    From Paul@21:1/5 to Jason on Wed Jul 10 11:57:04 2024
    On 7/10/2024 11:42 AM, Jason wrote:
    Since day One with this win 10 system, I've noticed on
    the Windows Update screen that some Group Policy is
    controlling some aspects of Update's operation. One that
    caught my eye when I finally looked is one that prohibits
    driver updates. Why would that be and should I figure out
    how to enable updates? CCleaner always reports out-of-date
    drivers but I've never let it update them. Should I?


    gpedit.msc
    Computer Configuration
    Administrative Templates
    Windows Components
    Windows Update
    Do not include drivers with Windows Update policy [ "Enabled" stops new drivers ]

    On Home, it might be like this via Regedit. The item won't exist, you create a new one.
    Removing the item, or setting the item to 0, disables it again.

    HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    ExcludeWUDriversInQualityUpdate DWORD32 1

    ( Ref: https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10 )

    The same Registry area is used by InControl, to control OS upgrades (stop them).
    If your screen content isn't quite the same, InControl has added three items. For example, my Win10 is frozen at "W10" "22H2" so no attempts are made to Upgrade to W11, when a W11 OS is already on the same hard drive.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jason@21:1/5 to All on Wed Jul 10 11:42:52 2024
    Since day One with this win 10 system, I've noticed on
    the Windows Update screen that some Group Policy is
    controlling some aspects of Update's operation. One that
    caught my eye when I finally looked is one that prohibits
    driver updates. Why would that be and should I figure out
    how to enable updates? CCleaner always reports out-of-date
    drivers but I've never let it update them. Should I?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From VanguardLH@21:1/5 to Jason on Wed Jul 10 11:54:01 2024
    Jason <jason_warren@INVALID.ieee.org> wrote:

    Since day One with this win 10 system, I've noticed on
    the Windows Update screen that some Group Policy is
    controlling some aspects of Update's operation. One that
    caught my eye when I finally looked is one that prohibits
    driver updates. Why would that be and should I figure out
    how to enable updates? CCleaner always reports out-of-date
    drivers but I've never let it update them. Should I?

    Why would you allow anyone other than yourself to do brain surgery on
    your hardware? Just because Microsoft offers driver updates doesn't
    mean you should get them. Unless a driver fixes a bug that you are
    actually experiencing with your hardware setup, or enables new features
    that you will actually use, there is no cause to update the driver.
    When a device needs a driver update, *YOU* are responsible for getting
    the correct driver, and to perform the compatibility and QA testing of
    the new driver in your setup. You are the sysadmin of your computer,
    not Microsoft.

    Whether it be Windows Update, CCleaner, or some other nagware
    complaining there is a later version of software or a driver, it is
    still YOUR responsibility to decide, test, and deploy the new code.
    There is no reason to fix what is not broken.

    Say a device maker submits a new driver version to Microsoft to add to
    its update catalog. That doesn't mean the new driver is perfect. It
    could have bugs. But now the defective driver gets presented to all
    users of that hardware. It takes time to submit a driver to Microsoft,
    time for Microsoft to curate the driver, and time to remove a defective
    driver from the WU catalog. Promise, for example, pushed out a new RAID
    driver version that got into the WU catalog, users reported severe data
    loss from file system corruption with the new driver version, Promise
    fixed the bug, but you couldn't get the new driver version from the WU
    catalog until about 2 months after the fix by Promise. Obviously it was
    far better and faster to get the fixed driver from Promise than to wait
    for it to appear in the WU catalog.

    "How to turn off driver updates in Windows Update in Windows 10" https://winaero.com/how-to-turn-off-driver-updates-in-windows-update-in-windows-10/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)