SharePoint Document Issues

Fix SharePoint Document ID Only Showing After Opening Word File Twice

Ayan Masood Sep 25, 2026 869 views

Question details

Users need to open a Word document twice to see the SharePoint Document ID.

SharePoint Document ID Appears Only After Opening a Word File Twice

Product: SharePoint Server 2019 / Microsoft Word
Device & OS: not provided
Scenario: Accessing Word documents from SharePoint Server 2019 on-premises libraries with multiple content types enabled.
Observed behavior: The Document ID fails to display on the first open but successfully appears upon opening the document a second time.

Before you start

Confirm the exact build of your SharePoint Server 2019 on-premises environment and verify your content type configurations before escalating the issue.

Solution 1Recommended

Isolate the Issue and Report to Microsoft Q&A

Since this is a server-specific issue not resolved by standard Office repairs, gathering environment details and escalating to SharePoint Server experts is the most effective approach.

This behavior has been identified specifically in SharePoint Server 2019 on-premises (e.g., build 16.0.10404.20003) and cannot be reproduced in SharePoint Online. Because users on the same Word version experience different results, local client troubleshooting is ineffective.

Note Environment Details

Document your exact SharePoint Server 2019 build number and the specific Microsoft Word version your affected users are running.

Create a Test Library

Create a standard, out-of-the-box document library in your SharePoint environment and enable management of content types to see if the issue is library-specific.

Post to Microsoft Q&A

Visit the Microsoft Q&A platform, tag your post with 'SharePoint Server', and provide the reproduction steps along with your build and content type configuration details.

Isolate the Issue and Report to Microsoft Q&A

Office Repair Ineffective: Repairing Microsoft Office installations will not resolve this issue, as it is rooted in how the SharePoint Server pushes content type metadata to the client, not a corrupted Word installation.

Solution 2

Verify Content Type Configuration

Rule out library-specific corruption or complex custom content type conflicts by testing in a clean document library environment.

Free Microsoft Office alternative

Try WPS Office for Your Document Needs

If you are facing persistent integration or display issues with Microsoft Word, consider using WPS Office as a lightweight, reliable, and completely free alternative that seamlessly handles all standard document formats.

1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
2. Install the Software: Run the installer and follow the on-screen prompts to set up WPS Office on your computer.
3. Open Your Documents: Right-click your .docx files, select 'Open with', and choose WPS Writer to enjoy seamless and fast document editing.

Fully compatible with Microsoft Word (.docx), Excel, and PowerPoint formats.Lightweight installation with extremely fast document loading times.Familiar, tabbed user interface ensuring a zero-learning-curve transition.Free built-in PDF editing and document management features.

microsoft office alternative - wps office

Frequently Asked Questions

Why does repairing Microsoft Office not fix the SharePoint Document ID issue?

Repairing Office usually fixes local file associations or corrupted binaries. In this case, users with the exact same Word build experience different behaviors, indicating the issue originates from the SharePoint Server 2019 metadata configuration or content type handling, rather than the local Office client.

Can this document ID issue happen in SharePoint Online?

This specific metadata sync delay has primarily been isolated to SharePoint Server 2019 on-premises environments (such as build 16.0.10404.20003). Standard testing indicates it does not typically reproduce in SharePoint Online.

How do content types affect Document IDs in SharePoint?

Content types define the specific metadata schemas (like Document IDs) associated with a file. When multiple content types are attached to a SharePoint library, Word must sync these properties upon opening. A delay or failure in this server-to-client sync process causes the ID to only appear on subsequent opens.

Document & File Issues