https://betanews.com/2018/11/20/microsoft-pulls-buggy-office-updates/https://betanews.com/2018/11/13/microsoft-windows-10-october-2018-update-back/Et tu, Office? After pulling Windows 10 update, Microsoft does the same for Office
Microsoft's update procedure for Windows 10 has been a little, er, wobbly of late. The Windows 10 October 2018 Update proved so problematic that it had to pulled, and even the re-released version is far from perfect.
Now it seems the cancer is spreading to Office. Having released a series of updates for Office 2010, 2013 and 2016 as part of this month's Patch Tuesday, Microsoft has now pulled two of them and advised sysadmins to uninstall the updates if they have already been installed.
See also:
* Microsoft pulls the problematic Windows 10 October 2018 Update
* The re-released Windows 10 1809 is still buggy -- and some fixes won't arrive until next year
* Re-released Windows 10 October 2018 Update breaks Apple iCloud
In both instances -- KB4461522 and KB2863821 -- Microsoft says that the problematic updates can lead to application crashes. While this is not as serious a problem as, say, data loss, it does little to quieten the fears that have been voiced about the quality control Microsoft has over its updates.
For the KB4461522 update, Microsoft says:
Notice:
After you install this update, you may experience crashes in Microsoft Access or other applications. To resolve this issue, uninstall the update by following the instructions in the "More information" section.
This update is no longer available.
It's a similar story for KB2863821:
Notice:
After you install this update, you may experience crashes in Microsoft Access or other applications. To resolve this issue, uninstall the update by following the instructions in the "More information" section.
This update is no longer available.
If you have installed either of the updates, the advice is to remove them as soon as you can. You'll then have to sit back and wait for Microsoft to release updated, non-buggy versions -- and it's impossible to say when they will appear.Pay attention, please.Microsoft has a problem. LOOK AT THE PICTURE. As a company, older employees have been being forced out over the last few years, moving the age of the "in charge" personnel lower and lower and lower.
Middle managers as a group have been removed and the recently promoted Team Leaders assigned to their Management Control and "internal to the team Quality Control duties".
Microsoft is a fine example of the new nation-wide "Due To Downsizing & Cost Cutting Millennials were put In Charge" syndrome.
These 20-30 somethings think differently than Joe Normal, and in this case they see nothing wrong with "moving on" somebody else's software problems to the next step in the process.
A millennial has a somewhat narrow view of "his job" and they do
their job, not everybody else's.
Microsoft is checking their software releases now, and is putting the brakes on errant software releases and
pulling back recently released OS and Office releases right and left at the moment.
===================================================
https://www.zdnet.com/article/linus-torvalds-after-big-linux-performance-hit-... 
Linux kernel founder Linus Torvalds: "When performance goes down by 50 percent on some loads, people need to start asking themselves whether it was worth it."
Major slowdowns caused by the new Linux 4.20 kernel have been traced to a mitigation for Spectre variant 2 that Linux founder Linus Torvalds now wants restricted.
As noted by Linux news site Phoronix, the sudden slowdowns have been caused by a newly implemented mitigation called Single Thread Indirect Branch Predictors (STIBP), which is on by default in the Linux 4.20 kernel for Intel systems with up-to-date microcode.
STIBP is one of three possible mitigations Intel added to its firmware updates in response to the Spectre v2 attacks. Others included Indirect Branch Restricted Speculation (IBRS), and Indirect Branch Predictor Barrier (IBPB), which could be enabled by operating-system makers.
STIBP specifically addresses attacks against Intel CPUs that have enabled Hyper Threading, its version of Simultaneous Multithreading (SMT)Speaking of the Wintel boys screwing up all over again (accidentally ???) so much so that their very latest patches that were contributed to the Linux Kernel intended to combat Meltdown and Spectre are now being pulled by Linus himself, acting directly, effective today.
Both Wintel companies are now "a Foundation Level player" in FOSS Linux and
are supposed to be able to be trusted to submit a patch to be included in the next kernel release.
Linus and company had correctly patch fixed Meltdown and Spectre 6 MONTHS ago
(back when Intel was saying it wasn't their processors and MS was saying they had no OS problems to fix) and for the Wintel boys themselves to submit new patches so very very late now, well the patches themselves should have been more thoroughly inspected before being released, AND THE INTEL/MICROSOFT PATCHES SHOULD HAVE BEEN THOROUGHLY VETTED BY THE LINUX SYSTEM MAINTAINERS BEFORE GOING INTO THE LINUX KERNEL with hindsight being all 20-20 as it often is (and as it could be said it is as if some of the black bag boys in the marketing department at Intel may have possibly actually
written some of these particular rotten patches, apparently).
These latest Wintel patches actually cut the overall Linux performance by 30 to 50 percent depending on the actual workload, for no apparent gain in protection over the original patch set put out by Linus and his boys months and months ago that successfully mitigated the issues at a "less than 5 to 10% processing delay" processing effectivity cost.
Linus is saying, politely but bluntly, that simply turning off speculative execution completely and stopping multi-threading completely and removing that entire code block from Linux would have less of a slowdown effect than the recent Wintel patches have done when they are implemented "as submitted". In any case,
all Wintel kernel submissions will now be looked at more carefully in the future because "automatically trusting the guys that built the stuff" really does seem to not be working all that well in the harsh light of reality any more. One of the Wintel boys seems to have become pretty much incompetent at driver programming and the other one of the Wintel boys is struggling in the marketplace so badly their motivations always seem to be somewhat suspect now-a-days.
A repeated theme is still showing up here, that the latest Intel processors really don't get much better, but the tests and the various background systems are getting tweeked by Intel to make it
seem like the newest Intel processor generation is getting a lot better (but really isn't).
Example: you write a 30 to 50% slow down into the patched Linux drivers, then you can magically fix that problem (the one that you actually created) in the next processor generation's software release and then your Marketing Dept. can claim a 45% improvement in processing power ---- does this sound at all familiar to you?
Throw on a couple of extra super fast cores that overheat the chipset (overpower existing laptop cooling systems) and inside 10 minutes thermal throttle the whole mess down to way slower than it was before ---- does this sound at all familiar to you?
Jack all your prices up 50% in early October then for a Black Friday sale you can sell a few of them at the original MSRP as "a really good sale price" ---- does this sound at all familiar to you?
And then you can also tweek the hell out of the testing benchmarks and then hire a lying test house for an additional 15-25% worth of "processing improvement" numbers that you know that Joe Normal type people will all initially see touted very loudly in your initial product release claims, but by the time the press embargoes are all over and
the real benchmark results are being released by independent testers nobody in the buyers marketplace will ever see or ever remember it was all a bunch of lying BOGUS BS to begin with---- does this sound at all familiar to you?
Those end users will just remember reading the original exaggerated claims and they will now see that you have gotten all of those same exaggerated claims printed up now on the outside of the product cartons.
Linus and Linux won't play along with any more bogus lying that you Wintel MMC boys do any more, you sorry ol' Mickey Mouse Club F---up boys, you clumsy clumsy stupid Wintel idiots ......
Since honesty and competence are key parts of being a Linux Foundation Level Member, Microsoft and Intel should both forfeit the Linux Foundation Member title and forfeit the $500,000 Linux Foundation Level membership fee and simply go back to being "standard level" members and get treated that way going forward. If they cannot be trusted to consistently ACT like Foundation Level Members, then they shouldn't hold that title going forward. 
Oh, by the way, on December 3rd (less than TWO WEEKS after angrily slapping his palm and cutting off all the latest Wintel patches, Linus and the boys have finished fixing the new Meltdown and Spectre variants with NEW LINUX KERNEL PROGRAMMING ---- at roughly the same ~5%~ processing penalty cost of the original Meltdown and Spectre patches that they did over six months ago to fix the first wave of Wintel security exposures.