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

Elena 0 Reputation points
2026-10-01T20:42:56.8466667+00:00

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:

  1. 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).
  2. 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).

Microsoft 365 and Office | Word | For business | Windows
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Oleksandr Bashniakov 0 Reputation points
    2026-10-10T15:33:32.2133333+00:00

    Hi!

    I found a workaround for the third-party converter dispatch issue in Word 2609 (Version 2609, Build 16.0.20430.20032, 64-bit).

    1. Set the following registry value to enable the experimental Markdown converter:
      Key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\ExternalFeatureOverrides\word
      Value name: Microsoft.Office.Word.MarkdownFileSupport
      Type: REG_SZ
      Value data: true
    2. Register a dummy text converter under:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Text Converters\Export\Dummy
      using the Name, Extensions, and Path registry values. Set its Name so that it appears alphabetically in the third position, counting from the newly enabled Markdown converter. This allows the second converter (immediately after Markdown), the third converter, and subsequent converters to be invoked correctly.

    The behavior of third-party converters depends on the registered converter names and their alphabetical ordering. The workaround can restore the expected dispatch behavior.

    This appears to be a converter registration/enumeration or dispatch issue in Word 2609. Could Microsoft investigate?

    Was this answer helpful?

    0 comments
  2. 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

  3. Jay1 Tran 1,720 Reputation points Independent Advisor
    2026-10-01T22:09:23.2466667+00:00

    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.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.