Word 2609: Save As via registered OOXML export converter silently fails (no error, no file)

Question

Word 2609: Save As via registered OOXML export converter silently fails (no error, no file)

Elena 0

Environment: Word for Microsoft 365, Version 2609 (verified 16.0.20430.20118, x64, Current Channel, Windows 11). Regression from Version 2608 (16.0.20326), which works.

Repro:

Install any third-party Open XML Format external file converter registered per the documented interface (dd300649) under HKLM\Software\Microsoft\Office\16.0\Word\Text Converters\OOXML Converters\Export. Example: Writage (Markdown converter, writage.com, free trial).
New document → F12 → Save as type: "Markdown (*.md)" → Save → Yes on the compatibility prompt.

Expected: converter is invoked, .md file written (2608 behavior). Actual: Word returns to the document/dialog. No file, no error.

Diagnostics already done (ProcMon + converter-side logging):

Word completes the dialog flow, shows the compatibility prompt, probes the target path, creates ~WRDxxxx.tmp beside it — then writes nothing, deletes the tmp, and abandons the save. It never performs the FileBlock OoxmlConverters check, never requests activation of the converter CLSID from RPCSS, never calls HrInitConverter.
Not a converter defect: on the same 2609 build, Document.SaveAs2(path, <converter SaveFormat>) via the object model and Ctrl+S on an opened .md both invoke the converter correctly (out-of-process in DllHost per its AppID/DllSurrogate registration).
Behavior is controlled by the Microsoft.Office.Word.MarkdownFileSupport feature gate: forcing it true via ExternalFeatureOverrides makes Save As produce the .md through Word's new native Markdown writer instead. With the gate in its default (off) state, the Save As path has no fallback to the registered export converter - it just aborts.
This matches the acknowledged 2609 Save As regression family: "Users cannot use Save As to create PDFs and store them in SharePoint" (silent failure, fixed by service change 2026-09-25) and the silent Save As → Plain Text reports on Microsoft Q&A.

Impact: every user of every third-party OOXML export converter loses Save As on 2609.

Request: restore fallback to registered OOXML export converters, as was done for the PDF case (https://support.microsoft.com/en-us/support/known-issues/cannot-create-saveaspdf-word).

0 comments

2 answers

Your answer

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Jay1 Tran 1,700 Independent Advisor

Hi Elena,

Thank you for providing such detailed diagnostics and reproduction steps.

Microsoft has confirmed that the Word Version 2609 Save As issue has been fixed, and the corresponding service update was rolled out on September 25, 2026.

If you are still experiencing the same behavior, please close all open Microsoft Office applications, including Word, Excel, Outlook, and PowerPoint. Once every Office application has been fully closed, reopen Microsoft Word and test the Save As operation again. This allows Word to start a new session and ensures that the latest service-side change has been picked up.

If the issue remains after reopening Word, restart Windows and test the operation once more. You may also verify under File > Account > About Word that you are using the latest available Current Channel build.

For more information, please refer to: Users cannot use Save As to create PDFs and store them in SharePoint in Word for Windows | Microsof…

Thank you for your time and patience. Wishing you a great day ahead.

Elena 0 Reputation points

2026-10-02T09:18:08.3466667+00:00
Dear Support Team,

Thank you for getting back to me, but unfortunately, this response addresses a different issue: the previously fixed Save As to PDF/SharePoint regression, not the issue I reported.

My report concerns Word 2609 silently failing to invoke registered third-party OOXML export converters during the interactive Save As workflow. In my case, this affects Writage, a Markdown converter, where users can no longer use the "Save As" → Markdown (*.md) even when saving to a local file.

Writage is still working correctly: it is invoked via Document.SaveAs2(...) and via Ctrl+S on an already opened .md file. The failure is specific to Word 2609’s interactive "Save As" path.

The linked PDF/SharePoint fix does not resolve this problem. Please review this as a separate issue affecting registered OOXML export converters, including Writage’s Markdown export.

Windows version: 11 Pro v.10.0.22621 Build 22621

MS Word version: 2609 (Build 20430.20118 Click-to-Run)

Many thanks!
Jay1 Tran 1,700 Reputation points Independent Advisor

2026-10-04T22:12:50.4+00:00

Hi Elena,

Thank you for following up and for providing the additional clarification regarding the specific Save As workflow you are experiencing.

Given the detailed diagnostics you have already performed, including testing Document.SaveAs2(...), Ctrl+S on an existing .md file, and comparing the behavior between Word 2608 and 2609, this scenario would require further investigation beyond the troubleshooting that can reasonably be performed here.

At this point, I recommend asking your IT administrator to create a support ticket with Microsoft Support through the Microsoft 365 admin center. This will allow the issue to be reviewed in more detail and escalated to the appropriate Word engineering team if necessary.

When submitting the ticket, please include the reproduction steps and diagnostics you have already collected, particularly the Word version comparison, ProcMon results, and converter-side logging. This information should help the support team investigate the behavior more efficiently without requiring you to repeat the troubleshooting already completed.

In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support

For instructions on submitting a support request, please refer to: Get support - Microsoft 365 admin | Microsoft Learn.

Thank you for your patience and for providing such comprehensive technical details.