Link to home
Create AccountLog in
Avatar of SmartPcGuy
SmartPcGuyFlag for United States of America

asked on

Word cannot save or create this file. make sure that the disk you want to save the file on is not full, write-protected, or damaged.

Hello all

"Word cannot save or create this file. make sure that the disk you want to save the file on is not full, write-protected, or damaged."

All the documents that generate this error are in a large directory on the root of C of a Windows 7 machine.  All documents were transferred over using Forensit's profile transfer wizard, from a windows XP machine.  The profile on the XP machine was an administrator, and the profile on the Windows 7 machine is administrator.  I verified all permissions were correct (since it is a stand-alone machine, I gave the files full-access to "everyone"), but I'm still getting this message.

The user can save the files elsewhere on the computer, but they want to be able to make changes to a document, re-name it, and save it in the same directory as the original.  That's how this message is appearing.

Also, there was a "read-only" issue that I had to resolve last week with this same directory.  I had to resolve it by migrating the profile to the built-in administrator account.  All other attempts to remove "read-only" status failed.

Any help would be appreciated.

Thanks!

 User generated image
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of SmartPcGuy

ASKER

The solution only partially solved the issue.

The files and folder that were having this issue were on the root of C, so I couldn't change the permissions on the top folder, at risk of jeopardizing the C drive's permissions.  Therefore, I moved all the files and folders to a new folder, then added the ownership permissions FOR A SECOND TIME, after the move.  

The issue was that the files and folders were on the root of C.  The ownership was already set to the user's account.  I just had to re-apply it.

THANKS!