Blog Post

Exchange Team Blog
5 MIN READ

Released: February 2019 Quarterly Exchange Updates

The_Exchange_Team's avatar
The_Exchange_Team
Icon for Microsoft rankMicrosoft
Feb 12, 2019
Today we are announcing the availability of quarterly servicing updates, cumulative and update rollups, for all supported versions of Exchange Server. Exchange Server 2010, 2013, 2016 and 2019 all re...
Updated Jul 01, 2019
Version 2.0
announcements
Exchange 2010
Exchange 2013
exchange 2016
exchange 2019
on premises
security
Deleted's avatar
Deleted
Just tried CU12 on our Test Edge box that did have vcredist_x64 installed already but the installed failed with:

Error:

The following error was generated when "$error.Clear();

$dllFile = join-path $RoleInstallPath "bin\ExSMIME.dll";

$regsvr = join-path (join-path $env:SystemRoot system32) regsvr32.exe;

start-SetupProcess -Name:"$regsvr" -Args:"/s `"$dllFile`"" -Timeout:120000;

" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 3.

at Microsoft.Exchange.Management.Tasks.RunProcessBase.InternalProcessRecord()

at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()

at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Deleted's avatar
Deleted
Feb 12, 2019
That is the error you will get if the Visual C++ 2012 runtime is not installed on the Edge Transport server. See the "Important" note in the post above for the link.
  • Deleted's avatar
    Deleted
    Feb 12, 2019
    It's about time Microsoft added that to the prerequisite checker - this is not new.
    • Deleted's avatar
      Deleted
      Feb 12, 2019
      Agreed.
      • Deleted's avatar
        Deleted
        Feb 12, 2019
        FWIW - The pre-req is included in the rules. However, pre-reqs run before actions taken by the MSI installer are completed. As Exchange was silently installing the pre-req previously, when we apply the CU upgrade that stops silently installing the binaries, the MSI removes on the next upgrade. This occurs after the pre-req engine has run. So we have a chicken and egg situation, where we detect something is installed that the MSI installer is going to remove. That is why we have the note to make certain that the package is installed before invoking setup to avoid the collision caused by the MSI installer removing the previous version.