Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix Word could not create the work file

Word could not create the work file: Fix a Broken Temp Path and Cache Location

10 min read Updated October 5, 2026 Outlook & Office Applications

Fix it now

The message is “Word could not create the work file. Check the temp environment variable.” Microsoft’s documented fix is not the temp folder most people go to: it is a missing Content.Word folder inside INetCache, a missing %userprofile% variable, or stale Office preview handlers left behind by a change of Office bitness.

Run these first in an elevated Command Prompt; chkdsk will ask to schedule at restart

sfc.exe /scannow
chkdsk /r /f
  1. Create the folder Microsoft names. Paste %LOCALAPPDATA%\Microsoft\Windows\INetCache into Explorer’s address bar and, inside it, create a folder called Content.Word. Create the INetCache path by hand first if it does not exist.
  2. Check the user environment variable. Open Start > Settings > System > About > Advanced system settings > Environment Variables and confirm there is a user variable named %userprofile% whose value is your profile folder, for example C:\Users\yourname. Add it if it is missing.
  3. Restart Word and open any document.
  4. If it still fails and this machine was moved from 64-bit to 32-bit Office, turn the Explorer preview pane off and retest. That is the documented workaround for the preview-handler half of this fault.
  5. Where the preview pane has to stay on, the Office preview handler registrations are what need removing; export the branch before you touch it and expect to lose Office document previews until they are reinstalled.

Run the malware scan and the two commands above before the folder work. Microsoft puts them first because a damaged file system produces the same message and rebuilding folders on a failing disk wastes the trip.

If Word opens a document and saves it, you are done. If it still cannot create its work file, the next section explains which of the three documented causes you are in.

Why it happens

Word does not edit your document on disk. It stages the work somewhere else and writes back to the original when you save, and this message means the staging area could not be created. The message tells you to check the temp environment variable, which is where almost everybody starts, and it is worth ruling out – but Microsoft’s own resolution for this error goes to three other places, and two of them are nothing to do with TEMP.

The first is a specific folder. Microsoft’s instruction is to create a folder named Content.Word inside %LOCALAPPDATA%\Microsoft\Windows\INetCache. Cleanup utilities, migration tools and roaming profile handling all remove that subfolder without recreating it, and Word cannot make it for itself. Creating INetCache alone is not enough; the named subfolder is the thing.

The second is the %userprofile% user environment variable, which Microsoft tells you to add pointing at the profile folder. The third is unrelated to folders altogether: on a machine that has been moved from 64-bit Office to 32-bit, the file preview handlers Office registered under the old architecture are left behind, and the preview pane calling into them produces this message. That is why the same error can appear when you have not even opened Word – the Explorer preview pane triggers it.

The four Windows codes that travel with it name the layer that failed and nothing more. 0x80070002 is ERROR_FILE_NOT_FOUND, the system cannot find the file specified. 0x80070003 is ERROR_PATH_NOT_FOUND, the system cannot find the path specified. 0x800700CE is ERROR_FILENAME_EXCED_RANGE, the filename or extension is too long. 0x8007000F is ERROR_INVALID_DRIVE, the system cannot find the drive specified. Each says where the request died; none says which of the three causes above put it there.

The Content.Word folder is missing

You have this one if The INetCache path exists, and there is no Content.Word inside it.

  1. Create Content.Word inside %LOCALAPPDATA%\Microsoft\Windows\INetCache.
  2. Restart Word and open a document.
  3. If the folder disappears again, find the cleanup tool or logon script that is removing it, because recreating it every week is not a fix.

The %userprofile% variable is missing from the user’s environment

You have this one if The folder exists and Word still fails, and the problem followed the user from another machine or a migration.

  1. Open Start > Settings > System > About > Advanced system settings > Environment Variables.
  2. Under User variables, add %userprofile% with the profile folder as its value, for example C:\Users\yourname.
  3. Sign out and back in, then test Word again.

Office was switched from 64-bit to 32-bit and the preview handlers were not

You have this one if The message appears in Explorer with the preview pane on, or in Word straight after an architecture change, and file previews stopped working at the same time.

  1. Turn the preview pane off in Explorer and retest. If the message stops, this is your cause.
  2. Remove the stale Office preview handler registrations if the pane has to stay on, exporting the registry branch first.
  3. Reinstall Office cleanly at the architecture you actually want, which is the durable answer.

Changing Office between 32-bit and 64-bit means removing the existing installation, not upgrading it in place. Leftovers from the old architecture are exactly what this cause is made of.

The file system or the profile is damaged

You have this one if Other applications misbehave too, or the machine has had a bad shutdown, or 0x80070570 appears alongside this message.

  1. Run a full malware scan, then sfc.exe /scannow, then chkdsk /r /f, in that order.
  2. Test with a second Windows account on the same machine to separate the profile from the installation.
  3. Where the profile is at fault, build a new one rather than repairing Office, which does not rewrite user folders.

Full reference

What Microsoft actually tells you to do, in order

  1. Scan the machine for malware.
  2. Run sfc.exe /scannow from an elevated Command Prompt.
  3. Run chkdsk /r /f and let it schedule itself for the next restart if it asks.
  4. Add a user environment variable named %userprofile% pointing at the profile folder.
  5. Create a folder named Content.Word inside %LOCALAPPDATA%\Microsoft\Windows\INetCache.
  6. Turn off the preview pane, or remove the Office preview handler registrations, where the machine was switched from 64-bit to 32-bit Office.

The codes and what each one rules in

Code Windows error Published text
0x80070002 2, ERROR_FILE_NOT_FOUND The system cannot find the file specified
0x80070003 3, ERROR_PATH_NOT_FOUND The system cannot find the path specified
0x800700CE 206, ERROR_FILENAME_EXCED_RANGE The filename or extension is too long
0x8007000F 15, ERROR_INVALID_DRIVE The system cannot find the drive specified

0x800700CE points somewhere specific and is worth separating out. It is a length failure rather than a permission or existence failure, and it turns up where a redirected profile prefixes an already deep path with a long UNC. Shortening the share or home-folder path is the fix; permissions are a red herring for that one. 0x8007000F is the mirror image: a drive letter in the path that is not connected at the moment Word needs it, which is what you get when working paths have been pointed at a mapping made only at logon.

Redirected and roaming profiles

  • Redirecting the local application data folder to a share is a common cause of this and of several neighbouring faults. Avoid it.
  • If the profile roams, confirm the cache folders are included rather than excluded from the profile, and that something creates them at logon.
  • On pooled desktops, have the profile tool create Content.Word at logon rather than assuming it survives.
  • Keep the home-folder path short. A long UNC prefix plus a deep document path is what produces 0x800700CE.

Checks worth doing before you accept it is fixed

  • Confirm you can create a file by hand in the INetCache folder under the affected account.
  • Confirm %TEMP% opens and that you can create and delete a file there.
  • Check free space on the volume holding the profile.
  • Confirm the Temp folder is not holding tens of thousands of files, which slows every open.

Why repairing Office rarely helps here

An Office repair rewrites the installation. It does not create user profile folders, it does not add environment variables to a user’s environment, and on a machine that has been moved between architectures it can leave the same preview registrations behind. That is why people repair, reboot, and see the same message. Fix the folder and the variable first; keep the repair for the case where the preview handlers need rebuilding after you have removed the stale ones.

Every code this article covers

Code What it points at Source
Word could not create the work file Word could not create the working copy it stages a document through; the full message continues “Check the temp environment variable” Microsoft Learn
0x80070002 Windows error 2, ERROR_FILE_NOT_FOUND: the system cannot find the file specified Microsoft Learn
0x80070003 Windows error 3, ERROR_PATH_NOT_FOUND: the system cannot find the path specified Microsoft Learn
0x800700CE Windows error 206, ERROR_FILENAME_EXCED_RANGE: the filename or extension is too long Microsoft Learn
0x8007000F Windows error 15, ERROR_INVALID_DRIVE: the system cannot find the drive specified Microsoft Learn

Confirm the fix worked

  1. Open a document, make a change and save it, and confirm no message appears.
  2. Confirm Content.Word exists inside %LOCALAPPDATA%\Microsoft\Windows\INetCache and that files appear in it while a document is open.
  3. Confirm the %userprofile% user variable is present under Environment Variables and points at the right folder.
  4. Sign out and back in, then repeat the first test, to prove nothing is removing the folder at logon.
  5. If the preview pane was involved, turn it back on and confirm a document preview renders without the message returning.

Questions people ask about this

Is my Office installation damaged?

Almost never. This is a folder that needs to exist and a variable that needs to be set, both of which live outside Office. That is also why a repair so often changes nothing: it rewrites the installation and leaves the profile exactly as it was.

Is there anything to buy to fix this?

No. It costs nothing. Everything involved is part of Windows or of an Office installation you already have, and no licence, edition or subscription changes the behaviour.

Why did it start after a profile migration?

Because migration tools copy documents and settings but do not always recreate the cache folders underneath them, and they can leave the environment pointing at the old machine’s paths. Both produce exactly this message on the first document you open.

Excel and PowerPoint work. Why only Word?

Word leans on the working file hardest, so it fails first. The others usually start failing shortly afterwards, or only on larger files. Fix it once and all of them stop complaining.

The message appears when I have not opened Word at all.

Then the Explorer preview pane is calling into an Office preview handler. That is the documented symptom on a machine moved from 64-bit to 32-bit Office. Turn the preview pane off to confirm it, then deal with the stale registrations.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office has detected a problem with this file: Protected View and File Block Rules Free Fix SMTP Protocol Errors 0x800CCC60 and 0x800CCC6F: Server Returns an Unexpected Reply Free Fix SMTP Errors 0x800CCC78 and 0x800CCC79: Outlook Cannot Send, Server Rejects Address Free Fix Outlook 0x800CCC13 Cannot Connect to Network: Repair a Broken Winsock Stack
โ† Back to Knowledge Base