Docs · guide

Word could not create the work file, and what it is really about

By Alberto Gulotta · Updated 25 September 2026 · 12 min read

Word could not create the work file names the TEMP variable, but Microsoft’s own page on the error never corrects TEMP. It gives four methods: a malware and disk check, a new user variable, a Content.Word folder, and turning off the File Explorer preview pane or deleting three registry keys.

Microsoft has a troubleshooting page on this exact sentence, and it is the source for everything below. It is titled “‘Could not create the work file’ error in Office” and sits on Microsoft Learn, where its address now leads into the previous-versions section; the four methods in the table above are its four sections in its own order. Where a step here goes beyond that page, the page it came from is named in the sentence.

1. Start with the File Explorer Preview pane, because it costs nothing. Open a folder of Word documents, then View › Show › Preview pane, and make sure it is unchecked. If the message was appearing as you clicked through files rather than as you opened them, start here.
2. Then repair the system files. Open Command Prompt as administrator, run sfc.exe /scannow, let it finish, then run chkdsk /r /f and restart. Microsoft puts this first.
3. Add the environment variable. Start › Settings › System › About › Advanced system settings › Environment Variables. Under User variables select New; in the name field type %userprofile%; in the value field type C:\Users\<username> with your own user folder name. OK out of every window and restart.
4. Rebuild the folder Word writes into. In File Explorer go to C:\Users\<username>\AppData\Local\Microsoft\Windows\INetCache, turning on Hidden items on the View ribbon if you cannot see it, and create a folder called Content.Word. Restart and try again.
5. Only then the registry, and back it up first. Microsoft’s own warning runs ahead of its instruction: “Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.” In the Registry Editor, File › Export writes that backup.
6. Delete the three preview-handler keys, then restart Windows. They are listed in the next section, one for each Office program. Microsoft’s page ends there: close Registry Editor, and restart Windows.

The second method is the one that looks invented, and it is not. Creating a new user variable whose name is %userprofile% reads like a mistake: %userprofile% is already a built-in variable, and putting percent signs in a variable name is not something anyone would think of. Microsoft’s wording is unambiguous: “In the Variable name field, enter %userprofile%. In the Variable value field, enter C:\Users\<username>.” It is step 5 and 6 of its own numbered list. Whether it helps on a given machine is a different question; that it is Microsoft’s instruction and not folklore is settled.

The keys Microsoft has you delete are Word Preview, PowerPoint Preview and Excel Preview, which is as plain a statement as the page makes that the fix is about the preview pane for all three programs, not about Word alone.

One published account is worth adding because it explains the timing. On Super User, the accepted answer begins: “In my case this error message popped up from the Word Preview just by selecting the file in Windows Explorer” — and the fix was the same three keys. If the ding arrives while you are clicking through a folder rather than while you are opening or saving, that is the preview handler, and method 4 is where to start rather than where to finish.

So the honest summary of scope is this. The instructions are Windows 10 and Windows 11 instructions, read off the menus they describe. Microsoft states no Office version on the page we read on 24 September 2026. The preview pane setting is a File Explorer setting rather than an Office one. None of that is a reason not to follow the page; it is a reason to know what you are being told and what you are inferring.

Not covered here. It does not cover the Mac, where the error message exists but the registry, INetCache and the File Explorer preview pane do not.

It does not cover the case where Word will not start at all, which is a different symptom with a different first step.

And it does not recommend a repair tool. Every method here is a menu, a command prompt or the registry editor already on the machine. What holds instead is simple: the four methods and the three registry keys are quoted from the Microsoft page that publishes them, with the date it was read.