Windows update stopped Brother MFG-240C from printing

[Porthos]

was wondering what to do if one comes in with 2004.

https://support.microsoft.com/en-us/help/4567523/windows-10-update-kb4567523

https://www.catalog.update.microsoft.com/Search.aspx?q=KB4567523

 

[Diggs]

I'm wondering if the patched 1903 will hold when it updates to 2004 or does it need to be re-patched?

 

[Sky-Knight]

It should hold, the fact that it's a manual patch probably means there's some registry stupidity somewhere that caused it. So these manual updates are less patches and more corruption cleanup.

 

[britechguy]

I'm wondering if the patched 1903 will hold when it updates to 2004 or does it need to be re-patched?

Virtually never. Microsoft does roll these fixes into the ISOs or online installer media that gets downloaded to do a Feature Update, typically the same day that the patches are released, but very soon afterward if not then.

This is one of the reasons I always try to create a fresh ISO when I need one rather than using an old one for any given Windows 10 Version. Yes, the installer can and will download all updates that have been made since that ISO was issued, but that's a far slower process than starting with one that's as up-to-date as can be. God bless the Media Creation Tool, which builds something that's "as new as you can get" whenever it's run.

 

[fincoder]

Microsoft does roll these fixes into the ISOs or online installer media that gets downloaded to do a Feature Update, typically the same day that the patches are released, but very soon afterward if not then.

If this is true I was unaware of it. Can you share a link that corroborates this? I typically use the same ISO for 6 months until the next feature update, so would be interested in any other info you have on this. I don't fancy downloading a new ISO and recreating the install USB every day.

Yes, the installer can and will download all updates that have been made since that ISO was issued, but that's a far slower process than starting with one that's as up-to-date as can be.

I generally skip updates during install, takes too long. A single cumulative update after install will apply all current patches and is reasonably fast.
I've never had an install problem that required the installer to check for updates or required a new ISO. If that happens one day it's the first thing I'll try.

 

[britechguy]

If this is true I was unaware of it. Can you share a link that corroborates this? I typically use the same ISO for 6 months until the next feature update, so would be interested in any other info you have on this. I don't fancy downloading a new ISO and recreating the install USB every day.

No one, including myself, does this anywhere close to "every day."

If you want to prove it to yourself, try creating a new ISO every month to two months using the Media Creation Tool. The sizes can change, sometimes quite a bit (hundreds of MB is about the biggest change I've observed). That simply would not happen if the ISO being built remained the same, and the Media Creation Tool does just that: builds it.

You can, of course, do exactly as you're doing. I've used really old ISOs when push has come to shove, as I know the resulting installation will be updated via Windows Update. I just prefer to have the amount of updating to be as minimal as can be.

 

[fincoder]

If you want to prove it to yourself, try creating a new ISO every month to two months using the Media Creation Tool. The sizes can change

I could try it, but I'd probably check the build numbers to see if it's changed. The size might change due to included drivers or apps, for example, not necessarily patches. If I do find the build number changes one day before the next feature release, then I would need to figure out when I should download and create a new installer.

No one, including myself, does this anywhere close to "every day."

No one? There might be someone... Anyway I only mentioned every day because you said this:
"I always try to create a fresh ISO when I need one"
I need to do an install at least every weekday.

So how often to you actually get a create a fresh ISO?

Of course all this vagueness is down to Microsoft's appalling lack of communication. Why can't we get on a mailing list that tells us when a new installer is available? Maybe someone should download the ISO every day just to check the build numbers and inform the world's techs and enthusiasts.

 

[Sky-Knight]

I download new ISOs twice a year, I don't bother making new ones beyond that. The only exception to that, is when I know there's a show stopping problem with the ISO. Which has only happened once in Win10s history, 1809.

Beyond that, it's a single delta patch to get the install current, and that takes far less time than waiting for a new ISO every time I need it.

 

[NJW]

Could someone clarify, please ... ?

I had a couple of clients who lost printing after installing KB4560960; I rolled them back and postponed updates.

Now that the KB4567512 fix is in (which is described as a Cumulative update), is this a substitute for 0960, or should I reapply that update before using this fix?

Edit to add (after @Diggs, below): This is on 1909, both before and after my intervention.

 

[Diggs]

In my case I couldn't roll back KB4560960 as Windows said it was critical but that was after rolling back from 2004 to 1903 so I got a bit lost at that point.

 

[britechguy]

@NJW,

While these are cumulative updates, the key thing is they're also "out of band," which means they will never be presented by Windows Update. So if you have the issue in 1909, manually apply KB4567512. (See also: https://win10.groups.io/g/win10/message/45714)
If you have the issue in 2004, manually apply KB4567523. (See also: https://win10.groups.io/g/win10/message/45773)

I imagine they're going to roll these patches into later cumulative updates as well, but in the meantime . . .

 

[NJW]

While these are cumulative updates, the key thing is they're also "out of band," which means they will never be presented by Windows Update. So if you have the issue in 1909, manually apply KB4567512.

Yes, I understand that. What I don't know is, if I have to allow updates again (remove the Pause) to have KB4560960 reapplied (which I rolled back to resolve the issue on the day) before applying – manually – KB4567512.

Or, if I can skip 0960 and just apply – manually – 7512.

In other words, does KB4567512 include the updates from KB4560960 (which had several security fixes, aiui). KB4567512 is described as a 'non-security update', but is about the same size as KB4560960, wtf is in it?

To put it another way, is KB4560960 a prerequisite for KB4560960?

Give me apt-get any day ...

 

[Porthos]

In other words, does KB4567512 include the updates from KB4560960

Yes.

To put it another way, is KB4560960 a prerequisite for KB4560960?

No, it is not. The 512 is a cumulative update just early to fix the issue.
July's update whatever number it ends up being will include all fixes.

 

[NJW]

The 512 is a cumulative update just early to fix the issue.
July's update whatever number it ends up being will include all fixes.

Thanks – I'll take your word for it!

 

[Porthos]

All Culmitive updates include all previous updates. Microsoft only patches issues with Culmitive updates, not just a small patch.

There are only installed as optional updates in the Windows update screen. Only the patch Tuesday updates are forced out to users that do not have updates paused or disabled.

 

[NJW]

Thanks @Porthos – I'm sure I knew that, but ...

Anyway, all sorted now, thanks.

 

[Porthos]

Thanks @Porthos – I'm sure I knew that, but ...

Anyway, all sorted now, thanks.

Not everyone knows about the way the "seeker" optional updates are delivered. Just putting out for all.