Office non-security patches are here

Topic

New Reply

No, you don’t want to install them yet. Office 2010 Update for Microsoft Office 2010 (KB3128031) Update for Microsoft Outlook 2010 (KB3191906) Office
[See the full post at: Office non-security patches are here]

2 users thanked author for this post.

Fred

Reply | Quote

Replies

Maybe they should patch their employees’ literary skills:

“May 2, 2017, update for Office 2010 (KB3128031)

Improves the robustness to make sure that the stability of Office 2010 applications in certain scenarios.”

Windows 10 Home 22H2, Acer Aspire TC-1660 desktop + LibreOffice, non-techie

2 users thanked author for this post.

SueW

Reply | Quote

Perfect wording – for a Mystery.

-Noel

Reply | Quote

All .NET versions got separate updates through catalog only

“After you apply the April 2017 security updates that are described in Microsoft security update guidance CVE-2017-0160, the Windows PowerShell v3.0+ stop-computer command fails. When this issue occurs, you receive a “Privilege not held” error message. This update provides a resolution to this issue.”

1 user thanked author for this post.

Reply | Quote

So they fixed the stop-computer error. Great.

The .NET updates – there are many – appear in the Windows Update and WSUS list. As you say, it looks like they’re Catalog-only, so folks won’t be seeing them in Windows Update. Yet.

1 user thanked author for this post.

Reply | Quote

Nothing for 2007 this month?

Reply | Quote

Office 2010, 2013 and 2016 only

Reply | Quote

It only gets security updates

even 2010 is hardly getting non-security updates

1 user thanked author for this post.

Ed

Reply | Quote

Thanks for jump-starting my lonesome brain cell abbodi! With the words “non-security patches” right there in the title of the post it appears I need to take a refresher course on reading comprehension!

Reply | Quote

One of my Excel 2010 workbooks failed to run Workbook_Open code after installing this months Office 2010 updates. After uninstalling and reinstalling individually, I traced the problem to:

Update for Microsoft Office 2010 KB3128031

Strangely, while that workbook failed, a new test workbook with a simple message called from Workbook_Open did run.

Copying all sheets and code to a new workbook did not fix the problem.

 

Microsoft now seems to have pulled the update but my Windows 7 update still offered it tonight. It is now hidden.

Edit to remove HTML

1 user thanked author for this post.

PKCano

Reply | Quote