October DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsClean PCRecommendedOne scan can reveal what keeps slowing WindowsLook for cleanup and repair opportunities.Run ScanOctober DealsAmazon USDeal season is back - check today's better picksAmazon US: current deals, useful picks and tech finds.See Picks×
Skip to content
World desk4 min

How to Install the September 2026 Exchange V2 Security Update and Verify It

A practical guide to selecting the September 2026 Exchange V2 update for the correct server and CU, installing it, verifying the result, and troubleshooting common failures.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To install the September 2026 Exchange V2 security update, first match the package to the server’s Exchange generation and cumulative update (CU), then install the Microsoft package for that exact version and CU. Restart before and after installation, and verify the result with Exchange Health Checker, the server’s file version, service status, and OWA/ECP tests—not just the installer’s success message.

“V2” is not a unique package identifier. Microsoft says the September 2026 V2 release adds CVE-2026-96940 to the original September release. Exchange 2016 and Exchange 2019 updates released from May through October 2026 are limited to Period 2 Extended Security Update (ESU) program customers. Confirm the applicable package and eligibility on Microsoft’s Exchange update history and its matching KB page before scheduling work.

As an Amazon Associate I earn from qualifying purchases.

Identify the right Exchange V2 update before installing

Start by recording the Exchange generation, installed CU, current build, and detected security update or interim update (IU) on every server. Select the September 2026 V2 package for that exact product and CU from Microsoft’s release announcement and corresponding KB/download page. An update made for a different CU may not apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Microsoft’s release announcement says the V2 release adds CVE-2026-96940 compared with the original September release. Do not choose a package by the “V2” label alone: verify its Exchange version, CU, KB identity, and release version in Microsoft’s current documentation. Exact September 2026 V2 KB/build combinations for Exchange 2016 and 2019 should be taken from the matching Microsoft KB rather than inferred from a general build list.

Exchange generation What to confirm before installation Eligibility or identifier guidance
Exchange Server Subscription Edition (SE) Installed CU and the September 2026 V2 package listed for that CU Use the matching Microsoft release announcement and KB/download page for the package identifier.
Exchange Server 2019 Installed CU and the September 2026 V2 package listed for that CU Microsoft limits updates released May–October 2026 to Period 2 ESU customers. Confirm enrollment and package access.
Exchange Server 2016 Installed CU and the September 2026 V2 package listed for that CU Microsoft limits updates released May–October 2026 to Period 2 ESU customers. Confirm enrollment and package access.

Use Microsoft Exchange Health Checker to inventory the environment before making the selection. It reports Exchange version/build information and can identify servers behind on CUs or security updates, as well as required manual actions. Microsoft also recommends installing security updates on machines that have only the Exchange Management Tools.

Prepare the server and maintenance window

Schedule work around the topology and workload, and follow the prerequisites in the specific update’s Microsoft KB. Preserve your organization’s normal backup and operational safeguards. There is no single maintenance-mode or antivirus procedure established for every Exchange deployment.

  1. Run Exchange Health Checker and record each server’s Exchange generation, CU, build, and detected IU or security hotfix.
  2. Confirm Period 2 ESU eligibility for Exchange 2016 or 2019 when the update falls within May–October 2026, and obtain the correct package through Microsoft’s applicable KB/download route.
  3. Restart the Exchange server before applying the update, as Microsoft recommends.

Install the matching package

Use the administrative rights and installation steps documented in the package’s Microsoft KB. Do not reuse a command from another Exchange generation or CU; there is no one universal install command appropriate for every package. Allow setup to complete, then restart the server even if the installer does not prompt for a restart.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

After the restart, check that the Exchange services that should be active in your environment have started. Microsoft includes this service check in its post-setup guidance.

Verify the installed update and Exchange health

Run Health Checker again

Run Exchange Health Checker after installation. In its Exchange Information section, review Build Number and Exchange IU or Security Hotfix Detected. Also review any manual actions it flags. Compare the reported information with the entry for the same Exchange generation and CU in Microsoft’s Exchange build numbers and release dates and the exact update KB.

Check the ExSetup.exe file version

From the Exchange Management Shell, Microsoft documents this command for displaying the ExSetup.exe file version:

Get-Command Exsetup.exe | ForEach-Object {$_.FileVersionInfo}

Compare the output with the Microsoft build entry for the server’s Exchange generation and CU. Microsoft’s build table lists the Exchange SE RTM September 2026 SU as 15.2.2562.49 (15.02.2562.049) and Exchange 2019 CU15 September 2026 SU as 15.2.1748.51 (15.02.1748.051). Those entries alone do not establish whether the later V2 re-release is distinguishable by build string, so confirm the package-specific result in the matching KB and Health Checker output.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion reports the CU version; it does not by itself prove which SU or hotfix is installed.

Check services and client access

Confirm the expected Exchange services are running, then test Outlook on the web (OWA) and the Exchange admin center (ECP). To confirm a particular CVE is addressed, consult the matching Microsoft KB or the relevant entry in the Microsoft Security Update Guide. Do not treat a general build display as proof of remediation if Microsoft specifies additional steps.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Troubleshoot installation or OWA/ECP failures

Windows Installer says the upgrade patch cannot be installed

If Windows Installer reports that the upgrade patch cannot be installed because the target program may be missing or is a different version, compare the server’s installed CU with the SU package. Microsoft identifies a CU/SU mismatch as a cause. Obtain the SU that matches the installed CU, or follow Microsoft’s supported CU path before applying an update intended for another CU.

OWA or ECP returns HTTP 500 after the update

Microsoft’s OWA/ECP HTTP 500 troubleshooting article documents reinstalling the security update from an elevated command prompt, restarting, and testing access again as an initial remedy. If ECP continues to fail, follow the article’s recovery steps, which include checking the ECP virtual directory’s BinsearchFolder paths, running UpdateCas.ps1 and UpdateConfigFiles.ps1, running iisreset, and restarting. Use paths that match the actual Exchange installation; example paths in Microsoft’s article are not universal.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

An interrupted update leaves services stopped or disabled

Use Microsoft’s Exchange update troubleshooting guidance and setup logs to diagnose a failed or interrupted installation. Restore only services that were active before setup; POP3 and IMAP4 are normally disabled unless the environment uses them.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More from the Wire

  1. World desk4 min
    How to Spot an AI Voice Scam Before Sending MoneyDon’t rely on how a caller sounds. Pause, call back through a known number, and verify the emergency with another trusted person before sending money.
  2. Mountain View desk4 min
    Google’s SynthID Detector: How to Check AI-Generated Images, Video and AudioGoogle’s SynthID Detector looks for an embedded watermark in supported images, video and audio. Here is what its results do—and do not—show.
  3. Redmond desk20 min
    How to create a link to File or Folder in Windows 11Windows 11 gives you several ways to point to a file or folder without moving or duplicating it. You can create a desktop shortcut,…
Recommended PC Tool
Recommended PC Tool
Windows Errors? Fix Them Before They SpreadFree repair scan
Outdated Drivers Are Slowing You DownFree scan - exact matches

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.