As I reported the day gone by, the July 2018 Home windows and Workplace patches teem with insects. We’re simply starting to see the fallout.
The July three non-security Workplace 2016 patch KB 4018385 is formally yanked. In the event you don’t recall KB 4018385 — a small patch in a sea of Workplace fixes — the unique KB article describes it thusly:
Whilst you insert a 2D chart (as an example, a column, bar, scatter, line, space, or bubble chart) that comprises many values right into a worksheet, some gridlines on the backside of the chart aren’t displayed. After you put in this replace, gridlines will also be drawn generally in a chart with quite a lot of knowledge and logarithmic scale. Whilst you paintings with a chart that comprises filtered content material in an Workplace 2016 utility, the Workplace 2016 utility might crash. This factor happens for those who set up the replace KB4018319.
In different phrases, non-security patch KB 4018385 is a repair for a worm presented within the April Workplace 2016 safety patch KB 4018319. As Susan Bradley warned 3 months in the past:
Remember that problems were reported [for KB 4018319] by means of customers with problems opening or saving a .xls or .xlsx/.xlsb record with charts embedded. Presently the one workaround is casting off the updates.
So what we’re seeing is a non-security patch for a worm in three-month-old safety patch that crashed Workplace … and the brand new non-security patch additionally crashes Workplace. That is growth.
The KB 4018385 article now states:
This replace is now not to be had. It used to be got rid of as it reasons Workplace 2016 to crash whilst you paintings with charts. There may be recently no repair to be had for this factor. The workaround is to uninstall the KB 4018385 replace.
Plus ça exchange.
In a fully other a part of the arena, the entire July safety patches were up to date within the Microsoft Catalog. These days afternoon the day gone by, the entire 2018-07 patches got a brand new “Remaining Up to date” date of July 13, apart from for a couple of stragglers dated July 12. You could recall that each one 129 of the patches have been firstly posted on July 10, Patch Tuesday.
No reputable reason why given for the exchange, however Susan Bradley has a most likely clarification:
A improve case used to be opened and the phrase got here again that this basically affects the ones with virtualization/VMware. In the event you aren’t working that, you received’t be impacted.
Even if I do favor witp’s clarification:
I believe time go back and forth of patches is probably the most possible reason.
With a hat tip to James Gleick.
Suffering with a worm on this month’s patches? Let’s do the time warp once more at the AskWoody Living room.