Microsoft 365 Current Channel Version 2609 Build 20430.20182 Rolls Out

Microsoft 365 Current Channel Version 2609 Build 20430.20182 started reaching devices on October 13, 2026, and Microsoft's update-size page lists it as the most current Current Channel release.

Microsoft also announced updates for Monthly Enterprise Channel and Semi-Annual Enterprise Channel users as part of the same gradual rollout, which began October 13 Pacific time, though those channels use different build numbers.

Microsoft says devices configured to update automatically through the Office Content Delivery Network don't need to do anything. Admins who manage updates directly can download the latest release for their channel and start deploying it now, according to Microsoft's Message Center notice, published October 14.

This Microsoft 365 Apps Current Channel October 2026 update arrives after two community-reported problems tied to earlier Version 2609 builds. One affects Word users on Windows 11 who rely on a registered third-party OOXML export converter for Save As. The other affects Microsoft 365 Apps for business customers running Excel on Windows, specifically workbooks stored in OneDrive on Build 20430.20092.

Neither Microsoft Q&A thread identifies these as confirmed fixes for Build 20430.20182. Microsoft's official release notes do document separate Excel and Outlook crash fixes, but don't specifically address the two reported regressions.

What Microsoft 365 Current Channel Version 2609 Build 20430.20182 confirms

Microsoft's update-size page lists a tight sequence leading into this release: Build 20430.20118 on September 30, Build 20430.20146 on October 6, and Build 20430.20182 on October 13, marked as the current Current Channel build.

The two earlier builds carry listed download sizes of 51 MB and 48 MB respectively when updating to the October 13 release. Microsoft hasn't posted a separate download-size figure for the new build itself. Its figures are approximate and apply to specific update paths for the English-language 64-bit version of Microsoft 365 Apps.

Microsoft has also published Current Channel release notes detailing two fixes in Build 20430.20182:

• Excel: Fixed an issue that could cause Excel to close unexpectedly after coauthoring in a workbook.

• Outlook: Fixed an issue that could cause Outlook to exit unexpectedly while searching for users.

Those are the two resolved issues Microsoft explicitly lists for the October 13 Current Channel release. Neither description confirms a fix for the OneDrive-related Excel crash or Word's third-party converter failure discussed below.

The October 13 updates also have distinct build numbers for other channels. Microsoft's update-size page lists Build 20430.20180 for Monthly Enterprise Channel and Build 20430.20178 for Semi-Annual Enterprise Channel.

Because the rollout is staged, not every device will pick up Build 20430.20182 at the same time. The simplest way to confirm what's actually installed is to open File > Account in Word, Excel, or another Microsoft 365 app and check the version number directly, rather than assuming the update already applied.

Why the Word Save As regression still matters

This one matters specifically to Word users on Windows 11, Current Channel, who save files through a registered third-party OOXML export converter rather than Word's built-in formats.

An October 1 Microsoft Q&A report describes Word Version 2609 Build 20430.20118, verified as 16.0.20430.20118, x64, silently failing to complete Save As through that kind of converter: no file gets written, no error appears, and the same action worked on Version 2608.

The reporter's own testing narrowed the cause further. Saving through the Document.SaveAs2 method in the object model, or using Ctrl+S on a file already open, both invoked the converter correctly.

The reporter interpreted that as evidence that the problem sits specifically in how the Save As dialog initiates conversion rather than in the converter itself.

The thread attributes the failure to the Microsoft.Office.Word.MarkdownFileSupport feature gate, saying that with it in its default off state, Save As has no fallback to the registered converter and simply aborts.

That explanation reflects the reporter's analysis rather than a root cause Microsoft has publicly confirmed.

The thread places this alongside other reported Version 2609 Save As failures, including a separate case where PDF exports to SharePoint failed silently.

An independent advisor's reply says a service-side change addressing the SharePoint PDF issue rolled out on September 25, 2026, a date that predates Build 20430.20118's release, and describes it as a backend change rather than something tied to one client build.

The original reporter subsequently clarified that the SharePoint PDF fix addressed a different issue, not the registered-converter failure.

Microsoft's October 13 release notes don't identify the registered-converter scenario as fixed or confirm how it behaves on Build 20430.20182.

If a workflow depends on a registered OOXML export converter, a practical test before trusting Build 20430.20182 with it is straightforward: save a representative file through that exact converter, confirm the output file exists on disk, and reopen it to check the content came through intact.

Excel crashes with OneDrive files: what changed, and on which build

This report is narrower than it sounds: it applies to Microsoft 365 Apps for business on Windows, Current Channel, specifically when opening Excel files stored in OneDrive.

A September 24 Microsoft Q&A thread describes Excel crashing immediately after opening OneDrive-hosted workbooks following an update to Version 2609 Build 20430.20092, while the same file opened normally once copied to a local folder.

Other files in the same OneDrive location showed the identical crash.

The thread includes Event Viewer details identifying EXCEL.EXE and Rtc.dll at version 16.0.20430.20092, exception code 0xc0000005, and a fault offset of 0x000000000024177e.

Those details provide a useful signature for troubleshooting, though they don't establish that every Excel crash involving OneDrive has the same cause.

The original poster said the usual fixes, repairing the Microsoft 365 installation, resetting or unlinking and relinking OneDrive, disabling add-ins, and rebooting, didn't change anything.

Rolling back to Version 2608 Build 20326.20158 reportedly resolved the crash immediately, with OneDrive files opening normally afterward.

The thread frames that rollback as a community workaround rather than a Microsoft-recommended fix, since Office may reapply the newer build depending on how an organization manages updates.

This crash was reported on Build 20430.20092, not the October 13 release.

Microsoft's new release notes do confirm an Excel crash fix, but the description specifically concerns Excel closing unexpectedly after coauthoring in a workbook. It doesn't establish that the OneDrive-related Rtc.dll crash was addressed.

The available Microsoft documentation therefore doesn't identify the OneDrive crash as a confirmed fix for Build 20430.20182.

What to check before deploying Build 20430.20182

Confirming the actual installed build matters more than trusting the Version 2609 label on its own.

Open File > Account in Word or Excel to see whether a device is on Build 20430.20182, 20430.20146, 20430.20118, or still 20430.20092.

Both reported client failures are tied to specific earlier builds, while the September 25 service-side change concerning SharePoint PDF exports is separate from those client build numbers.

For a managed deployment, a sensible precaution is to test the two workflows these reports touch before rolling out widely: opening and editing Excel workbooks stored in OneDrive, and running Word Save As through any third-party OOXML export converters a team relies on.

Microsoft's Message Center notice confirms that organizations managing updates directly can download the latest releases for their configured channels and begin deployment.

Piloting Build 20430.20182 on a small group before a full Current Channel rollout is a reasonable precaution given the two reports, though that's editorial guidance rather than a requirement Microsoft states directly.

If either the Excel crash or the Word Save As failure shows up again on Build 20430.20182, treat the Microsoft Q&A threads as community evidence, not proof that the issue is fixed or widespread.

Check Microsoft's Current Channel release notes, update history, Message Center notices, and relevant support advisories before drawing a conclusion.

Automatic-update users can let the rollout proceed and spot-check Word Save As and OneDrive-based Excel files once Build 20430.20182 lands.

Managed environments should confirm the installed build through File > Account, pilot it before a full push, and watch Microsoft's official update pages rather than a single forum thread for the final word on either regression.