It’s important to marvel who’s testing these items.
Admins, particularly, have had a tricky month. April introduced widespread breakdowns – bluescreens, hangs, very sluggish habits – to a whole bunch of 1000’s of Win7 and eight.1 machines. This wasn’t a “small proportion” type of occasion. For some corporations, rebooting in a single day on Tuesday introduced seas of blue screens on Wednesday morning.
The primary spherical of cumulative updates and Month-to-month Rollups arrived on Patch Tuesday, however the now-ubiquitous second spherical didn’t present up till late Thursday afternoon, two and a half weeks later. Speak about admins taking a beating.
We nonetheless have one Tuesday left this month – the legendary “E week” that Microsoft by no means talks about – so the month might but finish with each a bang and whimper.
Right here’s how issues look as early Monday morning.
Nonetheless no ‘optionally available non-security’ cumulative replace for 1809
It took some time, however the second spherical of April patches lastly arrived. The one exception is for Home windows 10 model 1809, which nonetheless hasn’t seen an “optionally available non-security” patch. (They’re “optionally available” as a result of it’s a must to be a seeker – click on Test for updates – with the intention to get hit with the patch.)
Now we have a dependable report that the second patches this month have been held up due to persevering with issues with the Japanese new period date bugs. That very same report additionally says that even the most recent patches have bugs. I discover all of it superb – Microsoft’s been engaged on this drawback for no less than a yr, and the patches-of-patches have been stumbling throughout themselves.
Even Win10 1903 – the model nonetheless in beta testing – received a brand new patch, KB 4497093, bringing the construct quantity as much as 18362.86. It’s for “Insiders who’re at the moment within the Quick ring solely and on Construct 18362.53. We’ll roll this out to the Sluggish and Launch Preview rings in a bit.”
Six soiled patches, 5 blasted antivirus corporations
April’s Patch Tuesday introduced speedy complaints of Win7 bluescreens. Inside a few days we came upon that six patches – for Win 7, 8.1, Server 2008 R2, 2012 and 2012 R2 – had conflicts with 5 totally different corporations’ antivirus merchandise. The present tally:
Sophos – The corporate now says it’s found out the supply of the issue:
“Now we have recognized a everlasting repair and at the moment are mechanically rolling out the repair to prospects beginning 25th April 2019. This may happen over a two- to three-week interval.”
Microsoft continues to dam the six soiled patches on methods operating Sophos Endpoint.
Avira – The parents at Avira have been remarkably quiet. Our newest report from UAz says they might have lastly stumble on an answer – verified within the very early hours of Monday morning. Earlier makes an attempt at an Avira resolution failed, generally spectacularly. Microsoft has not modified its terse announcement:
“Microsoft has briefly blocked units from receiving this replace if Avira antivirus software program is put in. We’re presently investigating this problem with Avira and can present an replace when obtainable.”
Arcabit – The small Polish-language AV provider has launched an replace that solves the issue, based on Microsoft, though the Microsoft hyperlink to Arcabit’s assist article factors to a Technical Help telephone quantity, and no dialogue.
Avast/AVG – The corporate has issued hotfixes to keep away from the bluescreens. (Avast owns AVG.) Oddly, although, the way in which to put in the hotfixes isn’t what you would possibly count on:
- Boot your machine
- Let the machine stand for about 15 minutes whereas emergency updater works. The updater runs on system context reasonably than the person, so you don’t want to log in for it to activate.
- Reboot your machine. Your machine ought to now function usually, even with the Microsoft updates listed above.
That, to me no less than, is a very distressing manner to use a hotfix.
Microsoft not blocks the six soiled patches on machines operating Avast or AVG.
McAfee – Late to the sport, McAfee has acknowledged that putting in the soiled six patches might result in sluggish boot up occasions or sluggish efficiency. The one resolution to the issue, at current – apart from uninstalling the soiled six – is to disable any user-defined (non-default) Entry Safety guidelines.
Microsoft says it’s “presently investigating this problem with McAfee,” however they’ve been saying that for per week.
A number of extra patch issues
I’m seeing scattered reviews that Win7 customers are being supplied KB 3185319 — an replace from Sept. 13, 2016 — as a checked Essential replace to Win7. It’s a part of the MS16-104 bundle. I wrote about bugs on this patch again in October 2016. This isn’t the primary time we’ve seen KB 3185319 seem out of the blue.
There are additionally reviews of locked Server 2008 machines after putting in this month’s Month-to-month Rollup, KB 4493471.
Sustain with the most recent on the AskWoody Lounge.