Sage 50 · 2 min read · Updated August 24, 2026

The file cannot be restored to the selected directory" Sage 50 error

Sage 50 is telling you Windows blocked the restore because your user account cannot write to the folder you picked.


You tried to restore a backup and Sage 50 stopped you with:

The file cannot be restored to the selected directory because you do not have write permissions for this directory.

Despite the wording, nothing is wrong with your backup file. Sage 50 is reporting a Windows permission problem. The account you are running under is not allowed to create or replace files in the folder you chose as the restore destination, so the restore never starts.

Why Windows blocks the restore

A restore has to write new files into the destination folder. If that folder sits somewhere your account cannot modify, such as another user’s profile, a protected system location, or a network share with restricted access, Windows refuses the write and Sage 50 passes the refusal along as this message.

It also happens when the folder belongs to a previous installation or a different user, or when the folder is marked read-only at the share level on a server.

Restore to a folder you own

The simplest fix is to change the destination. Restore to a folder inside your own documents area, or to a new empty folder you create yourself on the local drive. If the restore completes there, the message was purely a permissions issue and you can move the restored data afterwards.

If you need the data in the original location, an administrator can grant your account modify rights on that folder through the folder’s security settings in Windows, and the restore should then go through.

Check the obvious causes first

A few quick checks resolve most cases. Confirm you are logged into Windows with your usual account rather than a temporary or limited one. If the destination is on a server, make sure the share allows changes and not just reading. If someone else created the folder, have them grant you access or pick a different folder. And if you are restoring over an existing company, make sure the old files are not open in Sage 50 on any machine, since a locked file can look like a permission failure.

When the restore still fails

If Windows permissions check out and the restore still refuses to run, the backup itself may be damaged or incomplete, and a permissions message can mask that. Our engineers handle damaged Sage 50 and Simply Accounting databases regularly, and we can evaluate the backup and tell you what is recoverable before any work begins. See our Sage 50 database repair service for what that covers, or contact us about the file for a free evaluation and quote.

If your real goal is moving this data into QuickBooks rather than back into Sage 50, that is a different job from a restore, and our Sage 50 to QuickBooks conversion page explains what carries over.