R
Robert__S
Guest
I asked this question recently, but I've pinpointed the action that causes it, so I'm reposting it in the Windows area.
When I have the Preview pane open in the file explorer, I get a dialog with "Word could not create the work file. Check the temp environment variable". If I dismiss this dialog twice, the contents of the file appear in the preview pane.
My temp environment variable points to C:\Users\<user>\AppData\Local\Temp.
When I examine the permissions on this folder in the Security tab of the Properties dialog, it says "No permissions have been assigned for this object.
Warning: this is a potential security risk because anyone who can access this object can take ownership of it. The object’s owner should assign permissions as soon as possible." There are a whole lot of files in this folder, so I assume that it has read/write permissions.
I've tried deleting the temp folder. It is re-created with read/write permissions, but it has appeared with no permissions again today.
This problem occurs with two user accounts on this machine.
The "chkdsk" command does not reveal any errors.
I'm using Windows Pro 10 64 bit
Continue reading...
When I have the Preview pane open in the file explorer, I get a dialog with "Word could not create the work file. Check the temp environment variable". If I dismiss this dialog twice, the contents of the file appear in the preview pane.
My temp environment variable points to C:\Users\<user>\AppData\Local\Temp.
When I examine the permissions on this folder in the Security tab of the Properties dialog, it says "No permissions have been assigned for this object.
Warning: this is a potential security risk because anyone who can access this object can take ownership of it. The object’s owner should assign permissions as soon as possible." There are a whole lot of files in this folder, so I assume that it has read/write permissions.
I've tried deleting the temp folder. It is re-created with read/write permissions, but it has appeared with no permissions again today.
This problem occurs with two user accounts on this machine.
The "chkdsk" command does not reveal any errors.
I'm using Windows Pro 10 64 bit
Continue reading...