Forum Discussion
Autopatch Readiness Not Ready
I've recently started rolling out Autopatch in our environment. I've started see devices registered with an Autopatch readiness state of Not ready. A majority of those devices are showing a Conflicting Configuration for the registry key SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\DoNotConnectToWindowsUpdateInternetLocations. But on all the devices I've looked at that key is set to 0. Which means that setting is explicitly disabled. So, it should allow devices access to the internet for Windows Updates. As far as I can tell we're not setting that regkey anywhere explicitly in a GPO. All of our devices are CoManaged with SCCM. So, I'm assuming this is something SCCM is setting. What's confusing to me is the Microsoft documentation I've looked at regarding conflicting configuration states it's looking at any setting for that existing registry key. But, if that registry key exists and it's explicitly allowing internet access to Windows Updates why would that be a problem? My other concern is if I do the suggested remediations and delete that registry key all together am I going to break something else? Or, if I delete the key, is SCCM just going to add it right back?
3 Replies
Microsoft documentation states that if the key exists with any value other than 0, it prevents Windows Update from connecting to the internet.
Even if you haven't explicitly set this in GPO, SCCM (Configuration Manager) may be setting or enforcing policies via client configuration or configuration items.
Generally, this key is used to control connection behavior. Removing it (if not needed) typically won't break Windows Update functionality, especially if the system is configured to connect normally. But, if SCCM policies explicitly set or rely on this key, deleting it may cause configuration drift or be overwritten.
