• Patch Lady – hiding the GUI controls from us


    So as I read that last night I had to go fire up a 2004 to confirm.  Now as I see it what’s going on is in the GUI of a Windows 10 2004 you no longer see all the knobs to turn to defer all the stuff we recommend that you defer.  But to be honest I’ve seen where Microsoft has “made the GUI less complicated” in the last few feature releases and I can no longer depends on the advanced windows update settings of Windows 10 to best control the operating system.  I’m not convinced this is exactly “new” just something we’ve suspected for the last few feature releases where Microsoft decided to hide these settings in the GUI.

    As I see it, the local group policy editor on a Windows 10 Pro version still allows me to choose a deferral of 365 days.  That’s not the greatest solution to gaining control over your computer, but at least it means we are not without options.

    The 2004 feature release is still “offered” not shoved to me.

    Now then (and pardon the rant) what is more confusing is the fact that I have forgotten more about patching cadence than I can remember these days.

    We have gone from Current branch, current branch for business, Semi annual channel, semi annual targeted, oh now we changing our names to align the patching names to Office 365, oh now we are changing the name of Office 365, oh now we are changing the rings to channels, or is it channels to rings?  I can’t keep up… Oh we are supporting it for 12 months, no 18 months, no we’re doing 30 months for enterprise.

    Get the point that I’m exhausted with the constant churn in naming, servicing and moving things around …meanwhile Enterprises are running versions that I consider to no longer be appropriate because they too can’t keep up with the churn.

    The one thing I do wish that the https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 Windows Health dashboard would do would be to put some estimate of impact.  Yesterday Woody posted about a new bug that causes spontaneous reboots.  But here’s the thing… it’s listed in the 1909 health dashboard as being triggered LAST month not THIS month so it’s not a June bug, it’s a May one.  I haven’t seen widespread reports of this in EITHER May or June.  I wish they would give some hint as to the magnitude of the issue.  I don’t think you and I will see this issue.

    • Keep up to date on bios and video card drivers.
    • Don’t use multiple antivirus software on your PC – in fact I recommend you stay with Defender.
    • Don’t use gaming hacks to get around licensing.
    • Don’t install ancient software that includes ancient drivers on Windows 10.

    Do those steps and you’ll probably sail through Patch Tuesday with zero issues.

    As of 1903 there is a new “target version option” in the local group policy editor and I think I’ll need to expand our “best practices” and start recommending THAT setting.  Hang loose a detailed discussion of these buried local group policy settings is in the works and will be in the AskWoody newsletter.  Stay tuned, I’ll let you know when (it won’t be this weekend though)