Windows  ·  medium  ·  Microsoft Office

A document always opens read-only

A document opens read-only every time, with no other user holding it. Six different settings produce this and they are in six different places — but they can be told apart by where the read-only notice appears.

What you see

The title bar says Read-Only, or a yellow bar offers an Edit Anyway or Enable Editing button. Saving prompts for a new file name. Other people may be able to edit the same file normally.

What is actually wrong

In rough order of frequency: the file has the read-only attribute set, it was saved with the read-only-recommended flag, it is an email attachment opening in reading view, it is marked as final, editing is restricted, or the folder it sits in does not grant write access. A stale lock file is a seventh, and is covered separately.

Codes and articles

opens read-onlyMark as FinalRestrict Editingreading view attachmentsread-only recommended

Start here — find out which fix applies

A script that runs the 1 inspection command from the write-up below and prints what each one returned. It reads the machine and changes nothing — every command that could write, delete, start or stop is excluded from it by construction. Run this first, then pick the fix its output points at.

Download the read-only diagnosticchanges nothing · safe to run before reading

Fixes (4)

Clear the read-only attribute and the recommendation flag
PowerShell as the affected user10 minuteslow riskreversible

The file follows the problem wherever it is copied. Start here.

  1. Check the file system attribute.

    PowerShell
    Get-ItemProperty 'C:\path\to\file.docx' | Select-Object Name, IsReadOnly, Attributes

    Files restored from a backup, extracted from some zip tools, or copied from a CD or a locked-down share very often arrive with this set, and nothing in Office says so beyond the words Read-Only.

  2. Clear it.

    PowerShell
    Set-ItemProperty 'C:\path\to\file.docx' -Name IsReadOnly -Value $false

  3. For a whole folder that came from a backup.

    PowerShell
    Get-ChildItem 'C:\path\to\folder' -Recurse -File | Where-Object IsReadOnly | Set-ItemProperty -Name IsReadOnly -Value $false

  4. If the attribute was already clear, check the read-only-recommended flag, which is saved inside the document. Open it, then File → Save As → Tools → General Options, and clear "Read-only recommended".

    This flag is stored in the file, so it survives copying and appears on every machine. It is a recommendation rather than a lock, which is why Edit Anyway works and why it is so often left in place for years.

Confirm it workedThe file opens for editing with no read-only notice and saves in place.
If you need to undo itSet IsReadOnly back to $true, or re-tick Read-only recommended, if the protection was deliberate.
Download this fix as a PowerShell script1 step you do yourself · asks before each step
Stop attachments opening in reading view
The Office application, as the affected user10 minuteslow riskreversible

The file is opened directly from an email and is read-only, but editable once saved to disk.

  1. Understand what is happening first. An attachment opened from Outlook is extracted to a temporary folder, so editing it in place would save changes somewhere the user will never find them again. Read-only here is protecting them.

    The right answer is nearly always to save the attachment somewhere real and work on that, not to turn the protection off. Changes made to the temporary copy are lost when the folder is cleared.

  2. Save the attachment to a proper location and open it from there. That resolves it without changing any setting.

  3. If the behaviour is unwanted anyway, it is a per-application setting: File → Options → General → clear "Open e-mail attachments and other uneditable files in reading view".

  4. Note this does not bypass Protected View, which is separate and applies to files from the internet zone. If a yellow Enable Editing bar remains, that is Protected View and is covered by the document-will-not-open entry.

Confirm it workedA saved copy of the attachment opens for editing normally.
If you need to undo itRe-tick the reading view option.
Remove protection applied inside the document
The Office application20 minuteslow riskreversible

A banner says the document is marked as final, or editing is restricted.

  1. For Mark as Final: File → Info → Protect Document → Mark as Final to toggle it off, or simply press Edit Anyway on the banner.

    Mark as Final is a courtesy flag, not security. Anyone can turn it off in two clicks, and it is worth saying so to anyone who is relying on it to protect a document.

  2. For Restrict Editing: Review → Restrict Editing → Stop Protection. If it was applied with a password you need that password — there is no supported way around it.

  3. For an Excel worksheet: Review → Unprotect Sheet, or Unprotect Workbook for the structure.

  4. Check for Information Rights Management, which shows a permissions banner rather than a read-only one. That is enforced by the service and can only be changed by the document owner or a rights administrator.

  5. If the document must stay protected but this user needs to edit it, change the protection rather than removing it — Restrict Editing allows exceptions per user.

Confirm it workedThe document accepts edits and saves in place.
If you need to undo itReapply the same protection from the same menu. Note the password if one was in use before you remove it.
Check write access to the folder
PowerShell as the affected user20 minuteslow riskreversible

Everything in one folder or share opens read-only.

  1. Test whether the user can actually write there, rather than reading the permissions and inferring it.

    PowerShell
    try { $t = Join-Path '\\server\share\folder' ('wtest_' + [guid]::NewGuid() + '.tmp'); [IO.File]::WriteAllText($t,'x'); Remove-Item $t; 'WRITE OK' } catch { 'WRITE DENIED: ' + $_.Exception.Message }

    Effective access on a share is the intersection of the share permission and the NTFS permission, and reading either one alone routinely gives the wrong answer. Writing a file is the only test that accounts for both.

  2. If the write fails, look at both layers.

    PowerShell
    (Get-Acl '\\server\share\folder').Access | Select-Object IdentityReference, FileSystemRights, AccessControlType

  3. On the file server, check the share-level permission as well.

    PowerShell
    Get-SmbShareAccess -Name 'share' | Select-Object AccountName, AccessRight

  4. Have the permission corrected by whoever owns the share. Granting it locally on the client is not possible and attempting it wastes time.

  5. If the write test succeeds and files still open read-only, go back to the attribute and document-protection fixes — the share is not the cause.

Confirm it workedThe write test succeeds and documents in the folder open for editing.
If you need to undo itNo client-side change was made. Any permission change on the server should be reversed by whoever applied it if it turns out to be wrong.
Download this fix as a PowerShell script2 steps you do yourself · asks before each step

Related faults

"File is locked for editing by another user" — including when that user is youWindowsOffice applications open slowly, hang, or start with a blank windowWindows"Microsoft has blocked macros from running because the source of this file is untrusted"WindowsA document will not open — Protected View, "file format is not valid", or a corrupt fileWindowsDouble-clicking a file opens Office but not the documentWindowsPrinting from Office fails, prints blank, or goes to the wrong printerWindows

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.