Microsoft Confirms Bizarre Word Bug: PDFs Saving to Hidden Folders with Random Names

If you recently tried saving or exporting a Microsoft Word document as a PDF—only to find it completely vanished from your intended folder—you aren’t alone.

Microsoft has officially confirmed a widespread and frustrating bug in Microsoft Word. When users attempt to save a document hosted on a network share or mapped network drive as a PDF, the app silently routes the generated file to a hidden Windows temporary cache directory. To make matters worse, instead of using your original document title, Word assigns the output a completely random, alphanumeric string.

Here is a breakdown of why this error is happening, where your missing files are going, and what you can do until an official patch rolls out.

What Is Happening with Word’s PDF Export?

The issue manifests primarily when working with files stored on network drives, shared corporate folders, or mapped network locations.

When executing a standard Save As or Export to PDF command in Word, the software completes the job without displaying an explicit error message. However, the resulting PDF never arrives in your chosen folder.

  Expected Destination:                      Actual Destination (Bug):
 ┌───────────────────────────┐              ┌───────────────────────────┐
 │ Network Drive (Z:\Share)  │   ──►X──►    │ Windows INetCache Folder  │
 ├───────────────────────────┤              ├───────────────────────────┤
 │ Document_Final.pdf        │              │ 458d72b7.pdf (Random Name)│
 └───────────────────────────┘              └───────────────────────────┘

The Two Core Symptoms:

1. Wrong Destination Folder: Rather than saving locally or to your network directory, Word dumps the file into a buried system cache directory:

   C:\Users\<username>\AppData\Local\Microsoft\Windows\INetCache\Content.MSO\

2. Random Filenames: The file name ignores your document title altogether, renaming the PDF to hexadecimal/alphanumeric strings like 1f10f000.pdf or 458d72b7.pdf.

Why Is This Bug Occurring?

While Microsoft continues to investigate a permanent fix, the root cause appears tied to how Microsoft Word handles temporary background caching during network file operations.

When processing network documents, Word generates a cached instance inside the local INetCache temporary folder. Under normal circumstances, Word compiles the converted PDF locally and then moves the finished PDF to the target destination path specified by the user.

Because of a breakdown in this handoff process, Word completes the local render inside INetCache but fails to push the renamed file back to the network drive, leaving it stranded as an unnamed temporary cached object.

How to Work Around the Issue Right Now

While an official Microsoft Office update is in development to permanently address the pathing glitch, you can use these tested workarounds to prevent your PDFs from going missing:

1. Move the File Locally Before Saving

• Copy the source Word document from your network drive or share to your local Desktop or Documents folder.

• Open the local copy and execute File > Export or Save As > PDF.

• Move the newly created PDF back to your network location.

2. Use Microsoft Print to PDF

Instead of using Word’s built-in Save As PDF or Export functions:

• Go to File > Print (or press Ctrl + P).

• Select Microsoft Print to PDF from your list of available printers.

• Click Print, specify your network folder, and type your desired filename manually.

3. Recover Lost PDFs from the Cache

If you recently lost a file and need to recover it without re-exporting:

• Press Win + R to open the Run dialog box.

• Paste the following path (replace <username> with your Windows account name) and hit Enter:

  %localappdata%\Microsoft\Windows\INetCache\Content.MSO\

• Sort files by Date Modified to locate your recently created PDF files with random names.

Final Thoughts

Silent file saves to obscure system folders can disrupt daily workflows, especially for office environments heavily reliant on shared network drives. Keep an eye on incoming Microsoft 365 / Office updates for an official release note patch resolving this behavior.