Microsoft 365 Current Channel Version 2609 build 20430.20182 rolls out

Microsoft 365 Current Channel Version 2609 Build 20430.20182 started reaching devices this week, dated October 13, 2026, and Microsoft's update-size page now lists it as the most current Current Channel release (Microsoft Learn, today). 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 the notice doesn't name Build 20430.20182 specifically for those two channels (Microsoft 365 Message Center Archive, today).

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 Current Channel release and start deploying it now, according to the same Message Center notice (Microsoft 365 Message Center Archive, today).

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 (Microsoft Q&A, 2 weeks ago; Microsoft Q&A, 3 weeks ago). Neither Microsoft Q&A thread, nor Microsoft's own update pages, identify these as known issues or confirmed fixes for Build 20430.20182, which is the gap the rest of this piece covers.

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 now Build 20430.20182 on October 13, marked as the current Current Channel build (Microsoft Learn, today). The two earlier builds carry listed download sizes of 51 MB and 48 MB respectively; no size is posted yet for Build 20430.20182.

Microsoft hasn't published separate Current Channel release notes detailing what changed inside this build. The cited update-size page lists the build and its release date but not a changelog, fixed-issue list, or feature summary, so anyone trying to confirm whether a specific bug was addressed has to rely on secondary reporting rather than an official list.

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 any 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. A 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 fine on Version 2608 (Microsoft Q&A, 2 weeks ago).

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, which the reporter interpreted 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, though that explanation reflects the reporter's own analysis rather than something Microsoft has documented publicly (Microsoft Q&A, 2 weeks ago).

The thread places this alongside other reported Version 2609 Save As failures, including a separate case where PDF exports to SharePoint failed silently. A reply in that thread says a service-side change addressing the SharePoint PDF issue rolled out on September 25, 2026, a date that predates Build 20430.20118's own release, and describes it as a backend change rather than something tied to one client build (Microsoft Q&A, 2 weeks ago). The Microsoft material cited here doesn't identify the registered-converter scenario as covered by that fix, 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 actually 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 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, and other files in the same OneDrive location showed the identical crash (Microsoft Q&A, 3 weeks ago).

Multiple users in the thread reported matching Event Viewer details: EXCEL.EXE and Rtc.dll both at version 16.0.20430.20092, exception code 0xc0000005, and a fault offset of 0x000000000024177e (Microsoft Q&A, 3 weeks ago). That matching signature across separate reports is a reasonable sign the issue wasn't limited to one machine, though it still isn't the same thing as a Microsoft-confirmed defect.

Reporters said the usual fixes, repairing the Microsoft 365 install, resetting or unlinking and relinking OneDrive, disabling add-ins, and rebooting, didn't change anything. The original poster said rolling back to Version 2608 Build 20326.20158 resolved the crash immediately, with OneDrive files opening normally afterward, though 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 (Microsoft Q&A, 3 weeks ago).

This crash was reported on Build 20430.20092, not the October 13 release. The Microsoft material cited here doesn't identify this as a known issue or 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, since both reported client failures are tied to specific builds, while the September 25 service-side change is a separate backend fix rather than something tied to one build number (Microsoft Learn, today).

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 actually relies on.

Microsoft's Message Center notice confirms that organizations managing updates directly can download Build 20430.20182 and begin deployment now (Microsoft 365 Message Center Archive, today). Piloting the build on a small group before a full rollout is a reasonable precaution given the two unresolved reports above, though that's editorial guidance rather than something 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 the issue is fixed or absent. Check Microsoft's Current Channel update-size page, update history, Message Center notices, and any support or release-health 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.