Patch Tuesday, RIP (or not....)

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


What could possibly go wrong?
Nov 7, 2020
It seems Microsoft is ditching Patch Tuesday in favour of continuous patching - this makes a lot of sense in many ways because Patch Tuesday was founded in the days when ubiquitous, fast connectivity was not the norm.

Welcome, Windows Autopatch :)

Of course the concept of Patch Tuesday will live on informally within enterprises because nobody wants to reboot three times a week, not on an endpoint and certainly not on a server. It might be the case that we get more micro-patches that actually don't need a full reboot but rather a process or service to restart - like our browser updates do.

Anyway, interesting news with Microsoft modernising the approach :)
That's awesome. Yeah, no enterprise is going to reboot three times a week but at least they can choose to if something is critical enough to them. And in the meantime maybe Microsoft can fix bugs like the print spooler issues in less than three months because they're no longer hamstrung by this arbitrary monthly cadence.
Unless they fix the need to reboot to apply almost any patch, this is horrible news. I setup my PC with my environment, and leave it that way all month long. I despise having to re-establish it when forced to do a reboot because of Patch Tuesday. The easy fix is to allow updates without forced reboots, much as Linux does.
Perversely, it's actually enterprise-focused. I can only assume that they will reduce the reboot requirements wherever possible - nobody will welcome frequent reboots, Windows nowadays does not need it. I can say my corporate VMs nag me into a reboot once a week, my personal Surface Pro 7 gets rebooted maybe twice a month.

When will Windows Autopatch be available?

Windows Autopatch will be released in July 2022. Stay up to date by bookmarking the Windows IT Pro Blog.

How much does Windows Autopatch cost?
Windows Autopatch is offered as a feature to Windows 10/11 Enterprise E3 at no additional cost.


What are the prerequisites for Windows Autopatch?

Intune only:

  • Azure Active Directory (Azure AD)
  • Microsoft Intune
  • Windows 10/11 supported versions

  • Hybrid Azure AD-Joined or Azure AD-joined only
  • Microsoft Intune
  • Configuration Manager, version 2010 or later
  • Switch workloads for device configuration, Windows Update and Microsoft 365 Apps from Configuration Manager to Intune (min Pilot Intune)
  • Co-management workloads
I'm waiting for the TED talk where someone's presentation laptop automatically reboots during the presentation because of an auto patch.

Microsoft doesn't seem to learn from it's mistakes.