Closed qmro closed 1 year ago
Try running gpupdate /force
in an elevated command prompt after applying registry change. Does policy applies this way?
I set the policy to "Not Configured", ran "disablewindowsupdatedriversdownload.cmd" then executed gpupdate /force
and waited till it completed. The policy has not changed from "Not Configured" and it remained like that after a restart. (I would like to add that checking for an update after that both before and after a restart no longer 'updates' the driver, which is odd because I ran "disablewindowsupdatedriversdownload.cmd" after a fresh install of WIndows yet drivers did 'update'. Also "enablewindowsupdatedriversdownload.cmd" does not revert the registry key back to 0.)
I will close the issue, turns out the error has been from my side. Running the script in the utility folder and restarting does the job.
The mentioned event occurs despite running "disablewindowsupdatedriversdownload.cmd" present in the "utility" folder. After some inspection, it appears that it modifies the registry which seems insufficient. I have been experiencing this in the Pro editions of Windows 10 and 11. Upon further research, I found a method to achieve the same effect through Group Policy Editor as follows by enabling the policy in this path: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update > Do not include drivers with Windows Updates If possible with respect to your time and ability, please update "disablewindowsupdatedriversdownload.cmd" to include the Group Policy modification.