KB4530684 CU Win 10 v1903 build 18362.535 & v1909 build 18363.535 Win Update

Anak said:

VBF, according to this: How to disable driver updates from Windows Update| Method 1: The Hardware dialog It's ambiguous at best.
I can get to the window you used but couldn't find the second window so I used the second method.

Method 2: The Windows Registry:

• I went to the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching
• Located the Dword SearchOrderConfig - It's located in the driversearching key and set it to zero (0) to stop driver updates.

I can't use Method 3 because I'm running the Home OS version.

Thanks to ddleo for the link.
I went to his here link described in his Post #76 and near the top there is a link for How to disable driver updates from Windows Update and I went there for the 3 methods.

If you look at the link you provided, the second window with the options was only for Win 7. Under Win 10, I agree about the ambiguity hence my comment "..... although I don't know if it includes driver updates:"

I set it the way I showed anyway (Pro and Home systems) and have (so far) never had an issue. Tbh, if my systems get problems of this magnitude and I cannot roll back a driver, my friend Mr Macrium can take over

Anak said:

Thanks to ddleo for the link.
I went to his here link described in his Post #76 and near the top there is a link for How to disable driver updates from Windows Update and I went there for the 3 methods.

You're most welcome Steve.
In this post (where I describe the method for preventing automatic driver updates), there is a big Warning, which should be seriously considered regardless of the way a driver is disabled, I.e via Group Policy Editor (Pro edition) or .reg file (Home edition).

So, you and anybody else using this method to prevent driver updates, should
note that Warning!

ddelo said:

You're most welcome Steve.
In this post (where I describe the method for preventing automatic driver updates), there is a big Warning, which should be seriously considered regardless of the way a driver is disabled, I.e via Group Policy Editor (Pro edition) or .reg file (Home edition).

So, you and anybody else using this method to prevent driver updates, should
note that Warning!

And the very fact that your warning is necessary makes me very wary of it inasmuch as I would feel as if I POTENTIALLY was painting myself into a corner if the reversal failed.
Also, I wonder what happens if you apply your Restrictions, over time forget they are there and then allow a major CU or Feature Update to install.
Possibly all may be well but do we actually know?

Yes, I realise I'm playing Devil's Advocate here and in no way am I disparaging your research @ddelo but I do feel that the strategy I mentioned in #81 is somewhat safer.

Now call me a coward and i'll hold my hand up

VBF said:

Also, I wonder what happens if you apply your Restrictions, over time forget they are there and then allow a major CU or Feature Update to install.
Possibly all may be well but do we actually know

Now call me a coward and i'll hold my hand up

Yes everything will be as supposed to. I have been using this Group Policy setting to prevent Microsoft from updating my Intel(R) 9 Series Chipset Family SATA AHCI Controller Driver and it's been working flawlessly for almost a couple of years.
It has survived all CUs and FUs since 1803.

And nobody will call you anything Andy.
It's a matter of preference and peace of mind. You tweak something, if you feel comfortable with it. If not, you don't do it and you gain a peaceful sleep at night!

ddelo said:

Yes everything will be as supposed to. I have been using this Group Policy setting to prevent Microsoft from updating my Intel(R) 9 Series Chipset Family SATA AHCI Controller Driver and it's been working flawlessly for almost a couple of years.
It has survived all CUs and FUs since 1803.

And nobody will call you anything Andy.
It's a matter of preference and peace of mind. You tweak something, if you feel comfortable with it. If not, you don't do it and you gain a peaceful sleep at night!

I agree...now I'm Handy Andy am I?

The good thing with Windows is that there are 20 ways to do everything
The bad thing with Windows is that there are 20 ways to do everything

xips said:

All is good now. I rolled back to build 476 and filtered the Hardware IDs in Group Policy resulting in no Brother drivers within the (test re)update queue. Thanks again Dimitri

Im glad you got it working Chris.
Thank you for informing us of the outcome.