Microsoft Pulls Botched Updates KB4461522 and KB2863821

[nir]

Both patches said to cause crashes in various apps

Two of the updates that Microsoft released earlier this month have officially been pulled after the company acknowledged bugs potentially causing app crashes.

As I reported today, update KB4461529 breaks down Microsoft Outlook 2010 and generates a crash just after launch. However, Microsoft hasn’t pulled this patch given its security nature, but the company recommends users to wait for a fix and switch to the web-based version of Outlook.

Recently, however, the software giant acknowledged that two other updates, namely KB4461522 and KB2863821, are causing similar app crashes as well, but in this case, the firm decided to retire both of them until a fix is ready.

Both updates are released for Microsoft Office 2010 Service Pack 2, and according to their official KB pages linked above, they come with the following improvements:

“This update makes some changes for the Japanese calendar in Office 2010 so that the new Japanese era name can be displayed correctly when a new era begins. Additional updates may be required for Office applications because of expected changes in the Japanese era. We will update this article as necessary.”

Uninstall the update

However, Microsoft has acknowledged in an update posted on the KB pages that the update was pulled due to crashes caused to some apps.

“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 says.

If you hit the said crashes, you are recommended to remove the updates as soon as possible, though it goes without saying that you’re going to lose the fixes that Microsoft detailed above.

There’s no ETA for a fix or when the updates may be re-released without the said bugs, so for now, the only option is to remove the botched patch and wait until Microsoft shares more details.

Source

[steven36]

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.

 

Source

[Karlston]

I don't think these botched updates are the only things Microsoft is pulling.

[BimBamSmash]

One can only be a tough SOB to take up a job that requires keeping a decade-old code up-to-date to address all modern threats, without changing the code's foundations, and under strict time constraints.