Hi

We are having an issue with WSUS trying to install updates for Outlook Social Connector 2013 (KB3054854) and Outlook (KB2956170) even though we do not have Outlook installed as part of our 2013 Office install.

Naturally when the update is actually installed it errors with a detection error.

Is there a way of determining why the WU client is detecting that outlook is installed or blocking it? Is this a problem with the detection logic of the update perhaps?

We do have lots of outlook installed elsewhere so cannot just unapproved the updates.

Thanks for any thoughts.

Andy

Hi,

By "Naturally when the update is actually installed it errors with a detection error." What is the error message?

This behavior seems to be by design, Outlook may have some core components that are shared with other Office applications, even Outlook is not enabled in the installation, some of these components are still needed by other applications, this may be why the updates are needed even Outlook is not enabled.

Regards,

Melon Chen
TechNet Community Su

Hi thanks for your input.

Yup, understood and this would be ok if the update didn't then throw a "detection" error which presumably means it cannot detect outlook. :-)

To eliminate a problem with WSUS I have downloaded the updates and tried to apply manually. The error I get is OPatchInstall: Property 'PACKAGE.PROMPT.DETECTIONERROR' value 'An error occurred while running detection.'

The office update log file is here: https://onedrive.live.com/redir?resid=625831E6D0D131F0!12856&authkey=!ACJwx3DiN_1cSJY&ithint=file%2clog

Is there a better log I should be looking at?

We have all language packs installed and I have also just noticed that the Office setup program as run from add/remove programs uninstall\change is not running either.

Corrupt Install?

Andy

Hi,

Is the issue you described on one machine or all users' machines? If the Setup program can't be started on only one machine, it seems the installation is corrupted, you may need to use the Fix it tool:

https://support.office.com/en-ca/article/Uninstall-Office-2013-or-Office-365-from-a-Windows-computer-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8

Check if this will also fix the detection error.

Regards,

Melon Chen
TechNet Community Su