C:\Users\[username]\AppData\Local\Microsoft\Windows\INetCache\Content.MSO with a random name instead of the expected location. Word shows no errors whatsoever — the user believes the document was saved correctly, when in fact it is lost deep inside the cache. According to Microsoft, the problem only occurs with the Save/Save As + PDF + SharePoint combination. Using export or saving to another location completely bypasses the bug. Some users reported that rolling back to a previous version of Word resolves the issue, but Microsoft has not yet given an official response on when a fix will be released. The Register sent a request, but the company did not reply. ### 💡 Why it matters This is an unpleasant reminder that even familiar tools can quietly let you down. It is especially critical for those who regularly save PDF documents to SharePoint Online and rely on the silent "successful" save. The file goes to a random folder without any warning, so a user may only discover the loss much later. Until Microsoft releases a fix, it's better to play it safe: check where the file is actually being saved, or use export, which is unaffected by the bug. ### 🧩 Context This is not Microsoft's first failure recently. There have previously been issues with pasting in Excel, a botched Microsoft 365 update that deactivated Office 2016 and 2019, and even the random deletion of customer data before the retention period expired. September's Windows update also brought serious bugs — from audio and domain device problems to File History failures, some of which were fixed in the September 22 preview patch, while others remain unresolved. Against this backdrop, the PDF bug looks like yet another episode in a string of instability across the Microsoft ecosystem.Source: www.theregister.com · post in Telegram