The KB 3035583 patch is NOT overriding Windows 10 registry settings

Topic

New Reply

There are reports all over the web that the new KB 3035583 – the detested “Get Windows 10” patch — is violating Microsoft’s terms of engagement, and
[See the full post at: The KB 3035583 patch is NOT overriding Windows 10 registry settings]

Reply | Quote

Replies

“More than that, in systems that have the Automatic Update setting “Give me recommended updates the same way I receive important updates” unchecked, the new KB 3035583 appears as an unchecked, optional patch.”

I can absolutely verify that.

Reply | Quote

Yep, it’s italicized too.

Reply | Quote

Same for me. Optional, unchecked, italicized: hidden! Get thee gone foul demon.

Reply | Quote

woody says:
May 6, 2016 at 7:40 am

Yep, it’s italicized too.

Forgot what that means. Can’t find it in search.

JF

Reply | Quote

If you look closely at the line for 3035583 in Windows Update, it appears in italics.

Reply | Quote

I think it means that it’s “recommended”.

Reply | Quote

Correct, italicised means Recommended, which is floating somewhere between true Important Updates (non-security, still mandatory according to Microsoft) and true Optional Updates.
If the relevant check box it ticked, then it becomes Important, while if the check box is unticked, then it becomes Optional. Italicised just shows that is not meant to be true Optional.
Recommended means in general that there are new features which Microsoft would like users to install, but not enforcing this behaviour. If the intended initial purpose is still followed by Microsoft, this is subject to another discussion.

Reply | Quote

CH100; Much obliged for the clear explanation and thanks also to RCPete and Woody.

This online forum is the most helpful and friendliest I’ve experienced.

JF

Reply | Quote

Back in the day (XP) there were three categories. Important, recommended, and optional. As of Vista there are two visible, whether you check the box “Give me recommended updates the same way I receive important updates” in the options determines if the “recommended updates” appear italicized in the optional section, or in the important section.

Until February of 2015 it seemed irrelevant to me and was checked, now I have to review everything so it still doesn’t matter since I have to review everything and many of the junk ones are “important” anyway. Does anyone know when the first junk update was released? I know KB2952664 came out somewhere in the first half of 2014, anyone have more info?

Does anyone know what info microsoft is officially after? I know as of windows 8 they want to assign each person / computer a unique tracking ID for marketing purposes (per the control panel), but are there any more specifics they’ve admitted to (EULA, etc..)?

Reply | Quote

Not a forum Joe, although it does function like a forum sometimes, thanks to Woody. Thank you for your kind words. I appreciate it.

Reply | Quote

Apologies for not reading your site more frequently. So I missed this until today.

Like Woody, I have trusted MS to stick to the published documentation. So I haven’t been checking my registry very often. But today I did, and I can report that *something* has been mucking about in there recently.

Back in January, per instructions posted here and in KB3080351, I had set BOTH of these:
Subkey: HKLMSoftwarePoliciesMicrosoftWindowsGwx
DWORD value: DisableGwx = 1

Subkey: HKLMSOFTWAREPoliciesMicrosoftWindowsWindowsUpdate
DWORD value: DisableOSUpgrade = 1

When I checked today, the 1st one was still there, but the 2nd one was SOLID GONE.

Since the last time I checked my registry for these values, I did a reset of WUA because it was running so slowly. So it *might* have been that.

And I installed most of the April batch of patches, by installing KB3145739 *MANUALLY* first, and then installing the rest of the security patches. So it *might* have been that.

But I did *NOT* install KB3035583. So that wasn’t the cause of the registry modification, at least for me.

Have another machine, which got the same treatment, *except* for the WUA reset, so it might provide a cleaner testcase. Said machine is currently being used by my spouse; will check later today or tomorrow when I can get access to it, and then post a followup.

Reply | Quote

Please do keep us posted. I’m hearing some sporadic complaints about one or the other of the keys getting zapped, but don’t have any reliable details. And I haven’t a clue which KB is doing it.

Reply | Quote

Reset of WUA is the likely cause and not any other update. The reset removes all the custom registry keys related to Windows Update and this was one of them, unless configured via Group Policy and not registry editing in which case I would expect to come back.

Reply | Quote