I've set the following on a fresh install of Windows Pro 64 22h2 but unknown devices are still automatically installed. How do i stop this, short of not connecting to the internet? When I instal the manufacturer's drivers, Windows default to the Windows update drivers after a sysperp; which causes problems for me. Thanks in advance.
@ecktt There is nothing need to play with. This option what you told about works great. But maybe I can't understand exactly what you mean. Maybe you can somehow specify what doesn't work for you or what exactly you want to disable.
Basically, if I set the 2 options mentioned above, on connecting to the internet, devices without drivers (eg video, chipset, etc) are automatically installed from the windows update. So basically, the setting are ignored by the operating system. I've remade the Windows Pro 22h2 install media twice, using the media creation tool and rufus, just in case the install media was defective but I am getting the same results. I've tried this on a Lenovo Ideapad X390, X13 and L13gen2 with repeatable behaviour. This would not be a problem if sysprep would use the drivers installed by me on after imaging a laptop during the hardware detection phase. A workaround would be to install all drivers offline before connecting to the internet but this does not resolve the initial issue and becomes a hassle with the wide range of hardware I have to deal with.
Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "ExcludeWUDriversInQualityUpdate"=dword:00000001
Good suggestion, but this, it's already in the first post... That's where this whole long story starts here, which has been told for 8+ years, if begin from releasing Windows 10.
Well, I hoped it would have worked but that wasn't why I replied. I was just sharing information. Most guides on blocking driver updates list all 3, ie Systems properties setting, the GP and the registry key. The fact is, the latter 2 are the same setting. Shonk will now know that.
I personally use it on many computers and it works great. If it doesn't work for you, you have to look for a solution in your system, but not claim that it doesn't work. It works without any problems and has always worked.
Not doubting your situation and am not here to debate you either since that used to work for me. But, as indicated in the original post, I am having this issue with 22h2 and it is possible you're not on that build. I have found a solution which just worked on a Lenovo X390 and now going to try it on a Lenovo x13. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching] "SearchOrderConfig"=dword:00000000
But as you know, this 22H2 doesn't mean anything, because there are several such things that use this combination in the number. For example Windows 10 19045.2311 version 22H2 Windows 11 2262x.898 version 22H2 x can also be different So, maybe you'll reveal the deep secret of what your mysterious 22H2 could mean. And I wouldn't be at all surprised if you have some early development so-called Windows 11 and it doesn't work.