Whenever I attempt to open an existing document using Word 2016 on my Windows 10 computer, I encounter an error:
Word could not create the work file. Check the temp environment variable.
Although I am able to edit and save the document without any issues, the error message persists in the background and produces an annoying sound every time I open a document. I have attempted to create a new document in Word and successfully save it, but upon reopening the file, the same error message appears.
In my search for a solution, I have come across articles that suggest using regedit to verify that the Cache environment variable is set correctly.
I have confirmed that my variable is set to %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache, which is the recommended setting. However, I have noticed that the aforementioned location is marked as read-only in Windows, which strikes me as unusual.
I am unsure whether this is a normal occurrence or if it is related to my problem. Has anyone recently found a solution to this error message?
2 Answers
Introduction
Microsoft Word is one of the most popular word processing software used all over the world. However, like any other software, it is prone to errors and bugs. One such error is the “Word could not create the work file. Check the temp environment variable” error in Word 2016 on Windows 10. This error message can be frustrating and can interfere with your work if not resolved quickly. In this blog post, we will discuss the causes of this error and how to fix it.
Cause of the Error
The “Word could not create the work file. Check the temp environment variable” error occurs when Word is unable to create a temporary file to save the changes you make to a document. This can happen due to several reasons, including:
1. Insufficient Disk Space
If your computer’s hard drive is running out of space, Word may not be able to create a temporary file to save your changes. This can cause the “Word could not create the work file” error. To fix this issue, you need to free up some disk space on your computer.
2. Incorrect Temp Environment Variable
The error can also occur if the temporary environment variable is incorrect or corrupted. The temporary environment variable is a system variable that tells Word where to store temporary files. If it is incorrect or corrupted, Word may not be able to create a temporary file to save your changes.
3. Read-only Location
As mentioned in the original post, the location where the temporary files are stored may be set to read-only. This can cause the “Word could not create the work file” error. This is not normal, and you need to change the settings to allow Word to create temporary files.
Solutions to the Error
Now that we know the causes of the “Word could not create the work file” error, let’s look at some solutions to fix it.
1. Free Up Disk Space
As mentioned earlier, the error can occur if your computer’s hard drive is running out of space. To free up disk space, you can delete unwanted files or uninstall programs that you no longer use. You can also use disk cleanup tools like CCleaner to remove temporary files and other junk files that are taking up space on your hard drive.
2. Check the Temp Environment Variable
To check the temp environment variable, follow these steps:
- Press the Windows key + R to open the Run dialog box.
- Type “sysdm.cpl” and press Enter to open the System Properties window.
- Click on the “Advanced” tab and then click on the “Environment Variables” button.
- Under “System Variables,” look for the “TEMP” and “TMP” variables. If they are not set to the correct location, click on “Edit” and set them to “%USERPROFILE%AppDataLocalTemp”.
- Click “OK” to save the changes.
3. Change the Location of the Temporary Files
If the location where the temporary files are stored is set to read-only, you need to change the settings to allow Word to create temporary files. To do this, follow these steps:
- Open File Explorer and navigate to the location where the temporary files are stored (usually C:Users%username%AppDataLocalTemp).
- Right-click on the “Temp” folder and select “Properties”.
- Click on the “Security” tab and then click on the “Edit” button.
- Select your user account from the list and then check the “Full Control” box under “Allow”.
- Click “OK” to save the changes.
4. Repair or Reinstall Microsoft Office
If none of the above solutions work, you can try repairing or reinstalling Microsoft Office. To repair Microsoft Office, follow these steps:
- Open the Control Panel and click on “Programs and Features”.
- Find Microsoft Office in the list of installed programs and click on it.
- Click on “Change” and then select “Repair”.
- Follow the on-screen instructions to complete the repair process.
If repairing Microsoft Office does not work, you can try reinstalling it. To reinstall Microsoft Office, you need to uninstall it first and then reinstall it using the installation media.
Conclusion
The “Word could not create the work file. Check the temp environment variable” error can be frustrating, but it can be fixed using the solutions discussed in this blog post. It is essential to keep your computer’s hard drive clean and free up disk space regularly to avoid such errors. Checking the temp environment variable and changing the location of the temporary files can also help fix the error. If all else fails, repairing or reinstalling Microsoft Office can be a last resort.
I experienced the same error message while using the Word Preview feature simply by selecting a file in Windows Explorer. Based on your description of the message appearing in the background, it seems likely that you are encountering a similar issue. I was able to resolve this problem by deleting specific Registry Keys as follows:
Word Preview : HKCR\CLSID\{84F66100-FF7C-4fb4-B0C0-02CD7FB668FE}
PowerPoint Preview : HKCR\CLSID\{65235197-874B-4A07-BDC5-E65EA825B718}
Excel Preview : HKCR\CLSID\{00020827-0000-0000-C000-000000000046}
Microsoft indicates that this issue may occur when a user installs the 64-bit version of Office, uninstalls it, and then installs the 32-bit version. However, I am skeptical that I ever installed the 64-bit version.