Office non-security patches for July 2017 are here

Topic

New Reply

No, you don’t want to install them yet, even if we are on DECFON 3. Office 2013 Update for Microsoft Word 2013 (KB3213567) Update for Skype for Busine
[See the full post at: Office non-security patches for July 2017 are here]

2 users thanked author for this post.

Elly, ch100

Reply | Quote

Replies

Office 2010 still gets non-security patches, hardly

2 users thanked author for this post.

ch100, PKCano

Reply | Quote

I didn’t realize that office 2010 did not get non security patches.. Though I see a few patches in May 2017 and Dec 2016? So what is the official stance? Like shouldn’t they have released the 32Bit Outlook 2010 patch today to fix the attachment issues?

Reply | Quote

You are correct. Office 2010 does get non security updates. But there were none offered today. I will correct the post momentarily. Thanks

1 user thanked author for this post.

SueW

Reply | Quote

I am running Office 2016 on two Win10 Pro machines and I am at a loss as to how to determine what patches have been applied . . .

Am I correct that there is no way to tell?

Thanks!

Reply | Quote

You don’t need to know
Install what is available when you decide to update.

Reply | Quote

I believe the information you seek (on how to determine installed updates) is located on the MS KB3213547 page @pkcano linked for WinX Office 2016 update

1 user thanked author for this post.

ch100

Reply | Quote

It is actually complicated due to newer updates being cumulative and hiding in the list their superseded updates. When a newer update is uninstalled, sometimes older updates come back in the list of installed updates.
There is delta updating involved and the date of older updates can change to the current date.
This is why it is easier to say what is missing than what is installed, by scanning against Microsoft Update.
And for all practical purposes, this is all that matters.

Reply | Quote

Thx for that explanation

Am I correct in my assumption that the Office Version “Build Number” is the important factor, for determining whether it is updated properly?

I don’t keep an eye on the build number on mine, sorry! but I won’t be installing this month’s Off2013 update on my machine, as I don’t use the Dutch version/translation that it relates to.

Reply | Quote

It does not matter what you use or do not use. As long as it is offered, then some internal detection mechanism has determined that it is needed. I am generally not getting concerned with this level of detail, but rather with the end result. For my purpose, Windows Update/WSUS are authoritative.
The Office build number depends on few factors.
If you look at the current Microsoft documentation for Office update, all patches for a month are presented together as CU.
https://blogs.technet.microsoft.com/messaging_with_communications/2017/07/03/current-cumulative-updates-for-office-q3-2017/
https://support.office.com/en-us/article/Office-Updates-a118ec61-f007-492f-bfa5-5a6f764d5471
They act as a group. I don’t know what happens when only some of the patches are applied, while others are not. Would the build number for Word be different than for Excel for example?
When Visio and/or Project are installed in addition to the main Office suite, patches for what seems to apply to one product, apply at the same time to other products, while sometimes there are duplicates in the list.
Office Update is based on Microsoft Installer which I think is very much like the XP style of updating and totally different than what is known as CBS starting with Vista. CBS is the current model of updating Windows and in a larger sense how Windows is constructed from modules.
If @abbodi86 read this, I think he would be able to provide more insight at the level of detail which does not concern me so much.

Reply | Quote

Old article, still current as contents about correct Office patching
https://blogs.technet.microsoft.com/messaging_with_communications/2011/08/04/keeping-up-with-office-updates/

1 user thanked author for this post.

MrBrian

Reply | Quote

All Office updates are cumulatives for the product/component they patch, which is determined by the file name
meaning as example, latest word2013-kb3213567 update replaces all previous Word 2013 updates

traditional MSI Office installation overall version does not get updated or changed with individual patches, only a Service Pack change it
however, the individual patches changes the build version for the components/files they update
example, latest word2013-kb3213567 update is 15.0.4945.1000, whereas Office 2013 SP1 version still 15.0.4569.1506

of course you would need all latest individual updates for the products you have to get current
https://support.office.com/en-us/article/Update-history-for-Office-2013-19214f38-85b7-4734-b2f8-a6a598bb0117

2 users thanked author for this post.

ch100, Kirsty

Reply | Quote

@abbodi86
If I check the catalog or WSUS for supersedence, it is not handled exactly as you mentioned here. It is largely consistent every 1-2 months but not entirely.
Does this mean that either the supersedence is not correctly updated in metadata for each patch or those updates to which I made reference refer mostly to Office as a whole and not to separate products?
I am normally not concerned with individual patches, but I would like to reduce the numbers of those installed at any time on the machine by having only the latest required and not keeping the old one which bloat the machine.
You posted in the past ways of removing old office patches which are convoluted and not supported in general and I will post another one here, easy to use which is HomeDev’s PatchCleaner, not supported officially and risky
http://www.homedev.com.au/free/patchcleaner

Reply | Quote

Yes i know, metadata supersedence doesn’t always reflect the true supersedence chain
specially for Office updates, were Security Update is never marked as superseded by a General Update (there could be a special exceptions)

but the Windows Installer / Windows Update is smart enough to calculate supersedence based on product patches version

thanks for that
yeah, all methods seems to be risky and needs a closer look to be sure

1 user thanked author for this post.

ch100

Reply | Quote

FWIW, Preston Gralla has written an article that comprehensively covers all of the updates to date for Office 365 / 2016: https://tinyurl.com/y9v2alnv&lt
Edit to remove HTML

Reply | Quote

There were no updates listed for Office 2010

Not having had an Office 2010 problem in quite a while, I actually found that comforting.

I take that back, I DID have an Office 2010 problem… It came about because a few months ago an update to Office 2010 broke the ability to double-click a .xls file and have it open in Excel (which is fixed by disabling DDE for .xls files via the registry).

So… Yeah, I’m feeling good about Office 2010 not getting updates this time around.

-Noel

1 user thanked author for this post.

samak

Reply | Quote

“I actually found that comforting”

Me too!

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

Reply | Quote

Is it safe to install Silverlight Security Patches?

Reply | Quote

The answer is in two parts.

1. Is it safe to install Silverlight?
Only if you use it. Otherwise the general opinion is to avoid it.
I routinely install it for convenience because there are (rarely) web sites requiring it.

2. Is it safe to install Silverlight patches?
They are offered only if you first install Silverlight.
It is UNSAFE TO AVOID Silverlight patches.

3 users thanked author for this post.

SueW, Microfix, Kirsty

Reply | Quote

I got offered the Silverlight patch even though I uninstalled Silverlight at least 2 years ago!

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

Reply | Quote

Silverlight leaves multitudes of registry entries once uninstalled. Once silverlight is uninstalled, press the ‘Windows’ an ‘R’ keys to access the run command.

Type ‘regedit’ into your run command and [Enter]

Within regedit, press ‘ctrl’ and ‘f’ keys doing a search for ‘silverlight’ within regedit then press ‘F3’ for the next item…and so on

Windows - commercial by definition and now function...

2 users thanked author for this post.

samak, ch100

Reply | Quote

Wow !  I have hundreds of entries in HKEY_CLASSES_ROOT\Installer\Assemblies

All seem to be referring to items like

c:|Program Files (x86)|Microsoft Silverlight|3.0.40624.0|de|Microsoft.VisualBasic.resources.dll

c:|Program Files (x86)|Microsoft Silverlight|3.0.40624.0|de|mscorlib.resources.dll

c:|Program Files (x86)|Microsoft Silverlight|3.0.40624.0|de|system.resources.dll

 

Is it safe to delete the lot of them?

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

Reply | Quote

ch100 wrote:

1. Is it safe to install Silverlight? Only if you use it. Otherwise the general opinion is to avoid it.

The general opinion part is great advice

Windows - commercial by definition and now function...

Reply | Quote

They finally patched the patch to patch the issues that the June sec update KB3203467 caused in Outlook 2010 (32-bit).
If you remember, they released patch KB3015545 which broke even more and was pulled…. now, that patch has been superseded with KB4011042.

Normally I wouldn’t touch these, but since several of our users have had broken Outlook clients for 2 weeks…we’ll be installing these as-needed over the next few days.

1 user thanked author for this post.

SueW

Reply | Quote